<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 01/08/2013 09:00 PM, JC Martin wrote:
<blockquote
cite="mid:42243FE24FEE6949AD4647D68AF230E6237A94@RHV-EXRDA-S11.corp.ebay.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Gary,</div>
<div><br>
</div>
<div>This is a very interesting feature. I have a question on
where the definition of ensembles will reside. It seems from the
linked document that the definition of ensemble membership will
only reside in Heat.</div>
</blockquote>
<br>
The idea is that the definition of the Ensemble will be maintained
outside of Nova - for example by Heat or another tenant facing
application. Only Ensembles that are currently active will be
maintained in Nova. The interface can be expanded to enable
suspending and rescheduling of the Ensembles. <br>
<br>
<blockquote
cite="mid:42243FE24FEE6949AD4647D68AF230E6237A94@RHV-EXRDA-S11.corp.ebay.com"
type="cite">
<div>However, I would think that generic grouping capabilities in
Nova would be useful (e.g. to boot a group of VM). I can see
that many of such group operations might require the type of
scheduling that is available in Heat, but I would prefer that
the basic notion of VM group be implemented in Nova, with the
right scheduling support, so that it can be available without
having Heat deployed and can also be exposed in Horizon more
easily.</div>
<div>This could be implemented in a way similar to the host
aggregates.</div>
</blockquote>
<br>
Storing and maintaining VM's that are not running is not in the
scope of Nova and are better handled by applications like Heat.<br>
<br>
Thanks<br>
Gary<br>
<br>
<blockquote
cite="mid:42243FE24FEE6949AD4647D68AF230E6237A94@RHV-EXRDA-S11.corp.ebay.com"
type="cite">
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>JC</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Gary Kotton <<a
moz-do-not-send="true" href="mailto:gkotton@redhat.com">gkotton@redhat.com</a>><br>
<span style="font-weight:bold">Organization: </span>Red Hat<br>
<span style="font-weight:bold">Reply-To: </span><<a
moz-do-not-send="true" href="mailto:gkotton@redhat.com">gkotton@redhat.com</a>>,
"<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>"
<<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tue, 8 Jan 2013
15:27:20 +0200<br>
<span style="font-weight:bold">To: </span>"<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>"
<<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev]
[Scheduler] New scheduler feature - VM Ensembles<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000"><font
face="Helvetica,Arial,sans-serif">Hi,<span
style="vertical-align: baseline; font-variant: normal;
font-style: normal; font-size: 15px; background-color:
transparent; text-decoration: none; font-family: Arial;
font-weight: normal;"></span></font><br>
<font face="Helvetica,Arial,sans-serif"><span
style="vertical-align:baseline;font-variant:normal;font-style:normal;font-size:15px;background-color:transparent;text-decoration:none;font-family:Arial;font-weight:normal">The
link
<a moz-do-not-send="true"
href="https://docs.google.com/document/d/1bAMtkaIFn4ZSMqqsXjs_riXofuRvApa--qo4UTwsmhw/edit"
target="_blank">
https://docs.google.com/<wbr>document/d/<wbr>1bAMtkaIFn4ZSMqqsXjs_<wbr>riXofuRvApa--qo4UTwsmhw/edit</a>
introduces the concept of a VM ensemble or VM group into
Nova. An ensemble will provide the tenant the ability to
group together VMs that provide a certain service or
part of the same application. More specifically it
enables configuring scheduling policies per group. This
will in turn allow for a more robust and resilient
service. Specifically, it will allow a tenant to deploy
a multi-VM application that is designed for VM fault
tolerance in a way that application availability is
actually resilient to physical host failure.
</span></font><br>
<font face="Helvetica,Arial,sans-serif">Any inputs and
comments will be greatly appreciated.</font><br>
<font face="Helvetica,Arial,sans-serif">Thanks</font><br>
<font face="Helvetica,Arial,sans-serif">Gary</font><br>
</div>
</div>
_______________________________________________ OpenStack-dev
mailing list <a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">
OpenStack-dev@lists.openstack.org</a> <a
moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a> </span>
</blockquote>
<br>
</body>
</html>