Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 22

...

Run the script as root, so you can sudo su to switch to root.

Code Block
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.

...

Info

Info

Make sure you have the Physical node installed before installing the SNS 1.1.1 base packages.

Follow the steps below to install SNS 1.1.1 base packages:

  1. Use SSH to log in to the server. Please provide the user password when prompted.

    Code Block
    ssh <username>@<server_ip>
  2. Once logged in, switch to the root user. Please provide the password when prompted.

    Code Block
    sudo su
  3. To install the base packages, execute the following command.

    Code Block
    sudo su -c "bash <(wget -qO- https://apt.cloud.datacore.com/installssa/install-ssa.sh)" root
  4. Installation is done via script. Please contact your Solutions Architect for the SNS installation.

    There are a few prechecks to accept.
    It adds the apt repository, then installs the latest periferyssa debian package as shown in the example below:

    Code BlockWe'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.

    through the scripts which when passed will ask for confirmation to proceed with installation. Please provide yes to proceed.

    Code Block
    The apt repository for the Swarm Software Appliance has now been installed\n added to this machine.
    The script will now install the application pending some environmental checks
    Do you want to proceed? (yes/no)
    
    
  5. Accepting those prechecks adds the Swarm deb repo.

  6. Type ‘yes’, then hit enter. It proceeds to install the bootstrapper.

    Code Block
    Do you want to proceed? (yes/no) yes
    ok, attempting to install
    installing ssa bootstrapper
    Extracting templates from packages: 100%
    Scanning processes...
    Scanning processor microcode...
    Scanning linux images...
    
    Running kernel seems to be up-to-date.
    
    The processor microcode seems to be up-to-date.
    
    No services need to be restarted.
    
    No containers need to be restarted.
    
    No user sessions are running outdated binaries.
    
    No VM guests are running outdated hypervisor (qemu) binaries on this host.
    2024-03-19 16:49:39 - Installing pre-requisites
    Hit:1 https://apt.cloud.datacore.com/dev jammy InRelease
    Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
    Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease
    Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
    Hit:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
    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.
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    ca-certificates is already the newest version (20230311ubuntu0.22.04.1).
    ca-certificates set to manually installed.
    curl is already the newest version (7.81.0-1ubuntu1.15).
    curl set to manually installed.
    gnupg is already the newest version (2.2.27-3ubuntu2.1).
    gnupg set to manually installed.
    The following NEW packages will be installed:
      apt-transport-https
    0 upgraded, 1 newly installed, 0 to remove and 62 not upgraded.
    Need to get 1,510 B of archives.
    After this operation, 170 kB of additional disk space will be used.
    Get:1 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 apt-transport-https all 2.4.11 [1,510 B]
    Fetched 1,510 B in 0s (8,571 B/s)
    Selecting previously unselected package apt-transport-https.
    (Reading database ... 174603 files and directories currently installed.)
    Preparing to unpack .../apt-transport-https_2.4.11_all.deb ...
    Unpacking apt-transport-https (2.4.11) ...
    Setting up apt-transport-https (2.4.11) ...
    Scanning processes...
    Scanning processor microcode...
    Scanning linux images...
    
    Running kernel seems to be up-to-date.
    
    The processor microcode seems to be up-to-date.
    
    No services need to be restarted.
    
    No containers need to be restarted.
    
    No user sessions are running outdated binaries.
    
    No VM guests are running outdated hypervisor (qemu) binaries on this host.
    Hit:1 https://apt.cloud.datacore.com/dev jammy InRelease
    Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
    Get:3 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]
    Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
    Hit:5 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
    Hit:6 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
    Get:7 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [7,386 B]
    Fetched 19.5 kB in 0s (44.8 kB/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.
    2024-03-19 16:49:44 - Repository configured successfully. To install Node.js, run: apt-get install nodejs -y
    Scanning processes...
    Scanning processor microcode...
    Scanning linux images...
    
    Running kernel seems to be up-to-date.
    
    The processor microcode seems to be up-to-date.
    
    No services need to be restarted.
    
    No containers need to be restarted.
    
    No user sessions are running outdated binaries.
    
    No VM guests are running outdated hypervisor (qemu) binaries on this host.
    Scanning processes...
    Scanning processor microcode...
    Scanning linux images...
    
    Running kernel seems to be up-to-date.
    
    The processor microcode seems to be up-to-date.
    
    No services need to be restarted.
    
    No containers need to be restarted.
    
    No user sessions are running outdated binaries.
    
    No VM guests are running outdated hypervisor (qemu) binaries on this host.
    npm notice
    npm notice New major version of npm available! 9.8.1 -> 10.5.0
    npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.5.0
    npm notice Run npm install -g npm@10.5.0 to update!
    npm notice

If the installer is at “Scanning linux images…” stage, press return and it should proceed further.

Once the bootstrapper is installed, it installs Nodejs, TypeScript, and some npm packages.

Code Block
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.
2024-03-20 15:26:43 - Repository configured successfully. To install Node.js, run: apt-get install nodejs -y
Reading package lists...
Building dependency tree...
Reading state information...
nodejs is already the newest version (18.18.2-1nodesource1).
The following packages were automatically installed and are no longer required:
  libavahi-client-dev libavahi-common-dev libavahi-compat-libdnssd-dev libavahi-compat-libdnssd1 libdbus-1-dev pkg-config wireguard wireguard-tools
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 58 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
node-typescript is already the newest version (4.5.4+ds1-1).
The following packages were automatically installed and are no longer required:
  libavahi-client-dev libavahi-common-dev libavahi-compat-libdnssd-dev libavahi-compat-libdnssd1 libdbus-1-dev pkg-config wireguard wireguard-tools
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
Scanning processes...
Scanning processor microcode...
Scanning linux images...

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
The bootstrapper and api services have now been installed you can now go to http://<IP address>/ui to continue configuration

Once the installation is complete, it will display the URL to continue the configuration. Copy that URL and manually enter it in the browser for UI configuration. When the below pop-up prompts, you are ready to go to the UI to configure the system.

...

  1. It may take a while to finish installation. Once the installation is complete, a URL will be provided to access the UI (see the below screenshot).

    image-20250130-123752.pngImage Added
Info

Info

Make sure the template file has been generated before accessing the UI to create a cluster. Run the command ls /etc/hosttype to verify the existence of the file.

If the file exists, execute cat /etc/hosttype to check its contents. If the file is empty or not generated or contains the template name "test", halt the cluster creation process and contact the DataCore’s Customer Support Engineer to resolve the issue. Once the issue is fixed, you can proceed with the cluster creation as mentioned below. This will help avoid reinstalling the Debian package again.

Tip

Next, see [DRAFT] SWARM Containerized Stack Installation