i26g Infrastructure Adapters

What They Are

The i26g Control Plane is being developed to manage the application’s VMs, networks, and volumes within a supplied boundary, with optional capabilities such as DNS and snapshots. It does that through a small, published interface — and the i26g Infrastructure Adapters are what implement that interface for each kind of infrastructure.

They cover virtualization on your own hardware, rented and cloud machines, and DNS, whether it is a local DNS server, part of your VPS or cloud provider, or a separate service.

Like the control plane, the infrastructure adapters are in early development. The capabilities and rules below describe the intended design. Supported providers will be listed with each release.

Why They Are Separate

The adapters are delivered as part of i26g, but not built into the control plane:

• They are released as a versioned set, tested against each control plane release, with a compatibility statement for each.
• You pin them. Your boundary declaration names the adapter set and its version, so you always know exactly which code acts on your infrastructure.
• The control plane verifies them at startup — the set’s integrity, its locked provider dependencies, and the interface version — and refuses to start if integrity or dependency verification fails, or an adapter declares an unsupported interface version.
• You decide on upgrades. The control plane can propose a newer set; changing the pinned version is your change to make.

Separate releases let adapters receive fixes and support new providers without requiring a control-plane release.

Capabilities and Testing

Every adapter must pass conformance tests before release. These exercise each required capability and each optional capability it declares, checking resource operations and results against the published contract.

The capabilities are split into required ones — creating VMs, a network within the supplied zone, and volumes within the supplied storage, and listing what exists — and optional ones, such as snapshots, DNS, and additional networks, which the control plane uses when an adapter provides them.

The Interface Between i26g and Your Infrastructure describes the interface and the adapters in detail.

Your Provider Is Not Listed

A provider outside the set needs an adapter that passes the same conformance tests. You can write one yourself, or i26g Custom Development can build it for the infrastructure you use.