Tidy up Wallaby renos
Change-Id: Idad2d4f8bf5f54c57d2c5fccbf6eff7d54f040dd
This commit is contained in:
parent
0b5089ed5a
commit
63405a4728
@ -1,4 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- Add new option prometheus_openstack_exporter_timeout to override default
|
||||
scrape_timeout for openstack exporter job.
|
||||
- |
|
||||
Add new option ``prometheus_openstack_exporter_timeout`` to override
|
||||
default ``scrape_timeout`` for openstack exporter job.
|
||||
|
@ -1,17 +1,18 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Adds support for elasticsearch storage backend with cloudkitty:
|
||||
That feature let you store cloudkitty rating documents directly within
|
||||
your elasticsearch cluster.
|
||||
Adds support for Elasticsearch storage backend with Cloudkitty:
|
||||
This feature allows for storage of Cloudkitty rating documents directly
|
||||
within an Elasticsearch cluster.
|
||||
|
||||
If you already have an elasticsearch cluster running for logging it create
|
||||
a new cloudkitty specific index. That let you use kibana, grafana or any
|
||||
other interface to browse your rating data and create appropriate
|
||||
dashboard or build an appropriate billing service over it.
|
||||
If you already have an Elasticsearch cluster running for logging a new
|
||||
cloudkitty specific index will be used. This allows you to use Kibana,
|
||||
Grafana or another interface to browse your rating data and create
|
||||
an appropriate dashboard or build an appropriate billing service over it.
|
||||
|
||||
Adds support for prometheus as a fetcher/collector for cloudkitty:
|
||||
That feature let you use prometheus metrics as your source of rating.
|
||||
Using prometheus let you rate pretty much any openstack object directly
|
||||
from the kolla provided exporters (Openstack_exporter) or your own
|
||||
customs exporters.
|
||||
- |
|
||||
Adds support for Prometheus as a fetcher/collector for Cloudkitty:
|
||||
This feature allows for use of Prometheus metrics as your source of rating.
|
||||
Using Prometheus allows for rating almost any OpenStack object directly
|
||||
from the Kolla provided exporters (openstack_exporter) or your own
|
||||
custom exporters.
|
||||
|
@ -1,6 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Adds support to import custom ``grafana`` dashboards. Dashboard's JSON
|
||||
files should be placed into "{{ node_custom_config }}/grafana/dashboards/"
|
||||
folder.
|
||||
Adds support to import custom Grafana dashboards. The dashboard JSON files
|
||||
should be placed into ``{{ node_custom_config }}/grafana/dashboards/``.
|
||||
|
@ -3,7 +3,7 @@ upgrade:
|
||||
- |
|
||||
The Monasca Log Metrics service has been deprecated and is now
|
||||
disabled by default. If you wish to enable it, you can set
|
||||
`monasca_enable_log_metrics_service` to `True` in `globals.yml`.
|
||||
``monasca_enable_log_metrics_service`` to ``True`` in ``globals.yml``.
|
||||
deprecations:
|
||||
- |
|
||||
The Monasca Log Metrics service has been deprecated and will be
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add `kolla_externally_managed_cert` option to disable copy of certificates
|
||||
from the operator host to kolla-ansible managed hosts.
|
||||
Add ``kolla_externally_managed_cert`` option to disable copy of
|
||||
certificates from the operator host to Kolla Ansible managed hosts.
|
||||
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for aodh services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for barbican services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for blazar services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for cinder services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for cloudkitty services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for cyborg services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for designate services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for elasticsearch services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for gnocchi services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for haproxy services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for ironic services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for kibana services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for magnum services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for manila services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for octavia services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for redis services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for sahara services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for senlin services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for skydive services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for tacker services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for trove services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for vitrage services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implements container healthchecks for watcher services.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -0,0 +1,10 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implemented container healthchecks for following services: ``aodh``,
|
||||
``barbican``, ``blazar``, ``cinder``, ``cloudkitty``, ``cyborg``,
|
||||
``designate``, ``elasticsearch``, ``gnocchi``, ``haproxy``, ``ironic``,
|
||||
``kibana``, ``magnum``, ``manila``, ``octavia``, ``redis``, ``sahara``,
|
||||
``senlin``, ``skydive``, ``tacker``, ``trove``, ``vitrage``, ``watcher``.
|
||||
See `blueprint
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check>`__
|
@ -1,8 +1,8 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The Mariadb role now allows the creation of multiple clusters.
|
||||
This provides a benefit to operators as they are able to install
|
||||
and maintain several clusters at once using kolla-ansible.
|
||||
This is useful when deploying db clusters for cells or db clusters
|
||||
for services that have large demands on the database.
|
||||
The Mariadb role now allows the creation of multiple clusters. This
|
||||
provides a benefit to operators as they are able to install and maintain
|
||||
several clusters at once using kolla-ansible. This is useful when
|
||||
deploying database clusters for cells or database clusters for services
|
||||
that have large demands on the database.
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Switch octavia-api to wsgi running under apache.
|
||||
Switch ``octavia-api`` to WSGI running under Apache.
|
||||
- |
|
||||
Added configuration options to enable backend TLS encryption from HAProxy
|
||||
to the Octavia service. When used in conjunction with enabling TLS for
|
||||
|
@ -1,6 +1,8 @@
|
||||
---
|
||||
deprecations:
|
||||
upgrade:
|
||||
- |
|
||||
cinder v2 api is not supported in wallaby, and we remove it
|
||||
from kolla project. See `API v2 support removed in Wallaby
|
||||
Removes support for Cinder v2 API. This API was planned for removal from
|
||||
Cinder in the Wallaby release but has been postposed until Xena. Cinder v2
|
||||
API endpoints are removed from the Keystone endpoint catalogue on upgrade.
|
||||
`API v2 support removed in Wallaby
|
||||
<http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018697.html>`__
|
||||
|
@ -2,6 +2,6 @@
|
||||
upgrade:
|
||||
- |
|
||||
Customizing Neutron Linux bridge and Open vSwitch Agents config via
|
||||
ml2_conf.ini is removed. The config has been split out for these
|
||||
agents into linuxbridge_agent.ini and openvswitch_agent.ini respectively.
|
||||
The old behaviour was deprecated in Ussuri for removal in Victoria.
|
||||
``ml2_conf.ini`` is removed. The config has been split out for these
|
||||
agents into ``linuxbridge_agent.ini`` and ``openvswitch_agent.ini``
|
||||
respectively. The old behaviour was deprecated in Ussuri.
|
||||
|
Loading…
Reference in New Issue
Block a user