This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
2_x:datamodel:ip-addresses [2023/10/03 12:03] – [Continuous IP status coherency check] cnaud | 2_x:datamodel:ip-addresses [2023/10/03 15:42] – [Automation] cnaud | ||
---|---|---|---|
Line 97: | Line 97: | ||
==== 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 216: | ||
When an IP is set to the status " | When an IP is set to the status " | ||
- | ===== Automation | + | ==== Automation ==== |
When linking an IP together with a CI, one must insure that both the CI's and the IP's status are consistent. 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. 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: | ||
Line 207: | Line 223: | ||
* **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. | ||
+ | |||
+ | These actions are handled by background tasks which default parameters can be overwritten in the configuration file. | ||
+ | |||
+ | < | ||
+ | ' | ||
+ | ... | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | 0 => ' | ||
+ | ), | ||
+ | ), | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | 0 => ' | ||
+ | 1 => ' | ||
+ | ), | ||
+ | ), | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ), | ||
+ | ... | ||
+ | ), | ||
+ | |||
+ | </ | ||
+ | |||
+ | ^ 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 | | ||
+ |