Segregating configuration of ONAP components
Description
Activity
Former user May 10, 2018 at 8:29 PM
last 2 tasks security and log demo containers no longer required - closing
Former user April 13, 2018 at 2:49 PM
post any issues with 2.7.2 helm to the OOM team - as we just switched to 2.7.2 around April 9 from 2.6.1
Former user February 6, 2018 at 1:34 AM
About our discussion a couple hours ago on the tagging and data-router binary issues
the tag work can be reverted in support of the prepull - as the prepull takes a lower priority than any yaml change - in the future we will align with the generated manifest when
The binary files like log.n should be able to be removed - but refer this to the DCAE team first for integration testing
The index and .log files in the db (after talking with Mike - will likely need to stay there) - as we talked I was thinking that keeping the empty log files would be ok - but don't delete them as the kafka container will likely not create them on the fly.
The issue (a new JIRA) will be to define the configuration of the kafka container from a clean install - and apply this at startup (I know a violation of microservice statelessness) - currently these files represent a running shapshot - along with the .lock files
*
Former user January 29, 2018 at 4:44 AM
Team,
For any breaking changes, API changes, config changes, or general devops modifications - give a heads up to the community
Also, most important - at the time of merge - monitor newsgroup and wiki traffic
https://lists.onap.org/pipermail/onap-discuss/2018-January/007674.html
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Sprint
NoneFix versions
Priority
Medium
Details
Details
Assignee
Former userReporter
Former userSprint
Fix versions
Priority
Medium
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?