Support servername in cloud::dashboard
Set servername default value to fqdn
Merge pull request #381 from dsavineau/bug/380/dsavineau

Support servername in cloud::dashboard
network/lbaas: manage or not HAproxy package

- Update fixtures and Puppetfile with last commit in
  puppet-neutron/havana
- Allow cloud::network::lbaas to manage or not HAproxy package.

With this commit, we should be able to run cloud::loadbalancer and
cloud::network::lbaas without dupplicated resource.

Bug #49
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
dashboard: use puppet-horizon from upstream

- Update fixtures and Puppet file
- Update cloud::dashboard

Close bug #367
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
cloud::dashboard: fix lint issues

Bug #367
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #383 from enovance/horizon-upstream

dashboard: use puppet-horizon from upstream
messaging: user latest RabbitMQ puppet module

- Update fixtures and Puppetfile
- Update cloud::messaging manifest
- Update cloud::messaging specs tests

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Keystone: Move to SQL backend for Token storage

Using Memcache as storage backend for Tokens in Keystone, we hit this
bug: https://bugs.launchpad.net/keystone/+bug/1242620

It generates some bugs when running Tempest framework and also failures
in our QA process.

After some investigation, it seems the bug will not be fixed in Havana
and we should switch to SQL backend. Another work will be done
also on the MySQL keystone tables to avoid useless replication for
large scale deployments.

Bug #379
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Keystone / Rspec: Ensure we have SQL backend for tokens

Ensure in the tests that puppet-keystone provide us by default SQL
backend to store tokens.

Bug #379
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Keystone: Add token_driver param in cloud::identity

Allow the end-user to use another backend (memcache) but let SQL by
default.

Bug #379
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #392 from enovance/bug/379/emilien

Keystone: Move to SQL backend for Token storage
Use fork for puppet-corosync module

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #393 from enovance/corosync-module-src

Use fork for puppet-corosync module
volume/api: specify a default backend

When using multi-backend in Cinder, we need to specify a default type to
avoid any error when creating a volume without specifying a type.

This patch is backward compatible when not using multi-backend and make
the catalog fail if we don't specify the value.

Also, it updates puppet-cinder to last stable/havana commit.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Red Hat: Add crond service support

- Add cron service support for both Debian & RH OS families.
- Clean unit tests

Bug #396
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Red Hat: Cleanup cloud::sql

Clean a test where it fails when the class is called from a OS different
from Red Hat or Debian families.
This is already tested in cloud::init class.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
MySQL: use same bootstrap script for both RH & Debian

It seems the bug* fixed upstream has been packaged uptsream for both Red
Hat and Debian/Ubuntu.

This patch aims to:
- move the debian script to one generic
- delete the red hat script
- use the generic for all OS.

* https://bugs.launchpad.net/codership-mysql/+bug/1087368

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
cloud::sql / Comments cleaning

Some cleaning on comments and lint warning.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Revert "MySQL: use same bootstrap script for both RH & Debian"

This reverts commit b44621a0308926c731a094d63dee54ced574a5a1.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>

Conflicts:
	manifests/database/sql.pp