<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" class="" style="word-wrap:break-word">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div>Adrian,</div>
<br>
I know for sure you can attach key=value metadata to the flavors. I just looked up in the admin guide, (http://docs.openstack.org/admin-guide-cloud/content/customize-flavors.html) and it mentions that the extra_specs key=value pairs are just used for scheduling
though. :/<br>
<br>
So, Nova would have to be extended to support a non scheduled type of metadata (That could be useful for other things too...), but doesn't seem to exist today.<br>
<br>
One other possibility would be, if a nova scheduling filter can remove things from the extra_specs metadata before it hits the next plugin, we could slide in a MagnumFilter at the beginning of scheduler_default_filters that removes the magnum_server_type entry.
Looking through the code, I think it would work, but makes me feel a little dirty too. I've attached an example that might be close to working for that... Maybe the Nova folks would like to weigh in if its a good plan or not?<br>
<br>
But, if the filter doesn't fly, then for Liberty it looks like your config option plan seems to be the best way to go.<br>
<br>
I like the plan, especially the default flavor/image. That should make it much easier to use if the user trusts what the admin setup for them. Nice and easy. :)<br>
<br>
Thanks,<br>
Kevin<br>
<br>
class MagnumFilter(filters.BaseHostFilter):<br>
def host_passes(self, host_state, filter_properties):<br>
try:<br>
del filter_properties['instance_type']['extra_specs']['magnum_server_type']<br>
except:<br>
pass<br>
return True<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF119903"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Adrian Otto [adrian.otto@rackspace.com]<br>
<b>Sent:</b> Thursday, July 16, 2015 2:51 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?<br>
</font><br>
</div>
<div></div>
<div>
<div>Kevin,</div>
<div><br>
</div>
<div>You make a really good point. Reducing required inputs from users in exchange for a little more setup by cloud operators is a well justified tradeoff. I'm pretty sure flavors in Nova can have tag Metadata added without a nova extension, right? Can someone
check to be sure?</div>
<div><br>
</div>
<div>If we do have a way to tag flavors, then let's default the value (as you said) to use in cases where the flavor is untagged, and make that configurable as a Magnum config directive. We could also log a warning each time the default is used unless the administrator
disables the log notices in our config. That way we have a way to direct them to relevant documentation if they start using Magnum without tagging any flavors first.</div>
<div><br>
</div>
<div>We should also mention flavor tagging in our various setup guides with references to detailed instructions.</div>
<div><br>
</div>
<div>Let's also make sure that flavor and image args to bay_create also have a configurable default in Magnum for when they are omitted by the user.</div>
<div><br>
</div>
<div>Adrian</div>
<br>
<br>
-------- Original message --------<br>
From: "Fox, Kevin M" <Kevin.Fox@pnnl.gov> <br>
Date: 07/16/2015 1:32 PM (GMT-08:00) <br>
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>
<br>
Subject: Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?
<br>
<br>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Good point.<br>
<br>
+1 on server_type. it seems reasonable.<br>
<br>
As for the need, I'd really rather not have my users have to know how to map flavors to server_types themselves. Its something they will get wrong at times, and we'll get emails about/spend time explaining.<br>
<br>
The lack of heat conditionals has been unpleasant. I know its being worked on now, but not there yet.<br>
<br>
In talking with the heat developers, their current recommendation has been, put the conditional stuff as provider resources in different environment files, and make the template generic. (ala
<a href="http://hardysteven.blogspot.com/2013/10/heat-providersenvironments-101-ive.html)." target="_blank">
http://hardysteven.blogspot.com/2013/10/heat-providersenvironments-101-ive.html).</a> You can then switch out one environment for another to switch things somewhat conditionally then. I'm not sure if this is flexible enough to handle the concern you have though.<br>
<br>
But, I think the conditional thing is not the real issue. Whether it supported proper conditionals, it would work with environments, or it would work with seperate templates, any way you slice it, you need some way to fetch which of the choices you want to
specify. Either by being specified manually by the user, or some stored mapping in a config file, nova flavor metadata, or flavor mapping stored in the magnum db.<br>
<br>
So does the user provide that piece of information or does the admin attach it to the flavor some how? I'm all for the admin doing it, since I can do it when I setup the flavors/magnum and never have to worry about it again. Maybe even support a default = 'vm'
so that I only have to go in and tag the ironic flavors as such. That means I only have to worry about tagging 1 or 2 flavors by hand, and the users don't have to do anything. A way better user experience for all involved.<br>
<br>
Thanks,<br>
Kevin<br>
<br>
<div style="font-family:Times New Roman; color:#000000; font-size:16px">
<hr tabindex="-1">
<div id="divRpF38742" style="direction:ltr"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Adrian Otto [adrian.otto@rackspace.com]<br>
<b>Sent:</b> Thursday, July 16, 2015 12:35 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?<br>
</font><br>
</div>
<div></div>
<div>To be clear we have two pursuits on this thread:
<div class=""><br class="">
</div>
<div class="">1) What to rename bay.blatform to.</div>
<div class="">2) How we might eliminate the attribute, or replace it with something more intuitive</div>
<div class=""><br class="">
</div>
<div class="">We have a consensus now on how to address #1. My direction to Kannan is to proceed using server_type as the new attribute name. If anyone disagrees, you can let us know now, or submit a subsequent patch to address that concern, and we can vote
on it in Gerrit.</div>
<div class=""><br class="">
</div>
<div class="">On this subject of potentially eliminating, or replacing this attribute with something else, let’s continue to discuss that.</div>
<div class=""><br class="">
</div>
<div class="">One key issue is that our current HOT file format does not have any facility for conditional logic evaluation, so if the Bay orchestration differs between various server_type values, we need to select the appropriate value based on the way the
bay is created. I’m open to hearing suggestions for implementing any needed conditional logic, if we can put it into a better place.</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 16, 2015, at 8:54 AM, Fox, Kevin M <<a href="mailto:Kevin.Fox@pnnl.gov" class="" target="_blank">Kevin.Fox@pnnl.gov</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="" style="font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; direction:ltr; font-family:Tahoma; font-size:10pt">
Wait... so the issue is if you were to just use nova flavor, you don't have enough information to choose a set of templates that may be more optimal for that flavor type (like vm's or bare metal)? Is this a NaaS vs flatdhcp kind of thing? I just took a quick
skim of the heat templates and it wasn't really clear why the template needs to know.<br class="">
<br class="">
If that sort of thing is needed, maybe allow a heat environment or the template set to be tagged onto nova flavors in Magnum by the admin, and then the user can be concerned only with nova flavors? They are use to dealing with them. Sahara and Trove do some
similar things I think.<br class="">
<br class="">
Thanks,<br class="">
Kevin<br class="">
<br class="">
<div class="" style="font-family:'Times New Roman'; font-size:16px">
<hr tabindex="-1" class="">
<div id="divRpF608861" class="" style="direction:ltr"><font class="" face="Tahoma" size="2"><b class="">From:</b><span class="Apple-converted-space"> </span>Hongbin Lu [<a href="mailto:hongbin.lu@huawei.com" class="" target="_blank">hongbin.lu@huawei.com</a>]<br class="">
<b class="">Sent:</b><span class="Apple-converted-space"> </span>Wednesday, July 15, 2015 8:42 PM<br class="">
<b class="">To:</b><span class="Apple-converted-space"> </span>OpenStack Development Mailing List (not for usage questions)<br class="">
<b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?<br class="">
</font><br class="">
</div>
<div class=""></div>
<div class="">
<div class="WordSection1">
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">Kai,</span></div>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span></p>
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">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.</span></div>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span></p>
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">[1]<span class="Apple-converted-space"> </span><a href="https://review.openstack.org/#/c/198984/6" class="" style="color:purple; text-decoration:underline" target="_blank">https://review.openstack.org/#/c/198984/6</a></span></div>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span></p>
<div class="">
<div class="" style="border-style:solid none none; border-top-color:rgb(181,196,223); border-top-width:1pt; padding:3pt 0cm 0cm">
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<b class=""><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif" lang="EN-US">From:</span></b><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif" lang="EN-US"><span class="Apple-converted-space"> </span>Kai Qiang Wu [<a href="mailto:wkqwu@cn.ibm.com" class="" target="_blank">mailto:wkqwu@cn.ibm.com</a>]<span class="Apple-converted-space"> </span><br class="">
<b class="">Sent:</b><span class="Apple-converted-space"> </span>July-15-15 10:36 PM<br class="">
<b class="">To:</b><span class="Apple-converted-space"> </span>OpenStack Development Mailing List (not for usage questions)<br class="">
<b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span></div>
</div>
</div>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
</p>
<div class="" style="margin:0px 0cm; font-size:12pt; font-family:SimSun"><span class="" style="font-size:10pt; font-family:Arial,sans-serif">Hi HongBin,</span><br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">I think flavors introduces more confusion than nova_instance_type or instance_type.</span><br class="">
<br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">As flavors not have binding with 'vm' or 'baremetal',</span><br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">Let me summary the initial question:<span class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif"> We have two kinds of templates for kubernetes now,<span class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; 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 class="">
<span class="" style="font-size:10pt; 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 class="">
<br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">1> If used flavor, it is nova specific concept: take two as example,<span class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif"> m1.small, or m1.middle.<span class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif"> m1.small < 'VM' m1.middle < 'VM' </span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif"> Both m1.small and m1.middle can be used in 'VM' environment.</span><br class="">
<span class="" style="font-size:10pt; 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 class="">
<br class="">
<br class="">
<span class="" style="font-size:10pt; 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 class="">
<br class="">
<br class="">
<span class="" style="font-size:10pt; 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 class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">instance_type = 'vm', it means such templates fit for normal 'VM' heat stack deploy</span><br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">instance_type = 'baremetal', it means such templates fit for ironic baremetal heat stack deploy.</span><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">Thanks!</span><br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif"> <span class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">Best Wishes,</span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">--------------------------------------------------------------------------------</span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">Kai Qiang Wu (</span><span class="" style="font-size:10pt" lang="ZH-CN">吴开强</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><span class="Apple-converted-space"> </span> Kennan</span><span class="" style="font-size:10pt" lang="ZH-CN">）</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
IBM China System and Technology Lab, Beijing<br class="">
<br class="">
E-mail:<span class="Apple-converted-space"> </span><a href="mailto:wkqwu@cn.ibm.com" class="" style="color:purple; text-decoration:underline" target="_blank">wkqwu@cn.ibm.com</a><br class="">
Tel: 86-10-82451647<br class="">
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br class="">
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193</span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">--------------------------------------------------------------------------------</span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">Follow your heart. You are miracle!<span class="Apple-converted-space"> </span></span><br class="">
<br class="">
<span id="cid:image001.gif@01D0BF57.74EDB5E0"><image001.gif></span><span class="" style="font-size:10pt; font-family:Arial,sans-serif; color:rgb(66,66,130)">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 class="">
<br class="">
<span class="" style="font-size:7.5pt; font-family:Arial,sans-serif; color:rgb(95,95,95)">From:<span class="Apple-converted-space"> </span></span><span class="" style="font-size:7.5pt; font-family:Arial,sans-serif">Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com" class="" style="color:purple; text-decoration:underline" target="_blank">hongbin.lu@huawei.com</a>></span><br class="">
<span class="" style="font-size:7.5pt; font-family:Arial,sans-serif; color:rgb(95,95,95)">To:<span class="Apple-converted-space"> </span></span><span class="" 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" class="" style="color:purple; text-decoration:underline" target="_blank">openstack-dev@lists.openstack.org</a>></span><br class="">
<span class="" style="font-size:7.5pt; font-family:Arial,sans-serif; color:rgb(95,95,95)">Date:<span class="Apple-converted-space"> </span></span><span class="" style="font-size:7.5pt; font-family:Arial,sans-serif">07/16/2015 04:44 AM</span><br class="">
<span class="" style="font-size:7.5pt; font-family:Arial,sans-serif; color:rgb(95,95,95)">Subject:<span class="Apple-converted-space"> </span></span><span class="" 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></div>
<div class="MsoNormal" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<hr class="" style="color:rgb(128,145,165)" noshade="" size="2" width="100%" align="left">
</div>
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<br class="">
<br class="">
<br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">+1 for the idea of using Nova flavor directly.</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">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></div>
<div class="" style="margin:0cm 0cm 0.0001pt 36pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)">・<span class="Apple-converted-space"> </span></span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">platform:
vm or baremetal</span><br class="">
<span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)">・<span class="Apple-converted-space"> </span></span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">os:
atomic, coreos, …</span><br class="">
<span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)">・<span class="Apple-converted-space"> </span></span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">coe:
kubernetes, swarm or mesos</span></div>
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">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></div>
<div class="" style="margin:0cm 0cm 0.0001pt 36pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)">・<span class="Apple-converted-space"> </span></span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">flavor:
baremetal, m1.small, m1.medium, …</span><br class="">
<span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)">・<span class="Apple-converted-space"> </span></span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">os:
atomic, coreos, ...</span><br class="">
<span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)">・<span class="Apple-converted-space"> </span></span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Symbol; color:rgb(31,73,125)"> </span><span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">coe:
kubernetes, swarm or mesos</span></div>
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">This approach can avoid introducing a new field in baymodel to indicate what Nova flavor already indicates.</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">Best regards,</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">Hongbin</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<b class=""><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif">From:</span></b><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif"> Fox, Kevin M [<a href="mailto:Kevin.Fox@pnnl.gov" class="" style="color:purple; text-decoration:underline" target="_blank">mailto:Kevin.Fox@pnnl.gov</a>]<span class="Apple-converted-space"> </span><b class=""><br class="">
Sent:</b> July-15-15 12:37 PM<b class=""><br class="">
To:</b> OpenStack Development Mailing List (not for usage questions)<b class=""><br class="">
Subject:</b> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br class="">
<span class="" style="font-family:Arial,sans-serif"> </span><br class="">
<span class="" style="font-size:10pt; 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 class="">
<br class="">
Thanks,<br class="">
Kevin</span></div>
<div class="MsoNormal" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun; text-align:center" align="center">
<hr class="" size="2" width="100%" align="center">
</div>
<div class="" style="margin:0cm 0cm 0.0001pt; font-size:12pt; font-family:SimSun">
<b class=""><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif">From:</span></b><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif"> Daneyon Hansen (danehans) [<a href="mailto:danehans@cisco.com" class="" target="_blank">danehans@cisco.com</a>]<b class=""><br class="">
Sent:</b> Wednesday, July 15, 2015 9:20 AM<b class=""><br class="">
To:</b> OpenStack Development Mailing List (not for usage questions)<b class=""><br class="">
Subject:</b> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br class="">
<span class="" style="font-size:10pt; font-family:Courier">All,</span><br class="">
<span class="" style="font-size:10pt; font-family:'Times New Roman',serif"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Courier">IMO virt_type does not properly describe bare metal deployments. What about using the compute_driver parameter?</span><br class="">
<span class="" style="font-family:'Times New Roman',serif"> </span><br class="">
<span class="" style="font-family:Arial,sans-serif">compute_driver</span><span class="" style="font-size:10pt; font-family:'Times New Roman',serif"> =<span class="Apple-converted-space"> </span></span><span class="" style="font-family:Arial,sans-serif">None</span><br class="">
<span class="" style="font-family:Arial,sans-serif"><br class="">
</span><br class="">
<span class="" 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 class="">
<span class="" style="font-family:Arial,sans-serif"><br class="">
</span><br class="">
<a href="http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-family:Arial,sans-serif">http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html</span></a><br class="">
<a href="http://docs.openstack.org/developer/ironic/deploy/install-guide.html" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-family:'Times New Roman',serif">http://docs.openstack.org/developer/ironic/deploy/install-guide.html</span></a><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif"> </span><br class="">
<b class=""><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">From:<span class="Apple-converted-space"> </span></span></b><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">Adrian Otto <</span><a href="mailto:adrian.otto@rackspace.com" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">adrian.otto@rackspace.com</span></a><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">><b class=""><br class="">
Reply-To:<span class="Apple-converted-space"> </span></b>"OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">openstack-dev@lists.openstack.org</span></a><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">><b class=""><br class="">
Date:<span class="Apple-converted-space"> </span></b>Tuesday, July 14, 2015 at 7:44 PM<b class=""><br class="">
To:<span class="Apple-converted-space"> </span></b>"OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">openstack-dev@lists.openstack.org</span></a><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">><b class=""><br class="">
Subject:<span class="Apple-converted-space"> </span></b>Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif"> </span></div>
<p class="MsoNormal" style="margin:0cm 0cm 12pt 36pt; font-size:12pt; font-family:SimSun">
<span class="" style="font-size:10pt; 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 class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif">Adrian</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif"><br class="">
<br class="">
-------- Original message --------<br class="">
From: Hongbin Lu <</span><a href="mailto:hongbin.lu@huawei.com" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">hongbin.lu@huawei.com</span></a><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">><span class="Apple-converted-space"> </span><br class="">
Date: 07/14/2015 7:20 PM (GMT-08:00)<span class="Apple-converted-space"> </span><br class="">
To: "OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">openstack-dev@lists.openstack.org</span></a><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">><span class="Apple-converted-space"> </span><br class="">
Subject: Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?<span class="Apple-converted-space"> </span></span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">I am going to propose a third option:</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">3. virt_type</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">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 class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">[1]<span class="Apple-converted-space"> </span></span><a href="https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Calibri,sans-serif">https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup</span></a><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">Best regards,</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">Hongbin</span><br class="">
<span class="" style="font-size:10pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)"> </span><br class="">
<b class=""><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif">From:</span></b><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif"> Kai Qiang Wu [</span><a href="mailto:wkqwu@cn.ibm.com" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif">mailto:wkqwu@cn.ibm.com</span></a><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif">]<span class="Apple-converted-space"> </span><b class=""><br class="">
Sent:</b> July-14-15 9:35 PM<b class=""><br class="">
To:</b> </span><a href="mailto:openstack-dev@lists.openstack.org" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif">openstack-dev@lists.openstack.org</span></a><b class=""><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif"><br class="">
Subject:</span></b><span class="" style="font-size:10pt; font-family:Tahoma,sans-serif"> [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</span><br class="">
<span class="" style="font-family:Arial,sans-serif"> </span><br class="">
<span class="" style="font-size:10pt; font-family:Arial,sans-serif">Hi Magnum Guys,</span><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
I want to raise this question through ML.</span><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
In this patch<span class="Apple-converted-space"> </span></span><a href="https://review.openstack.org/#/c/200401/" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Arial,sans-serif">https://review.openstack.org/#/c/200401/</span></a><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
For some old history reason, we use<span class="Apple-converted-space"> </span><b class="">platform<span class="Apple-converted-space"> </span></b>to indicate 'vm' or 'baremetal'.<br class="">
This seems not proper for that, @Adrian proposed nova_instance_type, and someone prefer other names, let me summarize as below:</span><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
1. nova_instance_type 2 votes</span><span class="" style="font-family:Arial,sans-serif"><br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
2. instance_type 2 votes</span><span class="" style="font-family:Arial,sans-serif"><br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
3. others (1 vote, but not proposed any name)</span><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
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 class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
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 class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
Please help to vote for that name.<span class="Apple-converted-space"> </span></span><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
Thanks</span><span class="" style="font-family:Arial,sans-serif"><br class="">
<br class="">
<br class="">
<br class="">
</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
Best Wishes,<br class="">
--------------------------------------------------------------------------------<br class="">
Kai Qiang Wu (</span><span class="" style="font-size:10pt" lang="ZH-CN">吴开强</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"> Kennan</span><span class="" style="font-size:10pt" lang="ZH-CN">）</span><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
IBM China System and Technology Lab, Beijing<br class="">
<br class="">
E-mail:<span class="Apple-converted-space"> </span></span><a href="mailto:wkqwu@cn.ibm.com" class="" style="color:purple; text-decoration:underline" target="_blank"><span class="" style="font-size:10pt; font-family:Arial,sans-serif">wkqwu@cn.ibm.com</span></a><span class="" style="font-size:10pt; font-family:Arial,sans-serif"><br class="">
Tel: 86-10-82451647<br class="">
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br class="">
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br class="">
--------------------------------------------------------------------------------<br class="">
Follow your heart. You are miracle!<span class="Apple-converted-space"> </span></span><tt class="" style="font-family:SimSun"><span class="" style="font-size:10pt">__________________________________________________________________________</span></tt><span class="" style="font-size:10pt"><br class="">
<tt class="" style="font-family:SimSun">OpenStack Development Mailing List (not for usage questions)</tt><br class="">
<tt class="" style="font-family:SimSun">Unsubscribe:<span class="Apple-converted-space"> </span><a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="" style="color:purple; text-decoration:underline" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></tt><br class="">
<tt class="" style="font-family:SimSun"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="" style="color:purple; text-decoration:underline" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt></span></p>
</div>
</div>
</div>
</div>
<span class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; float:none; display:inline!important">__________________________________________________________________________</span><br class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<span class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; float:none; display:inline!important">OpenStack
Development Mailing List (not for usage questions)</span><br class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<span class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; float:none; display:inline!important">Unsubscribe:
<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<span class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; float:none; display:inline!important"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span></div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>