New features¶
Component |
Support scope |
Feature |
---|---|---|
OpenStack |
Full |
|
Full |
||
TechPreview |
||
n/a |
||
Full |
||
Tungsten Fabric |
Full |
|
Bare metal |
TechPreview |
MariaDB minor version update¶
Updated the minor version of MariaDB from 10.4 to 10.6. The update applies automatically during the MOSK cluster update procedure.
End-user IP addresses captured in cloud’s logs¶
Exposed the IP addresses of the cloud users that consume API of a cloud to all user-facing cloud services, such as OpenStack, Ceph, and others. Now, the IP addresses get recoded in the corresponding logs allowing for easy troubleshooting and security auditing of the cloud.
CPU isolation using cpusets¶
TechPreview
Implemented the capability to configure CPU isolation using the cpusets
mechanism in Linux kernel. Configuring CPU isolation using the isolcpus
configuration parameter for Linux kernel is considered deprecated.
OpenStack security checklist compliance¶
Validated MOSK against the upstream OpenStack Security Checklist. The default configuration of MOSK services that include Identity, Dashboard, Compute, Block Storage, and Networking services is compliant with the security recommendations from the OpenStack community.
Encryption of all the internal communications for MOSK services will become available in one of the nearest product releases.
LoadBalancer configuration for PowerDNS¶
Implemented the capability to configure the LoadBalancer type for PowerDNS
through the spec:features:designate
definition in the
OpenStackDeployment
CR, for example, to expose the TCP protocol instead of
the default UDP, or both.
Access to external DNS for Tungsten Fabric¶
Added the tf-control-dns-external
service to the list of the Tungsten
Fabric configuration options. The service is created by default to expose TF
control dns
. You can disable creation of this service using the
enableDNSExternal
parameter in the TFOperator
CR.
MOSK on local mdadm RAID devices of level 10¶
TechPreview
Implemented the initial Technology Preview support for MOSK
deployment on local software-based mdadm Redundant Array of Independent Disks
(RAID) devices of level 10 (raid10
) to withstand failure of one device
at a time.
The raid10
RAID type requires at least four and in total an even number
of storage devices available on your servers.
To create and configure RAID, use the softRaidDevices
field in
BaremetalHostProfile
.
Also, added the capability to create LVM volume groups on top of mdadm-based RAID devices.