-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compliance Checks with Ansible #8
Comments
These are the ansible files mentioned. |
dev_nsoTesting the capabilities of NSO templates for runbook automation. environmentThe inventory here uses the NSO DevNET lab. Set up Local NSO Notes on LAB setup: overviewnso_self-healing.yaml: upload to githubSet up Local NSOncs-setup --package nso/packages/neds/cisco-ios-cli-6.67 cd ~/nso-instance ncs_cli -C -u admin conf devices device edge-sw01 Set up NETCONFtelnet 10.10.20.173 conf telnet 10.10.20.174 conf re-sync NSOncs_cli -C -u admin Try running the main playbookcopy files ansible-playbook -i inventory/devnet.ini nso_self-healing.yaml -vv
ansible-playbook -i inventory/devnet.ini nso_self-healing.yaml -vv --extra-vars "nso_username=admin nso_password=admin" got the following error
makes me think there is something wrong with the URL or ports the role inclue is
which then runs
|
feedback from user:
User is working on a compliance check where they use Ansible module to interact with NSO’s compliance templates. The challenge is we only could figure out how to save the results to the state directory with the html results. This has been difficult because we want to GET the results form the API to pass to Ansible.
I have a task to run the compliance report but there doesn't seem to be a great way to get the report itself from the API?
Right now, the script just looks to see if there were any violation errors and if there are, it will re-apply the template
It would be best if a preview of what the compliance report violations are could be added to the script. Trying to use the URI module to download that report like a web page could be awkward.
I had to write a small module to attach a device template in NSO as the nso_action ansible module didn't seem to be able to handle it correctly. This could be a bug in the ansible module.
The text was updated successfully, but these errors were encountered: