For cloud providers

CloudRING is being built for providers who want to run their own cloud on their own hardware without writing a control plane from scratch.

What it’s meant to give you

• A reusable platform: identity, tenancy, IAM, orders, quota, metering, and one API, CLI and portal.
• A way to offer your own services next to the ones from the project and from independent teams, all through OCSv3.
• Control over your deployment. You decide which modules to admit, and your commercial terms, capacity, customer commitments and legal compliance stay yours.
• Later on, opt-in federation with other providers that never hands over root authority.

How far along it is

The latest prerelease includes a development installer built to bring up one empty provider in a single VM, and its live acceptance checks haven’t passed yet. The repository also has site inventory and installation contracts, but open issues block a supported independent installation. The first production-grade goal, a highly available installation of an empty provider, is roadmap goal G02. CloudRING isn’t ready to serve real customers.

One-engineer operations (G22)

Roadmap goal G22 aims to show that one trained engineer can run the whole platform in normal conditions. The plan: one operator console and CLI for the whole platform, guided and reversible repair, and a measured workload budget that has to hold over a 14-day campaign with an independent walkthrough.

Get involved

If you run infrastructure and want to shape how CloudRING installs, operates and connects to a provider’s hardware, open an issue. The provider adapter model and the site installation contract are good places to start reading.