"Default" naming for default security group can confuse end users

[Liz Blanchard]

It would be great to rename the "Default" security group to be "Default security group" so that when users click on this name as a link in the table in Horizon's "Access & Security" section it will be clear that this is a security group. Also, it would be best to update this in the API to be sure they are consistent. This will also help when users are looking to select this security group from the list in the Launch Instance modal in Horizon.

[Julie Pichon (jpichon)]

I believe this is created automatically by Nova/Neutron (depending on which is managing the security groups), I don't think this can be changed at the Horizon level. We're simply retrieving the existing data.

[Liz Blanchard (lblanchard)]

Ah okay, thanks for the heads up on this one Julie! Do you think I should reassign this to the nova project?

Thanks,
Liz

[Akihiro Motoki (amotoki)]

A question:

> It would be great to rename the "Default" security group to be "Default security group" so that when users click on this name as a link in the table it will be clear that this is a security group.

Isn't "Default" in the security table sufficient?
It is displayed in "Name" column in the security table, so "Default security group" doesn't provide much.
Changing the description to "Default security group" might be better.

AFAIK, "default" is a RESERVED name in security group implementation in nova/neutron.
Changing name directly leads to a backward-incompatible API change and it will be rejected with high possibility. (At least, I disagree changing the default name as neutron-core if it is proposed.)
We can replace "default" to other name when displaying security group in Horizon layer, but we also need to consider the consistency between API and Horizon. I am afraid that different names between API and Horizon may cause another confusion to users. Thought?

[Ana Krivokapić (akrivoka)]

I don't like the idea of indroducing inconsistencies between API and UI. In this case, the table in the UI looks quite similar to the output of 'nova secgroup-list' in the CLI. I don't see it as confusing, but that's just my opinion.

[Liz Blanchard (lblanchard)]

Hi All,

Yes I'd agree that we should maintain consistency between the UI and API here. I like Akihiro's suggestion of changing the description at the very least. Would another option be to change the terminology in both API and UI? I can continue to test this with end users too, but we observed 3 of the 5 participants in our usability study with end users get tripped up by this.

Thanks,
Liz

[Julie Pichon (jpichon)]

It sounds like it would be worthwhile to open the bug with Nova and Neutron, as they create the default security groups (we can add them to this bug so they also have the history). Changing the description sounds like a good idea to me, since it's shown in Horizon's "Access & Security" too and shouldn't affect anything else that depends on the security groups.

[Christopher Yeoh (cyeoh-0)]

For backwards compatibility reasons we can't just change the name of the default security group in Nova. I think however it may be possible to update the description for the default as that is a lot less likely to break any existing apps.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/102509

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/102522

[Gary W. Smith (gary-w-smith)]

Moving the Horizon priority to low to match the Nova priority.

[Joe Gordon (jogo)]

It sounds like the issue is that its unclear what is an isn't a security group in horizon. I don't think nova should change the default name.

[Julie Pichon (jpichon)]

From comment #7 the idea was to update the default description, rather than the name.

[Abhishek Talwar (abhishek-talwar)]

Hi Ravindra,

I wanted to ask if you are currently working on the neutron part of this bug as I would like to pick it up. I currently see you inactive on this bug so kindly let me know if I can work on this and close this.

Thanks and Regards
Abhishek Talwar

[Ravindra Joshi (ravindra-joshi)]

You can take up this bug.

Thank you.
Regards,
Ravindra Joshi

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Abhishek Talwar
Sent: Wednesday, November 19, 2014 11:54 AM
To: Ravindra Joshi
Subject: [Bug 1291570] Re: "Default" naming for default security group can confuse end users

Hi Ravindra,

I wanted to ask if you are currently working on the neutron part of this bug as I would like to pick it up. I currently see you inactive on this bug so kindly let me know if I can work on this and close this.

Thanks and Regards
Abhishek Talwar

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1291570

Title:
  "Default" naming for default security group can confuse end users

Status in OpenStack Dashboard (Horizon):
  Confirmed
Status in OpenStack Neutron (virtual network service):
  In Progress
Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  It would be great to rename the "Default" security group to be
  "Default security group" so that when users click on this name as a
  link in the table in Horizon's "Access & Security" section it will be
  clear that this is a security group. Also, it would be best to update
  this in the API to be sure they are consistent. This will also help
  when users are looking to select this security group from the list in
  the Launch Instance modal in Horizon.

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

DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/135552

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/102522
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/135552
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f20b725b4a056090567504441d59ed88bfe62cef
Submitter: Jenkins
Branch: master

commit f20b725b4a056090567504441d59ed88bfe62cef
Author: abhishek.talwar <email address hidden>
Date: Wed Nov 19 15:24:42 2014 +0530

    Change description of default security group

    The description for default security group in neutron
    is “default”.
    This confuses the end users, so updated the description
    from “default” to “Default security group”.
    Closes-Bug: #1291570

    Change-Id: I9e024de935e8d17afd3d459cfa17e9feb0cd79fa

[OpenStack Infra (hudson-openstack)]

Change abandoned by Kyle Mestery (<email address hidden>) on branch: master
Review: https://review.openstack.org/102509
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Akihiro Motoki (amotoki)]

There is nothing to do in horizon. Removing horizon from the affected project.