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:21] – [IP Interfaces] 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 51: Line 53:
  
 === Physical Interface Properties === === Physical Interface Properties ===
 +^  Name  ^  Type  ^  Mandatory?  ^
 +| Name | Alphanumeric string | Yes |
 +| Status | Possible values: Active, Inactive, Obsolete, Stock | Yes |
 +| Device | Foreign key to a(n) Connectable CI | Yes |
 +| Comment | Multiline character string | No | 
 +| MAC address | Multi format MAC Address | No |
 +| Speed | Decimal value (could be negative) | No |
  
- +=== Tabs === 
-=== Tabs === +
-IP addresses are visible through a dedicated tab. +
 ^  Tab  ^  Description  ^ ^  Tab  ^  Description  ^
 | VLANs | VLANs that the interface is connected to | | VLANs | VLANs that the interface is connected to |
Line 62: Line 69:
 There is no limitation in the number of IPv4s and / or IPv6s that a physical interface can host. There is no limitation in the number of IPv4s and / or IPv6s that a physical interface can host.
  
-{{classdetails_physicalinterface.png}} +{{classdetails_physicalinterface3x.png}} 
  
 <note> <note>
Line 68: Line 75:
 </note> </note>
  
-===== Connectable CI===== +===== Connectable CI and Network Interfaces ===== 
-{{classicon_server.png  }} +{{icons8-server.png  }} 
 A Connectable CI is an abstract class of CIs that groups all CIs that can be connected to an IP network. Such CI can host one or multiple physical interfaces. A Connectable CI is an abstract class of CIs that groups all CIs that can be connected to an IP network. Such CI can host one or multiple physical interfaces.
  
-=== Tabs  === +On this class, TeemIp adds a computed tab that displays all IP addresses (v4 or v6) hosted by all physical interfaces attached to the CI, thus providing an overview on all IPs hosted by the CI.
-A computed tab has been added to connectable CIs. +
-^  Tab  ^  Description  ^ +
-| Interfaces' IPs | All IP addresses (v4 or v6) hosted by all physical interfaces attached to the CI | +
- +
-This allow you to have an overview on all IPs hosted by the CI.+
  
-{{classdetails_connectableci.png}} +{{classdetails_connectableci3x.png}} 
2_x/datamodel/teemip-config-mgmt.1671027694.txt.gz · Last modified: by cnaud

Page Tools