STEELDOME TECHNOLOGIES

STRATISYSTEM API GUIDE

API guide for StratiSTOR, StratiSERV, and HyperSERV.

STRATISYSTEM OS — API AND SDK REFERENCE

Unified Infrastructure Management. Open Integration. Programmable Operations.

StratiSYSTEM OS provides a comprehensive set of application programming interfaces (APIs), software development resources, and command-line interfaces that enable administrators, developers, managed service providers, and technology partners to automate, integrate, and extend infrastructure operations.

The primary interface for infrastructure management and automation is the StratiSYSTEM Cluster REST API. Additional component-level interfaces provide access to underlying storage, virtualization, container orchestration, and compatible cloud infrastructure technologies.

Together, these interfaces provide a flexible foundation for infrastructure automation, external management platforms, application integration, custom service delivery, and programmatic infrastructure operations.

One operating system. Open interfaces. Infinite integration possibilities.

API ARCHITECTURE AND INTEGRATION OVERVIEW

StratiSYSTEM exposes infrastructure capabilities through multiple management and integration layers. Each interface serves a distinct purpose, ranging from unified cluster administration to specialized component-level operations and application integration.

API or Interface Interface Type Primary Function
StratiSYSTEM Cluster API REST / JSON Primary infrastructure management, automation, monitoring, provisioning, and cluster operations.
Clustered Storage Service API REST, CLI, Native Libraries Component-level management of distributed storage clusters, pools, storage services, and performance metrics.
Virtual Machine Hypervisor API Native API, RPC, CLI Low-level QEMU/KVM virtualization management through libvirt.
Kubernetes API REST / JSON Container orchestration, application deployment, service management, and Kubernetes resource administration.
S3-Compatible Object Storage API HTTP / HTTPS Application-level access to compatible object storage services, buckets, objects, and associated metadata.
OpenStack APIs REST / JSON External cloud infrastructure orchestration and integration where compatible OpenStack services are deployed.

STRATISYSTEM CLUSTER API (REST)

The StratiSYSTEM Cluster REST API is the primary programmatic management interface for the StratiSYSTEM infrastructure operating system. It provides a unified interface for managing compute, storage, networking, virtualization, and infrastructure orchestration across SteelDome-powered environments.

The API enables administrators, developers, and technology partners to interact programmatically with infrastructure resources and integrate StratiSYSTEM capabilities into external management platforms, automation frameworks, service portals, and operational toolchains.

Rather than requiring integrations to communicate independently with the underlying infrastructure components, the StratiSYSTEM Cluster REST API provides a consistent management layer across supported StratiSTOR, StratiSERV, and HyperSERV environments.

API Characteristics

Purpose Unified infrastructure management, provisioning, automation, monitoring, and third-party integration.
API Interface RESTful API utilizing HTTP-based requests and JSON-formatted information.
Management Scope Supported StratiSYSTEM infrastructure resources, cluster services, storage, virtualization, networking, and operational workflows.
Integration Methods REST clients, SDK resources, scripting languages, automation frameworks, and custom applications.
Applicable Platforms StratiSTOR, StratiSERV, and HyperSERV, subject to the installed platform configuration and supported API capabilities.

Typical Infrastructure Operations

Depending on the installed platform, software release, and available API endpoints, the StratiSYSTEM Cluster REST API supports infrastructure operations across the following functional areas:

Enterprise and Partner Integration Opportunities

The StratiSYSTEM Cluster REST API provides a programmable infrastructure foundation for developing custom integrations and extending existing enterprise management ecosystems.

Integration Category Typical Use Cases
Infrastructure Automation Automated provisioning, resource configuration, workload deployment, and repeatable infrastructure operations.
Managed Service Provider Platforms Provider-specific operational workflows, customer infrastructure provisioning, and managed service delivery integrations.
Customer Self-Service Portals Custom interfaces for authorized resource provisioning, workload administration, infrastructure visibility, and service management.
Infrastructure as Code (IaC) Integration with custom deployment frameworks, configuration management systems, and declarative infrastructure workflows.
Monitoring and Observability External monitoring platforms, operational dashboards, resource inventory systems, and capacity planning applications.
ITSM, PSA, and RMM Custom integration with IT service management, professional services automation, remote monitoring, and infrastructure support platforms.
Data Protection and Recovery Integration of supported protection and recovery operations into external business continuity and operational automation workflows.
Custom Application Development Development of specialized infrastructure management applications, technology partner integrations, and custom operational services.

StratiSYSTEM API and SDK Documentation

The StratiSYSTEM API and SDK Guide provides the authoritative reference for available API endpoints, authentication requirements, request parameters, response structures, supported operations, and integration examples.

STRATISYSTEM API AND SDK GUIDE

