1. © 2013 IBM Corporation Accelerating Product and Service Innovation Leveraging IBM SmartCloud in UrbanCode Deploy Michael Elder, IBM Senior Technical Staff Member mdelder@us.ibm.commdelder@us.ibm.com | http://linkedin.com/in/mdelderhttp://linkedin.com/in/mdelder

2. © 2013 IBM Corporation Accelerating Product and Service Innovation Agenda  How does Cloud enable DevOps? Software Defined Environments enable complete systems to be defined in a wholly repeatable way  Enabling cloud patterns for consumption in UrbanCode Deploy  Preparing reusable infrastructure in UrbanCode Deploy Resource Template  Preparing bindings between applications and reusable infrastructure Application Blueprint

3. © 2013 IBM Corporation Accelerating Product and Service Innovation Plan / MeasureDevelopment / TestRelease / DeployMonitor / Optimize Scaled Reliable Repeatable Practiced DevOps Maturity Model Define release with business objectives Measure to customer value Define release with business objectives Measure to customer value Plan and source strategically Dashboard portfolio measures Plan and source strategically Dashboard portfolio measures Link objectives to releases Measure to project metrics Link objectives to releases Measure to project metrics Automate problem isolation and issue resolution Optimize continuously Automate problem isolation and issue resolution Optimize continuously Improve continuously with development intelligence Test Continuously Improve continuously with development intelligence Test Continuously Manage environments through automation Provide self-service build, provision and deploy Manage environments through automation Provide self-service build, provision and deploy Monitor using business and end user context Centralize event notification and incident resolution Monitor using business and end user context Centralize event notification and incident resolution Deliver and build with test Centralize test management Link lifecycle information Deliver and build with test Centralize test management Link lifecycle information Plan departmental releases and automate status Automated deployment with standard topologies Plan departmental releases and automate status Automated deployment with standard topologies Optimize applications Use enterprise issue resolution procedures Optimize applications Use enterprise issue resolution procedures Deliver and integrate continuously Manage data and virtualize services for test Deliver and integrate continuously Manage data and virtualize services for test Standardize and automate cross-enterprise Automate patterns-based provision and deploy Standardize and automate cross-enterprise Automate patterns-based provision and deploy Document objectives locally Manage department resources Document objectives locally Manage department resources Monitor resources consistently Collaborate Dev/Ops informally Monitor resources consistently Collaborate Dev/Ops informally Manage Lifecycle artifacts Schedule SCM integrations and automated builds Test following construction Manage Lifecycle artifacts Schedule SCM integrations and automated builds Test following construction Plan and manage releases Standardize deployments Plan and manage releases Standardize deployments Industry norm

4. © 2013 IBM Corporation Accelerating Product and Service Innovation 4 Release & Deploy Automation Deployment of Applications across Environments Applications are managed for deployment Components from the app Specific versions of the Components’ artifacts are deployed Compliancy keeps track of whether the actual versions matches the expected Each Component knows its relevant deployment processes Compare versions across environments and define Snapshots of known working sets of Components View deployment requests against the environment

5. © 2013 IBM Corporation Accelerating Product and Service Innovation Improve Delivery Lifecycle with Software Defined Environments SCM Build Automation IBM Endpoint Manager QA PROD Provision platformExecute application deployment and manage settings across environments Patch/update Publish build Pull changes SmartCloud Orchestrator Platform Config Management Environments Deploy early and often to ensure higher quality and faster releases using repeatable, reliable, and managed automation DEV IBM PureApplication System

6. © 2013 IBM Corporation Accelerating Product and Service Innovation IBM UrbanCode Deploy Blueprint Application Resource Template Continuous Delivery to Cloud  Capture cloud pattern to be used for creating an Environment  Incremental deployment of application builds to cloud environments  Map the application to multiple cloud patterns The freedom to provision a version of a full stack or incrementally deploy an application version into an already provisioned environment Environments | Processes | Configurations Create env from pattern Deploy app QA PROD DEV Import pattern

7. © 2013 IBM Corporation Accelerating Product and Service Innovation Understanding Environments in 4.x  uDeploy 4.x used the notion of discrete Environment(s) within an Application  Each Environment declared its “Resources” and “Component Mappings”

8. © 2013 IBM Corporation Accelerating Product and Service Innovation Understanding Environments in v6.x  UrbanCode Deploy v6.0 introduces a global Resource hierarchy  Resources can be organized into groups for your Lines of Business, Applications, Environment classes (Dev, QA, Cert, Prod, etc)  Component Resources exist in the tree and Component versions are matched to the appropriate resource when deployed Entire resource tree is available, organized into top- level groups Agent resources represent running agents on live hosts Component resources represent where Components are deployed Multiple application components can be placed on the same node in the resource tree

