Documentation

User Tools

Site Tools

Trace:
2_x:datamodel:teemip-config-mgmt

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
2_x:datamodel:teemip-config-mgmt [2022/12/14 14:55] – cnaud2_x:datamodel:teemip-config-mgmt [2023/11/03 11:06] (current) – [Physical Interfaces] cnaud
Line 1: Line 1:
 ====== CMDB Core ====== ====== CMDB Core ======
-TeemIp's Configuration Management core module is iTop's mandatory Configuration Management module that has been slightly adapted to integrate with TeemIp' specific IP objects. For a comprehensive reference to that module, please, refer to the [[https://wiki.openitop.org/doku.php?id=LATEST:datamodel:itop-config-mgmt|Configuration Management Core]] chapter in iTop wiki.+The core module of the Configuration Management Data Base in TeemIp is made of the [[https://wiki.openitop.org/doku.php?id=LATEST:datamodel:itop-config-mgmt|Configuration Management Core]] module of iTop that has been altered to integrate TeemIp's specific IP objects. The page below lists all these alterations.
  
-Here below is the list of modifications that TeemIp is bringing to iTop CMDB core elements. 
  
 ===== Functional CI ===== ===== Functional CI =====
Line 9: Line 8:
  
 <note tip> <note tip>
-TeemIp adds to it the method **GetNameForIPAttribute** where the shortname of the IP associated to the CI is defined. Because the method is defined in the XML data model file, it can be overloaded to handle specific cases, like the creation of different names for the different IPs that a CI may have.+TeemIp brings the method **GetNameForIPAttribute** where the shortname of the IP associated to the CI is defined. Because the method is defined in the XML data model file, it can be overloaded to handle specific cases, like the creation of different names for the different IPs that a CI may have.
 </note> </note>
  
Line 22: Line 21:
 | Management IP | Foreign key to a(n) IPv4 or IPv6 Address | No | | Management IP | Foreign key to a(n) IPv4 or IPv6 Address | No |
  
-Upon creation or modification, a management IP can be set as a foreign key to an IP address. A drop-down box will list a choice of available IP addresses.+Upon creation or modification, a management IP can be attached as a foreign key to an IP address. A drop-down box will list a choice of available IP addresses.
 <note> <note>
-  * Only addresses which status is released or unassigned (i.e. not allocated nor reserved) will be offered,+  * According to the **Allow attachment of already allocated IPs to CIs** parameter defined in the [[2_x:datamodel:ip-settings|Global IP Settings]] of the IP's organization: 
 +    * Only addresses which status is //**released**// or //**unassigned**// (i.e. not allocated nor reserved) will be offered, 
 +    * Or 
 +    * Only addresses which status is //**allocated**//, //**released**// or //**unassigned**// (i.e. not reserved) will be offered,
   * Status of IP is automatically changed when IP is attached to the data centre device or removed from it,   * Status of IP is automatically changed when IP is attached to the data centre device or removed from it,
   * If enabled through IP settings, CI name is copied into IP short name.   * If enabled through IP settings, CI name is copied into IP short name.
Line 52: Line 54:
 === Physical Interface Properties === === Physical Interface Properties ===
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
-| Name  Alphanumeric string | Yes |+| Name | Alphanumeric string | Yes | 
 +| Status | Possible values: Active, Inactive, Obsolete, Stock | Yes |
 | Device | Foreign key to a(n) Connectable CI | Yes | | Device | Foreign key to a(n) Connectable CI | Yes |
 | Comment | Multiline character string | No |  | Comment | Multiline character string | No | 
2_x/datamodel/teemip-config-mgmt.1671029701.txt.gz · Last modified: by cnaud

Page Tools