...
This will allow connecting to VMs and pods directly from the Lab Network. Please replace the sample IPs with your IP addresses. Please replace the interface name (eno24 used in the example) with you server's interface name.
| Code Block | ||
|---|---|---|
| ||
cat <<\EOF >> netdefault.xml
<network>
<name>default</name>
<bridge name="vmbr0"/>
<forward mode='route' dev='eno24'/>
# <forward/>
<ip address="10.121.7.129" netmask="255.255.255.224">
<dhcp>
<range start="10.121.7.144" end="10.121.7.158"/>
</dhcp>
</ip>
</network>
EOF
sudo virsh net-list
sudo virsh net-destroy default
sudo virsh net-undefine default
sudo virsh net-define netdefault.xml
sudo virsh net-start default
sudo virsh net-autostart default |
...
EMCO Deployment Verification
Perform the following steps to verify correct EMCO deployment:
| Code Block | ||
|---|---|---|
| ||
# Determine IP address of EMCO VM:
[onaplab@os12 ~]$ sudo virsh list --all
Id Name State
----------------------------------------------------
6 amcop-vm-01 running
9 edge_k8s-1 running
10 edge_k8s-2 running
[onaplab@os12 ~]$ sudo domifaddr amcop-vm-01
sudo: domifaddr: command not found
[onaplab@os12 ~]$ sudo virsh domifaddr amcop-vm-01
Name MAC address Protocol Address
-------------------------------------------------------------------------------
vnet0 52:54:00:1a:8e:8b ipv4 10.121.7.145/27
# ssh to EMCO VM. You should be able to ssh without specifying the key:
[onaplab@os12 ~]$ ssh onaplab@10.121.7.145
# Verify K8S pods:
onaplab@emco:~$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-6f954885fb-bb2mr 1/1 Running 0 28d
kube-system calico-node-ldcpv 1/1 Running 0 28d
kube-system coredns-6b968665c4-6558h 1/1 Running 0 28d
kube-system coredns-6b968665c4-rq6bf 0/1 Pending 0 28d
kube-system dns-autoscaler-5fc5fdbf6-njch7 1/1 Running 0 28d
kube-system kube-apiserver-node1 1/1 Running 0 28d
kube-system kube-controller-manager-node1 1/1 Running 0 28d
kube-system kube-proxy-gg95d 1/1 Running 0 28d
kube-system kube-scheduler-node1 1/1 Running 0 28d
kube-system kubernetes-dashboard-6c7466966c-cjpxm 1/1 Running 0 28d
kube-system nodelocaldns-7pxcs 1/1 Running 0 28d
kube-system tiller-deploy-8756df4d9-zq52m 1/1 Running 0 28d
onap dev-cassandra-0 1/1 Running 0 28d
onap dev-cassandra-1 1/1 Running 0 28d
onap dev-cassandra-2 1/1 Running 0 28d
onap dev-cds-blueprints-processor-6d697cc4d6-wzlfj 0/1 Init:1/3 0 28d
onap dev-cds-db-0 1/1 Running 0 28d
onap dev-cds-py-executor-7dcdc5f7f6-tpfmg 1/1 Running 0 28d
onap dev-cds-sdc-listener-f99d4588d-nt2tk 0/1 Init:0/1 4021 28d
onap dev-cds-ui-7768bb4b-cfbzd 1/1 Running 0 28d
onap dev-mariadb-galera-0 1/1 Running 0 28d
onap dev-mariadb-galera-1 1/1 Running 0 28d
onap dev-mariadb-galera-2 1/1 Running 0 28d
onap4k8s clm-668c45d96d-99gpb 1/1 Running 0 28d
onap4k8s emcoui-57846bd5df-c774f 1/1 Running 0 28d
onap4k8s etcd-768d5b6cc-ptmmr 1/1 Running 0 28d
onap4k8s middleend-6d67c9bf54-tvs7s 1/1 Running 0 28d
onap4k8s mongo-7988cb488b-kf29q 1/1 Running 0 28d
onap4k8s ncm-9f4b85787-nqnlm 1/1 Running 0 28d
onap4k8s orchestrator-5fd4845f8f-qsxlf 1/1 Running 0 28d
onap4k8s ovnaction-f794f65b6-w85ms 1/1 Running 0 28d
onap4k8s rsync-7d9f5fbd9b-r72sp 1/1 Running 0 28d
# Verify K8S services:
onaplab@emco:~$ kubectl get svc --all-namespaces
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.233.0.1 <none> 443/TCP 28d
kube-system coredns ClusterIP 10.233.0.3 <none> 53/UDP,53/TCP,9153/TCP 28d
kube-system kubernetes-dashboard ClusterIP 10.233.35.188 <none> 443/TCP 28d
kube-system tiller-deploy ClusterIP 10.233.33.249 <none> 44134/TCP 28d
onap cassandra ClusterIP None <none> 7000/TCP,7001/TCP,7199/TCP,9042/TCP,9160/TCP,61621/TCP 28d
onap cds-blueprints-processor-cluster ClusterIP 10.233.4.219 <none> 5701/TCP 28d
onap cds-blueprints-processor-grpc ClusterIP 10.233.34.1 <none> 9111/TCP 28d
onap cds-blueprints-processor-http ClusterIP 10.233.31.74 <none> 8080/TCP 28d
onap cds-db ClusterIP None <none> 3306/TCP 28d
onap cds-py-executor ClusterIP 10.233.43.240 <none> 50052/TCP,50053/TCP 28d
onap cds-sdc-listener ClusterIP 10.233.2.48 <none> 8080/TCP 28d
onap cds-ui NodePort 10.233.55.19 <none> 3000:30497/TCP 28d
onap mariadb-galera ClusterIP None <none> 3306/TCP 28d
onap4k8s clm NodePort 10.233.59.50 <none> 9061:31856/TCP 28d
onap4k8s emcoui NodePort 10.233.2.5 <none> 9080:30480/TCP 28d
onap4k8s etcd ClusterIP 10.233.54.80 <none> 2379/TCP,2380/TCP 28d
onap4k8s middleend NodePort 10.233.11.225 <none> 9891:31289/TCP 28d
onap4k8s mongo ClusterIP 10.233.19.133 <none> 27017/TCP 28d
onap4k8s ncm NodePort 10.233.16.20 <none> 9031:32737/TCP 28d
onap4k8s orchestrator NodePort 10.233.23.25 <none> 9015:31298/TCP 28d
onap4k8s ovnaction NodePort 10.233.37.45 <none> 9053:32514/TCP,9051:31181/TCP 28d
onap4k8s rsync NodePort 10.233.60.47 <none> 9041:30555/TCP 28d
|
Access EMCOUI GUI:
| Code Block | ||
|---|---|---|
| ||
# Determine EMCOUI Service Port:
onaplab@emco:~$ kubectl get svc emcoui -n onap4k8s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
emcoui NodePort 10.233.2.5 <none> 9080:30480/TCP 28d
# To connect to EMCOUI GUI use IP address of amcop-vm-01 and port 30480 |
To connect to EMCOUI GUI use IP address of amcop-vm-01 and port 30480:
Edge Cluster Deployment Verification
...