1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
7 To support K8S deployment, TCA is packaged using CDAP SDK as base container. Deployment of TCA is done using cloudify blueprint which gets executed part of DCAE bootstrap container during ONAP/DCAE installation.
9 The logs for TCA are accessible through CDAP GUI which is exposed on 11011/http. To enable external cluster access, a K8S nodeport is required.
11 Prior to El-Alto release, 32010 nodeport was assigned by default to enable logs/validation. In El-Alto reason for security reasons, nodeport is no longer enabled by default under ONAP/DCAE deployment.
17 Following procedure can be used to enable nodeport for troubleshooting purpose.
20 Update existing TCA service to change the service type from ClusterIP to NodePort by editing service definition
23 kubectl edit services -n onap dcae-tca-analytics
25 * Change type from ClusterIP to NodePort
27 * Set externalTrafficPolicy: Cluster
29 Once modified, save and exit. K8s will redeploy the TCA service and nodeport 32010 will be available for access.
31 Following is an example
33 Original service definition
38 clusterIP: 10.43.62.180
45 app: dcae-tca-analytics
52 Modified service definition to expose NodePort
57 clusterIP: 10.43.62.180
58 externalTrafficPolicy: Cluster
66 app: dcae-tca-analytics
74 - Verify if updates done are reflected in K8S
78 kubectl get svc -n onap | grep dcae-tca-analytics
79 dcae-tca-analytics NodePort 10.43.62.180 <none> 11011:32010/TCP 83
82 - CDAP GUI can now be accessed using **http://<k8snodeip>:32010**
84 - Verify if following TCA process are in "RUNNING" state under **http://<k8snodeip>:32010/oldcdap/ns/cdap_tca_hi_lo/apps/dcae-tca/overview/programs**
86 * TCADMaaPMRPublisherWorker
87 * TCADMaaPMRSubscriberWorker
91 - Under each process, logs can be viewed (or downloaded) by clicking on "Logs" tab