1 of 20

OpenShift and OpenStack: Delivering Applications (Better) Together

By Scott McCarty @fatherlinux

1

2 of 20

Why not just use OpenShift?

Why not just use OpenStack?

3 of 20

Exposition & Consumption of Resources

4 of 20

Exposition of Resource

5 of 20

Consumption of Resource

Historically, consuming resources meant running processes (pstree output on the right)
Now consuming resources means running distributed processes in containers across a cluster of systems

This is what OpenShift & Kubernetes is really good at. We don’t necessarily want to schedule an entire VM to run a single process

Old sysadmins used to make jokes that the servers worked fine until we let the developers use them

I think we have finally started to understand that giving developers access to resources is how we build new products that make money and keep us in business
Developer Joke: “Chuck Norris can write infinite recursion functions…and have them return.” (reminds me of a time when I wrote a fork bomb in college and crashed the system that everybody in the lab was using)
Sysadmin Joke: “Chuck Norris’s first program was kill -9.”

6 of 20

Fancy Files

Fancy Processes

Also Fancy File Servers

7 of 20

Load Applications at the Factory, not the Dock

There are several main value propositions to containers

Standardization: instead of loading boxes, bags, crates, barrels, bicycles, pianos, etc, we can now load one unit
Performance: Containers are fancy processes so there is no overhead for virtualization
Intermodal: Package/Load at the factory instead of the dock (New: never mentioned by Docker Inc)

In 1906, it took 45 days to load a ship, coincidentally about the same amount of time it takes to requisition a physical server
Imagine you are loading a bunch of lamps. If you break them on the dock, you have to wait for new ones to arrive. If you load at the factory, you go grab a new lamp and keep loading. Now, with code if something doesn’t work, you can fix it at the factory, on the developers laptop
“It works on my machine” always holds true for Chuck Norris

8 of 20

9 of 20

The Tenancy Scale

Security is about levels of isolation, or tenancy
Back in the day, I used to telnet into a shared webserver in college. Literally, we could all run processes side by side, like a free system in Tron
Now days, sometimes you need an application in two different data centers with affected by different weather patterns or fault lines
The conversation is how much isololation is enough? Walk from left to right

Sometimes a process is enough isolation
Sometimes we need a container. If you are running in a shell in a container, you can run “ps -ef” and you don’t see other people’s processes
Sometimes we need the extra isolation of virtual server
Sometimes a physical server
Sometimes a different rack in the data center
Sometimes a different data center affected by different weather patterns or earchquake fault lines.

10 of 20

Container Patterns

11 of 20

Application Containers

Code: mysqld
Configuration: /etc/my.cnf
Data: /var/lib/mysql
Other stuff :-)

12 of 20

13 of 20

Integration Points

14 of 20

Still Early Days

Interesting work

Installation: Heat vs. Ansible
Identity: Keystone
Resources: heat templates, URLs

Works pretty well

Storage: Persistent Volumes and Cinder Volumes
Network: Neutron Networking
Network: Load Balancer

15 of 20

Traditional Storage

16 of 20

Cloud Storage

17 of 20

Automation at Scale

18 of 20

Demo Time

19 of 20

Conclusion

OpenShift + OpenStack =

Distributed Systems Operating System

Question
???
???
???

20 of 20

Citations

OpenShift on OpenStack Heat Template Work: http://bit.ly/23Zh6l1
Dynamic Cinder Provisioning: red.ht/1qPRqFA
OpenShift Commons Briefing (Mark Lamourine): http://bit.ly/1NwLEDh
Workload and Containerization Characteristics: http://red.ht/1SBw9ql

By Scott McCarty @fatherlinux