SDC on OOM
- Michael Lando
- Tal Gitelman
- 1.1 Rancher access
- 1.2 K8 access
- 1.3 SDC docker dependency structure and troubleshooting info:
- 1.4 Useful commends
- 1.4.1 Retrieve all pods in the system in the ONAP name space or use --all-namespace to show pods from all namespaces
- 1.4.2 For more info on the pods
- 1.4.3 Retrieve all the services defined in the system
- 1.4.4 View k8 context
- 1.4.5 View the helm chart releases and there state :
- 1.4.6 View the repositories from which charts are retrieved
- 1.4.7 Config upgrade
- 1.4.8 update container
- 2 Beijing
- 3 Casablanca
- 3.1.1 Update config map
- 3.1.2 To check status of a pod
- 3.1.3 Log into the docker in a pod
- 3.1.4 Log into ta specific container in a pod
- 3.1.5 View container logs
- 3.1.6 show config maps
- 3.1.7 View config map as yaml
- 3.1.8 Delete full deploy
- 3.1.9 To delete a pod stuck in terminating
- 3.1.10 full install
- 3.2 configuring access to SDC using portal
Rancher access
the IP changes according to the env where the setup is created, use the ui to identify the ip where Rancher is installed and access its external IP.
K8 access
the IP changes according to the env where the setup is created, use the ui to identify the ip where Rancher is installed and access its external IP.
SDC docker dependency structure and troubleshooting info:
Useful commends
Retrieve all pods in the system in the ONAP name space or use --all-namespace to show pods from all namespaces
root@rancher:~# kubectl get pods -n onap
NAME READY STATUS RESTARTS AGE
dev-sdc-be-7dfd76f8b7-hc26c 2/2 Running 0 2d
dev-sdc-cs-7d7787b7f5-6ch55 1/1 Running 0 2d
dev-sdc-es-9477ccd7c-8jt5p 1/1 Running 0 2d
dev-sdc-fe-59dbb59656-v7kwn 2/2 Running 0 2d
dev-sdc-kb-7cfbd85c7b-pgpnj 1/1 Running 0 2d
dev-sdc-onboarding-be-745c794884-6c9tf 2/2 Running 0 2d
dev-sdc-wfd-6f7c9d778b-hbzlf 1/1 Running 0 2d
For more info on the pods
Retrieve all the services defined in the system
View k8 context
View the helm chart releases and there state :
View the repositories from which charts are retrieved
Config upgrade
should use the local/onap syntax to let K8 decide based on the parent chart (local/onap)
update container
disable the pods wait for pods to stop and start them
Update config map
in case you want to update the env json for sdc.
update the file under oom/kubernetes/sdc/resources/config/environments/AUTO.json
stop pods make the charts and start the pods
To check status of a pod
Log into the docker in a pod
Log into ta specific container in a pod
in case there a number of containers in the same pod use -c
View container logs
in case there a number of containers in the same pod use -c
show config maps
View config map as yaml
Delete full deploy
then check that all pods are stopped.
look for all Terminating to be gone if not wait till they are.
Look for persistent volumes claims
that have not been removed.
Delete them if the do not go down
Look for persistent volumes that have not been removed.
Remove them persistent volumes
To delete a pod stuck in terminating
full install
configuring access to SDC using portal
portal application is the only on with an exposed external port.
Look for the external IP of the node that has portal IP 10.0.0.4 in the UI interface for the instances.
kubectl get service -o wide -n onap
define the IP in you local machine to allow so that the browser can resolve it to the correct IP
10.12.6.37 portal.api.simpledemo.onap.org
10.12.6.37 sdc.api.fe.simpledemo.onap.org
to access the portal usethe link below after the resolving has been updated.