Doc(eos_designs): Add lab topology for single-dc-l3ls example

[ankudinov]

Change Summary

add clab topology to start testing AVD examples and labs.arista integration
this PR also changes the platform to cEOS

How to test:
start sandbox lab on lab.arista

wget https://github.com/ankudinov/avd/archive/refs/heads/single-dc-l3ls-lab-topo.tar.gz
tar -xvzf single-dc-l3ls-lab-topo.tar.gz
cp -r avd-single-dc-l3ls-lab-topo/ansible_collections/arista/avd/examples/single-dc-l3ls/* .
make start
ansible-playbook build.yml
ansible-playbook deploy.yml
ssh arista@dc1-leaf1-server1
ping 10.10.12.182

check anything else

[github-actions]

Review docs on Read the Docs

To test this pull request:

# Create virtual environment for this testing below the current directory
python -m venv test-avd-pr-6483
# Activate the virtual environment
source test-avd-pr-6483/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/ankudinov/avd.git@single-dc-l3ls-lab-topo#subdirectory=python-avd" --force
# Point Ansible collections path to the Python virtual environment
export ANSIBLE_COLLECTIONS_PATH=$VIRTUAL_ENV/ansible_collections
# Install Ansible collection
python -m ansible.cli.galaxy collection install git+https://github.com/ankudinov/avd.git#/ansible_collections/arista/avd/,single-dc-l3ls-lab-topo --force
cd test-avd-pr-6483
# Run your playbook using `python -m ansible.cli.playbook path/to/playbook.yml ...`

[carl-baillargeon]

In the example documentation, we have a section called "Testing AVD output without a lab". Should we update this section or add a note saying you can try it out with clab, etc.?

[JulioPDX]

In the example documentation, we have a section called "Testing AVD output without a lab". Should we update this section or add a note saying you can try it out with clab, etc.?

Seems like a great use for a all-in-one click here to start lab through Arista backend. Or self-hosted instructions with VsCode and clab installed.

[JulioPDX]

LGTM - This entire workflow is awesome. Like Carl mentioned, we need to add a section that this is available and how to get started if outside of the Arista backend labs. I know we need to get one of these merged to start backend testing. We can update the readme in a near future PR.

[joelbreton2]

LGTM

[gmuloc]

In the example documentation, we have a section called "Testing AVD output without a lab". Should we update this section or add a note saying you can try it out with clab, etc.?

https://github.com/aristanetworks/avd-internal/issues/349

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ClausHolbechArista]

please use ntp.pool.org pool.ntp.org

[ankudinov]

ack. can be changed. this is coming from acLabs templates, but I'm happy to adjust it

[ClausHolbechArista]

I don't think this will work well without vxlan. Use virtual-router

[ankudinov]

this is wrong - has to be simple ip address =)
I'm surprised this actually worked in my lab

[ClausHolbechArista]

this route looks wrong.

[ankudinov]

why? valid route and the remote host was reachable. What do I miss?

[ClausHolbechArista]

this should call out cEOS-lab since cEOS can also be something else.