Fix role SHA's for Newton-3 release

Change-Id: Iac3fec6f70963e97d12cbe4fd8cafb05a99c56a2

ansible-role-requirements.yml

@@ -1,160 +1,160 @@
 - name: apt_package_pinning
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-apt_package_pinning
-  version: master
+  version: 2d802898d34ba9275dbf38641097eedb831d2a08
 - name: pip_install
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-pip_install
-  version: master
+  version: 2aa35cd95df220c7eb5474d949e8d2254114c305
 - name: galera_client
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-galera_client
-  version: master
+  version: 2d53f4d22232430cce07e9c041375d0900ebdf11
 - name: galera_server
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-galera_server
-  version: master
+  version: a3bb3b73b99e6097c6c876fd61d30d3bb56532f0
 - name: ceph_client
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-ceph_client
-  version: master
+  version: d3a0ac205a1e289deccf84776d5eb7c9a735d89d
 - name: haproxy_server
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-haproxy_server
-  version: master
+  version: 0b64c3aa58bba97db98fdfd90312c4fa82903a04
 - name: keepalived
   scm: git
   src: https://github.com/evrardjp/ansible-keepalived
-  version: master
+  version: 2.0.0
 - name: lxc_container_create
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-lxc_container_create
-  version: master
+  version: e81381092e340f93682fa88ad29649bb7294f577
 - name: lxc_hosts
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-lxc_hosts
-  version: master
+  version: fe749b5d7d819ab809e41c2d5d068d04148034eb
 - name: memcached_server
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-memcached_server
-  version: master
+  version: 736969d00ccdc6716d1b99e42485a9f7b2febffe
 - name: openstack-ansible-security
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-security
-  version: master
+  version: 83dd342b19b9982115ec22fd4cedcad7593baf4f
 - name: openstack_hosts
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-openstack_hosts
-  version: master
+  version: cb25f0b227c667bef97eec17476b998cbdd0fb06
 - name: os_keystone
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_keystone
-  version: master
+  version: 2b8aa0703cbdbb27ecbcb27aee0ea0f9d2a7037a
 - name: openstack_openrc
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-openstack_openrc
-  version: master
+  version: a45ef54b8ec345fea3399878b5d6e698be290809
 - name: os_aodh
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_aodh
-  version: master
+  version: 52b7dd42e885c4b502528b53544c297200837565
 - name: os_ceilometer
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_ceilometer
-  version: master
+  version: de037c4d3fd48728f3f63530d4818519ba924c5a
 - name: os_cinder
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_cinder
-  version: master
+  version: 8bc6f640036be3121d1c3f48595d8e2af11357bf
 - name: os_glance
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_glance
-  version: master
+  version: 66e8dc3b6eb3032888e5da9fbf869c278e75b5e6
 - name: os_gnocchi
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_gnocchi
-  version: master
+  version: 6d63addcfb0f267dca6e9cc1ce5c0df295ef5950
 - name: os_heat
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_heat
-  version: master
+  version: 8878e8c44d59a326211b705dc1808c55bdbb49d7
 - name: os_horizon
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_horizon
-  version: master
+  version: 0b6085c00709c7138f862a41441306fb6a6bafee
 - name: os_ironic
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_ironic
-  version: master
+  version: 581ce2053c01d7f7848db95b895785c6b33a41ed
 - name: os_magnum
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_magnum
-  version: master
+  version: 2cf15a702fde842c219ea96d8e3d439f305f8a8f
 - name: os_neutron
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_neutron
-  version: master
+  version: 91a5eff62b4250a29fd346ee23e8fce2503fa126
 - name: os_nova
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_nova
-  version: master
+  version: 57cc173e6d46bb1664f446dde8efb224671dce85
 - name: os_rally
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_rally
-  version: master
+  version: bf15d504effda5d78e7645cf36906dc37c2ab7ff
 - name: os_sahara
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_sahara
-  version: master
+  version: c3e9c5f47fcce63b8a175c87b9b191b98ea83ab0
 - name: os_swift
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_swift
-  version: master
+  version: 43a6244eccc909ae9a3cef35d991f45d058770cd
 - name: os_tempest
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-os_tempest
-  version: master
+  version: a3b77be7279d3a6d45c8cc48e6a06c296117b2f3
 - name: plugins
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-plugins
-  version: master
+  version: ffb02cfb550a0ebf4ab88e9241a8d42bc17751a4
 - name: rabbitmq_server
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-rabbitmq_server
-  version: master
+  version: dbcd0986a3641354a7d216379879f36f59af9428
 - name: repo_build
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-repo_build
-  version: master
+  version: aa2c987840d1ee4848386b14cf0a5bd42b5a01c3
 - name: repo_server
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-repo_server
-  version: master
+  version: 07aa872e9f5081ac408bbb6dab1afd94428c66e4
 - name: rsyslog_client
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-rsyslog_client
-  version: master
+  version: 90130c02df7f994195dfa986fa4fe715b83f6858
 - name: rsyslog_server
   scm: git
   src: https://git.openstack.org/openstack/openstack-ansible-rsyslog_server
-  version: master
+  version: 02eebf7884549d7fc29320ef706aa977f6bd4667
 - name: sshd
   scm: git
   src: https://github.com/willshersystems/ansible-sshd
-  version: master
+  version: 0.4.5
 - name: bird
   scm: git
   src: https://github.com/logan2211/ansible-bird
-  version: master
+  version: a4eb99569e41bc0a01d062516c6439d8dcf7fa58
 - name: etcd
   scm: git
   src: https://github.com/logan2211/ansible-etcd
-  version: master
+  version: d329b069d70f685e14ce0329ebe52fcc60dd1e64
 - name: unbound
   scm: git
   src: https://github.com/logan2211/ansible-unbound
-  version: master
+  version: 91e82005c4f30fb040152ed49815006e95b5b53a
 - name: resolvconf
   scm: git
   src: https://github.com/logan2211/ansible-resolvconf
-  version: master
+  version: d724ea9872c7d38de964008a533ada3f83a387d9

releasenotes/notes/add-disk-image-type-932898aca944f14a.yaml

@@ -0,0 +1,4 @@
+---
+features:
+  - Added new parameter ```cirros_img_disk_format``
+    to support disk formats other than qcow2.

releasenotes/notes/add-horizon-magnum-dashboard-support-4fcddedffb83bc28.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - The os_horizon role now has support for the horizon magnum-ui dashboard. The
+    dashboard may be enabled by setting ``horizon_enable_magnum_ui`` to ``True``
+    in ``/etc/openstack_deploy/user_variables.yml``.

releasenotes/notes/add-keystone-admin-roles-setting-83198a721c64ee3c.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - The ``horizon_keystone_admin_roles`` variable is added to support the
+    ``OPENSTACK_KEYSTONE_ADMIN_ROLES`` list in the horizon_local_settings.py
+    file.

releasenotes/notes/add-network-name-variables-d658745d7113110e.yaml

@@ -0,0 +1,8 @@
+---
+fixes:
+  - This role assumes that there is a network named "public|private" and a
+    subnet named "public|private-subnet". These names are made configurable
+    by the addition of two sets of variables; ``tempest_public_net_name``
+    and ``tempest_public_subnet_name`` for public networks and 
+    ``tempest_private_net_name`` and ``tempest_private_subnet_name`` for
+    private networks This addresses `bug 1588818 <https://bugs.launchpad.net/openstack-ansible/+bug/1588818>`_

releasenotes/notes/add-nova-lxd-f094438e4bf36d52.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - The os_nova role can now deploy the nova-lxd hypervisor.
+    This can be achieved by setting ``nova_virt_type`` to
+    ``lxd`` on a per-host basis in ``openstack_user_config.yml``
+    or on a global basis in ``user_variables.yml``.

releasenotes/notes/adding-v38526-381a407caa566b14.yaml

@@ -0,0 +1,8 @@
+---
+features:
+  - |
+    A task was added to disable secure ICMP redirects per the requirements in
+    V-38526. This change can cause problems in some environments, so it is
+    disabled by default. Deployers can enable the task (which disables secure
+    ICMP redirects) by setting ``security_disable_icmpv4_redirects_secure`` to
+    ``yes``.

releasenotes/notes/adding-v38548-9c51b30bf9780ff3.yaml

@@ -0,0 +1,8 @@
+---
+features:
+  - |
+    A new task was added to disable ICMPv6 redirects per the requirements in
+    V-38548. However, since this change can cause problems in running OpenStack
+    environments, it is disabled by default. Deployers who wish to enable this
+    task (and disable ICMPv6 redirects) should set
+    ``security_disable_icmpv6_redirects`` to ``yes``.

releasenotes/notes/aide-exclude-run-4d3c97a2d08eb373.yaml

@@ -0,0 +1,6 @@
+---
+fixes:
+  - |
+    The ``/run`` directory is excluded from AIDE checks since the files and
+    directories there are only temporary and often change when services
+    start and stop.

