...
"kubectl get services --namespace=onap | grep portal”
Accessing the ONAP Portal using OOM and a Kubernetes Cluster
If everything is successful, then to access Portal - http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#accessing-the-onap-portal-using-oom-and-a-kubernetes-cluster
...
- After 3 instances of Portal are up, edit IP in /etc/hosts file, and logon as demo user on http://portal.api.simpledemo.onap.org:30215/ONAPPORTAL/login.htm
- Then killed 1 instance, I am able to continue on Portal page seamlessly
- Another test on failover timing, when killed all 3 instances, the new Portal processes are coming up within 30 seconds
Troubleshoot
In case of failures, below commands may get handy for accessing the pods/logs and troubleshooting the issue.
To find all portal pods:
| Code Block |
|---|
> kubectl get pods --all-namespaces | grep portal
onap dev-portal-app-b8c6668d8-56bjb 2/2 Running 0 2m
onap dev-portal-app-b8c6668d8-g6whb 2/2 Running 0 2m
onap dev-portal-app-b8c6668d8-xshwg 2/2 Running 0 2m
onap dev-portal-cassandra-5ddbc59ffd-qc6rp 1/1 Running 0 2m
onap dev-portal-db-6d7fc58648-sp9sf 0/1 Running 0 2m
onap dev-portal-sdk-868f696cd7-mnjxk 0/2 Init:0/1 0 2m
onap dev-portal-widget-694c45b75f-nqdtt 0/1 Init:0/1 0 2m
onap dev-portal-zookeeper-db466fc-kggsw 1/1 Running 0 2m |
From above list, now to check DB logs:
| Code Block |
|---|
> kubectl logs --namespace=onap dev-portal-db-6d7fc58648-sp9sf -c portal-db
2018-05-30 19:49:16 139875765802880 [Note] mysqld (mysqld 10.2.15-MariaDB-10.2.15+maria~jessie) starting as process 1 ...
2018-05-30 19:49:16 139875765802880 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-30 19:49:16 139875765802880 [Note] InnoDB: Uses event mutexes
2018-05-30 19:49:16 139875765802880 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-05-30 19:49:16 139875765802880 [Note] InnoDB: Using Linux native AIO
2018-05-30 19:49:16 139875765802880 [Note] InnoDB: Number of pools: 1
2018-05-30 19:49:16 139875765802880 [Note] InnoDB: Using SSE2 crc32 instructions |
To check portal-app logs:
| Code Block |
|---|
> kubectl logs --namespace=onap dev-portal-app-b8c6668d8-56bjb -c portal-app
/start-apache-tomcat.sh: option -i value is
/start-apache-tomcat.sh: option -n value is
/start-apache-tomcat.sh: values for IP (-i) and/or name (-n) are empty or short
/start-apache-tomcat.sh: Starting server from /opt/apache-tomcat-8.0.37
30-May-2018 19:48:29.480 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.0.37
30-May-2018 19:48:29.482 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Sep 1 2016 10:01:52 UTC
30-May-2018 19:48:29.482 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.0.37.0 |
To get inside the portal-app docker and access the application logs:
| Code Block |
|---|
> kubectl exec -it dev-portal-app-b8c6668d8-56bjb -n onap /bin/sh
Defaulting container name to portal-app.
Use 'kubectl describe pod/dev-portal-app-b8c6668d8-56bjb' to see all of the containers in this pod.
/ # cd /opt/apache-tomcat-8.0.37/logs/onapportal
/opt/apache-tomcat-8.0.37/logs/onapportal # ls
application.log debug.log metrics.log
audit.log error.log |
Rocket chat - http://onap-integration.eastus.cloudapp.azure.com:3000/home