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
2_x:datamodel:teemip_cmdb [2023/09/15 15:57] cnaud2_x:datamodel:teemip_cmdb [2023/09/15 21:06] (current) – removed cnaud
Line 1: Line 1:
-====== CMDB ====== 
- 
-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. 
- 
-^  Module Name  ^  Description  ^ 
-| [[2_x:datamodel:teemip-config-mgmt|CMDB Core]] | This module is mandatory and covers all the basic building blocks of the CMDB: Organizations, Persons, Teams, Servers, Software Entitites, Groups...| 
-| [[2_x:datamodel:teemip-datacenter-devices|Datacenter Devices]] | This optional module provides support for datacenter related devices: Racks, Envlosures, Power connections and PDUs. | 
-| [[2_x:datamodel:teemip-endusers-devices|End-Users Devices]] | This optional module provides support for end-user related devices: PCs, Telephones, Printers and other Peripherals. | 
-| [[2_x:datamodel:teemip-network-mgmt|Network Management]] | This module is mandatory and provides network specific objects: IP Interfaces, VLANs, WAN links, DNS domains, AS numbers, VRFs.| 
-| [[2_x:datamodel:teemip-storage-mgmt|Storage Management]] | This optional module defines objects to manage advanced storage infrastructures, including SAN, NAS, Storage Systems,  Fiber Channel Interfaces, Volumes... | 
-| [[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 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: 
- 
-<note important> 
-  * 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, 
-  * 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. 
-</note> 
- 
-More details can be found in the [[2_x:datamodel:ip-addresses#links_between_ip_addresses_and_cis|IP addresses]] documentation page. 
- 
-==== 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:datamodel:ip-settings#automatic_ip_release|release]] IPs that are linked to an obsolete 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 [[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 [[2_x:datamodel:ip-settings|IP Settings]] documentation page.