Hi,

I am trying to install Openness Single-node Network Edge cluster Mode in AWS Ec2 Centos 7 Linux VM.

I am able to configure complete the preconditions as per documentation
Setup static hostname
Exchanging SSH keys between hosts).
Configuring inventory).- inventory .ini

Since i was facing some dependency errors
I have skipped kernel and tune profile as mentioned in some of the forums.
by setting kernel_skip :true and tuned_skip: true.

After making the above setting ,I am able to execute "./deploy_ne.sh single " with root access.
As a part of installation/deployment , the system rebooted.

Even though the system is up and"Running" in aws console, I am not able to connect to the system using WINSCP and facing "Connection Timeout" error.

kernel is crashing in centos after reboot once setup script is finished in virtual box

Hi Openness Team,

We have deployed edgenode in On-Premise IAC mode our our test setup. We have followed the on-premises-applications-onboarding guide link
https://github.com/open-ness/specs/blob/master/doc/applications-onboard/on-premises-applications-onboarding.md
to deploy container app on the edge-node m/c .

Following is our test setup :

We are following the following steps mentioned in the link to assgn ip address to the KNI interaface:

docker exec -it <app_docker_id> /bin/bash
ip link set dev vEth2 arp off
ip a a 192.168.10.25/24 dev vEth2
ip link set dev vEth2 up
wget 192.168.10.100 -Y off

Now , I want to assign this ip address dynamically through DHCP . For this, we have configured DHCP server on the downstream machine connected to downstream machine and trying to assign ip address on vEth1 through dhclient.

But vEth1 is not getting any ip address.

Can you please let us know why this is happening and how can we achieve our objective of assigning ip-address dynamically inside container app without running the manual steps mentioned above inside the app container ( ip link set dev vEth2 arp off and wget 192.168.10.100 -Y off commands ) .

Thanks and Regards,
Ashish Saxena

(nes_client) # show rings
ID: Name: Received: Sent: Dropped Ring Full: Dropped No Route:
0 NIS_UPSTR_GTPU N/A pkts N/A pkts N/A pkts N/A pkts
1 NIS_UPSTR_GTPC N/A pkts N/A pkts N/A pkts N/A pkts
2 NIS_UPSTR_RNIS N/A pkts N/A pkts N/A pkts N/A pkts
3 NIS_UPSTR_SCTP N/A pkts N/A pkts N/A pkts N/A pkts
4 NIS_DWSTR_GTPU N/A pkts N/A pkts N/A pkts N/A pkts
5 NIS_DWSTR_GTPC N/A pkts N/A pkts N/A pkts N/A pkts
6 NIS_DWSTR_RNIS N/A pkts N/A pkts N/A pkts N/A pkts
7 NIS_DWSTR_SCTP N/A pkts N/A pkts N/A pkts N/A pkts
8 NTS_UPSTR_GTPU N/A pkts N/A pkts N/A pkts N/A pkts
9 NTS_DWSTR_GTPU N/A pkts N/A pkts N/A pkts N/A pkts
10 NTS_UPSTR_IP N/A pkts N/A pkts N/A pkts N/A pkts
11 NTS_DWSTR_IP N/A pkts N/A pkts N/A pkts N/A pkts
12 NTS_LBP_ANY N/A pkts N/A pkts N/A pkts N/A pkts
13 PORT_0_IO_ANY N/A pkts N/A pkts N/A pkts N/A pkts
14 PORT_1_IO_ANY N/A pkts N/A pkts N/A pkts N/A pkts
15 PORT_2_IO_ANY N/A pkts N/A pkts N/A pkts N/A pkts

Hi OpenNESS team,

I've deployed the controller&node on-premise option and I've instantiated a simply nginx container on the edge node.

App is up and running but 80 port is not exposed even when i made a policy allowing 80 port and
the port is included in the application configuration:

How can I expose this port? I'm looking for something like:

Thank you

Issue

Cannot build docker image for fpga-opae.
It originally happened during installation of OpenNESS. See: https://github.com/open-ness/converged-edge-experience-kits/blob/master/roles/kubernetes/opae_fpga/node/tasks/main.yml#L42

How to reproduce

It happened during ansible OpenNESS installation, but it can be reproduced more easly at https://github.com/open-ness/edgeservices repo level.

1. Clone this repo.
2. Run make fpga-opae.

$ make fpga-opae
...
Step 25/30 : RUN echo "proxy=$http_proxy/" | sudo tee -a /etc/yum.conf
 ---> Running in 24c68f8e724f
