Omnia Configuration Tables

This section contains the configuration tables referenced throughout the Omnia documentation.

BuildStreaM Configuration

build_stream_config.yml

Parameter	Mandatory/Optional	Description
enable_build_stream	Mandatory	Enable or disable BuildStreaM pipeline. Accepted values: boolean values (true or false) or (yes or no) Default value: false
build_stream_host_ip	Mandatory	Optional: Build Stream API server host IP Accepted values: The public IP address of OIM or admin IP of OIM. The public IP address should be reachable from the GitLab server. Default value: The admin IP of OIM.
build_stream_port	Mandatory	BuildStreaM API server port. Accepted values: valid port number (1-65535) which is free Default value: 8010
aarch64_inventory_host_ip	Conditional Mandatory	Specify the aarch64 inventory host IP address for aarch64 builds. Accepted values: The admin IP of aarch64 host where OS is installed. Default value: None. If the inventory host IP address is not specified, the build images for aarch64 are not generated.

High Availability Configuration

high_availability_config.yml

Parameter	Details
cluster_name	Type: String Captures the name of the service cluster on which HA will be set up. Default value: service_cluster
enable_k8s_ha	Type: Boolean Possible values: true Default value: true Indicates whether to enable HA for the Kubernetes (K8s) service node or not. Set to true to enable.
virtual_ip_address	Type: String This is a mandatory and user-configurable parameter. Captures the virtual IP address for the K8s service node HA setup. Ensure that the virtual_ip_address does not belong to the dynamic_range or static_range mentioned in the network_spec.yml. Default value: 172.16.107.1 Note In multi-subnet DHCP deployments, the virtual IP address must be allocated from the IP range assigned to the service cluster nodes.

Local Repository Configuration

local_repo_config.yml

