Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
goSDN
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Terraform modules
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
danet
goSDN
Wiki
Testing with cEOS
Changes
Page history
New page
Templates
Clone repository
Create Testing with cEOS
authored
3 years ago
by
Andre Sterba
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Testing-with-cEOS.md
+51
-0
51 additions, 0 deletions
Testing-with-cEOS.md
with
51 additions
and
0 deletions
Testing-with-cEOS.md
0 → 100644
View page @
28f8e8e8
1.
Install
[
containerlab
](
https://containerlab.srlinux.dev/install/
)
on your machine.
***containerlab and cEOS do not work with cgroupsv2 enabled!***
This is tracked in this
[
upstream issue
](
https://github.com/srl-labs/containerlab/issues/467
)
.
Switch back to cgroupsv1 with the following kernel paramenter
`systemd.unified_cgroup_hierarchy=0`
.
2.
Use the following config to get two cEOS containers running.
```
yaml
name
:
gosdn-arista-base-topo
mgmt
:
network
:
gosdn-dev-net
topology
:
kinds
:
ceos
:
image
:
registry.code.fbi.h-da.de/danet/gosdn/ceos:latest
nodes
:
ceos0
:
kind
:
ceos
ceos1a
:
kind
:
ceos
links
:
-
endpoints
:
[
"
ceos0:eth1"
,
"
ceos1a:eth1"
]
```
3.
Run
`containerlab deploy --topo development.clab.yaml`
to deploy and
`containerlab destroy --topo development.clab.yaml`
to destroy the stack.
4.
You should now start the controller and init the gosdn-cli with
`gosdnc --controller 127.0.0.1:55055 init`
.
5.
Add a new device with
`./gosdnc dev create -a 172.20.20.2:6030 -u admin -p admin --name='test-ceos-1'`
and remember the UUID of the device.
```
sh
➜ gosdnc dev list
INFO[0000] OND 1: name: dev1, uuid: 5fb6e872-220d-492d-bf92-0d63a84d9841
```
6.
Test if you can get the hostname of the device via gNMI.
```
sh
➜ gosdnc dev get 5fb6e872-220d-492d-bf92-0d63a84d9841 /system/config/hostname
INFO[0000] timestamp:1643195928009506201 ond:
{
id
:
"5fb6e872-220d-492d-bf92-0d63a84d9841"
name:
"dev1"
device:
{
timestamp:1643195928009490650 update:
{
path:
{
element:
"system"
element:
"config"
element:
"hostname"
}
val:
{
string_val:
"ceos1a"
}}}}
<nil>
```
7.
You can also use
[
gnmic
](
https://gnmic.kmrd.dev/
)
to debug issues with cEOS.
```
sh
gnmic
-a
172.20.20.2:6030
-u
admin
-p
admin
--insecure
capabilities
```
This diff is collapsed.
Click to expand it.