Ricardo,
The blueprint is approved, thanks!
Adrian
> On Feb 24, 2016, at 2:53 PM, Ricardo Rocha wrote:
>
> Thanks, done.
>
> https://blueprints.launchpad.net/magnum/+spec/magnum-availability-zones
>
> We might have something already to expose the labels in the docker
Thanks, done.
https://blueprints.launchpad.net/magnum/+spec/magnum-availability-zones
We might have something already to expose the labels in the docker
daemon config.
On Wed, Feb 24, 2016 at 6:01 PM, Vilobh Meshram
wrote:
> +1 from me too for the idea.
+1 from me too for the idea. Please file a blueprint. Seems feasible and
useful.
-Vilobh
On Tue, Feb 23, 2016 at 7:25 PM, Adrian Otto
wrote:
> Ricardo,
>
> Yes, that approach would work. I don’t see any harm in automatically
> adding tags to the docker daemon on the
Ricardo,
Yes, that approach would work. I don’t see any harm in automatically adding
tags to the docker daemon on the bay nodes as part of the swarm heat template.
That would allow the filter selection you described.
Adrian
> On Feb 23, 2016, at 4:11 PM, Ricardo Rocha
Hi Ricardo,
+1 from me. I like this feature.
Best regards,
Hongbin
-Original Message-
From: Ricardo Rocha [mailto:rocha.po...@gmail.com]
Sent: February-23-16 5:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] containers across
Hi.
Has anyone looked into having magnum bay nodes deployed in different
availability zones? The goal would be to have multiple instances of a
container running on nodes across multiple AZs.
Looking at docker swarm this could be achieved using (for example)
affinity filters based on labels.