LBaaS: Member object doesn't contains VM instance id

Bug #1339266 reported by Anil Vishnoi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Expired
Wishlist
Unassigned

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.

Tags: api lbaas
tags: added: api
removed: lb
Changed in neutron:
importance: Undecided → Wishlist
Changed in neutron:
assignee: nobody → Arpita Deshpande (arpita-deshpande)
Revision history for this message
senthilmageswaran (senthilmageswaran-muthusamy) wrote :

It is possible to create pool members which are not necessary VM instances.
In that case, there wont be an instance ID, and it would be empty in member-show

Changed in neutron:
status: New → Incomplete
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 172 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Arpita Deshpande (arpita-deshpande) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.