[Yahoo-eng-team] [Bug 1624276] Re: Metering - metering-label-rule doesn't need 'tenant_id'

2016-09-28 Thread Ukesh 
** Changed in: python-neutronclient
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1624276

Title:
  Metering - metering-label-rule doesn't need 'tenant_id'

Status in neutron:
  Invalid
Status in python-neutronclient:
  Invalid

Bug description:
  In current metering-label-rule, 'tenant_id' is included into 
RESOURCE_ATTRIBUTE_MAP[1].
  However, even if we specify 'tenant_id' by using CLI or REST-API, 'tenant_id'
  isn't stored on DB[2] and we cannot see the result.  Therefore, I think
  following fixes are necessary:

  1. 'tenant_id' definition should be removed at extensions/metering.py.
  2. Remove 'tenant_id' option from CLI(meter-label-rule)

  [CLI]
  (neutron) meter-label-rule-create my-label 192.168.2.0/24 --tenant-id 
8ae2759224e94ed0a66011315a32d07c
  Created a new metering_label_rule:
  +---+--+
  | Field | Value|
  +---+--+
  | direction | ingress  |
  | excluded  | False|
  | id| 4ef89142-b216-42c7-9455-abc3a8fd1d3d |
  | metering_label_id | 543ce87e-2190-46d5-9d79-3fd113681372 |
  | remote_ip_prefix  | 192.168.2.0/24   |
  +---+--+

  [REST-API]
  $ source devstack/openrc admin admin
  $ export TOKEN=`openstack token issue | grep  ' id ' | get_field 2`
  $ curl -s -X POST -H "accept:application/json" -H "content-type: 
application/json" -d '{"metering_label_rule": {"remote_ip_prefix": 
"172.16.3.0/24", "metering_label_id": "d34c612f-3e02-433b-ba9f-f13b2ac6511d", 
"direction": "ingress", "excluded": false, "tenant_id": 
"8ae2759224e94ed0a66011315a32d07c"}}'  -H "x-auth-token:$TOKEN" 
localhost:9696/v2.0/metering/metering-label-rules | jq "."

  {
"metering_label_rule": {
  "remote_ip_prefix": "172.16.3.0/24",
  "direction": "ingress",
  "metering_label_id": "d34c612f-3e02-433b-ba9f-f13b2ac6511d",
  "id": "d300512f-db84-4680-92cd-dafb91bec33b",
  "excluded": false
}
  }

  [1] 
https://github.com/openstack/neutron/blob/master/neutron/extensions/metering.py#L79
  [2] 
https://github.com/openstack/neutron/blob/master/neutron/db/metering/metering_db.py#L171

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1624276/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1628386] [NEW] both project_id & tenant_id are available in 'meter-label-create' output

2016-09-28 Thread Ukesh 
Public bug reported:

Neutron returns both project_id and tenant_id for 'meter-label-create'
request as below,

$ neutron meter-label-create NAME --os-cloud devstack-admin
Created a new metering_label:
+-+--+
| Field   | Value|
+-+--+
| description |  |
| id  | 36f5ef6e-1187-4058-84c7-663601312fc6 |
| name| NAME |
| project_id  | 19bc004d6e0f4c689e114cbe2826fd0d |
| shared  | False|
| tenant_id   | 19bc004d6e0f4c689e114cbe2826fd0d |
+-+--+

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1628386

Title:
  both project_id & tenant_id are available in 'meter-label-create'
  output

Status in neutron:
  New

Bug description:
  Neutron returns both project_id and tenant_id for 'meter-label-create'
  request as below,

  $ neutron meter-label-create NAME --os-cloud devstack-admin
  Created a new metering_label:
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | id  | 36f5ef6e-1187-4058-84c7-663601312fc6 |
  | name| NAME |
  | project_id  | 19bc004d6e0f4c689e114cbe2826fd0d |
  | shared  | False|
  | tenant_id   | 19bc004d6e0f4c689e114cbe2826fd0d |
  +-+--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1628386/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1624276] Re: Metering - metering-label-rule doesn't need 'tenant_id'

2016-09-26 Thread Ukesh 
** Also affects: python-neutronclient
   Importance: Undecided
   Status: New

** Changed in: python-neutronclient
 Assignee: (unassigned) => Ukesh (ukeshkumar)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1624276

Title:
  Metering - metering-label-rule doesn't need 'tenant_id'

Status in neutron:
  Confirmed
Status in python-neutronclient:
  New

Bug description:
  In current metering-label-rule, 'tenant_id' is included into 
RESOURCE_ATTRIBUTE_MAP[1].
  However, even if we specify 'tenant_id' by using CLI or REST-API, 'tenant_id'
  isn't stored on DB[2] and we cannot see the result.  Therefore, I think
  following fixes are necessary:

  1. 'tenant_id' definition should be removed at extensions/metering.py.
  2. Remove 'tenant_id' option from CLI(meter-label-rule)

  [CLI]
  (neutron) meter-label-rule-create my-label 192.168.2.0/24 --tenant-id 
