This webinar discusses the gaps that prevent enterprises from fully automating the DevOps lifecycle and how technologies like Containers and Sandboxes can assist with crossing that chasm.

1. Mind the Gap: Crossing the
DevOps Chasm

3. DevOps

4. • What is the Gap in Enterprise DevOps?
• Why are containers so Darned popular?
• Why are Sandboxes needed?
• What are Sandboxes anyway?
• Closing the DevOps Gaps
• Sandboxes by Quali for DevOps
Agenda

5. Automation Starts Here
The DevOps Lifecycle
Application Release
Automation
(Configuration
Management)
Continuous Integration

6. So, what about containers?

7. I Can code, build, test and deploy on my own laptop!
Developers love them…

8. And run it here, right?

9. Or Here

10. The problem is…

11. Or Worse Yet…

12. Software starts on a developer laptop…
Why does this happen?

13. Containers are like putting a plant into a pot
 They are application centric
They are portable
They can managed and scheduled, even moved
Containers address many DevOps
challenges

14. Each Phase is Like Planting a
Garden!

15. I also need a Sandbox
A Sandbox is a container for
the environment where all
of the different
configurations can be
created
They are environment
centric:
They are flexible
They can be managed and
scheduled
They can be abstract

16. They can be simple or complex
Enterprise Sandbox
My laptop…
Production…

17. • Model the
infrastructure
• Create network
connections
• Describe applications
• Automate setup
• Define processes
• Integrate with DevOps
tools
Sandboxes are built with simple
tools

18. Containers inside of Sandboxes for DevOp
Uber Containers

19. DevOps + Containers + Sandboxes
Closing the DevOps Gap
MonitorOperateDeployReleaseTestBuildCodePlan

20. What is a Cloud Sandbox?
“Personal Replica of a Production
Environment for Automating DevOps”

21. Maybe this would be possible…
A
Sandbox

22. Why Is Cloud Sandbox Different?
PRODUCTION CLOUD
• Deployed for months/years
• Uniform, standardized
• Resources allocated to
applications
• No control over the resources
• Pre-defined
• Now
• Fixed allocation
CLOUD SANDBOX
• Deployed for hours/days
• Non-uniform, changing, evolving
• Resources allocated to users
• User has control over the
resources
• Design your own sandbox
• Now, queued or scheduled
• Contention for resource
allocation

23. CREATE
Sandboxes
DEFINE DEPLOY

24. Sandboxes
Run automatically

25. A Dev/Test Sandbox Example
Cisco Devnet

26. Cisco Devnet

27. Sandbox Blueprint Catalog
Cisco DevNet

28. Sandbox Blueprint Example
Cisco Devnet

29. For the Infrastructure:
• Cloud Sandboxes
• Environment portability
• Environment
consistency
• It is a context for
keeping meta-data
• Automation
• Dynamic multi-tenancy
for Environments
For DevOps Automation
Containers and Sandboxes
For the Application:
• Containers
• App portability
• Packaging
• It is a context for
keeping meta-data
• Automation Enabler
• Dynamic multi-tenancy
for apps

30. • Enterprise DevOps really does
require all of the steps
• Enterprises really do have
phases from Dev to
Production
• Enterprise production
environments are hybrid and
complicated
• Containers alone do not
address all of the gaps
• But Sandboxes help by
complementing containers
and addressing production
environments
Summary

31. • The Sandbox is Coming to DevOps
https://appdevelopermagazine.com/3584/2016/2/10/Cloud-Sandboxes-Are-Becoming-
the-Uber-Containers-for-the-DevOps-Cycle/
• Containers Enable DevOps and Hybrid Clouds, But
Sandboxes Are Also Critical for IT Success
• http://datacenterpost.com/2015/11/containers-enable-devops-and-hybrid-
clouds-but-sandboxes-are-also-critical-for-it-success/
• DevOps, Hybrid Cloud & Sandboxes
http://www.networkcomputing.com/data-centers/devops-hybrid-cloud-
sandboxes/413832201
References

32. Q&A
Joan Wrabetz
Joan.w@quali.com
@varbetz
www.quali.com