IT Operations Management (ITOM)
cancel

Demystifying Data Center Automation (DCA) Suite Operations Portal’s offerings-Series#4.2: New Design

Demystifying Data Center Automation (DCA) Suite Operations Portal’s offerings-Series#4.2: New Design

lazarmi

 This is the continuation of  Demystifying Data Center Automation (DCA) Suite Operations Portal’s offerings-Series#4.1: New Design

 As we said in the previous article where we finished with the Cloud Service Automation “design” and all properties, options have been set, the Offering is available into the Operations Portal, now, we have to revert to the Operations Orchestration flow for some refinements including:

  • Set the list of properties to be queried from CSA (“attachableID” and “attachableType”)
  • Pass the info queried to flow variables to be sure that each action will get the right inputs and the values will not be lost
  • Update CSA’s subscription with the relevant info and finally, to create the OO CP
  • Deploy it into OO Central and run the Process Definition Tool in order to synchronize CSA with all the available OO Flows

After all of these changes were made, will revert to the already created and bound Resource Offering, to add our OO Flow/Process Definition into!

 I hope this guide helps you with the design process between Operations Orchestration's flows and CSA’s Service Design creation. There are opportunities to have refinements and adjustments in order to accomplish the initial desired idea!

 The first thing we have to refine is “Get Artifact Properties” Inputs and Results.

As I said in part 3 of this blog series, that for performance reasons we will query only the properties we’re interested into and not all the available ones (the default behavior).

For that, within “Inputs” tab click on “propertyNames” property and adjust the list of properties:

Fig.31 InputsFig.31 Inputs

 

Within the “Results” tab of the same action, “Get Artifact Properties”, we have to define the results along with the correspondently Operations Orchestration flow variables to be sure that those values will be persisted and reused by the subsequent actions.

Since the result is the form of:

Fig.32 ResultsFig.32 Results

<property_name1>;value1,value2…valueX|<property_name2>;value1,value2…valueX |…|<property_nameY>;value1,value2…valueX

 

 

 

 

 

And the output of the JSP script is the form of:

Fig.33 JSP's outputFig.33 JSP's output

 

 We have to filter it to keep only the needed part of – in our case only the Server’s ID.

To do this, first of all we have to define the results and for each result we have to apply a filter like this:

Fig.34 Results & FiltersFig.34 Results & Filters

 

Testing each filter in part outputs the desired output!

Fig.35 Testing the filtersFig.35 Testing the filters

 The second thing is to refine “Run Communication Test” Inputs and Results.

The default can be observed that nothing has been assigned to any Inputs: 

Fig.36 Run Comm Test - default InputsFig.36 Run Comm Test - default Inputs

 

 As I said, we have to assign from the pool of previously-created OO Flow Variables and then eventually reassign them to other OO Flow Variables for re-usage.

Fig.37 Run Comm Test - InputsFig.37 Run Comm Test - Inputs

To  create a result variable which will be used by the next action “Run Communication Test Job Result”

Fig.38 run Comm Test - ResultsFig.38 run Comm Test - Results

 

The third thing is to refine “Run Communication Test Job Result” Inputs and Results.

Inputs:

Fig.39 Run Communication Test Job Result - InputsFig.39 Run Communication Test Job Result - InputsResults: (you have to press  the “+” sign three times!)

Fig.40 Run Communication Test Job Result - ResultsFig.40 Run Communication Test Job Result - Results

 The remaining steps are to update the Cloud Server Automation’s subscription with the above details and CSA itself too-with the job’s completion.

From the previous steps, it can be observed that three properties were selected in order to update the CSA’s subscription. As a result, our initial flow will suffer a slight modification: two additional “Update Service Component Property” actions will be added to be able to accomplish this.

 Before doing this, to add the other two actions, will set the right “Inputs” for the existing “Update Service Component Property” action and afterwards will copy and paste this action and change only few things!

So, here the “Inputs” for “Update Service Component Property” in order to update the “serverName” information:

*Note: we’ve updated the name of the action to be easier to distinguish between the similar actions/components

 

Fig.41 Update - serverNameFig.41 Update - serverName

 

Once this component has been duplicated to update the other details, our new flow will look like:

Fig.42 OO flowFig.42 OO flow

 

Continuing with the “Inputs” for “Update Service Component Property - serverID” action in order to update the “serverID” information:

Fig.43 Update - serverIDFig.43 Update - serverID

 With the “Inputs” for “Update Service Component Property - agentReachable” action in order to update the “agentReachable” information:

Fig.44 Update - agentReachableFig.44 Update - agentReachable

 

Finally we arrived at the last component which will notify CSA about the OO Flow’s completion in case of a success, “Update Process Instance State – Notify Flow Completion” action.  Here are the “Inputs”: 

Fig.45 Notify Flow CompletionFig.45 Notify Flow Completion

 

The last component  will notify CSA about the OO Flow’s completion in case of a failure, “Notify Error” action, so here are the “Inputs”:

Fig.46 Notify ErrorFig.46 Notify Error

 We are getting closer and closer by the end of our journey, and next step will be to create the Operations Orchestration Content Pack. This is being followed by deploying it into OO Central, synchronizing CSA and OO Central and finally updating our CSA Resource Offering.

Creating an Operations Orchestration Content Pack

Fig.47 Create CPFig.47 Create CP

From the OO Studio, right-click on the project “DCADemo” > “Create Content Pack” > which will result the following CP “DCADemo-cp-1.0.X.jar”

 

 

 

 

 

 

 

