Drop the 'default' model
Bug #1621295 reported by
Mark Shuttleworth
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
3.0 |
Triaged
|
Medium
|
Unassigned |
Bug Description
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.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
To post a comment you must log in.
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.