This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
extensions:teemip-request-mgmt [2020/05/08 17:44] – [Data entry] cnaud | extensions:teemip-request-mgmt [2021/03/23 18:58] – [IP address creation] cnaud | ||
---|---|---|---|
Line 35: | Line 35: | ||
===== Revision History ===== | ===== Revision History ===== | ||
^ Version | ^ Version | ||
+ | | 2.7.1 | 2021-04-01 | ||
| 2.6.1 | 2020-05-08 | | 2.6.1 | 2020-05-08 | ||
| 2.6.0 | 2020-04-14 | | 2.6.0 | 2020-04-14 | ||
Line 48: | Line 49: | ||
===== Features ===== | ===== Features ===== | ||
- | This extension allows Hostmasters to manage tickets that are specific to the IP management world: creation, modification or deletion | + | This extension allows Hostmasters to manage tickets that are specific to the IP management world: creation, modification or release |
- | Management of IP tickets is done following a workflow that automates the standard tasks associated to IP tickets: selection of an IP within a subnet, selection of a subnet within a subnet block, for instance. Such workflow insures that tickets are managed according to a defined process. Only authorized users can manage an IP request and change its status. | + | Management of IP tickets is done following a workflow that automates the standard tasks associated to IP tickets: selection of an IP within a subnet, selection of a subnet within a subnet block, for instance. Such workflow insures that tickets are managed according to a defined process. Only authorized users can manage an IP request and change its status. Full automation is also available to the end users who have the correct profile and for subnet blocks or subnets that allow such comprehensive automation. |
At any time of the life of the ticket, the support agent can communicate with the customer via a “Public log.” He can also communicate with teams internal to his company through a “Private log”. | At any time of the life of the ticket, the support agent can communicate with the customer via a “Public log.” He can also communicate with teams internal to his company through a “Private log”. | ||
- | Starting for revision 2.5.1, the extension includes | + | TeemIp |
+ | |||
+ | ===== Licensing ===== | ||
+ | The TeemIp Request Management extension is licensed under the terms of the GNU Affero General Public License Version 3 as published by the Free Software Foundation. This gives you legal permission to copy, distribute and/or modify TeemIp under certain conditions. Read the ’license.txt’ file in the TeemIp distribution. TeemIp is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY, | ||
===== Limitations ===== | ===== Limitations ===== | ||
Line 151: | Line 156: | ||
| Target class | Instantiated class of object that the IP should be linked to | No | | | Target class | Instantiated class of object that the IP should be linked to | No | | ||
| Functional CI | CI of class " | | Functional CI | CI of class " | ||
- | | Link between IP and CI | IP attribute of the CI that the IP should be allocate to | No | | + | | CI's IP attribute |
== Specific information for IP address V6 creation == | == Specific information for IP address V6 creation == | ||
Line 170: | Line 175: | ||
| Target class | Instantiated class of object that the IP should be linked to | No | | | Target class | Instantiated class of object that the IP should be linked to | No | | ||
| Functional CI | CI of class " | | Functional CI | CI of class " | ||
- | | Link between IP and CI | IP attribute of the CI that the IP should be allocate to | No | | + | | CI's IP attribute |
== Specific information for IP update == | == Specific information for IP update == | ||
Line 250: | Line 255: | ||
===== User profiles ===== | ===== User profiles ===== | ||
- | By default, IP request management is restricted to the Hostmaster | + | By default, IP request management is restricted to the **IP Helpdesk agent** |
Line 294: | Line 299: | ||
==== IP address creation ==== | ==== IP address creation ==== | ||
- | FIXME | + | When the Process action of an IPv4 or IPv6 creation is launched, TeemIp will look for the first 10 free IPs located |
- | When the Process action of an IPv4 or IPv6 creation is launched, TeemIp will look for the first 10 free IPs in the subnet and will list them at the top of the request. | + | |
<note important> | <note important> | ||
Line 307: | Line 311: | ||
</ | </ | ||
- | Once the IP is selected, pressing the " | + | Once the IP is selected, pressing the " |
- | If a Connectable CI has been selected, then the following action is performed or needs to be performed, according to the value of the Link between IP and CI attribute: | ||
- | * Management IP: the management IP of the selected device is automatically updated with the IP created, | ||
- | * Physical / Logical Interface: the agent needs to create a physical / logical interface (that includes the newly created IP) and to attach it to the device. | ||
- | If the agent wants to give a specific IP address that already exists in TeemIp' | + | If the agent wants to give a specific IP address that already exists in TeemIp' |
- | <note warning> | + | <note warning> |
</ | </ | ||
==== IP address update ==== | ==== IP address update ==== |