gistfile1.txt

=============
Release Notes
=============

r14.1.0
=======

Prelude
-------

.. releasenotes/notes/releasenotes-a800a042ad4e67cf.yaml @ e57ee85741bce8d541f7608865c725db3a0d967b

Reno release notes will now be provided as of newton-14.1!


New Features
------------

.. releasenotes/notes/add-maas-checks-for-filbeat-es-rsyslog-0289a1d9a1c198d0.yaml @ 2870f4e2d1c0571f66b0017ed984fe928e460c12

- This adds MaaS checks for elasticsearch, filebeat, and
  rsyslog. It checks the processes are running or not. If not,
  it will create an alarm.

.. releasenotes/notes/add-magnum-f5-93cc4c09fdb60d23.yaml @ 4356902a55deeb2a2ac5067f3f0fa812396c5877

- Added a Public endpoint for Magnum API

.. releasenotes/notes/add-tempest-execution-playbook-efe64a286f255c34.yaml @ 0e589df4fc7ce4327ea615c8ca28f72ee4920fce

- A new playbook has been introduced in the ``scripts/`` directory called
  ``run_tempest.yml``. This playbook will install tempest using the upstream
  OSA role, then execute the tempest tests defined in the sets enumerated
  in the ``tempest_test_sets`` variable.

.. releasenotes/notes/add-tempest-execution-playbook-efe64a286f255c34.yaml @ 0e589df4fc7ce4327ea615c8ca28f72ee4920fce

- A new variable, ``tempest_test_sets`` has been added to
  group_vars/all/rpc-o.yml. This variable contains a space-delimited string
  of tempest test sets to execute when running the ``scripts/run_tempest.yml``
  playbook.

.. releasenotes/notes/handle-merging-new-secrets-0e1fd06d86f0abbd.yaml @ 01d08b82dd972554e352036af83dd7f9f18c170d

- The ``update-yaml.py`` script now contains an optional argument, ``--output-file``, for specifying an output file.

.. releasenotes/notes/maas-version-var-2ea08457b0ad00b4.yaml @ 7765b305045f8f7f3a06148bbb9de62795f38e97

- RPC-MaaS has been seperated out into it's own repo. This change allows maas to be developed outside of rpc and maintained as an OpenStack version agnostic deployment for all things monitoring.

.. releasenotes/notes/maas-version-var-2ea08457b0ad00b4.yaml @ 7765b305045f8f7f3a06148bbb9de62795f38e97

- A variable has been added to allow RPC-MaaS to locked down to a specific version of the repo as needed. This variable is ``maas_version`` which has a default of "master".

.. releasenotes/notes/releasenotes-a800a042ad4e67cf.yaml @ e57ee85741bce8d541f7608865c725db3a0d967b

- Reno release notes will now be provided as of newton-14.1!


Known Issues
------------

.. releasenotes/notes/always-set-logging_upgrade-true-c7c4f7ffe1551372.yaml @ 74f832843f5997c9d6943d676727c2d99dd4fdee

- When upgrading ElasticSearch from RPCO r12 to r13, failure to set the Ansible var logging_upgrade=true may result in data corruption.


Upgrade Notes
-------------

.. releasenotes/notes/ceph-upgrade-434a53379d0db8f5.yaml @ faede343c6459f62257f35e74a6f39c0a9ae067f

- The ceph monitors and osds needs their configuration file to be updated for the Mitaka release, to adapt with the hostnames changes done in Mitaka. Please backup, destroy, and re-create the monitors, and make them rejoin the cluster in a serial way. The osds also need to have their configuration file updated.

.. releasenotes/notes/ceph-upgrade-434a53379d0db8f5.yaml @ faede343c6459f62257f35e74a6f39c0a9ae067f

- When re-created during the upgrade procedure, the ceph monitors will now have bind mounts to the hosts. This will make the backup of the mons easier in the future.

.. releasenotes/notes/elasticsearch-upgrade-a56013c6aa97b718.yaml @ d14f01c9ec62562cb5cb5212f268286e4567fff6

- The `elasticsearch-upgrade-pre.yml` play takes care of upgrading the legacy elasticsearch data and preparing the cluster for the upgrade of the elasticsearch packages. Due to some inconsistencies in the legacy elasticsearch mappings it is necessary to reindex all elasticsearch data into indices with the updated 2.x compatible mappings. Included with the upgrade tasks is a python wrapper to monitor and control the reindexing process.  It is recomended to reindex all indices prior to the current day before beginning the upgrade.  Please check the upgrade documentation for more information on how to reindex the existing elasticsearch indices.

.. releasenotes/notes/handle-merging-new-secrets-0e1fd06d86f0abbd.yaml @ 01d08b82dd972554e352036af83dd7f9f18c170d

- Any new secret variables that may be introduced in later releases are now handled by the ``update-secrets.sh`` script. ``test-upgrade.sh`` and ``deploy.sh`` have been updated to use ``update-secrets.sh`` to handle any new variables that may be introduced in newer releases. If the deployer is not using these scripts for upgrades, then ``update-secrets.sh`` needs to be invoked manually. Please see official RPCO upgrade docs for usage.


Bug Fixes
---------

.. releasenotes/notes/add-magnum-f5-93cc4c09fdb60d23.yaml @ 4356902a55deeb2a2ac5067f3f0fa812396c5877

- Magnum endpoint now uses a Magnum-specific monitor

.. releasenotes/notes/fix-rpc-maas-tool-check-validation-a5190a72be5830f6.yaml @ 2f3a0a76689122da4741b284200d3c594900e408

- `rpc-maas-tool.py` is modified so that validating the status of checks
  correctly reports when there are failures. This tool is used by the
  playbook `verify-maas.yml`.

.. releasenotes/notes/handle-merging-new-secrets-0e1fd06d86f0abbd.yaml @ 01d08b82dd972554e352036af83dd7f9f18c170d

- Secret variables defined in rpco specific variable files are now properly merged with any new secret variables that might be introduced in a subsequent release.

.. releasenotes/notes/remove-logstash-from-filebeat-dd09be25d7f1c37f.yaml @ ad411bb46b3508cf2a2d38ab337a4e7fcb025f73

- Having logstash process it's own log can lead to a "feedback" loop wherein an error that is logged into the logstash log will be re-logged ad-infinitum, eventually filling the disk and crashing logstash. This removes the filebeat shipping of the logstash.log file to logstash.

.. releasenotes/notes/setcheckfirewallvariabletofalse-de49a72bbad0e7db.yaml @ f03f90970d5fb514b9837c1546fc340d9bda7549

- The ``check_firewall`` variable is now set to false because the
  ``check firewall`` tasks are incompatible with Ansible 2.1.5. This
  fix allows for our ceph playbooks to run successfully.


Other Notes
-----------

.. releasenotes/notes/multi-layered-group-vars-cb60fcf454ca3bbe.yaml @ 35a375c7ff8104578ee93bfd6b1d9d3b612b2e62

- RPC-O previously relied on user-space configuration files
  to set variables used in playbooks across both
  OpenStack-Ansible and RPC-O playbooks. These user-space
  configuration files provided global overrides only and
  could not be scoped to specific host groups. These defaults
  have now been set in group_vars in the code tree, reducing
  the need to overwrite user-space files, making them easier
  to scope to host groups, and reducing their precedence level
  to improve future development flexibility.