LBaaS: Member object doesn't contains VM instance id
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-
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-
Project ID
5d787eb9991
Pool ID
3715ddb0-
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: |
added: api removed: lb |
Changed in neutron: | |
importance: | Undecided → Wishlist |
Changed in neutron: | |
assignee: | nobody → Arpita Deshpande (arpita-deshpande) |
Changed in neutron: | |
status: | New → Incomplete |
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