yahoo-eng-team team mailing list archive

[KaiLin <linkai3@xxxxxxxxxx>]

** Project changed: nova => openstack-api-site

** Description changed:

  when I give a specified tenant access to the specified private flavor, I
  use it like this :
  
  POST /v2/​{tenant_id}​/flavors/​{flavor_id}​/action
  {
      "addTenantAccess": {
          "tenant": "fake_tenant"
      }
  }
  tenant: The name of the tenant to which to give access.
  
  The response is:
  {
      "flavor_access": [
          {
              "flavor_id": "10",
              #here is "tenant_id"
              "tenant_id": "fake_tenant"
          },
          {
              "flavor_id": "10",
              "tenant_id": "openstack"
          }
      ]
  }
  
  when I use the private flavor to create VM in the specified tenant,it
  failed. But if I add the tenant access by using the tenant id,it can
  create VM successfully in the specified tenant .
  
  POST /v2/​{tenant_id}​/flavors/​{flavor_id}​/action
  {
      "addTenantAccess": {
          "tenant": "{tenant_id}"
      }
  }
+ I check the code, It also uses the "tenant" information as the "project id".
  
- I check the code, It also uses the "tenant" information as the "project id".
- So we should change "tenant" to "tenant_id" in the API of  the add Tenant Access to private flavor action.
+ So we should change the api guides in the add Tenant Access to private flavor action,
+ change "tenant: The name of the tenant to which to give access." to 
+ "tenant: The uuid of the tenant to which to give access."

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1358805

Title:
  Incorrect API in the add Tenant Access to private flavor action

Status in OpenStack API documentation site:
  New

Bug description:
  when I give a specified tenant access to the specified private flavor,
  I use it like this :

  POST /v2/​{tenant_id}​/flavors/​{flavor_id}​/action
  {
      "addTenantAccess": {
          "tenant": "fake_tenant"
      }
  }
  tenant: The name of the tenant to which to give access.

  The response is:
  {
      "flavor_access": [
          {
              "flavor_id": "10",
              #here is "tenant_id"
              "tenant_id": "fake_tenant"
          },
          {
              "flavor_id": "10",
              "tenant_id": "openstack"
          }
      ]
  }

  when I use the private flavor to create VM in the specified tenant,it
  failed. But if I add the tenant access by using the tenant id,it can
  create VM successfully in the specified tenant .

  POST /v2/​{tenant_id}​/flavors/​{flavor_id}​/action
  {
      "addTenantAccess": {
          "tenant": "{tenant_id}"
      }
  }
  I check the code, It also uses the "tenant" information as the "project id".

  So we should change the api guides in the add Tenant Access to private flavor action,
  change "tenant: The name of the tenant to which to give access." to 
  "tenant: The uuid of the tenant to which to give access."

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-api-site/+bug/1358805/+subscriptions