<div dir="ltr">Thank you Joe! It is precisely what I was looking for...<div><br></div><div>Cheers!</div><div>Thiago</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 21 October 2013 13:25, Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</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">For reference, here's a detailed description of the possible ways to segregate OpenStack Compute:<div>
<br></div><div><a href="http://docs.openstack.org/trunk/openstack-ops/content/scaling.html#segregate_cloud" target="_blank">http://docs.openstack.org/trunk/openstack-ops/content/scaling.html#segregate_cloud</a><br>
</div><div><br></div><div>My initial thought is to base your decision on how you want your segregated cloud to appear. For example: do you want each segregated area to have its own quota? If so, look into Cells or Regions. If not, then look into AZs or Host Aggregates. </div>
<div><br></div><div>As another example, with Regions, users will have to explicitly log in to a different region through the Dashboard. The different regions will not appear as one large Compute service. I'm not sure how Cells work in this regard. AZs and HAs appear under the same Dashboard session.</div>
<div><br></div><div>I'm not familiar enough with Neutron to know how a certain choice will affect the network service. I do know that separate Compute environments can share the same Identity and Image services, though.</div>
<div><br></div><div>I hope that helps,</div><div>Joe</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Sun, Oct 20, 2013 at 9:39 PM, Martinx - $B%8%'!<%`%:(B <span dir="ltr"><<a href="mailto:thiagocmartinsc@gmail.com" target="_blank">thiagocmartinsc@gmail.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 dir="ltr">Guys,<div><br></div><div>I would like to achieve the following configuration:</div>
<div><br></div><div><br>
</div><div>1- OpenStack Havana Cloud</div><div><br></div><div>1.1- AZ or Region - #1: KVM Compute Nodes</div>
<div><br></div><div>1.2- AZ or Region - #2: Docker Compute Nodes</div><div><br></div><div>If possible:</div><div><br></div><div>1.3- AZ or Region - #1.1: KVM Compute Nodes with VNC - For Servers</div><div><br>1.4- AZ or Region - #1.2: KVM Compute Nodes with SPICE - For Desktops<br>
</div><div><br></div><div>1.5 AZ or Region - #1.2.1: KVM Compute Nodes with IOMMU + GPU Passthrough + SPICE - For Render Farms</div><div><br></div><div><br></div><div>The topology I'm using in production today is "Per-Tenant router with Private Networs".</div>
<div><br></div><div>I already have my Havana up and running and I would like to add a new "environment" (Region or AZ?) powered by Docker, side by side with my regular KVM Compute Nodes, if possible.</div><div>
<br>
</div><div>I'm not using Chef or Puppet, just fresh Ubuntu 12.04.3 with Havana from Cloud Archive all installed by hand.</div><div><br></div><div><div>I would like to know the "best practices" to achieve a goal like this.</div>
</div><div><br></div><div>Thanks!</div><div>Thiago</div></div>
<br></div></div>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Joe Topjian<div>Systems Architect</div><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div>
<div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div>
</font></span></div>
</blockquote></div><br></div>