1. © 2013 IBM Corporation
Enterprise Cloud with IBM & Chef
#ChefConf 2013
Ann Marie Fred, SmartCloud Designer and Developer, IBM
Michael Elder, Senior Technical Staff Member, IBM

2. © 2013 IBM Corporation1
IBM’s statements regarding its plans, directions, and intent are subject to change or
withdrawal without notice at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general product
direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise,
or legal obligation to deliver any material, code or functionality. Information about potential
future products may not be incorporated into any contract. The development, release, and
timing of any future features or functionality described for our products remains at our sole
discretion.
Please note
Performance is based on measurements and projections using standard IBM benchmarks in
a controlled environment. The actual throughput or performance that any user will experience
will vary depending upon many factors, including considerations such as the amount of
multiprogramming in the user’s job stream, the I/O configuration, the storage configuration,
and the workload processed. Therefore, no assurance can be given that an individual user
will achieve results similar to those stated here.

3. © 2013 IBM Corporation2
In this session:
Our Pain Points: Sound familiar?
SmartCloud Provisioning and Chef – Keep it simple.
SmartCloud Orchestrator and Chef –
Add management and orchestration.
Continuous delivery of a cloud provider.
Starting to drink our own champagne – The rubber hits the road.
SmartCloud Continuous Delivery and Chef – A fully integrated tool chain for
dev/test.
Introducing Weaver
Looking Forward (we have a secret!)
Watch this space!

4. © 2013 IBM Corporation3
Why Transform…Our Pain Points. Sound familiar?
q Huge footprint of physical servers and
unknown virtualised state
q Underutilized hardware: average of
5-9% utilization per server
q Duplication in the capital request and
procurement process
q Long lead time to access additional
servers to service spikes in dev/test
q Development and IT labs had a variety
of tooling from home-grown to matured
implementations
q Teams heavily leveraging hypervisor
mgmt tools, images were everywhere!!
q Badly integrated reporting of defects,
build quality, and production issues
q Backlog of agile release content
coming from dev to test
q Manual (tribal) processes for release
lack repeatability/speed
q Testing run on simple environments
missing production issues
Reduce capital expense
and maximize existing
investment
Standardize &
Automate to drive Agile
Development and
Innovation
Optimize the Agile
development benefit by
using DevOps
principles

5. © 2013 IBM Corporation4
Make it easy to consume Chef on IBM SmartCloud
SmartCloud Provisioning & Chef

6. © 2013 IBM Corporation5
SmartCloud Provisioning and Chef – Keep it simple.
• Make it easy
• Use Chef
• Use IBM’s
Virtual System
Patterns
• Provide DND
interface for
creating new
patterns
• Support the IBM
Cloud Providers

7. © 2013 IBM Corporation6
Search & Download from the Community

8. © 2013 IBM Corporation7
Generate Script Package for the Chef Role

9. © 2013 IBM Corporation8
Create a Virtual System Pattern and Add Script Packages

10. © 2013 IBM Corporation9
Deploy a Multi-node Pattern

11. © 2013 IBM Corporation10
Add management and orchestration
SmartCloud Orchestrator & Chef

12. © 2013 IBM Corporation11
SmartCloud Orchestrator Chef Toolkit

13. © 2013 IBM Corporation12
Enable Better Collaboration for the Enterprise

14. © 2013 IBM Corporation13
Example Approval Process in SCO

15. © 2013 IBM Corporation14
Use Chef to make us better
Using Chef for Our Projects

16. © 2013 IBM Corporation15
Provision Test
Environment in Cloud
Deploy App from dev to
test environment
Configure Middleware
Orchestrate Functional
Performance, Security
and Integration Tests
Provision development
environment in Cloud
Build Automation
Unit Test Orchestration
Package & Release
Deliverables
Smoke Test Orchestration
Deploy Release
Deliverables to
production environment
Orchestrate smoke test
for production readiness
Provision staging
Environment in Cloud
Orchestrate User
Acceptance Tests
Development Testing Staging Production
Con$nuous
Delivery
Important to drink our own champagne
Goals for SmartCloud Orchestrator dev/test

17. © 2013 IBM Corporation16
The Goal
Enable component teams to develop their code in a
modular manner while continuously integrating and
validating the end-to-end functional and non-functional
quality of the product.
We needed:
• Running, testable software.
• Build results we can trust.