Access the official SteelDome API and software development documentation for programmatic infrastructure management and third-party integration.

Open the StratiSYSTEM API and SDK Guide (PDF)

CLUSTERED STORAGE SERVICE API (REST)

StratiSTOR incorporates Ceph-based distributed storage technologies to deliver scalable, resilient block, file, and object storage services. The underlying Ceph infrastructure exposes management APIs, command-line tools, and native client libraries that provide specialized access to distributed storage resources and cluster operations.

The Ceph Dashboard REST API, provided by the Ceph Manager Dashboard module when enabled, provides programmatic access to supported storage management and monitoring functions. Additional interfaces provide access to individual storage services and specialized administrative capabilities.

API Characteristics

Purpose Distributed storage administration, resource management, monitoring, and specialized storage integration.
API Interface Ceph Manager Dashboard REST API, administrative command-line tools, native client libraries, and storage-specific interfaces.
Storage Services RADOS, RADOS Block Device (RBD), Ceph File System (CephFS), and RADOS Gateway (RGW).
Administrative Tools ceph, rados, rbd, radosgw-admin, and CephFS administrative commands.
Native Libraries librados, librbd, and libcephfs, with available language bindings.

Typical Storage Operations

Storage Management and Data Access Interfaces

Storage management interfaces and application-level data access interfaces serve different purposes. The Ceph management API is intended for administrative operations, while applications access storage through the appropriate block, file, object, or native client interfaces.

Storage Service Interface Typical Application
Cluster Administration Ceph REST API and CLI Storage management, monitoring, and administrative operations.
Native Object Storage RADOS / librados Specialized native access to the distributed object storage layer.
Block Storage RBD, librbd, iSCSI, NVMe/TCP Virtual machine disks, databases, application volumes, and compatible external block storage consumers.
File Storage CephFS, SMB, NFS Shared filesystems, enterprise file services, application data, and collaborative storage.
Object Storage S3-compatible REST API through RGW Application objects, content repositories, backup targets, data lakes, and archival storage.

IMPORTANT

Direct administrative changes through native Ceph APIs and command-line interfaces can bypass StratiSYSTEM validation, cluster coordination, configuration management, and operational workflows. Use supported StratiSYSTEM management interfaces for managed storage changes. Use native interfaces for specialized diagnostics or documented administrative procedures only when their impact on the managed infrastructure is understood.

API Documentation and Developer Resources

VIRTUAL MACHINE HYPERVISOR API (LIBVIRT)

StratiSERV and HyperSERV utilize QEMU/KVM virtualization technologies to provide enterprise-grade virtual machine infrastructure. The underlying virtualization management layer incorporates libvirt, an established virtualization management API and supporting software ecosystem.

libvirt exposes a native C-based API, remote management capabilities, command-line interfaces, and language bindings that enable specialized access to virtual machine lifecycle operations, virtual hardware configuration, storage, networking, and resource monitoring.

Although libvirt supports multiple virtualization technologies, the relevant virtualization driver for StratiSERV and HyperSERV is QEMU/KVM. Support for other hypervisors within the libvirt project does not imply that those hypervisors are supported by StratiSYSTEM.

API Characteristics

Purpose Component-level management of QEMU/KVM virtual machines and associated virtualization resources.
API Interface Native libvirt API, remote procedure call (RPC) interfaces, command-line utilities, and language bindings.
Virtualization Technology QEMU with Kernel-based Virtual Machine (KVM) hardware acceleration.
Management Services The libvirt daemon architecture depends on the installed software release and configuration. Modular deployments use virtqemud for QEMU management and other service-specific daemons as required; monolithic deployments use libvirtd.
Command-Line Interface virsh and associated virtualization management utilities.
Language Bindings C, Python, Go, and other available libvirt language bindings.
Configuration Format XML-based definitions for virtual machines, virtual devices, storage, networking, and associated virtualization resources.

Typical Virtualization Operations

IMPORTANT

Direct modifications through libvirt, virsh, QEMU management interfaces, or virtual machine XML definitions can bypass StratiSYSTEM cluster coordination, configuration management, workload protection policies, and high-availability workflows. Use supported StratiSYSTEM management interfaces for virtual machine provisioning, configuration, migration, snapshots, backup, and recovery. Use component-level interfaces for specialized diagnostics or documented administrative procedures.

API Documentation and Developer Resources

KUBERNETES API (REST)

Kubernetes provides a declarative, RESTful application programming interface for managing containerized workloads, application services, persistent storage, configuration resources, and distributed application environments.

Within compatible Kubernetes deployments operating on StratiSYSTEM-powered infrastructure, the Kubernetes API serves as the primary interface for container orchestration and application-level resource management.

