[openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

Kai Qiang Wu wkqwu at cn.ibm.com
Thu Apr 21 06:57:55 UTC 2016

Hi Duan Li,

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.


Best Wishes,
Kai Qiang Wu (吴开强  Kennan)
IBM China System and Technology Lab, Beijing

E-mail: wkqwu at cn.ibm.com
Tel: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
         No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China
Follow your heart. You are miracle!

From:	"Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)"
            <li-gong.duan at hpe.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>
Date:	21/04/2016 02:31 pm
Subject:	Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to
            provision minion nodes

Hi Eli,

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

Gary Duan

From: Eli Qiao [mailto:liyong.qiao at intel.com]
Sent: Wednesday, April 20, 2016 5:08 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to
provision minion nodes


I think Duan Li is talking about using both 2 kinds of (secure-booted and
non-secure-booted) node deploy *minion* node.

The scenario may like this:
let say 2 flavors:
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]
and provision one cluster which minion nodes are build from 2 types of
flavor, then after cluster(bay ) provision finished , passing lable to
let k8s cluster to chose a minion node to start pod on that specific node.

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
provision bay, the scheduler work are done by k8s/swarm/mesos.


On 2016年04月20日 16:36, Kai Qiang Wu wrote:
      Hi Duan Li,

      Not sure if I get your point very clearly.

      1> Magnum did support :

      flavor-id for minion node
      master-flavor-id for master node

      So your K8s cluster could have such two kinds of flavors.

      2> For one question about ironic case (I found you deploy on ironic),
      I did not think Magnum templates now support ironic case now.
      As ironic VLAN related feature are still developing, and not merged
      (many patches are under review, pick one for example

      I am not sure how would you use ironic for k8s cluster ?

      Best Regards, Eli Qiao (乔立勇)
      Intel OTC China

      OpenStack Development Mailing List (not for usage questions)
      OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160421/91549fa2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160421/91549fa2/attachment.gif>

More information about the OpenStack-dev mailing list