<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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>This is a case for a cross project cloud (institutional?). It costs more to run two little clouds then one bigger one. Both in terms of man power, and in cases like these. under utilized resources.<br>
<br>
#3 is interesting though. If there is to be an openstack app catalog, it would be inportant to be able to pull the needed images from outside the cloud easily.<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> Adam Young<br>
<b>Sent:</b> Wednesday, April 22, 2015 6:32:17 AM<br>
<b>To:</b> openstack-operators@lists.openstack.org<br>
<b>Subject:</b> [Openstack-operators] Sharing resources across OpenStack instances<br>
</font><br>
<div></div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Its been my understanding that many people are deploying small OpenStack
<br>
instances as a way to share the Hardware owned by their particular team, <br>
group, or department. The Keystone instance represents ownership, and <br>
the identity of the users comes from a corporate LDAP server.<br>
<br>
Is there much demand for the following scenarios?<br>
<br>
1. A project team crosses organizational boundaries and has to work <br>
with VMs in two separate OpenStack instances. They need to set up a <br>
network that requires talking to two neutron instances.<br>
<br>
2. One group manages a powerful storage array. Several OpenStack <br>
instances need to be able to mount volumes from this array. Sometimes, <br>
those volumes have to be transferred from VMs running in one instance to <br>
another.<br>
<br>
3. A group is producing nightly builds. Part of this is an image <br>
building system that posts to glance. Ideally, multiple OpenStack <br>
instances would be able to pull their images from the same glance.<br>
<br>
4. Hadoop ( or some other orchestrated task) requires more resources <br>
than are in any single OpenStack instance, and needs to allocate <br>
resources across two or more instances for a single job.<br>
<br>
<br>
I suspect that these kinds of architectures are becoming more common. <br>
Can some of the operators validate these assumptions? Are there other, <br>
more common cases where Operations need to span multiple clouds which <br>
would require integration of one Nova server with multiple Cinder, <br>
Glance, or Neutron servers managed in other OpenStack instances?<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>
</div>
</span></font>
</body>
</html>