Feature cvp deployment #41
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implement a role to build CVP topology based on inventory file - Render expected container topology in a user defined folder with user defined name - Implement a role to collect cvp facts and create containers topology TODO: - Add configlet support - Add device support
- Implement function to extract devices attached under a container. - Create a subsection named devices with all devices to move to that container in CVP
Create configlet structure to load generated config to CVP Structure is saved in result['CVP_CONFIGLETS'] and can passed to cv_configlet
|
Currently Supported:
TODO:
|
Create a template to generate dataset required for cv_device. All devices part of DC1-FABRIC are included.
|
PR implements following tasks:
Everything is part of role: Task execution remains manual as it is a big change in topology and it is better to use change-control manually instead of fully-automated approach Ready for testing at scale |
titom73
changed the title
Validate a complete worflow from ZTP to Up & Running
From AVD/CVP perspective, example provides:
- Module to generate vars from inventory
- role to generate cv_device inputs and run all tasks related to CVP
- A single playbook for EOS config generation based on AVD and CVP
deployment
- A readme file with how-to
- Current version 1.0.1 of ansible-cvp
Tested in lab using GNS3 topology of 6 devices (2 spines and 2 pairs of
leafs) and CVP 2018.2.4 with complete ZTP process.
|
Tested in lab with CVP2018.2.4 / ansible-cvp 1.0.1 / 6 devices (2 spines and 2 pairs of leafs) / devices where in ZTP mode before running playbook |
|
Resync with |
Implement multiple input variables to make role more granular:
```yaml
device_filter: 'all'
container_root: '{{ fabric_name }}'
configlets_prefix: 'AVD-{{ fabric_name }}-'
```
A new var is also available to select either creation/update or deletion
```yaml
state: absent
```
|
Start rebase with collection structure |
|
Ready to review and merge |
Update repository documentation related to CV integration: eos_config_deploy_cvp/README.md: Add documentation related to role. plugins/README.md: Update file to document arista.avd.inventory_to_container module
|
Need to update |
Add correct diagram to describe eos_config_deploy_cvp Add wording about how it works
|
Ready for review by @carlbuchmann |
carlbuchmann
approved these changes
Feb 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create workflow to connect
ansible-avdto CloudVision serverMust be updated to support new AVD outputs