settingsLogin | Registersettings

[openstack-dev] [magnum] Architecture support for either VM or Ironic instance as Containers' Host ?

0 votes

I believe the MAGNUM architecture supports using either a VM Instance or an Ironic Instance as the Host for the COE’s masters and minions.

How is this done / abstracted within the MAGNUM Architecture ?
i.e. is there a ‘container-host-driver API’ that is defined; and implemented for both VM and Ironic ?
( Feel free to just refer me to a URL that describes this. )

The reason I ask is that I have a proprietary bare metal service that I would like to have MAGNUM run on top of.

Greg.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Jul 20, 2017 in openstack-dev by Waines,_Greg (2,700 points)   1 5 9

1 Response

0 votes

Hi Greg,

You're correct - magnum features support for running on top of VMs or
baremetal. Currently baremetal is supported for kubernetes on Fedora core
only[1]. There is a cluster template parameter 'server_type', which should
be set to 'BM' for baremetal clusters.

In terms of how this works within magnum, each magnum driver advertises one
or more (OS, COE, server_type) tuples that it supports via its 'provides'
property. There is no 'container-host-driver API' - magnum drivers are
largely just a collection of heat templates and a little python glue.

Due to historic and current limitations with ironic (mostly around
networking[2] and block storage support), drivers typically support either
VM or BM. Ironic networking has improved over the last few releases, and it
is becoming feasible to support baremetal using the standard VM drivers. I
think there is a general desire within the project to only support one set
of drivers and remove the maintenance burden.

In terms of your use case, I think that your proprietary bare metal service
would likely not work with any existing drivers. If it could be integrated
with heat, there there is a chance that you could implement a magnum driver
and reuse some of the shared magnum code for configuring and running COEs.

[1]
https://github.com/openstack/magnum/tree/master/magnum/drivers/k8s_fedora_ironic_v1
[2] https://bugs.launchpad.net/magnum/+bug/1544195

On 17 July 2017 at 14:18, Waines, Greg Greg.Waines@windriver.com wrote:

I believe the MAGNUM architecture supports using either a VM Instance or
an Ironic Instance as the Host for the COE’s masters and minions.

How is this done / abstracted within the MAGNUM Architecture ?

i.e. is there a ‘container-host-driver API’ that is defined; and
implemented for both VM and Ironic ?

( Feel free to just refer me to a URL that describes this. )

The reason I ask is that I have a proprietary bare metal service that I
would like to have MAGNUM run on top of.

Greg.


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


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jul 20, 2017 by mark_at_stackhpc.com (740 points)  
...