Allow constraints to be set for only the bootstrap node

[Liam Young]

In MaaS the currently accepted method for placing the bootstrap node seems to be to use --constraints ie

juju bootstrap --constraints "tags=bootstrap"

However the constraints being specified there are constraints for the whole environment and will apply to subsequent services deployed into that juju env (unless they specify their own constraints ? ) which means only servers tagged as bootstrap will be used for here on in.

I think the option for specifying environment constraints should be explicitly named and the scope of the 'constraints' option should be just the boostrap node. Something like:

juju bootstrap --env-constraints "tags=my_new_env" --constraints "tags=bootstrap"

[Nate Finch (natefinch)]

You can always use juju set-constraints to change the environment-wide constraints to something else....

However, I do agree that defaulting the environment's constraints to what you specified for the bootstrap node is not intuitive to me. I'd prefer that we require an explicit set-constraints call, rather than implicitly using the same constraints from bootstrap, especially given that there's currently no way to specify constraints that are just for bootstrap and don't change the environment defaults.

[Dave Cheney (dave-cheney)]

removing ppc64el tag, this isn't critical for ppc

[Liam Young (gnuoy)]

I honestly think that --constraint when passed to the bootstrap env confuses everyone who uses it for the first time.

[Anastasia (anastasia-macmood)]

As part of other work, we have added --bootstrap-constraints for the initial machine. These are separate from --constraints.

Please confirm that it suits your purpose.