|
CMDB - Software CIs and Versions
We want to track what versions of CIs are installed where obviously, and not just in production.
So for instance, we have software CI entered as xyz Version 1.0 installed on server CI abc and efg.
There is only one instance of the software CI entered just to be clear not two, one CI that has a relationship built between the two above servers (abc and efg).
The a new version of software CI xyz has been developed (in-house) due to some bugs/defects and they now want to deploy it into our Testing environment which server abc supports.
An RFC is submitted and reviewed to ensure software has been tested properly, release notes are included, and the the users in the testing environment are willing to receive the new software xyz version 1.1 at the specified time. The RFC gets approved and scheduled.
For us, this is a new CI called xyz version 1.1. We now have to remove the relationship from the software CI xyz 1.0 from server abc as this is now being replaced by xyz 1.1. But software CI abc 1.0 still exists as it has a relationship with server CI efg (production).
Does this seem like a reasonable approach to handle this scenarion? The problem we have is managing those relationships. We are trying to have a "magic" button to just copy the older version of the CI with the new version and replace just those relationships to where its being installed.
Just curious is others have gone down this path.
Again, thanks for your time and feedback.
|