Skip to main content
Version: 2.4

Storage node (SDS) Installation Guide

What is a Storage node (SDS)​

Storage node (SDS) play a roles as stack up SSDs & HDDs to CubeCOS Hyperconverged Infrastuctures' storage pool.

info

Before getting started with Storage node (SDS) installation you will need to prepare a control converged node or control node. Make sure to read through these requirements carefully as a successful deployment of Storage node (SDS) installation depends on it.

Dependency​

  • Control Converged node or Control node

Hardware recommendation​

For detailed hardware requitements and recommendation, reference the Hardware Requirement

Installation​

Choose a setup options - Wizard​

    First Time Setup Options:
    1: Wizard
    2: Advanced
    Enter index: 1

Accept the EULA​

    -- Welcome --
    Welcome to the Cube Appliance setup wizard.
    Using this setup wizard, you can:
    * View and accept the Software License Agreement
    * Set the appliance password
    * View and configure networking

    Press Enter to continue.


    -- Software License Agreement --
    Currently selected language: English
    1: Select language for license display
    2: Read Bigstack terms
    3: Read non-Bigstack terms
    4: Proceed to acceptance

    Select option: 4


    By choosing 'I agree,' you agree that (1) you have had the opportunity to
    review the terms of licenses presented above and (2) such terms govern this
    transaction. If you do not agree, choose 'I do not agree'.
    1: I agree
    2: I do not agree

    Select option: 1

Change node password​

To join a node to an existing CubeCOS cluster, the node's root password must match the destination cluster's root password.

Prerequisite

Prior to joining new nodes, the root password of the destination cluster must be changed. If you have not yet done so, please refer to the documentation on changing the cluster root password.

Change node password to match destination cluster password​

During the node setup process, you will be prompted to change the appliance password. Follow the on-screen instructions to update the password to match the root password of the destination cluster.

  1. Enter the old password.
    1. The default password is admin
  2. Enter the new password, which must match the destination cluster's root password.
  3. Confirm the new password.
  4. Verify the success message for password changes with "Password successfully changed."

Example of changing the node password​

-- Appliance Password --
Password changes are applied immediately.
Password has not been modified.
1: Change password
x: Exit
p: Previous screen
n: Next screen

Select option: 1

- Change Password -
Enter old password: admin
Enter new password:
Confirm new password:
Password successfully changed.

Configure hostname​

warning