18. © 2013 IBM Corporation17
Our Delivery Pipeline – Multi-Platform Product Delivery

19. © 2013 IBM Corporation18
Component Delivery Process – Multi-Geo & Timezone"
VIL Dev"
Write code"
SCUI Dev"
VIL Code"
SCUI Code"
Write code"
VIL Component"
SCUI Component"
VIL component build"
SCUI component build"
(Component) BVT" CVT"
Pass! Pass!
Fail! Fail!
Pass! Pass!
Fail! Fail!
(Component) BVT" CVT"
Product Driver"
SCO Product Build"
On to Integration!"

20. © 2013 IBM Corporation19
Integration Delivery Process"
Product Driver"
(Product) FVT"
SVT"
PVT"
Gemini"
Product Release"
Pass + Feature Complete!
(Product) BVT"

21. © 2013 IBM Corporation20
Gemini Deployment
• Jenkins jobs to publish the approved component builds to the Chef
Server
• Trigger chef client runs to drive deployment
• Kick off test automation and report results
Continuous
Deployment
Our Delivery Pipeline: Continuous Deployment

22. © 2013 IBM Corporation21
Help Enterprise Customers with Continuous Delivery
SmartCloud Continuous Delivery
& Chef

23. © 2013 IBM Corporation22
Implement delivery pipeline with IBM SmartCloud Continuous Delivery
Input changes, track, deploy, test and report
Version and
track delivery
assets
Provision
environment
Deploy and
configure
application
Run
automated
tests
Report
Continuous Delivery Pipeline
Development
Code
Change,
Unit tests
Feedback
on Change
Test
App
Change,
Auto Test
Test
Results
Operations
Environment
Patterns
Release
dashboards

24. © 2013 IBM Corporation23
Streamline Delivery
23
Test
Automation
Production
Configuration
(Code/Scripts)
Deliver Changes
Virtual Patterns
Best Practice
Workflow Automation
Repository Private Cloud
Manage
Deliverables
Provision
Environment
Verify
Changes
Monitor &
Maintain
Deliver Changes, Manage Deliverables, Provision, Test, Dashboard, Monitor

