Multi user account management in juju

[Mark Shuttleworth]

There are two distinct features aiming for 1.21 which address your needs:

 * multiple environments in a single juju server
 * multiple users in a single juju server

The combination will allow you to:

 * bootstrap Juju once (perhaps across a few servers for HA)
 * create several user accounts on that Juju server
 * those users can then create environments as and when they need them
   * each environment has its own cloud credentials
   * the user can share the environment with selected other users

You're seeing the first parts of support for that combination show up in
the GUI now, but 1.21 will be the first cut of a release with those
capabilities. It will work for both the command line and the GUI, of
course :)

The main benefits of this are:

 * fewer machines devoted to Juju and more to actual workloads
 * faster environment startup (you re-use the existing Juju server)
 * easier onramp for new users (bootstrap is hard, do it once HA)
 * sharing of environments between a group of admins

Hope that helps,
Mark

On 19/01/15 14:15, Rick Harding wrote:
> Note that this is pre-support for a new feature in Juju 1.21 which is not
> yet released. This is multiple users accessing the same deployed
> environment and doesn't seem to quite match the requirements.
>
> Rick Harding
>
> On Mon, Jan 19, 2015 at 4:50 AM, Vahric Muhtaryan <vahric at doruk.net.tr>
> wrote:
>
>> Today I red the juju-gui 1.3.0 release , its supporting multiple user
>> https://jujugui.wordpress.com/2015/01/14/juju-gui-1-3-0-release/
>>
>> From: Malshan Peiris <malshan at hsenidmobile.com>
>>
>> Hi all,
>>
>> Is there a way in juju to do following (We are going to use AWS as deploy
>> target and ubuntu 14.04 as client).
>>
>> 1) Have multiple user accounts for juju-gui, where a certain user will
>> only see his/her work area. If possible, a reserved machine for a single
>> user. Currently I only know to confiure a single admin password.
>>
>> 2) Same as above, but deployment using juju command line. So individual
>> users should have unique keys to AWS account where they can only affect a
>> specific AWS instance, not the whole account (so they can't add / remove
>> AWS instances).
>>