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 the machine section of a bundle i set the constraint to a tag.
machines:
'0':
series: xenial
contraints: tags=test
'1':
series: xenial
contraints: tags=test
'2':
series: xenial
contraints: tags=test
'3':
series: xenial
contraints: tags=test
BR
Christian
Am 2017-03-15 10:44, schrieb John Meinel:
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" <[email protected]>
wrote:
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, <[email protected]>
wrote:
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
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju [1]
--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju [1]
Links:
------
[1] https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
