On 27/03/15 17:13, Ali Saidi wrote: > I'm trying to understand how multiple users can interact with MaaS and > Juju. > > It seems like some support is now available [1,2], although I'm not certain > what state it's in. Is there any documentation about the different use > models for multiple users interacting with Juju? Is there a roadmap of > multi-user features?
Yes, this is a focus for 1.23 and 1.24, due before May. > In my ideal model someone using Juju would request a number of nodes from > MaaS and then be able to deploy only to them using Juju. However, I'd > prefer to not require a separate orchestration server for each user. Is > this possible? MAAS has multi-user support now; you can allocate machines to users, and each user can get tokens to pull machines from the available pool or from the set of machines pre-allocated to them. When you setup a Juju environment on MAAS, you provide the token, which will pull from your MAAS pool. Any additions to the Juju environment will pull machines from the same pool in MAAS. In Juju, we are just getting the initial multi-user capabilities in the current development branch. The idea, though, is that you can have multiple users administering a Juju environment. Initially, you'll just be able to say who can administer an environment (and possibly who can have read-only access to view that environment). In the roadmap, you'll get role-based access control not only over access to the environment, but over what sorts of operations are allowed, down to the fine level of who can scale which services, reconfigure them, or connect services. Does that help? Mark -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
