Skip to content
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.

Sign up for GitHub

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

Doc: update links to specific version #3039

Merged
merged 1 commit into from
Jul 13, 2023
Merged

Doc: update links to specific version #3039

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions ansible_collections/arista/avd/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Full documentation for the collection:

## Reference designs

- [L3LS VXLAN-EVPN, L2LS, and MPLS (beta)](https://avd.sh/en/stable/roles/eos_designs/index.html)
- [L3LS VXLAN-EVPN, L2LS, and MPLS (beta)](https://avd.arista.com/3.8/roles/eos_designs/index.html)

## Roles overview

Expand All @@ -43,7 +43,7 @@ This repository provides custom plugins for Arista's AVD collection:

## Collection installation

Ansible galaxy hosts all stable versions of this collection. Installation from ansible-galaxy is the most convenient approach for consuming `arista.avd` content. Please follow the collection installation [guide](https://avd.sh/en/stable/docs/installation/collection-installation.html).
Ansible galaxy hosts all stable versions of this collection. Installation from ansible-galaxy is the most convenient approach for consuming `arista.avd` content. Please follow the collection installation [guide](https://avd.arista.com/3.8/docs/installation/collection-installation.html).

## Examples

Expand All @@ -63,7 +63,7 @@ Support for this `arista.avd` collection is provided by the community directly i

## Contributing

Contributing pull requests are gladly welcomed for this repository. If you are planning a big change, please start a discussion first to make sure we'll be able to merge it. Please see [contribution guide](https://avd.sh/en/stable/docs/contribution/overview.html) for additional details.
Contributing pull requests are gladly welcomed for this repository. If you are planning a big change, please start a discussion first to make sure we'll be able to merge it. Please see [contribution guide](https://avd.arista.com/3.8/docs/contribution/overview.html) for additional details.

You can also open an [issue](https://github.com/aristanetworks/ansible-avd/issues) to report any problems or submit enhancements.

Expand Down
6 changes: 3 additions & 3 deletions ansible_collections/arista/avd/examples/campus-fabric/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ leaf:
inband_management_vlan: 10
```

Details on this feature can be found [here](https://avd.sh/en/stable/roles/eos_designs/doc/fabric-topology-v4.0.html?h=inband#inband-management-vlan).
Details on this feature can be found [here](https://avd.arista.com/3.8/roles/eos_designs/doc/fabric-topology-v4.0.html?h=inband#inband-management-vlan).

| Node | Management0 | Vlan10 |
| ------ | --------------- | --------- |
Expand Down Expand Up @@ -233,7 +233,7 @@ The tabs below show the Ansible **group_vars** used in this example.
```

=== "DC1_NETWORK_PORTS"
Our fabric would not be complete without connecting some devices to it. Therefore, we define port profiles and network port ranges in the **group_vars/DC1_NETWORKS_PORTS.yml** file. A single port_profile may be used across several switches and port ranges. In our example, we create a port profile called `PP-DOT1X` to define generic 802.1x (NAC) settings we wish to apply to a range of ports. The `network_ports` data model is where we define which switches and ports to apply the port profile. This data model allows a single regex statement to define a list of switches. In addition, the variable `switch_ports` expands into a range of ports. You can view more details of the `range_expand` filter [here](https://avd.sh/en/stable/plugins/index.html#range_expand-filter). These variables are applied to spine and leaf nodes since they are a part of this inventory group.
Our fabric would not be complete without connecting some devices to it. Therefore, we define port profiles and network port ranges in the **group_vars/DC1_NETWORKS_PORTS.yml** file. A single port_profile may be used across several switches and port ranges. In our example, we create a port profile called `PP-DOT1X` to define generic 802.1x (NAC) settings we wish to apply to a range of ports. The `network_ports` data model is where we define which switches and ports to apply the port profile. This data model allows a single regex statement to define a list of switches. In addition, the variable `switch_ports` expands into a range of ports. You can view more details of the `range_expand` filter [here](https://avd.arista.com/3.8/plugins/index.html#range_expand-filter). These variables are applied to spine and leaf nodes since they are a part of this inventory group.

``` yaml
--8<--
Expand All @@ -259,7 +259,7 @@ AVD provides a way to standardize and reuse port profiles through a compact data

![Figure: 3](images/dot1x_ports.svg)

The above sample port configuration is easily produced with `port_profiles` and `network_ports` data models. Each port has similar configuration items defined in `port_profiles`, while `network_ports` defines which switches and port ranges are to be applied. The `network_ports` data model allows regex to match switches and an `expand_range` filter to cover a range of ports. For details, see documentation for [`port_profiles`](https://avd.sh/en/stable/roles/eos_designs/doc/connected-endpoints.html#port-profiles) and [`network_ports`](https://avd.sh/en/stable/roles/eos_designs/doc/connected-endpoints.html#network-ports_1).
The above sample port configuration is easily produced with `port_profiles` and `network_ports` data models. Each port has similar configuration items defined in `port_profiles`, while `network_ports` defines which switches and port ranges are to be applied. The `network_ports` data model allows regex to match switches and an `expand_range` filter to cover a range of ports. For details, see documentation for [`port_profiles`](https://avd.arista.com/3.8/roles/eos_designs/doc/connected-endpoints.html#port-profiles) and [`network_ports`](https://avd.arista.com/3.8/roles/eos_designs/doc/connected-endpoints.html#network-ports_1).

## WAN/Core Edge

Expand Down