Ubuntu
maas package

document that nodes are brought up without security groups or firewall rules

Bug #975464 reported by Jamie Strandboge
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Won't Fix
Undecided
Unassigned
Precise
New
High
Dave Walker
maas (Ubuntu)
Triaged
High
kavya
Ubuntu ubuntu-12.04
Precise
Won't Fix
High
Unassigned
Ubuntu ubuntu-12.04

Bug Description

This is a tracking bug for a dependency of the maas MIR (bug #961344).

For 12.04, clearly document that nodes are brought up without firewall rules or security group in place.

Jamie Strandboge (jdstrand)
tags: added: rls-p-tracking
Changed in maas (Ubuntu Precise):
milestone: none → ubuntu-12.04
status: New → Triaged
Kate Stewart (kate.stewart)
Changed in ubuntu-release-notes:
importance: Undecided → Medium
importance: Medium → Undecided
status: New → Won't Fix
Jamie Strandboge (jdstrand)
Changed in maas (Ubuntu Precise):
importance: Undecided → High
Revision history for this message
Steve Langasek (vorlon) wrote :

Jamie, can I ask you to make a first pass at some text for this? I'm not entirely sure what "security groups" means in this context.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Hmm, I was hoping the server team would do that. Fyi, since MAAS behaves in a 'cloudy' way, people might expect the same terminology that they might find in EC2 or OpenStack, so security groups refer to hosts being in some sort of group that all share the same firewall ruleset.

First crack:

* MAAS does not currently support network security groups or apply firewall rules to individual nodes. Administrators desiring this protection may customize nodes after installation. A future release of MAAS may include this functionality (LP: #975468)

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Dave, can you review my crack at release note text?

kavya (kavyamensin123)
Changed in maas (Ubuntu):
assignee: nobody → kavya (kavyamensin123)
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in maas (Ubuntu Precise):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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