8ae2759224e94ed0a66011315a32d07c
  Created a new metering_label_rule:
  +---+--+
  | Field | Value|
  +---+--+
  | direction | ingress  |
  | excluded  | False|
  | id| 4ef89142-b216-42c7-9455-abc3a8fd1d3d |
  | metering_label_id | 543ce87e-2190-46d5-9d79-3fd113681372 |
  | remote_ip_prefix  | 192.168.2.0/24   |
  +---+--+

  [REST-API]
  $ source devstack/openrc admin admin
  $ export TOKEN=`openstack token issue | grep  ' id ' | get_field 2`
  $ curl -s -X POST -H "accept:application/json" -H "content-type: 
application/json" -d '{"metering_label_rule": {"remote_ip_prefix": 
"172.16.3.0/24", "metering_label_id": "d34c612f-3e02-433b-ba9f-f13b2ac6511d", 
"direction": "ingress", "excluded": false, "tenant_id": 
"8ae2759224e94ed0a66011315a32d07c"}}'  -H "x-auth-token:$TOKEN" 
localhost:9696/v2.0/metering/metering-label-rules | jq "."

  {
"metering_label_rule": {
  "remote_ip_prefix": "172.16.3.0/24",
  "direction": "ingress",
  "metering_label_id": "d34c612f-3e02-433b-ba9f-f13b2ac6511d",
  "id": "d300512f-db84-4680-92cd-dafb91bec33b",
  "excluded": false
}
  }

  [1] 
https://github.com/openstack/neutron/blob/master/neutron/extensions/metering.py#L79
  [2] 
https://github.com/openstack/neutron/blob/master/neutron/db/metering/metering_db.py#L171

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1624276/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1622974] [NEW] nova.api throws 500 for 'nova availability-zone-list'

2016-09-13 Thread Ukesh 
Public bug reported:

$ nova availability-zone-list
ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: 
req-d7fd01f2-24ae-4f95-a607-8a72ada21fee)

** Affects: nova
 Importance: Undecided
 Status: New

** Attachment added: "nova api log"
   https://bugs.launchpad.net/bugs/1622974/+attachment/4739943/+files/n-api.log

-- 
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/1622974

Title:
  nova.api throws 500 for 'nova availability-zone-list'

Status in OpenStack Compute (nova):
  New

Bug description:
  $ nova availability-zone-list
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-d7fd01f2-24ae-4f95-a607-8a72ada21fee)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1622974/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1619161] Re: flavor-list need return the extra-specs information directly

2016-09-02 Thread Ukesh 
With the current api design, we have to do multiple request to get the
extra-spec of all the flavors.

extra-spec information is not returned in '/v2.1/​{tenant_id}​/flavors'
as well as in '/v2.1/​{tenant_id}​/flavors/details' api(s) and so, to
get extra-spec for every single flavor, we have to call the api,
'/v2.1/​{tenant_id}​/flavors/​{flavor_id}​/os-extra_specs'.

** Changed in: nova
   Status: Confirmed => Invalid

-- 
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/1619161

Title:
  flavor-list need return the extra-specs information directly

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===
  Now the command of nova flavor-list --extra-specs can view 
  extra-specs information, but I use --debug to see a lot of 
  http GET requests for getting the extra_specs information
  of each flavor.

  With the increase of the flavors, it will get more and more 
  GET requests. This will affect the performance of the query.

  I think that the query returns a list of flavor, it should 
  directly contain extra_specs information.

  Steps to reproduce
  ==
  A chronological list of steps which will bring off the
  issue you noticed:
  * I performed the command:
$ nova --debug flavor-list --extra-specs

  Environment
  ===
  1. Exact version of OpenStack
   Mitaka

  
  Logs & Configs
  ==
  The debug info:
  DEBUG (session:195) REQ: curl -g -i -X GET 
http://10.43.239.62:8774/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/1/os-extra_specs
 -H "User-Agent: python-novaclient" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1}ae80c1ee126b1a4464c13c843706cc6a5b1bf259"
  DEBUG (connectionpool:368) "GET 
/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/1/os-extra_specs HTTP/1.1" 200 66
  DEBUG (session:224) RESP: [200] date: Thu, 01 Sep 2016 06:27:08 GMT 
connection: keep-alive content-type: application/json content-length: 66 
x-compute-request-id: req-15182618-4b28-4c78-87ef-d51f8da309f3 
  RESP BODY: {"extra_specs": {}}

  DEBUG (session:195) REQ: curl -g -i -X GET 
http://10.43.239.62:8774/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/2/os-extra_specs
 -H "User-Agent: python-novaclient" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1}ae80c1ee126b1a4464c13c843706cc6a5b1bf259"
  DEBUG (connectionpool:368) "GET 
/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/2/os-extra_specs HTTP/1.1" 200 19
  DEBUG (session:224) RESP: [200] date: Thu, 01 Sep 2016 06:27:09 GMT 
connection: keep-alive content-type: application/json content-length: 19 
x-compute-request-id: req-b519d74e-ed98-48e9-90be-838287f7e407 
  RESP BODY: {"extra_specs": {}}

  DEBUG (session:195) REQ: curl -g -i -X GET 
