The "Default" Security Group Is a Confusing Name

Bug #1020327 reported by John Postlethwait
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

The end-user perception seems to be that this "default" security group is named as such because it is applied by default, which is not true, it just happen to be THE default that Nova sets up. It should be given a more descriptive/explicit name as to not make end-users think that it will be applied by default.

Revision history for this message
Vish Ishaya (vishvananda) wrote :

um. The default group is applied by default afaik.

Revision history for this message
Mark McLoughlin (markmc) wrote :

John, if you can reproduce instances being created without the default security group, please provide instructions

The relevant code in nova/compute/api.py is:

 # Use 'default' security_group if none specified.
        if security_groups is None:
            security_groups = ['default']
        elif not isinstance(security_groups, list):
            security_groups = [security_groups]
        instance['security_groups'] = security_groups

and in _create_instance:

        if not security_group:
            security_group = 'default'

Changed in nova:
status: New → Incomplete
Revision history for this message
John Postlethwait (john-postlethwait) wrote :

Sorry guys, I filed this with the wrong information... This is invalid. You are both correct, it IS indeed applied by default.

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.