standardize start.sh for internal/external config via Ansible/Compose
standardize start for Ansible config for all of the containers we currently have.
Examples for each container should be something like:
git mv start.sh to config-internal.sh
config-external -> https:/
new start.sh -> https:/
This pattern needs to be repeated for each container in the system probably as separate patches per container.
Blueprint information
- Status:
- Complete
- Approver:
- Steven Dake
- Priority:
- Essential
- Drafter:
- Steven Dake
- Direction:
- Approved
- Assignee:
- Harm Weites
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- liberty-2
- Started by
- Steven Dake
- Completed by
- Harm Weites
Related branches
Related bugs
Sprints
Whiteboard
Here is the list of services need changes for internal-config.sh - https:/
Harm is responsible for reporting status in our weekly IRC meeting when requested. diga+coolsvap+harmw are implementing this feature. --steak
Notes:
mariadb - will eventually be done in https:/
mongodb - may be taken care of when we get ceilometer in a usable state, even using entrypoint-style of Dockerfile
hauthproxy - using start.py script, quite specific and will probably be taken care of if needed during HA/multi-host work
Gerrit topic: https:/
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-
Addressed by: https:/
Add config-