For anyone else interested in making use of SO-Monitoring,
We followed the steps below in order to resolve the issues getting
SO-Monitoring running. Thank you
@[email protected]<mailto:[email protected]> for testing
these steps through on your system.
1. enable SO-Monitoring NodePort
--------------------------------
Use below commands to create NodePort
- use as "release" the specific value of your deployment ("dev" or "onap")
<nfs-server>:/home/ubuntu# vi so-monitoring-service.json
{
"apiVersion": "v1",
"kind": "Service",
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "so-monitoring"
},
"name": "so-monitoring"
},
"spec": {
"externalTrafficPolicy": "Cluster",
"ports": [{
"name": "so-monitoring-port",
"nodePort": 30224,
"port": 9091,
"protocol": "TCP",
"targetPort": 9091
}],
"selector": {
"app": "so-monitoring",
"release": "dev"
},
"sessionAffinity": "None",
"type": "NodePort"
},
"status": {
"loadBalancer": {}
}
}
<nfs-server>:/home/ubuntu# kubectl -n onap apply -f so-monitoring-service.json
service/so-monitoring created
2. set SO-Monitoring User/Password
-----------------------------------
- add in
oom/kubernetes/so/charts/so-monitoring/resources/config/overrides/override.yaml
spring:
main:
allow-bean-definition-overriding: true
security:
usercredentials:
-
username: gui
password: '$2a$10$Fh9ffgPw2vnmsghsRD3ZauBL1aKXebigbq3BB1RPWtE62UDILsjke'
role: GUI-Client
- upgrade helm chart (example for release "onap", otherwise "dev") and restart
pod:
cd oom/kubernetes/
make so
helm upgrade onap-so local/so
kubectl delete pod onap-so-monitoring-xxx -n onap
3. Enable the Monitoring
------------------------
- add in the /etc/hosts a resolution for "so-monitoring"
e.g.
10.211.0.32 so-monitoring
4. Login to SO-Monitoring
-------------------------
URL: http://so-monitoring:30224
Credentials: gui/password1$
From: [email protected] <[email protected]> On Behalf Of
Andreas Geissler via lists.onap.org
Sent: Thursday 9 July 2020 10:03
To: [email protected]
Subject: [onap-discuss] Enabling SO-Monitor in Frankfurt #so
Dear SO project or other experienced users,
I raised in topic https://lists.onap.org/g/onap-discuss/topic/73076157#21310
<https://lists.onap.org/g/onap-discuss/topic/73076157#21310> the question,
whether there is an instruction how to enable the SO-Monitor in Frankfurt
release, as the node port has been removed from the Helm Chart.
I tried the hints given by Byung-Woo, but finally the queries are failing.
Is someone able to help on this, as the SO-Monitor would be a very useful tool
while testing ONAP usecases.
Thanks and best regards
Andreas
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21706): https://lists.onap.org/g/onap-discuss/message/21706
Mute This Topic: https://lists.onap.org/mt/75393828/21656
Mute #so: https://lists.onap.org/g/onap+onap-discuss/mutehashtag/so
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
