Hyper Open Edge Cloud

How to Install OS and Services on Rapid Space Server for a Partner

How a partner must install the OS and services on servers to become Rapid.Space hosting servers.
  • Last Update:2021-05-31
  • Version:002
  • Language:en

Here is the procedure to install a OCP server that will be used as Rapid.Space hosting server.

1. Install OS

Recommended OS is Debian 10. Debian 9 is also supported. You should follow rapidspace-HowTo.Partner.Server.OS.Installation to install the OS.

Install the OS on the small SSD disk so that the big SSD disk can be used totally by the Rapid.Space VM.

2. Install Production re6st

wget https://deploy.erp5.net/re6st
bash re6st

In order to install production re6st, you will need to be given a prodution token. The Rapid.Space team will provide you an one time Re6st token, unique for a server.

(In case you want to have a free re6stnet on your own PC instead of the OCP servers, you can follow rapidspace-HowTo.Use.SDN.For.A.Single.Server)

3. Install SlapOS

wget https://deploy.erp5.net/vifib
bash vifib

In order to install slapos, you will need to be given a token. The Rapid.Space team will provide you an one time SlapOS Token, unique for a server.

Please note that this script will also install a cron called "upgrader" to upgrade the machine regularly. It will also install the SSH public keys of all the vifib team in root account so that the team can SSH into your server.

Now reboot the server:


When the server will be back ensure that KVM is allowed in nested mode by:

grep -q 'Y\|1' /sys/module/kvm_*/parameters/nested && echo "KVM nested OK" || echo "KVM nested ERROR"

Which shall return

KVM nested OK

4. Set the disk to be used by the VM

Locate the big SSD disk with using lsblk:

lsblk -pd -e 11

The example output is:

/dev/sda   8:0    0   3.5T  0 disk
/dev/sdb   8:16   0 223.6G  0 disk

From this output one can see that /dev/sda is the big disk.

Allow usage of that disk by appending to the /etc/opt/slapos/slapos.cfg:

allowed-disk-for-vm = /dev/sda

Link the disk in the configuration:

ln -sf /dev/sda /dev/disk/disk-path-for-vm

This will result in using this disk for VM instantiated the server.

Make the link persist on reboot by:

echo "@reboot root ln -sf /dev/sda /dev/disk/disk-path-for-vm" > /etc/cron.d/link-disk-path-for-vm

5. Do the stress test

Before putting the machine in the cloud, the stress testing has to be done.

Install stress-ng:

apt -y install stress-ng

Run in for 24 hours:

nohup stress-ng --cpu 60 --timeout 24h </dev/null >/dev/null 2>&1 &

6. Add the machine to SlapOS Cloud by Rapid.Space administrator

Ask the rapid.space administrator to perform those steps.


Locate the server created in 3. Install SlapOS, remember it's reference (COMP-XXX).

Login as "rapid.space" user in https://vifib.erp5.net/ and locate the computer by its reference, then:

  • in Capacity tab set Capacity to 40
  • in Model tab set Network to proper network

Login as "rapid.space" user in https://slapos.vifib.com/ and locate the computer by its reference, then

  • set Monitoring: Enabled
  • set Upgrade: Auto Upgrade
  • set Allocation Scope: Open for Subscribers Only
  • by using Supply
    • install the <KRV>
  • by using Transfer:
    • set Future Location: <DHC>
    • Future Project: Rapid Space Computers