Ansible Config As Code With Network Backups To Git And Point-In-Time Rollback

preview_player
Показать описание

This demo utilizes config as code. This means that the configuration for my network kit is stored in my git repository in standard CLI format. When I invoke ansible to configure the equipment it will first do a backup, then it will clone the configuration repo and update the devices. If, for any reason, I want to rollback the configuration on all or any of the devices in that change window, all I have to do is specify a backup tag, and the automation will grab the correct snapshot from git and perform the restore.
Рекомендации по теме
Комментарии
Автор

I'm very new to this and trying to learn git/awx/linux all at once has got my brain feeling stuffed, I've got awx setup with minikube and docker. Would the roles need a separate directory on my gitlab repo to be able to be called and used here and they'll be recognized automatically when I run the certain playbook? I wish I could get some more direct guidance but anything to progress my knowledge since I know ansible and network automation go hand in hand.

MiguelGomez-pgdd
Автор

Hello Greg,

I came across your YouTube video, "Ansible Config As Code With Network Backups To Git And Point-In-Time Rollback, " and I'm trying to implement the same setup. However, no matter what I try, I keep encountering an error. I have taken the private key created for the AWX GitLab source control and used it for the cert-key, but it keeps asking for "sudo: a password is required."

I would appreciate any ideas you might have about what could be going wrong. I'm using AWX, NetBox, and GitLab for my lab.

Thank you!

damtoin