Upgrade N->O is broken due to glance registry removal

[Steven Hardy]

We completely removed glance registry in 4ccb27a but that fails to account for upgrades, where e.g newton users will have the service running, and the glance-registry.yaml service template will still exist in heat, and be mapped to OS::TripleO::Services::GlanceRegistry.

This means anyone with OS::TripleO::Services::GlanceRegistry in their *Services list (such as the upgrade job at present) will break on upgrade, and even if they remove OS::TripleO::Services::GlanceRegistry from the parameters (which would mean we've broken backwards compatibility), they'll still have to stop and disable the service manually.

Instead, lets stop and disable the service via the new composable service interface, then in pike we can map OS::TripleO::Services::GlanceRegistry to OS::Heat::None, and in some later release remove the mapping completely (after communicating to users they have to remove it from any custom roles_data files etc).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/424795
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=4f4582e1b7137931bc9142e7c9462b3c854d68dd
Submitter: Jenkins
Branch: master

commit 4f4582e1b7137931bc9142e7c9462b3c854d68dd
Author: Steven Hardy <email address hidden>
Date: Tue Jan 24 18:46:27 2017 +0000

    Add glance registry service to disable on upgrade

    We've broken the upgrade job because anyone upgrading with the
    glance registry deployed (and defined in their *Services parameters)
    will try to deploy with the old glance-registry.yaml defined in heat.

    Instead we define a template which stops and disables the service on
    upgrade.

    Closes-Bug: #1659079
    Change-Id: I03561954d794afae2be06811375d16611fa45973

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 6.0.0.0rc1 release candidate.