Templatize keystone ssl keys/certs

Keystone keys/certs files are fetched from heat metadata.
This will allow us distribute identical keyst/certs to all
control nodes instead of having different keys/certs on each node.

Relies-on: I6d4efa753b97bb8cdbd07b1bf7b1cd123f7a32ed
Related to blueprint tripleo-icehouse-ha-production-configuration

Change-Id: I420957eb883ef4e21440171fb41c5b46f8e743fa
Specify nova configuration file with --config-dir

This change use '--config-dir' option to indicate specific configuration
folder to store configuration files for setting nova services.
That allows, for exmaple, to define the same setting with different
value for two different nova services.

Change-Id: I77c382f05128112102959e1370736fc8564bcb1f
Closes-bug: #1326016
Sync mariadb cluster init with mysql element

Similar cluster init process is used for mariadb as for mysql.

Change-Id: I8089c70346c963c5d81beb1b365d5da00eb9545b
Allow single node mysql clusters to restart

We do not allow automatic restarting for mysql clusters due to possible
data loss issues. This is not a problem for single node clusters.

Related-Bug: #1336110
Change-Id: Id41c2fcf9602828b60692d866ee33737e33f87aa
Sync ml2 vlan ranges with ovs agent

The ml2 plugin runs in the API, the ovs agent runs on nodes, but the
two need the same view of the available resources, or hilarity will
ensue.

Change-Id: I3425bd2676ea21b68f8f8020e85143c2610ec66a
ensure-bridge: bring up bridges first on Debian

We should bring up the interfaces on boot in the same order
with which we bring them up in this script.

In this script we write out /etc/network/interfaces and then
bring up the bridges first, and interfaces second. This
allows us to bring up bridges using DHCP with attached ports
and is working quite well on initial deployment.

It has been reported that upon reboot (sometimes?) an Ubuntu
system does not obtain its DHCP ip_address correctly. This
is most likely due to the fact that ifup -a (which is
executed at boot time via networking.conf) brings up
the interfaces *in order* by which they are listed in
/etc/network/interfaces.

As this order does not match the order in this script this
is most likely the cause of the race which sometimes causes
DHCP to fail.

Change-Id: I91628cb78565aec9764e0dcb33c1b1fe165b7c4a
Closes-bug: #1329238
Merge "Allow single node mysql clusters to restart"
Merge "Sync ml2 vlan ranges with ovs agent"
Merge "ensure-bridge: bring up bridges first on Debian"
Merge "Templatize keystone ssl keys/certs"
Merge "Sync mariadb cluster init with mysql element"
Merge "Specify nova configuration file with --config-dir"