services/Registry.md
... ...
@@ -1,6 +1,6 @@
1 1
# Registry cleanup process
2 2
This process is used to remove inactive objects based on MRT data and the git commit history.
3
-The process is to be executed on a regular basis.
3
+The process is to be executed on a regular basis (yearly).
4 4
5 5
A maintainer is classified as "inactive" if the following conditions have been fulfilled:
6 6
1. All of the ASNs the maintainer has been directly or indirectly associated with (in any way and by following all references, whether through mnt-by, admin-c, tech-c, etc. or through an ORG) have not been observed originating a prefix in the global routing table at any point within the last three years. (Determined by analyzing the daily MRT RIB dumps provided by the DN42 Global Route collector.)
... ...
@@ -10,14 +10,17 @@ Maintainers that are not affiliated with an ASN (whether directly or indirectly
10 10
11 11
## Process
12 12
13
-Using **registry_wizard v0.3.10**:
13
+Using **registry_wizard (written for v0.3.11)**:
14 14
15
-1. Generate a list of active ASNs based on MRT data
15
+1. Generate a list of active ASNs based on MRT data:
16 16
`./registry_wizard /path/to/registry mrt_activity parse /path/to/mrt/files --cutoff-time <value> --list > active_list.txt`
17
-2. Based on the list of active ASNs and through referencing the registry git commit log, generate a list of inactive ASNs.
17
+2. Based on the list of active ASNs and through referencing the registry git commit log, generate a list of inactive ASNs:
18 18
`./registry_wizard /path/to/registry mrt_activity active_asn_to_inactive --list_file /path/to/active_list.txt --cutoff-time <value> > inactive_list.txt`
19
-3. Generate the removal commands to remove inactive objects based on the previous list
19
+3. Generate the removal commands to remove inactive objects based on the previous list:
20 20
`./registry_wizard /path/to/registry remove aut-num --list_file /path/to/list.txt --enable_subgraph_check`
21 21
22 22
ASNs can be excluded from removal by removing them from the list produced in the second step.
23
-Manual review of a few resources affiliated with "DN42-MNT" will be required as they cannot be removed in an automated way (for example, resources associated with an inactive maintainer that used to host the DN42 anycast DNS will be affiliated with DN42-MNT and will require manual removal).
23
+
24
+Manual review of a few resources (primarily those affiliated with "DN42-MNT") will be required as they cannot be removed in an automated way (for example, resources associated with an inactive maintainer that used to host the DN42 anycast DNS will be affiliated with DN42-MNT and will require manual removal).
25
+To identify the exact conflicts leading to the manual review requirement the following command can be used:
26
+`./registry_wizard /path/to/registry graph path mntner YAMAKAYA-MNT mntner DN42-MNT` (To list conflicts between YAMAKAYA-MNT and DN42-MNT)
... ...
\ No newline at end of file