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
Next revision		Previous revision
Next revisionBoth sides next revision
2_x:datamodel:teemip_cmdb [2020/08/11 10:37] – [Configuration Management Data Base] cnaud2_x:datamodel:teemip_cmdb [2023/09/15 15:25] – [CMDB - Configuration Management Data Base] 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 and Locations) and objects that are specific to network management (Domains, AS numbers, etc). Persons and Teams are also defined in this module.+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.
  
 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 13: Line 13:
 | [[2_x:datamodel:teemip-virtualization-mgmt|Virtualization Management]] | Virtual Machines, Hypervisors, Farms are defined in this module. You don't need to install this module if you don't want to managed virtualized infrastructures. | | [[2_x:datamodel:teemip-virtualization-mgmt|Virtualization Management]] | Virtual Machines, Hypervisors, Farms are defined in this module. You don't need to install this module if you don't want to managed virtualized infrastructures. |
  
-==== Linking IPs to CIs ====+==== 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:
  
Line 23: Line 23:
 </note> </note>
  
-More details can be found in the [[2_x:datamodel:ip-addresses#ip_addresses|wiki page]] dedicated to IP addresses. +More details can be found in the [[2_x:datamodel:ip-addresses#links_between_ip_addresses_and_cis|wiki page]] dedicated to IP addresses. 
-==== Obsoleting CIs ====+==== 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. 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.
  

Page Tools