<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/centos/binary/designate/designate-api, 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>2015-08-28T07:50:30+00:00</updated>
<entry>
<title>Remove docker directory</title>
<updated>2015-08-28T07:50:30+00:00</updated>
<author>
<name>Steven Dake</name>
<email>stdake@cisco.com</email>
</author>
<published>2015-08-28T02:23:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=f895ee07cc5c1030e32854cf9a4e91bbeaf4de12'/>
<id>urn:sha1:f895ee07cc5c1030e32854cf9a4e91bbeaf4de12</id>
<content type='text'>
Remove the docker directory (yay) and old build tools.

This will result in an f21 failing gate - however, I have a patch
submission to remove that gate from our project configuration.

Change-Id: I3c461cedb6906422c8076f60c470e773d6cdcf33
Partially-Implements: blueprint remove-docker-dir
</content>
</entry>
<entry>
<title>Remove config-internal from designate</title>
<updated>2015-08-08T05:33:00+00:00</updated>
<author>
<name>Steven Dake</name>
<email>stdake@cisco.com</email>
</author>
<published>2015-08-07T16:10:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=ba01f942068f2c38d446f9ec52b22bf93ed7aeb2'/>
<id>urn:sha1:ba01f942068f2c38d446f9ec52b22bf93ed7aeb2</id>
<content type='text'>
Change-Id: I15a9c34a08055c6f9ad53f211a8c1a62de3f58ff
Partially-Implements: blueprint remove-config-internal
</content>
</entry>
<entry>
<title>Add config-internal/config-external to Designate containers</title>
<updated>2015-07-08T14:45:35+00:00</updated>
<author>
<name>Swapnil Kulkarni</name>
<email>me@coolsvap.net</email>
</author>
<published>2015-07-03T09:23:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=1b4d6b37b3174272eb530a3214f83dec66d93119'/>
<id>urn:sha1:1b4d6b37b3174272eb530a3214f83dec66d93119</id>
<content type='text'>
Partially Implements: Blueprint standard-start

Change-Id: I96342c3bdb99d317ce75e0bbb78bdf469f9d1bf7
</content>
</entry>
<entry>
<title>Symlink all non Dockerfile resources in images</title>
<updated>2015-06-19T17:12:05+00:00</updated>
<author>
<name>Paul Bourke</name>
<email>paul.bourke@oracle.com</email>
</author>
<published>2015-06-17T11:14:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=897337cdd61f1702aa7e68da0466804bf0d21a86'/>
<id>urn:sha1:897337cdd61f1702aa7e68da0466804bf0d21a86</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Add the Designate DNSaaS services.</title>
<updated>2015-06-05T19:06:06+00:00</updated>
<author>
<name>Harm Weites</name>
<email>harm@weites.com</email>
</author>
<published>2015-05-29T18:21:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=76c5d9a6c86d77c66de2bf9b14740cd7912dff2d'/>
<id>urn:sha1:76c5d9a6c86d77c66de2bf9b14740cd7912dff2d</id>
<content type='text'>
This is a complete DNS solution, with hidden master and bind9 slave.

It lacks the designate-sink service, because there is no true specification
to implement that. It listens for Nova/Neutron events and creates records
though adding those to just 1 domain isn't helping much in an environment
with multiple tenants.

Change-Id: I500fb6058b118d25a4ccfd1d3479830c36af7e2a
Blueprint: designate-container
</content>
</entry>
</feed>
