Merge "Release notes cleanup for the next release"

This commit is contained in:
Zuul 2019-09-11 13:58:06 +00:00 committed by Gerrit Code Review
commit b9a2ac8914
5 changed files with 17 additions and 18 deletions

View File

@ -1,6 +1,5 @@
--- ---
fixes: fixes:
- | - |
Fixes issue that 0 physical memory calculated for aarch64. Since output Fixes detection of physical memory amount on AArch64 that was caused by
for aarch64 `lshw -quiet -json` is a bit different from x86_64. This fix different output of the ``lshw`` utility.
is compatible with both x86_64 and arm64.

View File

@ -1,5 +1,5 @@
--- ---
fixes: fixes:
- | - |
Fixes an issue where md devices disk holders could not be listed Fixes an issue where md devices disk holders could not be listed
correctly if they were nvme drives. correctly if they were NVMe drives.

View File

@ -1,3 +1,3 @@
--- ---
features: features:
- Adds software raid creation support on nvme drives. - Adds support for creating software RAID on NVMe drives.

View File

@ -1,4 +1,4 @@
--- ---
features: features:
- Adds the ability to specify the partition table type when creating raid. - Adds the ability to specify the partition table type when creating RAID.
When not specified, the type is set to msdos. When not specified, the type is set to ``msdos`` (MBR).

View File

@ -1,11 +1,11 @@
--- ---
fixes: fixes:
- Fixes an issue with the psize conversion when creating software raid. From - Fixes size conversion when creating software RAID with ``size_gb``
the documentation, provided. From the `RAID documentation
https://docs.openstack.org/ironic/latest/admin/raid.html#target-raid-configuration, <https://docs.openstack.org/ironic/latest/admin/raid.html#target-raid-configuration>`_
size_gb unit is GiB but parted default unit is MB. ``size_gb`` unit is GiB but parted defaults to MB.
- Fixes a RAID creation issue when there are several logical drives, with - Fixes creating software RAID when several logical drives have a size
more than one having its size specified (i.e not 'MAX'). specified (i.e not 'MAX'). See `story 2006352
https://storyboard.openstack.org/#!/story/2006352 <https://storyboard.openstack.org/#!/story/2006352>`_.
- Fixes a RAID creation issue when a logical drive with size 'MAX' is not - Fixes creating software RAID when a logical drive with size 'MAX' is not
last in the list of logical drives. the last in the list of logical drives.