User Tools

Site Tools


2_x:datamodel:teemip_cmdb

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
2_x:datamodel:teemip_cmdb [2023/09/15 15:30] – [CMDB] cnaud2_x:datamodel:teemip_cmdb [2023/09/15 15:52] – [Obsoleting CIs with IPs] cnaud
Line 24: Line 24:
  
 More details can be found in the [[2_x:datamodel:ip-addresses#links_between_ip_addresses_and_cis|IP addresses]] documentation. More details can be found in the [[2_x:datamodel:ip-addresses#links_between_ip_addresses_and_cis|IP addresses]] documentation.
 +==== Automation ====
 +When linking an IP together with a CI, one must insure that both the CI's and the IP's status are consistent. TeemIp provides configurable automation processes to help IP Administrators with that task.
 +  * One will release IPs that are linked to an obsolete CI,
 +  * Another one will allocate IPs that are attached to a production CI,
 +  * A last one will unassign IPs that are no longer attached to a CI.
 +
 +These processes are documented in the
 +
 ==== Obsoleting CIs with IPs ==== ==== Obsoleting CIs with IPs ====
-TeemIp's standard datamodel defines a status for most CIs : implementation, obsolete, production, stock. A conditional behaviour triggered by configuration parameters removes all the IPs attached to CIs that have a specific status (obsolete by default) as well as all the IPs attached to the interfaces of these CIs. These removed IPs are set to to the 'releasedstate.+TeemIp's standard datamodel defines a status for most CIs : implementation, obsolete, production, stock. A conditional behaviour triggered by configuration parameters removes all the IPs attached to CIs that have a specific status (obsolete by default) as well as all the IPs attached to the interfaces of these CIs. These removed IPs are set to to the **released** state.
  
 This action is not done when a CI is moved to the specific state but through a background task that runs, by default, every 1 hour. This action is not done when a CI is moved to the specific state but through a background task that runs, by default, every 1 hour.