yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #03295
[Bug 1161473] Re: API to add instance to a SecGroup should take ID not Name
** Changed in: nova
Status: Incomplete => 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/1161473
Title:
API to add instance to a SecGroup should take ID not Name
Status in OpenStack Compute (Nova):
Invalid
Bug description:
The API calls create instance boot and add Instance to Security Group
accept a security group name rather than an ID.
In Quantum Security Group Names are not constrained to be unique - so
if two groups are created with the same name it becomes impossible to
add instances to them via this API.
I think the right way to fix this is to change the Nova API to take
security group IDs instead of names.
Note there are tworelated bugs which can be fixed independently in advance of this API change:
- Make NovaQuntumSecurityGroupAPI validate that SecGroup names are unique within a project when it creates them (fixes the issue for users just of the Nova API - and makes the behavior consistent with Nova Security Groups)
https://bugs.launchpad.net/nova/+bug/1161472
- Nova should pass back a more meaningful message if Quantum finds multiple SecGroups with the same name
https://bugs.launchpad.net/nova/+bug/1161467
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1161473/+subscriptions