Ai-OPs
ai-ops.com
Docs
/
Installation
/

Installation Overview

Installation Overview

This section takes you from nothing to a running, licensed Koios server. It assumes no prior experience with Linux, Docker, or virtual machines — every command you need is written out.

Koios runs on an Ubuntu Server machine, either a virtual machine on a hypervisor you already have or a physical computer. All of Koios runs inside a single container on that machine, and you administer it from a browser on your own computer. Nothing is installed on the machines your operators use.

Before You Start

Gather these four things. Two of them come from someone else, so ask early:

WhatWhere it comes from
A license keyYour Ai-OPs representative
A static IP address, gateway, and subnet maskWhoever runs your network. You are asked for these partway through the Ubuntu install, so have them before you start
A machine, or the ability to create a virtual machineSee Choosing a Host
The Ubuntu Server installer imageA free download from Ubuntu. Covered in Installing Ubuntu

Record your network settings

Enter them here once and every command in this section shows your values instead of placeholders. They are kept in this browser only.

Use your own values

Enter your settings and the commands throughout the installation pages will show them instead of placeholders. They stay in this browser — nothing is sent anywhere, and nothing is saved to Koios.

Two Decisions

Make both before you begin. They change which pages you read.

Virtual machine or physical computer?

A virtual machine is the usual choice, and Hyper-V is our recommendation if you have Windows Server. A physical computer — including a small industrial PC — is equally supported and is often the better answer at a small site or on a plant floor. Choosing a Host covers both and explains what differs.

Does the machine have internet access?

SituationWhat changes
Has internet accessDocker and the Koios image download directly. Follow the path below as written
No internet accessRead Installing Without Internet Access first. The easiest route is to build the machine somewhere with internet and carry its virtual disk to the site — it changes the order of everything below

The Path

Follow these in order. Times are rough, and most of the total is unattended downloading.

StepPageWhat it doesTime
1System RequirementsConfirm the machine is big enough5 min
2Choosing a HostDecide where Koios will run5 min
3Creating the Virtual MachineHyper-V only. Skip on a physical machine15 min
4Installing UbuntuInstall the operating system, set its address, enable remote access20 min
5Network ConfigurationConfirm the address, open the ports10 min
6Time SynchronizationKeep the clock accurate5 min
7Installing Docker EngineInstall the runtime Koios needs10 min
8Getting the Koios ImageDownload Koios itself15 min
9Running Koios as a ServiceMake Koios start on boot and stay running10 min
10Licensing KoiosActivate your license10 min

Steps 1 through 6 are ordinary Ubuntu setup, unrelated to Koios. If you already have an Ubuntu machine with a static address, start at step 7.

A hypervisor console window has no copy and paste, so everything typed there is typed by hand. That is why step 4 sets the machine's address and installs an SSH server: from there on you work from your own computer and paste commands instead of retyping them.

What You End Up With

  • Koios reachable at https://<the static address you chose> from any browser on the network
  • A login of admin / koios, which you change immediately
  • Koios restarting by itself after a crash or a power cut, with no one logged in
  • All data held outside the container, so updating Koios never puts it at risk

No Internet on the Machine?

Installing Without Internet Access covers both routes: preparing a virtual disk on a connected computer, which is the one to prefer, and transferring the files by hand.

If Something Goes Wrong

If the Install Goes Wrong collects the failures that actually come up — ports already in use, an image that will not run, a machine that takes two minutes to boot — with the cause and the fix for each.

What's Next