/
INF Deployment Guideline - StarlingX O-Cloud - AIO Simplex

INF Deployment Guideline - StarlingX O-Cloud - AIO Simplex

Owned by Jackie Huang
Last updated: Dec 04, 2024
2 min read

 

1. Introduction

Detail the approach of steps for StarlingX O-Cloud All-in-one Simplex deployment

1.1) Description

 The All-in-one Simplex (AIO-SX) deployment option provides all three cloud functions (controller, worker, and storage) on a single server with the following benefits:

  • Requires only a small amount of cloud processing and storage power

  • Application consolidation using multiple containers or virtual machines on a single physical server

  • A storage backend solution using a single-node CEPH deployment

1.2) System topology

image-20241203-022834.png

 

2. Minimum Requirements

Detail the hardware and software requirements necessary for the installation

  • Number of servers: 1

  • 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

step-by-step instructions for deployment

3.1)Step 1: Install OS and Software from ISO image

Expected Result: The OS and Software installation complete successfully and reboot into the system.

 

3.2) Step 2: Bootstrap system with ansible playbook

Expected Result: Ansible bootstrap playbook complete successfully.

 

3.3) Step 3: Configure and unlock controller-0

Expected Result: The system is unlocked and reboot successfully.

4. Post-Installation Verification

Outline how to verify that the installation was successful.

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

Expected Result:

[sysadmin@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+

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

Expected Result: 

[sysadmin@controller-0 ~(keystone_admin)]$ ceph -s cluster: id: 8f463ab3-fcae-4003-b6f1-57563d98215a health: HEALTH_OK services: mon: 1 daemons, quorum controller-0 (age 2w) mgr: controller-0(active, since 2w) mds: kube-cephfs:1 {0=controller-0=up:active} osd: 1 osds: 1 up (since 2w), 1 in (since 4w) data: pools: 3 pools, 192 pgs objects: 27 objects, 9.3 KiB usage: 3.2 GiB used, 443 GiB / 446 GiB avail pgs: 192 active+clean

5. Troubleshooting

Provide common issues and their solutions.

  • Issue 1: (Describe the issue.)
    Solution: (Provide the solution.)

 

6. Additional Resources

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