Red Hat Seminar Think G-Cloud 2014

1. Agile, DevOps, Continuous Delivery and
Lean - How do you tie it all together in
GCloud?
Red Hat Breakout, Think GCloud March 2014
Jeremy Brown - Head of Middleware UK&I, Red Hat
@tenfourty
jeremy@redhat.com
0

2. Let's TALK about the RED
HAT model...

3. Many variations vendors
take on open source
Some enable optimizations for their hardware
Some use open-core to upsell proprietary add-ons
Some invest in focused areas
Some contribute little and soley ship and support

4. AND SOME...
GO ALL IN

6. Shadowman update
Reached $1.33B in FY13

7. Is Open Source a Business
Model?
No
But it is the best DEVELOPMENT model on the planet
Enables collaboration
Gives users flexibility to consume on their terms

8. Recap - Why are we doing
this cloud thing anyway?
Save money
Agility - turn our infrastructure into a PAYG utility model
Lock in
What else?

9. Now we need some
buzzwords
these are key themes that have influenced
my thinking

10. Pets vs Cattle
Pets are given names like pussinboots.cern.ch
The are unique, lovingly hand raised and cared for
When they get ill, you nurse them back to health
Cattle are given numbers like vm0042.cern.ch
They are almost identical to other cattle
When they get ill, you get another one
Future application architectures should use Cattle but Pets with strong configuration
management are viable and still needed

11. Continuous Delivery
https://en.wikipedia.org/wiki/Continuous_delivery

12. DevOps
Where Developers and Operations meet - DevOps
But it's much more than that!
DevOps is about the business
You can't write code with agile and deploy waterfall!
DevOps
Technology Operations
Quality
Assurance(QA)
Developm
ent
(SoftwareEngineering)
https://en.wikipedia.org/wiki/DevOps

13. Lean Startup
It's not just for startups, it's a cultural pattern
Lets ship the MVP (Minimum Viable Product)!
http://theleanstartup.com/principles

14. Infrastructure as Code
The implication of Continuous Deployment, DevOps and Lean is that we need to start
treating infrastructure as code
This will allow us to reduce cycle time
And version our infrastructure

15. Customer's Vision
Red Hat Strategic Advisory Board meeting with CIOs from several of our top
customers:
"They want to describe and automate all their systems and
applications fully with software, from hardware up through
complex, multi-tier apps and services.
They want to provision and manage the lifecycle of
everything (Linux and Windows, private and public clouds) in
an automated fashion.
Several said this was the holy grail for them"

16. Meanwhile...
up in the G-Clouds
We have many G-Clouds
Clouds have different security classifications
Clouds have different APIs - tied to the cloud provider so our apps are not portable

17. Customer's Problem
Red Hat Strategic Advisory Board meeting with CIOs from several of our top
customers:
"One of the problems they have is that everyone is defining
APIs for their own platforms, but they can’t take workloads
from one to another because the APIs they use for
orchestration are different."

18. Tying it all together
How do we "plumb" an application together that has different bits in different
clouds?
My data might be in one cloud
My main application(s) are in a different cloud
I might have a REST API exposed that runs in a third cloud

19. Future: Vision
Top-level application stack “manifest”
defines configuration and relationships of all services which comprise an
application
cross-service (e.g. {NW,St,DB,I,aP,xP,LB,DNS}aaS)
defines how to create/update/delete the entire application, perhaps even
suspend/resume
Enables efficient automatic application creation and deletion
Relevant across dev, QA, prod
An enabler for DevOps
Defrag the Data Centre - free up resources

20. Future: go “meta”
Application stack templates
Example: “give me a disaster resilient JEE app with a preconfigured database”
App manifests move from Word documents to become machine-processable
Automatic reasoning about application estates (auto-scaling, capacity
management, DR analysis, etc.)
Simplification, standardisation and efficiency gains across the board

21. Let me introduce you to an
idea
This might be pie in the sky but there is real
code!

22. OpenStack Heat
Inspired by (and compatible with) Amazon Cloud Formations
Mission:
The mission of the OpenStack Orchestration program is to
create human and machine-accessible services for
managing the entire lifecycle of infrastructure and
applications within OpenStack clouds.
https://wiki.openstack.org/wiki/Heat

23. How it works
A Heat template describes the infrastructure for a cloud application in a text file that
is readable and writable by humans, and can be checked into version control, diffed
etc.
Heat also provides an autoscaling service, so you can include a scaling group as a
resource in a template.
Templates can also specify the relationships between resources (e.g. this volume is
connected to this server).
Heat manages the whole lifecycle of the application - when you need to change your
infrastructure, simply modify the template and use it to update your existing stack.
Heat knows how to make the necessary changes. It will delete all of the resources
when you are finished with the application, too.
It has a pluggable resource adapter framework - plugins are easy to write for your
own cloud

24. Oh and it's open source and
has a strong community
OpenStack Havana Release
837 commits and 67 unique technical authors
OpenStack Icehouse Release
499 commits and 71 unique technical authors

25. Caveat: the project is just
focused on OpenStack
For now...

26. To Summarise
We have a problem with each cloud provider having a different API, so our
applications are still stuck and we can't treat our infrastructure as code
If we can't treat our infrastructure as code we can't do real DevOps, Continuous
Delivery and Lean
We need an open standard and a project that we rally around for application
orchestration
Is this Heat in the OpenStack project?
A Heat resource adapter for every G-Cloud?
Come and join the discussion, we are a community!
email me - jeremy@redhat.com

27. What do these have in
common?
Linux
OpenStack
Hadoop
Rails
MongoDB
Git
Cassandra

28. What do these have in
common?
They are all open source
They are all examples of next-generation IT solutions
They were started by users and developers, not companies

29. Cloud without open source
software?
No Amazon
No Rackspace
No Google
No Yahoo!
No Salesforce.com
No LinkedIn
No Pandora
No Twitter
No Facebook

30. Thank you
This is running on ,presentation OpenShift
the source code is on GitHub
and it was developed in HTML5 with reveal.js
Jeremy Brown @tenfourty
jeremy@redhat.com