f895b2bd09
The periodic task unneccessarily lists Heat stacks in the global tenant (across all tenants) which the Magnum service user may lack permission for. Also, the most restrictive way to let it use global stack-list is chose a Keystone role and open that operation to any user in any project holding that role. This commit substitutes a direct lookup of all bays' stack_id attributes for this global stack list. This direct lookup will yield the same net result. In order to get the neccessary permissions it will use each bay's stored Keystone trust to act on behalf of the bay's creating user. Co-Authored-By: Jiri Suchomel <jiri.suchomel@suse.com> Closes-Bug: #1589955 Change-Id: I67b176c137c463e37e037970cc4e468d51db30c9
37 lines
1023 B
ReStructuredText
37 lines
1023 B
ReStructuredText
.. _install-obs:
|
|
|
|
Install and configure for openSUSE and SUSE Linux Enterprise
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
This section describes how to install and configure the Container
|
|
Infrastructure Management service for openSUSE Leap 42.1 and SUSE Linux
|
|
Enterprise Server 12 SP1.
|
|
|
|
.. include:: common/prerequisites.rst
|
|
|
|
Install and configure components
|
|
--------------------------------
|
|
|
|
#. Install the packages:
|
|
|
|
.. code-block:: console
|
|
|
|
# zypper install openstack-magnum-api openstack-magnum-conductor
|
|
|
|
.. include:: common/configure_2_edit_magnum_conf.rst
|
|
|
|
.. include:: common/configure_3_populate_database.rst
|
|
|
|
Finalize installation
|
|
---------------------
|
|
|
|
* Start the Container Infrastructure Management services and configure
|
|
them to start when the system boots:
|
|
|
|
.. code-block:: console
|
|
|
|
# systemctl enable openstack-magnum-api.service \
|
|
openstack-magnum-conductor.service
|
|
# systemctl start openstack-magnum-api.service \
|
|
openstack-magnum-conductor.service
|