Clarify Security Groups "Add rule": Port range vs Single port
Bug #956773 reported by
Lukas Ocilka
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Gabriel Hurley |
Bug Description
Opening a single port actually means writing the same port into
From Port and To Port. It would be nice if the UI could handle
both: Port range / Single port (combo-box switcher might help)
and additionally users would instantly understand that they are
adding a port range or single port
UI doesn't need to 100% reflect `nova secgroup-add-rule` syntax
Changed in horizon: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
summary: |
- UX Improvements: Security Groups: Add a rule: Port range vs Single port + Clarify Security Groups "Add rule": Port range vs Single port |
Changed in horizon: | |
importance: | Wishlist → Low |
assignee: | nobody → Nebula (nebula) |
milestone: | none → grizzly-1 |
Changed in horizon: | |
assignee: | Nebula (nebula) → nobody |
Changed in horizon: | |
milestone: | grizzly-1 → grizzly-2 |
Changed in horizon: | |
assignee: | nobody → Gabriel Hurley (gabriel-hurley) |
status: | Confirmed → Won't Fix |
status: | Won't Fix → In Progress |
importance: | Low → Medium |
Changed in horizon: | |
milestone: | grizzly-2 → grizzly-3 |
Changed in horizon: | |
status: | In Progress → Fix Committed |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Does novaclient actually support portranges for security groups? If so, are there special flags that need to be set?