http://10.43.239.62:8774/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/3/os-extra_specs
 -H "User-Agent: python-novaclient" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1}ae80c1ee126b1a4464c13c843706cc6a5b1bf259"
  DEBUG (connectionpool:368) "GET 
/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/3/os-extra_specs HTTP/1.1" 200 19
  DEBUG (session:224) RESP: [200] date: Thu, 01 Sep 2016 06:27:09 GMT 
connection: keep-alive content-type: application/json content-length: 19 
x-compute-request-id: req-ad796e53-e8be-4caa-b182-219a1f3e63ca 
  RESP BODY: {"extra_specs": {}}

  DEBUG (session:195) REQ: curl -g -i -X GET 
http://10.43.239.62:8774/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/97/os-extra_specs
 -H "User-Agent: python-novaclient" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1}ae80c1ee126b1a4464c13c843706cc6a5b1bf259"
  DEBUG (connectionpool:368) "GET 
/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/97/os-extra_specs HTTP/1.1" 200 39
  DEBUG (session:224) RESP: [200] date: Thu, 01 Sep 2016 06:27:09 GMT 
connection: keep-alive content-type: application/json content-length: 39 
x-compute-request-id: req-4c8d466e-d013-4549-ae74-8ea4ca578061 
  RESP BODY: {"extra_specs": {"hw:numa_nodes": "1"}}

  DEBUG (session:195) REQ: curl -g -i -X GET 
http://10.43.239.62:8774/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/99/os-extra_specs
 -H "User-Agent: python-novaclient" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1}ae80c1ee126b1a4464c13c843706cc6a5b1bf259"
  DEBUG (connectionpool:368) "GET 
/v2/ed952123e0cc4ced9e581a7710bc24d5/flavors/99/os-extra_specs HTTP/1.1" 200 39
  DEBUG (session:224) RESP: [200] date: Thu, 01 Sep 2016 06:27:09 GMT 
connection: keep-alive content-type: application/json content-length: 39 
x-compute-request-id: req-9663e309-b421-45dd-9d6a-43f5a5464eab 
  RESP BODY: {"extra_specs": {"hw:numa_nodes": "2"}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1619161/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1526719] Re: metadata should be allowed to be search option

2016-01-06 Thread Ukesh 
** Also affects: python-novaclient
   Importance: Undecided
   Status: New

** Changed in: python-novaclient
 Assignee: (unassigned) => Ukesh (ukeshkumar)

-- 
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/1526719

Title:
  metadata should be allowed to be search option

Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  New

Bug description:
  we allow following options to be used when filter instance, however 
  metadata is not in the allow list while metadata is used by user (non-admin)

  56feb2b649cc25edd8d747806e2b9d6e0b3b8c5d added ip6 into the list and another 
microversion 
  might be used to offer metadata as option

   opt_list = ('reservation_id', 'name', 'status', 'image', 'flavor',
   'ip', 'changes-since', 'all_tenants')
   if api_version_request.is_supported(req, min_version='2.5'):
   opt_list += ('ip6',)
   return opt_list

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1526719/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1526719] Re: metadata should be allowed to be search option

2016-01-06 Thread Ukesh 
** Also affects: python-openstackclient
   Importance: Undecided
   Status: New

** Changed in: python-openstackclient
 Assignee: (unassigned) => Ukesh (ukeshkumar)

** Description changed:

- we allow following options to be used when filter instance, however 
+ we allow following options to be used when filter instance, however
  metadata is not in the allow list while metadata is used by user (non-admin)
  
- 56feb2b649cc25edd8d747806e2b9d6e0b3b8c5d added ip6 into the list and another 
microversion 
+ 56feb2b649cc25edd8d747806e2b9d6e0b3b8c5d added ip6 into the list and another 
microversion
  might be used to offer metadata as option
  
-  opt_list = ('reservation_id', 'name', 'status', 'image', 'flavor',
-  'ip', 'changes-since', 'all_tenants')
-  if api_version_request.is_supported(req, min_version='2.5'):
-  opt_list += ('ip6',)
-  return opt_list
+  opt_list = ('reservation_id', 'name', 'status', 'image', 'flavor',
+  'ip', 'changes-since', 'all_tenants')
+  if api_version_request.is_supported(req, min_version='2.5'):
+  opt_list += ('ip6',)
+  return opt_list
+ 
+ In python-novaclient & python-openstackclient, we have to add 'metadata'
+ optional argument to nova list & openstack server list commands

-- 
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/1526719

Title:
  metadata should be allowed to be search option

Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  New
Status in python-openstackclient:
  New

Bug description:
  we allow following options to be used when filter instance, however
  metadata is not in the allow list while metadata is used by user (non-admin)

  56feb2b649cc25edd8d747806e2b9d6e0b3b8c5d added ip6 into the list and another 
microversion
  might be used to offer metadata as option

   opt_list = ('reservation_id', 'name', 'status', 'image', 'flavor',
   'ip', 'changes-since', 'all_tenants')
   if api_version_request.is_supported(req, min_version='2.5'):
   opt_list += ('ip6',)
   return opt_list

  In python-novaclient & python-openstackclient, we have to add
  'metadata' optional argument to nova list & openstack server list
  commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1526719/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp