Versions Compared

Key

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

...

(info) Detail the approach of steps for StarlingX O-Cloud All-in-one Duplex deployment

1.1) Description 

 The All-in-one Duplex (AIO-DX) deployment option provides a pair of high availability (HA) servers with each server providing all three cloud functions (controller, worker, and storage).

An AIO-DX configuration provides the following benefits:

  • Only a small amount of cloud processing and storage power is required

  • Application consolidation using multiple containers or virtual machines on a single pair of physical servers

  • High availability (HA) services run on the controller function across two physical servers in either active/active or active/standby mode

  • A storage back end solution using a two-node CEPH deployment across two servers

  • Containers or virtual machines scheduled on both worker functions

  • Protection against overall server hardware fault, where

    • All controller HA services go active on the remaining healthy server

    • All containers and/or virtual machines are recovered on the remaining healthy server

1.2) System topology

image-20241205-025841.pngImage Added

2. Minimum Requirements

(info) Detail the hardware and software requirements necessary for the installation

  • Number of servers: 2

  • Cores:

    • Dual-CPU Intel® Xeon® E5 26xx family (SandyBridge) 8 cores/socket

    • or Single-CPU Intel® Xeon® D-15xx family, 8 cores (low-power/low-cost option)

  • RAM:

    • 64GB

  • Storage:

    • Primary Disk: 500 GB SSD or NVMe

    • Additional disks:

      • 1 or more 500 GB (min. 10K RPM) for Ceph OSD

  • Operating System

    • Debian 11 (bullsye), included in the StarlingX ISO installation.

  • More Details of the Requirements:

 

3. Installation

(info) step-by-step instructions for deployment

3.1) Step 1: Install OS and Software from ISO image on controller-0

Expected Result: The OS and Software installation complete successfully on controller-0 and reboot into the system.

 

3.2) Step 2: Bootstrap system with ansible playbook on controller-0

Expected Result: Ansible bootstrap playbook complete successfully on controller-0

 

3.3) Step 3: Configure and unlock controller-0

Expected Result: The system is unlocked and controller-0 reboot successfully.

3.4) Step 4: Install OS and Software on controller-1 thruogh PXE

Expected Result: The OS and Software installation complete successfully on controller-0 and reboot into the system.

3.5) Step 5: Configure and unlock controller-1

Expected Result: The system is unlocked and controller-1 reboot successfully.

4. Post-Installation Verification

(info) Outline how to verify that the installation was successful.

4.1) Step 1: Check if both controllers in the system is in state of unlocked, enabled and available

Expected Result:

Code Block
~(keystone_admin)$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+
| id | hostname     | personality | administrative | operational | availability |
+----+--------------+-------------+----------------+-------------+--------------+
| 1  | controller-0 | controller  | unlocked       | enabled     | available    |
| 2  | controller-1 | controller  | unlocked       | enabled     | available    |
+----+--------------+-------------+----------------+-------------+--------------+

4.2) Step 2: Check ceph cluster health if Ceph is configured:

Expected Result: 

Code Block
$ ceph -s
    cluster:
        id:     c18dfe3a-9b72-46e4-bb6e-6984f131598f
        health: HEALTH_OK

    services:
        mon: 2 daemons, quorum a,b (age 9m)
        mgr: a(active, since 6m), standbys: b
        mds: 1/1 daemons up, 1 hot standby
        osd: 2 osds: 2 up (since 7m), 2 in (since 7m)

    data:
        volumes: 1/1 healthy
        pools:   4 pools, 113 pgs
        objects: 25 objects, 594 KiB
        usage:   72 MiB used, 19 GiB / 20 GiB avail
        pgs:     113 active+clean

    io:
        client:   1.2 KiB/s rd, 2 op/s rd, 0 op/s wr

5. Troubleshooting

(info) Provide common issues and their solutions.

...

(info) List of additional documentation, links, or resources that may be helpful.