This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
2_x:datamodel:ip-addresses [2023/10/03 11:54] – [Links between IP Addresses and CIs] cnaud | 2_x:datamodel:ip-addresses [2024/04/04 16:10] (current) – cnaud | ||
---|---|---|---|
Line 79: | Line 79: | ||
By definition, FQDNs are absolute domain names. They specify the exact location of domain names in the tree hierarchy of the Domain Name System (DNS). This is why they end up with a dot.\\ | By definition, FQDNs are absolute domain names. They specify the exact location of domain names in the tree hierarchy of the Domain Name System (DNS). This is why they end up with a dot.\\ | ||
\\ | \\ | ||
+ | According to configuration parameter **Allow Duplicate Names**, unicity of the FQDN is checked: | ||
+ | * Duplicates may exist in different organizations, | ||
+ | * Within an organization, | ||
+ | * If parameter is set to: | ||
+ | * **No**, all other cases of duplicates are rejected, | ||
+ | * **Dual stack**, duplicates may exist between IPv4 and IPv6 spaces, | ||
+ | * **Yes**, unicity of FQDN is not verified. | ||
+ | |||
According to configuration parameter **Compute FQDN when short name is empty**, the FQDN may be computed regardless the content of the Short Name and DNS Domain. | According to configuration parameter **Compute FQDN when short name is empty**, the FQDN may be computed regardless the content of the Short Name and DNS Domain. | ||
</ | </ | ||
Line 91: | Line 99: | ||
For v6 IPs, a simple autocompletion mechanism is used to help typing the IP: its first 64 bits are copied from the subnet IP… which can, of course, be manually changed by the user. | For v6 IPs, a simple autocompletion mechanism is used to help typing the IP: its first 64 bits are copied from the subnet IP… which can, of course, be manually changed by the user. | ||
</ | </ | ||
- | ==== Modify | + | ==== Modifying |
From the detailed view of an IP Address, click on the {{pen-icon.png? | From the detailed view of an IP Address, click on the {{pen-icon.png? | ||
Line 97: | Line 105: | ||
==== Navigating between adjacent IPs ==== | ==== Navigating between adjacent IPs ==== | ||
- | FIXME | + | TeemIp provides an easy and efficient way to navigate between adjacent IPs. If the action is enabled, the left and rights arrows of the object menu {{navigate-icon.png? |
+ | |||
+ | < | ||
+ | ' | ||
+ | ... | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ), | ||
+ | ... | ||
+ | ), | ||
+ | |||
+ | </ | ||
+ | |||
+ | ^ Parameter | ||
+ | | enabled| Enable or disable the function | | ||
+ | | within_subnet_only| Limit the navigation to the subnet that the IP belongs to or not | | ||
==== Other Actions ==== | ==== Other Actions ==== | ||
Next to standard actions, a set of specific actions can be applied to IP Addresses. These can be found in the **Other Actions** menu available from the details page. | Next to standard actions, a set of specific actions can be applied to IP Addresses. These can be found in the **Other Actions** menu available from the details page. | ||
Line 200: | Line 224: | ||
When an IP is set to the status " | When an IP is set to the status " | ||
- | ==== Continuous IP status coherency check ==== | + | ==== Automation |
- | TeemIp may automatically and periodically check the status of IPs and their coherency with the CIs they are attached to, if any. This behaviour is driven by a set of parameters defined in [[2_x: | + | When linking an IP together with a CI, one must insure that both the CI's and the IP's status are consistent. |
- | * **Allocate IPs attached to production CIs** be set, TeemIp will make sure that IPs attached to CIs are " | + | |
- | * **Release IPs from CIs that become obsolete** be set, TeemIp will release all IPs that are still allocated to obsolete CIs, | + | * **Allocate IPs attached to production CIs** (*) be set to **Yes**, TeemIp will make sure that IPs attached to CIs are " |
- | * **Release IPs from subnets that are released** be set, TeemIp will release all IPs that belong to released subnets. | + | * **Release IPs from CIs that become obsolete** |
+ | * **Un-allocate IPs that are not attached to a CI** (*) be set to **Yes**, TeemIp will unassign the IPs that are no longer attached to a CI, | ||
+ | * **Release IPs from subnets that are released** be set to **Yes**, TeemIp will release all IPs that belong to released subnets, | ||
+ | * **Allow attachment of already allocated IPs to CIs** be set to **Yes**, TeemIp will allow, from the CI details screen, the attachment of an allocated IP to a CI. | ||
+ | |||
+ | The 3 first actions (*) are handled by background tasks which default parameters can be overwritten in the configuration file. | ||
+ | |||
+ | < | ||
+ | ' | ||
+ | ... | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | 0 => ' | ||
+ | 1 => ' | ||
+ | ), | ||
+ | ), | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | 0 => ' | ||
+ | ), | ||
+ | ), | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ), | ||
+ | ... | ||
+ | ), | ||
+ | |||
+ | </ | ||
+ | |||
+ | ^ Parameter | ||
+ | | enabled| Enable or disable the function | | ||
+ | | debug | Add verbosity to the process | | ||
+ | | periodicity | Periodicity of the background task | | ||
+ | | status_list | List of status that trigger the action | | ||
+ | | target_status | Status of the IP once the action is done | | ||
+ | Please, refer to the [[2_x: |