Bug 1109418 - [RFE] Improved Security Group and Rule Creation
Summary: [RFE] Improved Security Group and Rule Creation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: RHELOSP-RHCI
TreeView+ depends on / blocked
 
Reported: 2014-06-13 19:54 UTC by Matt Reid
Modified: 2016-04-18 06:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 07:57:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1326411 0 None None None Never

Description Matt Reid 2014-06-13 19:54:01 UTC
Description of problem:
It would be nice if Horizon gave more flexibility around security group and rule creation. Adding them one at a time through the UI can be very tedious, and it doesn't seem like there's an easy way to take a security group you set up in one instance and use it in a different instance of OpenStack, other than manually recreating each piece of it. It might be useful to allow importing and exporting rule sets. If there are common sets of ports to open, perhaps we could offer prebuilt sets that users could then extend if needed or pull into existing security groups?

Just seems like there's more we could do in this area to make it easier to get the ports open that you need to, and ensure that those settings are portable. If someone has a test environment they're playing around with, and they then set up production OpenStack, is there a good way for them to pull those security groups they set up and tested from test/dev into prod currently?

I can't speak towards if that's a legitimate use case, but it seems reasonable to me.

Comment 2 Matthias Runge 2015-12-08 07:57:03 UTC
upstream decided not to proceeed with this bug.


Note You need to log in before you can comment on or make changes to this bug.