Skip to main content

Getting started

OSISM is a solution for the holistic management of sustainable, sovereign software-defined cloud infrastructures. It provides a solid and stable base for the deployment and operation cloud infrastructures, for public cloud data centres and, at the edge, for distributed systems. It is also suitable for building supercomputers and HPC environments. OSISM enables fast, easy and consistent management and provisioning of compute, storage and network resources to run cloud-native applications.

The documentation is organised into guides:

  • The Concept Guide explains which components and modules make up OSISM. It also explains the use cases.
  • The Deploy Guide explains how the nodes of a cluster are created and bootstrapped. It also explains how the individual modules can be deployed.
  • The Upgrade Guide explains how the individual modules can be upgraded.
  • The Configuration Guide explains how the individual modules can be configured.
  • The Operations Guide explains how individual tasks can be done in day-to-day business in a running cluster.
  • The Troubleshooting Guide explains how to resolve problems. It is an extension of the Operations Guide.
  • The User Guide is intended for users of the individual components. It contains best practices, as well as other information.

Required knowledge​

We try to make deployment, upgrade, day2 operations etc. as easy as possible for everyone to use. However, knowledge is still required that we do not cover in our documentation. Wherever possible, we try to refer to existing documentation from e.g. Ansible or Docker.

If you are not sure whether you already have the required knowledge, need support in gaining the knowledge or would like a guided introduction, you are welcome to contact us at info@osism.tech. We are happy to help.

  • We assume that the reader is well familiar with Linux (LPIC2 level).
  • We assume that the reader has understood the basic concepts of Ansible and can use Ansible in a basic way.
  • We assume that the reader has understood the basic concepts of Docker and can use Docker in a basic way.
  • We assume that the reader has understood the basic concepts of Kubernetes and can use Kubernetes in a basic way.