This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
2_x:datamodel:start [2023/09/15 16:19] – cnaud | 2_x:datamodel:start [2023/09/15 21:11] – cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== TeemIp Data Model ====== | ====== TeemIp Data Model ====== | ||
- | FIXME | ||
- | TeemIp provides the following main features: | ||
- | * A Configuration Management Data Base (CMDB), widely enriched from iTop default' | ||
- | * An IP Management module to manage IP spaces, | ||
- | * A Helpdesk dedicated to the creation of IP objects (*), | ||
- | * A modelization of DHCP and DNS services (*). | ||
+ | ===== IP Management ===== | ||
+ | IP Management is the heart of TeemIp. This is the place where IPv4 and IPv6 spaces are administered. A set of IP objects modelizes your IP spaces: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
- | (*) These features | + | <note tip> IPv4 and IPv6 spaces |
+ | </ | ||
+ | |||
+ | {{overview_group_module-3x.png? | ||
+ | |||
+ | |||
+ | And different [[2_x: | ||
===== CMDB ===== | ===== CMDB ===== | ||
- | The [[2_x: | + | The **Configuration Management Data Base** defines |
- | ===== IP 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 | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | |||
+ | ===== 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 | ||
+ | |||
+ | <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. | ||
+ | </ | ||
+ | |||
+ | More details can be found in the [[2_x: | ||
+ | |||
+ | ===== 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: | ||
+ | |||
+ | These processes are documented in the [[2_x: | ||
- | [[2_x: | + | ===== TeemIp |
+ | TeemIp is a highly configurable application and many parameters allow you to adapt it to your own IP Management practices: | ||
+ | * The [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
===== Extensions ===== | ===== Extensions ===== |