<div dir="ltr">Hi, although I'm not participating in this story since very beginning, let me add my 2 cents.<div>For scalability purposes Nova considers rather use of 'cells' rather than 'regions' construct.</div><div>Regions as name suggests deals with geographically dispersed data centre locations.</div><div>In regards to Fuel architecture, since Fuel supports only one PXE network, it is IMO unable to deploy multi region clouds.</div><div>Fuel uses 'environments' construct, but again it doesn't fit to 'region' nor 'cell', since Fuel's 'environment' deploys just another cluster (with own set of controllers, computes etc.) over the shared PXE network.</div><div>It is probably quite affordable to add 'cells' capability to Fuel, maybe through Fuel-plugins mechanism, which could decouple nova-scheduler and related roles from 'main' controller role.</div><div>For true multi-region capability, it would be required to operate multi-cobbler Fuel instances / multiple PXE networks with appropriate 'region' names provided.</div><div>A initial approach to it would be probably to deploy multiple Fuel instances (one Fuel per region) and then bound them altogether through RESTful API / operate at scale through API, at least when it comes to Keystone and Galera cluster configuration.</div><div>There are several approaches to multi region, maybe good one would be plugin allowing to select remote data centre Galera cluster as a partner for replication.</div><div>I'm not sure at this moment how HA would be operated this way, since Keystone utilizes memcached for various operations. Would multi-region memcached memory states also be synchronized? </div><div>So multi-region DC could rise up a lot related to it problems.</div><div><br></div><div>Regards,</div><div><br></div><div>A.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 7, 2015 at 11:49 AM, Roman Sokolkov <span dir="ltr"><<a href="mailto:rsokolkov@mirantis.com" target="_blank">rsokolkov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sheena, thanks. I agree with Chris full Multi-DC it's different scale task.<div><br></div><div>For now Services just need +1 tiny step from Fuel/Product in favor supporting current Multi-DC deployments architectures. (i.e. shared Keystone)<div><br></div><div>Andrew, Ruslan, Mike,</div><div><br></div><div>i've created tiny blueprint <a href="https://blueprints.launchpad.net/fuel/+spec/expose-region-name-to-ui" target="_blank">https://blueprints.launchpad.net/fuel/+spec/expose-region-name-to-ui</a> </div><div><br></div><div>We just need to expose already existing functionality to UI.</div><div><br></div><div>Can someone pickup this blueprint? And/Or reassign to appropriate team.</div><div><br></div><div>Thanks</div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Oct 2, 2015 at 7:41 PM, Sheena Gregson <span dir="ltr"><<a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Forwarding since Chris isn’t subscribed.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Chris Clason [mailto:<a href="mailto:cclason@mirantis.com" target="_blank">cclason@mirantis.com</a>] <br><b>Sent:</b> Friday, October 02, 2015 6:30 PM<br><b>To:</b> Sheena Gregson <<a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a>>; OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br><b>Subject:</b> Re: [openstack-dev] [Fuel] 8.0 Region name support / Multi-DC</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">We are doing some technology evaluations with the intent of publishing reference architectures at various scale points (500, 1500, 2000 etc). Part of this work will be to determine how to best partition the nodes in to regions based on scale limits of OpenStack components and workload characteristics. The work we are doing increased in scope significantly, so the first RA will be coming at the end of Q1 or early Q2.</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">We do plan on using some components of Fuel for our testing but the main purpose is path finding. The work we do will eventually make it into Fuel, but we are going to run in front of it a bit. </p></div></div><div><div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">On Fri, Oct 2, 2015 at 9:19 AM Sheena Gregson <<a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a>> wrote:</p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><div><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Plans for multi-DC: my understanding is that we are working on developing a whitepaper in Q4 that will provide a possible OpenStack multi-DC configuration, but I do not know whether or not we intend to include Fuel in the scope of this work (my guess would be no). Chris – I copied you in case you wanted to comment here.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Regarding specifying region names in UI, is it possible to specify region names in API? And (apologies for my ignorance on this one) what is the relative equivalence to environments in Fuel (e.g. 1 environment : many regions, 1 environment == 1 region)?</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Roman Sokolkov [mailto:<a href="mailto:rsokolkov@mirantis.com" target="_blank">rsokolkov@mirantis.com</a>] <br><b>Sent:</b> Friday, October 02, 2015 5:26 PM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br><b>Subject:</b> [openstack-dev] [Fuel] 8.0 Region name support / Multi-DC</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Folks,</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">i've dug around 8.0 roadmap and didn't find anythind regarding Multi-DC support.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">My ask is about tiny(but useful) feature: give user ability to <b>specify Region name in UI.</b></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Region name is already in every puppet module, so we just need to add this to UI.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Do we have smth already?</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">More general question: What are our plans in regards Multi-DC?</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Thanks</p></div><div><div><p class="MsoNormal"> </p></div><p class="MsoNormal">-- </p><div><div><div><div><div><div><p class="MsoNormal">Roman Sokolkov,</p><div><p class="MsoNormal">Deployment Engineer,</p></div><div><p class="MsoNormal">Mirantis, Inc.<br>Skype rsokolkov,<br><a href="mailto:rsokolkov@mirantis.com" target="_blank">rsokolkov@mirantis.com</a></p></div></div></div></div></div></div></div></div></div></div></div></blockquote></div></div></div><div><p class="MsoNormal">-- </p></div><div><p class="MsoNormal">Chris Clason</p><div><p class="MsoNormal">Director of Architecture</p></div><div><p class="MsoNormal"><a href="mailto:cclason@mirantis.com" target="_blank">cclason@mirantis.com</a></p></div><div><p class="MsoNormal">Mobile: <a href="tel:%2B1.408.409.0295" value="+14084090295" target="_blank">+1.408.409.0295</a></p></div></div></div></div>
<br></div></div>__________________________________________________________________________<span class=""><br>
OpenStack Development Mailing List (not for usage questions)<br></span>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><span class=""><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Roman Sokolkov,<div>Deployment Engineer,</div><div>Mirantis, Inc.<br>Skype rsokolkov,<br><a href="mailto:rsokolkov@mirantis.com" target="_blank">rsokolkov@mirantis.com</a></div></div></div></div></div></div></div>
</span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div style="color:rgb(136,136,136);font-size:12.8000001907349px">Adam Heczko</div><div style="color:rgb(136,136,136);font-size:12.8000001907349px">Security Engineer @ Mirantis Inc.</div></div></div>
</div>