http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-301 L3 Support <p>We need to implement a new rule to delete data for Nodes (BOARD REPORT ,VLAN REPORT, INVENTORY REPORT ,IDU,IP DATA, TRANSMISSION LINK REPORT ,BTS, eNodeB, gNodeB, SRANBs, Role 2G, Role 4G, Role 5G) where the updated date is not in sync with today's date. This rule should be executed every time after the XML import is completed in each circle and can be modified as per te customer requirement.</p> <p>Additionally, the deletion process will only proceed if the item quantity is 50 or less (otherwise, it should not be executed.), also we can modify the item quantity and date for the deletion as per the requirement for every report ; </p> LS-301

Implementation of New Rule for Node Deletion Post XML Import

CR Deferred Closed Fixed Priyasha Tiwari Priyasha Tiwari Tue, 18 Mar 2025 05:34:20 +0200 Fri, 17 Apr 2026 05:01:02 +0300 Wed, 26 Nov 2025 10:23:29 +0200 NEP Thu, 20 Mar 2025 00:00:00 +0200 0 2 0 minutes 2 weeks, 2 days, 3 hours, 30 minutes 0 minutes 2 weeks, 2 days, 3 hours, 30 minutes <p>Build 3.7.71.463 is released with 50 node deletion restriction for RAN nodes</p> <p>kindly confirm whether it is done for all the mention nodes or not ..BOARD REPORT ,VLAN REPORT, INVENTORY REPORT ,IDU,IP DATA, TRANSMISSION LINK REPORT ,BTS, eNodeB, gNodeB, SRANBs, Role 2G, Role 4G, Role 5G)</p> <p>Hi Dear as discussed its done for all RAN nodes and its related configurational attributes. </p> <p>Build 3.7.71.465 is released containing below requested changes<br/> Hi Srishti, </p> <p>As discussed, we need to update the code to allow the number of nodes to be deleted to be configurable based on customer requirements.</p> <p>Additionally, please add a condition for date based deletions, so that customer can specify a range like deleting data from the past 10 or 15 days ,as needed.</p> <p>Build 3.7.71.472 released containing idu and other deletion addition to api. </p> <p>under testing wl-1day</p> <p>This is the condition-based logic we plan to implement, combining date and count rules. Please review and confirm.<br/> first condition to consider the count is limit can be set to true or false<br/> if Condition of count is set to true , below will be the cases:<br/> Case 1: Data older than x days ( x configurable) <br/> If the date is set to delete data older than x days ( Today -X) and the node count is set to Y, then deletion will proceed only if the number of nodes older than ( today-X) is less than Y , else no deletion and warning will be shown in logs<br/> Case 2: Data except for today's date , Duration is set to 0<br/> If we want to delete all data except for today date and the node count is set to Y , then deletion will proceed only if the number of nodes older than ( today-X) is less than Y , else no deletion and warning will be shown in log<br/> If Count Condition is set to false ,the deletion will occur according to the duration set ( older than X days )</p> <p> testing completed for patch -3.7.71.472, and found that only RAN nodes data are getting deleted, mw, ip, vlan,idu report no deleteion executed . </p> <p>The build 3.7.71.473 has been released with the updated support for configurable duration and nodeSize parameters.<br/> To trigger the deletion, please use the following API call:<br/> <a href="http://localhost:8090/NEP_SERVER/services/airtel/deletion/deleteRanNodes?versionName=Test_IPV6&amp;key=y@8j-bZHqp@teHvVB3-@w?K!R5M?YX&amp;duration=1352&amp;nodeSize=500&amp;isByNodeSize=true" class="external-link" rel="nofollow">http://localhost:8090/NEP_SERVER/services/airtel/deletion/deleteRanNodes?versionName=Test_IPV6&amp;key=y@8j-bZHqp@teHvVB3-@w?K!R5M?YX&amp;duration=1352&amp;nodeSize=500&amp;isByNodeSize=true</a><br/> Parameters:<br/> • versionName – Name of the version<br/> • duration – Number of days for which data is eligible for deletion (i.e., Delete all nodes that were last modified before 19-July-2025, today is 25-July-2025, so 6 days ago is 19-July-2025)<br/> • nodeSize – Maximum number of nodes allowed for deletion<br/> • isByNodeSize – Flag to control deletion based on node count (true = limit by node size, false = delete regardless of size)</p> <p>this details regarding the API working, shared with the customer ..<br/> Dear Team,<br/> The implementation of the logic for node deletion is now ready for production. The patch has already been applied and tested. Below is the API link that needs to be triggered as required. <br/> <a href="http://localhost:8090/NEP_SERVER/services/airtel/deletion/deleteRanNodes?versionName=Test_IPV6&amp;key=y@8j-bZHqp@teHvVB3-@w?K!R5M?YX&amp;duration=1352&amp;nodeSize=500&amp;isByNodeSize=true" class="external-link" rel="nofollow">http://localhost:8090/NEP_SERVER/services/airtel/deletion/deleteRanNodes?versionName=Test_IPV6&amp;key=y@8j-bZHqp@teHvVB3-@w?K!R5M?YX&amp;duration=1352&amp;nodeSize=500&amp;isByNodeSize=true</a></p> <p>All the points mentioned below have been added into the logic. Here is a summary of the API</p> <p>The deletion process is applicable to all nodes and report types for RAN and MW domains, including - eNodeB, gNodeB, BTS SRANBS,IDU, transmission links, and their sub-elements such as board, inventory, addinfo, IPDATA, interfaces,cells , vlan etc.<br/> Note - The main elements like Nodes and link deleted can also be tracked in the logs.</p> <p>The deletion criteria can be modified based on requirements. The logic implemented includes-<br/> • Count Condition: The first condition to consider is whether the count limit is set to true or false.<br/> • If Count Condition is set to true, the following cases apply:<br/> Case 1: Data older than X days (X configurable)<br/> o If the deletion is set to remove data older than X days (where the cutoff date is calculated as Today – X days, inclusive of Today) and the node count threshold is Y, deletion will proceed only if the number of nodes older than the cutoff date is less than Y.<br/> o Otherwise, no deletion will occur, and a warning will be logged.</p> <p> NOTE--_ ( today-X) is where the cutoff date is calculated as Today – X days, inclusive of Today)<br/> Example: If we want to delete data older than 7th August and today’s date is 15th August (inclusive), X will be 9 (i.e., 9 days older data).</p> <p>Case 2: Delete all data except today’s date (Duration = 0)<br/> o If the deletion is set to remove all data except today’s date and the node count threshold is Y, deletion will proceed only if the number of nodes older than the cutoff date is less than Y.<br/> o Otherwise, no deletion will occur, and a warning will be logged.<br/> • If Count Condition is set to false, deletion will occur according to the configured duration (i.e., older than X days) without checking the node count threshold.</p> <p>Tracking of deleted element or count for every circle- This can be monitored from the logs provided by the integration team. Keywords such as “Deleted” and “to delete” will help determine the exact number of nodes deleted from the database.</p> <p>Build 3.7.71.479 is released containing fixes for object not found error during deletion of sranbsnode</p> <p>under testing , unable to apply the patch for testing due to BO machine issue </p> <p>after testing , found out that the only sranbs node are getting deleted .. BTS ENODEB GNODEB nodes are not getting deleted </p> <p>after testing the new patch 481 for this bug, its working fine data is now deleting .. but l3 need to share the details regarding the days calculation for this API again ..</p> <p>Hi Team,<br/> As per the logic implemented in the code, the duration value represents the number of days from today after which data is considered old and eligible for deletion.<br/> So, to delete all GNodeB data before 1st October 2025, we calculate how many days have passed between today (7th October 2025) and 1st October 2025, which is 6 days. Duration = (Today’s date) − (Cut-off date you want to delete before)</p> <p>close this ticket</p> LS-542 LS-544 LS-543 Actual Start Fri, 30 May 2025 00:00:00 +0300 Baseline End Thu, 20 Mar 2025 00:00:00 +0200 Baseline Start Thu, 20 Mar 2025 00:00:00 +0200 Customer Date of Baselining Wed, 4 Jun 2025 05:19:53 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Thu, 20 Mar 2025 00:00:00 +0200 Planned Start Thu, 20 Mar 2025 00:00:00 +0200 Rank 0|xtil2p: Rank (Obsolete) 9223372036854775807 VTDirections