<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/k8s/pod/glance-pod.yaml, branch version-m2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=version-m2</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=version-m2'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2015-01-05T23:26:19+00:00</updated>
<entry>
<title>Start and stop scripts are outdated after Kubernetes update</title>
<updated>2015-01-05T23:26:19+00:00</updated>
<author>
<name>Ryan Hallisey</name>
<email>rhallise@redhat.com</email>
</author>
<published>2014-12-22T21:40:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=8229c1f6c3448f5b00d04cdf3928ca5776a44ff8'/>
<id>urn:sha1:8229c1f6c3448f5b00d04cdf3928ca5776a44ff8</id>
<content type='text'>
Kubernetes no longer uses 'kubecfg', but rather 'kubectl'.
Therefore, the way that pods and services are being created
needs to be changed.

In order to create a pod, the parameter 'kind' needs to be set
to 'pod' in the yaml file and the api version specified.

The stop script now reads from k8s/{pod,service,replication}/ in order
to stop all the started pods, services, and replication controllers.

Change-Id: Ibd39fa402e9df883df83272c3aefbb69009dfbd2
</content>
</entry>
<entry>
<title>add kubernetes volumes to glance pod</title>
<updated>2014-10-13T20:43:13+00:00</updated>
<author>
<name>Lars Kellogg-Stedman</name>
<email>lars@redhat.com</email>
</author>
<published>2014-10-10T18:49:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=282345c12e44194b73674464a98e207b396a9294'/>
<id>urn:sha1:282345c12e44194b73674464a98e207b396a9294</id>
<content type='text'>
Use kubernetes volumes for data storage rather than placing data
directly on the container filesystem.  That provides a starting point
for thinking about persistent data -- one could replace the emptyDir
source with an explicit path via hostDir, and then you would have
storage that would persist over a container delete/re-create.

Change-Id: Ifade1cb2ba546e5e0207c3d8c84965dc2195716b
</content>
</entry>
<entry>
<title>glance images need keystone password</title>
<updated>2014-10-13T20:42:28+00:00</updated>
<author>
<name>Lars Kellogg-Stedman</name>
<email>lars@redhat.com</email>
</author>
<published>2014-10-10T16:44:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=270826f662f8e9fbf68ece5762ccf6005b45cdeb'/>
<id>urn:sha1:270826f662f8e9fbf68ece5762ccf6005b45cdeb</id>
<content type='text'>
glance keystone password cannot be generated during container boot
because we need the same value in both the -api and -registry
containers.

Change-Id: I4099ca19bd7433ff2a75ffba3a1597eff0be2ce4
</content>
</entry>
<entry>
<title>convert all configs to yaml</title>
<updated>2014-10-13T15:25:11+00:00</updated>
<author>
<name>Lars Kellogg-Stedman</name>
<email>lars@redhat.com</email>
</author>
<published>2014-10-10T16:07:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=dd16b95aa6ec28b4df192319e9364441a6451182'/>
<id>urn:sha1:dd16b95aa6ec28b4df192319e9364441a6451182</id>
<content type='text'>
Change-Id: I7edbd3a59007d9e2f7f5ab5e4c020eeb58d03dd3
</content>
</entry>
</feed>
