<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=gb2312">
<meta name="Generator" content="Microsoft Word 12 (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:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:SimSun;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:SimSun;}
tt
{mso-style-priority:99;
font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:190463219;
mso-list-template-ids:-136252776;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:663119720;
mso-list-template-ids:-1476364756;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:988283940;
mso-list-template-ids:508881546;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kai,<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">Sorry for the confusion. To clarify, I was thinking how to name the field you proposed in baymodel [1]. I prefer to drop it and use the existing field ¡®flavor¡¯
to map the Heat template.<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">[1]
<a href="https://review.openstack.org/#/c/198984/6">https://review.openstack.org/#/c/198984/6</a><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>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kai Qiang Wu [mailto:wkqwu@cn.ibm.com]
<br>
<b>Sent:</b> July-15-15 10:36 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Hi HongBin,</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">I think flavors introduces more confusion than nova_instance_type or instance_type.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">As flavors not have binding with 'vm' or 'baremetal',</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Let me summary the initial question:
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> We have two kinds of templates for kubernetes now,
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(as templates in heat not flexible like programming language, if else etc. And separate templates are easy to maintain)</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">The two kinds of kubernets templates, One for boot VM, another boot Baremetal. 'VM' or Baremetal here is just used for heat template selection.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">1> If used flavor, it is nova specific concept: take two as example,
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> m1.small, or m1.middle.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> m1.small < 'VM' m1.middle < 'VM' </span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> Both m1.small and m1.middle can be used in 'VM' environment.</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">So we should not use m1.small as a template identification. That's why I think flavor not good to be used.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">2> @Adrian, we have --flavor-id field for baymodel now, it would picked up by heat-templates, and boot instances with such flavor.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">3> Finally, I think instance_type is better. instance_type can be used as heat templates identification parameter.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">instance_type = 'vm', it means such templates fit for normal 'VM' heat stack deploy</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">instance_type = 'baremetal', it means such templates fit for ironic baremetal heat stack deploy.</span><br>
<br>
<br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Thanks!</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> </span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Best Wishes,</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">--------------------------------------------------------------------------------</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Kai Qiang Wu (</span><span lang="ZH-CN" style="font-size:10.0pt">Î⿪ǿ</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> Kennan</span><span lang="ZH-CN" style="font-size:10.0pt">£©</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: <a href="mailto:wkqwu@cn.ibm.com">wkqwu@cn.ibm.com</a><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">--------------------------------------------------------------------------------</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Follow your heart. You are miracle!
</span><br>
<br>
<img border="0" width="16" height="16" id="_x0000_i1025" src="cid:image001.gif@01D0BF57.74EDB5E0" alt="Inactive hide details for Hongbin Lu ---07/16/2015 04:44:14 AM---+1 for the idea of using Nova flavor directly. Why we introduc"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#424282">Hongbin
Lu ---07/16/2015 04:44:14 AM---+1 for the idea of using Nova flavor directly. Why we introduced the ¡°platform¡± field to indicate ¡°v</span><br>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">07/16/2015 04:44 AM</span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1 for the idea of using Nova flavor directly.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Why we introduced the ¡°platform¡± field to indicate ¡°vm¡± or ¡°baremetel¡± is that magnum need to map a bay to a Heat template (which will be used to provision the bay). Currently,
Magnum has three layers of mapping:</span> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">¡€
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">platform: vm or baremetal</span><br>
<span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">¡€ </span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">os: atomic, coreos, ¡</span><br>
<span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">¡€ </span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">coe: kubernetes, swarm or mesos</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think we could just replace ¡°platform¡± with ¡°flavor¡±, if we can populate a list of flovars for VM and another list of flavors for baremetal (We may need an additional list of
flavors for container in the future for the nested container use case). Then, the new three layers would be:</span>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">¡€
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">flavor: baremetal, m1.small, m1.medium, ¡</span><br>
<span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">¡€ </span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">os: atomic, coreos, ...</span><br>
<span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">¡€ </span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;color:#1F497D"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#1F497D">
</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">coe: kubernetes, swarm or mesos</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This approach can avoid introducing a new field in baymodel to indicate what Nova flavor already indicates.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hongbin</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Fox, Kevin M [<a href="mailto:Kevin.Fox@pnnl.gov">mailto:Kevin.Fox@pnnl.gov</a>]
<b><br>
Sent:</b> July-15-15 12:37 PM<b><br>
To:</b> OpenStack Development Mailing List (not for usage questions)<b><br>
Subject:</b> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br>
<span style="font-family:"Arial","sans-serif""> </span><br>
<span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Maybe somehow I missed the point, but why not just use raw Nova flavors? They already abstract away irconic vs kvm vs hyperv/etc.<br>
<br>
Thanks,<br>
Kevin</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Daneyon Hansen (danehans) [danehans@cisco.com]<b><br>
Sent:</b> Wednesday, July 15, 2015 9:20 AM<b><br>
To:</b> OpenStack Development Mailing List (not for usage questions)<b><br>
Subject:</b> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br>
<span style="font-size:10.0pt;font-family:Courier">All,</span><br>
<span style="font-size:10.0pt;font-family:"Times New Roman","serif""> </span><br>
<span style="font-size:10.0pt;font-family:Courier">IMO virt_type does not properly describe bare metal deployments. What about using the compute_driver parameter?</span><br>
<span style="font-family:"Times New Roman","serif""> </span><br>
<span style="font-family:"Arial","sans-serif"">compute_driver</span><span style="font-size:10.0pt;font-family:"Times New Roman","serif""> =
</span><span style="font-family:"Arial","sans-serif"">None</span><br>
<span style="font-family:"Arial","sans-serif""><br>
</span><br>
<span style="font-family:"Arial","sans-serif"">(StrOpt) Driver to use for controlling virtualization. Options include: libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, baremetal.BareMetalDriver, vmwareapi.VMwareVCDriver, hyperv.HyperVDriver</span><br>
<span style="font-family:"Arial","sans-serif""><br>
</span><br>
<a href="http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html" target="_blank"><span style="font-family:"Arial","sans-serif"">http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html</span></a><br>
<a href="http://docs.openstack.org/developer/ironic/deploy/install-guide.html" target="_blank"><span style="font-family:"Times New Roman","serif"">http://docs.openstack.org/developer/ironic/deploy/install-guide.html</span></a><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span><br>
<b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">From: </span>
</b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Adrian Otto <</span><a href="mailto:adrian.otto@rackspace.com" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">adrian.otto@rackspace.com</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">><b><br>
Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">openstack-dev@lists.openstack.org</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">><b><br>
Date: </b>Tuesday, July 14, 2015 at 7:44 PM<b><br>
To: </b>"OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">openstack-dev@lists.openstack.org</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">><b><br>
Subject: </b>Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">One drawback to virt_type if not seen in the context of the acceptable values, is that it should be set to values like libvirt, xen, ironic, etc. That might actually be good. Instead of using
the values 'vm' or 'baremetal', we use the name of the nova virt driver, and interpret those to be vm or baremetal types. So if I set the value to 'xen', I know the nova instance type is a vm, and 'ironic' means a baremetal nova instance.
</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Adrian</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif""><br>
<br>
-------- Original message --------<br>
From: Hongbin Lu <</span><a href="mailto:hongbin.lu@huawei.com" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">hongbin.lu@huawei.com</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">>
<br>
Date: 07/14/2015 7:20 PM (GMT-08:00) <br>
To: "OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">openstack-dev@lists.openstack.org</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">>
<br>
Subject: Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?
</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am going to propose a third option:</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">3. virt_type</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I have concerns about option 1 and 2, because ¡°instance_type¡± and flavor was used interchangeably before [1]. If we use ¡°instance_type¡± to indicate ¡°vm¡± or ¡°baremetal¡±, it may cause
confusions.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[1]
</span><a href="https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup</span></a><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hongbin</span><br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><br>
<b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kai Qiang Wu [</span><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:wkqwu@cn.ibm.com</span></a><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<b><br>
Sent:</b> July-14-15 9:35 PM<b><br>
To:</b> </span><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">openstack-dev@lists.openstack.org</span></a><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
Subject:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br>
<span style="font-family:"Arial","sans-serif""> </span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Hi Magnum Guys,</span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
I want to raise this question through ML.</span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
In this patch </span><a href="https://review.openstack.org/#/c/200401/" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">https://review.openstack.org/#/c/200401/</span></a><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
For some old history reason, we use <b>platform </b>to indicate 'vm' or 'baremetal'.<br>
This seems not proper for that, @Adrian proposed nova_instance_type, and someone prefer other names, let me summarize as below:</span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
1. nova_instance_type 2 votes</span><span style="font-family:"Arial","sans-serif""><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
2. instance_type 2 votes</span><span style="font-family:"Arial","sans-serif""><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
3. others (1 vote, but not proposed any name)</span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Let's try to reach the agreement ASAP. I think count the final votes winner as the proper name is the best solution(considering community diversity).</span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
BTW, If you not proposed any better name, just vote to disagree all, I think that vote is not valid and not helpful to solve the issue.</span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Please help to vote for that name. </span><span style="font-family:"Arial","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Thanks</span><span style="font-family:"Arial","sans-serif""><br>
<br>
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</span><span lang="ZH-CN" style="font-size:10.0pt">Î⿪ǿ</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> Kennan</span><span lang="ZH-CN" style="font-size:10.0pt">£©</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </span><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">wkqwu@cn.ibm.com</span></a><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br>
--------------------------------------------------------------------------------<br>
Follow your heart. You are miracle! </span><tt><span style="font-size:10.0pt">__________________________________________________________________________</span></tt><span style="font-size:10.0pt"><br>
<tt>OpenStack Development Mailing List (not for usage questions)</tt><br>
<tt>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></tt><br>
<tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt></span><o:p></o:p></p>
</div>
</body>
</html>