releasenotes/notes/aide-initialization-fix-16ab0223747d7719.yaml

@@ -0,0 +1,17 @@
+---
+features:
+  - |
+    AIDE is configured to skip the entire ``/var`` directory when it does the
+    database initialization and when it performs checks. This reduces disk
+    I/O and allows these jobs to complete faster.
+
+    This also allows the initialization to become a blocking process and
+    Ansible will wait for the initialization to complete prior to running the
+    next task.
+fixes:
+  - |
+    AIDE initialization is now always run on subsequent playbook runs when
+    ``security_initialize_aide`` is set to ``yes``. The initialization will
+    be skipped if AIDE isn't installed or if the AIDE database already exists.
+
+    See `bug 1616281 <https://launchpad.net/bugs/1616281>`_ for more details.

releasenotes/notes/base-container-lvm-cow-2faa824f6cd4b083.yaml

@@ -0,0 +1,14 @@
+---
+features:
+  - The container cache preparation process now allows ``copy-on-write`` to be
+    set as the ``lxc_container_backing_method`` when the
+    ``lxc_container_backing_store`` is set to ``lvm``. When this is set a base
+    container will be created using a name of the form
+    `<linux-distribution>`-`distribution-release>`-`<host-cpu-architecture>`.
+    The container will be stopped as it is not used for anything except to be
+    a backing store for all other containers which will be based on a snapshot
+    of the base container.
+  - When using copy-on-write backing stores for containers, the base container
+    name may be set using the variable ``lxc_container_base_name`` which
+    defaults to
+    `<linux-distribution>`-`distribution-release>`-`<host-cpu-architecture>`.

releasenotes/notes/broader-image-support-69241983e5a36018.yaml

@@ -0,0 +1,30 @@
+---
+features:
+  - Added new variable ``tempest_img_name``.
+  - Added new variable ``tempest_img_url``.
+    This variable replaces ``cirros_tgz_url`` and ``cirros_img_url``.
+  - Added new variable ``tempest_image_file``.
+    This variable replaces the hard-coded value
+    for the ``img_file`` setting in tempest.conf.j2.  This will
+    allow users to specify images other than cirros.
+  - Added new variable ``tempest_img_disk_format``.
+    This variable replaces ``cirros_img_disk_format``.
+deprecations:
+  - Removed ``cirros_tgz_url`` and in most places replaced
+    with ``tempest_img_url``.
+  - Removed ``cirros_img_url`` and in most places replaced
+    with ``tempest_img_url``.
+  - Removed deprecated variable ``tempest_compute_image_alt_ssh_user``
+  - Removed deprecated variable ``tempest_compute_image_ssh_password``
+  - Removed deprecated variable
+    ``tempest_compute_image_alt_ssh_password``
+  - Renamed ``cirros_img_disk_format`` to ``tempest_img_disk_format``
+  - Downloading and unarchiving a .tar.gz has been removed.  The
+    related tempest options ``ami_img_file``, ``aki_img_file``, and
+    ``ari_img_file`` have been removed from tempest.conf.j2.
+  - The ``[boto]`` section of tempest.conf.j2 has been removed.  These
+    tests have been completely removed from tempest for some time.
+fixes:
+  - Removed various deprecated / no longer supported
+    features from tempest.conf.j2.  Some variables have been moved
+    to their new sections in the config.

releasenotes/notes/container-bind-mounts-1a3a763178255841.yaml

@@ -0,0 +1,12 @@
+---
+features:
+  - The ``lxc-container-create`` role now consumes the variable
+    ``lxc_container_bind_mounts`` which should contain a list
+    of bind mounts to apply to a newly created container. The
+    appropriate host and container directory will be created and
+    the configuration applied to the container config. This
+    feature is designed to be used in group_vars to ensure that
+    containers are fully prepared at the time they are created,
+    thus cutting down the number of times containers are restarted
+    during deployments and upgrades.
+

releasenotes/notes/container-create-lvm-cow-77c049188b8a2676.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - The container creation process now allows ``copy-on-write`` to be set as
+    the ``lxc_container_backing_method`` when the
+    ``lxc_container_backing_store`` is set to ``lvm``. When this is set it
+    will use a snapshot of the base container to build the containers.

releasenotes/notes/deprecate-repo-apt-packages-f8c4a22fc60828bf.yaml

@@ -1,5 +1,5 @@
 ---
-deprecations:
+upgrade:
-  - The ``repo_apt_packages`` variable has been deprecated.
+  - The variable ``repo_server_packages`` that defines the list of packages
-    ``repo_server_packages`` should be used instead to override
+    required to install a repo server has been replaced
-    packages required to install a repo server.
+    by ``repo_server_distro_packages``.

releasenotes/notes/enable-tcp-syncookes-boolean-4a884a66a3a0e4d7.yaml

@@ -0,0 +1,11 @@
+---
+upgrade:
+  - |
+    The variable ``security_sysctl_enable_tcp_syncookies`` has replaced
+    ``security_sysctl_tcp_syncookies`` and it is now a boolean instead of an
+    integer.  It is still enabled by default, but deployers can disable TCP
+    syncookies by setting the following Ansible variable:
+
+    .. code-block:: yaml
+
+       security_sysctl_enable_tcp_syncookies: no

releasenotes/notes/lxc-cache-gpg-156169a867d4653f.yaml

@@ -0,0 +1,7 @@
+---
+features:
+  - The lxc_hosts role can now make use of a primary and secondary gpg
+    keyserver for gpg validation of the downloaded cache. Setting the
+    servers to use can be done using the
+    ``lxc_image_cache_primary_keyserver`` and
+    ``lxc_image_cache_secondary_keyserver`` variables.

releasenotes/notes/lxc-container-start-delay-d7917f69d9469316.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - The LXC container creation process now has a configurable
+    delay for the task which waits for the container to start.
+    The variable ``lxc_container_ssh_delay`` can be set to
+    change the default delay of five seconds.

releasenotes/notes/multi-arch-build-1ad512acdf6cabb9.yaml

@@ -0,0 +1,7 @@
+---
+features:
+  - The repo build process is now able to support building and synchronizing
+    artifacts for multiple CPU architectures. Build artifacts are now tagged
+    with the appropriate CPU architecture by default, and synchronization of
+    build artifacts from secondary, architecture-specific repo servers back
+    to the primary repo server is supported.

releasenotes/notes/multi-distro-add-0e53560f66394691.yaml

@@ -1,12 +1,6 @@
 ---
 features:
   - CentOS 7 support has been added to the ``galera_client`` role.
-deprecations:
+upgrade:
-  - The variable **galera_client_apt_packages** has been deprecated
+  - The variable ``galera_client_apt_packages`` has been replaced
-    when deploying the ``galera_client`` role on Ubuntu 14.04. This
+    by ``galera_client_distro_packages``.
-    variable has been replaced with **galera_client_packages** and
-    will be removed in the Ocata release.
-  - The variable **galera_apt_pinned_packages** has been deprecated
-    when deploying the ``galera_client`` role on Ubuntu 14.04. This
-    variable has been replaced with **galera_pinned_packages**
-    and will be removed in the Ocata release.

releasenotes/notes/neutron-bgp-552e6e1f6d37f38d.yaml

@@ -0,0 +1,9 @@
+---
+features:
+  - "Neutron BGP dynamic routing plugin can now optionally be deployed and
+    configured. Please see `OpenStack Networking Guide: BGP dynamic routing
+    <http://docs.openstack.org/networking-guide/config-bgp-dynamic-routing.html>`_
+    for details about what the service is and what it provides."
+upgrade:
+  - Database migration tasks have been added for the dynamic routing neutron
+    plugin.

releasenotes/notes/neutron-networking-calico-b05b08f989f768ee.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - The Project Calico Neutron networking plugin is now integrated into the
+    ``os_neutron`` role. This can be activated using the instructions located
+    in the role documentation.

releasenotes/notes/online-lxc-network-add-3cfc84ea28e5eab0.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - The LXC container creation and modification process now supports
+    online network additions. This ensures a container remains online
+    when additional networks are added to a system.

releasenotes/notes/opportunistic-strategy-and-connection-plugin-bc476fa3607dcc4a.yaml

@@ -0,0 +1,11 @@
+---
+features:
+  - An opportunistic Ansible execution strategy has been implemented. This
+    allows the Ansible linear strategy to skip tasks with conditionals faster
+    by never queuing the task when the conditional is evaluated to be false.
+  - The Ansible SSH plugin has been modified to support running commands within
+    containers without having to directly ssh into them. The change will detect
+    presence of a container. If a container is found the physical host will be
+    used as the SSH target and commands will be run directly. This will improve
+    system reliability and speed while also opening up the possibility for SSH
+    to be disabled from within the container itself.

releasenotes/notes/os_keystone-centos7-support-0a5d97f81ac42e44.yaml

@@ -0,0 +1,4 @@
+---
+features:
+  - CentOS7/RHEL support has been added to the os_keystone
+    role.

releasenotes/notes/os_magnum-install-venv-30263e29e51a2610.yaml

@@ -0,0 +1,5 @@
+---
+upgrade:
+  - Installation of magnum and its dependent pip packages will now only
+    occur within a Python virtual environment. The ``magnum_venv_bin``,
+    ``magnum_venv_enabled`` variables have been removed.

releasenotes/notes/os_magnum-xenial-systemd-support-2e1ee4253dff2b5c.yaml

@@ -0,0 +1,4 @@
+---
+features:
+  - The ``os_magnum`` role now supports deployment on Ubuntu 16.04 using
+    systemd.

releasenotes/notes/os_rally-install-venv-71cbd1f6ce4fd983.yaml

@@ -0,0 +1,5 @@
+---
+upgrade:
+  - Installation of rally and its dependent pip packages will now only
+    occur within a Python virtual environment. The ``rally_venv_bin``,
+    ``rally_venv_enabled`` variables have been removed.

releasenotes/notes/os_sahara-only-install-venv-8ead48687897ce0b.yaml

@@ -0,0 +1,6 @@
+---
+upgrade:
+  - Installation of sahara and its dependent pip packages will now only
+    occur within a Python virtual environment. The ``sahara_venv_bin``,
+    ``sahara_venv_enabled``, ``sahara_venv_etc_dir``, and
+    ``sahara_non_venv_etc_dir`` variables have been removed.

releasenotes/notes/package-list-name-changes-007cacee4faf8ee6.yaml

@@ -0,0 +1,10 @@
+---
+upgrade:
+  - The variable ``keystone_apt_packages`` has been renamed to
+    ``keystone_distro_packages``.
+  - The variable ``keystone_idp_apt_packages`` has been renamed to
+    ``keystone_idp_distro_packages``.
+  - The variable ``keystone_sp_apt_packages`` has been renamed to
+    ``keystone_sp_distro_packages``.
+  - The variable ``keystone_developer_apt_packages`` has been renamed to
+    ``keystone_developer_mode_distro_packages``.

releasenotes/notes/package-list-name-changes-38f1554097b6bbe9.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``glance_apt_packages`` has been renamed to
+    ``glance_distro_packages``.

releasenotes/notes/package-list-name-changes-4a42f561dac5754e.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``horizon_apt_packages`` has been renamed to
+    ``horizon_distro_packages``.

releasenotes/notes/package-list-name-changes-4d5ad2e6ff5ecae2.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``aodh_apt_packages`` has been renamed to
+    ``aodh_distro_packages``.

releasenotes/notes/package-list-name-changes-6f74fbf336030242.yaml

@@ -0,0 +1,8 @@
+---
+upgrade:
+  - The variable ``cinder_apt_packages`` has been renamed to
+    ``cinder_distro_packages``.
+  - The variable ``cinder_volume_apt_packages`` has been renamed to
+    ``cinder_volume_distro_packages``.
+  - The variable ``cinder_lvm_volume_apt_packages`` has been renamed to
+    ``cinder_lvm_volume_distro_packages``.

releasenotes/notes/package-list-name-changes-7c8a6dd652b271cf.yaml

@@ -0,0 +1,8 @@
+---
+upgrade:
+  - The variable ``ironic_api_apt_packages`` has been renamed to
+    ``ironic_api_distro_packages``.
+  - The variable ``ironic_conductor_apt_packages`` has been renamed to
+    ``ironic_conductor_distro_packages``.
+  - The variable ``ironic_conductor_standalone_apt_packages`` has been renamed to
+    ``ironic_conductor_standalone_distro_packages``.

releasenotes/notes/package-list-name-changes-7fcd5583f0db0eb6.yaml

@@ -0,0 +1,6 @@
+---
+upgrade:
+  - The variable ``galera_pre_packages`` has been renamed to
+    ``galera_server_required_distro_packages``.
+  - The variable ``galera_packages`` has been renamed to
+    ``galera_server_mariadb_distro_packages``.

releasenotes/notes/package-list-name-changes-a26d94a44c24de2f.yaml

@@ -0,0 +1,6 @@
+---
+upgrade:
+  - The variable ``haproxy_pre_packages`` has been renamed to
+    ``haproxy_required_distro_packages``.
+  - The variable ``haproxy_packages`` has been renamed to
+    ``haproxy_distro_packages``.

releasenotes/notes/package-list-name-changes-a5571c0b72faadf2.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``memcached_apt_packages`` has been renamed to
+    ``memcached_distro_packages``.

releasenotes/notes/package-list-name-changes-a86f7e7c805c2d81.yaml

@@ -0,0 +1,10 @@
+---
+upgrade:
+  - The variable ``neutron_apt_packages`` has been renamed to
+    ``neutron_distro_packages``.
+  - The variable ``neutron_lbaas_apt_packages`` has been renamed to
+    ``neutron_lbaas_distro_packages``.
+  - The variable ``neutron_vpnaas_apt_packages`` has been renamed to
+    ``neutron_vpnaas_distro_packages``.
+  - The variable ``neutron_apt_remove_packages`` has been renamed to
+    ``neutron_remove_distro_packages``.

releasenotes/notes/package-list-name-changes-b484be7645bbe66a.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``heat_apt_packages`` has been renamed to
+    ``heat_distro_packages``.

releasenotes/notes/package-list-name-changes-e351db8b482f1326.yaml

@@ -0,0 +1,6 @@
+---
+upgrade:
+  - The variable ``ceilometer_apt_packages`` has been renamed to
+    ``ceilometer_distro_packages``.
+  - The variable ``ceilometer_developer_mode_apt_packages`` has been renamed to
+    ``ceilometer_developer_mode_distro_packages``.

releasenotes/notes/package-list-name-changes-e7a3fc551d742d23.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``lxc_apt_packages`` has been renamed to
+    ``lxc_hosts_distro_packages``.

releasenotes/notes/package-list-name-changes-fdf9c6573bfa1083.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``openstack_host_apt_packages`` has been renamed to
+    ``openstack_host_distro_packages``.

releasenotes/notes/package-state-003ff33c557af3b5.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The galera_client role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``galera_client_package_state`` to ``present``.
+upgrade:
+  - The galera_client role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``galera_client_package_state`` should be set to ``present``.

releasenotes/notes/package-state-2e8e2eb4b24475c4.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_ironic role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``ironic_package_state`` to ``present``.
+upgrade:
+  - The os_ironic role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``ironic_package_state`` should be set to ``present``.

releasenotes/notes/package-state-38187ec5242a005b.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_nova role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``nova_package_state`` to ``present``.
+upgrade:
+  - The os_nova role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``nova_package_state`` should be set to ``present``.

releasenotes/notes/package-state-3bf07796262fc9b9.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The memcached_server role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``memcached_package_state`` to ``present``.
+upgrade:
+  - The memcached_server role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``memcached_package_state`` should be set to ``present``.

releasenotes/notes/package-state-441864557ee5d75b.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_heat role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``heat_package_state`` to ``present``.
+upgrade:
+  - The os_heat role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``heat_package_state`` should be set to ``present``.

releasenotes/notes/package-state-48e933a395bbdc0c.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The rsyslog_server role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``rsyslog_server_package_state`` to ``present``.
+upgrade:
+  - The rsyslog_server role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``rsyslog_server_package_state`` should be set to ``present``.

releasenotes/notes/package-state-505f9772bb0d668e.yaml

@@ -0,0 +1,14 @@
+---
+features:
+  - The pip_install role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``pip_install_package_state`` to ``present``.
+upgrade:
+  - The pip_install role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``pip_install_package_state`` should be set to ``present``.
+

releasenotes/notes/package-state-55fceaf0cd23147e.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The repo_build role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``repo_build_package_state`` to ``present``.
+upgrade:
+  - The repo_build role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``repo_build_package_state`` should be set to ``present``.

releasenotes/notes/package-state-63a870de53dd5cd8.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_rally role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``rally_package_state`` to ``present``.
+upgrade:
+  - The os_rally role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``rally_package_state`` should be set to ``present``.

releasenotes/notes/package-state-646b25638f523411.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_glance role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``glance_package_state`` to ``present``.
+upgrade:
+  - The os_glance role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``glance_package_state`` should be set to ``present``.

releasenotes/notes/package-state-6684c5634bdf127a.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The security role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``security_package_state`` to ``present``.
+upgrade:
+  - The security role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``security_package_state`` should be set to ``present``.

releasenotes/notes/package-state-711a1eb4814311cc.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_keystone role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``keystone_package_state`` to ``present``.
+upgrade:
+  - The os_keystone role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``keystone_package_state`` should be set to ``present``.

releasenotes/notes/package-state-7caea8f1db708a2e.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_cinder role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``cinder_package_state`` to ``present``.
+upgrade:
+  - The os_cinder role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``cinder_package_state`` should be set to ``present``.

