<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div id=":16f" class="ii gt adP adO">
<div id=":16e">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi,<br>
</div>
<br>
Following the proposal for VM ensembles, we drafted
the blueprint <a
href="https://blueprints.launchpad.net/nova/+spec/vm-ensembles"
target="_blank">https://blueprints.launchpad.<wbr>net/nova/+spec/vm-ensembles</a>.
At the moment this is pending approval. How do we go
about getting the approval?<br>
<br>
</div>
The blueprint enables OpenStack to deploy mission
critical applications that are highly available. The
proposed functionality cannot be achieved by making use
of the existing scheduler hints.<br>
</div>
<br>
The work plan is as follows:<br>
- <b>Stage 0</b>: refactor instance validation code
(approved)<br>
- <b>Stage 1</b>: at the moment run_instance passes
the VM details to the scheduler. the idea here was to pass
an array of details. this will leave us with the same API
and just change the parameters passed. the scheduler will
treat the input accordingly - if there is one entry then
proceed with the existing flow. if there are more then it
will invoke the group scheduling (this is the current
patch set). <br>
-<b> Stage 2</b>: implement the group scheduling
(currently writing unit tests for this)<br>
- <b>Stage 3</b>: implement and extension that
enables a user to pass a group to nova<br>
<br>
Please note that there will be no database changes. In
stage 3 we will make use of the meta data to store the VM
groups. This will help with debugging and moving forward.<br>
<br>
Thanks<br>
Gary<br>
</div>
</div>
</div>
</div>
</div>
<br>
</body>
</html>