The API enables administrators, developers, operators, and automated controllers to create, retrieve, update, watch, and delete Kubernetes resources. Kubernetes controllers continuously reconcile the desired state defined through the API with the actual state of the application environment.

API Characteristics

Purpose Declarative deployment, scaling, orchestration, and management of containerized applications.
API Interface RESTful Kubernetes API exposed through kube-apiserver.
Management Model Declarative resource definitions, controllers, reconciliation loops, and desired-state management.
Command-Line Interface kubectl and compatible Kubernetes management tools.
Configuration Format JSON-based API resources, commonly authored and managed using YAML manifests.
Extensibility Custom Resource Definitions (CRDs), operators, custom controllers, admission webhooks, and aggregated APIs.

Typical Kubernetes Operations

Functional Area Supported Kubernetes Operations
Workload Management Create and manage Pods, Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs.
Service Discovery and Networking Manage Services, Ingress resources, compatible Gateway API resources, and NetworkPolicies, subject to installed networking components.
Persistent Storage Create and manage PersistentVolumes (PVs), PersistentVolumeClaims (PVCs), StorageClasses, and supported storage snapshot resources.
Storage Provisioning Integrate compatible Container Storage Interface (CSI) drivers for dynamic volume provisioning and application storage lifecycle management.
Configuration and Secrets Manage ConfigMaps, Secrets, application configuration, and supported workload environment definitions.
Application Scaling Manage replica counts and HorizontalPodAutoscaler resources where appropriate metrics services are available.
Application Resilience Utilize controllers, health probes, restart policies, scheduling mechanisms, and desired-state reconciliation to support application recovery.
Resource Governance Manage Namespaces, ResourceQuotas, LimitRanges, resource requests, and resource limits.
Monitoring and Logging Integrate compatible monitoring, metrics, and logging platforms such as Prometheus, Grafana, and Elasticsearch-based logging ecosystems.
Role-Based Access Control (RBAC) Manage Roles, ClusterRoles, RoleBindings, ClusterRoleBindings, and ServiceAccounts.
Custom Resources and Operators Extend Kubernetes through CustomResourceDefinitions, compatible operators, and specialized application controllers.
Accelerated Workloads Schedule supported accelerator-enabled applications through compatible device plugins, hardware resources, and workload configurations.

Integration with StratiSYSTEM Infrastructure

The StratiSYSTEM Cluster REST API and Kubernetes API operate at complementary management layers. StratiSYSTEM manages the underlying infrastructure resources, while Kubernetes manages the lifecycle and desired state of applications within its orchestration environment.

RECOMMENDED PRACTICE

Use the StratiSYSTEM Cluster REST API for supported infrastructure-level operations and the Kubernetes API for Kubernetes application resources. Access to Kubernetes APIs should be governed through appropriate authentication, least-privilege RBAC, service account permissions, and network security controls.

API Documentation and Developer Resources

S3-COMPATIBLE OBJECT STORAGE API (REST)

StratiSTOR and HyperSERV can provide S3-compatible object storage services through Ceph RADOS Gateway (RGW). The S3-compatible API enables applications to interact directly with object storage resources using established HTTP-based object storage interfaces.

Unlike infrastructure management APIs, which are primarily intended for administrators and automation platforms, the S3-compatible API provides application-level access to stored objects and associated storage resources.

API Characteristics

Purpose Application-level access to distributed object storage services.
API Interface S3-compatible REST API over HTTP or HTTPS.
Storage Gateway Ceph RADOS Gateway (RGW).
Authentication Supported S3 access credentials, request signing mechanisms, and applicable access policies.
Client Integration Compatible S3 SDKs, object storage applications, command-line clients, backup platforms, and custom applications.

Typical Object Storage Operations

IMPORTANT

S3 compatibility does not imply complete feature equivalence with every Amazon S3 service or API extension. Application integrations should be validated against the S3 operations and capabilities supported by the installed Ceph RADOS Gateway release and StratiSYSTEM configuration.

API Documentation and Developer Resources

OPENSTACK API INTEGRATION (REST)

OpenStack provides a modular collection of cloud infrastructure services and RESTful APIs for managing compute, networking, block storage, image repositories, identity, and infrastructure orchestration.

Where compatible OpenStack environments are deployed alongside SteelDome infrastructure, OpenStack APIs can provide an additional cloud management and orchestration layer for external application integration, private cloud services, and provider-specific infrastructure architectures.

OpenStack is an independent cloud infrastructure ecosystem. Its APIs complement rather than replace the native StratiSYSTEM Cluster REST API, and the availability of individual OpenStack services depends on the selected deployment architecture.

API Characteristics

