<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black">Hi Nguy,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black">We’ve deployed a large multi-region openstack deployment.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black">As a rule of thumb we’ve got a “keystone” region which is as best we can highly available and very redundant.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black">We then have all other regions talk back to this region, we just usually call it “keystone” or “core” and it’s hidden from the UI from users.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black">We then just run a large well kept Galara cluster to support it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:-webkit-standard;color:black">--Karl.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">openstack-discuss-request@lists.openstack.org <openstack-discuss-request@lists.openstack.org><br>
<b>Date: </b>Tuesday, 18 July 2023 at 9:25 pm<br>
<b>To: </b>openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org><br>
<b>Subject: </b>openstack-discuss Digest, Vol 57, Issue 55<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Send openstack-discuss mailing list submissions to<br>
openstack-discuss@lists.openstack.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss">
https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
openstack-discuss-request@lists.openstack.org<br>
<br>
You can reach the person managing the list at<br>
openstack-discuss-owner@lists.openstack.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of openstack-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [openstack][largescale-sig] Openstack multi region deployment<br>
(Nguy?n H?u Kh?i)<br>
2. Re: [openstack][largescale-sig] Openstack multi region<br>
deployment (Felix Huettner)<br>
3. Re: [openstack][largescale-sig] Openstack multi region<br>
deployment (Nguy?n H?u Kh?i)<br>
4. Re: [neutron] unmanaged router resources - OVN interconnect<br>
(Rodolfo Alonso Hernandez)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 18 Jul 2023 12:07:12 +0700<br>
From: Nguy?n H?u Kh?i <nguyenhuukhoinw@gmail.com><br>
To: OpenStack Discuss <openstack-discuss@lists.openstack.org><br>
Subject: [openstack][largescale-sig] Openstack multi region deployment<br>
Message-ID:<br>
<CABAODReJ6QW8A4OENEjmhFCiM-15B0qc2La_aMr1EKfaENq9iw@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello guys,<br>
<br>
I am going to deploy openstack multi regions and I know that keystone<br>
replication is the most challenging.<br>
<br>
I plan to set up 2 regions which use centralize galera cluster(3 nodes).<br>
and one standby edge galera cluster(3 nodes)<br>
<br>
When region 1 is node available, I will map region 2 to use standby edge<br>
galera cluster.<br>
<br>
I hope you give me some experience and advice with multi regions.<br>
<br>
Thank you very much.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230718/c95d3675/attachment-0001.htm">https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230718/c95d3675/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 18 Jul 2023 09:34:35 +0200<br>
From: Felix Huettner <felix.huettner@mail.schwarz><br>
To: Nguy?n H?u Kh?i <nguyenhuukhoinw@gmail.com><br>
Cc: OpenStack Discuss <openstack-discuss@lists.openstack.org><br>
Subject: Re: [openstack][largescale-sig] Openstack multi region<br>
deployment<br>
Message-ID: <ZLZAS-99RzzXfyr8@SIT-SLAP8639.int.lidl.net><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Hi,<br>
<br>
i think you have two options here:<br>
1. you could span a single galera cluster over all of your regions.<br>
this might have some latency issues, but if your are not too write<br>
heavy that might be fine. I know some companies use that setup.<br>
2. you use some kind of multiple galera clusters with replication.<br>
But i have not yet heard of anybody using this setup.<br>
<br>
An alternative might be to have separate keystone setups with separate<br>
databases. This would probably reduce the error potential, but might not<br>
fit your usecase.<br>
<br>
Thanks<br>
Felix<br>
<br>
<br>
On Tue, Jul 18, 2023 at 12:07:12PM +0700, Nguy?n H?u Kh?i wrote:<br>
> Hello guys,<br>
><br>
> I am going to deploy openstack multi regions and I know that keystone<br>
> replication is the most challenging.<br>
><br>
> I plan to set up 2 regions which use centralize galera cluster(3 nodes).<br>
> and one standby edge galera cluster(3 nodes)<br>
><br>
> When region 1 is node available, I will map region 2 to use standby edge<br>
> galera cluster.<br>
><br>
> I hope you give me some experience and advice with multi regions.<br>
><br>
> Thank you very much.<br>
Diese E Mail enth?lt m?glicherweise vertrauliche Inhalte und ist nur f?r die Verwertung durch den vorgesehenen Empf?nger bestimmt.<br>
Sollten Sie nicht der vorgesehene Empf?nger sein, setzen Sie den Absender bitte unverz?glich in Kenntnis und l?schen diese E Mail.<br>
<br>
Hinweise zum Datenschutz finden Sie hier<<a href="https://www.datenschutz.schwarz">https://www.datenschutz.schwarz</a>>.<br>
<br>
<br>
This e-mail may contain confidential content and is intended only for the specified recipient/s.<br>
If you are not the intended recipient, please inform the sender immediately and delete this e-mail.<br>
<br>
Information on data protection can be found here<<a href="https://www.datenschutz.schwarz">https://www.datenschutz.schwarz</a>>.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 18 Jul 2023 15:36:11 +0700<br>
From: Nguy?n H?u Kh?i <nguyenhuukhoinw@gmail.com><br>
To: Nguy?n H?u Kh?i <nguyenhuukhoinw@gmail.com>, OpenStack Discuss<br>
<openstack-discuss@lists.openstack.org><br>
Subject: Re: [openstack][largescale-sig] Openstack multi region<br>
deployment<br>
Message-ID:<br>
<CABAODRcJr=CGBW1_bRkLQJAxLZxAx8V4qvbdBmTUQBUm2SRsow@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi.<br>
Thank you for your reply.<br>
<br>
The first one has a problem because each region is too soft. If a member is<br>
down, so this region is gone.<br>
<br>
It is so challenge with us.<br>
<br>
<br>
Nguyen Huu Khoi<br>
<br>
<br>
On Tue, Jul 18, 2023 at 2:34?PM Felix Huettner <felix.huettner@mail.schwarz><br>
wrote:<br>
<br>
> Hi,<br>
><br>
> i think you have two options here:<br>
> 1. you could span a single galera cluster over all of your regions.<br>
> this might have some latency issues, but if your are not too write<br>
> heavy that might be fine. I know some companies use that setup.<br>
> 2. you use some kind of multiple galera clusters with replication.<br>
> But i have not yet heard of anybody using this setup.<br>
><br>
> An alternative might be to have separate keystone setups with separate<br>
> databases. This would probably reduce the error potential, but might not<br>
> fit your usecase.<br>
><br>
> Thanks<br>
> Felix<br>
><br>
><br>
> On Tue, Jul 18, 2023 at 12:07:12PM +0700, Nguy?n H?u Kh?i wrote:<br>
> > Hello guys,<br>
> ><br>
> > I am going to deploy openstack multi regions and I know that keystone<br>
> > replication is the most challenging.<br>
> ><br>
> > I plan to set up 2 regions which use centralize galera cluster(3 nodes).<br>
> > and one standby edge galera cluster(3 nodes)<br>
> ><br>
> > When region 1 is node available, I will map region 2 to use standby edge<br>
> > galera cluster.<br>
> ><br>
> > I hope you give me some experience and advice with multi regions.<br>
> ><br>
> > Thank you very much.<br>
> Diese E Mail enth?lt m?glicherweise vertrauliche Inhalte und ist nur f?r<br>
> die Verwertung durch den vorgesehenen Empf?nger bestimmt.<br>
> Sollten Sie nicht der vorgesehene Empf?nger sein, setzen Sie den Absender<br>
> bitte unverz?glich in Kenntnis und l?schen diese E Mail.<br>
><br>
> Hinweise zum Datenschutz finden Sie hier<<a href="https://www.datenschutz.schwarz">https://www.datenschutz.schwarz</a>>.<br>
><br>
><br>
> This e-mail may contain confidential content and is intended only for the<br>
> specified recipient/s.<br>
> If you are not the intended recipient, please inform the sender<br>
> immediately and delete this e-mail.<br>
><br>
> Information on data protection can be found here<<br>
> <a href="https://www.datenschutz.schwarz%3e">https://www.datenschutz.schwarz></a>.<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230718/749440e3/attachment-0001.htm">https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230718/749440e3/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 18 Jul 2023 13:23:27 +0200<br>
From: Rodolfo Alonso Hernandez <ralonsoh@redhat.com><br>
To: Roberto Bartzen Acosta <roberto.acosta@luizalabs.com><br>
Cc: openstack-discuss <openstack-discuss@lists.openstack.org>, Terry<br>
Wilson <twilson@redhat.com>, Tiago Pires <tiago.pires@luizalabs.com><br>
Subject: Re: [neutron] unmanaged router resources - OVN interconnect<br>
Message-ID:<br>
<CAECr9X7U7YsGBv9ajcmeOCxfdD+YLar8QyPwYBN0qaP10CzTug@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Ok, this is being tortuous. First of all: define a strategy. If you are<br>
going to create the resources in Neutron, define how. I've provided a way<br>
to do this, find a formal strategy to ground it.<br>
<br>
Second: (again) try to find a connection between resources, if you are<br>
going to use the strategy of creating the resources in Neutron. The<br>
"Logical_Router_Static_Route" belongs to a router univocally. If that<br>
router has been created by OpenStack, then you can modify the DB sync<br>
method to consider learned routes too.<br>
<br>
In order to do this, you'll need a set of resources that are going to be<br>
needed in Neutron, the OVN counterparts and other resources (like<br>
"Logical_Router_Static_Route") that will be added and will be present in<br>
OVN and not in Neutron DB. Also you'll need to know how to relate all of<br>
them.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230718/90712e47/attachment.htm">https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230718/90712e47/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
openstack-discuss mailing list<br>
openstack-discuss@lists.openstack.org<br>
<br>
<br>
------------------------------<br>
<br>
End of openstack-discuss Digest, Vol 57, Issue 55<br>
*************************************************<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>