<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Sorry for the confusion..
<div><br>
</div>
<div>I have moved the wiki page to:</div>
<div><a href="https://wiki.openstack.org/wiki/InstanceGroupApiExtension">https://wiki.openstack.org/wiki/InstanceGroupApiExtension</a></div>
<div>and the blue print to:</div>
<div>
<blockquote type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
</blockquote>
</div>
</div>
</blockquote>
</div>
<div><a href="https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension" style="font-family: Consolas; ">https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension</a></div>
<div><br>
</div>
<div>Thanks,</div>
<div>Senhua</div>
<div><br>
</div>
<div><br>
<div>
<div>On May 8, 2013, at 3:07 PM, Matthew Sherborne <<a href="mailto:msherborne@gmail.com">msherborne@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">
<div>I think it should be renamed 'instance groups' or 'instance aggregates' to be more explicit.<br>
<br>
</div>
When I started reading I was thinking 'group of users' :)<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, May 8, 2013 at 6:30 AM, Senhua Huang (senhuang) <span dir="ltr">
<<a href="mailto:senhuang@cisco.com" target="_blank">senhuang@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style="word-wrap:break-word">The wiki page for this proposal:
<div><a href="https://wiki.openstack.org/wiki/GroupApiExtension" target="_blank">https://wiki.openstack.org/wiki/GroupApiExtension</a></div>
<div><br>
</div>
<div>It is almost a direct copy of the Google Doc. </div>
<div><br>
</div>
<div>Feel free to edit it.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Senhua</div>
<div><br>
<div>
<div>
<div class="h5">
<div>On May 7, 2013, at 10:46 AM, Senhua Huang (senhuang) <<a href="mailto:senhuang@cisco.com" target="_blank">senhuang@cisco.com</a>> wrote:</div>
<br>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div style="word-wrap:break-word">Hi all,
<div><br>
</div>
<div>At the summit a few weeks ago, we (Gary Kotton, <span style="font-size:15px;font-family:Arial;vertical-align:baseline">Gilad Zlotkin,</span> Alex Glikson, I and a few other Nova developers) were talking about group scheduling, cross-project scheduling
and so on. As a first step towards these long term goals, we have been working on an API extension to Nova that achieves the following goals:</div>
<div>
<ul>
<li>to allow tenants to create a "group", which defines the desired relationship among all the members within this group</li><li>to allow tenants to add VM instances to an existing group</li><li>to allow tenants to remove a VM instance from an existing group </li><li>to allow tenants to specify policies (e.g., anti-affinity, network-proximity, rack-aware) that apply to the group</li><li>to allow tenants to view/list/describe a particular group</li><li>to allow tenants to remove a group </li></ul>
</div>
<div><br>
</div>
<div>In essence, "group" defines the relationship among individual instances. You can think of it as the hyper edge with properties in a hyper graph in the most abstract manner. There are several benefits of introducing this additional construct:</div>
<div>
<ul>
<li>it is more intuitive to use than padding various hints to every related instance creation call (now the relationship among these instances are handled by "group"</li><li>it makes easier to add scheduling algorithms that attempt to place a set of VM instances to achieve failure resilience, redundancy, topology-wareness and so on.
</li></ul>
<div><br>
</div>
</div>
<div>Gary, Alex, and I have put together an initial design doc on the API and how to use it for group scheduling:</div>
<div><a href="https://docs.google.com/document/d/1QUThPfZh6EeOOz1Yhyvx-jFUYHQgvCw9yBAGDGc0y78/edit?usp=sharing" target="_blank">https://docs.google.com/document/d/1QUThPfZh6EeOOz1Yhyvx-jFUYHQgvCw9yBAGDGc0y78/edit?usp=sharing</a></div>
<div><br>
</div>
<div>A related blue print is also created for Nova:</div>
<div><a href="https://blueprints.launchpad.net/nova/+spec/group-api-extension" target="_blank">https://blueprints.launchpad.net/nova/+spec/group-api-extension</a></div>
<div><br>
</div>
<div>We'd appreciate your feedback on the API and blue print and in particularly whether there are interesting potential use cases that can/cannot be supported by this API extension.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Senhua </div>
</div>
</div>
</div>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>