Comment 17 for bug 1768308

I'd like to challenge the need for model-constraints. The constraints stored in the model are just the values that will be used when applications are brought in without anything specified on their own. It's the same set of values, just if it's the default values the model thinks about.

I see nothing wrong with

juju add-model rickstuff --constraints mem=8G

It's just creating a model with the default constraints value set to 8G of ram.

I do agree that on bootstrap --constraints should be set for all models by default. At this point it's a control default option inherited by models on that controller shouldn't it be?

I do think that --bootstrap constraints should be its own entity as you're speaking about the actual controllers and not tied to default workloads of any sorts.