<html><body bgcolor="#FFFFFF"><p>Hi Duan Li, <br><br>We welcome to that contribution if you had. Just make sure that spec can be flexible handle 2 ~ N flavor cases. That could handle future requirements for N flavors, as in the ML, I found some ops had such requirements.<br><br><br><br>Thanks<br><br>Best Wishes,<br>--------------------------------------------------------------------------------<br>Kai Qiang Wu (吴开强 Kennan）<br>IBM China System and Technology Lab, Beijing<br><br>E-mail: wkqwu@cn.ibm.com<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! <br><br><img width="16" height="16" src="cid:1__=8FBBF50FDFB59E6D8f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for "Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)" ---21/04/2016 02:31:46 pm---Hi Eli, This is exactly wha"><font color="#424282">"Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)" ---21/04/2016 02:31:46 pm---Hi Eli, This is exactly what I want. If you guys think this requirement is reasonable, I’d like to c</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)" <li-gong.duan@hpe.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">21/04/2016 02:31 pm</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font color="#1F497D" face="Calibri">Hi Eli,</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">This is exactly what I want. If you guys think this requirement is reasonable, I’d like to commit a design spec so that we could discuss it in details.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Regards,</font><br><font color="#1F497D" face="Calibri">Gary Duan</font><br><font color="#1F497D" face="Calibri"> </font><br><b><font face="Calibri">From:</font></b><font face="Calibri"> Eli Qiao [</font><font face="Calibri"><a href="mailto:liyong.qiao@intel.com">mailto:liyong.qiao@intel.com</a></font><font face="Calibri">] </font><b><font face="Calibri"><br>Sent:</font></b><font face="Calibri"> Wednesday, April 20, 2016 5:08 PM</font><b><font face="Calibri"><br>To:</font></b><font face="Calibri"> openstack-dev@lists.openstack.org</font><b><font face="Calibri"><br>Subject:</font></b><font face="Calibri"> Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes</font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman"><br>Kannan,<br><br>I think Duan Li is talking about using both 2 kinds of </font><font size="4" face="Calibri">(secure-booted and non-secure-booted) node deploy *minion* node.<br><br>The scenario may like this:<br>let say 2 flavors:</font><ul><ul type="disc"><li><font size="4" face="Calibri">flavor_secure</font><li><font size="4" face="Calibri">flavor_none_secure</font></ul></ul><font size="4" face="Calibri">For now, flavor-id in baymodel can only be set as one value, Duan Li's requirement is to using flavor-id = [flavor_none_secure, flavor_secure]<br>and provision one cluster which minion nodes are build from 2 types of flavor, then after cluster(bay ) provision finished , passing lable to<br>let k8s cluster to chose a minion node to start pod on that specific node.<br><br><br>For now, Magnum doesn't support it yet, I think it good to have it, but the implementation may be differnece per COE since after we<br>provision bay, the scheduler work are done by k8s/swarm/mesos.<br><br>Eli.<br></font><br><font size="4" face="Times New Roman">On 2016</font><font size="4" face="宋体">年</font><font size="4" face="Times New Roman">04</font><font size="4" face="宋体">月</font><font size="4" face="Times New Roman">20</font><font size="4" face="宋体">日</font><font size="4" face="Times New Roman"> 16:36, Kai Qiang Wu wrote:</font><ul><ul><font size="4" face="Times New Roman">Hi Duan Li,<br><br>Not sure if I get your point very clearly.<br><br>1> Magnum did support :</font><u><font size="4" color="#0000FF" face="Times New Roman"><br></font></u><a href="https://github.com/openstack/magnum/blob/master/magnum/api/controllers/v1/baymodel.py#L65"><u><font size="4" color="#0000FF" face="Times New Roman">https://github.com/openstack/magnum/blob/master/magnum/api/controllers/v1/baymodel.py#L65</font></u></a><font size="4" face="Times New Roman"><br><br>flavor-id for minion node<br>master-flavor-id for master node<br><br>So your K8s cluster could have such two kinds of flavors.<br><br><br>2> For one question about ironic case (I found you deploy on ironic), I did not think Magnum templates now support ironic case now.<br>As ironic VLAN related feature are still developing, and not merged(many patches are under review, pick one for example </font><a href="https://review.openstack.org/#/c/277853"><u><font size="4" color="#0000FF" face="Times New Roman">https://review.openstack.org/#/c/277853</font></u></a><font size="4" face="Times New Roman">)<br><br><br>I am not sure how would you use ironic for k8s cluster ? <br></font><br><font face="Courier New">-- </font><br><font face="Courier New">Best Regards, Eli Qiao (</font><font face="宋体">乔立勇</font><font face="Courier New">)</font><br><font face="Courier New">Intel OTC China</font><tt>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><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><tt><br></tt><br><br></ul></ul><BR>
</body></html>