yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #37468
[Bug 1490516] Re: security group cannot be applied to a specified port of an instance but only to all ports.
@javeme:
It seems that this is a feature request. Feature requests for nova are
done with blueprints [1] and with specs [2]. I'll recommend to read [3]
if not yet done. To focus here on bugs which are a failures/errors/faults
I close this one as "Invalid". The effort to implement the requested
feature is then driven only by the blueprint (and spec).
If there are any questions left, feel free to contact me (markus_z)
in the IRC channel #openstack-nova
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints
** Tags added: api security-group
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: New => 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/1490516
Title:
security group cannot be applied to a specified port of an instance
but only to all ports.
Status in OpenStack Compute (nova):
Invalid
Bug description:
Security group cannot be applied to a specified port of an instance,
but only to all ports.
In general [1], we just want to add a security group to a specified
port, but this is not supported by the API 'addSecurityGroup'.
We should allow that different security groups are applied to
different ports of an instance.
[1] such as an instance with an outside port and an inside port.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1490516/+subscriptions
References