+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.\r
-.. http://creativecommons.org/licenses/by/4.0\r
-.. _sliceanalysis-installation:\r
-\r
-\r
-Installation\r
-============\r
-\r
-Slice Analysis MS can be deployed by OOM. Make sure to enable "dcae-slice-analysis-ms" in oom/kubernetes/dcaegen2-services/values.yaml first.\r
-\r
-Deployment Pre-requisites\r
-~~~~~~~~~~~~~~~~~~~~~~~~~\r
-- DCAE and DMaaP pods should be up and running. \r
-\r
-- DMaaP Bus Controller PostInstalls job should have completed successfully (executed as part of an OOM install).\r
-\r
-- PM mapper service should be running.\r
-\r
-- Config DB service should be running.\r
-\r
-- Make sure that cfy is installed and configured to work with the Cloudify deployment.\r
-\r
-\r
-Deployment steps\r
-~~~~~~~~~~~~~~~~\r
-1. Execute bash on the bootstrap Kubernetes pod. \r
- \r
- kubectl -n onap exec -it <dcaegen2-dcae-bootstrap> bash\r
-\r
-2. Go to the /blueprints directory.\r
-\r
- Check that the tag_version in the slice-analysis-ms blueprint is correct for the release\r
- of ONAP that it is being installed on see Nexus link below for slice-analysis-ms for tag_versions.\r
- Nexus link: https://nexus3.onap.org/#browse/browse:docker.public:v2%2Fonap%2Forg.onap.dcaegen2.services.components.slice-analysis-ms%2Ftags\r
-\r
-3. Create an input file.\r
-\r
-4. Run the Cloudify install command to install the slice-analysis-ms with the blueprint and the newly created input file k8s-slice-input.yaml.\r
-\r
- $ cfy install k8s-slice-analysis-ms.yaml -i k8s-slice-input.yaml --blueprint-id sliceanalysisms\r
-\r
- Details of the sample output are available at:\r
- https://wiki.onap.org/pages/viewpage.action?pageId=92998809.\r
-\r
-5. To un-deploy\r
-\r
- $ cfy uninstall sliceanalysisms\r
-\r
-\r
-Application configurations\r
-~~~~~~~~~~~~~~~~~~~~~~~~~~\r
-+-------------------------------+------------------------------------------------+\r
-|Configuration | Description |\r
-+===============================+================================================+\r
-|samples | Minimum number of samples to be present |\r
-| | for analysis |\r
-+-------------------------------+------------------------------------------------+\r
-|minimumPercentageChange | Minimum percentage of configuration change |\r
-| | above which control loop should be triggered |\r
-+-------------------------------+------------------------------------------------+\r
-|initialDelaySeconds | Initial delay in milliseconds for the consumer |\r
-| | thread to start after the application startup |\r
-+-------------------------------+------------------------------------------------+\r
-|config_db | Host where the config DB application is running|\r
-+-------------------------------+------------------------------------------------+\r
-|performance_management_topicurl| Dmaap Topic URL to which PM data are posted |\r
-| | by network functions |\r
-+-------------------------------+------------------------------------------------+\r
-|dcae_cl_topic_url | Dmaap topic to which onset message to trigger |\r
-| | the control loop are posted |\r
-+-------------------------------+------------------------------------------------+\r
-|dcae_cl_response_topic_url | Dmaap topic URL to which Policy posts the |\r
-| | message after successful control loop trigger |\r
-+-------------------------------+------------------------------------------------+\r
-|intelligent_slicing_topic_url | Dmaap topic URL to which ML MS posts the |\r
-| | messages |\r
-+-------------------------------+------------------------------------------------+\r
-|dmaap_polling_interval | Dmaap Polling interval in milliseconds |\r
-+-------------------------------+------------------------------------------------+\r
-\r