Clarify Security Groups "Add rule": Port range vs Single port

Bug #956773 reported by Lukas Ocilka on 2012-03-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
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

Devin Carlen (devcamcar) on 2012-03-16
Changed in horizon:
importance: Undecided → Wishlist
status: New → Confirmed
Gabriel Hurley (gabriel-hurley) wrote :

Does novaclient actually support portranges for security groups? If so, are there special flags that need to be set?

mikelococo (mikelococo) wrote :

"From" and "To" language evokes the idea of source and destination ports which is not what is meant here. You're really setting the first and last ports in a range. I don't think there's any sensible way to fix this bug that maintains 2 input fields. There should be a single "destination port" field that supports a sensible port specification syntax. I'm a fan of nmap syntax [1]:

 Single Port: 1234
 Port Range: 1234-1236
 Port List: 22,443,1234

This is related to #955878, which calls this problem out among others and was marked wontfix due to too many unrelated issues being reported in one bug.


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
Thierry Carrez (ttx) on 2013-02-21
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-04-04
Changed in horizon:
milestone: grizzly-3 → 2013.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers