Yes, this will work. I like the idea of being able to add constraints
dynamically so you don't have to change the YAML.
However, one thing to think about, as John said this way of using is
like deploying everything to on Availability Zone on AWS, it would
generally be a bad idea. The expected str
For now i found a way to work around this. I group machines now by tags.
Then use constraints to deploy the charms to those groups.
This works quite well. It would be nice if charm bundles would support
constraints without changing the .yaml file which i have to do now.. but
it works.
so in th
Zones are generally meant to be used to provide fault domains such that you
should be spreading your applications across zones. I can see how zones
could be used differently but it does feel like it would be going against
the grain.
John
=:->
On Mar 15, 2017 13:01, "Menno Smits" wrote:
Hi Chris
Hi Christian,
Someone who knows more about Juju's MAAS support may disagree with me but I
just had a quick look through the code I don't see any way to specify the
MAAS zone as part of a MAAS cloud definition.
- Menno
On 14 March 2017 at 13:26, wrote:
> Hi
>
> Is it possible to add-cloud a maa
Hi
Is it possible to add-cloud a maas cloud to a specific zone?
like
juju bootstrap --to zone=foozone
juju enable-ha --to zone=foozone
juju deploy --to zone=foozone
I'm using 2.1.1 devel version.
BR
Christian
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
http
