Merge "Tidy up release notes for Stein release"
This commit is contained in:
commit
cb845f7585
@ -1,4 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add ceilometer_ipmi into ceilometer role.
|
||||
Adds support for deploying a ``ceilometer_ipmi`` container for collecting
|
||||
Ceilometer metrics on IPMI.
|
||||
|
@ -1,3 +1,3 @@
|
||||
---
|
||||
features:
|
||||
- Add support in Cinder and Nova for Quobyte volumes
|
||||
- Adds support in Cinder and Nova for Quobyte volumes
|
||||
|
@ -1,3 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- Add cyborg ansible role
|
||||
- Adds support for deploying the OpenStack Cyborg service. Cyborg is a
|
||||
service for managing hardware accelerators.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Two new parameters (migration_interface, migration_interface_address) to make
|
||||
the use of a dedicated migration network possible.
|
||||
Adds support for a dedicated migration network. This is configured via the
|
||||
variables ``migration_interface`` and ``migration_interface_address``.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add support for deploying the Monasca fork of Grafana, which includes
|
||||
Adds support for deploying the Monasca fork of Grafana, which includes
|
||||
Keystone integration.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add the Monasca Log Metrics service. This service is responsible for
|
||||
generating metrics from log files.
|
||||
Adds support for deploying the Monasca Log Metrics service. This service is
|
||||
responsible for generating metrics from log files.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add support for deploying the Monasca Persister process. The
|
||||
Adds support for deploying the Monasca Persister process. The
|
||||
Persister is responsible for reading metrics, alarms and events
|
||||
from Kafka and storing them in a variety of backends.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add support for deploying the Monasca thresh service, an Apache Storm
|
||||
Adds support for deploying the Monasca thresh service, an Apache Storm
|
||||
topology for alerting.
|
||||
|
@ -1,3 +1,3 @@
|
||||
---
|
||||
features:
|
||||
- Add neutron-metering-agent into kolla-ansible
|
||||
- Adds support for deploying the Neutron metering agent.
|
||||
|
@ -1,3 +1,3 @@
|
||||
---
|
||||
features:
|
||||
- Add support Octavia custom policy.
|
||||
- Adds support for configuring custom policies in Octavia.
|
||||
|
@ -1,3 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- Add support specific Octavia network interface.
|
||||
- Adds support for using a separate network for Octavia. This is configured
|
||||
via ``octavia_network_interface`` and
|
||||
``octavia_network_interface_address``.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Added an option, haproxy_nova_serialconsole_proxy_tunnel_timeout,
|
||||
to configure the nova_serialconsole_proxy tunnel timeout. This default
|
||||
Adds an option, ``haproxy_nova_serialconsole_proxy_tunnel_timeout``,
|
||||
to configure the ``nova_serialconsole_proxy`` tunnel timeout. The default
|
||||
is to keep the websocket connection alive for 10 minutes.
|
||||
|
@ -1,4 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Configure Prometheus as Vitrage datasource automatically.
|
||||
Configures Prometheus as a Vitrage datasource automatically.
|
||||
|
@ -1,5 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Deploys and configures the prometheus-elasticsearch-exporter (https://github.com/justwatchcom/elasticsearch_exporter/)
|
||||
as part of the prometheus monitoring exporters stack.
|
||||
Adds support for deploying the `Prometheus Elasticsearch exporter
|
||||
<https://github.com/justwatchcom/elasticsearch_exporter/>`__ as part of the
|
||||
prometheus monitoring exporters stack.
|
||||
|
@ -1,5 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Deploys and configures the prometheus-openstack-exporter (https://github.com/Linaro/openstack-exporter/)
|
||||
as part of the prometheus monitoring exporters stack.
|
||||
Adds support for deploying the `Prometheus OpenStack exporter
|
||||
<https://github.com/Linaro/openstack-exporter/>`__ as part of the
|
||||
prometheus monitoring exporters stack.
|
||||
|
@ -1,4 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- Add the Monasca Agent which provides host and application
|
||||
specific monitoring data collection and forwarding.
|
||||
- Adds support for deploying the Monasca Agent, which provides host and
|
||||
application specific monitoring data collection and forwarding.
|
||||
|
@ -1,7 +1,8 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Bump up the max_files to 32768 and max_processes to 131072.
|
||||
when nova used ceph as backend, the default limit 1024 is not enough.
|
||||
each connection from rbd image to osd needs 1 fd and 2 threads. if we
|
||||
have 200 osds, we need 200 fds and 400 threads for 1 image.
|
||||
Adds support for configuring the maximum files and processes limits in the
|
||||
``nova_libvirt`` container, via the ``qemu_max_files`` and
|
||||
``qemu_max_processes`` variables. The default values for these are 32768
|
||||
and 131072 respectively. This is useful when Nova uses Ceph as a backend,
|
||||
since the default limit of 1024 is often not enough.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add ulimit support for kolla_docker which provides ability
|
||||
of modify docker ulimits。
|
||||
Adds support for configuring ulimit in containers, extending the dimension
|
||||
support added in Rocky release.
|
||||
|
@ -1,5 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add a configuration option `enable_keepalived` to allow disabling the
|
||||
service. This is useful when using an external LB in front of HAProxy.
|
||||
Adds a configuration option ``enable_keepalived`` to allow disabling the
|
||||
``keepalived`` service. This is useful when using an external load balancer
|
||||
in front of HAProxy.
|
||||
|
@ -1,12 +1,13 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
You can customise vendor info that is used through out Nova via the
|
||||
'release' file. To do this place a file called 'release' in one of the
|
||||
following locations:
|
||||
/etc/kolla/config/nova/release
|
||||
/etc/kolla/config/nova_compute/release
|
||||
/etc/kolla/config/nova_compute/{{ inventory_hostname }}/release
|
||||
Adds support for configuring vendor info in Nova via the ``release`` file.
|
||||
To do this place a file called ``release`` in one of the following
|
||||
locations:
|
||||
|
||||
* /etc/kolla/config/nova/release
|
||||
* /etc/kolla/config/nova_compute/release
|
||||
* /etc/kolla/config/nova_compute/{{ inventory_hostname }}/release
|
||||
|
||||
An example of the file can be seen at
|
||||
https://github.com/openstack/nova/blob/master/etc/nova/release.sample
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add support to configure glance-cache, enabled with
|
||||
``enable_glance_image_cache`` and configure cache size
|
||||
with ``glance_cache_max_size``.
|
||||
Adds support for configuring ``glance-cache``, enabled with
|
||||
``enable_glance_image_cache``. The cache size is configured via
|
||||
``glance_cache_max_size``.
|
||||
|
@ -1,9 +1,9 @@
|
||||
---
|
||||
upgrade:
|
||||
- |
|
||||
Added swift as gnocchi storage option.
|
||||
Here is the list of storage options for gnocchi-
|
||||
a) Uses swift if swift is enabled.
|
||||
b) Uses ceph if ceph is enabled.
|
||||
c) Defaults to file if swift and ceph are enabled.
|
||||
User has to explicitly set to swift or ceph if both enabled.
|
||||
Adds swift as a gnocchi storage option.
|
||||
Here is the list of storage options for gnocchi\:
|
||||
a) Use swift if swift is enabled.
|
||||
b) Use ceph if ceph is enabled.
|
||||
c) Default to file if swift and ceph are enabled.
|
||||
User has to explicitly set to swift or ceph if both are enabled.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implement Neutron rolling upgrade logic, apply for: neutron,
|
||||
vpnaas and fwaas because only these projects have supported for
|
||||
rolling upgrade database migration.
|
||||
Implements Neutron rolling upgrade logic, applied for Neutron server,
|
||||
VPNaaS and FWaaS because only these projects have support for rolling
|
||||
upgrade database migration.
|
||||
|
@ -1,4 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implement Nova rolling upgrade logic
|
||||
Implements Nova rolling upgrade logic.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Implement Swift rolling upgrade logic, enabled by default at
|
||||
swift_enable_rolling_upgrade: "yes" in etc/kolla/globals.yml file.
|
||||
Implements Swift rolling upgrade logic, enabled via
|
||||
``swift_enable_rolling_upgrade``, which is ``true`` by default.
|
||||
|
@ -1,3 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- Adds ability to provide a custom kibana config.
|
||||
- Adds support for providing custom kibana configuration via
|
||||
``/etc/kolla/config/kibana/kibana.yml``.
|
||||
|
@ -2,7 +2,6 @@
|
||||
features:
|
||||
- Docker logs are no longer allowed to grow unbounded and have
|
||||
been limited to a fixed size per container. Two new variables
|
||||
have been added, `docker_log_max_file` and `docker_log_max_size`
|
||||
which default to 5 and 50MB respectively. This means that for
|
||||
each container, there should be no more than 250MB of Docker
|
||||
logs.
|
||||
have been added, ``docker_log_max_file`` and ``docker_log_max_size`` which
|
||||
default to 5 and 50MB respectively. This means that for each container,
|
||||
there should be no more than 250MB of Docker logs.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
other:
|
||||
features:
|
||||
- |
|
||||
Link kolla_logs docker volume to /var/log/kolla.
|
||||
Shorter log path will help to debug from log.
|
||||
The volume path is compatible with docker-engine and docker-ce.
|
||||
Adds a symbolic link from the ``kolla_logs`` docker volume to
|
||||
``/var/log/kolla``, making it easier to find log files. The volume path is
|
||||
compatible with docker-engine and docker-ce.
|
||||
|
@ -1,7 +1,8 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Supports taking a backup of all MariaDB-hosted databases using Percona XtraBackup.
|
||||
Adds support for taking a backup of all MariaDB-hosted databases using
|
||||
Percona XtraBackup.
|
||||
security:
|
||||
- |
|
||||
When the MariaDB backup option is enabled, it will create a new database
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- Adds support for loading kernel modules required by containers. This is
|
||||
required since kolla images are removing support for loading kernel modules
|
||||
from within the container.
|
||||
required since kolla images removed support for loading kernel modules
|
||||
from within the container in the Stein release.
|
||||
|
@ -1,5 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add onos support, Networking-onos is Neutron's sub-project to provide
|
||||
connectivity between Neutron/Neutron's sub-project's and ONOS.
|
||||
Add support for configuring Neutron to use an ONOS SDN controller via
|
||||
the ``networking-onos`` project. Networking-onos is Neutron's sub-project
|
||||
to provide connectivity between Neutron and ONOS.
|
||||
|
@ -1,7 +1,8 @@
|
||||
---
|
||||
upgrade:
|
||||
- |
|
||||
Previously deprecated compute groups 'inner-compute' and 'external-compute'
|
||||
have now been removed in favor of the more simple 'compute' group. Please
|
||||
be sure to update your inventory. Set 'neutron_compute_dvr_mode' on nodes
|
||||
with which you wish to customise the value for neutron's 'agent_mode'.
|
||||
Previously deprecated compute groups ``inner-compute`` and
|
||||
``external-compute`` have now been removed in favor of the more simple
|
||||
``compute`` group. Please be sure to update your inventory. Set
|
||||
``neutron_compute_dvr_mode`` on nodes with which you wish to customise the
|
||||
value for neutron's ``agent_mode``.
|
||||
|
@ -2,10 +2,10 @@
|
||||
features:
|
||||
- |
|
||||
HAProxy configuration is now split per service, which makes creating and
|
||||
updating service configs much simpler.
|
||||
updating service configurations much simpler.
|
||||
upgrade:
|
||||
- |
|
||||
All haproxy related variables have been moved from the ``haproxy`` role to
|
||||
All HAProxy-related variables have been moved from the ``haproxy`` role to
|
||||
the ``haproxy-common`` role, with the exception of the following which were
|
||||
also split and renamed after the move\:
|
||||
|
||||
|
6
releasenotes/notes/stein-prelude-0fd9e090eb54e566.yaml
Normal file
6
releasenotes/notes/stein-prelude-0fd9e090eb54e566.yaml
Normal file
@ -0,0 +1,6 @@
|
||||
---
|
||||
prelude: |
|
||||
The Kolla Ansible ``8.0.0`` release is the first release in the Stein cycle.
|
||||
Highlights include full support for the OpenStack Monasca project, support
|
||||
for the Placement service which has been extracted from Nova, and support
|
||||
for performing full or incremental backups of the MariaDB database.
|
@ -1,11 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add support to stop a service with ``kolla-ansible stop`` command.
|
||||
This feature will allow to stop specific services with ``--tags`` and
|
||||
``--limit`` to a host.
|
||||
upgrade:
|
||||
- |
|
||||
New ``kolla-ansible stop`` command requires the usage of
|
||||
``--yes-i-really-really-mean-it`` to avoid accidentally
|
||||
stopping services.
|
||||
Adds support for stopping a service with the ``kolla-ansible stop``
|
||||
command. This feature allows specific services to be stopped with
|
||||
``--tags`` and ``--limit`` to limit the changes to a subset of hosts.
|
||||
|
@ -1,6 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Support ansible check and diff module for generate configurations. You could
|
||||
use ``EXTRA_OPTS='--check --diff' kolla-ansible genconfig`` to check what
|
||||
the configuration file will be like in dry-run mode.
|
||||
Adds support for Ansible check and diff mode when generating configuration.
|
||||
It is possible to use ``EXTRA_OPTS='--check --diff' kolla-ansible
|
||||
genconfig`` to check what the configuration file will be like in dry-run
|
||||
mode.
|
||||
|
@ -7,13 +7,14 @@ features:
|
||||
In a deployment where both Ceph and Swift have been deployed,
|
||||
this changes adds functionalality to support optional seperation
|
||||
of storage network traffic. This adds two new network interfaces
|
||||
'swift_storage_interface' and 'swift_replication_interface' which maintain
|
||||
backwards compatibility.
|
||||
``swift_storage_interface`` and ``swift_replication_interface`` which
|
||||
maintain backwards compatibility.
|
||||
|
||||
The Swift access network interface is configured via 'swift_storage_interface',
|
||||
which defaults to 'storage_interface'. The Swift replication network
|
||||
interface is configured via 'swift_replication_interface', which
|
||||
defaults to 'swift_storage_interface'.
|
||||
The Swift access network interface is configured via
|
||||
``swift_storage_interface``, which defaults to ``storage_interface``. The
|
||||
Swift replication network interface is configured via
|
||||
``swift_replication_interface``, which defaults to
|
||||
``swift_storage_interface``.
|
||||
|
||||
If a separate replication network is used, Kolla Ansible now deploys separate
|
||||
replication servers for the accounts, containers and objects, that listen on
|
||||
|
@ -1,4 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Add configuration to enable/disable custom horizon policy files per-service even if the service is not being deployed by kolla-ansible.
|
||||
Adds configuration variables to enable/disable custom horizon policy files
|
||||
per-service even if the service is not being deployed by kolla-ansible.
|
||||
|
Loading…
Reference in New Issue
Block a user