To deploy it into OO Central, first we have to login into it*, go to “Content Management” > “Content Packs” > “Deploy New Content”

*update the URL with the right IP

 

Fig.48 Deploy CP into OO CentralFig.48 Deploy CP into OO Central

 

To synchronize CSA with OO central, first we have to update “HPOOInputInfo.xml” with our project’s path “/Library/Exercises/*”

 

“[root@dca201601 /]# cd /usr/local/hp/csa/Tools/ProcessDefinitionTool && ls

CslHPOOInput.xml   HPOOInputSample.xml          OracleInputSample.properties      ProcessEngineInputSample.xml  db.properties          process-defn-tool.log

HPOOInputInfo.xml  MsSqlInputSample.properties  PostgreSqlInputSample.properties  config.properties             process-defn-tool.jar

 

[root@dca201601 ProcessDefinitionTool]# vi HPOOInputInfo.xml

       <ooengines>

  <ooengine name="OO-MACHINE-NAME" … username="admin">

 

<folder path="/Library/IT Operations Compliance/Actions" recursive="true" update="true"/>

<folder path="/Library/Data Center Automation Appliance/Provision Servers/Actions" recursive="true" update="true"/>

<folder path="/Library/Data Center Automation Appliance/Server Management/Actions" recursive="true" update="true"/>

<folder path="/Library/Integrations/Hewlett-Packard/Server Automation" recursive="true" update="true"/>

<folder path="/Library/Exercises" recursive="true" update="true"/>

 </ooengine>”

 

Once the above changes were made, we can start the actual sync process (may take a while):

 

“[root@dca201601 ProcessDefinitionTool]# java -jar process-defn-tool.jar -i HPOOInputInfo.xml -d db.properties

Connecting to Database.................................

Successfully connected to Database.

 

********************************************

Finished importing process definitions from OO flows at https://localhost:8443/PAS/services/WSCentralService

Total number of process definitions created: 1

  List of created process definition(s):

    1: /Library/Exercises/RUN_COMM_TEST_MANAGED

 

Total number of process definitions updated: 0

Total number of process definitions deleted: 0

 

********************************************

Finished importing process definitions from OO flows at https://localhost:8443/PAS/services/WSCentralService

Total number of process definitions created: 0

Total number of process definitions updated: 0

Total number of process definitions deleted: 0

 

********************************************

Finished importing process definitions from OO flows at https://localhost:8443/PAS/services/WSCentralService

Total number of process definitions created: 0

Total number of process definitions updated: 0

Total number of process definitions deleted: 0

 

********************************************

 

Now we’re ready to update CSA’s Resource Offering. To do this we have to switch to the Administration Console > Designs > Sequenced > Resource Offering > HP Server Automation > click on “Run Comm Test” > “Lifecycle” > “Deploying” > “Transition” > “Create New Action” > “OO-MACHINE-NAME (check HPOOInputInfo.xml again for the reason)” > “Next” > choose “/Library/Exercises/RUN_COMM_TEST_MANAGED”> “Create” 

Fig.49 Update the Resource OfferingFig.49 Update the Resource Offering

 

Finally, we can “Checkout” the Offering and “Submit Request”*after all the details have been filled out:

*both operations from the Operations Portal

Fig.50 CheckoutFig.50 Checkout

 

Fig.51 Submit RequestFig.51 Submit Request

 

Checking its execution from OO Central, can see that we’ve missed one required input: “attachableName” 

 

Fig.52 First Design ErrorFig.52 First Design Error

 

To correct this, we have to update “Get Artifact Properties” action to filter the server’s name into “attachableName” OO Flow variable from the already available “attachableID” property.

 

So, the “Inputs” will remain the same

Fig.53 InputsFig.53 Inputs

 

 But for the same “Get Artifact Properties” action, within “Results” we need to add a new variable and all the correspondent filters to output only the name of the server:

Fig.54 Get Artifact Properties - new Results & FiltersFig.54 Get Artifact Properties - new Results & Filters

 

 The “Inputs” for “Run Communication Test” action will look like: 

Fig.55 Run Communication Test - new InputsFig.55 Run Communication Test - new Inputs

 

Next actions will be to:

  • Create a new CP
  • Deploy it into OO Central
  • Checkout and Submit the Request again

 

To monitor and check the execution you have few alternatives:

 

OO central 

Fig.56 OO Central consoleFig.56 OO Central console

 

Fig.57 OO Flow's executionFig.57 OO Flow's execution

 

IT Operator Portal/Administration Console > Operations > Consumer > Run a Communication Test job on an already Managed Server (1.0.0) > Events

Fig.58 IT Operator Portal EventsFig.58 IT Operator Portal Events

 

Operations Portal

Fig.59 Operations PortalFig.59 Operations Portal

 

 Server Automation console:

Fig.60 Server Automation consoleFig.60 Server Automation console

 

 Hooray! Here our journey ends with the hope that you’re really confident in starting a new design from scratch!

 

Don’t forget to leave feedback and share with your friends!

 

Here some quick links for the other series:

 

 

Notes:

  • The OO Content Pack, OO Project and the CSA’s Offering (which contains the Service Design, Resource Offering as well) are attached to this blog (rename it to .zip)

 

 

 

Mihai Lazar
Automate & Orchestrate Solution Architect

*If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
  • infrastructure management
About the Author

lazarmi

Attachments
Comments
Contributor.

How has this process changed since CSA 4.8?