The O-Cloud Manager is an implementation of the O-RAN O2 IMS API on top of OpenShift and Advanced Cluster Management (ACM). It provides lifecycle management for O-Cloud infrastructure, including bare-metal server inventory, cluster provisioning and configuration, firmware management, and alarm monitoring — all exposed through O-RAN compliant REST APIs.
The typical workflow for deploying and managing clusters with the O-Cloud Manager is:
- Setup — Install prerequisites, deploy the operator, prepare the GitOps repository, onboard bare-metal servers, and define cluster templates.
- Provision — Create a ProvisioningRequest to allocate hardware, apply firmware settings, and install a cluster.
- Operate — Perform Day-2 configuration changes, firmware updates, and cluster upgrades on running clusters.
- Monitor — Use the O2 IMS REST APIs to query inventory, track cluster status, and monitor alarms.
- Prerequisites
- Environment Setup
- GitOps Repository Layout and Setup
- Server Onboarding
- Template Overview
- API Overview — authentication, filtering, field selection
- Inventory API — locations, sites, pools, resources
- Cluster API — node clusters, cluster resources
- Alarms API
See CONTRIBUTING.md for development workflow, testing requirements, and pull request guidelines.
This repo uses submodules to pull in konflux scripts from another repo. The hack/update_deps.sh script, which is called from various Makefile targets,
includes a call to git submodules update to ensure submodules are downloaded and up to date automatically in the designer workflow.
If you want to skip running the update command, if you're working on something related to submodules for example, set SKIP_SUBMODULES_SYNC to yes on the make command-line, such as:
$ make SKIP_SUBMODULE_SYNC=yes ci-job
Update dependencies
hack/update_deps.sh
Skipping submodule sync
hack/install_test_deps.sh
...