openstack/puppet-openstack-integration
Code Issues Proposed changes

Fix link to All-in-one section

Browse Source 
Anchor tags are autogenerated for headers using lower case, at least
with GitHub's Markdown engine.

Change-Id: Id5b40699042823650086cb0bf8afe95b3c0268d9
This commit is contained in:
Pierre Riteau
2016-08-26 10:56:27 +01:00
parent 2cdb5e0282
commit 371253b6eb
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -6,7 +6,7 @@ puppet-openstack-integration
1. [Overview - What is Puppet OpenStack Integration?](#overview)
2. [Description - What does the project do?](#description)
3. [Development - Guide for contributing](#development)
4. [All-in-one - How to deploy a cloud with Puppet](#All-In-One)
4. [All-in-one - How to deploy a cloud with Puppet](#all-in-one)
5. [Contributors - Those with commits](#contributors)
@@ -29,7 +29,7 @@ OpenStack services are balanced between three scenarios because OpenStack
Infastructure Jenkins slaves can not afford the load of running everything on
the same node.
One manifest (scenario-aio) is used for people who want to [run a simple All-In-One
scenario](#All-In-One).
scenario](#all-in-one).
| - | scenario001 | scenario002 | scenario003 | scenario-aio |
|:----------:|:-----------:|:-----------:|:-----------:|:-------------: