<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/specs/containerize-openstack.rst, branch juno-eol</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=juno-eol</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=juno-eol'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2015-04-07T03:25:18+00:00</updated>
<entry>
<title>Remove EXPOSE options from Dockerfiles</title>
<updated>2015-04-07T03:25:18+00:00</updated>
<author>
<name>Steven Dake</name>
<email>stdake@cisco.com</email>
</author>
<published>2015-03-28T15:11:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=a87980e5c21b17a60ba46cb53208140143ed8b15'/>
<id>urn:sha1:a87980e5c21b17a60ba46cb53208140143ed8b15</id>
<content type='text'>
The EXPOSE options will create a local docker-proxy.  This is
unnecessary with --net=host mode.  The docker-proxy adds about
20 microseconds of latency.  Add documentation to the specification
to indicate where to find the ports that are exposed by the
services in case someone were to desire to add EXPOSE back to
the Dockerfiles.

Change-Id: I398e922fe096d6022a2d5985bb92498f89a5ea31
</content>
</entry>
<entry>
<title>Fix typos in kolla/specs/containerize-openstack.rst</title>
<updated>2015-03-18T17:02:29+00:00</updated>
<author>
<name>Mitsuhiro SHIGEMATSU</name>
<email>shigematsu.mitsuhiro@lab.ntt.co.jp</email>
</author>
<published>2015-03-18T17:02:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=b3613dbae423f68810b69a139f1cae3fdb8b32cc'/>
<id>urn:sha1:b3613dbae423f68810b69a139f1cae3fdb8b32cc</id>
<content type='text'>
Change-Id: Ia21736dd43a4fe63fbf4567c96dd53b452594677
</content>
</entry>
<entry>
<title>Merge "Split OpenStack controller and OpenStack API"</title>
<updated>2015-03-06T16:41:41+00:00</updated>
<author>
<name>Jenkins</name>
<email>jenkins@review.openstack.org</email>
</author>
<published>2015-03-06T16:41:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=797960bf2608ae27773a0f2aa3ba8a47265fba66'/>
<id>urn:sha1:797960bf2608ae27773a0f2aa3ba8a47265fba66</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Split OpenStack controller and OpenStack API</title>
<updated>2015-02-20T22:00:55+00:00</updated>
<author>
<name>Steven Dake</name>
<email>stdake@cisco.com</email>
</author>
<published>2015-02-20T22:00:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=c4e56c0c15a2788702c4345b6afd52e3cb77eb93'/>
<id>urn:sha1:c4e56c0c15a2788702c4345b6afd52e3cb77eb93</id>
<content type='text'>
Permit different levels of horizontal scalability for API vs engine or
conductor processes.  Typically API may need different levels of scale
compared to the engine processes.
.

Change-Id: I2916fed7745bd9b0f67fda0abbb6d148315e5e00
</content>
</entry>
<entry>
<title>Revise OpenStack control container set</title>
<updated>2015-02-19T21:14:02+00:00</updated>
<author>
<name>Britt Houser</name>
<email>bhouser@cisco.com</email>
</author>
<published>2015-02-19T21:12:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=04f70c5d7b5e53fa24a03da8d7ce4818aa746a72'/>
<id>urn:sha1:04f70c5d7b5e53fa24a03da8d7ce4818aa746a72</id>
<content type='text'>
Added cinder and metadata

Change-Id: I42feae68a387dd5a9de97837f785d2672c320419
</content>
</entry>
<entry>
<title>Revise HA Control container-set</title>
<updated>2015-02-19T21:12:31+00:00</updated>
<author>
<name>Britt Houser</name>
<email>bhouser@cisco.com</email>
</author>
<published>2015-02-19T21:06:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=accd477cbe81139e62a8ee439f3ca5a48232bf05'/>
<id>urn:sha1:accd477cbe81139e62a8ee439f3ca5a48232bf05</id>
<content type='text'>
Added keepalived to HA control container set

Change-Id: Ic209bc6ca55125a52d1974003104238bb9c4caa2
</content>
</entry>
<entry>
<title>Add network operation container sets</title>
<updated>2015-02-19T21:11:24+00:00</updated>
<author>
<name>Britt Houser</name>
<email>bhouser@cisco.com</email>
</author>
<published>2015-02-19T20:32:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=2e5f23d7267ffa81b0f9a8a4f884c5c4a4982e87'/>
<id>urn:sha1:2e5f23d7267ffa81b0f9a8a4f884c5c4a4982e87</id>
<content type='text'>
Added a container set for network operations

Change-Id: I625f0f03366b1d68f210a0bf92e58d5ceb6c568d
</content>
</entry>
<entry>
<title>Fixed nested lists in container spec</title>
<updated>2015-02-18T21:42:55+00:00</updated>
<author>
<name>Britt Houser</name>
<email>bhouser@cisco.com</email>
</author>
<published>2015-02-18T21:21:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=9d72d99f86b300bedd188aa2c6db6daed0201ec2'/>
<id>urn:sha1:9d72d99f86b300bedd188aa2c6db6daed0201ec2</id>
<content type='text'>
The container spec file had a couple places were nested
lists were used which didn't have the necessary blank
lines before and after.  As such, they didn not render
to HTML correctly.

Change-Id: I5d17644facdc25ec30db563c217367672529b8e1
</content>
</entry>
<entry>
<title>Containerize OpenStack based upon SPC and fig</title>
<updated>2015-02-13T07:26:57+00:00</updated>
<author>
<name>Steven Dake</name>
<email>stdake@cisco.com</email>
</author>
<published>2015-02-07T15:51:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=ddc12789bc0536a2a5dec419124817de9152d292'/>
<id>urn:sha1:ddc12789bc0536a2a5dec419124817de9152d292</id>
<content type='text'>
This specification proposes using fig (being renamed to compose
soon) to provide single-node multi-container orchestration.  By
using this mechanism, a very simple Ansible Playbook could easily
deploy a single node in to a specific role type - such as a controller
node, a compute node, or a storage node.

This specification further proposes using super-privileged containers
to provide solutions for the upgrade and rollback use cases of an
OpenStack deployment.

Change-Id: I56ff1fdf8b19b47be97778b55ea947ebb43995c1
</content>
</entry>
</feed>
