<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docs/vagrant.md, 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-21T09:10:31+00:00</updated>
<entry>
<title>Prepare for MD to RST conversion</title>
<updated>2015-08-21T09:10:31+00:00</updated>
<author>
<name>Steven Dake</name>
<email>stdake@cisco.com</email>
</author>
<published>2015-08-21T06:00:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=bbcf22cc1298dd0ad4f0826c9e1186298c64569e'/>
<id>urn:sha1:bbcf22cc1298dd0ad4f0826c9e1186298c64569e</id>
<content type='text'>
Sphinx and OpenStack documentation standards require the use of
RST formatted documentation.  In order to get out docs integrated
into docs.openstack.org, the following steps must be taken:

1. we need to first convert the documentation to RST
2. sphinx support must be added to the repository
3. project-config must be updated with a publish-docs job

The ability to pubish to docs.openstack.org is a privilege only
available to Big Tent projects.  As a result, we should be taking
advantage of this to help spread the word on our implementation.

Note the documentation was converted with a tool called pandoc
the syntax of which was:
pandoc -f markdown -t rst file.md &gt; z
mv z file.rst

In order for git to preserve history the files have to be git mv'ed
in one commit followed by the pandoc operation in a separate commit.

Change-Id: Iba2a70b989e8305da03e8204a9b130d457b00cf0
</content>
</entry>
<entry>
<title>Fix group name in vagrant docs</title>
<updated>2015-08-20T10:38:42+00:00</updated>
<author>
<name>Sam Yaple</name>
<email>sam@yaple.net</email>
</author>
<published>2015-08-18T00:57:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=795810fef387ddf40d5db14c023d312c97bfbc60'/>
<id>urn:sha1:795810fef387ddf40d5db14c023d312c97bfbc60</id>
<content type='text'>
Change-Id: I9a031dc3aea3c2ca549e3c2353c64e95180f2ba7
</content>
</entry>
<entry>
<title>Vagrantfile and docs</title>
<updated>2015-07-31T18:13:34+00:00</updated>
<author>
<name>Harm Weites</name>
<email>harm@weites.com</email>
</author>
<published>2015-07-21T19:57:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=37561cc1f7fa729f87368bfd46706fa4b57e52e8'/>
<id>urn:sha1:37561cc1f7fa729f87368bfd46706fa4b57e52e8</id>
<content type='text'>
With Vagrant it becomes real easy to create a dev environment to
test and checkout $code. The focus is specifically on setting up
an environment to play around in, developing Kolla and showing
what it is capable of in a clean virtualised environment. When
done, the environment can be destroy and re-created at will when
needed.

Change-Id: I440d004e76c337f298cad2397cf4c13f2cc35ddb
Implements: blueprint vagrant-devenv
</content>
</entry>
</feed>
