Doc: AVD with Ansible Automation Platform Guide #3910
Conversation
github-actions
bot
added
the
type: documentation
| Please note, that this guide leverages AAP version 2.4. The workflows should be similar in newer versions; if there are any questions, please see the official [AAP documentation](https://access.redhat.com/documentation/en-us/red_hat_ansible_automation_platform/2.4). | ||
|
|
||
| - An accessible lab topology running Arista EOS. | ||
| - An AVD project or Git repository with playbooks and an inventory. To get started, you may also use any of our [example topologies](../../examples/single-dc-l3ls/README.md). |
There was a problem hiding this comment.
"AVD project" is referring to an AAP project right? Maybe a clarification could help here
There was a problem hiding this comment.
I meant an AVD project or a git repo that has the usual items (inventory, group vars, playbooks)
| tasks: | ||
| - name: Provision CVP with AVD configuration | ||
| import_role: | ||
| name: eos_config_deploy_cvp |
There was a problem hiding this comment.
Perhaps add a Studios example with cv_deploy?
There was a problem hiding this comment.
Do you mean to replace this one or show an additional build and deploy step with cv_deploy?
There was a problem hiding this comment.
I agree here, we should start giving examples for the role cv_deploy, considering it is the new way to use static configlets studios.
|
|
Going to set overwrite on the variables as well to make the source of truth rule all the things. |
Disregard, the way we set overwrite on inventory sync, even if folks added a custom var to host or groups, those would be removed when the inventory is updated. Only difference is if someone supplies a job specific variable. |
ClausHolbechArista
added
the
one approval
|
|
||
| ## Requirements to get started | ||
|
|
||
| Please note, that this guide leverages AAP version 2.4. The workflows should be similar in newer versions; if there are any questions, please see the official [AAP documentation](https://access.redhat.com/documentation/en-us/red_hat_ansible_automation_platform/2.4). |
There was a problem hiding this comment.
Can we suggest to open an issue with us to keep this document up to date?
|
|
||
| Our topology leverages two spines and four leaf nodes to create a layer three leaf spine topology. The topology is managed by Arista CloudVision Portal (CVP). In our case, the EOS nodes are constantly streaming to CVP and gives us the ability to provision the nodes with CVP. AAP will act as our controller to communicate any updates to CVP, which can then push the updates to our topology. | ||
|
|
||
|  |
There was a problem hiding this comment.
For consistency in the document, should we change RH AAP for AAP? And cvp in capital letters (ie CVP)?
Also, the colour of the arrows, does it mean anything? If yes, what? If not, I think to use the same colour will be a good idea
There was a problem hiding this comment.
I agree with just AAP. Good catch and we should just use CloudVision (CV).
|
|
||
| ## Job templates and workflow templates | ||
|
|
||
| One thing that may need some clarification is the naming of "job templates." These map to playbooks within our project. There is also an option to build workflow templates: a series of job templates with some control logic built-in. For this example, we will use a job template to build and deploy our node configurations with CVP. |
Change Summary
This getting started guide will walk AVD users through getting up and running with AVD and AAP.
Proposed changes
Please see change summary
How to test
View docs generated with PR
Checklist
Repository Checklist