Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

SON-Handler application acts upon reception of  two types of events (Measurement and Fault events) and Neighbor list change notification from SDNR.

Fault events are sent whenever collisions/confusions found by the Ran-simulator due to pci changes and at the same time SDNR notification is also sent whenever there is change in pci value.Measurement events are periodically sent from Ran-simulator which gives the KPI information.

SON-Handler processes the events and calls OOF for global optimization. Then it determines the actions based on OOF response and writes to unauthenticated.DCAE_CL_OUTPUT for policy to take necessary actions. 

Blueprint/model/image

Βlueprint component file can be found in

https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/son-handler.git;a=blob;f=dpo/blueprints/k8s-sonhms.yaml;h=d77f0fc01888fc42ea84712ee8d0a95c5fb36fdf;hb=refs/heads/master

Blueprint inputs file can be found in

https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/son-handler.git;a=blob;f=dpo/blueprints/k8s-sonhms-inputs.yaml;h=e417c01a7c0c1fc738cd154e3e3b5f9abbedf584;hb=refs/heads/master

Docker image metadata for component can be found in

https://nexus3.onap.org/repository/docker.snapshot/v2/onap/org.onap.dcaegen2.services.son-handler/manifests/1.0.0

Deployment Prerequisite/dependencies

SON-Handler service requires DMAAP and Policy components to be functional.

SON-hadler service requires  the following dmaap topics to be present in the running DMAAP instance :

1.PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO

2.unauthenticated.SEC_FAULT_OUTPUT

3.unauthenticated.SEC_MEASUREMENT_OUTPUT

4.DCAE_CL_RSP

Policy model required for SON-handler service should be created and pushed to policy component.

Deployment Steps

  • Copy sonhms-blueprint and inputs file to /blueprints directory in DCAE bootstrap POD
  • Log-in to the DCAE bootstrap POD's main container

  • validate and deploy blueprint

    Deploy component
     cfy install -b sonhms -d sonhms -i <inputsFilePath> <blueprintFilePath>

  • undeploy

    Undeploy component
    cfy uninstall sonhms


  • delete blueprint

    Delete blueprint
    cfy blueprints delete sonhms

Validation

The status of service can be checked after the deployment using command "kubectl get pods --namespace onap |grep son"

Verify
ubuntu@k8s-dcae-1:~$ kubectl get pods --namespace onap | grep son 
dep-s37e79facdf9b4820a933852d56127cd9-dcae-sonhms-59897b86qmv5p   1/1       Running            0          5h





  • No labels