...
Looking at verifying sonar locally using eclemma
Developer Deployment
Deployment Integrity
ELK containers
Logstash port
Elasticsearch port
Code Block | ||
---|---|---|
| ||
# get pod names
ubuntu@ip-10-0-0-169:~$ sudo kubectl get services --all-namespaces | grep log-
onap log-es NodePort 10.43.82.53 <none> 9200:30254/TCP 1h
onap log-es-tcp ClusterIP 10.43.90.198 <none> 9300/TCP 1h
onap log-kibana NodePort 10.43.167.146 <none> 5601:30253/TCP 1h
onap log-ls NodePort 10.43.250.182 <none> 5044:30255/TCP 1h
onap log-ls-http ClusterIP 10.43.81.173 <none> 9600/TCP 1h
# check inside docker container first
ubuntu@ip-10-0-0-169:~$ kubectl exec -it -n onap onap-log-elasticsearch-756cfb559b-wk8c6 bash
[elasticsearch@onap-log-elasticsearch-756cfb559b-wk8c6 ~]$ curl http://127.0.0.1:9200
{
"name" : "-pEf9q9",
"cluster_name" : "onap-log",
"cluster_uuid" : "ferqW-rdR_-Ys9EkWw82rw",
"version" : {
"number" : "5.5.0",
"build_hash" : "260387d",
"build_date" : "2017-06-30T23:16:05.735Z",
"build_snapshot" : false,
"lucene_version" : "6.6.0"
},
"tagline" : "You Know, for Search"
}
# check nodeport outside container
ubuntu@ip-10-0-0-169:~$ curl http://127.0.0.1:30254 |
Kibana port
Pairwise Testing
AAI and Log Deployment
...