9. © 2013 IBM Corporation Accelerating Product and Service Innovation What’s a Component Resource?  Components capture Process and Versions –Automation processes know how to deploy the component, undeploy the component, or any repeatable tasks relevant to the Component –Versions know about the artifacts which are produced by the build or third parties  Component Resources are prototypes for real Resources –Place these in the Resource Tree wherever a matching Component Version should be deployed –Replace specific Component mappings Component Version Process JKE DB v1.0.2 JKE Tomcat v6.0.2 JKE War v3.0.10

10. © 2013 IBM Corporation Accelerating Product and Service Innovation Preparing the Cloud – Define the Pattern  IT Specialist defines a new pattern in the cloud (using the SmartCloud web interface)

11. © 2013 IBM Corporation Accelerating Product and Service Innovation Preparing the Cloud – Update the Script Package on each Part  Import the IBM UrbanCode Agent Script Package into the catalog  Add the agent to each image part in the virtual system pattern

12. © 2013 IBM Corporation Accelerating Product and Service Innovation Prepare Reusable Infrastructure in UrbanCode Deploy  Release Manager “imports” information about the pattern into UrbanCode Deploy –Creates a new “Resource Template” which is a subtree with information from the pattern –Each image in the pattern becomes a potential “Agent prototype” to run behavior on behalf of a deployment process Define Connections against the cloud Select an available Virtual System Pattern Resource Templates are global, available for all Applications

13. © 2013 IBM Corporation Accelerating Product and Service Innovation Prepare Reusable Infrastructure in UrbanCode Deploy – Results  Properties for the Cloud Pattern are read and remembered for future requests

14. © 2013 IBM Corporation Accelerating Product and Service Innovation Prepare Reusable Blueprints in UrbanCode Deploy  Release Manager defines a new “Application Blueprint” using this Resource Template –Binds information about the application and component placement to the pattern Blueprints are descriptions of an environment which can be instantiated, built on Resource Templates and binding Components from the Application No live “agent”

15. © 2013 IBM Corporation Accelerating Product and Service Innovation Creating New Environments with Application Components  Release Manager or Lead (Developer/Tester) applies the Application Blueprint to create a ready to use Environment (running compute resources) –The Environment is associated with the Application –After the cloud resources are allocated, they continue running and are updated incrementally for new deployments until the Environment is destroyed Environments are running systems which can now be created from a Blueprint, or manually allocated/designed if needed for existing systems Live agent, running on a host in the cloud

16. © 2013 IBM Corporation Accelerating Product and Service Innovation Creating Live Environments in the Cloud – Part 1  Built into the New Environment dialog  Choose a Blueprint and a Base Resource  Leads to additional dialogs to configure Cloud connection and properties for the deployment Blueprints defined within the Application, selected to “seed” the Environment Since we’re creating a new Environment, it needs a home in the Resource Tree

17. © 2013 IBM Corporation Accelerating Product and Service Innovation Creating Live Environments in the Cloud – Part 2 “Where” to deploy this pattern into the cloud – Select a Cloud Group or Environment Profile ** IPAS only supports Environment Profiles Each image part exposes properties that can be overridden by the user

18. © 2013 IBM Corporation Accelerating Product and Service Innovation Support for Chef Solo to configure a Component  Chef is a ruby-based automation platform created by Opscode  Chef Solo runs a local client to “converge” the node which just means execute the automation  We can embed Chef recipes in a Component version, and use properties known to UCD to drive customization of the recipe –Example: replace token with value of database hostname, which will then by used by the recipe to configure the connection Optionally install chef- solo onto the host, or pre-install into virtual image Replace tokens in the *_node.json files which are included in the component artifacts Invoke chef-solo –N to configure the host

19. © 2013 IBM Corporation Accelerating Product and Service Innovation 19 © Copyright IBM Corporation 2013. All rights reserved. The information contained in these materials is provided for informational purposes only, and 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, these materials. Nothing contained in these materials 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. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. www.ibm.com/software

20. © 2013 IBM Corporation Accelerating Product and Service Innovation Additional Material

21. © 2013 IBM Corporation Accelerating Product and Service Innovation The Basics  Application –A logical grouping of deployables –Single unit of management –Self-contained definitions of automation, target environments –Create Snapshots for “good” sets of versioned Components Component – Files or configuration to be deployed, steps to deploy them – Generally mapped to something in an external system – Components are versioned and associated with artifacts – May contain binaries or scripts

22. © 2013 IBM Corporation Accelerating Product and Service Innovation Understanding the World  Understand computing objects as “Resources”  Resources map to Agents  Every OS has an agent, and each agent corresponds to a resource  Child resources can be created to represent logical containers/spaces  Components are mapped onto Resources

23. © 2013 IBM Corporation Accelerating Product and Service Innovation Bringing it together: Environment (v4.x)  Combines resources into a single logical deployment target  Specifies 0+ resources or groups for each component  Good place for environment configuration (database URL, etc)