The document discusses various approaches to application development on OpenStack including doing it yourself with open source tools (DIY), using configuration management tools to gather automation tools into a management layer (Mantl), and adopting standards and components through Platform as a Service tools (Cloud Foundry). It provides examples of tools for infrastructure as code (Heat), container orchestration (Docker), and describes the basic flow of application deployment on Cloud Foundry including using its open source software plus commercial modules. The goal is to help development teams focus on application delivery rather than underlying OpenStack configuration and management.

1. Application Development
on Metapod
Pioneers, Settlers, and Town Planners
Steve Watkins

2. IT Operations spends
75% of their time
making OpenStack
work.
DIY OpenStack Cloud
Collaboration
Configuration Management
Source/Image Control
Working Environment
Continuous Integration
IT Operations spends
25% of their
Integrating Tool for
Development Team

3. Metapod Allows Customers to Focus on Application
Delivery…Not on OpenStack
… Delivered as a Service
OpenStack and AWS APIs
OpenStack Unified CLI
HA Service Orchestration
Hardware
Networking
Computing Networking Storage Identity
Dashboard
Cisco Metapod Private Cloud Platform
 24x7 Cloud Operations and Support
 SLA Guarantees
 Monitoring and Error Detection
 Platform and Security Updates
 Instant Provisioning
 Open, well-documented APIs
 Integration with existing tools
 API-Driven Instant provisioning
Advanced Operational Support

4. IT Value –
• 75% Focus on DevOps
Methods, Tool
Integration, Image and
Security on top of IAAS
• 25% on Monitoring,
Governance Capacity
Management
Innovation Collaboration
Configuration Management
Source/Image Control
Working Environment
Continuous Integration
Cisco Metapod IAAS – Compute, Networking, Storage
Cisco Value - Stability
and Availability
Consumed “Infra-as-a-
Service”
Metapod Cloud
Administration
Operation

5. Pioneers, Settlers and
Town Planners
5

6. From Simon Wardley’s blog
If you really want bimodal then you'll need to give
something up…
http://blog.gardeviance.org/2015/10/if-you-
really-want-bimodal-then-youll.html

11. What does this mean for
Application Development?
13

12. DIY tool. Open source,
Git Hub source code,
lots manual delivery

13. Do It Yourself Tools –
Heat
15

14. Many ways to hit Infrastructure as Code
heat_template_version: 2013-05-23
description: Simple template to deploy a two compute
instances
resources:
my_web_instance:
type: OS::Nova::Server
properties:
key_name: Skunkworks_key
image: Cirros.0.3.1.raw
flavor: m1.small
networks:
- network: demo1-1029
my_DB_Instance:
type: OS::Nova::Server
properties:
key_name: Skunkworks_Key
image: Cirros.0.3.1.raw
flavor: m1.medium
networks:
network: demo1-1029

15. Demo
17

16. Gather these tools into a
management layer to
simplify automation

17. Organizing Delivery -
Mantl
19

18. Containers + Schedulers + Production Tooling +
Operators + Documentation = Container Stack
Container
Linux Kernel
Host / VM 1 Host / VM 2 Host / VM 3
Linux KernelLinux Kernel
Docker Engine
ContainerContainer
Docker Engine Docker Engine
Container Scheduler (Distributed, Clustered) API
Linux Kernel
Host / VM 4
DB
Docker Engine
Terraform – Provision & Configure VM’s in IaaS
Ansible, puppet, chef, configuration management for you VM’s
Sensu, Nagios, collectd, syslog, cadvisor (collect container stats)
ELK Stack
People (Ops) Documentation
A lot of the ‘DevOPS’
tooling/movement assumes
this stack is consumed ‘as a
Service’ from the cloud.
If you need containers on
prem and/or cross-cloud (no
lockin), you’ll need an open
container stack.
People (Ops)
Container Stack
DevOps (development teams)

19. Mantl Stack
21

20. Demo
22

21. Adopt standards
components and
polidies, which leads to
PaaS tools

22. Industrializing AppDev-
Cloud Foundry
24

23. 26
Open source, forms the
base
Commercial value
added modules

24. 28

25. Basic Flow of Deployment
29

26. Demo
30

27. Summary
31

28. Adopt standards
components and
policies, which leads to
PaaS tools
Gather these tools into a
management layer to
simplify automation
DIY tool. Open source,
Git Hub source code,
lots manual delivery

29. 33

30. • BRKCLD-2503 - Cloud Network
Automation with OpenStack Neutron
You might also be interested in…
34