Open Stack

Hi Duan Li,

Not sure if I get your point very clearly.

1> Magnum did support :
https://github.com/openstack/magnum/blob/master/magnum/api/controllers/v1/baymodel.py#L65

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
https://review.openstack.org/#/c/277853)


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

Also in this summit
https://etherpad.openstack.org/p/magnum-newton-design-summit-topics, we
will have session about ironic cases:
here it is : Ironic Integration: Add support for Ironic virt-driver

If you had ways to make ironic work with Magnum, we welcome your
contribution for that topic.


Thanks

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
100193
--------------------------------------------------------------------------------
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:	20/04/2016 03:46 pm
Subject:	[openstack-dev] [Magnum] Magnum supports 2 Nova flavor to
            provision	minion nodes



Hi Folks,

We are considering whether Magnum can supports 2 Nova flavors to provision
Kubernetes and other COE minion nodes.
This requirement comes from the below use cases:
      -          There are 2 kind of baremetal machines in customer site:
      one is legacy machines which doesn’t support UEFI secure boot and
      others are new machines which support UEFI secure boot. User want to
      use Magnum to provisions a Magnum bay of Kubernetes from these 2 kind
      of baremetal machines and for the machines supporting secure boot,
      user wants to use UEFI secure boot to boot them up. And 2 Kubernetes
      label(secure-booted and non-secure-booted) are created and User can
      deploy their data-senstive/cirtical workload/containers/pods on the
      baremetal machines which are secure-booted.

This requirement requires Magnum to supports 2 Nova flavors(one is
“extra_spec: secure_boot=True” and the other doesn’t specify it) based on
the Ironic feature(
https://specs.openstack.org/openstack/ironic-specs/specs/kilo-implemented/uefi-secure-boot.html
 ).

Could you kindly give me some comments on these requirement or whether it
is reasonable from your point? If you agree, we can write design spec and
implement this feature?

Regards,
Gary
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160420/8a5bdc65/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/20160420/8a5bdc65/attachment.gif>