ControllerCount contraint added kilo->liberty

[Steven Hardy]

https://review.openstack.org/#/q/Ib4917843f3e4770f0260db72719ed6af0ee8dc13

Here I added the contraint to ensure at least one controller, otherwise there's no control plane and the resulting deployment isn't functional.

Turns out some folks were relying on the old behavior to deploy some unusual architectures where compute clusters are isolated from controllers (and managed via different underclouds)

The easiest way to fix this is just remove the contraint I think, done so in https://review.openstack.org/#/c/344739/ but will need backport to mitaka/stable as this is viewed as a regression from kilo-era TripleO

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/345649

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/345650

[Steven Hardy (shardy)]

https://review.openstack.org/#/q/Idb21779f3ad9d875576bdb5e6502ed27a72600ba,n,z

Patch landed on master, backports proposed

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/345649
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=43b7dc023102dfaf5c44671abda2b9339e270aa9
Submitter: Jenkins
Branch: stable/mitaka

commit 43b7dc023102dfaf5c44671abda2b9339e270aa9
Author: Steven Hardy <email address hidden>
Date: Wed Jul 20 11:55:12 2016 +0100

    Remove the ControllerCount constraint

    Some deployments want to deploy zero controllers, and this will become
    a more likely configuration when support for custom roles lands (e.g
    a set of decomposed custom roles vs the monolithic controller role
    may be deployed instead).

    Closes-Bug: #1604777
    Change-Id: Idb21779f3ad9d875576bdb5e6502ed27a72600ba
    (cherry picked from commit ac1a10e26b0340c649c17d9cdbfa24979b6183cf)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/345650
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=bb8d7e58e937b819227d471f7ab0884181e2befd
Submitter: Jenkins
Branch: stable/liberty

commit bb8d7e58e937b819227d471f7ab0884181e2befd
Author: Steven Hardy <email address hidden>
Date: Wed Jul 20 11:55:12 2016 +0100

    Remove the ControllerCount constraint

    Some deployments want to deploy zero controllers, and this will become
    a more likely configuration when support for custom roles lands (e.g
    a set of decomposed custom roles vs the monolithic controller role
    may be deployed instead).

    Closes-Bug: #1604777
    Change-Id: Idb21779f3ad9d875576bdb5e6502ed27a72600ba
    (cherry picked from commit ac1a10e26b0340c649c17d9cdbfa24979b6183cf)

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/tripleo-heat-templates 2.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 2.1.0 release.