Creating CI's and relationships via workflows.

[ajuriol]

Hi Everyone.

We would like to be able to create CI's for example a server and relationships like applications during the processing of a requested item. So typically information would be collected by various teams using various catalog tasks within the workflow. At some point in the workflow we would then commit everything to the CMDB.

If anyone has done something like this and would be kind enough to share their ideas / experiences / script examples that would be greatly appreciated.

Many Thanks

Alberto

[marcus_redfern]

Thanks for that Akash - we had actually managed to work out how to do this already from other Community posts

We're just running a toolset evaluation at the moment rather than dealing with a production instance but we have now managed to pass variables through from the Catalog items into the workflows and scripts to create CI's in the required classes.

Our catalog fulfillment eval scenario was to take a couple of simple questions from a catalog item -

What size server do you want? - Small / Medium / large

Server Name Required - Free text string

It then goes through an approval process (we fired a request approval workflow with a couple of approval routes depending on the value)

and after approval then for each RITM it steps through a number of tasks from an execution plan which

- Raised a standard change for   new server build

- based on the server size selected looks up a more complex set of server attributes (RAM/HDD/CPU count etc.) from "template" CI's in the CMDB

- Creates a new Server CI with the server name required valise and with those attributes in a Pending Build status

- then pass those attributes off to a Jenkins job to build out a server from those attributes

- then on return value of Jenkins job update the CI status to either Installed or Build Failed

all working end to end now and moving on to other eval areas like event management and Service Watch.

Marcus