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

Segregation of configuration for SDNC component - SDNC Stateful

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      OOM Sprint 7, OOM Sprint 9 - Beijing freeze, OOM Sprint 10 - Integration

      Description

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

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

        Attachments

        1. create-all-output
          2 kB
        2. describe-nfs-provisioner
          3 kB
        3. describe-sdnc
          8 kB
        4. describe-sdnc-conf-configmap
          16 kB
        5. describe-sdnc-dbhost
          11 kB
        6. describe-sdnc-dgbuilder
          5 kB
        7. describe-sdnc-log-configmap
          2 kB
        8. describe-sdnc-logging-cfg-configmap
          3 kB
        9. describe-sdnc-portal
          6 kB
        10. get-pod-status
          0.4 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            mayankg2703 Mayank Gupta
            Reporter:
            mahendrr Mahendra Raghuwanshi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: