(r1) IBMQuickDeployerExampleDeployFromBlueprint < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

~~EditAttach~~Printable

TWiki > Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployer > IBMQuickDeployerSetupAndRun > IBMQuickDeployerExampleDeployFromBlueprint

Revision 1 - 2017-12-04 - 20:35:02 - Main.ccarty

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Topic title (use a lowercase style, which is known as "sentence-style" capitalization) <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: Main.ClareCarty<br>
Build basis: CE/CLM 6.0.4+
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

Quick Deployer ships with a set of sample blueprints which are pre-set templates based on the CE/CLM Recommended Topologies. This page describes a method for using Quick Deployer to install CE/CLM environments using these blueprints. 

---++ Standard Topology Blueprints installed by Quick Deployer

Once Quick Deployer is installed, the user can select the Resources tab and explore the available Resource Templates. 

<img src="%ATTACHURLPATH%/resource_temp.png" alt="resource_temp.png" width="800" height="510" />

Select one of the templates and drill down to explore in more detail. 

<img src="%ATTACHURLPATH%/rt_nodes.png" alt="rt_nodes.png" width="799" height="589" />

In the example above, The Departmental Continuous Engineering template is shown. You can *Expand all* to see more detail.

<img src="%ATTACHURLPATH%/agent_prot_tags.png" alt="agent_prot_tags.png" width="1173" height="708" />

As you can see, the applications are distributed over 5 nodes or VMs three of which are Application Server environments. 

---++ How to leverage the Blueprints

The blueprints can be leveraged by connecting the agents - which are installed on the target VMs - to the application environment using a naming convention set up in the Agent prototype.

Taking a slice from the example above:-

<img src="%ATTACHURLPATH%/edit_agent_prot.png" alt="edit_agent_prot.png" width="995" height="87" />

If you edit the agent prototype for each node it will show the naming convention to be used for the target VM names. For instance,

<img src="%ATTACHURLPATH%/ex_agent_prot.png" alt="ex_agent_prot.png" width="513" height="267" />

Here the agent name for the DB server must include the environment name and end in '-db'. 
So if the environment is going to be called win16qd21, the DB server name should be something like win16qd21-db

Similarly, the agent prototypes for the IHS and other nodes:-

     <img src="%ATTACHURLPATH%/ex_agent_prot2.png" alt="ex_agent_prot2.png" width="489" height="245" />

  
     <img src="%ATTACHURLPATH%/ex_agent_prot3.png" alt="ex_agent_prot3.png" width="499" height="249" />

  
     <img src="%ATTACHURLPATH%/ex_agent_prot4.png" alt="ex_agent_prot4.png" width="503" height="249" />

  
     <img src="%ATTACHURLPATH%/ex_agent_prot5.png" alt="ex_agent_prot5.png" width="505" height="249" />

Again if we use win16qd21 as our environment name, this nets out to agent names as follows:-
   * db: win16qd21-db
   * ihs: win16qd21-ihs
   * node 1: win16qd21-os-1
   * node 2: win16qd21-os-2
   * node 3: win16qd21-os-3

If the agents are installed on target VMs using the client from the appropriate UCD server, then they will automatically come online.

<img src="%ATTACHURLPATH%/agents.png" alt="agents.png" width="1070" height="339" />

---+++ 
---++++ VM naming convention

---++++ Environment naming convention


---++ Heading 1

---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]], [[DeploymentWebHome][Deployment web home]]

---+++++!! External links:          

   * [[https://www.ibm.com][IBM]]

---+++++!! Additional contributors: Main.TWikiUser, Main.TWikiUser

<sticky></div></sticky>
   * agent_prot_tags.png: <br />
     

   * agents.png: <br />
     

   * agents_comp.png: <br />
     <img src="%ATTACHURLPATH%/agents_comp.png" alt="agents_comp.png" width="1161" height="785" />

     

   * env_with_blueprint.png: <br />
     <img src="%ATTACHURLPATH%/env_with_blueprint.png" alt="env_with_blueprint.png" width="1197" height="666" />

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.