A valid hostname must be in lowercase and cannot contain special characters (!@#$%^&*()), underscores (_), or spaces.

A valid hostname must:

  • Contain only lowercase letters (a-z), numbers (0-9), and hyphens (-)
  • Be 64 characters or less in length
  • Be unique within the network
  • Must start with a letter
  • Not be entirely numeric
    -- Host Name Configuration --
    Host name: unconfigured
    1: Change the host name
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: 1


    - Change the Host Name -
    Enter the new host name: storage01


    -- Host Name Configuration --
    Host name: storage01
    1: Change the host name
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

[Optional] Configure network bonding​

Network bonding is optional and only required for deployments that require network redundancy. To better understand network configuration options and deployment scenarios, refer to the network configuration section.

Skip to Configure IP address - IF.1 if bonding and VLAN are not required.

info

If a network cable is connected, the [Speed] column will display the link status (e.g., 1000Mb/s, 10Gb/s). If no cable is detected, it will show N/A.

warning

Do not use bond0, bond1, bondx, or bd0 as bonding interface names. These names are reserved or may conflict with system defaults.

    -- Network Bonding Settings --
    --------------------------------------------------
    Label          BusID   Driver  State    Speed
    --------------------------------------------------
        IF.1   0000:04:00.0    r8169     UP    1000F
    --------------------------------------------------
    1: Display policy
    2: Configure network bonding
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

[Optional] Create VLAN​

    -- VLAN Settings --
    --------------------------------------------------
    Label          BusID   Driver  State    Speed
    --------------------------------------------------
        IF.1   0000:04:00.0    r8169     UP    1000F
    --------------------------------------------------
    1: Display policy
    2: Configure vlan network
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

Configure IP address​

    -- Networking Settings --
    --------------------------------------------------
    Label          BusID   Driver  State    Speed
    --------------------------------------------------
        IF.1   0000:04:00.0    r8169     UP    1000F
    --------------------------------------------------
    1: Display device status
    2: Display policy
    3: Configure IF.1
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: 3


    - Configure IF.1 -
    Enter the IPv4 address: 10.32.2.251
    Enter the IPv4 subnet mask: 255.255.0.0
    Enter the IPv4 default gateway: 10.32.0.254


    -- Networking Settings --
    --------------------------------------------------
    Label          BusID   Driver  State    Speed
    --------------------------------------------------
        IF.1   0000:04:00.0    r8169     UP    1000F
    --------------------------------------------------
    1: Display device status
    2: Display policy
    3: Configure IF.1
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

Setting DNS​

    -- DNS Configuration --
    No DNS servers configured.
    1: Set DNS server 1
    2: Set DNS server 2
    3: Set DNS server 3
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: 1


    - Set DNS Server 1 -
    Enter the DNS server IP address: 1.1.1.1


    -- DNS Configuration --
    DNS server 1: 1.1.1.1
    1: Set DNS server 1
    2: Set DNS server 2
    3: Set DNS server 3
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

Setting the timezone​

info

Set the same timezone on all nodes within the cluster to ensure consistent timekeeping. This is critical for proper coordination of services and log synchronization across the cluster.

    -- Time Configuration --
    Time configuration changes are applied immediately.
    Time Zone: America/New_York
    Date: 01/02/2023
    Time: 01:14:19
    1: Change the time zone
    2: Change the date
    3: Change the time
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: 1

    - Change the Time Zone -
    Select a continent or ocean:
    1: Africa
    2: Americas
    3: Asia
    4: Atlantic Ocean
    5: Australia
    6: Europe
    7: Pacific Ocean
    8: Etc
    Enter index: 3
    Select a timezone:
    1: (UTC+02:00) Asia/Jerusalem
    2: (UTC+03:00) Asia/Kuwait
    3: (UTC+03:00) Asia/Riyadh
    ~~~~~~
    30: (UTC+08:00) Asia/Taipei
    ~~~~~~
    39: (UTC+12:00) Asia/Kamchatka
    Enter index: 30


    -- Time Configuration --
    Time configuration changes are applied immediately.
    Time Zone: Asia/Taipei
    Date: 01/02/2023
    Time: 14:14:21
    1: Change the time zone
    2: Change the date
    3: Change the time
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

Configure the storage role​

    -- Cube Role --
    Current role: undef
    Current Management: IF.1
    Current Domain/Region: default/RegionOne
    Current Cube Secret Seed: N/A
    1: Change role
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: 1


    - Change Role -
    Select a role:
    1: control
    2: compute
    3: storage
    4: control-converged
    5: edge-core
    6: moderator
    Enter index: 3
    Specify controller hostname: cc1
    Specify controller IP: 10.32.2.240
    Specify management interface: IF.1
    Specify storage interface [frontend(,backend)]: IF.1
    Specify region ("RegionOne"):
    Specify cluster secret seed: bigstack


    -- Cube Role --
    Current role: storage
    Current Controller: cc1(10.32.2.240)
    Current Management: IF.1
    Current Storage: IF.1
    Current Domain/Region: default/RegionOne
    Current Cube Secret Seed: bigstack
    1: Change role
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

Configure High Availability​

    -- Cube High Availability --
    Current HA setting: disabled
    1: Change HA
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: 1

    - Change HA -
    High Available Cube:
    1: Yes
    2: No
    Enter index: 1
    Specify control group hostname [HOST,HOST,...]: cc1,cc2,cc3
    Specify control group address [IP,IP,...]: 10.32.2.241,10.32.2.242,10.32.2.243

    -- Cube High Availability --
    Current HA setting: enabled
    Current Control Group:
    cc1(10.32.2.241),cc2(10.32.2.242),cc3(10.32.2.243)
    1: Change HA
    x: Exit
    p: Previous screen
    n: Next screen

    Select option: n

Summary​

    Summary
    Password has not been modified.
    Host name: storage01
    IF.1
        Default interface.
        IPv4 Mode: Manual
        IPv4 Address: 10.32.2.251
        IPv4 Netmask: 255.255.0.0
        IPv4 Gateway: 10.32.0.254
        IPv6 Mode: Automatic
    DNS server 1: 1.1.1.1
    Time Zone: Asia/Taipei
    Date: 01/02/2023
    Time: 14:14:47
    Role: storage
    Controller: cc1(10.32.2.240)
    Management: IF.1
    Storage: IF.1
    Domain/Region: default/RegionOne
    Cube Secret Seed: bigstack
    High Availability: disabled
    1: Accept the configuration
    2: Cancel the configuration
    3: Modify the configuration

    Select option: 1

The time required to apply the policy may vary depending on your hardware performance.

Monitor the console output. A success message will appear once the policy application is complete and the node is ready for the next step.

Verify policy success in the console with

Policy changes were successfully applied.

Error message​

    Policy changes could not be applied. System must be rebooted.
    Press enter to continue:

Please Re-image the node, if the error message above is presented and start over the installation progress​

Last updated on by Brian Su