I have a slightly different requirement. Currently in our OpenStack cloud, if a user wants to use Juju, it must install a Juju controller in his project. It would be useful to use a single controller for the whole cloud and to just switch the project which the controller uses. Juju already can deal with multiple models, so it would just need to distinguish which models exist in a given project. It also should be possible to authenticate with OpenStack credentials in the Juju GUI.
— Beppe > Date: Tue, 29 Aug 2017 19:29:14 +0530 > From: Akshat Jiwan Sharma <akshatji...@gmail.com> > To: juju@lists.ubuntu.com > Subject: Juju-gui only show localhost as the deployment option > Message-ID: > <cakzbvx07nrkvhyvuzcqg6fzxnox0xi+igyy6h_nroyrmo0g...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Is there a way I can configure multiple providers using the Juju-GUI? Also > is there a way I can configure cloud providers based on user access roles? > For example a user with access to a particular model can deploy only to a > specific cloud provider. > > If one controller can manage multiple clouds and one controller can have > many users then what is the mapping of the relationship between the users > and the clouds? > > Thanks, > Akshat > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
