Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c85f4199b1015f7ea6e836000d, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c85f4199b1015f7ea6e836000d, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c8664c0be0016687d83fdb0025, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c8664c0be0016687d83fdb0025, userName='null'}

Panel

In this section:

Table of Contents

...

  • Five CentOS 7 or Ubuntu 18 Virtual Machines
    • These should be dedicated virtual machines with unique hostnames and with no other production applications running on them. Base OS packages should be installed and updated to the latest versions.
    • Requires an active internet connection. This is used to automatically install and configure software dependencies.
    • Should not have any pre-existing OS level firewall rules (iptables).
  • vCPU/Core: 8
    • Example: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50 GHz
  • RAM: 8 GB
  • NIC Interface: 1
  • Disks mounted to each Virtual Machine: 4
    • Host OS: 100 GB minimum
    • 3x disks for Docker storage: 100 GB minimum each per VM (this will grow as you add data to the system over time)
      • Disk space monitoring and alerting configured at safe threshold (for example, 80% used capacity)
      • Ability to expand disk space when it reaches the threshold
  • Docker version 19.03.48
  • Storidge version 1.0.0-3186

...

  1. SSH into each of the five servers and run the following command to install the Storidge software:

    Code Block
    $ curl -fsSL ftp://104.131.153.182/pub/ce/cio-ce | sudo bash -s -- -f -r 3085


    Wait for the above command to finish its execution successfully. It is expected to take several minutes.

  2. On the first node (primary node) in the cluster, run the following command:

    Code Block
    $ cioctl create --all-managers --noportainer

    Copy the join command and run that on the rest of the nodes in the cluster (nodes 2 to 5).

    For example: 

    Code Block
    $ cioctl node add 10.10.10.1 3b6ca81e9370a228c7fc8 edbfa3c6361-3aff2bb8

  3. Once you have added all your nodes to the cluster, return to the primary node and initialize the cluster with the ‘cioctl init’ command that was displayed after running the ‘cioctl create’ command.

    For example: 

    Code Block
    $ cioctl init e2e14943

    You can now see the cluster form. This may take several minutes.

  4. To verify that all five nodes are present and that their status is ‘normal’, run the following command:

    Code Block
    $ cio node ls

...