Cannot target zone constraints in juju deploy bundle with MAAS provider
Bug #1786967 reported by
Drew Freiberger
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
As I understand it, juju deploy ubuntu --to zone=zone1 works with MAAS provider, but in a bundle, can it be targetted with a constraint?
machines:
0:
constraints: 'zone=zone1,
When trying this, I received unknown constraint "zone"
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| affects: | juju-core → juju |
| Changed in juju: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
juju-core relates to juju 1.X.
I'm guessing you mean to target 2.x.
Zone is not allowed as a constraint (--constraints), it is allowed as a placement directive (--to). The difference is that the former is applied to all units of an application (so juju add-unit X would also target exactly that zone), while --to applies only to the next unit that is being added.
Zone is not currently allowed as a constraint because it conflicts with the idea of availability. (If zones are defined as availability
zones as they are in most places, then zone on an application prevents you from actually giving good availability when you have more than one unit.)
I don't know if you could put a "zone" into the "to:" section of an application, but it doesn't fit under constraints.