proxy=/
Removing intermediate container 24c68f8e724f
 ---> 79bcd801af6f
Step 26/30 : RUN sudo yum clean expire-cache
 ---> Running in 4c1c3d2f758c
Loaded plugins: fastestmirror, ovl
Options error: Error parsing "proxy = '/'": URL must be http, ftp, https, socks4, socks4a, socks5 or socks5h not ""
The command '/bin/sh -c sudo yum clean expire-cache' returned a non-zero code: 1
make: *** [fpga-opae] Error 1

Possible solution

Check if http_proxy variable exists in the Dockerfile.

The GA requirements for the Kubernetes CSR Duration KEP state:

Inform external signer implementations of the spec.expirationSeconds field

smart-edge-open/edgeservices is an external signer implementation. This diff outlines how this signer may be updated to honor this new field:

diff --git a/pkg/certsigner/certsigner.go b/pkg/certsigner/certsigner.go
index 927299b..96bedf1 100644
--- a/pkg/certsigner/certsigner.go
+++ b/pkg/certsigner/certsigner.go
@@ -22,6 +22,7 @@ import (
 	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
 	"k8s.io/client-go/informers"
 	"k8s.io/client-go/kubernetes"
+	"k8s.io/client-go/util/certificate/csr"
 	capihelper "k8s.io/kubernetes/pkg/apis/certificates/v1"
 	"k8s.io/kubernetes/pkg/controller/certificates"
 	"k8s.io/kubernetes/pkg/controller/certificates/authority"
@@ -99,7 +100,7 @@ func (c *CertificateSigner) handleCSR(csr *capi.CertificateSigningRequest) error
 	}
 
 	certData, err := c.ca.Sign(x509cr.Raw, authority.PermissiveSigningPolicy{
-		TTL:    c.cfg.CertTTL.Duration,
+		TTL:    c.duration(csr.Spec.ExpirationSeconds),
 		Usages: csr.Spec.Usages,
 	})
 	if err != nil {
@@ -118,6 +119,28 @@ func (c *CertificateSigner) handleCSR(csr *capi.CertificateSigningRequest) error
 	return nil
 }
 
