openstack
/
charm-guide
Code Issues Proposed changes

Finalise release notes for 2023.2 

Change-Id: Id69f7d6ad1c416ee9730878ba70191408d82ea18
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
This commit is contained in:
Peter Matulis 2023-11-29 16:59:20 -05:00
parent fc1682f4ef
commit 54c11d8ab3
No known key found for this signature in database
2 changed files with 29 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/project/release-schedule.rst
View File

@ -25,13 +25,13 @@ latter dates are estimated and subject to revision.
- Release timeline - Release timeline
* - 2023.2 - Bobcat * - 2023.2 - Bobcat
- under development - current stable
- Fri, Sep 29, 2023 (estimated) - Fri, Sep 29, 2023
- Fri, Oct 27, 2023 (estimated) - Thu, Nov 30, 2023
- -- - --
* - 2023.1 - Antelope * - 2023.1 - Antelope
- current stable - --
- Fri, Mar 31, 2023 - Fri, Mar 31, 2023
- Fri, Jun 2, 2023 - Fri, Jun 2, 2023
- -- - --

45
doc/source/release-notes/2023.2-bobcat.rst
View File

@ -1,10 +1,10 @@
=========================================== ===============
2023.2 (Bobcat) (under development) 2023.2 (Bobcat)
=========================================== ===============
The 2023.2 (Bobcat) OpenStack Charms release includes updates for the charms The 2023.2 (Bobcat) OpenStack Charms release includes updates for the charms
described on the :doc:`../project/openstack-charms` page. As of this release, described on the :doc:`../project/openstack-charms` page. As of this release,
the project consists of 62 stable charms. the project consists of 65 stable charms.
.. note:: .. note::
@ -84,8 +84,8 @@ For example, to set the role cache expiration time to 10 seconds do:
juju config keystone role-cache-expiration=10 juju config keystone role-cache-expiration=10
Designate-bind allow transfer config designate-bind charm: new option for ``zone transfer`` feature
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The designate-bind charm now supports configuring the BIND9 ``allow-transfer`` The designate-bind charm now supports configuring the BIND9 ``allow-transfer``
option. If not set, the corresponding feature is disabled. option. If not set, the corresponding feature is disabled.
@ -132,20 +132,25 @@ These properties will only be added to images that go through the
magnum charm: new option to expose cluster_user_trust magnum charm: new option to expose cluster_user_trust
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This configuration option controls whether to assign a trust to the cluster user The magnum charm has a new configuration option: ``cluster-user-trust``.
or not. This option needs to be set to True for clusters with
volume_driver=cinder, cloud_provider_enabled=true or registry_enabled=true in This controls whether to assign a trust to the cluster user or not. This option
the underlying cluster template to work. This is a potential security risk since needs to be set to True for clusters with volume_driver=cinder,
the trust gives instances OpenStack API access to the cluster's project. cloud_provider_enabled=true or registry_enabled=true in the underlying cluster
template to work. This is a potential security risk since the trust gives
instances OpenStack API access to the cluster's project.
For more details see bug `LP #1996237`_. For more details see bug `LP #1996237`_.
nova-cloud-controller charm: new relation to openstack-dashboard nova-cloud-controller charm: new relation to openstack-dashboard
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The nova-cloud-controller charm has a new relation:
``juju integrate nova-cloud-controller:dashboard openstack-dashboard:dashboard`` ``juju integrate nova-cloud-controller:dashboard openstack-dashboard:dashboard``
allows nova-cloud-controller to know that possible hosts and IP addresses that
the cloud users use to access the OpenStack Dashboard, the nova-cloud-controller This allows nova-cloud-controller to know what hosts and IP addresses cloud
users may use to access the OpenStack Dashboard. The nova-cloud-controller
units use this information to configure the nova-serialproxy daemon and `allow units use this information to configure the nova-serialproxy daemon and `allow
requests`_ coming from the web browsers visiting the dashboard. requests`_ coming from the web browsers visiting the dashboard.
@ -239,7 +244,7 @@ instances that have been evacuated/migrated.
This is present in 2023.2, and has been backported to the ussuri release. This is present in 2023.2, and has been backported to the ussuri release.
For more details see `LP #2019141`_. For more details see bug `LP #2019141`_.
Removed features Removed features
---------------- ----------------
@ -275,11 +280,11 @@ containers may lose their IP addresses and network connectivity on reboot.
For more details see `Upgrade issues`_. For more details see `Upgrade issues`_.
Designate charm default values not used designate charm: some settings not honoured
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Due to `LP #2042944`_ the following designate charm config options aren't The following designate charm configuration options aren't applied when
applied when creating zone records: creating zone records:
* ``default-soa-expire`` * ``default-soa-expire``
* ``default-soa-minimum`` * ``default-soa-minimum``
@ -287,8 +292,8 @@ applied when creating zone records:
* ``default-soa-retry`` * ``default-soa-retry``
* ``default-ttl`` * ``default-ttl``
The ``openstack zone create ...`` and designate API for zone creation allow As a workaround, the ``openstack zone create`` command and the designate API
these parameters to be set directly as a workaround. for zone creation allow these parameters to be set directly.
For more details see bug `LP #2042944`_. For more details see bug `LP #2042944`_.