OTRS ITSM Config Item Change Management

Moderator: crythias

Locked
pds
Znuny newbie
Posts: 2
Joined: 11 Nov 2010, 23:02
Znuny Version: 2.4.7 +ITSM

OTRS ITSM Config Item Change Management

Post by pds »

I need a little help trying to apply otrs itsm...

For example I have 3 servers alpha, bravo, charlie each running a service or appliance eg apache2. I want to track the version and config of apache2 used and be able to pull up a list of servers running the current config, those still running the old config and those running a testing config.

Should I create a CI called apache2 config, and 3 CI's one for each server and then link server CI to the service config CI. If so then how do I apply versions of apache2 config to each server?
Or should I create each version of apache2 config as a separate CI, and then unlink old version and link new version as I complete the Change for a particular machine?

I feel I am missing something here ....
pds
Znuny newbie
Posts: 2
Joined: 11 Nov 2010, 23:02
Znuny Version: 2.4.7 +ITSM

Re: OTRS ITSM Config Item Change Management

Post by pds »

pds wrote:I need a little help trying to apply otrs itsm...

For example I have 3 servers alpha, bravo, charlie each running a service or appliance eg apache2. I want to track the version and config of apache2 currently used and be able to pull up a list of servers running the current config, those still running the old config and those running a testing config.
Reading and thinking a little more... would it work and be easier to maintain if I:
1) add software and version fields to the computer CI type so that for example I can add the following information to each server:
apache2 vers-a
mysql vers-b
2) make those fields searchable

Then if when I want to modify a config across a number of servers:
1) Create a Change for the whole job, with Work Orders for each machine running the current config.
2) For each Work Order upgrade the machine, change the CI record, close the Work Order
3) When all work orders complete close the change

If there are any problems relating to the config modification they can raised as tickets and linked to the Change or the WorkOrder as well as the Computer CI.

Is that a sane way of using OTRS to track configs across a couple of data centres and a few dozen servers... or is there a better way.

Thanks for your comments or suggestions.
Locked