[Yahoo-eng-team] [Bug 1161472] Re: Nova-Quantum SecurityGroup API should enforce unique group names
** 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/1161472 Title: Nova-Quantum SecurityGroup API should enforce unique group names 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 Nova Security Group Names are constrained to be unique. 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 the Nova API. To maintain backwards compatibility with Nova Security Groups, and to avoid issues during Instance Creation or when adding Instances to a Security Group the NovaQauntumSecurityGroupAPI should enforce uniqueness of Group Names. This will provide consistency for users of the Nova API (it will still be possible to break this model by creating SecGroups with non-unique names in Quantum). The longer term solution would be for the Nova API to work with SecurityGroup IDs (which are always unique) rather than Names. Forcing Quantum (which is already using uuids for Security groups) to also impose unique names to satisfy Nova does not feel like a good fix. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1161472/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1161472] Re: Nova-Quantum SecurityGroup API should enforce unique group names
The example you used was passing in a security group ID (which will always be unique), but the create call allows either a name or an ID to be passed in. In he case of a name being used then the bug is still valid. ** Changed in: nova Status: Invalid => Confirmed -- 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/1161472 Title: Nova-Quantum SecurityGroup API should enforce unique group names Status in OpenStack Compute (Nova): Confirmed Bug description: The API calls create instance boot and add Instance to Security Group accept a security group name rather than an ID. In Nova Security Group Names are constrained to be unique. 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 the Nova API. To maintain backwards compatibility with Nova Security Groups, and to avoid issues during Instance Creation or when adding Instances to a Security Group the NovaQauntumSecurityGroupAPI should enforce uniqueness of Group Names. This will provide consistency for users of the Nova API (it will still be possible to break this model by creating SecGroups with non-unique names in Quantum). The longer term solution would be for the Nova API to work with SecurityGroup IDs (which are always unique) rather than Names. Forcing Quantum (which is already using uuids for Security groups) to also impose unique names to satisfy Nova does not feel like a good fix. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1161472/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1161472] Re: Nova-Quantum SecurityGroup API should enforce unique group names
** Changed in: nova Status: Fix Committed => Fix Released -- 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/1161472 Title: Nova-Quantum SecurityGroup API should enforce unique group names Status in OpenStack Compute (Nova): Fix Released Bug description: The API calls create instance boot and add Instance to Security Group accept a security group name rather than an ID. In Nova Security Group Names are constrained to be unique. 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 the Nova API. To maintain backwards compatibility with Nova Security Groups, and to avoid issues during Instance Creation or when adding Instances to a Security Group the NovaQauntumSecurityGroupAPI should enforce uniqueness of Group Names. This will provide consistency for users of the Nova API (it will still be possible to break this model by creating SecGroups with non-unique names in Quantum). The longer term solution would be for the Nova API to work with SecurityGroup IDs (which are always unique) rather than Names. Forcing Quantum (which is already using uuids for Security groups) to also impose unique names to satisfy Nova does not feel like a good fix. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1161472/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