releasenotes/notes/package-state-7cbc7179b51ecdde.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_gnocchi role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``gnocchi_package_state`` to ``present``.
+upgrade:
+  - The os_gnocchi role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``gnocchi_package_state`` should be set to ``present``.

releasenotes/notes/package-state-7d62ea1e50ad391b.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_magnum role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``magnum_package_state`` to ``present``.
+upgrade:
+  - The os_magnum role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``magnum_package_state`` should be set to ``present``.

releasenotes/notes/package-state-8b0189f8824b7568.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The rsyslog_client role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``rsyslog_client_package_state`` to ``present``.
+upgrade:
+  - The rsyslog_client role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``rsyslog_client_package_state`` should be set to ``present``.

releasenotes/notes/package-state-979c963fb18f7a25.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_sahara role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``sahara_package_state`` to ``present``.
+upgrade:
+  - The os_sahara role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``sahara_package_state`` should be set to ``present``.

releasenotes/notes/package-state-9a2f60adb4ab68cd.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The repo_server role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``repo_server_package_state`` to ``present``.
+upgrade:
+  - The repo_server role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``repo_server_package_state`` should be set to ``present``.

releasenotes/notes/package-state-b032231a3cc99ee0.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_aodh role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``aodh_package_state`` to ``present``.
+upgrade:
+  - The os_aodh role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``aodh_package_state`` should be set to ``present``.

releasenotes/notes/package-state-b41a0e911ad95d1c.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The openstack_hosts role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``openstack_hosts_package_state`` to ``present``.
+upgrade:
+  - The openstack_hosts role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``openstack_hosts_package_state`` should be set to ``present``.

releasenotes/notes/package-state-b7a3d3c242e2c3aa.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The galera_server role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``galera_server_package_state`` to ``present``.
+upgrade:
+  - The galera_server role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``galera_server_package_state`` should be set to ``present``.

releasenotes/notes/package-state-bb93a1d4b272425d.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The rabbitmq_server role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``rabbitmq_package_state`` to ``present``.
+upgrade:
+  - The rabbitmq_server role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``rabbitmq_package_state`` should be set to ``present``.

releasenotes/notes/package-state-c9c7e01e77b596d0.yaml

@@ -0,0 +1,14 @@
+---
+features:
+  - The lxc_hosts role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``lxc_hosts_package_state`` to ``present``.
+upgrade:
+  - The lxc_hosts role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``lxc_hosts_package_state`` should be set to ``present``.
+

releasenotes/notes/package-state-ed22b9a6683690b3.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_ceilometer role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``ceilometer_package_state`` to ``present``.
+upgrade:
+  - The os_ceilometer role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``ceilometer_package_state`` should be set to ``present``.

releasenotes/notes/package-state-f2309b07440d0ae8.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_swift role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``swift_package_state`` to ``present``.
+upgrade:
+  - The os_swift role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``swift_package_state`` should be set to ``present``.

releasenotes/notes/package-state-fb7d26a4b7c41a77.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_neutron role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``neutron_package_state`` to ``present``.
+upgrade:
+  - The os_neutron role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``neutron_package_state`` should be set to ``present``.

releasenotes/notes/package-state-fda322f5e667bbec.yaml

@@ -0,0 +1,13 @@
+---
+features:
+  - The os_horizon role now supports the ability to configure whether
+    apt/yum tasks install the latest available package, or just ensure
+    that the package is present. The default action is to ensure that
+    the latest package is present. The action taken may be changed to
+    only ensure that the package is present by setting
+    ``horizon_package_state`` to ``present``.
+upgrade:
+  - The os_horizon role always checks whether the latest package is
+    installed when executed. If a deployer wishes to change the check to
+    only validate the presence of the package, the option
+    ``horizon_package_state`` should be set to ``present``.

releasenotes/notes/package-var-rename-6ec3af6242073a2e.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``rsyslog_client_packages`` has been replaced
+    by ``rsyslog_client_distro_packages``.

releasenotes/notes/package_var_rename-9a55f7030595fdef.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The variable ``rsyslog_server_packages`` has been replaced
+    by ``rsyslog_server_distro_packages``.

releasenotes/notes/remove-lvm-config-from-openstack-hosts-efb7d0b3a22d49df.yaml

@@ -0,0 +1,6 @@
+---
+upgrade:
+  - |
+    The LVM configuration tasks and ``lvm.conf`` template have been removed
+    from the ``openstack_hosts`` role since they are no longer needed. All of
+    the LVM configuration is properly handled in the ``os_cinder`` role.

