<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 http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"Futura Bk";
panose-1:2 11 5 2 2 2 4 2 3 3;}
@font-face
{font-family:"Futura Hv";
panose-1:2 11 7 2 2 2 4 2 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
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="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Kai Qiang,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your comments, your consideration is very comprehensive, I think it is a good way to implement this feature.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards<o:p></o:p></p>
<p class="MsoNormal">Mike <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText">Date: Wed, 27 Apr 2016 17:38:32 +0800<o:p></o:p></p>
<p class="MsoPlainText">From: "Kai Qiang Wu" <wkqwu@cn.ibm.com><o:p></o:p></p>
<p class="MsoPlainText">To: "OpenStack Development Mailing List \(not for usage questions\)"<o:p></o:p></p>
<p class="MsoPlainText"> <openstack-dev@lists.openstack.org><o:p></o:p></p>
<p class="MsoPlainText">Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to<o:p></o:p></p>
<p class="MsoPlainText"> provision minion nodes<o:p></o:p></p>
<p class="MsoPlainText">Message-ID: <201604271004.u3RA49v4008575@d23av04.au.ibm.com><o:p></o:p></p>
<p class="MsoPlainText">Content-Type: text/plain; charset="gb2312"<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hi Mike,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Since right now, we have also support bay-update (node_count)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I am thinking the following case:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">1> baymodel-create have default flavor, and extra labels specify the(other<o:p></o:p></p>
<p class="MsoPlainText">node flavors) requirements,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">if (other node flavors) count <= bay(node_count), the extra nodes would be<o:p></o:p></p>
<p class="MsoPlainText">created use default flavor<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">if (other node flavors) count > bay(node_count), it should pop error,<o:p></o:p></p>
<p class="MsoPlainText">since it not quite clear why flavor to use<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">2> magnum bay-update k8sbay replace node_count < existed node_count, it<o:p></o:p></p>
<p class="MsoPlainText">should be OK. same as old behavior<o:p></o:p></p>
<p class="MsoPlainText"> if node_count > existed node_count, all new nodes would use default<o:p></o:p></p>
<p class="MsoPlainText">flavor_id, (if not, we need to find what's the better policy to handle<o:p></o:p></p>
<p class="MsoPlainText">that)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Refer:<o:p></o:p></p>
<p class="MsoPlainText">https://github.com/openstack/magnum/blob/master/doc/source/dev/quickstart.rst<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">What do you think ?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Best Wishes,<o:p></o:p></p>
<p class="MsoPlainText">--------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText">Kai Qiang Wu (??? Kennan?<o:p></o:p></p>
<p class="MsoPlainText">IBM China System and Technology Lab, Beijing<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">E-mail: wkqwu@cn.ibm.com<o:p></o:p></p>
<p class="MsoPlainText">Tel: 86-10-82451647<o:p></o:p></p>
<p class="MsoPlainText">Address: Building 28(Ring Building), ZhongGuanCun Software Park,<o:p></o:p></p>
<p class="MsoPlainText"> No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China<o:p></o:p></p>
<p class="MsoPlainText">100193<o:p></o:p></p>
<p class="MsoPlainText">--------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText">Follow your heart. You are miracle!<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">From: "Ma, Wen-Tao (Mike, HP Servers-PSC-BJ)" <wentao.ma@hpe.com><o:p></o:p></p>
<p class="MsoPlainText">To: "openstack-dev@lists.openstack.org"<o:p></o:p></p>
<p class="MsoPlainText"> <openstack-dev@lists.openstack.org><o:p></o:p></p>
<p class="MsoPlainText">Date: 27/04/2016 03:10 pm<o:p></o:p></p>
<p class="MsoPlainText">Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to<o:p></o:p></p>
<p class="MsoPlainText"> provision minion nodes<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hi Hong bin,<o:p></o:p></p>
<p class="MsoPlainText">Thanks very much. It?s good suggestion, I think it is a good way by using<o:p></o:p></p>
<p class="MsoPlainText">labels for extra flavors. But I notice that there is not the ?node-count<o:p></o:p></p>
<p class="MsoPlainText">parameter in baymodel.<o:p></o:p></p>
<p class="MsoPlainText">So I think it doesn?t need specify minion-flavor-0 counts by ?node-count.<o:p></o:p></p>
<p class="MsoPlainText">We can specify all of the flavor id and count ratio in the labels. It will<o:p></o:p></p>
<p class="MsoPlainText">check the minion node count with this ratio of labels when creating magnum<o:p></o:p></p>
<p class="MsoPlainText">bay that specified total minion node count . If the node-count in baycreate<o:p></o:p></p>
<p class="MsoPlainText">doesn?t match with the flavor ratio, it will return the ratio match error<o:p></o:p></p>
<p class="MsoPlainText">message. If there is not the multi-flavor-ratio key in lables, it will<o:p></o:p></p>
<p class="MsoPlainText">just use minion-flavor-0 to create 10 minion nodes.<o:p></o:p></p>
<p class="MsoPlainText">$ magnum baymodel-create --name k8sbaymodel --flavor-id minion-flavor-0<o:p></o:p></p>
<p class="MsoPlainText">--labels multi-<o:p></o:p></p>
<p class="MsoPlainText">flavor-ratio=minion-flavor-0:3,minions-flavor-1:5,minion-flavor-2:2<o:p></o:p></p>
<p class="MsoPlainText">$ magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 10<o:p></o:p></p>
<p class="MsoPlainText">Do you think about it?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> -----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">> From: Ma, Wen-Tao (Mike, HP Servers-PSC-BJ) [mailto:wentao.ma@hpe.com]<o:p></o:p></p>
<p class="MsoPlainText">> Sent: April-26-16 3:01 AM<o:p></o:p></p>
<p class="MsoPlainText">> To: openstack-dev@lists.openstack.org<o:p></o:p></p>
<p class="MsoPlainText">> Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to<o:p></o:p></p>
<p class="MsoPlainText">> provision minion nodes<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Hi Hongbin, Ricardo<o:p></o:p></p>
<p class="MsoPlainText">> This is mike, I am working with Gary now.<o:p></o:p></p>
<p class="MsoPlainText">> Thanks for Ricardo's good suggestion. I have tried the "map/index"<o:p></o:p></p>
<p class="MsoPlainText">> method , we can use it to passed the minion_flavor_map and the index<o:p></o:p></p>
<p class="MsoPlainText">> into the minion cluster stack. It does work well.<o:p></o:p></p>
<p class="MsoPlainText">> I think we can update magnum baymodel-create to set the N minion<o:p></o:p></p>
<p class="MsoPlainText">> flavors in the minion_flavor_map and assign minion counts for each<o:p></o:p></p>
<p class="MsoPlainText">> flavor.<o:p></o:p></p>
<p class="MsoPlainText">> For example :<o:p></o:p></p>
<p class="MsoPlainText">> magnum baymodel-create --name k8s-bay-model --flavor-id minion-flavor-<o:p></o:p></p>
<p class="MsoPlainText">> 0:3,minion-flavor-1:5, minion-flavor-2:2. It will create 3 types flavor<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The suggested approach seems to break the existing behaviour. I think it is<o:p></o:p></p>
<p class="MsoPlainText">better to support this feature in a backward-compatible way. How about<o:p></o:p></p>
<p class="MsoPlainText">using labels:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">$ magnum baymodel-create --name k8sbaymodel --flavor-id minion-flavor-0<o:p></o:p></p>
<p class="MsoPlainText">--node-count 3 --labels<o:p></o:p></p>
<p class="MsoPlainText">extra-flavor-ids=minions-flavor-1:5,minion-flavor-2:2<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> minion node and total minion nodes count is 10. The magnum baymode.py<o:p></o:p></p>
<p class="MsoPlainText">> will parse this dictionary and pass them to the heat template<o:p></o:p></p>
<p class="MsoPlainText">> parameters minion_flavor_map, minion_flavor_count_map. Then the heat<o:p></o:p></p>
<p class="MsoPlainText">> stack will work well.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> kubecluster-fedora-ironic.yaml<o:p></o:p></p>
<p class="MsoPlainText">> parameters:<o:p></o:p></p>
<p class="MsoPlainText">> minion_flavor_map:<o:p></o:p></p>
<p class="MsoPlainText">> type: json<o:p></o:p></p>
<p class="MsoPlainText">> default:<o:p></o:p></p>
<p class="MsoPlainText">> '0': minion-flavor-0<o:p></o:p></p>
<p class="MsoPlainText">> '1': minion-flavor-1<o:p></o:p></p>
<p class="MsoPlainText">> '2': minion-flavor-2<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> minion_flavor_count_map:<o:p></o:p></p>
<p class="MsoPlainText">> type: json<o:p></o:p></p>
<p class="MsoPlainText">> default:<o:p></o:p></p>
<p class="MsoPlainText">> '0': 3<o:p></o:p></p>
<p class="MsoPlainText">> '1': 5<o:p></o:p></p>
<p class="MsoPlainText">> '2': 2<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> resources:<o:p></o:p></p>
<p class="MsoPlainText">> kube_minions_flavors:<o:p></o:p></p>
<p class="MsoPlainText">> type: OS::Heat::ResourceGroup<o:p></o:p></p>
<p class="MsoPlainText">> properties:<o:p></o:p></p>
<p class="MsoPlainText">> count: { get_param: minion_flavors_counts }<o:p></o:p></p>
<p class="MsoPlainText">> resource_def:<o:p></o:p></p>
<p class="MsoPlainText">> type: kubecluster-minion-fedora-ironic.yaml<o:p></o:p></p>
<p class="MsoPlainText">> properties:<o:p></o:p></p>
<p class="MsoPlainText">> minion_flavor_map: {get_param: minion_flavor_map}<o:p></o:p></p>
<p class="MsoPlainText">> minion_flavor_count_map: {get_param: minion_flavor_count_map}<o:p></o:p></p>
<p class="MsoPlainText">> minion_flavor_index: '%index%'<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> How do you think about this interface in magnum baymodel to support N<o:p></o:p></p>
<p class="MsoPlainText">> falvor to provision minion nodes? Do you have any comments about this<o:p></o:p></p>
<p class="MsoPlainText">> design for this feature?<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Thanks && Regards<o:p></o:p></p>
<p class="MsoPlainText">> Mike Ma<o:p></o:p></p>
<p class="MsoPlainText">> HP Servers Core Platform Software China Email wentao.ma@hpe.com<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> -----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">> From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)<o:p></o:p></p>
<p class="MsoPlainText">> Sent: Monday, April 25, 2016 3:37 PM<o:p></o:p></p>
<p class="MsoPlainText">> To: OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">> <openstack-dev@lists.openstack.org><o:p></o:p></p>
<p class="MsoPlainText">> Cc: Ma, Wen-Tao (Mike, HP Servers-PSC-BJ) <wentao.ma@hpe.com><o:p></o:p></p>
<p class="MsoPlainText">> Subject: RE: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to<o:p></o:p></p>
<p class="MsoPlainText">> provision minion nodes<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Hi Ricardo,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> This is really good suggestion. I'd like to see whether we can use<o:p></o:p></p>
<p class="MsoPlainText">> "foreach"/"repeat" in ResourceGroup in Heat.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Regards,<o:p></o:p></p>
<p class="MsoPlainText">> Gary Duan<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> -----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">> From: Ricardo Rocha [mailto:rocha.porto@gmail.com]<o:p></o:p></p>
<p class="MsoPlainText">> Sent: Thursday, April 21, 2016 3:49 AM<o:p></o:p></p>
<p class="MsoPlainText">> To: OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">> <openstack-dev@lists.openstack.org><o:p></o:p></p>
<p class="MsoPlainText">> Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to<o:p></o:p></p>
<p class="MsoPlainText">> provision minion nodes<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Hi Hongbin.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> On Wed, Apr 20, 2016 at 8:13 PM, Hongbin Lu <hongbin.lu@huawei.com><o:p></o:p></p>
<p class="MsoPlainText">> wrote:<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)<o:p></o:p></p>
<p class="MsoPlainText">> > [mailto:li-gong.duan@hpe.com]<o:p></o:p></p>
<p class="MsoPlainText">> > Sent: April-20-16 3:39 AM<o:p></o:p></p>
<p class="MsoPlainText">> > To: OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">> > Subject: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to<o:p></o:p></p>
<p class="MsoPlainText">> > provision minion nodes<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > Hi Folks,<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > We are considering whether Magnum can supports 2 Nova flavors to<o:p></o:p></p>
<p class="MsoPlainText">> > provision Kubernetes and other COE minion nodes.<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > This requirement comes from the below use cases:<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > - There are 2 kind of baremetal machines in customer site:<o:p></o:p></p>
<p class="MsoPlainText">> one is<o:p></o:p></p>
<p class="MsoPlainText">> > legacy machines which doesn?t support UEFI secure boot and others are<o:p></o:p></p>
<p class="MsoPlainText">> > new machines which support UEFI secure boot. User want to use Magnum<o:p></o:p></p>
<p class="MsoPlainText">> > to provisions a Magnum bay of Kubernetes from these 2 kind of<o:p></o:p></p>
<p class="MsoPlainText">> > baremetal machines and for the machines supporting secure boot, user<o:p></o:p></p>
<p class="MsoPlainText">> > wants to use UEFI secure boot to boot them up. And 2 Kubernetes<o:p></o:p></p>
<p class="MsoPlainText">> > label(secure-booted and<o:p></o:p></p>
<p class="MsoPlainText">> > non-secure-booted) are created and User can deploy their<o:p></o:p></p>
<p class="MsoPlainText">> > data-senstive/cirtical workload/containers/pods on the baremetal<o:p></o:p></p>
<p class="MsoPlainText">> > machines which are secure-booted.<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > This requirement requires Magnum to supports 2 Nova flavors(one is<o:p></o:p></p>
<p class="MsoPlainText">> > ?extra_spec: secure_boot=True? and the other doesn?t specify it)<o:p></o:p></p>
<p class="MsoPlainText">> based<o:p></o:p></p>
<p class="MsoPlainText">> > on the Ironic<o:p></o:p></p>
<p class="MsoPlainText">> > feature(https://specs.openstack.org/openstack/ironic-<o:p></o:p></p>
<p class="MsoPlainText">> specs/specs/kilo-<o:p></o:p></p>
<p class="MsoPlainText">> > implemented/uefi-secure-boot.html<o:p></o:p></p>
<p class="MsoPlainText">> > ).<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > Could you kindly give me some comments on these requirement or<o:p></o:p></p>
<p class="MsoPlainText">> whether<o:p></o:p></p>
<p class="MsoPlainText">> > it is reasonable from your point? If you agree, we can write design<o:p></o:p></p>
<p class="MsoPlainText">> > spec and implement this feature?<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > I think the requirement is reasonable, but I would like to solve the<o:p></o:p></p>
<p class="MsoPlainText">> > problem in a generic way. In particular, there could be another user<o:p></o:p></p>
<p class="MsoPlainText">> > who might ask for N nova flavors to provision COE nodes in the future.<o:p></o:p></p>
<p class="MsoPlainText">> > A challenge to support N groups of Nova instances is how to express<o:p></o:p></p>
<p class="MsoPlainText">> > arbitrary number of resource groups (with different flavors) in a<o:p></o:p></p>
<p class="MsoPlainText">> Heat<o:p></o:p></p>
<p class="MsoPlainText">> > template (Magnum uses Heat template to provision COE clusters). Heat<o:p></o:p></p>
<p class="MsoPlainText">> > doesn?t seem to support the logic of looping from 1 to N. There could<o:p></o:p></p>
<p class="MsoPlainText">> > be other challenges/complexities along the way. If the proposed<o:p></o:p></p>
<p class="MsoPlainText">> design<o:p></o:p></p>
<p class="MsoPlainText">> > can address all the challenges and the implementation is clean, I am<o:p></o:p></p>
<p class="MsoPlainText">> > OK to add support for this feature. Thoughts from others?<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> This looks similar to the way we looked at passing a list of<o:p></o:p></p>
<p class="MsoPlainText">> availability zones. Mathieu asked and got a good answer:<o:p></o:p></p>
<p class="MsoPlainText">> http://lists.openstack.org/pipermail/openstack-dev/2016-<o:p></o:p></p>
<p class="MsoPlainText">> March/088175.html<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Something similar can probably be used to pass multiple flavors? Just<o:p></o:p></p>
<p class="MsoPlainText">> in case it helps.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Cheers,<o:p></o:p></p>
<p class="MsoPlainText">> Ricardo<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > Regards,<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> > Gary<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">> ______________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> > ____ OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">> > Unsubscribe:<o:p></o:p></p>
<p class="MsoPlainText">> > OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<o:p></o:p></p>
<p class="MsoPlainText">> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
<p class="MsoPlainText">> ><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> _______________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> ___<o:p></o:p></p>
<p class="MsoPlainText">> OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">> Unsubscribe: OpenStack-dev-<o:p></o:p></p>
<p class="MsoPlainText">> request@lists.openstack.org?subject:unsubscribe<o:p></o:p></p>
<p class="MsoPlainText">> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> _______________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> ___<o:p></o:p></p>
<p class="MsoPlainText">> OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">> Unsubscribe: OpenStack-dev-<o:p></o:p></p>
<p class="MsoPlainText">> request@lists.openstack.org?subject:unsubscribe<o:p></o:p></p>
<p class="MsoPlainText">> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">------------------------------<o:p></o:p></p>
<p class="MsoPlainText">__________________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<o:p></o:p></p>
<p class="MsoPlainText">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-------------- next part --------------<o:p></o:p></p>
<p class="MsoPlainText">An HTML attachment was scrubbed...<o:p></o:p></p>
<p class="MsoPlainText">URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160427/6bdfb4fe/attachment-0001.html><o:p></o:p></p>
<p class="MsoPlainText">-------------- next part --------------<o:p></o:p></p>
<p class="MsoPlainText">A non-text attachment was scrubbed...<o:p></o:p></p>
<p class="MsoPlainText">Name: graycol.gif<o:p></o:p></p>
<p class="MsoPlainText">Type: image/gif<o:p></o:p></p>
<p class="MsoPlainText">Size: 105 bytes<o:p></o:p></p>
<p class="MsoPlainText">Desc: not available<o:p></o:p></p>
<p class="MsoPlainText">URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160427/6bdfb4fe/attachment-0001.gif><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">------------------------------<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span style="font-size:8.0pt;font-family:"Futura Bk",sans-serif;color:#595959">Mike Ma<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span style="font-size:8.0pt;font-family:"Futura Bk",sans-serif;color:#595959">HP Servers Core Platform Software China
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span style="font-size:8.0pt;font-family:"Futura Hv",sans-serif;color:#595959">Mobile</span><span style="font-size:8.0pt;font-family:"Futura Bk",sans-serif;color:#595959"> +86 18610248322<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span style="font-size:8.0pt;font-family:"Futura Hv",sans-serif;color:#595959">Email</span><span style="font-size:8.0pt;font-family:"Futura Bk",sans-serif;color:#595959">
<u><a href="mailto:wentao.ma@hpe.com">wentao.ma@hpe.com</a></u><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span style="font-size:8.0pt;font-family:"Futura Bk",sans-serif;color:#595959"><o:p> </o:p></span></p>
<p class="MsoNormal"><a href="http://www.hpe.com/"><span style="color:windowtext;text-decoration:none"><img border="0" width="116" height="45" id="Picture_x0020_1" src="cid:image001.png@01D1A16C.F01939E0" alt="http://h71028.www7.hp.com/hpe_logo_email_signature/HPE_logo_email_signature.png"></span></a><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>