Thanks Adrian, I think that we are on same page for this: Using nova ironic
drive to provision hyper machines as bay. ;-) In my previous email, I also
mentioned two integration proposals with assumption of using ironic driver
provision those hyper machines.
1) Once Hyper and k8s integration
Thanks Peng, then I can see two integration points for Magnum and Hyper:
1) Once Hyper and k8s integration finished, we can deploy k8s in two mode:
docker and hyper mode, the end user can select which mode they want to use.
For such case, we do not need to create a new bay but may need some
Hi Jay,
Yes, we are working with the community to integrate Hyper with Mesos and K8S.
Since Hyper uses Pod as the default job unit, it is quite easy to integrate with
K8S. Mesos takes a bit more efforts, but still straightforward.
We expect to finish both integration in v0.4 early August.
Best,
Hi Peng,
Just want to get more for Hyper. If we create a hyper bay, then can I set
up multiple hosts in a hyper bay? If so, who will do the scheduling, does
mesos or some others integrate with hyper?
I did not find much info for hyper cluster management.
Thanks.
2015-07-16 9:54 GMT+08:00 Peng
Jay,
Hyper is a substitute for a Docker host, so I expect it could work equally well
for all of the current bay types. Hyper’s idea of a “pod” and a Kubernetes
“pod” are similar, but different. I’m not yet convinced that integrating Hyper
host creation direct with Magnum (and completely
-- Original --
From: “Adrian Otto”adrian.o...@rackspace.com;
Date: Wed, Jul 15, 2015 02:31 AM
To: “OpenStack Development Mailing List (not for usage
questions)“openstack-dev@lists.openstack.org;
Subject: Re: [openstack-dev] [magnum][bp] Power Magnum to run
