2_x:datamodel:ip-addresses
Differences
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:15] – [Allocate Address to CI] 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 139: | Line 163: | ||
| + | ==== Management of DNS RRS ==== | ||
| + | <note tip> | ||
| + | The management of the DNS resource records is available if the [[extensions: | ||
| + | </ | ||
| + | === Create / Update DNS RRs === | ||
| + | This action will create the **A / AAAA**, **PTR** and **CNAME** DNS resource records that may be linked to the IP. A few criteria need to be met for this to happen: | ||
| + | * A zone corresponding to the IP's **DNS Domain** and belonging to the right **DNS view** must exist to create the A or AAAA records, | ||
| + | * A reverse zone corresponding to the IP must exist to create the PTR record, | ||
| + | * Each alias must belong to an existing zone in order to create a CNAME record. | ||
| - | ==== Links between IP Addresses and CIs ==== | + | === Delete DNS RRs === |
| + | This action will just delete all resource records linked to the IP. | ||
| + | |||
| + | ====== Links between IP Addresses and CIs ====== | ||
| TeemIp has been designed to provide a comprehensive modelization and documentation of the link(s) that a CI and an IP address may share together. | TeemIp has been designed to provide a comprehensive modelization and documentation of the link(s) that a CI and an IP address may share together. | ||
| Line 146: | Line 182: | ||
| * A unique IP can be attached to them, | * A unique IP can be attached to them, | ||
| * An IP address must be in the status Released or Unassigned to be attached to a CI, | * An IP address must be in the status Released or Unassigned to be attached to a CI, | ||
| - | * IPs that are in state Allocated cannot be set as IP attribute | + | * IPs that are in state Allocated cannot be set as IP attribute |
| - | * Once CI is created or updated, status of attached IP is automatically changed to Allocated, | + | * Reserved |
| + | * Once a CI is created or updated, | ||
| * If a Management IP is removed from the CI, its status becomes Unassigned unless it is still linked to another CI. | * If a Management IP is removed from the CI, its status becomes Unassigned unless it is still linked to another CI. | ||
| Line 153: | Line 190: | ||
| * One or more IPs (with no limitation of quantity) can be attached to them, | * One or more IPs (with no limitation of quantity) can be attached to them, | ||
| * An IP can be attached to them, regardless their status, | * An IP can be attached to them, regardless their status, | ||
| - | * Once CI is created or updated, status of attached | + | * Once an interface |
| * If a link with an IP address is removed, status of IP moves back to Unassigned unless it is still linked to another CI. | * If a link with an IP address is removed, status of IP moves back to Unassigned unless it is still linked to another CI. | ||
| Line 160: | Line 197: | ||
| </ | </ | ||
| - | === Impact of CIs' life cycle to IPs === | + | ==== Impact of CIs' life cycle to IPs ==== |
| Changes on CIs may have an impact on IPs. Here is what happens when... | Changes on CIs may have an impact on IPs. Here is what happens when... | ||
| - | == - A Functional CI is created == | + | === - A Functional CI is created |
| * It is checked if the CI has IP Attributes, | * It is checked if the CI has IP Attributes, | ||
| * For each of these that do point to an IP: | * For each of these that do point to an IP: | ||
| Line 168: | Line 205: | ||
| * Short name attribute is computed. | * Short name attribute is computed. | ||
| - | == - A Functional CI is updated == | + | === - A Functional CI is updated |
| * It is checked if the CI has IP Attributes, | * It is checked if the CI has IP Attributes, | ||
| * For each of these: | * For each of these: | ||
| Line 174: | Line 211: | ||
| * Short name is changed if the CI name has changed. | * Short name is changed if the CI name has changed. | ||
| - | == - A Functional | + | === - A Functional |
| * It is checked if the CI had IP Attributes, | * It is checked if the CI had IP Attributes, | ||
| * For each of these that do point to an IP: | * For each of these that do point to an IP: | ||
| Line 180: | Line 217: | ||
| * Short name attribute is reset to empty string. | * Short name attribute is reset to empty string. | ||
| - | == - A functional CI becomes obsolete == | + | === - A functional CI becomes obsolete |
| - | * Its IPs may automatically be released from it, as described in the related [[2_x: | + | * Its IPs may automatically be released from it, if IP Setting **Release IPs from CIs that become obsolete** is set. |
| - | === Releasing IPs === | + | ==== Releasing IPs ==== |
| 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. |
| - | | + | |
| - | | + | |
| - | | + | |
| + | | ||
| + | * **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: | ||
2_x/datamodel/ip-addresses.1696324507.txt.gz · Last modified: 2023/10/03 11:15 by cnaud