kolla/docker/common/swift/swift-object-replicator/start.sh

#!/bin/bash

set -o errexit

CMD="/usr/bin/swift-object-replicator"
ARGS="/etc/swift/object-server.conf --verbose"

# Loading common functions.
source /opt/kolla/kolla-common.sh

# Execute config strategy
set_configs

exec $CMD $ARGS
Symlink all non Dockerfile resources in images The only files in the docker image directories that differ majorly between distros are the Dockerfiles (e.g. different package manager mechanisms, different repo sources, etc). The supporting files such as the start.sh/check.sh and config files should largely stay the same between base images. This change moves these files up into a "common" directory, and symlinks them in the same way that the build script is managed. This means when adding a new base distro only new Dockerfiles need to be created. Also, if a distro does happen to require a vastly different start.sh script for example, one can choose to simply not symlink to the common and instead drop in a custom one. Implements: blueprint refactor-base-image-layout Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284 2015-06-17 11:14:59 +00:00			`#!/bin/bash`
Implement Swift Containers Known bugs/TODOs at this time of this patch update: https://bugs.launchpad.net/kolla/+bug/1477990 https://bugs.launchpad.net/kolla/+bug/1477993 Implements: Blueprint swift-container Closes-bug: #1477992 Co-Authored-By: Paul Bourke <paul.bourke@oracle.com> Change-Id: I031f88a7cd1867104fef12df6ab3ffcc06cb65d6 2015-07-15 16:00:23 +01:00
Add config-internal/config-external to Swift containers These containers look to be broken, bad. Fixing them should be done through a separate bug. Here we only focus on getting aligned for Ansible deployments. Partially Implements: Blueprint standard-start Change-Id: I9d538f2c39510266f30cfed88e01c203f35bfb8e 2015-07-02 23:37:16 +02:00			`set -o errexit`
Symlink all non Dockerfile resources in images The only files in the docker image directories that differ majorly between distros are the Dockerfiles (e.g. different package manager mechanisms, different repo sources, etc). The supporting files such as the start.sh/check.sh and config files should largely stay the same between base images. This change moves these files up into a "common" directory, and symlinks them in the same way that the build script is managed. This means when adding a new base distro only new Dockerfiles need to be created. Also, if a distro does happen to require a vastly different start.sh script for example, one can choose to simply not symlink to the common and instead drop in a custom one. Implements: blueprint refactor-base-image-layout Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284 2015-06-17 11:14:59 +00:00
Implement Swift Containers Known bugs/TODOs at this time of this patch update: https://bugs.launchpad.net/kolla/+bug/1477990 https://bugs.launchpad.net/kolla/+bug/1477993 Implements: Blueprint swift-container Closes-bug: #1477992 Co-Authored-By: Paul Bourke <paul.bourke@oracle.com> Change-Id: I031f88a7cd1867104fef12df6ab3ffcc06cb65d6 2015-07-15 16:00:23 +01:00			`CMD="/usr/bin/swift-object-replicator"`
			`ARGS="/etc/swift/object-server.conf --verbose"`
Symlink all non Dockerfile resources in images The only files in the docker image directories that differ majorly between distros are the Dockerfiles (e.g. different package manager mechanisms, different repo sources, etc). The supporting files such as the start.sh/check.sh and config files should largely stay the same between base images. This change moves these files up into a "common" directory, and symlinks them in the same way that the build script is managed. This means when adding a new base distro only new Dockerfiles need to be created. Also, if a distro does happen to require a vastly different start.sh script for example, one can choose to simply not symlink to the common and instead drop in a custom one. Implements: blueprint refactor-base-image-layout Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284 2015-06-17 11:14:59 +00:00
Add config-internal/config-external to Swift containers These containers look to be broken, bad. Fixing them should be done through a separate bug. Here we only focus on getting aligned for Ansible deployments. Partially Implements: Blueprint standard-start Change-Id: I9d538f2c39510266f30cfed88e01c203f35bfb8e 2015-07-02 23:37:16 +02:00			`# Loading common functions.`
			`source /opt/kolla/kolla-common.sh`
Symlink all non Dockerfile resources in images The only files in the docker image directories that differ majorly between distros are the Dockerfiles (e.g. different package manager mechanisms, different repo sources, etc). The supporting files such as the start.sh/check.sh and config files should largely stay the same between base images. This change moves these files up into a "common" directory, and symlinks them in the same way that the build script is managed. This means when adding a new base distro only new Dockerfiles need to be created. Also, if a distro does happen to require a vastly different start.sh script for example, one can choose to simply not symlink to the common and instead drop in a custom one. Implements: blueprint refactor-base-image-layout Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284 2015-06-17 11:14:59 +00:00
Remove config-internal for swift Change-Id: I07e105a5638ad9fde67e58bf371dffda64563a53 Partially-Implements: blueprint remove-config-internal 2015-08-07 17:28:16 +00:00			`# Execute config strategy`
Add config-internal/config-external to Swift containers These containers look to be broken, bad. Fixing them should be done through a separate bug. Here we only focus on getting aligned for Ansible deployments. Partially Implements: Blueprint standard-start Change-Id: I9d538f2c39510266f30cfed88e01c203f35bfb8e 2015-07-02 23:37:16 +02:00			`set_configs`
Symlink all non Dockerfile resources in images The only files in the docker image directories that differ majorly between distros are the Dockerfiles (e.g. different package manager mechanisms, different repo sources, etc). The supporting files such as the start.sh/check.sh and config files should largely stay the same between base images. This change moves these files up into a "common" directory, and symlinks them in the same way that the build script is managed. This means when adding a new base distro only new Dockerfiles need to be created. Also, if a distro does happen to require a vastly different start.sh script for example, one can choose to simply not symlink to the common and instead drop in a custom one. Implements: blueprint refactor-base-image-layout Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284 2015-06-17 11:14:59 +00:00
Add config-internal/config-external to Swift containers These containers look to be broken, bad. Fixing them should be done through a separate bug. Here we only focus on getting aligned for Ansible deployments. Partially Implements: Blueprint standard-start Change-Id: I9d538f2c39510266f30cfed88e01c203f35bfb8e 2015-07-02 23:37:16 +02:00			`exec $CMD $ARGS`