The document discusses hyper_, a secure, multi-tenant container cloud solution spearheaded by James Kulina. It highlights the evolution to Container as a Service (CaaS), showcasing hyper_ as a hypervisor-agnostic docker runtime that ensures security and efficiency through reduced boot times and persistent storage capabilities. The initiative aims to provide a seamless user experience in app development, enabling self-service and lowering operational costs.

1. HYPER_ :Secure, Multi-tenant Container
Cloud
James Kulina
Chief Operating Officer @ Hyper_
james@hyper.sh
@hyper_sh

2. 2
 CaaS - How did we get here?
 The end goal
 CaaS Today
 What is Hyper?
 How Hyper works
 Next Generation CaaS
 Hypernetes – Secure, Multi-tenant Kubernetes distro
Agenda

3. 3
How did we get here?
 Hypervisor Virtualization
 Cost reduction
 Allowed higher utilization of
Servers
 IaaS
 Developers could spin up virtual
machines and launch new idea
 Automation
 PaaS
 Focus on app deployment
 Abstract away infra details
 Docker
 Moved conversation to APP
centric
 App portability
 Immutability

4. 4
CaaS - The End Goal
 Enable Value Creation
 Accelerate App Development
 Self service
 Ensure Security
 Maintain same level of security that virtualization provides
 Reduce Risk
 App portability
 Multi-cloud strategy
 Lower Costs
 Minimize OPS

5. 5
CaaS Today
COE COE
VM VM VM VM
Container Container Container Container
IaaS
 Requires Prebuilt VM pools
 Capacity Planning – What is
instance type, what is storage
setup, and my VPC SDN setup?
 Know Scheduling result before
scheduled
 Low utilization of resources –
scheduling within a pool means
idle resources
Problem:
 Two separate management layers
 Need to manage IaaS (instance
types, VPC SDN, storage)
 Manage application containers
(orchestration, service discovery)
 Nest container SDN in VM VPC
SDN
 Nesting Storage, How do you do
persistent volumes? Use Flocker
on top of AWS EBS volumes?

6. 6
What is Hyper?
 Hyper
Hypervisor agnostic Docker Runtime
HyperContainer = hypervisor + Docker image
Run any Docker image any hypervisor (KVM, Xen, Virtualbox, ESX)
Secure as VM
FAST as Container
200 – 300ms Boot time

7. 7
How HyperContainer Works
hyperkernel
hyperstart
POD
RAILS NGINX LOGSTASH
HOST
Logstash imageNGINX imageRAILS image
HyperContainer
 Pull Docker image onto
Physical drive on Host
 HyperContainer
 NO GUEST OS
 Optimized Linux Kernel
 Hyperkernel will run HyperStart
 Micro Init service
 Hyperstart loads Docker images
into HyperContainer
 Uses POD concept
 MOUNT namespace for image
isolation, Docker images won't see
each others rootfs

8. 8
Best of Both Worlds!
Container HyperContainer VM
Isolation Weak Strong Strong
Portable Yes Yes No
Boot Time 100-200ms 200-300ms 60s
Image Size MBs MBs GBs
Immutable Yes Yes No
Compatible No Good Great
Mature No Good Great
BYOK No Yes Yes
ROI Low High N/A

9. 9
Build the Public CaaS w/o IaaS
COE COE
VM VM VM VM
Container Container Container Container
IaaS

10. 10
Build the Public CaaS w/o IaaS
CaaS
Hyper
Container
Hyper
Container
Hyper
Container
Hyper
Container
Hyper
Container
Hyper
Container

11. 11
Hypernetes – Multi-tenant Kubernetes Distro

12. 12
Open Source
Hyper
https://hyper.sh
https://docs.hyper.sh
@hyper_sh
https://hyperteam.slack.com
Hypernetes
https://hypernetes.com
https://docs.hypernetes.com
Github
github.com/hyperhq/hyper
github.com/hyperhq/hypernetes

13. 13
Hyper_ Container Cloud BETA
 Docker workflow
 Docker native workflow makes working with Hyper_ as simple as running Docker on your own laptop.
 Secure as virtual machines
 Applications run with hardware enforced isolation giving you the security of virtual machines with the
speed of containers.
 Hyper Elastic
 Sub-second start up times allow you to meet your user’s demands without wasting money on over-
provisioning
 Persistent Storage
 Run stateful workloads using Hyper_’s fully featured persistent storage. Take advantage of replicated,
distributed and redundant storage right from your container.
 Pay Per Second
 Per second billing means that you only pay for what you use. Combine that with sub-second start up
times and you’ll only pay for exactly what you need.

14. 14
LAUNCHING SOON
Sign up at Hyper.sh

15. 15
THANK YOU!
james@hyper.sh
@hyper_sh