Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-460 Segregating configuration of ONAP components
  3. OOM-557

Segregation of configuration for Portal component

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None
    • OOM Sprint 7, OOM Sprint 9 - Beijing freeze, OOM Sprint 10 - Integration

      As of now, PODs of Portal are dependent on the config-init for the creation of configuration and then mounting it in the containers.

      We want to segregate the Portal configuration part from config-init and want to use helm install directly to create the PODs of Portal with required configuration.

        1. create_all_output
          3 kB
        2. describe-portalapps
          13 kB
        3. describe-portaldb
          4 kB
        4. describe-portal-filebeat-configmap
          2 kB
        5. describe-portal-mariadb-configmap
          0.5 kB
        6. describe-portal-onap-portal-configmap
          6 kB
        7. describe-portal-onapportal-log-configmap
          16 kB
        8. describe-portal-onap-portal-sdk-configmap
          6 kB
        9. describe-portal-onapportalsdk-log-configmap
          15 kB
        10. describe-portal-onapwidgetms-configmap
          1 kB
        11. describe-portalwidgets
          6 kB
        12. get-pod-status
          0.3 kB

            mayankg2703 mayankg2703
            mahendrr mahendrr
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: