yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51068
[Bug 1254722] Re: Security group record in Server Details should include ID as well as Name
This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on.
** Changed in: nova
Status: Confirmed => Opinion
--
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/1254722
Title:
Security group record in Server Details should include ID as well as
Name
Status in OpenStack Compute (nova):
Opinion
Bug description:
This is one of the areas where the Nova v2 API is inconsistent,
exposed in this case because of the move towards Neutron.
In Nova-network a security group name is mandatory, and must be unique within the tenant.
In Neutron the name is optional, and all operations are based on the uuid.
However although all SecGroup operations are based on id/uuid, the
security group element of a server details response only includes
'name'. to add to the confusion if name is not defined for a Neutron
Security Group then name is set to the uuid.
The proposal is to add an 'id' field to the security group element, at
least for the Neutron driver and preferably for Nova Network as well.
Because this is generated in code which is shared between v2 and v3
APIs then we need to decide whether the V2 APi can be extended with
this additional field, or if it will have to remove the ID entries
(perhaps conditionally on whether an API extension is enabled)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1254722/+subscriptions