Key Manager settings should moved from cinder::api to init

[Alan Bishop]

The Key Manager settings are currently configured by cinder::api, but cinder-api is not the only service that accesses the Key Manager. The cinder-volume and cinder-backup services need to be able to clone encryption keys. However, the parameters are not configured unless the node is also running the cinder-api service.

The problem can be fixed by moving the keymgr_XXX parameters from cinder::api to init.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/739126
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=970fa8d7a1fdee5e599d6724b30f8cf1ee71dd99
Submitter: Zuul
Branch: master

commit 970fa8d7a1fdee5e599d6724b30f8cf1ee71dd99
Author: Alan Bishop <email address hidden>
Date: Thu Jul 2 10:16:49 2020 -0700

    Move the keymgr_XXX parameters from cinder::api to init

    The Key Manager is used by several cinder services, and not just
    cinder-api. For example, the cinder-backup and cinder-volume services
    use the Key Manager to clone encryption keys. Moving the Key Manager
    parameters from cinder::api to init ensures the settings are always
    configured, even when the cinder-api service isn't included in the
    deployment.

    Closes-Bug: #1886081
    Change-Id: Ie3c95da2c0dab83e3c4b7e10f8a3531301692da5