Peng,
Several questions Here. You mentioned that HyperStack is a single big “bay”.
Then, who is doing the multi-host scheduling, Hyper or something else? Were you
suggesting to integrate Hyper with Magnum directly? Or you were suggesting to
integrate Hyper with Magnum indirectly (i.e. through
Hi Peng,
Please check some of my understandings in line.
Thanks
2015-07-18 0:33 GMT+08:00 Peng Zhao p...@hyper.sh:
Hi, Adrian, Jay and all,
There could be a much longer version of this, but let me try to explain in
a minimalist way.
Bay currently has two modes: VM-based, BM-based. In
Hong Bin,
I have some online discussion with Peng, seems hyper is now integrating
with Kubernetes and also have plan integrate with mesos for scheduling.
Once mesos integration finished, we can treat mesos+hyper as another kind
of bay.
Thanks
2015-07-19 4:15 GMT+08:00 Hongbin Lu
Hi, Adrian, Jay and all,
There could be a much longer version of this, but let me try to explain in a
minimalist way.
Bay currently has two modes: VM-based, BM-based. In both cases, Bay helps to
isolate different tenants' containers. In other words, bay is single-tenancy.
For BM-based bay,
Team,
I woud like to ask for your input about adding support for Hyper in Magnum:
https://blueprints.launchpad.net/magnum/+spec/hyperstack
We touched on this in our last team meeting, and it was apparent that achieving
a higher level of understanding of the technology before weighing in about
Here is the bp of Magnum+Hyper+Metal integration:
https://blueprints.launchpad.net/magnum/+spec/hyperstack
Wanted to hear more thoughts and kickstart some brainstorming.
Thanks, Peng
- Hyper - Make VM run like
