<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>No, what I mean is that user should be able to specify multiple AZs in his request, something like:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>nova boot --flavor 2 --image ubuntu --availability-zone AZ1 --availability-zone AZ2 vm1<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De :</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jérôme Gallard [mailto:gallard.jerome@gmail.com] <br><b>Envoyé :</b> jeudi 27 mars 2014 10:51<br><b>À :</b> OpenStack Development Mailing List (not for usage questions)<br><b>Objet :</b> Re: [openstack-dev] [nova][scheduler] Availability Zones and Host aggregates..<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><br>Hi Toan,<br>Is what you say related to : <a href="https://blueprints.launchpad.net/nova/+spec/schedule-set-availability-zones">https://blueprints.launchpad.net/nova/+spec/schedule-set-availability-zones</a> ?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>2014-03-27 10:37 GMT+01:00 Khanh-Toan Tran <<a href="mailto:khanh-toan.tran@cloudwatt.com" target="_blank">khanh-toan.tran@cloudwatt.com</a>>:<o:p></o:p></p><div><p class=MsoNormal><br><br>----- Original Message -----<br>> From: "Sangeeta Singh" <<a href="mailto:singhs@yahoo-inc.com">singhs@yahoo-inc.com</a>><br>> To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>> Sent: Wednesday, March 26, 2014 6:54:18 PM<br>> Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host aggregates..<br>><br>><br>><br>> On 3/26/14, 10:17 AM, "Khanh-Toan Tran" <<a href="mailto:khanh-toan.tran@cloudwatt.com">khanh-toan.tran@cloudwatt.com</a>><br>> wrote:<br>><br>> ><br>> ><br>> >----- Original Message -----<br>> >> From: "Sangeeta Singh" <<a href="mailto:singhs@yahoo-inc.com">singhs@yahoo-inc.com</a>><br>> >> To: "OpenStack Development Mailing List (not for usage questions)"<br>> >><<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>> >> Sent: Tuesday, March 25, 2014 9:50:00 PM<br>> >> Subject: [openstack-dev] [nova][scheduler] Availability Zones and Host<br>> >>aggregates..<br>> >><br>> >> Hi,<br>> >><br>> >> The availability Zones filter states that theoretically a compute node<br>> >>can be<br>> >> part of multiple availability zones. I have a requirement where I need<br>> >>to<br>> >> make a compute node part to 2 AZ. When I try to create a host aggregates<br>> >> with AZ I can not add the node in two host aggregates that have AZ<br>> >>defined.<br>> >> However if I create a host aggregate without associating an AZ then I<br>> >>can<br>> >> add the compute nodes to it. After doing that I can update the<br>> >> host-aggregate an associate an AZ. This looks like a bug.<br>> >><br>> >> I can see the compute node to be listed in the 2 AZ with the<br>> >> availability-zone-list command.<br>> >><br>> ><br>> >Yes it appears a bug to me (apparently the AZ metadata indertion is<br>> >considered as a normal metadata so no check is done), and so does the<br>> >message in the AvailabilityZoneFilter. I don't know why you need a<br>> >compute node that belongs to 2 different availability-zones. Maybe I'm<br>> >wrong but for me it's logical that availability-zones do not share the<br>> >same compute nodes. The "availability-zones" have the role of partition<br>> >your compute nodes into "zones" that are physically separated (in large<br>> >term it would require separation of physical servers, networking<br>> >equipments, power sources, etc). So that when user deploys 2 VMs in 2<br>> >different zones, he knows that these VMs do not fall into a same host and<br>> >if some zone falls, the others continue working, thus the client will not<br>> >lose all of his VMs. It's smaller than Regions which ensure total<br>> >separation at the cost of low-layer connectivity and central management<br>> >(e.g. scheduling per region).<br>> ><br>> >See: <a href="http://www.linuxjournal.com/content/introduction-openstack" target="_blank">http://www.linuxjournal.com/content/introduction-openstack</a><br>> ><br>> >The former purpose of regouping hosts with the same characteristics is<br>> >ensured by host-aggregates.<br>> ><br>> >> The problem that I have is that I can still not boot a VM on the<br>> >>compute node<br>> >> when I do not specify the AZ in the command though I have set the<br>> >>default<br>> >> availability zone and the default schedule zone in nova.conf.<br>> >><br>> >> I get the error ³ERROR: The requested availability zone is not<br>> >>available²<br>> >><br>> >> What I am trying to achieve is have two AZ that the user can select<br>> >>during<br>> >> the boot but then have a default AZ which has the HV from both AZ1 AND<br>> >>AZ2<br>> >> so that when the user does not specify any AZ in the boot command I<br>> >>scatter<br>> >> my VM on both the AZ in a balanced way.<br>> >><br>> ><br>> >I do not understand your goal. When you create two availability-zones and<br>> >put ALL of your compute nodes into these AZs, then if you don't specifies<br>> >the AZ in your request, then AZFilter will automatically accept all hosts.<br>> >The defaut weigher (RalWeigher) will then distribute the workload fairely<br>> >among these nodes regardless of AZ it belongs to. Maybe it is what you<br>> >want?<br>><br>> With Havana that does not happen as there is a concept of<br>> default_scheduler_zone which is none if not specified and when we specify<br>> one can only specify a since AZ whereas in my case I basically want the 2<br>> AZ that I create both to be considered default zones if nothing is<br>> specified.<o:p></o:p></p></div></div><p class=MsoNormal>If you look into the code of the AvailabilityFilter, you'll see that the filter automatically accepts host if there is NO availability-zone in the request, which is the case when user does not specify AZ. This is exactly what I see in my Openstack platform (Hanava stable). FYI, I didn't set up a default AZ in config. So whenever I creates several VMs without specifying an AZ, the scheduler spreads the VMs into all hosts regardless of their AZ.<br><br>What I think lacking is that user can not select a set of AZs instead of one or none right now.<o:p></o:p></p><div><div><p class=MsoNormal><br>> ><br>> >> Any pointers.<br>> >><br>> >> Thanks,<br>> >> Sangeeta<br>> >><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>> ><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>><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><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><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>