Home
DevCentral
Search
Configure Global Search
Log In
Transactions
T1422
Change Details
Change Details
Old
New
Diff
The docker_containers pillar entry contains mixed data, according we need one container or several containers for a service. Example of one service, two containers: ``` jenkins_slave: apsile: ip: 172.17.0.100 elapsi: ip: 172.17.0.101 ``` Example of one service, one container: ```counterexample cachet: app_port: 39080 host: status.nasqueron.org mysql_link: acquisitariat ``` To make easier to write Salt states depending of this pillar entry, plan is to standardize the configuration entry to one service, several container. Accordingly, all the containers deployment logic should support several containers for one service.
The docker_containers pillar entry contains mixed data, according we need one container or several containers for a service. Example of one service, two containers: ``` jenkins_slave: apsile: ip: 172.17.0.100 elapsi: ip: 172.17.0.101 ``` Example of one service, one container: ```counterexample cachet: app_port: 39080 host: status.nasqueron.org mysql_link: acquisitariat ``` To make easier to write Salt states depending of this pillar entry, plan is to standardize the configuration entry to one service, several container. Accordingly, all the containers deployment logic should support several containers for one service.
Continue