This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 2_x:datamodel:ip-addresses [2024/01/26 16:27] – [Modify an IP Address] cnaud | 2_x:datamodel:ip-addresses [2024/07/26 09:23] (current) – [Automation] cnaud | ||
|---|---|---|---|
| Line 39: | Line 39: | ||
| * **Reserved**: | * **Reserved**: | ||
| * **Unassigned**: | * **Unassigned**: | ||
| + | |||
| + | If [[extensions: | ||
| </ | </ | ||
| Line 79: | Line 81: | ||
| 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 214: | Line 224: | ||
| ==== Releasing IPs ==== | ==== Releasing IPs ==== | ||
| - | When an IP is set to the status " | + | When an IP is set to the status " |
| ==== Automation ==== | ==== Automation ==== | ||
| Line 224: | Line 234: | ||
| * **Release IPs from subnets that are released** be set to **Yes**, TeemIp will release all IPs that belong to released subnets, | * **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. | * **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. | ||
| + | * **Detach released IPs from CIs** be set to **Yes**, TeemIp will detach IPs which status moves to " | ||
| The 3 first actions (*) are handled by background tasks which default parameters can be overwritten in the configuration file. | The 3 first actions (*) are handled by background tasks which default parameters can be overwritten in the configuration file. | ||