Downloaded 88 times
Uploaded byIBM Rational software
Deployment module slides
This document provides an overview of deployment tasks in UrbanCode Deploy v6.1, including examining inventory, creating snapshots, requesting deployment processes, deploying to environments, examining logs, and running reports. Snapshots capture component versions and configurations for deployment. Environments are sets of resources hosting applications, and their inventories can be compared. Deployment and security reports contain historical information.
More Related Content
Deployment module slides
- 1. © Copyright IBMCorporation 2015 Essentials of UrbanCode Deploy v6.1 Deployment
- 2. 2 © CopyrightIBM Corporation 2015 Module overview After completing this module, you should be able to complete these tasks: Examine Inventory Create Snapshots Request a deployment process Deploy to an environment Examine logging Run reports
- 3. 3 © CopyrightIBM Corporation 2015 Deployment: Inventory UrbanCode Deploy retains an inventory and history for environments and resources Compliancy shows whether actual component inventory matches expected inventory Snapshots are known working sets of components Shows which component versions are deployed on the environment Shows what version of properties were used for deployment
- 4. 4 © CopyrightIBM Corporation 2015 Deployment: Inventory Inventories between environments can be compared 1. 2. 3. File and configuration differences can also be viewed here
- 5. 5 © CopyrightIBM Corporation 2015 Deployment: Inventory compliancy Fresh environment - Mapped to some resource, but nothing has been deployed
- 6. 6 © CopyrightIBM Corporation 2015 Deployment: Inventory compliancy Deploy 1.0 of WEB and DB - Since no resources have any inventory, we target all of them - As soon as deployment begins, we set desired inventory for the environment
- 7. 7 © CopyrightIBM Corporation 2015 Deployment: Inventory compliancy Deploy 1.0 of WEB and DB - Since no resources have any inventory, we target all of them - As soon as deployment begins, we set desired inventory for the environment
- 8. 8 © CopyrightIBM Corporation 2015 Deployment: Inventory compliancy Failure! - DB worked, but one of the web machines was down - Environment is shown as “noncompliant” - Two machines have “actual inventory” due to successful deployment
- 9. 9 © CopyrightIBM Corporation 2015 Deployment: Inventory compliancy Retry - Deploy the same thing, but it checks inventory first (Only resources missing the desired inventory)
- 10. 10 © CopyrightIBM Corporation 2015 Deployment: Inventory compliancy Success!
- 11. 11 © CopyrightIBM Corporation 2015 Deployment: snapshots Creating a Snapshot Component Versions 1 1 2 2 3 3 321Web Mid. Code DB Snapshot 3 2 1 Mid. Config 1 2 3 3 Snapshot Deployment ENVSnapshot 3 2 1 WEB HOST MID HOST DB HOST 2 1 1 3 2 X 3 3 1 Snapshots are collections of component versions and configuration •Typically taken after successful testing has been completed on an non- production environment, then can be deployed to other environments •Useful for automation, auditing, and visibility •Can be compared with other snapshots •Snapshot deployment can be previewed in an environment
- 12. 12 © CopyrightIBM Corporation 2015 Process request When you have a snapshot you select the environment to deploy to and select the Process to use for the deployment. It may be the same Process used to deploy to another environment.
- 13. 13 © CopyrightIBM Corporation 2015 Environments • User defined set of resources that host an application. • Environments have different topologies • Environments are assigned to specific applications • Approvals are assigned to specific environments Note: UrbanCode Deploy maintains an inventory of every artifact that is deployed to each environment and tracks the differences between them..
- 14. 14 © CopyrightIBM Corporation 2015 Comparing environments • Select the environment to compare, click save and the environment comparison list opens. The component versions in each environment is shown. • You can compare differences between environment properties. • You can compare differences between environment files.
- 15. 15 © CopyrightIBM Corporation 2015 Output log • Server output is written to the server_install_directory/var/log/deployserver.out log file. • You can open the file directly or access it from the UI (Settings > System > Output Log).
- 16. 16 © CopyrightIBM Corporation 2015 Reports • Deployment reports - contain historical information about deployments. Data can be filtered in various ways and reports can be printed and saved. In addition, you can save search criteria for later use. • Security reports - provide information about user roles and privileges.
- 17. 17 © CopyrightIBM Corporation 2015 Module summary In this module you learned: Examine Inventory Create Snapshots Request a deployment process Deploy to an environment Examine logging Run reports
Editor's Notes
- #4 When you deploy what you have in your application it becomes your standard of what you want. If a component didn’t make it to an environment then it will not show compliancy. Components get added to an inventory when the application is deployed. If everything went well it will be in compliance, if it didn’t you will know. You can have properties on components and properties on componnent resources. On resources you can have properties on them also. You could have changed the properties on a component. Component properties are things that are consumed by component processes that could be relative to other components. Component properties could be things about artifacts. Inventory tracks all the components that are there. You could have components there that are not from snapshots. It tracks components that you tried to deploy. You see the inventory for each environment.
- #5 This is what you examine before you create a snapshot.
- #6 Two versions of the web component here. You created environment, resource group, there is no inventory yet because nothing is deployed. The resource is the abstract mapping of the target. It’s an abstract object that points to a physical machine.
- #7 The language is a bit confusing. It’s talking the actual deployment target which is mapped to a resource. When is inventory set? Not when you set up the environment, the inventory is not set up yet. You must run deployment tto get inventory -that’s when it sets the compliancy.
- #9 Resource describes where the deployment is going. It just identifies the computer target.
- #13 As environments get more critical you could have differences in a final production environment. Take snapshot of your final test environment or final production environment. You move the snapshot from test to production and you have a problem, you go back to the snapshot you have of production. So you always have a baseline snapshot of what was working in production.
- #14 You cannot create an environment naked on it’s own it is always part of an application. An application has the whole lifecycle in it usually. It contains all the components that you are worried about. You might have an application for every business unit or every application.
- #15 This is assuming the environment are all part of the same application. You can’t compare environments from different applications.
- #16 This is what you use to troubleshoot a deployment.
- #17 Reports are good for showing how long things took. If you have performance issues reports are good for sorting it out. Security reports gives you rosters of what teams are assigned to different componnts, and what teams are assigned to different environments. Reports could show what roles or users, or teams could do what. Reports are good for administrators.