Lessons Learnt from Running a Container-Native Cloud
This is a liveblog of the session titled “Lessons Learnt from Running a Container-Native Cloud,” led by Xu Wang. Wang is the CTO and co-founder of Hyper.sh, a company that has been working on leveraging hypervisor isolation for containers. This session claims to discuss some lessons learned from running a cloud leveraging this sort of technology.
Wang starts with a brief overview of Hyper.sh. The information for this session comes from running a Hypernetes (Hyper.sh plus Kubernetes)-based cloud for a year.
So, what is a “container-native” cloud? Wang provides some criteria:
- A container is a first-class citizen in the cloud. This means container-level APIs and the ability to launch containers without a VM.
- The cloud offers container-centric resources (floating IPs, security groups, etc.).
- The cloud offers container-based services (load balancing, scheduled jobs, functions, etc.).
- Billing is handled on a per-container level (not on a VM level).
To be honest, I don’t see how any cloud other than Hyper.sh’s own offering could meet these criteria; none of the major public cloud providers (Microsoft Azure, AWS, GCP) currently satisfy Wang’s requirements. A “standard” OpenStack installation doesn’t meet these requirements. This makes the session more like a Continue reading
Telcos own the wired and wireless infrastructure needed for smart cities.
It provides a migration path from perimeter-based security appliances.
Companies will be able to test self-driving cars, AR/VR, and drones.
Past Ericsson executives have ended up at Verizon.