...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{
"vnfs": [{
"eventName": "Heartbeat_vDNS",
"heartbeatcountmissed": 3,
"heartbeatinterval": 60,
"closedLoopControlName": "ControlLoopEvent1",
"policyVersion": "1.0.0.5",
"policyName": "vFireWall",
"policyScope": "resource=sampleResource,type=sampletype,CLName=sampleCLName",
"target_type": "VNF",
"target": "genVnfName",
"version": "1.0"
}, {
"eventName": "Heartbeat_vFW",
"heartbeatcountmissed": 3,
"heartbeatinterval": 60,
"closedLoopControlName": "ControlLoopEvent1",
"policyVersion": "1.0.0.5",
"policyName": "vFireWall",
"policyScope": "resource=sampleResource,type=sampletype,CLName=sampleCLName",
"target_type": "VNF",
"target": "genVnfName",
"version": "1.0"
}, {
"eventName": "Heartbeat_xx",
"heartbeatcountmissed": 3,
"heartbeatinterval": 60,
"closedLoopControlName": "ControlLoopEvent1",
"policyVersion": "1.0.0.5",
"policyName": "vFireWall",
"policyScope": "resource=sampleResource,type=sampletype,CLName=sampleCLName",
"target_type": "VNF",
"target": "genVnfName",
"version": "1.0"
}]
} |
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
["{\"closedLoopEventClient\": \"DCAE_Heartbeat_MS\", \"policyVersion\": \"1.0.0.5\", \"policyName\": \"vFireWall\", \"policyScope\": \"resource=sampleResource,type=sampletype,CLName=sampleCLName\", \"target_type\": \"VNF\", \"AAI\": {\"generic-vnf.vnf-name\": \"testnode001\"}, \"closedLoopAlarmStart\": 1556768386209, \"closedLoopEventStatus\": \"ABATED\", \"closedLoopControlName\": \"ControlLoopEvent1\", \"version\": \"1.0\", \"target\": \"genVnfName\", \"requestID\": \"8c1b8bd8-06f7-493f-8ed7-daaa4cc481bc\", \"from\": \"DCAE\"}"] |
Dynamic Configuration Update
As the Heartbeat service periodically polls Consul KV using configbindingService api's - the run time configuration of Heartbeat service can be updated dynamically without having to redeploy/restart the service. The updates to configuration can be triggered either from Policy (or CLAMP) or made directly in Consul.
Locate the servicename by executing into Heartbeat Service pod and getting env HOSTNAME value
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@k8s-rancher:~# kubectl exec -it -n onap dep-s78f36f2daf0843518f2e25184769eb8b-dcae-heartbeat-servithzx2 /bin/bash
Defaulting container name to s78f36f2daf0843518f2e25184769eb8b-dcae-heartbeat-service.
Use 'kubectl describe pod/dep-s78f36f2daf0843518f2e25184769eb8b-dcae-heartbeat-servithzx2 -n onap' to see all of the containers in this pod.
misshtbt@s78f36f2daf0843518f2e25184769eb8b-dcae-heartbeat-service:~/bin$ env | grep HOSTNAME
HOSTNAME=s78f36f2daf0843518f2e25184769eb8b-dcae-heartbeat-service |
Change the configuration for Service in KV-store through UI
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
http://<k8snodeip>:30270/ui/#/dc1/kv/ |
