yahoo-eng-team team mailing list archive

[Anil Vishnoi <1339266@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I would rather consider it enhancement than a bug. I created two VM
instances in my openstack setup.

VM1 ( id - 3d248e17-922c-4619-aa60-d30684108c01) & VM2 (id - acb0148f-
508d-4c6f-a9b1-4d160960764d).

I created pool (A) and added both of these VM instances as a pool
member. But when i see details of member VM1 (from member tab in horizon
lbaas view), i don't see the VM instance- id.

Member Details:
ID
    b6e2e91a-56f3-4da2-8abb-934db5b3bc91
Project ID
    5d787eb9991a4030beba90cf0ea2461d
Pool ID
    3715ddb0-acab-4a37-9db8-dcb47edc88ed
Address
    1.1.1.2
Protocol Port
    8000
Weight
    1
Admin State Up
    Yes
Status
    ACTIVE 


I think by definition of pool member its fine, but  I believe having pool member's original resource object id reference in the member object can make things bit more convenient. For example, i am writing my lbaas driver, in which for each pool member i want to fetch few stats from the ceilometer service, but ceilometer service requires instance-id in the rest api for fetching the stats. In the current state, to find out instance-id from the member object details, i need to fetch all the VM details for the tenant and then need to match based on private/floating ip of the VM. I feel its a bit cumbersome approach. 

So if member object can provide the resource id of  the associated
resource, it can make things more convenient in term of associating the
member with openstack resource.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: lb lbaas

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

Title:
  LBaaS: Member object doesn't contains VM instance id

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I would rather consider it enhancement than a bug. I created two VM
  instances in my openstack setup.

  VM1 ( id - 3d248e17-922c-4619-aa60-d30684108c01) & VM2 (id - acb0148f-
  508d-4c6f-a9b1-4d160960764d).

  I created pool (A) and added both of these VM instances as a pool
  member. But when i see details of member VM1 (from member tab in
  horizon lbaas view), i don't see the VM instance- id.

  Member Details:
  ID
      b6e2e91a-56f3-4da2-8abb-934db5b3bc91
  Project ID
      5d787eb9991a4030beba90cf0ea2461d
  Pool ID
      3715ddb0-acab-4a37-9db8-dcb47edc88ed
  Address
      1.1.1.2
  Protocol Port
      8000
  Weight
      1
  Admin State Up
      Yes
  Status
      ACTIVE 

  
  I think by definition of pool member its fine, but  I believe having pool member's original resource object id reference in the member object can make things bit more convenient. For example, i am writing my lbaas driver, in which for each pool member i want to fetch few stats from the ceilometer service, but ceilometer service requires instance-id in the rest api for fetching the stats. In the current state, to find out instance-id from the member object details, i need to fetch all the VM details for the tenant and then need to match based on private/floating ip of the VM. I feel its a bit cumbersome approach. 

  So if member object can provide the resource id of  the associated
  resource, it can make things more convenient in term of associating
  the member with openstack resource.

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