Drop the 'default' model

[Mark Shuttleworth]

With putting the juju server application and unit information (jujud and juju-db) into the controller model status explicitly, I think we can drop the default model. So you have to add-model after bootstrap or provide a -m modelname to bootstrap.

[Richard Harding (rharding)]

Mark, I'm very concerned with this one especially in light of the work to add controller/mongo to the controller model as applications.

We added the default model because users would bootstrap and start deploying things right away into the controller model. Then they were unable to destroy-model the controller model and felt like they were guided into deploying into the wrong place.

We encourage users to not put things in the controller model and so we have the default so that users are guided to a path that's safe for experimentation without requiring a fresh bootstrap when they find they don't want that deployment/model config/etc around. Putting that extra step back to users after we tried that and have gotten feedback from users that it's not helpful feels like a step backward.

[Mark Shuttleworth (sabdfl)]

I guess my thinking, having played with it a lot over the past few
months as 2.0 has matured, is that "add-model foo" is very natural to
do, and means that you don't have lots of "default" models.

Another approach might be to name the initial model with the same name
as the controller.

But I think the big change of *explicitly showing* ongo and jujud in the
status mean that showing the controller model by default won't create
the illusion of having a blank canvas to work with. Initially, you would
bootstrap and see "nothing here", which made it tempting to deploy stuff
there.

Mark

[dann frazier (dannf)]

Even if it were not the default, I'd like to have a way to tell bootstrap that I know what I'm doing, so please do not create the default model (--no-default-model?). My use case is that I have a jenkins server that instantiates a unique juju model for each job - the default is never used. So I currently either need to remove it after each bootstrap, or special case it when processing the model list. Not a huge problem of course, but a papercut IMO.