<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/designate/designate-api/extend_start.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-08-11T01:03:27+00:00</updated>
<entry>
<title>Fix designate bootstrap.</title>
<updated>2016-08-11T01:03:27+00:00</updated>
<author>
<name>Ross Krumbeck</name>
<email>ross.krumbeck@gmail.com</email>
</author>
<published>2016-08-08T10:14:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=e4259f805b91ce0859e7190f97f8dbf34ee92e45'/>
<id>urn:sha1:e4259f805b91ce0859e7190f97f8dbf34ee92e45</id>
<content type='text'>
According to
http://docs.openstack.org/developer/designate/getting-started.html#initialize-start-the-central-service
designate database bootstrap to be done by designate-manage database sync.
Was also missing designate-manage pool_manager_cache sync.
designate-manage command is packaged with designate-central.
Boot strap commands moved to designate-central.
Added creation of log directories.
Added python2-oslo-reports and python2-suds for bootstrap to complete.

Change-Id: I3896064b0abb31c96307b16005a340fc193aac3c
Closes-Bug: 1610795
</content>
</entry>
<entry>
<title>Drop root for designate</title>
<updated>2015-11-10T09:41:13+00:00</updated>
<author>
<name>Michal Rostecki</name>
<email>mrostecki@mirantis.com</email>
</author>
<published>2015-11-10T09:41:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=c691334181405b0fe22e0624de8fb823720259d8'/>
<id>urn:sha1:c691334181405b0fe22e0624de8fb823720259d8</id>
<content type='text'>
Change-Id: I1df05608be62cc008ccef1ca88d0b37983568d22
Partially-Implements: blueprint drop-root
</content>
</entry>
<entry>
<title>Fix issue with su and bad kernels</title>
<updated>2015-10-13T15:13:55+00:00</updated>
<author>
<name>Sam Yaple</name>
<email>sam@yaple.net</email>
</author>
<published>2015-10-13T06:30:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=5f200e044648efe64f297d186432839762f91395'/>
<id>urn:sha1:5f200e044648efe64f297d186432839762f91395</id>
<content type='text'>
Long story short, some kernels before 3.15 had an issue with using su
in a container when the network namespace was --net=host. The gate
has a 3.10 and a 3.13 kernel and has a problem with this. This changes
everything to use sudo

backport: liberty
Partially-Implements: blueprint functional-testing-gate
Change-Id: I4d79ccaa1cddffcc8393f64e7e1be2538efe33e5
</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>
</feed>
