Details
-
Story
-
Status: Closed
-
Medium
-
Resolution: Done
-
None
-
None
-
OOM Sprint 7, OOM Sprint 9 - Beijing freeze, OOM Sprint 10 - Integration
Description
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.
===================
Analysis:
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?
Attachments
Issue Links
- blocks
-
OOM-656 Framework for reserving nodeports 302nn - need a policy
- Closed
-
OOM-628 Segregation of configuration for logging-demo component - LOG-118
- Closed
- relates to
-
LOG-168 Support configmaps via latest Helm - follow OOM-460
- Closed
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...