Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-422

As a ONAP user, I would like to deploy the POA-Context Aggregator in OOM on a Kubernetes environment

XMLWordPrintable

      General Information

      The current solution does not deploy the microservices via OOM in a Kubenetes environment.  This story is written to address the task of getting this microservice deployable via OOM.  Ultimately this will be moved to public, that will be addressed by other stories.  The success criteria for this does not include healthchecks / validation of functionality of the microservices.

      Additional Information

      • 1 microservice / container

      To be investigated

      • how do we deploy our own configuration on top of the image that is being laid down?
      • how do we make the pod accessible via name/fqdn rather than an IP address?

      Attachments

      • N/A

      Value

      • Ability to build and automate deployment aligns this feature/microservices with other deployments in ONAP.

      Success Criteria

      • The microservice can be deployed via OOM at any given time
      • The microservice can be deleted via OOM at any given time
      • Able to login to each pods and ensure the ms is running within   

        1.
        		 [TEST] POA-Context Aggregator deployment Sub-task Closed pau2882
        2.
        		 Create Helm chart for the ContextAggregator Sub-task Closed vitalyla
        3.
        		 Add application and context builders configuration templates Sub-task Closed vitalyla

            moreza moreza
            jbalasub jbalasub
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: