Registered controllers have no cloud

[Cory Johns]

When a shared controller is registered, it doesn't seem to get a value for the "cloud" field (e.g., http://pastebin.ubuntu.com/23670398/). Nor does there seem to be any way to set it (presumably this would have to be done during registration or bootstrap).

One effect of this is that default credentials for the cloud aren't used, and you have to manually specify the credential using --credential when doing things like add-model.

[Cory Johns (johnsca)]

This is affecting conjure-up now, as we need to be able to tell what cloud a controller is to compare it against a spell's whitelist / blacklist.

I know that in the future, and currently with JAAS, controllers could support multiple clouds. But we at least need a way to see what clouds they do support (ideally from the show-controller output) to know what credential to use and whether to list them per the white/blacklist.

[Cory Johns (johnsca)]

Sorry, I meant list-controllers in that last comment, since show-controllers doesn't do what one would expect: https://bugs.launchpad.net/juju/+bug/1652106

[Anastasia (anastasia-macmood)]

I think that this will be mitigated by addressing bug # 1643822. I'll mark this report as its duplicate.

We are also working on making the life in multi-cloud, multi-client paradigm simpler. A lot of commands that have previously expected local knowledge of clouds or credentials will now also check your remote clouds and credentials so the need to download from the controller will be reduced.