Compute
Review the Compute updates introduced in RHOSO beta before you deploy the release.
New features Copy linkLink copied!
Review the new features introduced in RHOSO beta before you deploy the release.
- You can schedule archival and purge of deleted rows from Compute service (nova) cells
-
The nova-operator now schedules a periodic job for each Compute service (nova) cell to archive and purge the deleted rows from the cell database. The frequency of the job and the age of the database rows to archive and purge can be fine tuned in the
{{OpenStackControlPlane.spec.nova.template.cellTemplates[].dbPurge}}structure for each cell in the cellTemplates.
Deprecated functionality Copy linkLink copied!
Review the deprecated functionality introduced in RHOSO beta before you deploy the release.
Deprecated functionality will likely not be supported in future major releases of this product and is not recommended for new deployments.
- i440fx PC machine type no longer tested or supported
-
In RHOSP 17, the i440fx PC machine type, pc-i440fx, was deprecated and Q35 became the default machine type for x86_64.
In RHOSP 18, the i440fx PC machine type is no longer tested or supported.
The i440fx PC machine type is still available for use under a support exception for legacy applications that cannot function with the Q35 machine type. If you have such a workload, contact Red Hat support to request a support exception.
With the removal of support for the i440fx PC machine type from RHOSP, you cannot use pc-i440fx to certify VNFs or third-party integrations. You must use the Q35 machine type.
Jira:OSPRH-7373
Known issues Copy linkLink copied!
Review the known issues introduced in RHOSO beta before you deploy the release.
- No network block device (NBD) live migration with TLS enabled
-
In RHOSO 18.0 Beta, a bug prevents you from using a network block device (NBD) to live migrate storage between Compute nodes with TLS enabled. See https://issues.redhat.com/browse/OSPRH-6931.
This issue only affects storage migration when TLS is enabled. You can live migrate storage with TLS not enabled.
- Do not mix NUMA and non-NUMA instances on same Compute host
-
Instances without a NUMA topology should not coexist with NUMA instances on the same host.
- Cannot delete instance when
cpu_power_managmentis set totrue -
When an instance is first started and the host core state is changed there is a short time period where it cannot be updated again. During this period instance deletion can fail. if this happens a second delete attempt should succeed after a short delay of a few seconds.
Jira:OSPRH-7103