OSISM is a comprehensive platform for managing software-defined cloud infrastructure that goes far beyond being a simple deployment tool for OpenStack. While OSISM does support the deployment and management of OpenStack as a key component, its capabilities extend to orchestrating a wide array of services and tools needed to build and operate a modern private cloud. By leveraging OSISM, organizations gain a powerful toolset for building, managing, and scaling private cloud infrastructures tailored to their specific needs, while also maintaining full control over their data and operations.
OSISM is used by the Sovereign Cloud Stack (SCS) to manage the core infrastructure services. OSISM is SCS compliant.
OSISM is made up of many individual components. Most modules can also be used independently of each other.
- Infrastructure as a Service (IaaS) with OpenStack
- Software Defined Storage (SDS) with Ceph
- Bare Metal as a Service (BMaaS) with Ironic
- Software Defined Networking (SDN) with SONiC & OVN
- Kubernetes (K8s) with K3S
- Kubernetes as a Service (KaaS) with Gardener
- Kubernetes as a Service (KaaS) with Cluster API
- Identity & Access Management with Keycloak
- Privileged Access Management (PAM) to all infrastructure with Teleport
- Logging, Monitoring & Telemetry with Prometheus & Grafana
- Realtime insights with Netdata
The documentation can be found at osism.tech. The associated repository is osism/osism.github.io.
If you have found a bug, a feature is missing or you have a question just open a bug in osism/issues. We will then move it to the right place and assign it as soon as possible.
On Matrix we are available via #osism for problems, suggestions, feedback etc. around OSISM. We are also happy to discuss topics like OpenStack, Ceph, and Ansible in general.
Contributions are welcome, and they are greatly appreciated. Open Source Software lives from contributions.
