juju2: how to edit a maas "cloud"?

[Andreas Hasenack]

On Wed, Apr 27, 2016 at 1:04 PM, John Meinel <john at arbash-meinel.com> wrote:

>
>
> On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack <andreas at canonical.com>
> wrote:
>
>> On Wed, Apr 27, 2016 at 10:59 AM, John Meinel <john at arbash-meinel.com>
>> wrote:
>>
>>> ...
>>>
>>>
>>>>
>>>>> As noted, the number of times you have to bootstrap should be going
>>>>> down, and if you are bootstrapping different-but-similar, then you again
>>>>> have a single config that can be reused.
>>>>>
>>>>
>>>> I'd love to be able to share a controller node with my colleagues. I
>>>> tried setting that up and creating a juju user, but in the end that user's
>>>> MAAS nodes were all allocated to "me" in MAAS, which was a bit unexpected.
>>>> The person running juju commands had his own MAAS credentials setup. Until
>>>> that is not setup, I can't keep a MAAS node allocated to my user 24/7, it's
>>>> an expensive resource. I need to play with this shared controller idea a
>>>> bit more.
>>>>
>>>>
>>>>
>>> Were they using the same model or had they created their own model to
>>> work in? It may be that you had given them Admin rights on the controller,
>>> which meant that "juju add-model" then uses the admin credentials by
>>> default. I've heard that users that aren't admin but can create models are
>>> being prompted for what credentials should be used for this model.
>>>
>>
>> They were not admins. This is what I did, from memory:
>> - bootstrapped on MAAS
>> - created a model for user foo
>> - created user foo, with --share for that model
>> - granted user foo write access acl to model foo
>> - sent the register line to the user
>>
>> That user already had a cloud for this MAAS server, with credentials. He
>> ran the register command, then deployed services. The MAAS nodes that got
>> these services were under my name, not his.
>>
>>
>
> Unfortunately, for the 2.0 series the credentials used to manage machines
> are tied to the model. He'll need to create a different model (juju
> add-model --credentials XXX) to create machines with different credentials.
> The problem is that generally visibility between machines/security
> groups/etc is not guaranteed between
>

Can he add another model without having to be an admin in the controller?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160427/82878fcd/attachment.html>