No way to set default constraints for new models after bootstrap

[Jason Hobbs]

After I bootstrap, there is no way to set default constraints for new models - I have to set them per model.

The problem with that is that I want to have different constraints for my bootstrap node (or rather, no constraints - I just deploy with --to) than for my nodes used in my models.

I have a CI system that creates new models dynamically, I don't want to have to add a configuration option for it to set constraints on each model it creates - it would be much simpler to be able to specify the default constraints for all new models directly after I bootstrap.

I was able to work around this by using bootstrap constraints to specify an empty tags constraint, which overrides the normal constraints.
juju bootstrap --config agent-stream=devel integrationmaas --to hayward-00
                --constraints="tags=hw-jhobbs" --bootstrap-constraints="tags="

Still, that's not very intuitive, and this should be a setting that should be able to be changed after bootstrap..

[John A Meinel (jameinel)]

don't we have "juju model-defaults" which is exactly the "use this setting for all newly created models".

Did we just miss that constraints need to be part of the model-config/model-defaults interactions?

It looks like we do have 'juju set-model-constraints', but IMO those should probably just fold into 'model-config' as a 'constraints' field and then get inherited from model-defaults.

juju model-config constraints=BLAH

seems more consistent than
juju set-model-constraints BLAH

we could continue to support 'set-model-constraints' for CLI compatibility, but gain consistency with other model-level configuration.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.