Comment 1 for bug 1621295

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.