Include documentation from goat/gap/geant-automation-platform

docs/workflow/promote_p_to_pe.md

+# Promote P to PE
+
+Promote a router from the P role to a PE role.

docs/workflow/redeploy_base_config.md

+# Redeploy base configuration
+
+When a new router is deployed, it is loaded with the current version of
+configuration that contain the bare necessities. For various reasons, this 
+template may change, and the resulting configuration follows from this. To 
+update a router 'in the wild' where this change should be reflected, the 
+workflow `redeploy_base_config` is used.
+
+This workflow only takes a trouble ticket number as initial input, and 
+deploys the base configuration, first as a dry run. After confirmation by an 
+operator, the configuration is committed to the machine, and this completes 
+the workflow.

docs/workflow/terminate_iptrunk.md

+# Terminate IP trunk
+
+This workflow deletes all the configuration related with an IPtrunk from the
+network and brings the subscription from `ACTIVE` to `TERMINATED`. The steps
+are the following:
+
+- Modify the ISIS metric of the trunks so to evacuate traffic - and await
+confirmation from an operator.
+- Delete all the configuration (first dry then actual deletion):
+    - LAG and members of the LAG
+    - reference in LLDP protocol (if Juniper)
+    - reference in ISIS protocol
+- Delete the IPv4/IPv6 networks from IPAM

docs/workflow/terminate_router.md

+# Terminate Router
+
+To terminate a router, the workflow `terminate_router` is used. The operator 
+is presented with an input form that requires once again a trouble ticket 
+number. On top of this, there is also the option whether this workflow should
+remove all configuration on the router, and whether IPAM entries related to 
+this device should be removed.
+
+The workflow consists of the following steps:
+
+- Deprovision IPAM resources (if selected).
+- Try to remove configuration form the router (if selected).
+- Commit removal of configuration (if selected).
+- For Nokia devices: remove interfaces from Netbox.
+- Remove the device from LibreNMS.
+- For PE routers: apply the archiving license in Kentik.
+- Set the subscription status to `TERMINATED`.

docs/workflow/terminate_site.md

+# Terminate Site
+
+The `terminate_site` workflow will take an existing and active site 
+subscription from an `ACTIVE` to a `TERMINATED` state. This requires all 
+dependant subscription instances to already be terminated. If this is not 
+the case, the workflow will be unavailable for an operator to run, accompanied
+by an error message explaining this fact.

docs/workflow/update_ibgp_mesh.md

+# Update iBGP mesh
+
+Once a new router is added to the network, it must become reachable by all 
+other devices. To achieve this, the `update_ibgp_mesh` workflow must be 
+executed. This workflow will add the new P router to all PE routers in the 
+network, and add all existing PE routers to the new P router. The only input 
+this workflow takes, is a trouble ticket number. All other required 
+information is already in the service database.
+
+The workflow will run 5 Ansible playbooks:
+
+1. Check: add P router to all PE routers
+2. Deploy: add P router to all PE routers
+3. Check: add all PE routers to P router
+4. Deploy: add all PE routers to P router
+5. Verify: check that the iBGP has come up
+
+Once these playbooks have been run successfully, the new P router is added 
+to LibreNMS. Finally, the subscription model of the router is updated such that
+`router_access_via_ts` is set to `False`. This is because the router is now 
+reachable by other machines by its loopback address. Using out of band access is
+therefore not needed anymore.