This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
2_x:datamodel:teemip_cmdb [2019/06/20 17:19] – [Obsoleting CIs] cnaud | 2_x:datamodel:teemip_cmdb [2023/09/15 15:57] – cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Configuration Management Data Base ===== | + | ====== CMDB ====== |
- | The configuration management data base defines the objects that can be managed inside TeemIp next to the pure IP objects (subnets, addresses, etc.). Widely inherited from iTop, it defines all the physical devices (PCs, Servers, Printers, Network devices, Telephones, etc.) but also some logicals elements (Groups, Application Solutions, Business Processes), software objects (Software Instances, Licenses, etc.), structuring entities (Organizations | + | The **Configuration Management Data Base** |
In order to keep the elements to manage as simple as possible while covering most IT needs, the configuration management domain has been split into 6 modules, including a TeemIp specific one that groups the objects related to network management. | In order to keep the elements to manage as simple as possible while covering most IT needs, the configuration management domain has been split into 6 modules, including a TeemIp specific one that groups the objects related to network management. | ||
^ Module Name ^ Description | ^ Module Name ^ Description | ||
- | | [[2_x: | ||
| [[2_x: | | [[2_x: | ||
| [[2_x: | | [[2_x: | ||
| [[2_x: | | [[2_x: | ||
| [[2_x: | | [[2_x: | ||
+ | | [[2_x: | ||
| [[2_x: | | [[2_x: | ||
- | ==== Linking | + | ==== Linking CIs to IPs ==== |
In TeemIp, many configuration items have one or multiple IP addresses as attributes. These addresses are actually keys toward IPv4 or IPv6 objects managed through the IP Management module. When attaching or detaching an IP address to or from a CI, the following points should be kept in mind: | In TeemIp, many configuration items have one or multiple IP addresses as attributes. These addresses are actually keys toward IPv4 or IPv6 objects managed through the IP Management module. When attaching or detaching an IP address to or from a CI, the following points should be kept in mind: | ||
<note important> | <note important> | ||
- | * When a CI is created or modified, only addresses which status is released or unassigned (ie not allocated nor reserved) are offered, | + | * When a **CI is created** or modified, only addresses which status is **released** or **unassigned** (ie not allocated nor reserved) are offered, |
- | * Status of an IP is automatically changed to allocated when it is attached to a device or to released when removed from it, | + | * Status of an IP is automatically changed to **allocated** when it is **attached** to a device or to **released** when **removed** from it, |
- | * When attached and if enabled through IP settings, the name of the CI is copied into the short name of the IP, | + | * When **attached** and if enabled through IP settings, the **name** of the CI is **copied** into the short name of the IP, |
- | * When detached and if enabled through IP settings, the short name of the IP is reset to an empty string. | + | * When **detached** and if enabled through IP settings, the short name of the IP is **reset** to an empty string. |
</ | </ | ||
- | More details can be found in the [[2_x: | + | More details can be found in the [[2_x: |
- | ==== Obsoleting CIs ==== | + | |
- | TeemIp' | + | |
- | This action is not done when a CI is moved to the specific state but through a background | + | ==== 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 [[2_x: | ||
+ | * Another one will [[2_x: | ||
+ | * A last one will [[2_x: | ||
- | === Configuration === | + | These processes are documented in the [[2_x: |
- | Once TeemIp has been installed, the standard configuration file config-itop.php will show the following section under the modules specific settings: | ||
- | |||
- | <code php> | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ), | ||
- | ), | ||
- | ), | ||
- | </ | ||
- | |||
- | ^ Parameter | ||
- | | enabled | boolean | Should the process run? | false | | ||
- | | debug | boolean | Should the CRON log be enriched with debug information? | ||
- | | 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 | [' | ||
- | |||
- | |||
- | 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: | ||
- | |||
- | <note important> | ||
- | By default, the process is disabled both globally and at organizations level ! | ||
- | </ |