Hi,
Recently I've been looking at supporting our technology owners in handling lifecycle management of hardware and software in relation to our business applications. We're also in the process om moving to the common service data model.
We have discovery running on our compute infrastructure. We also have SAM Foundation.
Our application services are manually created, and encapsulates the applications CIs created by Discovery. By that I mean things like DB instances, weblogic servers, IIS instances, tomcat instances etc - classes extending cmdb_ci_appl.
These application CIs are running on servers which have software installations, populated in the cmdb_sam_sw_install table by Discovery.
Now when I'm looking at software product models, they are set via discovery models by SAM. However, the application instances created by Discovery, extending the cmdb_ci_appl table, have no software models. Discovery does not match these to models when inserting them. Sometimes they are related to an "unkown" model, but these seem to be version agnostic. Two IIS servers with different version have the same model. This means we cannot use these models to keep track of lifecycles.
Looking to APM, there are functionalities to iterate through the infrastructure CIs supporting the application service and connect all software models of software installations (cmdb_sam_sw_install) for these servers to the application service (retreived software models related list on the application service form). But in my mind that is just one side of the coin. That represent the software installed on the infrastructure, but not the operational application CIs that we have specifically included in the application service. These application CIs have their own version, so they should be covered by lifecycles management via software models, right?
Basically I am missing the orange relationship in this image below. Has anyone else figured this out? I would expect Discovery to relate the application CIs to a model the same way it does with software installs.
Has anyone managed to implement this via a custom sensor or anything like that?
