Prepare master branch for M1
With branching done earlier than the rc1 freeze, we needed to bring the release notes from the updated roles into the integrated repo. On top of the changes needed for M1 is the version change. The openstack SHAs will be updated in a separate commit. Change-Id: I4d5211062966bc4fdb9f5d36eec46d9911012acd
This commit is contained in:
parent
963bd85ae2
commit
dc421891ff
@ -14,7 +14,7 @@
|
||||
# limitations under the License.
|
||||
|
||||
## OpenStack Source Code Release
|
||||
openstack_release: 18.0.0.0b3
|
||||
openstack_release: 19.0.0.0b1
|
||||
|
||||
## Verbosity Options
|
||||
debug: False
|
||||
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for aodh will now be executed
|
||||
through delegation to the ``aodh_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
aodh_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``aodh_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for barbican will now be executed
|
||||
through delegation to the ``barbican_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
barbican_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``barbican_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,25 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for ceilometer will now be executed
|
||||
through delegation to the ``ceilometer_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
ceilometer_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The following variables are no longer used and have therefore been
|
||||
removed.
|
||||
|
||||
* ``ceilometer_requires_pip_packages``
|
||||
* ``ceilometer_service_name``
|
||||
* ``ceilometer_service_port``
|
||||
* ``ceilometer_service_proto``
|
||||
* ``ceilometer_service_type``
|
||||
* ``ceilometer_service_description``
|
||||
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for cinder will now be executed
|
||||
through delegation to the ``cinder_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
cinder_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``cinder_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- The option ``repo_venv_default_pip_packages`` has been added which will
|
||||
allow deployers to insert any packages into a service venv as needed.
|
||||
The option expects a list of strings which are valid python package names as
|
||||
found on PYPI.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
upgrade:
|
||||
- The variable `cinder_iscsi_helper` has been replaced by the new variable
|
||||
which is `cinder_target_helper` due to the fact that iscsi_helper has
|
||||
been deprecated in Cinder.
|
@ -1,2 +1,3 @@
|
||||
---
|
||||
features:
|
||||
- The ``os-designate`` role now supports Ubuntu 16.04 and SystemD.
|
||||
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for designate will now be executed
|
||||
through delegation to the ``designate_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
designate_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``designate_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
deprecations:
|
||||
- |
|
||||
The ``get_gested`` filter has been removed, as it is not used by any
|
||||
roles/plays.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for glance will now be executed
|
||||
through delegation to the ``glance_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
glance_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``glance_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for gnocchi will now be executed
|
||||
through delegation to the ``gnocchi_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
gnocchi_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``gnocchi_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for heat will now be executed
|
||||
through delegation to the ``heat_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
heat_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``heat_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for horizon will now be executed
|
||||
through delegation to the ``horizon_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
horizon_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``horizon_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for ironic will now be executed
|
||||
through delegation to the ``ironic_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
ironic_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``ironic_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
5
releasenotes/notes/journal-log-ccba504642b49612.yaml
Normal file
5
releasenotes/notes/journal-log-ccba504642b49612.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/barbican`` is no longer used to capture service
|
||||
logs. All logging for the barbican service will now be sent directly to the
|
||||
systemd journal.
|
9
releasenotes/notes/journal-log-ccbb504642b49611.yaml
Normal file
9
releasenotes/notes/journal-log-ccbb504642b49611.yaml
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/keystone`` is no longer used to capture service
|
||||
logs. All logging for the Keystone service will now be sent directly to the
|
||||
systmed journal.
|
||||
other:
|
||||
- When running keystone with apache(httpd) all apache logs will be stored in
|
||||
the standard apache log directory which is controlled by the distro specific
|
||||
variable ``keystone_apache_default_log_folder``.
|
5
releasenotes/notes/journal-log-ccbb504642b49614.yaml
Normal file
5
releasenotes/notes/journal-log-ccbb504642b49614.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/congress`` is no longer used to capture service
|
||||
logs. All logging for the congress service will now be sent directly to the
|
||||
systmed journal.
|
5
releasenotes/notes/journal-log-cwbr504hd9b59612.yaml
Normal file
5
releasenotes/notes/journal-log-cwbr504hd9b59612.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/cinder`` is no longer used to capture service
|
||||
logs. All logging for the cinder service will now be sent directly to the
|
||||
systemd journal.
|
9
releasenotes/notes/journal-log-cxcb512642b49617.yaml
Normal file
9
releasenotes/notes/journal-log-cxcb512642b49617.yaml
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/aodh`` is no longer used to capture service
|
||||
logs. All logging for the aodh service will now be sent directly to the
|
||||
systmed journal.
|
||||
other:
|
||||
- When running aodh with apache(httpd) all apache logs will be stored in
|
||||
the standard apache log directory which is controlled by the distro specific
|
||||
variable ``aodh_apache_default_log_folder``.
|
6
releasenotes/notes/journal-log-xcba504642b49619.yaml
Normal file
6
releasenotes/notes/journal-log-xcba504642b49619.yaml
Normal file
@ -0,0 +1,6 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/ceilometer`` is no longer used to capture service
|
||||
logs. All logging for the ceilometer service will now be sent directly to the
|
||||
systemd journal.
|
||||
|
5
releasenotes/notes/journal-log-ycba504642b47619.yaml
Normal file
5
releasenotes/notes/journal-log-ycba504642b47619.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
deprecations:
|
||||
- The log path, ``/var/log/designate`` is no longer used to capture service
|
||||
logs. All logging for the designate service will now be sent directly to the
|
||||
systmed journal.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service updates for keystone will now be executed
|
||||
through delegation to the ``keystone_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
keystone_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``keystone_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,22 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for magnum will now be executed
|
||||
through delegation to the ``magnum_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
magnum_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
- |
|
||||
Instead of downloading images to the magnum API servers, the
|
||||
images will now download to the ``magnum_service_setup_host`` to
|
||||
the folder set in ``magnum_image_path`` owned by
|
||||
``magnum_image_path_owner``.
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``magnum_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for neutron will now be executed
|
||||
through delegation to the ``neutron_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
neutron_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``neutron_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for nova will now be executed
|
||||
through delegation to the ``nova_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
nova_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``nova_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,18 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for octavia will now be executed
|
||||
through delegation to the ``octavia_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
octavia_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``octavia_image_downloader`` has been removed. The image
|
||||
download now uses the same host designated by the
|
||||
``octavia_service_setup_host`` for the image download.
|
@ -0,0 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The role now supports using the distribution packages for the OpenStack
|
||||
services instead of the pip ones. This feature is disabled by default
|
||||
and can be enabled by simply setting the ``nova_install_method``
|
||||
variable to ``distro``.
|
@ -0,0 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The role now supports using the distribution packages for the OpenStack
|
||||
services instead of the pip ones. This feature is disabled by default
|
||||
and can be enabled by simply setting the ``neutron_install_method``
|
||||
variable to ``distro``.
|
@ -0,0 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The role now supports using the distribution packages for the OpenStack
|
||||
services instead of the pip ones. This feature is disabled by default
|
||||
and can be enabled by simply setting the ``nova_install_method``
|
||||
variable to ``distro``.
|
@ -0,0 +1,20 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- trove_oslomsg_rpc_servers replaces trove_rabbitmq_servers
|
||||
- trove_oslomsg_rpc_port replaces trove_rabbitmq_port
|
||||
- trove_oslomsg_rpc_use_ssl replaces trove_rabbitmq_use_ssl
|
||||
- trove_oslomsg_rpc_userid replaces trove_rabbitmq_userid
|
||||
- trove_oslomsg_rpc_vhost replaces trove_rabbitmq_vhost
|
||||
- added trove_oslomsg_notify_servers
|
||||
- added trove_oslomsg_notify_port
|
||||
- added trove_oslomsg_notify_use_ssl
|
||||
- added trove_oslomsg_notify_userid
|
||||
- added trove_oslomsg_notify_vhost
|
||||
- added trove_oslomsg_notify_password
|
@ -0,0 +1,20 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- barbican_oslomsg_rpc_servers replaces rabbitmq_servers
|
||||
- barbican_oslomsg_rpc_port replaces rabbitmq_port
|
||||
- barbican_oslomsg_rpc_userid replaces barbican_rabbitmq_userid
|
||||
- barbican_oslomsg_rpc_vhost replaces barbican_rabbitmq_vhost
|
||||
- added barbican_oslomsg_rpc_use_ssl
|
||||
- added barbican_oslomsg_notify_servers
|
||||
- added barbican_oslomsg_notify_port
|
||||
- added barbican_oslomsg_notify_use_ssl
|
||||
- added barbican_oslomsg_notify_userid
|
||||
- added barbican_oslomsg_notify_vhost
|
||||
- added barbican_oslomsg_notify_password
|
@ -0,0 +1,15 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- aodh_oslomsg_rpc_servers replaces aodh_rabbitmq_servers
|
||||
- aodh_oslomsg_rpc_port replaces aodh_rabbitmq_port
|
||||
- aodh_oslomsg_rpc_use_ssl replaces aodh_rabbitmq_use_ssl
|
||||
- aodh_oslomsg_rpc_userid replaces aodh_rabbitmq_userid
|
||||
- aodh_oslomsg_rpc_vhost replaces aodh_rabbitmq_vhost
|
||||
- aodh_oslomsg_rpc_password replaces aodh_rabbitmq_password
|
@ -0,0 +1,20 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- ceilometer_oslomsg_rpc_servers replaces rabbitmq_servers
|
||||
- ceilometer_oslomsg_rpc_port replaces rabbitmq_port
|
||||
- ceilometer_oslomsg_rpc_userid replaces ceilometer_rabbitmq_userid
|
||||
- ceilometer_oslomsg_rpc_vhost replaces ceilometer_rabbitmq_vhost
|
||||
- added ceilometer_oslomsg_rpc_use_ssl
|
||||
- added ceilometer_oslomsg_notify_servers
|
||||
- added ceilometer_oslomsg_notify_port
|
||||
- added ceilometer_oslomsg_notify_use_ssl
|
||||
- added ceilometer_oslomsg_notify_userid
|
||||
- added ceilometer_oslomsg_notify_vhost
|
||||
- added ceilometer_oslomsg_notify_password
|
@ -0,0 +1,20 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- designate_oslomsg_rpc_servers replaces designate_rabbitmq_servers
|
||||
- designate_oslomsg_rpc_port replaces designate_rabbitmq_port
|
||||
- designate_oslomsg_rpc_use_ssl replaces designate_rabbitmq_use_ssl
|
||||
- designate_oslomsg_rpc_userid replaces designate_rabbitmq_userid
|
||||
- designate_oslomsg_rpc_vhost replaces designate_rabbitmq_vhost
|
||||
- designate_oslomsg_notify_servers replaces designate_rabbitmq_telemetry_servers
|
||||
- designate_oslomsg_notify_port replaces designate_rabbitmq_telemetry_port
|
||||
- designate_oslomsg_notify_use_ssl replaces designate_rabbitmq_telemetry_use_ssl
|
||||
- designate_oslomsg_notify_userid replaces designate_rabbitmq_telemetry_userid
|
||||
- designate_oslomsg_notify_vhost replaces designate_rabbitmq_telemetry_vhost
|
||||
- designate_oslomsg_notify_password replaces designate_rabbitmq_telemetry_password
|
@ -0,0 +1,20 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- magnum_oslomsg_rpc_servers replaces rabbitmq_servers
|
||||
- magnum_oslomsg_rpc_port replaces rabbitmq_port
|
||||
- magnum_oslomsg_rpc_userid replaces magnum_rabbitmq_userid
|
||||
- magnum_oslomsg_rpc_vhost replaces magnum_rabbitmq_vhost
|
||||
- added magnum_oslomsg_rpc_use_ssl
|
||||
- added magnum_oslomsg_notify_servers
|
||||
- added magnum_oslomsg_notify_port
|
||||
- added magnum_oslomsg_notify_use_ssl
|
||||
- added magnum_oslomsg_notify_userid
|
||||
- added magnum_oslomsg_notify_vhost
|
||||
- added magnum_oslomsg_notify_password
|
@ -0,0 +1,15 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- swift_oslomsg_notify_servers replaces swift_rabbitmq_telemetry_servers
|
||||
- swift_oslomsg_notify_port replaces swift_rabbitmq_telemetry_port
|
||||
- swift_oslomsg_notify_use_ssl replaces swift_rabbitmq_telemetry_use_ssl
|
||||
- swift_oslomsg_notify_userid replaces swift_rabbitmq_telemetry_userid
|
||||
- swift_oslomsg_notify_vhost replaces swift_rabbitmq_telemetry_vhost
|
||||
- swift_oslomsg_notify_password replaces swift_rabbitmq_telemetry_password
|
@ -0,0 +1,20 @@
|
||||
---
|
||||
features:
|
||||
- Support separate oslo.messaging services for RPC and Notifications
|
||||
to enable operation of separate and different messaging backend servers.
|
||||
deprecations:
|
||||
- |
|
||||
The rabbitmq server parameters have been replaced by corresponding
|
||||
oslo.messaging RPC and Notify parameters in order to abstract the
|
||||
messaging service from the actual backend server deployment.
|
||||
- octavia_oslomsg_rpc_servers replaces octavia_rabbitmq_servers
|
||||
- octavia_oslomsg_rpc_port replaces octavia_rabbitmq_port
|
||||
- octavia_oslomsg_rpc_use_ssl replaces octavia_rabbitmq_use_ssl
|
||||
- octavia_oslomsg_rpc_userid replaces octavia_rabbitmq_userid
|
||||
- octavia_oslomsg_rpc_vhost replaces octavia_rabbitmq_vhost
|
||||
- octavia_oslomsg_notify_servers replaces octavia_rabbitmq_telemetry_servers
|
||||
- octavia_oslomsg_notify_port replaces octavia_rabbitmq_telemetry_port
|
||||
- octavia_oslomsg_notify_use_ssl replaces octavia_rabbitmq_telemetry_use_ssl
|
||||
- octavia_oslomsg_notify_userid replaces octavia_rabbitmq_telemetry_userid
|
||||
- octavia_oslomsg_notify_vhost replaces octavia_rabbitmq_telemetry_vhost
|
||||
- octavia_oslomsg_notify_password replaces octavia_rabbitmq_telemetry_password
|
10
releasenotes/notes/pypi-cache-removed-c03a9a0658c9d89f.yaml
Normal file
10
releasenotes/notes/pypi-cache-removed-c03a9a0658c9d89f.yaml
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
deprecations:
|
||||
- |
|
||||
The repo server's reverse proxy for pypi has now been removed,
|
||||
leaving only the pypiserver to serve packages already on the
|
||||
repo server. The attempt to reverse proxy upstream pypi turned
|
||||
out to be very unstable with increased complexity for deployers
|
||||
using proxies or offline installs. With this, the variables
|
||||
``repo_nginx_pypi_upstream`` and ``repo_nginx_proxy_cache_path``
|
||||
have also been removed.
|
6
releasenotes/notes/remove-v1-api-4c66f43c4f8404b6.yaml
Normal file
6
releasenotes/notes/remove-v1-api-4c66f43c4f8404b6.yaml
Normal file
@ -0,0 +1,6 @@
|
||||
---
|
||||
upgrade:
|
||||
- |
|
||||
The glance v1 API is now removed upstream and the deployment code is now
|
||||
removed from this glance ansible role. The variable ``glance_enable_v1_api``
|
||||
is removed.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``repo_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for sahara will now be executed
|
||||
through delegation to the ``sahara_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
sahara_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``sahara_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
The conditional that determines whether the ``sso_callback_template.html``
|
||||
file is deployed for federated deployments has been fixed.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The service setup in keystone for swift will now be executed
|
||||
through delegation to the ``swift_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
swift_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``swift_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
It is now possible to specify a list of tests for tempest to
|
||||
blacklist when executing using the ``tempest_test_blacklist``
|
||||
list variable.
|
@ -0,0 +1,17 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The trove service setup in keystone will now be executed
|
||||
through delegation to the ``trove_service_setup_host`` which,
|
||||
by default, is ``localhost`` (the deploy host). Deployers can
|
||||
opt to rather change this to the utility container by implementing
|
||||
the following override in ``user_variables.yml``.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
trove_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The variable ``trove_requires_pip_packages`` is no longer required
|
||||
and has therefore been removed.
|
Loading…
x
Reference in New Issue
Block a user