Purpose Modular cloud infrastructure management, service orchestration, and cloud application integration.
API Interface Independent RESTful APIs exposed by individual OpenStack services.
Authentication OpenStack Identity service (Keystone), supported authentication tokens, roles, and project-scoped access policies.
Command-Line Interface OpenStackClient and applicable service-specific command-line utilities.
Developer Integration OpenStack SDKs, REST clients, compatible automation frameworks, and cloud orchestration applications.

OpenStack Services and APIs

Service Functional Area Typical Operations
Nova Compute Provision, start, stop, resize, migrate, and manage cloud compute instances.
Neutron Networking Manage virtual networks, subnets, routers, ports, floating IP addresses, and security groups.
Cinder Block Storage Create, attach, detach, extend, snapshot, and manage compatible block storage volumes.
Glance Image Management Upload, retrieve, catalog, and manage virtual machine images and associated metadata.
Keystone Identity and Authentication Manage users, groups, domains, projects, roles, authentication tokens, and service catalogs.
Heat Orchestration Deploy and manage infrastructure stacks through template-based orchestration.
Placement Resource Inventory and Allocation Track resource providers, inventories, allocations, and resource selection information.
Manila Shared File Services Provision and manage compatible shared filesystems, share access rules, and associated resources.
Swift Object Storage Manage object storage accounts, containers, objects, and associated metadata in compatible Swift environments.
Horizon Web Management Dashboard Provide graphical access to supported OpenStack services through their respective APIs. Horizon is a management application rather than a standalone infrastructure service API.

API Documentation and Developer Resources

SELECTING THE APPROPRIATE API

Selecting the appropriate interface is essential for maintaining operational consistency, infrastructure integrity, and clear management responsibilities. The preferred API depends on the resource being managed and the architectural layer responsible for that resource.

Required Operation Recommended Interface
Manage StratiSYSTEM infrastructure and cluster resources. StratiSYSTEM Cluster REST API
Automate supported virtual machine provisioning, migration, backup, and lifecycle operations exposed by the installed API release. StratiSYSTEM Cluster REST API
Provision and manage supported StratiSYSTEM storage services exposed by the installed API release. StratiSYSTEM Cluster REST API
Develop custom infrastructure management portals and external integrations. StratiSYSTEM Cluster REST API
Retrieve specialized Ceph storage diagnostics and component-level information. Ceph REST API or native administrative interfaces
Retrieve specialized virtual machine diagnostics or low-level virtualization information. libvirt API or supported virtualization utilities
Deploy and manage Kubernetes application workloads. Kubernetes API
Provision persistent storage for Kubernetes applications. Kubernetes API and compatible CSI integration
Upload, retrieve, and manage application objects. S3-Compatible Object Storage API
Manage resources owned by an independently deployed OpenStack cloud environment. Applicable OpenStack Service API

API SECURITY AND OPERATIONAL BEST PRACTICES

Programmatic infrastructure interfaces provide powerful administrative and operational capabilities. API integrations should be designed to maintain infrastructure security, configuration consistency, operational accountability, and predictable behavior during normal operations and failure conditions.

Authentication and Access Control

Transport Security and Network Access

Reliable Automation and Error Handling

API Versioning and Compatibility

StratiSYSTEM incorporates independently evolving infrastructure technologies. API capabilities, resource definitions, supported operations, authentication mechanisms, and response structures may vary between software releases.

IMPORTANT

The upstream component documentation referenced throughout this guide describes the capabilities of the respective open-source technologies. Not every upstream feature, API endpoint, configuration option, or administrative operation is necessarily exposed, enabled, validated, or supported within a particular StratiSYSTEM deployment. The official StratiSYSTEM API and SDK Guide and applicable SteelDome product documentation remain the authoritative references for supported SteelDome infrastructure operations.

UNIFIED INFRASTRUCTURE. OPEN INTEGRATION. PROGRAMMABLE OPERATIONS.

StratiSYSTEM is designed to provide organizations, developers, managed service providers, and technology partners with a programmable software-defined infrastructure foundation that can integrate into existing operational ecosystems and support the development of new infrastructure services.

By combining the unified StratiSYSTEM Cluster REST API with established storage, virtualization, container orchestration, and cloud integration technologies, SteelDome provides architectural flexibility without requiring organizations to surrender control over their automation strategies or application development environments.

Whether automating enterprise infrastructure, developing managed service offerings, integrating external applications, building custom management portals, or orchestrating modern cloud-native workloads, StratiSYSTEM provides a consistent foundation for extending infrastructure capabilities through documented and programmable interfaces.

Automate your infrastructure. Build your integrations. Extend without compromise.

One operating system. Infinite possibilities.

For official SteelDome API endpoint definitions, supported operations, authentication requirements, and developer integration guidance, refer to the StratiSYSTEM API and SDK Guide.