Page Content

When we want to make sure a datacenter is in good shape, the providers of the machines and the RapidSpace administrator must work together to do this whole list of checks :

Make sure the IP of each machine is statically set

Provider need to make sure that the interfaces are configured in static mode in /etc/network/interfaces.

Provider should also make sure that no DHCP client is running by making sure "ps aux | grep dhc" is returning nothing.

TODO: Provider must send to RapidSpace administrator the output of "cat /etc/network/interfaces ; ps aux | grep dhc" for EACH machine in the rack.

Make sure that network latency is good

Provider need to make sure the matency is correct in IPv4 and in IPv6 with re6st.

TODO: Provider must send to RapidSpace administrator the output of "ping -c 4 google.com ; ping6 -c 4 slap.vifib.com" for at least a machine in the network.

Make sure re6st is correctly configured

The re6st configuration file should contain "interface <INTERFACE>" with <INTERFACE> being the interface connected to the other machines of the rack.

TODO: Provider must send to RapidSpace administrator the output of "cat /etc/re6stnet/re6stnet.conf ; ip -6 r" for all machines in the network.

Make sure slapos is correctly configured

Generic

The slapos configuration must contain a section "manager:devperm" and it should have a manager_list in the section "slapos" like this:

[manager:devperm]
allowed-disk-for-vm = /dev/sdb


[slapos]
[...]
manager_list = devperm,prerm

The slapos configuration should also contain the section "networkcache" properly configured like this:

[networkcache]
[...]
download-from-binary-cache-force-url-list =
  https://lab.nexedi.com/nexedi/slapos/raw/1.0.
  https://lab.node.vifib.com/nexedi/slapos/raw/1.0.

VPS.Brute on Capri servers

If the machine is Capri server which shall hold VPS brute configuration you can use deploy script like:

rm -f rapid.space-vps-brute-capri ; wget https://deploy.erp5.net/rapid.space-vps-brute-capri ; bash rapid.space-vps-brute-capri

This will automatically configure /etc/opt/slapos/slapos.cfg.

Make sure kvm software release is supplied in all the machines

RapidSpace administrator must make sure that all the machines in the datacenter have the latest version of KVM software release supplied.

Follow 6. Add the machine to SlapOS Cloud by Rapid.Space administrator of rapidspace-HowTo.Partner.Setup.Server.Installation.

Make sure the machines are correctly configured in SlapOS master

The machines should have capacity set to 40. Their allocation scope should be Open/Subscription.