Parameter	Mandatory/Optional	Details
user_registry	Optional	Type: JSON list This variable accepts a list of user container registries from which additional container images can be downloaded and synchronized into the Omnia local repository. Omnia connects to the specified registries, pulls the required images, and stores them in local repository. These images are then accessed by the cluster nodes from local repository. host: Registry IP and port on which user registry is hosted. User registry can use both HTTP and HTTPS. To be strictly specified in the format IP:port. cert_path: Path to the SSL certificate file. This field is required when the registry uses HTTPS and must point to a file with a .crt extension. key_path: Path to the SSL private key file. This parameter is mandatory when the registry operates over HTTPS and must reference a file with a .key extension. Note User registry certificates and private keys specified in cert_path and key_path must already exist at the given locations, and these paths must be accessible from within the omnia_core container.
user_repo_url_x86_64	Optional	Type: JSON list This variable accepts the x86_64 repository urls from which the software packages/images will be downloaded and accessed by the cluster. Omnia downloads the software packages from the given list of URLs and stores them into a local Pulp container. These packages are then accessed by the cluster nodes from that Pulp container. url The URL defines the base URL for the repository, and it should always point to the repodata directory of the repository. gpgkey defines gpgkey for the repository. If gpgkey is omitted then gpgcheck=0 is set for that repository. name defines the name of the software .rpm package. If you are using SSL certificates for encryption, include the sslcacert, sslclientkey, and sslclientcert fields, and ensure each is populated with the correct certificate or key data. Omit these fields entirely if SSL is not in use. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set policies (always, partial) for each user repository individually. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Example: - { url: "https://download.docker.com/linux/centos/9/x86_64/stable", gpgkey: "https://download.docker.com/linux/centos/gpg", name: "docker-ce-repo", sslcacert: "", sslclientkey: "", sslclientcert: "", policy: "" } Note All SSL related certificates must be kept in /opt/omnia/user-repo-certs/<user_repo_name>. The certificate files are encrypted post local_repo.yml playbook execution. Execute the ansible-vault decrypt <certificate_file> --vault-password-file /opt/omnia/input/project_default/.local_repo_credentials_key command to decrypt the files.
user_repo_url_aarch64	Optional	Type: JSON list This variable accepts the aarch64 repository urls from which the software packages/images will be downloaded and accessed by the cluster. Omnia downloads the software packages from the given list of URLs and stores them into a local Pulp container. These packages are then accessed by the cluster nodes from that Pulp container. url The URL defines the base URL for the repository, and it should always point to the repodata directory of the repository. gpgkey defines gpgkey for the repository. If gpgkey is omitted then gpgcheck=0 is set for that repository. name defines the name of the software .rpm package. If you are using SSL certificates for encryption, include the sslcacert, sslclientkey, and sslclientcert fields, and ensure each is populated with the correct certificate or key data. Omit these fields entirely if SSL is not in use. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set policies (always, partial) for each user repository individually. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Example: - { url: "https://download.docker.com/linux/centos/9/aarch64/stable", gpgkey: "https://download.docker.com/linux/centos/gpg", name: "docker-ce-repo", sslcacert: "", sslclientkey: "", sslclientcert: "", policy: "" } Note All SSL related certificates must be kept in /opt/omnia/user-repo-certs/<user_repo_name>. The certificate files are encrypted post local_repo.yml playbook execution. Execute the ansible-vault decrypt <certificate_file> --vault-password-file /opt/omnia/input/project_default/.local_repo_credentials_key command to decrypt the files.
rhel_os_url_x86_64	Mandatory	Type: string Mandatory when cluster_os_type is rhel in /opt/omnia/input/project_default/software_config.json and the RHEL subscription is not registered. For RHEL systems without a subscription, the repository URLs for codeready-builder, appstream, and baseos are mandatory. Additional packages required for the cluster are downloaded from the provided rhel_os_url and stored in the Pulp container. url defines the baseurl for the repository where the OS package is hosted. gpgkey defines the gpgkey for the repository. If gpgkey is omitted, then gpgcheck=0 is set for that repository. name defines the name of the OS package. If you are using SSL certificates for encryption, include the sslcacert, sslclientkey, and sslclientcert fields, and ensure each is populated with the correct certificate or key data. Omit these fields entirely if SSL is not in use. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set an individual policy (always, partial) for the rhel_os_url. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Example: If cluster_os_type is rhel, rhel_os_url might be - { url: "http://crb.com/CRB/x86_64/os/", gpgkey: "http://crb.com/CRB/x86_64/os/RPM-GPG-KEY", sslcacert: "", sslclientkey: "", sslclientcert: "", name: "codeready-builder"} Note All SSL related certificates must be kept in /opt/omnia/rhel-repo-certs/<rhel_repo_name>. The certificate files are encrypted post local_repo.yml playbook execution. Execute the ansible-vault decrypt <certificate_file> --vault-password-file /opt/omnia/input/project_default/.local_repo_credentials_key command to decrypt the files.
rhel_os_url_aarch64	Mandatory	Type: string Mandatory when cluster_os_type is rhel in /opt/omnia/input/project_default/software_config.json and the RHEL subscription is not registered. For RHEL systems without a subscription, the repository URLs for codeready-builder, appstream, and baseos are mandatory. Additional packages required for the cluster are downloaded from the provided rhel_os_url and stored in the Pulp container. url defines the baseurl for the repository where the OS package is hosted. gpgkey defines the gpgkey for the repository. If gpgkey is omitted, then gpgcheck=0 is set for that repository. name defines the name of the OS package. If you are using SSL certificates for encryption, include the sslcacert, sslclientkey, and sslclientcert fields, and ensure each is populated with the correct certificate or key data. Omit these fields entirely if SSL is not in use. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set an individual policy (always, partial) for the rhel_os_url. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Example: If cluster_os_type is rhel, rhel_os_url might be - { url: "http://crb.com/CRB/aarch64/os/", gpgkey: "http://crb.com/CRB/aarch64/os/RPM-GPG-KEY", sslcacert: "", sslclientkey: "", sslclientcert: "", name: "codeready-builder" } Note All SSL related certificates must be kept in /opt/omnia/rhel-repo-certs/<rhel_repo_name>. The certificate files are encrypted post local_repo.yml playbook execution. Execute the ansible-vault decrypt <certificate_file> --vault-password-file /opt/omnia/input/project_default/.local_repo_credentials_key command to decrypt the files.
rhel_subscription_repo_config_x86_64	Optional	Type: JSON list Optional configuration for overriding policy and caching settings for RHEL subscription-based repositories on x86_64 architecture. When subscription is enabled, this config takes precedence over dynamically generated URLs for matching repositories and adds any additional repositories. Matching is done by repository name (e.g., x86_64_appstream) and Non-matching repositories are added as additional repos. Additional packages required for the cluster are downloaded from the provided rhel_subscription_repo_config_x86_64 and stored in the Pulp container. url defines the baseurl for the repository where the OS package is hosted. gpgkey defines the aarch64_gpgkey for the repository. If gpgkey is omitted, then gpgcheck=0 is set for that repository. name defines the name of the OS package. To override any of the 3 base repos (baseos, appstream, codeready-builder), the ‘name’ field must match exactly: ‘baseos’, ‘appstream’, or ‘codeready-builder’ SSL certificates are ALWAYS auto-populated from RHEL subscription defaults Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set an individual policy (always, partial) for the rhel_subscription_repo_config_x86_64. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Example : Override baseos with standard URL (only url and name required, certs auto-populated) - { url: "https://cdn.redhat.com/content/dist/rhel10/10.0/x86_64/baseos/os/", name: "baseos" } Override appstream with custom URL and policy - { url: "https://cdn.redhat.com/content/dist/rhel10/10.0/x86_64/appstream/os/", name: "appstream", policy: "always" } Add supplementary repo (non-base repo, certs auto-populated) - { url: "https://cdn.redhat.com/content/dist/rhel10/10.0/x86_64/supplementary/os/", name: "supplementary", policy: "always", caching: false } Note All SSL related certificates must be kept in /opt/omnia/rhel-repo-certs/<rhel_repo_name>. The certificate files are encrypted post local_repo.yml playbook execution. Execute the ansible-vault decrypt <certificate_file> --vault-password-file /opt/omnia/input/project_default/.local_repo_credentials_key command to decrypt the files.
rhel_subscription_repo_config_aarch64	Optional	Type: JSON list Optional configuration for overriding policy and caching settings for RHEL subscription-based repositories on x86_64 architecture. When subscription is enabled, this config takes precedence over dynamically generated URLs for matching repositories and adds any additional repositories. Matching is done by repository name (e.g., x86_64_appstream) and Non-matching repositories are added as additional repos. Additional packages required for the cluster are downloaded from the provided rhel_subscription_repo_config_aarch64 and stored in the Pulp container. url defines the baseurl for the repository where the OS package is hosted. gpgkey defines the aarch64_gpgkey for the repository. If gpgkey is omitted, then gpgcheck=0 is set for that repository. name defines the name of the OS package. If you are using SSL certificates for encryption, include the sslcacert, sslclientkey, and sslclientcert fields, and ensure each is populated with the correct certificate or key data. Omit these fields entirely if SSL is not in use. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set an individual policy (always, partial) for the rhel_subscription_repo_config_aarch64. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Example : Override baseos with standard URL (only url and name required, certs auto-populated) - { url: "https://cdn.redhat.com/content/dist/rhel10/10.0/aarch64/baseos/os/", name: "baseos" } Override appstream with custom URL and policy - { url: "https://cdn.redhat.com/content/dist/rhel10/10.0/aarch64/appstream/os/", name: "appstream", policy: "always" } Add supplementary repo (non-base repo, certs auto-populated) - { url: "https://cdn.redhat.com/content/dist/rhel10/10.0/aarch64/supplementary/os/", name: "supplementary", policy: "always", caching: false } Note All SSL related certificates must be kept in /opt/omnia/rhel-repo-certs/<rhel_repo_name>. The certificate files are encrypted post local_repo.yml playbook execution. Execute the ansible-vault decrypt <certificate_file> --vault-password-file /opt/omnia/input/project_default/.local_repo_credentials_key command to decrypt the files.
omnia_repo_url_rhel_x86_64	Mandatory	Type: JSON list This variable accepts a list of all the x86_64 repo urls from where .rpm packages will be downloaded for RHEL clusters. url defines the baseurl for the repository where the package is hosted. gpgkey defines the gpgkey for the repository. If gpgkey is omitted, then gpgcheck=0 is set for that repository. name defines the name of the software .rpm package. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set individual policies (always, partial) for the repository URLs. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Default value: { url: “https://download.docker.com/linux/centos/10/x86_64/stable/”, gpgkey: “https://download.docker.com/linux/centos/gpg”, name: “docker-ce-repo”} { url: “https://dl.fedoraproject.org/pub/epel/10/Everything/x86_64/”, gpgkey: “https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-9”, name: “epel”} Note These inputs are not validated by Omnia. Incorrect values provided to this variable can lead to unexpected failures during Omnia’s deployment. Ensure that all the listed URLs are reachable from the OIM.
omnia_repo_url_rhel_aarch64	Mandatory	Type: JSON list This variable accepts a list of all the aarch64 repo urls from where .rpm packages will be downloaded for RHEL clusters. url defines the baseurl for the repository where the package is hosted. gpgkey defines the gpgkey for the repository. If gpgkey is omitted, then gpgcheck=0 is set for that repository. name defines the name of the software .rpm package. Irrespective of the value set to repo_config in /opt/omnia/input/project_default/software_config.json, you can set individual policies (always, partial) for the repository URLs. To do so, add the policy key and provide the desired value while providing the repository URLs. Enable or disable local caching of repository content in the Pulp container. true: Store packages locally to improve performance and reduce bandwidth. false : Always download fresh packages from the repository. Allowed values: true,false (OPTIONAL). Defaults to true if not provided.To do so, add the caching key and provide the desired value while providing the repository URLs. Default value: { url: “https://download.docker.com/linux/centos/10/aarch64/stable/”, gpgkey: “https://download.docker.com/linux/centos/gpg”, name: “docker-ce”} { url: “https://dl.fedoraproject.org/pub/epel/10/Everything/aarch64/”, gpgkey: “https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-9”, name: “epel”} Note These inputs are not validated by Omnia. Incorrect values provided to this variable can lead to unexpected failures during Omnia’s deployment. Ensure that all the listed URLs are reachable from the OIM.
additional_repos_x86_64	Optional	Type: JSON list Each repository entry must include: url: Repository base URL. name: Unique repository name. gpgkey: URL to the repository GPG key, or empty string (“”) if you are not using GPG. Example: yaml additional_repos_x86_64: { url: “https://nginx.org/packages/rhel/9/x86_64/”, gpgkey: “”, name: “test-nginx” }
additional_repos_aarch64	Optional	Type: JSON list Each repository entry must include: url: Repository base URL. name: Unique repository name. gpgkey: URL to the repository GPG key, or empty string (“”) if you are not using GPG. Example: yaml additional_repos_aarch64: { url: “https://nginx.org/packages/rhel/9/aarch64/”, gpgkey: “”, name: “test-nginx-arm” }

Network Configuration

network_spec.yml

Network Name	Parameters for the network	Parameter details
admin_network	oim_nic_name string Mandatory	The name of the interface on the OIM server associated with the admin network. Default value: eno1”
	subnet IP address Mandatory	The subnet address for the admin network. Default value: 172.16.0.0”
	netmask_bits integer Mandatory	The number of bits in the subnet mask. Default value: 24”
	primary_oim_admin_ip IP address Mandatory	The admin IP address of the OIM server which is configured. Default value: 172.16.107.254”
	primary_oim_bmc_ip IP address Optional	The iDRAC IP address of the OIM server. Mandatory only if idrac_telemetry is set to true and telemetry data needs to be collected from the OIM server. Optional - can be omitted if iDRAC telemetry for the OIM server is not required. Default value: ""
	router IP address Optional	In connected deployments, the router field should typically be set to the external rack gateway, such as a SONiC switch, which provides connectivity beyond the rack network. In air-gapped deployments, the router field can be set to the OIM’s IP address if the OIM is acting as the rack gateway. If another dedicated router or gateway is available, its IP address should be specified instead. The configured value is advertised to nodes via DHCP as their default gateway. Default value: 172.16.107.254
	dynamic_range IP address range Mandatory	The range of dynamic IP addresses available on the admin network. Default value: 172.16.107.201-172.16.107.250”
	dns array of IP addresses Optional	The list of external DNS server IP addresses for the admin network. Default value: []
	ntp_servers array of NTP server objects Optional	The list of NTP servers for the admin network. Each NTP server entry should include address (IP address or hostname) and type (server or pool). Default value: []
additional_subnets	array of subnet objects Optional	Optional field for multi-RAC/multi-subnet PXE deployments. Each entry defines a separate subnet that the CoreDHCP server will manage via DHCP relay (giaddr-based routing). Requires coresmd v0.5+ with multi-subnet support. Leave empty array ([]) for single-subnet deployments. Default value: [] Each additional subnet entry contains the following parameters: subnet - The network address of the additional subnet (e.g. “10.40.1.0”) netmask_bits - The CIDR prefix length (e.g. “24”) router - The gateway/router IP for this subnet (used as DHCP option 3) dynamic_range - The DHCP IP pool range in “start_ip-end_ip” format. Must fall within the subnet. For more information about configuring Multi-Subnet DHCP, see Configuring Multi-Subnet DHCP.
ib_network	subnet IP address Mandatory	The subnet of the IB network. Default value: 192.168.0.0
	netmask_bits integer Mandatory	The number of bits in the subnet mask. This value must be same as the admin_network netmask_bits. Default value: 24
	dns array of IP addresses Optional	External DNS server IP addresses for the InfiniBand network. Default value: []

Omnia Configuration

omnia_config.yml

Variables	Mandatory/Optional	Details
cluster_name	Mandatory	Type: String Name of the cluster on which you want to deploy Kubernetes. This input is case-sensitive. Do not add any special characters except _ (underscore) in the cluster name.
deployment	Mandatory	Type: Boolean Indicates if Kubernetes will be deployed or not. Accepted values: true or false
k8s_cni	Mandatory	Type: String Kubernetes SDN network. Accepted values: calico Default value: calico
pod_external_ip_range	Mandatory	Type: String These addresses will be used by the loadbalancer for assigning external IPs to Kubernetes services. Ensure that the IP range provided is not assigned to any node in the cluster. Ensure that the pod_external_ip_range defined in the omnia_config.yml file is reachable from the OpenManage Enterprise appliance and the SFM network. Sample values: 172.16.107.170-172.16.107.200
k8s_service_addresses	Optional	Type: String Kubernetes internal network for services. This network must be unused in your network infrastructure. Default value: "10.233.0.0/18"
k8s_pod_network_cidr	Optional	Type: String Kubernetes pod network CIDR for internal network. When used, it will assign IP addresses from this range to individual pods. This network must be unused in your network infrastructure. Default value: "10.233.64.0/18"
csi_powerscale_driver_secret_file_path	Optional	Type: File path If you want to deploy the CSI driver for PowerScale on your service cluster, add the file path of the secrets.yaml file to this variable.
csi_powerscale_driver_values_file_path	Optional	Type: File path If you want to deploy the CSI driver for PowerScale on your service cluster, add the file path of the values.yaml file to this variable.
nfs_storage_name	Mandatory	Type: String Use same name as mentioned in each of the name available in storage_config.yml.
k8s_crio_storage_size	Mandatory	Type: String Specifies the disk size allocated for CRI-O container storage.
etcd_on_local_disk	Optional	Type: Boolean Determines whether ETCD is deployed on local disk or NFS storage. Accepted values: true or false Default value: false When set to true, ETCD is deployed on local disk on all master nodes. The system prioritizes BOSS card if available, and falls back to SSD/SATA disks if BOSS is not present. The /var/lib/etcd directory is mounted on the selected local disk. When set to false or omitted, ETCD storage is provisioned using NFS, and no local disk configuration is performed for ETCD. Important: Migration from NFS to local disk is not supported during upgrades. This configuration is only applicable for fresh installations.

Provisioning Configuration

provision_config.yml

Parameter	Details
pxe_mapping_file_path string Mandatory	Enter the path where user has placed the PXE mapping CSV file that contains the node details for provisioning. The file must follow the format: FUNCTIONAL_GROUP_NAME, GROUP_NAME, SERVICE_TAG, PARENT_SERVICE_TAG, HOSTNAME, ADMIN_MAC, ADMIN_IP, BMC_MAC, BMC_IP, IB_NIC_NAME, IB_IP. Ensure that admin IPs given in mapping file are within the network defined in the network_spec.yml A sample file is provided here: /omnia/examples/pxe_mapping_file.csv
language string Mandatory	Language to be used during OS provisioning. Only supported value: en_US.UTF-8
default_lease_time integer Mandatory	Default lease time for IPs assigned by DHCP. Unit: seconds. Range: 21600-31536000 Default value: 86400
dns_enabled boolean Optional	Enable DNS-based hostname resolution for compute nodes using coresmd (CoreDNS + OpenCHAMI SMD plugin). When true, nodes use coresmd for hostname resolution instead of static /etc/hosts file management. DNS records are generated automatically from SMD inventory using the NID-based pattern. The cluster domain is read from OIM metadata (domain_name). When enabled, /etc/hosts is still populated from the PXE mapping file for custom hostnames (hybrid mode). Default value: false
kernel_version_override string Optional	Pin a specific kernel version for boot image selection. Leave empty (") to auto-select the latest available image from S3. Example: 6.12.0-55.76.1.el10_0 Default value: "
additional_cloud_init_config_file string Optional	Path to an external YAML file containing additional cloud-init directives (write_files and runcmd) to inject into the provisioning pipeline. Supports both cluster-wide (common) and per-functional-group (groups) customization. Leave empty to disable. For details, see Additional Cloud-Init Configuration. Default value: " Example: /opt/omnia/input/project_default/additional_cloud_init.yml

Security Configuration

security_config.yml

Parameter	Details
domain_name string Required	Sets the intended domain name. If dc=omnia,dc=test, provide omnia.test If dc=dell,dc=omnia,dc=com, provide dell.omnia.com Default values: omnia.test

Storage Configuration

storage_config.yml

Parameter	Details
mounts List (dict) Mandatory	Configure mount points compatible with cloud-init mounts module. Source must be known at boot time (NFS paths, UUIDs, local devices). For runtime-discovered sources (iSCSI/multipath), use powervault_config section. Mandatory Fields: name—Unique identifier for this mount entry. Pattern: [a-zA-Z0-9_-], length 1-64 source - Device or network path. Mandatory * For NFS: server_ip:/export/path (e.g., 192.168.1.100:/export/share, nfs-server.example.com:/home) * For local: /dev/sdc, UUID=xxx, LABEL=xxx * For CIFS: //server/share * Note: NFS paths must be resolvable at boot time (use IP or DNS-resolvable hostname) mount_point - Absolute path for the mount point. Mandatory * Must be an absolute path starting with / (e.g., /home, /mnt/vast, /opt/data) * Avoid system directories (/etc, /sys, /proc, /boot, /root, /tmp) * Common patterns: /mnt/, /opt/, /home, /var/lib/* * Note: Path must be unique across all mount entries Optional Fields: fs_type—Filesystem type. Default: “auto”. Choices: auto, ext2, ext3, ext4, xfs, nfs, nfs4, cifs, tmpfs, cephfs, vfat, ntfs, none, fuse.s3fs. If specified, takes PRIORITY over mount_params profile mnt_opts—Mount options string (e.g., defaults,noexec,nofail). If specified, takes PRIORITY over mount_params profile dump_freq—Dump frequency. Default: “0”. Allowed values: “0”-“2”. If specified, takes PRIORITY over mount_params profile fsck_pass—Fsck pass number. Default: “0”. Allowed values: “0”-“9”. If specified, takes PRIORITY over mount_params profile mount_params—Name of a profile in mount_params section. Used ONLY for fields not explicitly specified in the mount entry mount_on_oim—Boolean flag to mount on OIM (Omnia Image Management). Default: false. Ensure storage is network-accessible from OIM before enabling permissions—Directory ownership and mode for the mount point (applied via chown + chmod after mount) owner: User owner (name or numeric UID). Default: “root” group: Group owner (name or numeric GID). Default: “root” mode: Octal permission string (3-4 digits). Default: “0755”. Examples: “0755”, “1777” Node-Specific Bind Mounts (paired parameters): node_key—Per-node subdirectory isolation variable. Optional * Allowed values: “local_hostname” - hostname of the node “local_ipv4” - IPv4 address of the node “instance_id” - instance ID of the node from cloud-init Default: “local_hostname” When set, node_mount_point is MANDATORY Generates bind mounts: <mount_point>/<node_key_value>/<target> -> <target> node_mount_point—List of bind mount target paths. Mandatory when node_key is set. Minimum 1 entry, values must be unique absolute paths. Pattern: <mount_point>/<node_key_value>/<target_stripped_slash> -> <target> Node Targeting (exactly ONE is required - mutually exclusive): functional_group_prefix—List of functional group name prefixes. All nodes whose group name starts with any listed prefix receive this mount. Example: [“slurm”] matches slurm_control_node, slurm_node, etc. MUTUALLY EXCLUSIVE with groups groups—List of GROUP_NAME values from pxe_mapping_file.csv. Only nodes assigned to the listed PXE groups receive this mount. Example: [“grp1”, “grp2”] targets only nodes in those groups. MUTUALLY EXCLUSIVE with functional_group_prefix
mount_params dict Optional	Named default profiles for mount configurations. Profiles are referenced by name from mount entries via the mount_params field. Mandatory Profile Fields: fs_type—Default filesystem type. Choices: auto, ext2, ext3, ext4, xfs, nfs, nfs4, cifs, tmpfs, cephfs, vfat, ntfs, none, fuse.s3fs mnt_opts—Default mount options string (comma-separated) Optional Profile Fields: dump_freq—Default dump frequency. Allowed values: “0”-“2” fsck_pass—Default fsck pass number. Allowed values: “0”-“9” Predefined Profiles: nfs_default—Default NFS mount fs_type: “nfs” mnt_opts: “nosuid,rw,sync,hard” dump_freq: “0” fsck_pass: “0” vast_rdma—VAST NFS with RDMA configuration over InfiniBand fs_type: “nfs” mnt_opts: “proto=rdma,nconnect=8,timeo=600,retrans=2,rsize=1048576,wsize=1048576,hard” vast_tcp—VAST NFS storage with standard TCP configuration fs_type: “nfs” mnt_opts: “nosuid,rw,sync,hard”
powervault_config List (dict) Optional	PowerVault iSCSI storage configuration. Processed entirely via runcmd script (setup_iscsi_storage.sh). The device path (/dev/mapper/XXX) is only known after iSCSI login + multipath scan, so powervault mounts CANNOT use the cloud-init mounts module. The runcmd script handles: iscsid enable, initiator name, discovery, login, multipathd, volume_id matching, partitioning, formatting, mount, and bind mounts. NOTE: The groups field is NOT supported for powervault_config entries. Only functional_group_prefix is available for node targeting. Mandatory Fields: name—Unique identifier for this PowerVault entry. Pattern: [a-zA-Z0-9_-], length 1-64 ip—List of PowerVault controller IPv4 addresses for iSCSI discovery. Minimum 1 address, values must be unique iscsi_initiator—iSCSI initiator IQN for the host. Pattern: iqn.<date>.<domain>:<identifier> volume_id—Volume WWN/identifier for multipath device matching. Pattern: hex string [a-fA-F0-9]+ mount_point—Absolute path where the discovered device gets mounted functional_group_prefix—List of OpenCHAMI functional group name prefixes. All nodes whose group name starts with any listed prefix receive this entry Optional Fields: port—TCP port for iSCSI target service. Default: 3260. Range: 1-65535 fs_type—Filesystem type. Default: “xfs”. Choices: xfs, ext4, ext3, ext2, nfs, nfs4, cifs, ntfs, auto. If specified, takes PRIORITY over mount_params profile mnt_opts—Mount options string. If specified, takes PRIORITY over mount_params profile dump_freq—Dump frequency. Default: “0”. Allowed values: “0”-“2” fsck_pass—Fsck pass number. Default: “0”. Allowed values: “0”-“9” mount_params—Named profile key from mount_params section Node-Specific Bind Mounts (paired parameters): node_key—Per-node subdirectory isolation variable. Choices: “local_hostname”, “local_ipv4”, “instance_id”. Default: “local_hostname”. When set, node_mount_point is MANDATORY. When node_key is specified, fs_type is forced to “none” and mnt_opts is forced to “bind” regardless of user input node_mount_point—List of bind mount target paths. Mandatory when node_key is set. Pattern: <mount_point>/<node_key_value>/<target_stripped_slash> -> <target> Permissions (optional sub-object, applied via chown + chmod after mount): permissions.owner—User owner (name or UID). Default: “root” permissions.group—Group owner (name or GID). Default: “root” permissions.mode—Octal permission string (3-4 digits). Default: “0755”

Telemetry Configuration

telemetry_config.yml

Parameter	Mandatory/Optional	Details
telemetry_sources > idrac > metrics_enabled	Mandatory	Type: Boolean Enable or disable iDRAC metrics collection from Dell PowerEdge servers Collected metrics: temperature, power, fan speed, storage health, CPU/memory errors Data path: iDRAC Receiver -> ActiveMQ -> KafkaPump -> Kafka ‘idrac’ topic iDRAC Receiver -> ActiveMQ -> VictoriaPump -> vmagent -> victoria_metrics Accepted values: true or false Default value: true Note If iDRAC telemetry is enabled, mysqldb_user, mysqldb_password, and mysqldb_root_password parameters in the omnia_config_credentials.yml file become mandatory. Note If you want to deploy only Slurm clusters (slurm_custom), set metrics_enabled to false.
telemetry_sources > idrac > collection_targets	Mandatory	Collection targets define where iDRAC data is sent before Vector processing Supported values: victoria_metrics, kafka Multiple targets: Can specify both [victoria_metrics, kafka] Default: [victoria_metrics, kafka]
idrac_telemetry_configurations > mysqldb_storage	Conditional Mandatory	MySQL database storage for iDRAC telemetry Purpose: Storage configuration for iDRAC telemetry MySQL database Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 1Gi Required when: telemetry_sources > idrac > metrics_enabled is true
telemetry_sources > ldms > metrics_enabled	Mandatory	Type: Boolean Enable or disable LDMS metrics collection from compute nodes Collected metrics: CPU, memory, network, disk metrics Data path: LDMS samplers → LDMS aggregator → store_avro_kafka → Kafka ‘ldms’ topic Accepted values: true or false Default value: true
telemetry_sources > ldms > collection_targets	Mandatory	LDMS only supports Kafka collection (no direct victoria_metrics path) Vector-LDMS bridge consumes from Kafka and routes to victoria_metrics Supported values: kafka Default: [kafka]
telemetry_sources > dcgm > metrics_enabled	Optional	Type: Boolean Enable or disable DCGM (NVIDIA Data Center GPU Manager) metrics collection Collected metrics: GPU temperature, utilization, memory, ECC errors, power Requires: NVIDIA GPU driver installed on compute nodes Accepted values: true or false Default value: true
telemetry_sources > powerscale > metrics_enabled	Optional	Type: Boolean Enable or disable PowerScale metrics collection from Dell PowerScale (OneFS) storage Collected metrics: Storage metrics from Dell PowerScale clusters Requires: CSM Observability (Karavi) values file configured Data path: CSM Metrics PowerScale → OTEL Collector → vmagent(shared) → victoria_metrics Accepted values: true or false Default value: true
telemetry_sources > powerscale > logs_enabled	Optional	Type: Boolean Enable or disable PowerScale logs collection Accepted values: true or false Default value: true
telemetry_sources > powerscale > collection_targets	Conditional Mandatory	PowerScale uses dedicated vmagent(shared) (no Kafka, no Vector) Supported values: victoria_metrics, victoria_logs Default: [victoria_metrics, victoria_logs]
telemetry_sources > ufm > metrics_enabled	Optional	Type: Boolean Enable or disable UFM (NVIDIA UFM InfiniBand Fabric Manager) metrics collection Collected metrics: IB port state, transmit/receive data, error counters, fabric topology Requires: NVIDIA UFM appliance with Prometheus exporter enabled Data path: UFM Prometheus Exporter → vmagent(shared) → victoria_metrics Accepted values: true or false Default value: false
telemetry_sources > ufm > logs_enabled	Optional	Type: Boolean Enable or disable UFM syslog logs collection Accepted values: true or false Default value: false
telemetry_sources > ufm > collection_targets	Conditional Mandatory	UFM uses vmagent(shared) for metrics and VLAgent for logs Supported values: victoria_metrics, victoria_logs Default: [victoria_metrics, victoria_logs]
telemetry_sources > vast > metrics_enabled	Optional	Type: Boolean Enable or disable VAST (Data Storage) metrics collection Collected metrics: IB port state, transmit/receive data, error counters, fabric topology Requires: VAST appliance with Prometheus exporter enabled Data path: Prometheus Exporter → vmagent(shared) → victoria_metrics Accepted values: true or false Default value: false
telemetry_sources > vast > logs_enabled	Optional	Type: Boolean Enable or disable VAST syslog logs collection Accepted values: true or false Default value: false
telemetry_sources > vast > collection_targets	Conditional Mandatory	VAST uses vmagent(shared) for metrics and VLAgent for logs Supported values: victoria_metrics, victoria_logs Default: [victoria_metrics, victoria_logs]
telemetry_bridges > vector_ldms > metrics_enabled	Optional	Type: Boolean Enable or disable Vector-LDMS bridge (Kafka-to-victoria_metrics bridge for LDMS metrics) Purpose: Consume LDMS metrics from Kafka ‘ldms’ topic, transform NERSC schema to Prometheus format, and write to victoria_metrics Data flow: Kafka ‘ldms’ topic → Vector-LDMS → vmagent-vector → victoria_metrics Requires: telemetry_sources > ldms > metrics_enabled = true Accepted values: true or false Default value: true
telemetry_bridges > vector_ome > metrics_enabled	Optional	Type: Boolean Enable or disable Vector-OME metrics routing (Kafka-to-Victoria bridge for OME metrics) Data flow: Kafka ‘ome.*’ topics → Vector-OME → vmagent-vector (metrics) Requires: OME to be configured with kafka Accepted values: true or false Default value: true
telemetry_bridges > vector_ome > logs_enabled	Optional	Type: Boolean Enable or disable Vector-OME logs routing Data flow: Kafka ‘ome.*’ topics → Vector-OME → vlagent-vector (logs) Accepted values: true or false Default value: true
telemetry_bridges > vector_ome > ome_identifier	Optional	Identifier used by Vector-OME for topic identification and routing Internally used to match topics with the prefix (e.g., ^ome\\..*$) Type: String minLength: 1 Default value: ome Note: Change only if your OME Kafka topics use a different prefix
telemetry_sinks > victoria_metrics > persistence_size	Conditional Mandatory	Storage per vmstorage pod PVC Important: Total VictoriaMetrics storage depends on deployment mode: Single-node mode: Total storage = persistence_size * 1 pod Cluster mode: Total storage = persistence_size * 3 vmstorage pods Example (cluster): 8Gi * 3 = 24Gi total VictoriaMetrics storage Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 8Gi (results in 24Gi total storage for cluster mode)
telemetry_sinks > victoria_metrics > retention_period	Conditional Mandatory	Metric retention period in hours Default: 168 (7 days)
telemetry_sinks > victoria_metrics > additional_metric_remote_write_endpoints	Optional	Additional remote write endpoints for metrics (optional) Purpose: Send metrics to external VictoriaMetrics instances in addition to Omnia-managed VictoriaMetrics Format: List of endpoint objects with ‘url’ field (must start with http:// or https://) TLS: Set ‘tls_insecure_skip_verify: true’ to skip TLS certificate verification Default: [] (empty — only Omnia VictoriaMetrics receives metrics) Example: - url: https://external-metrics-server:8480/insert/0/prometheus/api/v1/write tls_insecure_skip_verify: false
telemetry_sinks > victoria_logs > storage_size	Conditional Mandatory	Storage per vlstorage pod PVC Total storage = storage_size × 3 vlstorage pods Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 8Gi (results in 24Gi total storage) Sizing formula: (140 MB/day × retention_days × node_count) / 3 replicas Warning Storage under-provisioning can lead to data loss before the retention period is reached. Calculate storage requirements based on expected log volume and retention needs.
telemetry_sinks > victoria_logs > retention_period	Conditional Mandatory	Log retention period in hours Type: Integer (hours) Accepted values: 24-8760 (1 day to 1 year) Default: 168 (7 days) Note: Retention is global and applies to all log streams uniformly. Deletion occurs asynchronously during background merge operations. Note VictoriaLogs does not return an error when log entries with timestamps outside the configured retention window are submitted. Log entries will be automatically removed from VictoriaLogs after the retention period.
telemetry_sinks > victoria_logs > additional_log_write_endpoints	Optional	Additional remote write endpoints for logs (optional) Purpose: Send logs to external VictoriaLogs instances in addition to Omnia-managed VictoriaLogs Format: List of endpoint objects with ‘url’ field (must start with http:// or https://) TLS: Set ‘tls_insecure_skip_verify: true’ to skip TLS certificate verification Default: [] (empty — only Omnia VictoriaLogs receives logs) Example: - url: https://external-logs-server:9481/internal/insert tls_insecure_skip_verify: false
telemetry_sinks > kafka > persistence_size	Conditional Mandatory	Storage per Kafka pod PVC Total = persistence_size × 6 pods (3 brokers + 3 controllers) Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 8Gi (results in 48Gi total storage) The default 8Gi size is suitable for small clusters (typically fewer than 5 nodes). For larger clusters, you should increase the persistence_size and adjust log_retention_hours and log_retention_bytes based on expected data volume and cluster size. Caution Ensure that the Kafka broker settings persistence_size, log_retention_hours, and log_retention_bytes are configured based on your data retention requirements. If the persistent volume reaches its capacity before logs are deleted according to the log retention period configured, Kafka brokers may run out of disk space. For more details on managing Kafka log retention and cleanup policies, see Managing Kafka logs with delete and compact policies.
telemetry_sinks > kafka > log_retention_hours	Conditional Mandatory	Log retention period in hours Default: 168 (7 days)
telemetry_sinks > kafka > log_retention_bytes	Conditional Mandatory	Maximum size of Kafka logs (in bytes) before deletion Default: -1 (unlimited)
telemetry_sinks > kafka > log_segment_bytes	Conditional Mandatory	Maximum size of Kafka log segments (in bytes) Default: 1073741824 (1 GB)
telemetry_sinks > kafka > topic_partitions	Conditional Mandatory	Topic partitions per source (object format, not array) Format: {topic_name: partition_count} Required when: Source has kafka in collection_targets Allowed topics: idrac, ldms only Default partition counts: idrac=1, ldms=2 Example: {idrac: 1, ldms: 2}
ldms_configurations > agg_port	Conditional Mandatory	Aggregator port on service K8s cluster Valid range: 6001-6100 Default: 6001
ldms_configurations > store_port	Conditional Mandatory	Store daemon port on service K8s cluster The port can be the same as LDMS aggregator port Valid range: 6001-6100 Default: 6001
ldms_configurations > sampler_port	Conditional Mandatory	Sampler port on compute nodes Valid range: 10001-10100 Default: 10001
ldms_configurations > sampler_plugins	Mandatory	Sampler plugins define which metrics to collect from compute nodes Parameters: plugin_name: Name of the LDMS sampler plugin config_parameters: Plugin-specific configuration (as a single string) activation_parameters: Collection schedule in MICROSECONDS Format: interval=<microseconds> offset=<microseconds> Example: interval=30000000 (30 seconds) Default plugins: meminfo: Memory usage statistics (free, used, buffers, cached) procstat2: Process statistics (CPU, memory, I/O per process) vmstat: Virtual memory statistics (paging, swapping, memory pressure) loadavg: System load average (1, 5, and 15 minute averages) procnetdev2: Network interface statistics (bytes, packets, errors, drops per interface) Default activation_parameters: interval=30000000 (30 seconds for all plugins except procnetdev2 which includes offset=0)
powerscale_configurations > otel_collector_storage_size	Conditional Mandatory	PVC size for OTEL Collector metric batching and buffering Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 5Gi
powerscale_configurations > csm_observability_values_file_path	Conditional Mandatory	Path to the CSM Observability (Karavi Observability) values.yaml file Required when: telemetry_sources > powerscale > metrics_enabled: true Reference: https://raw.githubusercontent.com/dell/helm-charts/refs/heads/release-v1.17.1/charts/karavi-observability/values.yaml Default value: " Note In the values.yaml file, only set karaviMetricsPowerscale -> enabled: true. Set the following parameters to false: karaviMetricsPowerflex -> enabled=false, karaviMetricsPowerstore -> enabled=false, karaviMetricsPowerscaleauthorization.-> enabled=false, karaviMetricsPowermax -> enabled=false. Note Update the isiAuthType in the values.yaml file based on the current auth type setting. To check the current auth type setting, use the command isi http settings view. Note For CSI PowerScale health metrics, enable controller > healthMonitor > enabled: true and node > healthMonitor > enabled: true in the CSI PowerScale values.yaml (https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.17.0/charts/csi-isilon/values.yaml).
ufm_configuration > ufm_endpoint	Conditional Mandatory	UFM appliance IP address or hostname Required when: telemetry_sources > ufm > metrics_enabled is true Example: 172.20.44.180 or ufm.example.com Default value: "
ufm_configuration > ufm_metrics_port	Optional	UFM Prometheus exporter port Default value: 9001 (UFM default Prometheus port)
ufm_configuration > scrape_interval	Optional	Prometheus scrape interval for UFM metrics Accepted values: Prometheus duration format (e.g., 15s, 30s, 1m) Default value: 30s
ufm_configuration > scrape_timeout	Optional	Prometheus scrape timeout (must be <= scrape_interval) Accepted values: Prometheus duration format (e.g., 10s, 15s) Default value: 15s
ufm_configuration > tls_mode	Optional	TLS mode for connecting to UFM Prometheus endpoint Accepted values: self_signed, ca_signed self_signed: Skip TLS verification (insecure_skip_verify=true) ca_signed: Use CA certificate for TLS verification Default value: self_signed
ufm_configuration > ufm_ca_cert_path	Optional	Path to CA certificate file for UFM TLS verification Required when: tls_mode is ca_signed Must be a valid PEM-format certificate file Default value: " (empty — not used when tls_mode is self_signed)
ufm_configuration > auth_mode	Optional	Authentication mode for UFM Prometheus endpoint Accepted values: basic, none basic: Use ufm_username/ufm_password from omnia_config_credentials.yml none: No authentication (UFM endpoint is open) Default value: basic
vast_configuration > vast_endpoint	Conditional Mandatory	VAST appliance IP address or hostname Required when: telemetry_sources > vast > metrics_enabled is true Example: 172.20.44.180 or vast.example.com Default value: "
vast_configuration > vast_metrics_port	Optional	VAST Prometheus exporter port Default value: 9001 (VAST default Prometheus port)
vast_configuration > scrape_interval	Optional	Prometheus scrape interval for VAST metrics Accepted values: Prometheus duration format (e.g., 15s, 30s, 1m) Default value: 30s
vast_configuration > scrape_timeout	Optional	Prometheus scrape timeout (must be <= scrape_interval) Accepted values: Prometheus duration format (e.g., 10s, 15s) Default value: 15s
vast_configuration > tls_mode	Optional	TLS mode for connecting to VAST Prometheus endpoint Accepted values: self_signed, ca_signed self_signed: Skip TLS verification (insecure_skip_verify=true) ca_signed: Use CA certificate for TLS verification Default value: self_signed
vast_configuration > vast_ca_cert_path	Optional	Path to CA certificate file for VAST TLS verification Required when: tls_mode is ca_signed Must be a valid PEM-format certificate file Default value: " (empty — not used when tls_mode is self_signed)
vast_configuration > auth_mode	Optional	Authentication mode for VAST Prometheus endpoint Accepted values: basic, none basic: Use vast_username/vast_password from omnia_config_credentials.yml none: No authentication (VAST endpoint is open) Default value: basic

Telemetry Storage Configuration

telemetry_storage_config.yml

Parameter	Mandatory/Optional	Details
victoria_cluster > vmstorage > replicas	Mandatory	Number of vmstorage pod replicas Default value: 3 Note: For cluster mode, minimum 3 replicas are recommended for high availability
victoria_cluster > vmstorage > resources > requests > memory	Mandatory	Memory request for vmstorage pods Default value: 1Gi
victoria_cluster > vmstorage > resources > requests > cpu	Mandatory	CPU request for vmstorage pods Default value: 250m
victoria_cluster > vmstorage > resources > limits > memory	Mandatory	Memory limit for vmstorage pods Default value: 2Gi
victoria_cluster > vmstorage > resources > limits > cpu	Mandatory	CPU limit for vmstorage pods Default value: 1000m
victoria_cluster > vminsert > resources > requests > memory	Mandatory	Memory request for vminsert pods Default value: 256Mi
victoria_cluster > vminsert > resources > requests > cpu	Mandatory	CPU request for vminsert pods Default value: 100m
victoria_cluster > vminsert > resources > limits > memory	Mandatory	Memory limit for vminsert pods Default value: 512Mi
victoria_cluster > vminsert > resources > limits > cpu	Mandatory	CPU limit for vminsert pods Default value: 500m
victoria_cluster > vmselect > resources > requests > memory	Mandatory	Memory request for vmselect pods Default value: 256Mi
victoria_cluster > vmselect > resources > requests > cpu	Mandatory	CPU request for vmselect pods Default value: 100m
victoria_cluster > vmselect > resources > limits > memory	Mandatory	Memory limit for vmselect pods Default value: 512Mi
victoria_cluster > vmselect > resources > limits > cpu	Mandatory	CPU limit for vmselect pods Default value: 500m
victoria_cluster > vmagent > replicas	Mandatory	Number of vmagent pod replicas Default value: 2
victoria_cluster > vmagent > resources > requests > memory	Mandatory	Memory request for vmagent pods Default value: 128Mi
victoria_cluster > vmagent > resources > requests > cpu	Mandatory	CPU request for vmagent pods Default value: 50m
victoria_cluster > vmagent > resources > limits > memory	Mandatory	Memory limit for vmagent pods Default value: 512Mi
victoria_cluster > vmagent > resources > limits > cpu	Mandatory	CPU limit for vmagent pods Default value: 250m
victoria_logs_cluster > vlstorage > replicas	Mandatory	Number of vlstorage pod replicas Default value: 2
victoria_logs_cluster > vlstorage > resources > requests > memory	Mandatory	Memory request for vlstorage pods Default value: 512Mi
victoria_logs_cluster > vlstorage > resources > requests > cpu	Mandatory	CPU request for vlstorage pods Default value: 100m
victoria_logs_cluster > vlstorage > resources > limits > memory	Mandatory	Memory limit for vlstorage pods Default value: 1Gi
victoria_logs_cluster > vlstorage > resources > limits > cpu	Mandatory	CPU limit for vlstorage pods Default value: 500m
victoria_logs_cluster > vlinsert > resources > requests > memory	Mandatory	Memory request for vlinsert pods Default value: 256Mi
victoria_logs_cluster > vlinsert > resources > requests > cpu	Mandatory	CPU request for vlinsert pods Default value: 100m
victoria_logs_cluster > vlinsert > resources > limits > memory	Mandatory	Memory limit for vlinsert pods Default value: 512Mi
victoria_logs_cluster > vlinsert > resources > limits > cpu	Mandatory	CPU limit for vlinsert pods Default value: 500m
victoria_logs_cluster > vlselect > replicas	Mandatory	Number of vlselect pod replicas Default value: 2
victoria_logs_cluster > vlselect > resources > requests > memory	Mandatory	Memory request for vlselect pods Default value: 256Mi
victoria_logs_cluster > vlselect > resources > requests > cpu	Mandatory	CPU request for vlselect pods Default value: 100m
victoria_logs_cluster > vlselect > resources > limits > memory	Mandatory	Memory limit for vlselect pods Default value: 512Mi
victoria_logs_cluster > vlselect > resources > limits > cpu	Mandatory	CPU limit for vlselect pods Default value: 500m
victoria_logs_cluster > vlagent > replicas	Mandatory	Number of vlagent pod replicas Default value: 2
victoria_logs_cluster > vlagent > pvc_size	Mandatory	PVC size for vlagent pods Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 5Gi
victoria_logs_cluster > vlagent > resources > requests > memory	Mandatory	Memory request for vlagent pods Default value: 64Mi
victoria_logs_cluster > vlagent > resources > requests > cpu	Mandatory	CPU request for vlagent pods Default value: 25m
victoria_logs_cluster > vlagent > resources > limits > memory	Mandatory	Memory limit for vlagent pods Default value: 256Mi
victoria_logs_cluster > vlagent > resources > limits > cpu	Mandatory	CPU limit for vlagent pods Default value: 100m
vector > ldms > replicas	Mandatory	Number of Vector-LDMS pod replicas Default value: 2
vector > ldms > resources > requests > memory	Mandatory	Memory request for Vector-LDMS pods Default value: 128Mi
vector > ldms > resources > requests > cpu	Mandatory	CPU request for Vector-LDMS pods Default value: 50m
vector > ldms > resources > limits > memory	Mandatory	Memory limit for Vector-LDMS pods Default value: 256Mi
vector > ldms > resources > limits > cpu	Mandatory	CPU limit for Vector-LDMS pods Default value: 250m
vector > ome > replicas	Mandatory	Number of Vector-OME pod replicas Default value: 2
vector > ome > resources > requests > memory	Mandatory	Memory request for Vector-OME pods Default value: 256Mi
vector > ome > resources > requests > cpu	Mandatory	CPU request for Vector-OME pods Default value: 100m
vector > ome > resources > limits > memory	Mandatory	Memory limit for Vector-OME pods Default value: 512Mi
vector > ome > resources > limits > cpu	Mandatory	CPU limit for Vector-OME pods Default value: 500m
vector > vlagent_vector > replicas	Mandatory	Number of vlagent-vector pod replicas Default value: 2
vector > vlagent_vector > pvc_size	Mandatory	PVC size for vlagent-vector pods Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 5Gi
vector > vlagent_vector > resources > requests > memory	Mandatory	Memory request for vlagent-vector pods Default value: 128Mi
vector > vlagent_vector > resources > requests > cpu	Mandatory	CPU request for vlagent-vector pods Default value: 50m
vector > vlagent_vector > resources > limits > memory	Mandatory	Memory limit for vlagent-vector pods Default value: 256Mi
vector > vlagent_vector > resources > limits > cpu	Mandatory	CPU limit for vlagent-vector pods Default value: 250m
vector > vmagent_vector > replicas	Mandatory	Number of vmagent-vector pod replicas Default value: 2
vector > vmagent_vector > pvc_size	Mandatory	PVC size for vmagent-vector pods Accepted values: Must be specified in the form of X[Ki|Mi|Gi|Ti|Pi|Ei] Default value: 5Gi
vector > vmagent_vector > resources > requests > memory	Mandatory	Memory request for vmagent-vector pods Default value: 128Mi
vector > vmagent_vector > resources > requests > cpu	Mandatory	CPU request for vmagent-vector pods Default value: 50m
vector > vmagent_vector > resources > limits > memory	Mandatory	Memory limit for vmagent-vector pods Default value: 256Mi
vector > vmagent_vector > resources > limits > cpu	Mandatory	CPU limit for vmagent-vector pods Default value: 250m
csi_volume_exporter > resources > requests > cpu	Mandatory	CPU request for CSI Volume Exporter pods Default value: 50m
csi_volume_exporter > resources > requests > memory	Mandatory	Memory request for CSI Volume Exporter pods Default value: 64Mi
csi_volume_exporter > resources > limits > cpu	Mandatory	CPU limit for CSI Volume Exporter pods Default value: 200m
csi_volume_exporter > resources > limits > memory	Mandatory	Memory limit for CSI Volume Exporter pods Default value: 256Mi
csm_metrics_powerscale_resources > requests > cpu	Mandatory	CPU request for CSM Metrics PowerScale pods Default value: 100m
csm_metrics_powerscale_resources > requests > memory	Mandatory	Memory request for CSM Metrics PowerScale pods Default value: 128Mi
csm_metrics_powerscale_resources > limits > cpu	Mandatory	CPU limit for CSM Metrics PowerScale pods Default value: 500m
csm_metrics_powerscale_resources > limits > memory	Mandatory	Memory limit for CSM Metrics PowerScale pods Default value: 512Mi

GitLab Configuration

gitlab_config.yml

Parameter	Mandatory/Optional	Description
gitlab_host	Mandatory	IP address of the target host where GitLab will be deployed. Must be accessible from the OIM server.
gitlab_project_name	Mandatory	Name of the GitLab project that Omnia creates or manage. Default value: omnia-catalog This project is created automatically if it does not exist.
gitlab_project_visibility	Mandatory	Visibility options that you can set for the GitLab project. Possible Values: private: Project access must be granted explicitly for each user internal: The project can be cloned by any logged‑in user public: The project can be cloned without any authentication
gitlab_default_branch	Mandatory	The default branch used for repository and API operations Default value: main This branch is used as the default for all operations
gitlab_https_port	Mandatory	HTTPS port exposed via GitLab NGINX Default value: 443 Must be between 1-65535 Must not conflict with other services
gitlab_min_storage_gb	Mandatory	Free disk space validated before install Default value: 20 GitLab requires at least 20GB of free disk space
gitlab_min_cpu_cores	Mandatory	Minimum CPU core count validated before install Default value: 2 More cores may be needed for production workloads
gitlab_puma_workers	Mandatory	Number of worker processes Default value: 2 Scale with CPU cores (recommended: 1-2 workers per CPU core)
gitlab_sidekiq_concurrency	Mandatory	Background job concurrency Default value: 10 Adjust based on available memory and workload

If you have any feedback about Omnia documentation, please reach out at omnia.readme@dell.com.