<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla-ansible.git/deploy-guide/source/index.rst, branch stable/2026.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/'/>
<updated>2021-01-27T19:08:41+00:00</updated>
<entry>
<title>[docs] Unify project's naming convention</title>
<updated>2021-01-27T19:08:41+00:00</updated>
<author>
<name>Piotr Parczewski</name>
<email>piotr@stackhpc.com</email>
</author>
<published>2021-01-18T22:14:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=5db72659a062d45085227c237343a1c7a2687fe4'/>
<id>urn:sha1:5db72659a062d45085227c237343a1c7a2687fe4</id>
<content type='text'>
There are inconsitencies across the documentation and the source code files
when it comes to project's name (Kolla Ansible vs. Kolla-Ansible). This
commit aims at unifying it so that the naming becomes consistent everywhere.

Change-Id: I903b2e08f5458b1a1abc4af3abefe20b66c23a54
</content>
</entry>
<entry>
<title>[deploy-guide] Moving the quick start to the deploy folder</title>
<updated>2017-03-28T15:25:16+00:00</updated>
<author>
<name>Alexandra Settle</name>
<email>a.settle@outlook.com</email>
</author>
<published>2017-03-22T11:05:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=f6d93e5ecd9717f75e13000ce1e0263889edc108'/>
<id>urn:sha1:f6d93e5ecd9717f75e13000ce1e0263889edc108</id>
<content type='text'>
Currently the project-deploy-guide links to the entire dev
doc repo for Kolla-Ansible. This is incorrect. It should link
only to installation information that can be found in the quick
start guide. This patch remedies that change, and ensures that
there is a link to the kolla deploy guide published at
docs.o.o.

Change-Id: I43738e341e996cb5a589a09c4c59c0dc8b058458
</content>
</entry>
<entry>
<title>Deployment Guide</title>
<updated>2017-03-02T21:44:07+00:00</updated>
<author>
<name>Sayantani Goswami</name>
<email>sayantani.goswami@intel.com</email>
</author>
<published>2017-02-01T23:22:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=78cf8abd1b193aa8a904bbbb49ce2bdee7c5af6f'/>
<id>urn:sha1:78cf8abd1b193aa8a904bbbb49ce2bdee7c5af6f</id>
<content type='text'>
This builds the deployment guide that will be published to
https://docs.openstack.org/project-deploy-guide/newton/.

In this approach, all existing documents in kolla-ansible/doc directory
will remain. The kolla-ansible/deploy-guide directory will simply
include all documents that exist in the kolla-ansible/doc directory.
All new changes will be made to the documents in the docs directory
which will be imported to the deployment-guide. However, I believe we
will also have to build the deployment-guide every time a change is
merged to the docs in the doc directory.

Change-Id: I98db4ec45403cf48086381b45bf5a12bbf998911
</content>
</entry>
<entry>
<title>Build deploy guide files and tox environment</title>
<updated>2017-01-27T23:33:19+00:00</updated>
<author>
<name>RobiJoe</name>
<email>joseph.robinson@rackspace.com</email>
</author>
<published>2017-01-27T06:55:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=566ef56167ee1d74905b258e3ed7571a91d8dae1'/>
<id>urn:sha1:566ef56167ee1d74905b258e3ed7571a91d8dae1</id>
<content type='text'>
* This patch moves the tox environment and deployment
guide placeholder files introduced in https://review.openstack.org/#/c/422931
from the kolla/ repository to the kolla-ansible/repository
* Remove or add content as needed

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