Skip to content
Snippets Groups Projects
Verified Commit 9ada9933 authored by Karel van Klink's avatar Karel van Klink :smiley_cat:
Browse files

update glossary

parent 21baa262
Branches
No related tags found
2 merge requests!21[2024-02-06] Publish docs,!20Feature/document workflows
Pipeline #85642 failed
...@@ -71,8 +71,8 @@ but not committed to the machine. ...@@ -71,8 +71,8 @@ but not committed to the machine.
After the dry run, the operator is presented with a view of the outcome of After the dry run, the operator is presented with a view of the outcome of
this playbook. This is their opportunity to verify successful execution of this playbook. This is their opportunity to verify successful execution of
the Ansible playbook, and whether the difference in configuration is as the Ansible playbook, and whether the difference in configuration is as
expected. If this is not the case, this is their chance to abort the expected. If not, this is their chance to abort the workflow, and no harm is
workflow, and no harm is done to the router. done to the router.
When the operator confirms the outcome of this playbook execution, the When the operator confirms the outcome of this playbook execution, the
playbook runs once again, but it will also commit the configuration after playbook runs once again, but it will also commit the configuration after
...@@ -107,9 +107,9 @@ The workflow will run 5 Ansible playbooks: ...@@ -107,9 +107,9 @@ The workflow will run 5 Ansible playbooks:
Once these playbooks have been run successfully, the new P router is added 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 to LibreNMS. Finally, the subscription model of the router is updated such that
`router_access_via_ts` is set to `False`. This is due to the fact that the `router_access_via_ts` is set to `False`. This is because the router is now
router is now reachable by other machines by its loopback address. Using out reachable by other machines by its loopback address. Using out of band access is
of band access is therefore not needed anymore. therefore not needed anymore.
### Redeploy ### Redeploy
......
...@@ -7,6 +7,7 @@ ...@@ -7,6 +7,7 @@
*[DNS]: Domain Name System *[DNS]: Domain Name System
*[DTAP]: Development, Testing, Acceptance, and Production *[DTAP]: Development, Testing, Acceptance, and Production
*[eBGP]: External BGP *[eBGP]: External BGP
*[FQDN]: Fully Quantified Domain Name
*[GA]: Access Port *[GA]: Access Port
*[GAN]: Access Node *[GAN]: Access Node
*[GAP]: GÉANT Automation Platform *[GAP]: GÉANT Automation Platform
......
...@@ -7,7 +7,7 @@ configuration as code ...@@ -7,7 +7,7 @@ configuration as code
[Cc]omponents? [Cc]omponents?
contains? contains?
GAP GAP
GÉANT Automation Platform GÉANT( Automation Platform)?
GOAT GOAT
GSO GSO
IFS IFS
......
AAA AAA
AMT
Ansible Ansible
APIs? APIs?
BGP i?BGP
DCIM DCIM
DDI DDI
[Dd]eprovision
DHCP DHCP
DNS DNS
Dockerfile Dockerfile
DTAP DTAP
EVE EVE
FQDN
FXP FXP
GAN GAN
[Hh]ostnames?
IGP IGP
Infoblox Infoblox
IP( address)? IP( address)?
IPAM IPAM
IP/MPLS IP/MPLS
ISIS ISIS
ISO
MPLS MPLS
MTTR MTTR
MTU MTU
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment