origo
  1. Home
  2. /
  3. Origo OS
  4. /
  5. Infrastructure Services

Infrastructure Services

Out-of-the-box Origo OS can function as a private cloud replacing e.g. VMware or Hyper-V. This is great if your organization simply wants to run Windows or Linux VMs. Origo OS can also be “linked” to the Origo Registry and gain access to various infrastructure services like e.g. DNS services and a catalog of pre-configured virtual appliances (called Stacks) that deliver services like database services or Kubernetes. This can be combined with the Origo Public Cloud Toolkit for extremely easy access to setting up a public cloud offering.

Origo OS and Origo Infrastructure Services are free to use for non-commercial entities and if you run Origo OS on 8 physical cores or less.

Commercial entities must have a hosting agreement and in turn get access to a number of commercial services.

Below is a short description of the services an Engine gets access to when linked to the registry.

  • DNS services: Origo makes DNS services avaible for both engines running Origo OS and VMs running the Public Cloud Toolkit through the Origo DNS API. VMs in Origo OS with external ip addresses get access to registrering DNS entries in the uncloud.co, uncloud.dk or stabile.io zones. Every VM you provision in a linked Origo OS installation using one of the stacks from the registry, automatically registers a DNS A-record in the default zone of the client’s choice and aquires a TLS-certificate using Let’s Encrypt. Clients may import their own DNS zones and use these. The Public Cloud Toolkit provides a UI for managing DNS zones.
  • Metered usage services: Every Engine running Origo OS collects detailed data for CPU, memory, storage, network and GPU usage. When an engine is linked to the Origo Registry, this data is exposed in a consolidated manner through the Origo Billing API. This is used by the invoicing services and the billing services.
  • User registration services: The Registry provides a sign-up and registration flow for users signing up to use a customer’s collection of linked Engines. This flow is leveraged by the public cloud toolkit to provide a seamless sign-up experience for end-users.
  • Invoicing services: Customers with a hosting agreement that have external clients can optionally use the invoicing services to give their clients access to invoices through self-services and send out monthly invoices specifying usage and cost.
  • Billing services: Customers with a hosting agreement that have external clients can optionally use the billing services to charge their clients each month for their usage. If payment is not succesful, the services can optionally send out notices, suspend client’s accountsm etc. Currently Stripe is used as the processing backend.
  • Engine reporting and status services: Every linked Engine reports a detailed status to the registry, including details about VMs and services for each user, status for backups, monitoring, etc. This data is exposed through the Origo Reporting API. The public cloud toolkit use this to generate the UI that clients use to manage their services and virtual infrastructure.
  • User authentication, authorization and synchronization services: The Registry provides centralized authentication and authorization services for a customer’s linked engines through the Origo User API. This is achieved by synchronizing user account data across linked engines. This is used by the public cloud toolkit to allow centralized management of ressources across linked engines.
  • Basic monitoring services: Monitoring data is collected from linked Engines and exposed in a consolidated manner through the Origo Monitoring API. This is leveraged by the public cloud toolkit.
  • Docker registry services: The Kubernetes services provided by e.g. the Kubernetes Stack depend on the Docker registry provided by Origo Infrastructure Services for various functions like bare metal networking, storage classes, etc.
  • Stack registry services: A curated catalog of Stacks (services) which linked Engines can download and install. Engines get access to this catalog through the Origo Registry API.
  • Shared image storage services: Every Stack provided by the Stack Registry is backed by one or several images. When a Stack is installed these are downloaded from the shared image storage services.