Documentation

User Tools

Site Tools

Trace:
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
Last revisionBoth sides next revision
2_x:datamodel:teemip_cmdb [2023/09/15 15:52] – [Obsoleting CIs with IPs] cnaud2_x:datamodel:teemip_cmdb [2023/09/15 15:57] – cnaud
Line 23: Line 23:
 </note> </note>
  
-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 page. 
 ==== Automation ==== ==== 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. 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, +  * One will [[2_x:datamodel:ip-settings#automatic_ip_release|release]] IPs that are linked to an obsolete CI, 
-  * Another one will allocate IPs that are attached to a production CI, +  * Another one will [[2_x:datamodel:ip-settings#automatic_ip_allocation|allocate]] IPs that are attached to a production CI, 
-  * A last one will unassign IPs that are no longer attached to a CI. +  * A last one will [[2_x:datamodel:ip-settings#automatic_ip_un-assignment|unassign]] IPs that are no longer attached to a CI.
- +
-These processes are documented in the +
- +
-==== 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 **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. +
- +
-=== Configuration === +
- +
-Once TeemIp has been installed, the standard configuration file config-itop.php will show the following section under the modules specific settings: +
- +
-<code php> +
- 'teemip-ip-mgmt' => array ( +
- 'ip_release_on_ci_status' => array ( +
-   'enabled' => true, +
-   'debug' => false, +
-   'periodicity' => 3600, +
-   'status_list' => array ( +
-     'obsolete', +
-   ), +
- ), +
- ), +
-</code> +
- +
-^ Parameter  ^  Type  ^  Description  ^  Default Value  ^ +
-| enabled | boolean | Should the process run? | false | +
-| debug | boolean | Should the CRON log be enriched with debug information? | false | +
-| periodicity | integer | Defines the periodicity of the process, in seconds | 3600 | +
-| status_list | array | IP release process will be applied to CIs with these status | ['obsolete'] | +
  
-When the process is enabled, TeemIp administrator can further decide to activate or deactivate it for each organization. This is controlled through the [[2_x:datamodel:ip-settings|global IP settings]] parameter "Release IPs of CIs that become obsolete".+These processes are documented in the [[2_x:datamodel:ip-settings|IP Settings]] documentation page.
  
-<note important> 
-By default, the process is disabled both **globally** and at the **Global IP settings** level ! 
-</note> 

Page Tools