Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Ceph default configuration options¶
Warning
This procedure is valid for MOSK clusters that use the deprecated
KaaSCephCluster
custom resource (CR) instead of the MiraCeph
CR that is
available since MOSK 25.2 as a new Ceph configuration entrypoint. For the
equivalent procedure with the MiraCeph
CR, refer to the following section:
Ceph Controller provides the capability to specify configuration options for
the Ceph cluster through the spec.cephClusterSpec.rookConfig
key-value
parameter of the KaaSCephCluster
resource as if they were set in a usual
ceph.conf
file. For details, see Ceph advanced configuration.
However, if rookConfig
is empty, Ceph Controller still specifies the
following default configuration options for each Ceph cluster:
Required network parameters that you can change through the
spec.cephClusterSpec.network
section:cluster network = <spec.cephClusterSpec.network.clusterNet> public network = <spec.cephClusterSpec.network.publicNet>
General default configuration options that you can override using the
rookConfig
parameter:mon target pg per osd = 200 mon max pg per osd = 600 # Workaround configuration option to avoid the # https://github.com/rook/rook/issues/7573 issue # when updating to Rook 1.6.x versions: rgw_data_log_backing = omap
If rookConfig
is empty but the spec.cephClsuterSpec.objectStore.rgw
section is defined, Ceph Controller specifies the following OpenStack-related
default configuration options for each Ceph cluster:
Ceph Object Gateway options, which you can override using the
rookConfig
parameter:rgw swift account in url = true rgw keystone accepted roles = '_member_, Member, member, swiftoperator' rgw keystone accepted admin roles = admin rgw keystone implicit tenants = true rgw swift versioning enabled = true rgw enforce swift acls = true rgw_max_attr_name_len = 64 rgw_max_attrs_num_in_req = 32 rgw_max_attr_size = 1024 rgw_bucket_quota_ttl = 0 rgw_user_quota_bucket_sync_interval = 0 rgw_user_quota_sync_interval = 0 rgw s3 auth use keystone = true
Additional parameters for the Keystone integration:
Warning
All values with the
keystone
prefix are programmatically specified for each MOSK deployment. Do not modify these parameters manually.rgw keystone api version = 3 rgw keystone url = <keystoneAuthURL> rgw keystone admin user = <keystoneUser> rgw keystone admin password = <keystonePassword> rgw keystone admin domain = <keystoneProjectDomain> rgw keystone admin project = <keystoneProjectName>
See also