25. © 2013 IBM Corporation24
Example:
Pa#ern
for
HelloWorldEnvironment
# topology with an identifier!
topology(:hello_world_env) {!
name 'Hello World Environment'!
description 'Hello World JSP app on a single node' !
!
# Provider responsible for provisioning nodes within the topology!
provider :systemz, :url => 'https://urltoservices[ZOSMF?]’!
!
# A web server hosting the hello world application component!
node (:app_server) {!
# The node is provisioned using the image identifier by the provider – what does this mean for Z?!
provider :image => ’websphere_liberty-1.0’!
!
# The Hello World component to be provisioned with key properties!
component(:hello_world_app) {!
name “Hello World Application”!
description “Provides an embedded Jetty with a hello world web application”!
property :asset_id => 'hello_world_app'!
property :asset_version => '2.0.3'!
}!
!
# Automation defined to provision the Hello World app using property values from within
# the topology!
chef_automation (:hello_world_app_role) {!
role 'webapp_role'!
property :port => 8080 !
property :context_root => '/'!
property :war_archive => "http://asset-lib.ibm.com/oslc/#{hello_world_app.asset_id}_#!
{hello_world_app.asset_version}.war”!
} !
}! 24
Describe each node in the
pattern
Describe components & their
properties within the node
Bind to Chef Roles
concept
IBM Confidential

26. © 2013 IBM Corporation25
Example: Pattern for JKE 2 Node Environment
import “web_platform.weaver” # Pattern for Platform!
import ”jke_app.weaver” # Pattern for Application!
!
topology (:qa_environment) {!
name ”Integration Testing Environment"!
description "JKE App on two node IWD pattern”!
!
use :jke!
use :qa_platform!
!
# Realize application nodes onto pattern nodes!
realizes jke.app_server => qa_platform.tomcat_server!
realizes jke.db_server => qa_platform.mysql_server!
!
# Environment specific properties !
property :build_tag => ”TODO", :description => "Build id from build system”!
!
# Set properties for the infrastructure node (excerpt)!
qa_platform.name = “JKEBanking_#{build_tag}”!
!
app_server.hello_world_app_role.port = 9080!
!
!
# Override other values in any of the application or pattern topology (if needed)!
jke.app_server.web_app.context_root = “/”!
}!
jke app
(Logical App)
QA
Environment
web_platform
(Cloud
Infrstracture)
At
this
layer,
we’re
se8ng
proper;es
and
binding
some
dependencies,
but
not
a
lot
of
detail
on
how
to
realize
the
running
environment
25
IBM Confidential
Composable
language
–
factor
our
app
&
plaEorm

27. © 2013 IBM Corporation26
Ruby
API
&
Command
Line
Interface
!
!
# Ruby code for deployment (!
e = Weaver::Environment.new(“hello_world_env.weaver”)!
e.deploy # can be done via Command Line Interface or Ant tasks as well)!
!
!
!
!
!
!
# Get hostname, port, and context from running Environment!
hostname = e.app_server.hostname!
port = e.app_server.hello_world_app_role.port!
context = e.app_server.hello_world_app_role.context_root !
puts http://#{hostname}#{context}:#{port} # prints the web app url!
26
Translates
the
paKern
into
a
series
of
API
calls
to
the
underlying
provider
(like
OpenStack)
IBM Confidential

28. © 2013 IBM Corporation27
Looking Forward

29. © 2013 IBM Corporation28
UrbanCode improves software delivery enabling continuous release
and deployment via Application Release Automation (ARA)
Drive down cost. Reduce the amount
of manual labor, resource wait-time,
and rework
• Push-button deployments improve productivity
of developer and operations staff
Speed time to market. Increase frequency
of software delivery
• Automated software release and deployment
reduces errors
• Built-in best practices
Reduce risk. Deliver higher quality application
releases with increased compliance
• End-to-end transparency, auditability
and reduced time to feedback
Enabling clients to more rapidly deliver mobile, cloud, big data and traditional
applications
28
Application Blueprint
IBM Confidential until April 22, 2013

30. © 2013 IBM Corporation29
Watch this space!
We are investing a great deal of effort into using Chef and continuous
delivery ourselves, and making it easier for our enterprise customers to
use them as well.
Read the Enterprise DevOps Blog on developerWorks:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/devops/
Learn about SmartCloud Continuous Delivery:
https://jazz.net/products/smartcloud-continuous-delivery/
Tips on making automated tests faster: Enterprise DevOps Blog,
Making Your Automated Tests Faster
Visit us at our Ped!

31. © 2013 IBM Corporation30
Acknowledgements and Disclaimers:
© Copyright IBM Corporation 2013. All rights reserved.
§ U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
§ Please update paragraph below for the particular product or family brand trademarks you mention such as WebSphere,
DB2, Maximo, Clearcase, Lotus, etc
IBM, the IBM logo, ibm.com, [IBM Brand, if trademarked], and [IBM Product, if trademarked] are trademarks or registered trademarks
of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked
terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S.
registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be
registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml
If you have mentioned trademarks that are not from IBM, please update and add the following lines:
[Insert any special 3rd party trademark names/attributions here]
Other company, product, or service names may be trademarks or service marks of others.
Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all
countries in which IBM operates.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are
provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or
advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this
presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages
arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is
intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering
the terms and conditions of the applicable license agreement governing the use of IBM software.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they
may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these
materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific
sales, revenue growth or other results.

32. © 2013 IBM Corporation31
SCD Artifact Library
(RAM)
Virtual System
IBM SmartCloud Provisioning
(cloud console)
Jazz Build
Engine(s)
31
Deliver
changes
Request
delivery
Post results
Publish
packages
Request
pa:ern
deployment
Provision
pa:ern
Retrieve
packages
31
Rational Team Concert
client
SCD Client Ext
Rational Team Concert
server
SCD Server Ext
Configure
application
Rational Quality Manager
Verify
configured
application
Request
automated
verification
1. Developer delivers
application or configuration
changes
2. RTC triggers delivery
request
3. Worker services request –
build/package of
application & automation
4. Worker publishes
application & automation
packages
5. Worker requests pa:ern
deployment in cloud
6. PaDern provisioning
triggers (a) package
retrieval and (b) package
execution using Chef Solo.
7. Worker requests automated
verification through RQM,
which triggers automated
tests
8. Worker reports results back
to RTC