Default standalone deploys docker by default

[Emilien Macchi]

Podman is the default in standalone generated environments (e.g. environments/standalone/standalone-tripleo.yaml), however since we haven't made it the default in overcloud-resource-registry-puppet.j2.yaml until we get CentOS8, it's still being deployed because the roles/Standalone.yaml contains the Docker service.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/669173

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/669173
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=41e6757708848d659d4f51a369491c734232fe66
Submitter: Zuul
Branch: master

commit 41e6757708848d659d4f51a369491c734232fe66
Author: Emilien Macchi <email address hidden>
Date: Thu Jul 4 09:04:22 2019 -0400

    Disable Docker in default Standalone environments

    Podman is the default in standalone generated environments
    (e.g. environments/standalone/standalone-tripleo.yaml), however since we
    haven't made it the default in overcloud-resource-registry-puppet.j2.yaml
    until we get CentOS8, docker was still being deployed because the
    roles/Standalone.yaml used to contain the Docker service.

    This patch aims to make sure we disable Docker.
    Note: for scenario004 & 012, we need to enable Docker as Pacemaker is
    enabled and the job runs on CentOS7.

    Closes-Bug: #1835411
    Change-Id: Ib34ba24c84f34a1533a90189d5154825c6dfa868

[OpenStack Infra (hudson-openstack)]

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