Documentation

User Tools

Site Tools

Trace:
extensions:teemip-request-mgmt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
extensions:teemip-request-mgmt [2021/03/23 17:42] – [Revision History] cnaudextensions:teemip-request-mgmt [2021/03/23 18:58] – [IP address creation] cnaud
Line 35: Line 35:
 ===== Revision History ===== ===== Revision History =====
 ^  Version  ^  Release Date  ^  Comments  ^ ^  Version  ^  Release Date  ^  Comments  ^
-|  2.7.1  |  2021-04-01  | Allow automatic request processing for some profiles. \\ Adds a group of recently created requests in Portal list of ongoing tickets.  \\ Align extension structure with new guidelines. |+|  2.7.1  |  2021-04-01  | Allow automatic request processing for some profiles. \\ Add a group of recently created requests in Portal list of ongoing tickets.  \\ Align extension structure with new guidelines. |
 |  2.6.1  |  2020-05-08  | Revision for TeemIp 2.6.1 | |  2.6.1  |  2020-05-08  | Revision for TeemIp 2.6.1 |
 |  2.6.0  |  2020-04-14  | Revision for TeemIp 2.6.0 | |  2.6.0  |  2020-04-14  | Revision for TeemIp 2.6.0 |
Line 49: Line 49:
 ===== Features ===== ===== Features =====
  
-This extension allows Hostmasters to manage tickets that are specific to the IP management world: creation, modification or deletion of IPs, creation, modification or deletion of subnets.+This extension allows Hostmasters to manage tickets that are specific to the IP management world: creation, modification or release of IPs, creation, modification or release of subnets.
  
-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 portal that is described [[2_x:portal:start|here]].+TeemIp IP Request Management includes a dedicated portal that is described [[2_x:portal:start|here]].
  
 ===== Licensing ===== ===== Licensing =====
Line 156: 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 "Target class" which the IP address should be allocated to | No | | Functional CI | CI of class "Target class" which the IP address should be allocated to | No |
-| Link between IP and CI | IP attribute of the CI that the IP should be allocate to  | No |+| CI's IP attribute | IP attribute of the CI that the IP should be allocate to  | No |
  
 == Specific information for IP address V6 creation == == Specific information for IP address V6 creation ==
Line 175: 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 "Target class" which the IP address should be allocated to | No | | Functional CI | CI of class "Target class" which the IP address should be allocated to | No |
-| Link between IP and CI | IP attribute of the CI that the IP should be allocate to  | No |+| CI's IP attribute | IP attribute of the CI that the IP should be allocate to  | No |
  
 == Specific information for IP update == == Specific information for IP update ==
Line 255: Line 255:
 ===== User profiles ===== ===== User profiles =====
  
-By default, IP request management is restricted to the Hostmaster profile that is defined with TeemIp.+By default, IP request management is restricted to the **IP Helpdesk agent** profile that is defined with TeemIp.
  
  
Line 299: 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 in the subnet, from an IP offset defined in the Global IP Setings, and will list them at the top of the request.
-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 312: Line 311:
 </note> </note>
  
-Once the IP is selected, pressing the "Process" button will create the IP in the data base with the attributes set in the request.  At the same time, the ticket is put in the Resolved state.+Once the IP is selected, pressing the "Process" button will create the IP in the data base with the attributes set in the request and, if a Functional CI has been selected and one of its IP Address attributes chosen, will update the CI's attribute with the newly created IP address. At the same time, the ticket is put in the Resolved state.
  
-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's data base, then he needs to press the Modify button instead of the Process one and select the right IP in the <color #ff0000>**IP Address**</color> field of the ticket. Once done, the ticket still needs to be processed in order to  move the ticket to the Resolved state.+If the agent wants to give a specific IP address that already exists in TeemIp's data base, then he needs to press the Modify button instead of the Process one and select the right IP in the **IP Address** field of the ticket. Once done, the ticket still needs to be processed in order to  move the ticket to the Resolved state.
  
-<note warning>When a direct allocation is done, the attributes given in the IP request will not overwrite the ones of the already existing IP !+<note warning>When a direct allocation is done, the attributes given in the IP request, but the IP Status will not overwrite the ones of the already existing IP !
 </note> </note>
 ==== IP address update ==== ==== IP address update ====
extensions/teemip-request-mgmt.txt · Last modified: 2024/04/04 14:45 by cnaud

Page Tools