[Openstack-operators] [openstack-dev] Mirantis Fuel Multi-Region
vkuklin at mirantis.com
Tue Nov 17 12:23:00 UTC 2015
Let me comment on a couple of things. Multiregion support is possible from
deployment side. You need to pass a region parameter to corresponding nodes
It is a part of detached services feature which is delivered through
Please look into this change:
It should allow you to set Region name per-node. You will need just to
download nodes settings and add a corresponding parameter 'region' into
deployment yaml files. This will lead for controllers (or corresponding
nodes roles whether you choos to use separated controller services) to
create endpoints with corresponding region name.
Should you face any issues, please create a bug at Launchpad or contact us
within openstack-dev mailing list with [Fuel] tag in the message or
approach us at #fuel-dev IRC channel.
And another comment regarding multirack installation. In 8.0 we are
planning to enable multiple rack configuration MVP to allow users to be
able to deploy across multiple L2 segments for admin network. Please refer
to https://blueprints.launchpad.net/fuel/+spec/l3-multiple-racks .
On Tue, Nov 17, 2015 at 12:53 PM, Dina Belova <dbelova at mirantis.com> wrote:
> + openstack-dev mailing list to bring more Fuel audience.
> On Tue, Nov 17, 2015 at 12:44 PM, Federico Michele Facca <
> federico.facca at create-net.org> wrote:
>> as said, you need to do manual changes to your deployed nodes.
>> then you will have to:
>> - synch your galera cluster across the two dc
>> - configure properly the load balancers
>> - configure the memcached configuration
>> - register the services of the second region on the new shared keystone
>> PS: I think that you can change the region name in the YAML file using
>> fuel cli (
>> but that won't help much honestly, being the trivial of the steps above.
>> Future Internet is closer than you think!
>> Official Mirantis partner for OpenStack Training
>> Dr. Federico M. Facca
>> Via alla Cascata 56/D
>> 38123 Povo Trento (Italy)
>> P +39 0461 312471
>> M +39 334 6049758
>> E federico.facca at create-net.org
>> T @chicco785
>> W www.create-net.org
>> On Tue, Nov 17, 2015 at 10:29 AM, Eren Türkay <erent at skyatlas.com> wrote:
>>> On 17-11-2015 10:40, Federico Michele Facca wrote:
>>> > Hi Eren,
>>> Hello Federico
>>> > afaik, with the new plugin architecture, in fuel 7/8 it should be easy
>>> > create a plugin for achieve your goal.
>>> > in case of manual job, depending on your cloud architecture there are
>>> > options, the main ones are:
>>> > - you keep a single keystone in a datacenter and register the new
>>> > services in there.
>>> Yes, that's what I am aiming for. I need a single keystone and multiple
>>> endpoints. However, as far as I understand, multi-dc isn't supported yet
>>> Mirantis (nor the region name change). Do you know the actual/example
>>> implementation for multi-dc with new plugin architecture? Here are my
>>> regarding to the issue. It seems deploying multi-site with fuel is
>>> really hard
>>> and not supported.
>>> Eren Türkay, System Administrator
>>> https://skyatlas.com/ | +90 850 885 0357
>>> Yildiz Teknik Universitesi Davutpasa Kampusu
>>> Teknopark Bolgesi, D2 Blok No:107
>>> Esenler, Istanbul Pk.34220
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
> Best regards,
> Dina Belova
> Software Engineer
> Mirantis Inc.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Fuel Library Tech Lead,
+7 (495) 640-49-04
+7 (926) 702-39-68
35bk3, Vorontsovskaya Str.
vkuklin at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators