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:29] – [Linking CIs to IPs] cnaud2_x:datamodel:teemip_cmdb [2023/09/15 15:31] – [Obsoleting CIs with IPs] cnaud
Line 1: Line 1:
 ====== CMDB ====== ====== 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, Locations, etc...) and objects that are specific to network management (Domains, AS numbers, VRFs, etc..). Persons and Teams are also defined in this module.+The **Configuration Management Data Base** defines the objects (Configuration Items or **CIs**) 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, Locations, etc...) and objects that are specific to network management (Domains, AS numbers, VRFs, etc..). Persons and Teams are also defined in this module.
  
 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.
Line 25: Line 25:
 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.
 ==== 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.