+func (c *CertificateSigner) duration(expirationSeconds *int32) time.Duration {
+	defaultDuration := c.cfg.CertTTL.Duration
+
+	if expirationSeconds == nil {
+		return defaultDuration
+	}
+
+	// honor requested duration is if it is less than the default TTL
+	// use 10 min (2x hard coded backdate above) as a sanity check lower bound
+	const min = 10 * time.Minute
+	switch requestedDuration := csr.ExpirationSecondsToDuration(*expirationSeconds); {
+	case requestedDuration > defaultDuration:
+		return defaultDuration
+
+	case requestedDuration < min:
+		return min
+
+	default:
+		return requestedDuration
+	}
+}
+
 func loadCA(certPath, keyPath string) (authority.CertificateAuthority, error) {
 	caCert, err := tls.LoadX509KeyPair(certPath, keyPath)
 	if err != nil {

Note that this requires Kubernetes v1.22+

get_node_service does not filter services for given node. Function does not exit with "Service '${svc}' not found on node '${node}'" if service is found on other node(s).

Hi Openness Team,

We have been following the getting started and applications onboarding documentation for deploying Openness and trying to run our test application on Edge Node.

We want to run end-to-end bump in the wire scenario on the setup.

Attached is our test setup:

We are using On-Premise mode for deploying the Controller and Edgenode.

Test Application is deployed as a container on the Edge Node. All the m/c have ip address in the same subnet. We have created traffic rule to accept the packets with destination ip address 50.50.50.50 . We are pinging the same ip address from the upstream m/c, and after applying the traffic rule on the test application container ,the icmp request packets are received inside the Container app .

Now , we want the packets to reach the downstream machine. Earlier , on Openness version 19.09 , we were able to achieve this by adding appropriate route on the container app , but after upgrading to the latest version 19.12 , we are not able to receive the packets at the downstream m/c .
From the nes_client cli , it is observed that the count for received and send packets has been increasing at the KNI interface which means container is sending out the packets , but the packets are not reaching the downstream interface.
Below are the cli stats:

show all

ID: Name: Received: Sent: Dropped(TX full): Dropped(HW): IP Fragmented(Forwarded):
0 0000:60:00.0 38258 pkts 30587 pkts 0 pkts 0 pkts 0 pkts
(ac:1f:6b:6b:49:84) 10378488 bytes 9747584 bytes 0 bytes
1 0000:60:00.1 624 pkts 31597 pkts 0 pkts 0 pkts 0 pkts
(ac:1f:6b:6b:49:85) 47042 bytes 9845566 bytes 0 bytes
2 KNI 2 pkts 0 pkts 0 pkts 0 pkts 0 pkts
(26:f6:c3:98:bb:5e) 148 bytes 0 bytes 0 bytes
3 KNI 2857 pkts 0 pkts 0 pkts 0 pkts 0 pkts
(not registered) 476358 bytes 0 bytes 0 bytes
4 KNI 2687 pkts 0 pkts 0 pkts 0 pkts 0 pkts
(not registered) 449010 bytes 0 bytes 0 bytes
5 KNI 2497 pkts 0 pkts 0 pkts 0 pkts 0 pkts
(not registered) 415830 bytes 0 bytes 0 bytes
6 KNI 2074 pkts 0 pkts 0 pkts 0 pkts 0 pkts
(not registered) 344188 bytes 0 bytes 0 bytes
7 KNI 6801 pkts 6817 pkts 0 pkts 0 pkts 0 pkts
(ce:8d:eb:0c:fb:18) 668994 bytes 668066 bytes 0 bytes

Can you please help us in resolving the issue to run our test scenario.

Thanks and Regards,
Ashish

I'm trying to test LBO capability of NTS when deployed onprems (experience-kit-20.03). However, when adding a breakout interface from the controller WebUI, as suggested in the Preparing set-up for Local Breakout Point (LBP), I get the error in the screenshot and nts stops.

From the nts container running in the node, I can see these error messages:

NES: [ERR] Missing: section PORT2, entry lbp-mac, in config file.
NES: [ERR] Failed to add dataplane rules.
NES: [ERR] Could not initialize nes ACL.
NES: [ERR] Could not initialize ctrl.

Any ideas of what is wrong?

While I try to get the config file, here some references in the code and a more complete log of nts:
https://github.com/open-ness/edgenode/blob/6b6a486b7258078965103cd332285b2e1f8e5b35/internal/nts/daemon/nts/nts_acl.c#L135-L138
https://github.com/open-ness/edgenode/blob/6b6a486b7258078965103cd332285b2e1f8e5b35/internal/nts/daemon/nts/nts_acl.c#L444-L448

$ sudo docker logs --follow nts

Starting to listen on socket /var/lib/appliance/nts/control-socket

NES: [INFO] No "DNS" in config file, DNS agent won't start
NES: [WARNING] DNS agent not working
NES: [INFO] NTS_IO started
NES: [INFO] NES_IO started
NES: [INFO] KNI initialized
VHOST_CONFIG: vhost-user server: socket created, fd: 1061
VHOST_CONFIG: bind to /var/lib/appliance/nts/qemu/usvhost-1
NES: [INFO] Accepted connection on descriptor 1066 (/var/lib/appliance/nts/control-socket)
NES: [INFO] Client disconnected, sock_fd: 1066
NES: [INFO] Accepted connection on descriptor 1066 (/var/lib/appliance/nts/control-socket)
NES: [INFO] Allocating KNI port 0
KNI: pci: 00:00:00 	 00:00
NES: [INFO] New KNI device registered, waiting to be authorized.
NES: [INFO] KNI inteface vEth0 has been created for 2f6396e2f54f7016d2919e32de16524b7b5a86173fcaa236fc5c427c48c5dd6e
KNI DAEMON: [ERROR] kni_docker_daemon(187): Failed to remove the KNI inteface for 2f6396e2f54f7016d2919e32de16524b7b5a86173fcaa236fc5c427c48c5dd6e
NES: [INFO] Client disconnected, sock_fd: 1066
KNI DAEMON: [INFO] kni_docker_daemon(232): vEth0 attached to 2f6396e2f54f7016d2919e32de16524b7b5a86173fcaa236fc5c427c48c5dd6e, namespace[/var/run/docker/netns/1fa92e00f5e3]
NES: [INFO] Accepted connection on descriptor 1066 (/var/lib/appliance/nts/control-socket)
NES: [INFO] Adding authorization entry for MAC: 4a:24:65:d1:f6:21
NES: [WARNING] Overlapping rule: prio:5,enb_ip:0.0.0.0/0,srv_ip:53.53.53.53/32
NES: [INFO] Client disconnected, sock_fd: 1066
NES: [INFO] Accepted connection on descriptor 1066 (/var/lib/appliance/nts/control-socket)
NES: [INFO] Removing KNI interface for 2f6396e2f54f7016d2919e32de16524b7b5a86173fcaa236fc5c427c48c5dd6e
NES: [INFO] Removing KNI device 0
NES: [INFO] KNI device 0 removed
KNI DAEMON: [INFO] kni_docker_daemon(240): vEth0 removed from 2f6396e2f54f7016d2919e32de16524b7b5a86173fcaa236fc5c427c48c5dd6e, namespace[/var/run/docker/netns/1fa92e00f5e3]
NES: [INFO] Client disconnected, sock_fd: 1066
NES: [INFO] Accepted connection on descriptor 1066 (/var/lib/appliance/nts/control-socket)
NES: [INFO] No more entries in NTS_ACL_LOOKUP_0
NES: [INFO] Client disconnected, sock_fd: 1066
NES: [INFO] Signal received, exiting now...
EAL: Detected 6 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/vhost-1/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
OVS DAEMON: [INFO] ovs_docker_daemon(277): OVS disabled - shutting down
KNI DAEMON: [INFO] kni_docker_daemon(305): [Started]
KNI DAEMON: [INFO] kni_docker_daemon(306): Waiting for containers events
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:0b:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:13:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:1b:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
NES: [INFO] Could not load config file /opt/intel/nev_sdk/nes_root/scripts/nes.cfg.
NES: [INFO] Port 1 initialized and started
NES: [INFO] 
Checking link status for 1 port
NES: [INFO] Port 1 Link Up - speed 10000 Mbps - full-duplex
NES: [INFO] done
NES: [INFO] DPDK port: 1 PCI address: 0000:13:00.0 MAC address: 00:0c:29:0a:6b:46
USER1: rte_ip_frag_table_create: allocated of 402653312 bytes at socket 0
NES: [INFO] Port 2 initialized and started
NES: [INFO] 
Checking link status for 2 port
NES: [INFO] Port 2 Link Up - speed 10000 Mbps - full-duplex
NES: [INFO] done
NES: [INFO] DPDK port: 2 PCI address: 0000:1b:00.0 MAC address: 00:0c:29:0a:6b:50
USER1: rte_ip_frag_table_create: allocated of 402653312 bytes at socket 0
NES: [INFO] Port 0 initialized and started
NES: [INFO] 
Checking link status for 0 port
NES: [INFO] Port 0 Link Up - speed 10000 Mbps - full-duplex
NES: [INFO] done
NES: [INFO] DPDK port: 0 PCI address: 0000:0b:00.0 MAC address: 00:0c:29:0a:6b:3c
USER1: rte_ip_frag_table_create: allocated of 402653312 bytes at socket 0
NES: [INFO] NIS_IO started
NES: [INFO] Starting nes_ctrl_main
NES: [ERR] Missing: section PORT2, entry lbp-mac, in config file.
NES: [ERR] Failed to add dataplane rules.
NES: [ERR] Could not initialize nes ACL.
NES: [ERR] Could not initialize ctrl.
NES: [INFO] No "DNS" in config file, DNS agent won't start
NES: [WARNING] DNS agent not working
NES: [INFO] NTS_IO started
NES: [INFO] KNI initialized
VHOST_CONFIG: vhost-user server: socket created, fd: 1061
VHOST_CONFIG: bind to /var/lib/appliance/nts/qemu/usvhost-1
NES: [INFO] Lcore 4 stopped

When using command tool "go mod download" to cache all third-party dependency libraries, it failed while go version was 1.14, but if the go version was lower than 1.14, command tool "go mod download" would work right.

[root@controller edgenode]# gvm use go1.14
Now using version go1.14
[root@controller edgenode]# go version
go version go1.14 linux/amd64
[root@controller edgenode]# go mod download
go: errors parsing go.mod:
/root/edgenode/go.mod:6: usage: go 1.23
[root@controller edgenode]#

Hi, when I ran 03_build_and_deploy.sh, the script terminated at "Building images" step. So following by your instructions, I ran ./scripts/ansible/common/scripts/reinstall-urllib3-module.sh and then re-run 03_build_and_deploy.sh. However, it seemd like it did not work. Could you please tell me how to fix it? The output is as follows. Thank you very much!

TASK [Build images] *****************************************************************************************************************
fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": "source /etc/profile && RTE_SDK=/opt/dpdk-18.08 RTE_TARGET=x86_64-native-linuxapp-gcc make build-docker", "delta": "0:00:53.418771", "end": "2019-10-08 10:52:02.253623", "msg": "non-zero return code", "rc": 2, "start": "2019-10-08 10:51:08.834852", "stderr": "/usr/lib/python2.7/site-packages/requests/init.py:91: RequestsDependencyWarning: urllib3 (1.25.6) or chardet (3.0.4) doesn't match a supported version!\n RequestsDependencyWarning)\nThe NTS_MEM_MB_S0 variable is not set. Defaulting to a blank string.\nThe NTS_MEM_MB_S1 variable is not set. Defaulting to a blank string.\nThe REMOTE_SYSLOG_IP variable is not set. Defaulting to a blank string.\nsyslog-ng uses an image, skipping\nBuilding edgednssvr\nService 'edgednssvr' failed to build: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)\nmake: *** [build-docker] Error 1", "stderr_lines": ["/usr/lib/python2.7/site-packages/requests/init.py:91: RequestsDependencyWarning: urllib3 (1.25.6) or chardet (3.0.4) doesn't match a supported version!", " RequestsDependencyWarning)", "The NTS_MEM_MB_S0 variable is not set. Defaulting to a blank string.", "The NTS_MEM_MB_S1 variable is not set. Defaulting to a blank string.", "The REMOTE_SYSLOG_IP variable is not set. Defaulting to a blank string.", "syslog-ng uses an image, skipping", "Building edgednssvr", "Service 'edgednssvr' failed to build: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)", "make: *** [build-docker] Error 1"], "stdout": "make -C internal/nts/eda_libs\nmake[1]: Entering directory /root/edgenode/internal/nts/eda_libs'\nmake[1]: build' is up to date.\nmake[1]: Leaving directory /root/edgenode/internal/nts/eda_libs'\nmkdir -p \"dist\"\nGOOS=linux go build -o \"dist/appliance\" ./cmd/appliance\nmkdir -p \"dist\"\nGOOS=linux go build -a --ldflags '-extldflags \"-static\"' -tags netgo -installsuffix netgo -o \"dist/edgednssvr\" ./cmd/edgednssvr\nmake -C internal/nts\nmake[1]: Entering directory /root/edgenode/internal/nts'\n== libs\n== libnes_api\nmake[4]: Nothing to be done for libnes_sq.o'.\n== libnes_cfgfile\n== libnes_daemon\n== libnes_lookup\n== libnes_queue\n== libnes_sq\n== libnes_acl\n== libnes_api_shared\nmake[4]: Nothing to be done for libnes_api.o'.\n/root/edgenode/internal/nts//build/lib must be added to /etc/ld.so.conf or LD_LIBRARY_PATH variable to allow binary to link with dynamic library\n== daemon\nmake[3]: Nothing to be done for nis_io.o'.\n== client\nmake[1]: Leaving directory /root/edgenode/internal/nts'\ncp build/appliance/Dockerfile "/tmp/tmp.5HO3pXV7ty/Dockerfile_appliance"\ncp build/appliance/entrypoint.sh "/tmp/tmp.5HO3pXV7ty"\ncp /opt/dpdk-18.08/usertools/dpdk-devbind.py "/tmp/tmp.5HO3pXV7ty"\ncp "dist/appliance" "/tmp/tmp.5HO3pXV7ty"\ncp build/edgednssvr/Dockerfile "/tmp/tmp.5HO3pXV7ty/Dockerfile_edgednssvr"\ncp "dist/edgednssvr" "/tmp/tmp.5HO3pXV7ty"\nmkdir -p "/tmp/tmp.5HO3pXV7ty/nts"\ncp internal/nts/build/nes-daemon "/tmp/tmp.5HO3pXV7ty/nts"\ncp internal/nts/kni_docker_daemon.py "/tmp/tmp.5HO3pXV7ty/nts"\ncp internal/nts/entrypoint.sh "/tmp/tmp.5HO3pXV7ty/nts"\ncp internal/nts/build/libnes_api_shared.so "/tmp/tmp.5HO3pXV7ty/nts"\ncp internal/nts/Dockerfile "/tmp/tmp.5HO3pXV7ty/Dockerfile_nts"\ncp docker-compose.yml "/tmp/tmp.5HO3pXV7ty"\ncd "/tmp/tmp.5HO3pXV7ty" && VER=1.0 docker-compose build\nStep 1/5 : FROM alpine:latest", "stdout_lines": ["make -C internal/nts/eda_libs", "make[1]: Entering directory /root/edgenode/internal/nts/eda_libs'", "make[1]: build' is up to date.", "make[1]: Leaving directory /root/edgenode/internal/nts/eda_libs'", "mkdir -p \"dist\"", "GOOS=linux go build -o \"dist/appliance\" ./cmd/appliance", "mkdir -p \"dist\"", "GOOS=linux go build -a --ldflags '-extldflags \"-static\"' -tags netgo -installsuffix netgo -o \"dist/edgednssvr\" ./cmd/edgednssvr", "make -C internal/nts", "make[1]: Entering directory /root/edgenode/internal/nts'", "== libs", "== libnes_api", "make[4]: Nothing to be done for libnes_sq.o'.", "== libnes_cfgfile", "== libnes_daemon", "== libnes_lookup", "== libnes_queue", "== libnes_sq", "== libnes_acl", "== libnes_api_shared", "make[4]: Nothing to be done for libnes_api.o'.", "/root/edgenode/internal/nts//build/lib must be added to /etc/ld.so.conf or LD_LIBRARY_PATH variable to allow binary to link with dynamic library", "== daemon", "make[3]: Nothing to be done for nis_io.o'.", "== client", "make[1]: Leaving directory /root/edgenode/internal/nts'", "cp build/appliance/Dockerfile "/tmp/tmp.5HO3pXV7ty/Dockerfile_appliance"", "cp build/appliance/entrypoint.sh "/tmp/tmp.5HO3pXV7ty"", "cp /opt/dpdk-18.08/usertools/dpdk-devbind.py "/tmp/tmp.5HO3pXV7ty"", "cp "dist/appliance" "/tmp/tmp.5HO3pXV7ty"", "cp build/edgednssvr/Dockerfile "/tmp/tmp.5HO3pXV7ty/Dockerfile_edgednssvr"", "cp "dist/edgednssvr" "/tmp/tmp.5HO3pXV7ty"", "mkdir -p "/tmp/tmp.5HO3pXV7ty/nts"", "cp internal/nts/build/nes-daemon "/tmp/tmp.5HO3pXV7ty/nts"", "cp internal/nts/kni_docker_daemon.py "/tmp/tmp.5HO3pXV7ty/nts"", "cp internal/nts/entrypoint.sh "/tmp/tmp.5HO3pXV7ty/nts"", "cp internal/nts/build/libnes_api_shared.so "/tmp/tmp.5HO3pXV7ty/nts"", "cp internal/nts/Dockerfile "/tmp/tmp.5HO3pXV7ty/Dockerfile_nts"", "cp docker-compose.yml "/tmp/tmp.5HO3pXV7ty"", "cd "/tmp/tmp.5HO3pXV7ty" && VER=1.0 docker-compose build", "Step 1/5 : FROM alpine:latest"]}
PLAY RECAP **************************************************************************************************************************
127.0.0.1 : ok=30 changed=5 unreachable=0 failed=1 skipped=6 rescued=0 ignored=0

