This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
extensions:teemip-request-mgmt [2021/03/29 17:35] – [IP Request Management] cnaud | extensions:teemip-request-mgmt [2024/04/04 14:45] (current) – [Revision History] cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{ classicon_iprequest.png}} | + | {{ picto_iprequestmanagement.png}} |
| | ||
---- dataentry summary ---- | ---- dataentry summary ---- | ||
Line 6: | Line 6: | ||
index_hidden | index_hidden | ||
level_hidden | level_hidden | ||
- | version | + | collector_hidden |
- | release_dt | + | version |
- | TeemIp | + | release_dt |
+ | TeemIp | ||
+ | iTop : 3.x | ||
code : teemip-ip-request-mgmt | code : teemip-ip-request-mgmt | ||
+ | localization | ||
state : stable | state : stable | ||
diffusion_hidden | diffusion_hidden | ||
- | product_hidden | + | product_hidden |
module-lists_hidden : | module-lists_hidden : | ||
keyword_tags | keyword_tags | ||
dependencies_s | dependencies_s | ||
- | download_wiki | + | download_wiki |
- | git hub_wiki | + | github_wiki |
+ | php-max | ||
---- | ---- | ||
+ | |||
Line 35: | Line 40: | ||
===== Revision History ===== | ===== Revision History ===== | ||
- | ^ Version | + | ^ Version |
- | | 2.7.1 | 2021-04-01 | + | | **3.1.1** |
- | | 2.6.1 | 2020-05-08 | + | | 3.1.0 | 2023-06-21 |
- | | 2.6.0 | 2020-04-14 | + | | 3.0.1 | 2022-09-09 |
- | | 2.5.1 | 2019-12-10 | + | | 3.0.0 | 2022-01-10 |
- | | 2.5.0 | 2019-09-24 | + | | 2.7.1 | 2021-04-01 |
- | | 2.4.0 | 2019-02-09 | + | | 2.6.1 | 2020-05-08 |
- | | 2.3.0 | 2018-08-28 | + | | 2.6.0 | 2020-04-14 |
- | | 2.2.0 | | + | | 2.5.1 | 2019-12-10 |
- | | 2.1.2 | 2017-11-11 | + | | 2.5.0 | 2019-09-24 |
- | | 2.1.1 | 2016-12-19 | + | | 2.4.0 | 2019-02-09 |
+ | | 2.3.0 | 2018-08-28 | ||
+ | | 2.1.2 | 2017-11-11 | ||
+ | | 2.1.1 | 2016-12-19 | ||
Line 59: | Line 67: | ||
===== Licensing ===== | ===== 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, | + | 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 |
===== Limitations ===== | ===== Limitations ===== | ||
Line 91: | Line 99: | ||
Once installed, the module will add a menu group called IP Helpdesk where IP requests will be managed from. | Once installed, the module will add a menu group called IP Helpdesk where IP requests will be managed from. | ||
- | {{ details_menu_iphelpdesk.png }} | + | {{ details_menu_iphelpdesk3x.png }} |
The overview dashboard allows agents and managers to monitor the helpdesk activity. It displays a set of 6 dashlets: | The overview dashboard allows agents and managers to monitor the helpdesk activity. It displays a set of 6 dashlets: | ||
Line 105: | Line 113: | ||
===== IP Request ===== | ===== IP Request ===== | ||
- | {{classicon_iprequest.png }} | + | {{iprequest.png }} |
IP requests in TeemIp are focusing on IP management. A catalogue of 6 types of IP requests have been defined, each of them focusing on a specific request: | IP requests in TeemIp are focusing on IP management. A catalogue of 6 types of IP requests have been defined, each of them focusing on a specific request: | ||
Line 138: | Line 146: | ||
| User comment | Multiline character string | | User comment | Multiline character string | ||
- | < | + | < |
== Specific information for IP address V4 creation == | == Specific information for IP address V4 creation == | ||
- | {{classicon_ipv4address.png }} | + | {{icons8-rj45-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 161: | Line 169: | ||
== Specific information for IP address V6 creation == | == Specific information for IP address V6 creation == | ||
- | {{classicon_ipv6address.png }} | + | {{icons8-rj45v6-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 180: | Line 188: | ||
== Specific information for IP update == | == Specific information for IP update == | ||
- | {{classicon_ipv4address.png }} | + | {{icons8-rj45-48.png }} |
- | {{classicon_ipv6address.png }} | + | {{icons8-rj45v6-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 193: | Line 201: | ||
== Specific information for IP release == | == Specific information for IP release == | ||
- | {{classicon_ipv4address.png }} | + | {{icons8-rj45-48.png }} |
- | {{classicon_ipv6address.png }} | + | {{icons8-rj45v6-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 202: | Line 210: | ||
== Specific information for Subnet V4 creation == | == Specific information for Subnet V4 creation == | ||
- | {{classicon_ipv4subnet.png }} | + | {{icons8-subnet-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 215: | Line 223: | ||
== Specific information for Subnet V6 creation == | == Specific information for Subnet V6 creation == | ||
- | {{classicon_ipv6subnet.png }} | + | {{icons8-subnetv6-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 228: | Line 236: | ||
== Specific information for Subnet update == | == Specific information for Subnet update == | ||
- | {{classicon_ipv4subnet.png }} | + | {{icons8-subnet-48.png }} |
- | {{classicon_ipv6subnet.png }} | + | {{icons8-subnetv6-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 242: | Line 250: | ||
== Specific information for Subnet release == | == Specific information for Subnet release == | ||
- | {{classicon_ipv4subnet.png }} | + | {{icons8-subnet-48.png }} |
- | {{classicon_ipv6subnet.png }} | + | {{icons8-subnetv6-48.png }} |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 262: | Line 270: | ||
From the Helpdesk menu, click on the “New IP Request” link. User is then asked to select amongst the 6 types of requests: | From the Helpdesk menu, click on the “New IP Request” link. User is then asked to select amongst the 6 types of requests: | ||
- | {{ classcreate_iprequest1.png }} | + | {{ classcreate_iprequest13x.png }} |
Once selection is done, the creation form is displayed (IPv4 subnet creation, in the example below). | Once selection is done, the creation form is displayed (IPv4 subnet creation, in the example below). | ||
- | {{ classcreate_iprequest2.png }} | + | {{ classcreate_iprequest23x.png }} |
Line 276: | Line 284: | ||
The **private log** is the preferred way for keeping track of the investigations or operations: copy/paste of command line results, summary of communications with a provider, etc. | The **private log** is the preferred way for keeping track of the investigations or operations: copy/paste of command line results, summary of communications with a provider, etc. | ||
- | {{public-privatelog_iprequest.png}} | + | {{public-privatelog_iprequest3x.png}} |
Each entry in the public or private log is tracked with the name of the user who updated it and when it was done. It cannot be modified nor deleted. | Each entry in the public or private log is tracked with the name of the user who updated it and when it was done. It cannot be modified nor deleted. | ||
Line 284: | Line 292: | ||
===== Assigning an IP request to a team and agent ===== | ===== Assigning an IP request to a team and agent ===== | ||
- | Once an IP request is created, it needs to be assigned to a team and agent before being further processed. For that to happen, select the Assign action in the “Other Actions” menu available from the details page. | + | Once an IP request is created, it needs to be assigned to a team and agent before being further processed. For that to happen, select the Assign action in the list of menus available from the details page. |
- | {{ details-popup-menu-iprequestotheractions.png }} | + | {{ details-popup-menu-iprequestotheractions3x.png }} |
- | Then select the Support team you want to assign the ticket to as well as the agent from this team. | + | Then select the Support team you want to assign the ticket to, as well as the agent from this team. |
- | {{ classassign_iprequest.png }} | + | {{ classassign_iprequest3x.png }} |
< | < | ||
Line 306: | Line 314: | ||
</ | </ | ||
- | {{ classprocess_iprequestipcreation.PNG }} | + | {{ classprocess_iprequestipcreation13x.png }} |
+ | {{ classprocess_iprequestipcreation23x.png | ||
< | < | ||
Line 332: | Line 341: | ||
</ | </ | ||
- | {{ classprocess_iprequestsubnetcreation.PNG }} | + | {{ classprocess_iprequestsubnetcreation.png }} |
Once the subnet is selected, pressing the " | Once the subnet is selected, pressing the " | ||
Line 360: | Line 369: | ||
For creation requests, the subnet or the subnet block, where the IP or subnet are supposed to be picked from, need to be eligible for automatic creation. This behaviour is driven buy a parameter named " | For creation requests, the subnet or the subnet block, where the IP or subnet are supposed to be picked from, need to be eligible for automatic creation. This behaviour is driven buy a parameter named " | ||
- | {{ classdetails_ipv4subnet.png }} | + | {{ classdetails_ipv4subnet3x.png }} |
- | {{ classdetails_ipv6block.png }} | + | {{ classdetails_ipv6block3x.png }} |
===== IP Request Life Cycle ===== | ===== IP Request Life Cycle ===== | ||
All IP requests share the same life cycle. This one is pretty simple and can be summarized as follows: | All IP requests share the same life cycle. This one is pretty simple and can be summarized as follows: | ||
- | {{ lifecycle_iprequest.PNG }} | + | {{ lifecycle_iprequest3x.png }} |