Hi all,
I am glad to introduce the HyperStack project to you.
HyperStack is a native, multi-tenant CaaS solution built on top of OpenStack.
In terms of architecture, HyperStack = Bare-metal + Hyper + Kubernetes + Cinder
+ Neutron.
HyperStack is different from Magnum in that HyperStack doesn't employ the Bay
concept. Instead, HyperStack pools all bare-metal servers into one singe
cluster. Due to the hypervisor nature in Hyper, different tenants' applications
are completely isolated (no shared kernel), thus co-exist without security
concerns in a same cluster.
Given this, HyperStack is a solution for public cloud providers who want to
offer the secure, multi-tenant CaaS.
Ref:
https://trello-attachments.s3.amazonaws.com/55545e127c7cbe0ec5b82f2b/1258x535/1c85a755dcb5e4a4147d37e6aa22fd40/upload_7_23_2015_at_11_00_41_AM.png
The next step is to present a working beta of HyperStack at Tokyo summit, which
we submitted a presentation:
https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/Presentation/4030.
Please vote if you are interested.
In the future, we want to integrate HyperStack with Magnum and Nova to make
sure one OpenStack deployment can offer both IaaS and native CaaS services.
Best,
Peng
---------- Background
---------------------------------------------------------------------------
Hyper is a hypervisor-agnostic Docker runtime. It allows to run Docker images
with any hypervisor (KVM, Xen, Vbox, ESX). Hyper is different from the
minimalist Linux distros like CoreOS by that Hyper runs on the physical box and
load the Docker images from the metal into the VM instance, in which no guest
OS is present. Instead, Hyper boots a minimalist kernel in the VM to host the
Docker images (Pod).
With this approach, Hyper is able to bring some encouraging results, which are
similar to container:
- 300ms to boot a new HyperVM instance with a pod of Docker images
- 20MB for min mem footprint of a HyperVM instance
- Immutable HyperVM, only kernel+images, serves as atomic unit (Pod) for
scheduling
- Immune from the shared kernel problem in LXC, isolated by VM
- Work seamlessly with OpenStack components, Neutron, Cinder, due to the
hypervisor nature
- BYOK, bring-your-own-kernel is somewhat mandatory for a public cloud platform
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
