juju 2.0 bundle support: Missing constraint support for maas names to support bundle placement

[Larry Michel]

In bug 1170337, this was initially requested but it was fixed with tag support only.

With bundle support being added in 2.0, we are trying to deploy our bundle and need to be able to do it using the maas names as constraints rather than the maas tags.

Requesting that support for maas names be added to Juju 2.0 bundle support.

[Gui Bot (rick-harding+guibot)]

I think the provider specific ones being a problem still stands. I think we can mitigate that though by adding support in Juju to understand it, but that we don't use these in the charmstore where folks share/collaborate on bundles as having these specific names causes problems in the reusability of the bundle. It's a bit like a charm that only works on one provider. It's useful, but very much against the Juju ethos. Unfortunately I don't think we'll be able to get this into 2.0 ahead of the other work in flight.

[Jason Hobbs (jason-hobbs)]

For some background on why we want to be able to target specific machines, we do machine wear leveling in OIL. We try to use all of the machines equally, and that requires us to be able to target specific machines for deployment.

We do have a work around with tags matching the machine name.

[Ryan Beisner (1chb1n)]

+1 There are real-world use cases for being able to deploy --to a specific MAAS machine name/ID.

Currently, the only way to achieve that is to tag a MAAS machine with a unique value, such as the hostname.

Any time a use case requires a user to set the same value to two different properties on the same object, I'd consider that a bug. This use case fits that.

[Mike McCracken (mikemc)]

This impacts conjure-up as well, because for MAAS we provide a UI that lets you pin a specific maas machine onto a juju machine defined in a bundle. The workaround using tags means that conjure-up automatically creates a tag on each used machine that has redundant information - we just use the maas machine ID as a tag so we can reference it in a constraint.

This makes the tags UI in MAAS much less useful, since there are now N otherwise useless tags.

[Ryan Beisner (1chb1n)]

With Juju 2, one can bootstrap --to a particular MAAS node, but cannot deploy --to a particular MAAS node. That seems odd.

[John A Meinel (jameinel)]

you can certainly 'juju add-machine maas-name' and then 'juju deploy --to X', I'm not sure that 'juju deploy --to maas-name' was missed.

[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.