[openstack-dev] Kolla multinode , multi-region deployment support

Michal Rostecki michal.rostecki at gmail.com
Wed Apr 20 12:46:09 UTC 2016

On Wed, 2016-04-20 at 06:57 +0000, Steven Dake (stdake) wrote:
> Grzegorz,
> This is a technical question about our roadmap and should be sent to
> the openstack-dev mailing list.  As such, ccing openstack-dev so
> everyone can benefit from my thinking on this matter and others can
> weigh in.
> From: Grzegorz Koper <grzegorz.koper at pl.ibm.com<mailto:grzegorz.koper
> @pl.ibm.com>>
> Date: Monday, April 18, 2016 at 12:41 AM
> To: Steven Dake <stdake at cisco.com<mailto:stdake at cisco.com>>
> Cc: Michal Nasiadka <michal.nasiadka at pl.ibm.com<mailto:michal.nasiadk
> a at pl.ibm.com>>
> Subject: Kolla multinode , multi-region deployment support
> Hello,
> First of all, thanks for all the work on Kolla project.
> We are currently testing both Kolla Liberty and Mitaka branch ( yes i
> know about the Liberty issues, and upcoming patch ).
> We would love to deploy multinode, multi-region topology but failing
> to find any documentation at the topic.
> Found this https://blueprints.launchpad.net/kolla/+spec/multi-kolla-c
> onfig but it looks forgotten ;]
> Do You have any ideas or plans to implement such a setup in Kolla ?
> Maybe some tips and tricks if we would like to start on this ourselfs
> ?
> Thanks in advance
> I'm sure the team thanks for for the kudos on the impelmentation of
> Kolla!
> Nobody has brought up multi-Azs on the mailing list, in irc, or in
> our weekly irc meeting.  Your correct that blueprint hasn't seen much
> discussion, even though its in the "discussion" phase.
> Not really understanding how Azs are setup, I think it would be a
> fantastic feature and would be pleased to support the development of
> such work.  I don't have any real pointers on where to begin, other
> then we have what I feel is a pretty full plate for Newton already
> and the core team will be stretched thin implementing this with our
> current community of developers.  We do welcome new contributors and
> can help you get your initial deployment setup so you can begin work
> if you desire.  Anyone on the core reviewer team can approve a
> blueprint once an assignee has been determined to lead the
> effort.  All you have to do is ask :)
> Join us on #openstack-kolla to discuss the work, or drop into our
> design sessions on Wednesday/Thursday of summit where we discuss our
> roadmap.
> Regards,
> -steve

I'd like to add that we have to keep in mind also this blueprint: https

So, we have to handle both configs per cloud and configs per cloud

My proposition here is to have the following config trees:

/etc/kolla - default config path
/etc/kolla/<cloud_name>/<region> - where default region is "region_one"

And then add an option "multiregion" or "multicloud" in config to tell
kolla whether it should look at the first path or at the second one.
Then of course support pointing kolla-ansible to the concrete cloud we
want to deploy or upgrade.

I woudn't like to have a separate path for <region> without
<cloud_name> - I think that supporting only one cloud with many regions
is unnecessary. IMO we shoud be focused only for scenarios for AIO
(first path) and multicloud-multiregion.

However, Steven, I don't know what availability zones have to do with
the multiregion blueprint. AZ is something existing in the single cloud
when you associate hosts, isn't it? And AZ is something which we are
able to use currently in kolla (in contrast to regions or multiple

More information about the OpenStack-dev mailing list