<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>We have 2 public networks, one for the internet and one public nonroutable one. Then we use per tenant private networks and two routers per tenant. One on each net. Then default the internet one and the internet router config provides an extra route to
the nonroutable net router. Has worked well in production for 6 months with icehouse.<br>
<br>
Thanks,<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Emrah Aslan<br>
<b>Sent:</b> Monday, November 03, 2014 1:44:34 AM<br>
<b>To:</b> Michaël Van de Borne; openstack-operators<br>
<b>Subject:</b> Re: [Openstack-operators] Networking architecture question: communication between tenants<br>
</font><br>
<div></div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi all,<br>
<br>
I've checked but couldn’t find an exact solution - somehow can not troubleshoot caused by lack of 3rd party troubleshooting sw. Cloud-wide Galera cluster has lots of bugs for sure.<br>
<br>
Has anyone tried the AWS amazon tier2 services. We are having exactly the same problem within the AWS cloud services.
<br>
<br>
Kind Regards<br>
<br>
Emrah ASLAN<br>
Cisco/Citrix System Engineer<br>
<br>
<br>
<br>
www.logicom.com.tr<br>
Noramin İş Merkezi | No: 237 /114 | 34398 Maslak ,İstanbul ,TR<br>
<br>
T: +90 212 2762720 | D: +90 850 2215821 | M: +90 533 2853803 | F: +90 212 2762750<br>
<br>
<br>
<br>
Değerli İş Ortaklarımız,<br>
Logicom kampanyaları , fırsat, duyuru ve stok bilgilerinin sizlere düzenli ulaşması için aşağıdaki linki tıklayarak e-mail adresinizi güncellemenizi rica ediyoruz.<br>
<a href="http://visitor.r20.constantcontact.com/manage/optin?v=001t9egDEMH10MEulnTu-Lzln0RXbiYIgR2HnLd_hpHmPb0K44ZxJOya0FvCOF3TI8c2qeErt1Xrn3PlZqntTSqiSTW40PTK2XQ8OlOUe4qYOE%3D">http://visitor.r20.constantcontact.com/manage/optin?v=001t9egDEMH10MEulnTu-Lzln0RXbiYIgR2HnLd_hpHmPb0K44ZxJOya0FvCOF3TI8c2qeErt1Xrn3PlZqntTSqiSTW40PTK2XQ8OlOUe4qYOE%3D</a><br>
<br>
-----Original Message-----<br>
From: Michaël Van de Borne [<a href="mailto:michael.vandeborne@cetic.be">mailto:michael.vandeborne@cetic.be</a>]
<br>
Sent: Monday, November 03, 2014 11:25 AM<br>
To: openstack-operators<br>
Subject: [Openstack-operators] Networking architecture question: communication between tenants<br>
<br>
Hello,<br>
<br>
I'm building a private cloud in which I'd like Application Server instances from separate tenants to access the same unique cloud-wide Galera cluster (which would have its own tenant).<br>
<br>
I'm wondering what the best network topology would be to achieve this. <br>
The constraint is that tenant A Application Server instances should not see Tenant B App Servers.<br>
- should I go with a per-tenant router topology? and assign 2 NICs to App Server instances: first one in their tenant network, second one in Galera cluster tenant? is that possible?<br>
- should I go with one router for all tenants?<br>
- should the Galera cluster only be accessed from its floating IPs in order to avoid all communication between tenants?<br>
<br>
Am I missing something?<br>
<br>
Your architectural thoughts are welcome.<br>
<br>
thank you,<br>
<br>
cheers,<br>
<br>
michaël<br>
<br>
--<br>
Michaël Van de Borne<br>
R&D Engineer, SOA team, CETIC<br>
Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype: mikemowgli <a href="http://www.cetic.be">
www.cetic.be</a>, rue des Frères Wright, 29/3, B-6041 Charleroi<br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
OpenStack-operators@lists.openstack.org<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
OpenStack-operators@lists.openstack.org<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div>
</span></font>
</body>
</html>