[Bug 1129720] Re: juju instances not including the "default" security group

Martin Packman martin.packman at canonical.com
Thu Jan 9 12:50:45 UTC 2014


I'm not sure adding the default group is the right fix for wanting ad-
hoc per environment rules. I'd prefer if juju started tolerating
external tampering with the environment-specific juju group it adds to
all machines it creates. We could potentially report via status any
addition ports opened.

There are arguments in all directions depending on the exact use-case
though. In cases where you have more than one environment on the same
cloud account (for instance, a staging and a live deployment), the fact
the default group applies to both could cause issues, would be
impossible to monitor/alter one without affecting the other. If the
account is also used for non-juju work, sharing rules via the default
group could be either a convenience or a hole.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1129720

Title:
  juju instances not including the "default" security group

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



More information about the Ubuntu-server-bugs mailing list