Specific machine placement by hostname in bundle
Bug #1882025 reported by
Vern Hart
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
From the command line we can specify:
juju deploy graylog --to graylog-1.maas
But there isn't an equivalent for bundles.
We commonly tag individual machines with their name and use those tags as a constraint in the machines section and use the machine id in an application's "to:" directive:
machines:
"0":
applications:
graylog:
charm: cs:graylog
to:
- "0"
It could potentially simplify and make things a bit clearer if we could specify the machine name directly in the to directive:
applications:
graylog:
charm: cs:graylog
to:
- "graylog-1.maas"
Is this technically feasible?
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
Changed in juju: | |
milestone: | 2.9.1 → 2.9.2 |
Changed in juju: | |
milestone: | 2.9.2 → 2.9.3 |
Changed in juju: | |
milestone: | 2.9.3 → 2.9.4 |
Changed in juju: | |
milestone: | 2.9.4 → 2.9.5 |
Changed in juju: | |
milestone: | 2.9.5 → 2.9.6 |
Changed in juju: | |
milestone: | 2.9.6 → 2.9.7 |
Changed in juju: | |
milestone: | 2.9.7 → 2.9.8 |
Changed in juju: | |
milestone: | 2.9.8 → 2.9.9 |
Changed in juju: | |
milestone: | 2.9.9 → 2.9.10 |
Changed in juju: | |
milestone: | 2.9.10 → 2.9.11 |
Changed in juju: | |
milestone: | 2.9.11 → 2.9.12 |
Changed in juju: | |
milestone: | 2.9.12 → 2.9.13 |
Changed in juju: | |
milestone: | 2.9.13 → 2.9.14 |
Changed in juju: | |
milestone: | 2.9.14 → 2.9.15 |
Changed in juju: | |
milestone: | 2.9.15 → 2.9.16 |
Changed in juju: | |
milestone: | 2.9.16 → 2.9.17 |
Changed in juju: | |
milestone: | 2.9.17 → 2.9.18 |
Changed in juju: | |
milestone: | 2.9.18 → 2.9.19 |
Changed in juju: | |
milestone: | 2.9.19 → 2.9.20 |
Changed in juju: | |
milestone: | 2.9.20 → 2.9.21 |
Changed in juju: | |
milestone: | 2.9.21 → 2.9.22 |
Changed in juju: | |
milestone: | 2.9.22 → 2.9.23 |
Changed in juju: | |
milestone: | 2.9.23 → 2.9.24 |
Changed in juju: | |
milestone: | 2.9.24 → 2.9.25 |
Changed in juju: | |
milestone: | 2.9.25 → 2.9.26 |
Changed in juju: | |
milestone: | 2.9.26 → 2.9.27 |
Changed in juju: | |
milestone: | 2.9.27 → 2.9.28 |
Changed in juju: | |
milestone: | 2.9.28 → 2.9.29 |
Changed in juju: | |
milestone: | 2.9.29 → none |
tags: | added: bundles |
To post a comment you must log in.
It is feasible but some work is needed since in bundles, the "to" is interpreted as follows:
(<containertype >:)?(<unit> |<machine> |new)
So we'd need to figure out a syntax to use to support the new semantics.