<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/swift/swift-base/config-swift.sh, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=master</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2016-02-01T18:14:31+00:00</updated>
<entry>
<title>Fix Swift for multinode P+ACO deployment</title>
<updated>2016-02-01T18:14:31+00:00</updated>
<author>
<name>Qiu Yu</name>
<email>qiuyu@ebaysf.com</email>
</author>
<published>2016-01-29T19:06:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=b209da1306c454366210e88f5a7a0e14bdd88fc4'/>
<id>urn:sha1:b209da1306c454366210e88f5a7a0e14bdd88fc4</id>
<content type='text'>
Current Swift playbook is based on the preassumption of AIO setup.
However, if one goes with default multinode setup
(ansible/inventory/multinode), it follows the P + ACO deployment model,
which proxy-server runs on controller nodes where ACO
(account/container/object services) run on storage nodes.

It will break because swift proxy-server no longer has access (it
shouldn't have) to /srv/node path. This change ensure disk mounting part
only happens on storage node. It also moves chown from proxy-server
Dockerfile to rsyncd because no matter with PACO, P+ACO or P+A+C+O
model, rsyncd is always running on each storage node.

Change-Id: I3aa20454902caa9c84d3901bb91e4e4c93ac5f34
Partially-Implements: blueprint swift-physical-disk
Closes-Bug: #1537544
</content>
</entry>
<entry>
<title>Common start.sh</title>
<updated>2015-10-06T03:30:26+00:00</updated>
<author>
<name>Sam Yaple</name>
<email>sam@yaple.net</email>
</author>
<published>2015-09-30T11:23:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=cb4e875ae1e1ec2e6ddf8a6b37f42283697fd50c'/>
<id>urn:sha1:cb4e875ae1e1ec2e6ddf8a6b37f42283697fd50c</id>
<content type='text'>
The majority of the start.sh code is identical. This removes that
duplicate code while still maintaining the ability to call code in a
specific container.

The start.sh is moved into /usr/local/bin/kolla_start in the container

The extend_start.sh script is called by the kolla_start script at the
location /usr/local/bin/kolla_extend_start . It always exists because
we create a noop kolla_extend_start in the base directory. We override
it with extend_start.sh in a specific image should we need to.

Of note, the neutron-agents container is exempt from this new
structure due to it being a fat container.

Additionally, we fix the inconsistent permissions throughout. 644 for
repo files and the scripts are set to 755 via a Docker RUN command to
ensure someones local perm change won't break upstream containers.

Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad
Closes-Bug: #1501295
</content>
</entry>
<entry>
<title>Move docker_templates to docker dir</title>
<updated>2015-08-28T13:33:50+00:00</updated>
<author>
<name>Sam Yaple</name>
<email>sam@yaple.net</email>
</author>
<published>2015-08-28T12:16:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=cbd42ca6e90cca2ff4b84f5e4e46224e6455e8b2'/>
<id>urn:sha1:cbd42ca6e90cca2ff4b84f5e4e46224e6455e8b2</id>
<content type='text'>
Updated build.py to reflect this change.
Deprecate --template option and make it a noop.

Change-Id: I7cd98d1ee684a4c64984a49597159868152683b2
Partially-Implements: blueprint remove-docker-dir
</content>
</entry>
</feed>
