Re: AZs and placement

[Martin Packman]

On 16/12/2016, Brent Clements  wrote:
> This is great info.
>
> I apologize for my ignorance but what would that, as placement for each
> unit, look like in a bundle?

For each application, it can look something like this:

  an-application:
charm: ./a-charm
num_units: 3
to:
  - zone=zone-a
  - zone=zone-a
  - zone=zone-a

Martin

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

AZs and placement

[Martin Packman]

There have been a couple of reports of Juju struggling with
availability zones recently. This isn't new code, it was introduced in
1.20, but with 2.0 it appears that we're not surfacing errors from
improper zone selection[1], which is a particular issue when we also
seem to not be selecting a valid zone[2]. This is seen with both
Openstack (datacenterd) and vSphere.

We don't have a global option to say only use a particular AZ, so the
only way at present to do this right is specify a zone placement for
every unit. I did find how to do that spelled out in the
documentation, though it's not completely intuitive:



$ juju deploy an-application -n 3 --to zone=$ZONE,zone=$ZONE,zone=$ZONE

Note that a placement directive is needed per unit.

Also, of note, we have only just fixed a bug[3] that prevented
combining constraints and placement directives in bundles. So,
currently care is required if creating a bundle that needs to specify
a zone for everything.

Martin


[1] "Openstack provider error not surfaced on bootstrap"

[2] "inconsistent results when fetching availability zones while
bootstrapping with vsphere as provider"

[3] "Juju ignores constraints set in the bundle and deploys KVMs with
default values"


-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev