lxd, maas and manual do not make sense in list-clouds

[Mark Shuttleworth]

list-clouds is a lovely feature, but I think we have overcooked lxd, maas and manual.

maas is a type not a cloud. I would expect MAAS clouds to show up in list-clouds only if they have been defined in clouds.yaml, and then they would show up in their name. At some stage I would expect the ability to have MAAS clouds with multiple regions (think canonical/london and canonical/boston). But I definitely don't expect a 'generic' maas cloud to be in list-clouds until I define them, and then they are named local:foo

lxd is also a type of cloud. I think we can have a pre-defined lxd cloud called localhost though, with a single default region 'localhost'. So this would show up as type lxd, cloud localhost, region localhost. In future I expect we can define lxd clouds called foo, with regions corresponding to hosts that share the same lxd API credentials (each host being a 'region'). That would let me make a multi-region cloud out of a small set of servers and test / demo multi-region deployments that way.

manual is NOT a cloud and shouldn't be in the list. If we really want a reference to it, then we could add text like this after the listing:

Unsupported cloud types can still be used with the manual provider in Juju, see URL.

[Anastasia (anastasia-macmood)]

Fix against master: https://github.com/juju/juju/pull/5134

I have not explicitly called out manual as a cloud type as there are other cloud types that juju defines but they do not have public or built-in clouds.

Maybe we consider having a list-cloud-type command or have a flag for list-clouds that lists all cloud types that have not come up as types in cloud-list?...

[Mark Shuttleworth (sabdfl)]

It's pretty clear that "cloud types" and "known clouds" are totally
different beasts, and not to be conflated or confused.

[Anastasia (anastasia-macmood)]

Proposal above has been updated to:

a. list public, built-in and personal clouds sorted in alphabetical order within each group;
b. display message "No maas clouds configured." when no cloud of type 'maas' exist;
c. display message "Unsupported cloud types can still be used with the manual provider." all the time.

[Anastasia (anastasia-macmood)]

After some discussions and considerations, I've dropped all mentioning of maas or manual.

The output now looks like this:

juju list-clouds

CLOUD TYPE REGIONS
aws ec2 us-east-1, us-west-1, us-west-2, eu-west-1, eu-central-1, ap-southeast-1, ap-southeast-2 ...
aws-china ec2 cn-north-1
aws-gov ec2 us-gov-west-1
azure azure centralus, eastus, eastus2, northcentralus, southcentralus, westus, northeurope ...
azure-china azure chinaeast, chinanorth
cloudsigma cloudsigma hnl, mia, sjc, wdc, zrh
google gce us-east1, us-central1, europe-west1, asia-east1
joyent joyent eu-ams-1, us-sw-1, us-east-1, us-east-2, us-east-3, us-west-1
rackspace rackspace dfw, ord, iad, lon, syd, hkg
localhost lxd localhost

Plus your personal clouds.

[Anastasia (anastasia-macmood)]

Awful cut-and-paste.. with correct alignment....

CLOUD TYPE REGIONS
aws ec2 us-east-1, us-west-1, us-west-2, eu-west-1, eu-central-1, ap-southeast-1, ap-southeast-2 ...
aws-china ec2 cn-north-1
aws-gov ec2 us-gov-west-1
azure azure centralus, eastus, eastus2, northcentralus, southcentralus, westus, northeurope ...
azure-china azure chinaeast, chinanorth
cloudsigma cloudsigma hnl, mia, sjc, wdc, zrh
google gce us-east1, us-central1, europe-west1, asia-east1
joyent joyent eu-ams-1, us-sw-1, us-east-1, us-east-2, us-east-3, us-west-1
rackspace rackspace dfw, ord, iad, lon, syd, hkg
localhost lxd localhost

[Anastasia (anastasia-macmood)]

Output doesn't align correctly in the launchpad textfield (especially after the comment is saved).

Sample output is here http://pastebin.ubuntu.com/16121359/

[Mark Shuttleworth (sabdfl)]

Thanks you Anastasia, this looks much better.

Mark

[Mark Shuttleworth (sabdfl)]

\o/ thank you! Going to take it for a spin now :)