Add SVI Example for Arista EOS platform

[JacksonIsaac]

SUMMARY

Add SVI Example for Arista EOS platform

Refers #40323 and ansible/community#311

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

eos_l3_interface

ANSIBLE VERSION

ansible 2.6.0
  config file = None
  configured module search path = ['/Users/jacksonisaac/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /anaconda3/lib/python3.6/site-packages/ansible-2.6.0-py3.6.egg/ansible
  executable location = /anaconda3/bin/ansible
  python version = 3.6.4 |Anaconda, Inc.| (default, Jan 16 2018, 12:04:33) [GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)]

ADDITIONAL INFORMATION

N/A. Just replicating #40021

[ansibot]

cc @ganeshrn @privateip @trishnaguha
click here for bot help

[IPvSean]

@JacksonIsaac based on the speed and have 5 identical pull requests I think we are going to institute a new policy for pull requests for the contest. I went ahead and "tested" this one for you to show you what we are looking for since I was not clear. Tagging @gundalow and @acozine for awareness and commentary.

This is still super easy, I just want pull requests to do the bare minimum of testing->

• provide the output of the playbook being run
• run the show command on the network device so we know the playbook was actually executed

For this pull request->

➜  ansible-napalm-samples git:(master) ✗ ansible-playbook test.yml

PLAY [arista] ********************************************************************************************************************************************************************

TASK [Set interface Vlan1 (SVI) IPv4 address] ************************************************************************************************************************************
changed: [eos]

PLAY RECAP ***********************************************************************************************************************************************************************
eos                        : ok=1    changed=1    unreachable=0    failed=0

and I can check that it ran properly->

eos#sh run int vlan1
interface Vlan1
   ip address 192.168.0.5/24

and we will go ahead and accept this pull request now that it is tested, I would like you to provide the output for the 4 other pull requests.

[JacksonIsaac]

Hi @IPvSean I was actually stuck at setting up the environment due to limited internet. I tried to boot up a VM on AWS so that I don't need to worry about network issues etc. but was unable to do so.

I even tried to use VyOS VMI and again didn't understand how exactly I could setup vagrant and vbox, so tried to run a Windows RDP on AWS and was still figuring things out.

[IPvSean]

@JacksonIsaac I can help you out on VyOS-> https://github.com/network-automation/linklight/tree/master/vagrant-demo

[JacksonIsaac]

@IPvSean Yes I was following this link only as mentioned by you on one of the other PRs :)

[JacksonIsaac]

Just figuring out to setup the environment on Cloud VM

[JacksonIsaac]

@IPvSean Any way I can test this ansible-playbook on AWS (or any other cloud platform) for different OSes I have opened PR for ? I am having difficulty setting up vagrant on my local machine.

[JacksonIsaac]

I have followed the steps given in the vagrant-demo link and tried to run the exercise01/backup.yml. I kept on getting some or the other error while setting up the complete cluser of leaf0x, spine0x and ansible. I then modified the Vagrantfile to run only VyOS i.e., leaf01 and tried ansible-playbook backup.yml -u vagrant -k

It keeps on giving an error saying

[WARNING]: Unable to parse /etc/ansible/hosts as an inventory source

[WARNING]: No inventory was parsed, only implicit localhost is available

[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [network] **********************************************************************************************************************************************************************

skipping: no hosts matched

I also tried putting the following code in Vagrantfile itself and still couldn't figure out where I am going wrong.

config.vm.provision "ansible" do |ansible|  
  ansible.verbose = "v"
  ansible.playbook = "training-course/exercise01/backup.yml"
end

[JacksonIsaac]

Ah okay, I figured this step out. I had to run vagrant provision leaf01 and it executed the ansible playbook for me :)

[IPvSean]

hey @JacksonIsaac this PR is good, please continue conversations about problems (e.g. VyOS) on the respective PR. This Arista one looks good and I am going to tell @acozine to accept the PR!

[acozine]

Thanks @JacksonIsaac for contributing to the documentation!