Need change sudo version from sudo=1.9.0-r0 => sudo=1.9.5p2-r0

GOOS=linux go build -a --ldflags '-extldflags "-static"' -tags netgo -installsuffix netgo -o ./dist/edgednssvr/edgednssvr ./cmd/edgednssvr
VER=1.0 docker-compose build edgednssvr
Step 1/15 : FROM alpine:3.12.0 AS edgedns-deps-image
---> a24bb4013296
Step 2/15 : RUN printf "http://nl.alpinelinux.org/alpine/v3.12/main\nhttp://nl.alpinelinux.org/alpine/v3.12/community" >> /etc/apk/repositories
---> Running in 58a1c5acf93b
Removing intermediate container 58a1c5acf93b
---> 6827dc6bfa5e
Step 3/15 : RUN apk add --no-cache sudo=1.9.0-r0
---> Running in 522348f69fb0
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz
fetch http://nl.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz
fetch http://nl.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz
^[[91mERROR: unsatisfiable constraints:
^[[0m sudo-1.9.5p2-r0:
breaks: world[sudo=1.9.0-r0]

I have deployed 20.03 on_premise (onprem_dataplane: "ovncni")

docker/openness services do not appear appear to be start when an edge node reboots. I don't seem to be able to find any guidelines on the procedure for restarting services.

(Edge node still appears in controller UI, but just returns a 500 error on any attempt to edit)

Currently my only workaround is a full re-deployment via deploy_onprem.sh which isn't practical, particularly when using several edge nodes.

Hi ,

Please help in finding out in which module are the Controller APIs are implemented ?

Thanks and Regards
Abhijit