Skip to main content
Version: 1.3

Swift Deploy

Replace your CubeOS node with existing configuration policy.

Backup CubeOS Policies on the existing node#

Connect to root shell#

$ ssh [email protected]Warning: Permanently added '192.168.1.x' (ECDSA) to the list of known hosts.Password:

Backup the directory & files over root shell#

We need to backup the list of files below to a network storage or external drive.

  • /etc/policies/cubesys/cubesys1_0.yml
  • /etc/policies/network/network1_0.yml
  • /etc/policies/time/time1_0.yml

Installation with policies#

Prepare a NEW unconfigured CubeOS nodes.

[Optional] Setting IP address over KVM#

# ifconfig eth0 192.168.1.100 netmask 255.255.255.0 up

Copy policies to New node from your pc#

# scp -r policy [email protected]:~

Connect to root shell#

$ ssh [email protected]Warning: Permanently added '192.168.1.100' (ECDSA) to the list of known hosts.Password:

Check the policy files#

# ls -l /root/policytotal 12drwxr-xr-x 2 root root 4096 Aug  4 13:38 cubesysdrwxr-xr-x 2 root root 4096 Aug  4 13:38 networkdrwxr-xr-x 2 root root 4096 Aug  4 13:38 time
# ls -l /root/policy/cubesys/total 4-rw-r--r-- 1 root root 435 Aug  4 13:38 cubesys1_0.yml
# ls -l /root/policy/network/total 4-rw-r--r-- 1 root root 435 Aug  4 13:38 network1_0.yml
# ls -l /root/policy/time/total 4-rw-r--r-- 1 root root 435 Aug  4 13:38 time1_0.yml

[Important] Setting timezone#

Make sure timezone are synced with other CubeOS nodes

# hex_config timezone Asia/Taipei

[Important] Setting Time/date#

Make sure time/date are synced with other CubeOS nodes

# hex_config date '"2020-08-04 13:46:10"'

Create Marker files#

# touch /etc/appliance/state/sla_accepted# echo configured > /etc/appliance/state/configured

Apply policy#

# hex_config apply /root/policy
  • if this is a single node start, just run boot> cluster_sync
  • if this is a cluster start, wait until bootstrap_done is done in all nodes and run cluster> start to sync cluster data for all nodes
  • CubeOS self configuration on first time setup, run cluster> set_ready X, X is number(1~3) of storage data replication depend on your cluster stage
Last updated on by Roy Tan