5. 5
● Share the host operating system’s kernel
● Container images package an
application’s run-time requirements
● Containers are instances of those images,
typically running a single process per
each container
CONTAINERS, WHAT!?
Containers isolate software from its surroundings.
?
6. 6
● You specify how your applications run,
and Kubernetes keeps instances of it
running for you.
● Scale applications based on resource
consumption
● First release in 2014, using lessons
learned from Google’s Borg
● Red Hat is second largest contributor
after Google itself
KUBER-WHAT-EZE?
Kubernetes, at its core, is a way to orchestrate how your containers run.
7. 7
OPENSHIFT
Kubernetes for the enterprise
● Just running Kubernetes alone is
like using Linux-From-Scratch
instead of your favorite distro
● Promotes best practices and has
already worried about things for
you in advance
● Loaded with tools for a DevOps
philosophy
8. 8
● It could be just VMs!
● It could just be Docker!
● It could be Bare Metal!
But, it’s not the only way!
You can run VNF-Asterisk in plenty of ways, that’s part of how we explore it.
Intersection in Makati City, the Philippines, Wikipedia
10. 10
They’re all over! We have gaps and flexibility
here on purpose. But, there’s certain a number
of gaps that we’re interested in. Some of them
are, from a Kubernetes perspective:
● The kube-proxy doesn’t honor UDP (at
least not the way that we want it)
● Multi-interface support in Kubernetes is
still burgeoning
● We didn’t touch IPv6 with a 10-foot pole
PLEASE MIND THE GAPS!
These technology gaps are part of why we’re exploring VNFs using Asterisk.
"Mind the gap" tile mosaic at Victoria station in London, Wikipedia
12. INSERT DESIGNATOR, IF NEEDED12
Container Orchestration
KUBERNETES
VoIP monitoring and analytics
HOMER
WHAT TECH ARE YOU ROLLING?
Some new -- some classics.
VNF-ASTERISK
Asterisk (w/ Sorcery) +
Controller +
Service Discovery
13. INSERT DESIGNATOR, IF NEEDED13
AND ANSIBLE!
● Agentless configuration management
● Requires only SSH on remote node, and Python
● “Playbooks” defined in easy-to-read YAML
● Excellent documentation!!