Initial SSA Debian Install
Run the install-ssa script.
sudo su -c "bash <(wget -qO- https://apt.cloud.datacore.com/installssa/install-ssa.sh)" root
Run the script as root, so you can sudo su to switch to root.
datacore@demo00:~$ sudo su root@demo00:/home/datacore#
You may or may not need to enter a password here to switch to root depending on the permissions provided earlier when installing the system.
Installation is done via script. Please contact your Solutions Architect for the SNS code installation.
There are a few prechecks to accept.
It adds the apt repository, then installs the latest periferyssa package as shown in the example below.See the example output below: We're running as root great The detected os version is Description: Ubuntu 22.04.3 LTS checking for updates in apt Adding the public key for the apt repository Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). OK Adding the perifery apt repository Repository: 'deb https://apt.cloud.datacore.com/dev jammy main' Description: Archive for codename: jammy components: main More info: https://apt.cloud.datacore.com/dev Adding repository. Adding deb entry to /etc/apt/sources.list.d/archive_uri-https_apt_cloud_datacore_com_dev-jammy.list Adding disabled deb-src entry to /etc/apt/sources.list.d/archive_uri-https_apt_cloud_datacore_com_dev-jammy.list Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease Get:3 https://apt.cloud.datacore.com/dev jammy InRelease [1,164 B] Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:5 http://security.ubuntu.com/ubuntu jammy-security InRelease Get:6 https://apt.cloud.datacore.com/dev jammy/main amd64 Packages [1,204 B] Fetched 2,368 B in 1s (4,586 B/s) Reading package lists... Done W: https://apt.cloud.datacore.com/dev/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: https://apt.cloud.datacore.com/dev/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. The apt repository for the Swarm Software Appliance has now been installed\n The script will now install the application pending some environmental checks Do you want to proceed? (yes/no)
Accepting those prechecks adds the Swarm deb repo.
Select yes; it proceeds to install bootstrapper.
If the installer is at “Scanning linux images…” stage, press return and it should proceed further.
Once the bootstrapper is installed, the UI will install Nodejs, TypeScript, and some npm packages.
When the below pop-up prompts, you are ready to go to the UI to configure the system.
Click Create Cluster to create a new cluster.
Provide a name for your new cluster.
Click Next; it shows a final confirmation screen. Click Continue to accept all the entries or click Back to go back and correct the entries.
Clicking on Continue will start the deployment, which includes:
Installing k3s
Installing flux
Adding base overseer
Adding bucket login details
Using hostype to push the configuration
Helm reconcilliation via flux
The K3s install takes a few seconds to complete, then you should be able to use Kubectl to query the cluster.
When cluster manifests are deployed, the terminal looks like this:
When K3s is online, the UI looks like this:
It may take a few minutes for the storage nodes to come online.
The gateway gets created when the storage nodes are up. We are about 30 sec away from a running cluster.
When the pods are in this state, you are ready to login.
Now, the UI will switch to the following screen:
Login credentials for the first-time install are:
username – periferyadmin
password – password
The UI asks you to update the default password. Once updated, you can log in to the system as a normal user and see the below dashboard.
© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.