Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-460

Segregating configuration of ONAP components


    • Type: Story
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Beijing Release
    • Labels:


      Currently createConfig.sh provides complete configuration for all the ONAP components. Now it needs to be split per component.

      Also instead of executing createConfig.sh explicitly, this should be called from oneclick createAll.bash script with the component name as parameter.



      For configuration, we are running pod using config-init image file.

      this image docker file is at location: kubernetes/config/docker/init/Dockerfile

      inside that file, folder /opt/config/src/ is being created in which all the onap-config is being copied(by un-taring onap-cfg.tar.gz).

      using make-tar.sh we make a tar of all files inside src/config and that tar file is being copied into the image at the time of image creation.

      when we run container /root/config-init.sh, it will make configuration and put all the configurations inside /docker_nfs directory (mount path).

       /root/config-init.sh is part of docker image.


      Open Questions:

      Where can we find actual docker file for config_init? Are we correct in our assumption that config-init.sh, DockerFile and make-tar.sh are the ones which are inside kubernetes/config/docker/init/ directory?  


          Issue Links

          There are no Sub-Tasks for this issue.
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.



              • Assignee:
                mahendrr Mahendra Raghuwanshi
                vasundhra Vasundhra Choudhary
              • Votes:
                0 Vote for this issue
                5 Start watching this issue


                • Created: