yahoo-eng-team team mailing list archive

[Matt <mreid@xxxxxxxxxx>]

Public bug reported:

It might save users potentially a lot of time if instead of only
offering an INGRESS and an EGRESS direction, if they could specify a
BOTH direction. Whenever someone needs to enter both an ingress and
egress rule for the same port they have to enter it twice, remembering
all of the information they need (since it can't be cloned). If they
forget to flip the direction the second time from the default value,
it'll error out as a duplicate and they'll have to try a third time. If
they messed up the second rule, there's no edit, so they would have to
delete it if they got a value wrong and do it all over again.

It would be awesome if the UI allowed for specifying both an ingress and
egress rule at the same time, even if all it did was create the ingress
and egress rows and put them in the table, at least they'd be guaranteed
to have the same configuration.

** Affects: horizon
     Importance: Undecided
         Status: New


** Tags: low-hanging-fruit ux

** Attachment added: "Can't create a rule that opens up a port in both directions at once"
   https://bugs.launchpad.net/bugs/1325736/+attachment/4124384/+files/Security_Rule_Creation_Direction.png

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1325736

Title:
  Security Group Rules can only be specified in one direction

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  It might save users potentially a lot of time if instead of only
  offering an INGRESS and an EGRESS direction, if they could specify a
  BOTH direction. Whenever someone needs to enter both an ingress and
  egress rule for the same port they have to enter it twice, remembering
  all of the information they need (since it can't be cloned). If they
  forget to flip the direction the second time from the default value,
  it'll error out as a duplicate and they'll have to try a third time.
  If they messed up the second rule, there's no edit, so they would have
  to delete it if they got a value wrong and do it all over again.

  It would be awesome if the UI allowed for specifying both an ingress
  and egress rule at the same time, even if all it did was create the
  ingress and egress rows and put them in the table, at least they'd be
  guaranteed to have the same configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1325736/+subscriptions