Add SONiC CLOS network lab

[Giluerre]

Proposed Changes

Add emulated CLOS topology based on sonic-vm and containerlab.

[byteocean]

I had the Connection refused issue when deploy.sh is executed. Is it normal?

Changes detected, applying configuration...
namespace/c9s-clos created
topology.clabernetes.containerlab.dev/clos created
Waiting for services to be ready...
Provisioning SONiC nodes...
Running init_setup.sh on 172.18.1.10
ssh: connect to host 172.18.1.10 port 22: Connection refused
Running init_setup.sh on 172.18.1.11
ssh: connect to host 172.18.1.11 port 22: Connection refused
Running init_setup.sh on 172.18.1.14
ssh: connect to host 172.18.1.14 port 22: Connection refused
Running init_setup.sh on 172.18.1.15
ssh: connect to host 172.18.1.15 port 22: Connection refused

==========================================
SONiC Lab Topology - External IPs
==========================================
client1 -> 172.18.1.12
client2 -> 172.18.1.13
sonic-leaf1 -> 172.18.1.10
sonic-leaf2 -> 172.18.1.11
sonic-spine1 -> 172.18.1.14
sonic-spine2 -> 172.18.1.15

Script ended successfully

[Giluerre]

Regarding the "connection refused" issue: most of the time I don't get this error message, but I have seen it a few times. In those cases, the problem was that the VM did not reach a state where the SSH server was functional during the 180-second sleep period. Could you please try waiting an additional 2 minutes, or change the sleep to 300 seconds, and check whether the issue still persists?

[byteocean]

@Giluerre thanks for replying. I tried with 300 seconds and the setup worked. In other projects, we had similar issues and we used backoff delay during retrying to enhance the experience, because hardcoded 300s is long time to wait.

Another general comments is that, instead of relying on the make setup-test-e2e in the Makefile, which should invoke real tests in my opinion, it would be good to have kind creation/destroying embedded also in your setup script, e.g., deploy.sh. Switching back-and-forth between sub-repos was a bit confusing at beginning.

[byteocean]

thanks @Giluerre. I am able to setup the environment and use agent_cli (e.g., ./agent_cli --address 172.18.1.12:57400 list interfaces) to talk to uploaded agents in VMs.