releasenotes/notes/remove-rsyslog_client_repos-055ce574bee8bd14.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - In the ``rsyslog_client`` role, the variable ``rsyslog_client_repos`` has
+    been removed as it is no longer used.

releasenotes/notes/removed-aodh-api-init-9e2406629196efff.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - The aodh-api init service is removed since aodh-api is deployed as an
+    apache mod_wsgi service.

releasenotes/notes/repo-build-deprecate-repo-build-apt-packages-df1ca334b857787a.yaml

@@ -1,5 +1,5 @@
 ---
-deprecations:
+upgrade:
-  - The ``repo_build_apt_packages`` variable has been deprecated.
+  - The ``repo_build_apt_packages`` variable has been renamed.
-    ``repo_build_packages`` should be used instead to override
+    ``repo_build_distro_packages`` should be used instead to
-    packages required to build Python wheels and venvs.
+    override packages required to build Python wheels and venvs.

releasenotes/notes/sahara-horizon-panel-d80d17da528b4c07.yaml

@@ -0,0 +1,9 @@
+---
+features:
+  - |
+    The Sahara dashboard is available in Horizon. Deployers can enable
+    the panel by setting the following Ansible variable:
+
+    .. code-block:: yaml
+
+        horizon_enable_sahara_ui: True

releasenotes/notes/selective-git-clone-77d766cc0eaa2175.yaml

@@ -0,0 +1,8 @@
+---
+features:
+  - The repo build process now selectively clones git repositories
+    based on whether each OpenStack service group has any hosts in
+    it. If there are no hosts in the group, the git repo for the
+    service will not be cloned. This behaviour can be optionally
+    changed to force all git repositories to be cloned by setting
+    ``repo_build_git_selective`` to ``no``.

releasenotes/notes/selective-wheel-build-34b1c154bb548ed7.yaml

@@ -0,0 +1,8 @@
+---
+features:
+  - The repo build process now selectively builds python packages
+    based on whether each OpenStack service group has any hosts in
+    it. If there are no hosts in the group, the list of python
+    packages for the service will not be built. This behaviour can
+    be optionally changed to force all python packages to be built
+    by setting ``repo_build_wheel_selective`` to ``no``.

releasenotes/notes/service-conf-path-b27cab31dbc72ad4.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - A new variable is supported in the ``neutron_services`` dictionary called
+    ``service_conf_path``. This variable enables services to deploy their
+    config templates to paths outside of /etc/neutron by specifying a
+    directory using the new variable.

releasenotes/notes/swift-syslog-log-perms-5a116171a1adeae3.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - The os_swift role now allows the permissions for the log files created
+    by the swift account, container and object servers to be set. The
+    variable is ``swift_syslog_log_perms`` and is set to ``0644`` by
+    default.

releasenotes/notes/upper-constraints-override-6853ffec6c07d7f5.yaml

@@ -0,0 +1,9 @@
+---
+features:
+  - The ``repo_build`` role now provides the ability to override the
+    upper-constraints applied which are sourced from OpenStack and
+    from the global-requirements-pins.txt file. The variable
+    ``repo_build_upper_constraints_overrides`` can be populated with
+    a list of upper constraints. This list will take the highest
+    precedence in the constraints process, with the exception of
+    the pins set in the git source SHAs.

releasenotes/notes/var-deprecations-417d87b9d386466a.yaml

@@ -1,12 +1,11 @@
 ---
-deprecations:
+upgrade:
   - |
     The following variables have been renamed in order to make the variable
     names neutral for multiple operating systems.
 
-      * nova_apt_packages -> nova_packages
+      * nova_apt_packages -> nova_distro_packages
-      * nova_spice_apt_packages -> nova_spice_packages
+      * nova_spice_apt_packages -> nova_spice_distro_packages
-      * nova_novnc_apt_packages -> nova_novnc_packages
+      * nova_novnc_apt_packages -> nova_novnc_distro_packages
-      * nova_compute_kvm_apt_packages -> nova_compute_kvm_package
+      * nova_compute_kvm_apt_packages -> nova_compute_kvm_distro_packages
 
-    The old variable names will be removed in the Ocata cycle.

releasenotes/notes/xtrabackup-compact-disable-8ae9215207147ebc.yaml

@@ -0,0 +1,4 @@
+---
+fixes:
+  - The ``--compact`` flag has been removed from xtrabackup options. This had been
+    shown to cause crashes in some SST situations