This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
2_x:datamodel:teemip_cmdb [2023/09/15 15:30] – [CMDB] cnaud | 2_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: | More details can be found in the [[2_x: | ||
+ | ==== 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' | + | TeemIp' |
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. |