DCE 5.0 All-in-One Deployment¶

This document explains how to deploy DCE 5.0 on an all-in-one machine.

Environment Preparation¶

First, you need to prepare a good network environment and capacity planning.

Network Requirements¶

Hardware

• Usually, the all-in-one machine has multiple network cards or one network card with multiple ports, so it is recommended to create a Bond and make the Bond with LACP port group highly available.
• It is not recommended to divide into multiple planes temporarily, and share one data plane.
• The network port needs to be in trunk mode.

Reserved VLANs

At least 2 VLANs are required: 1 for BMC VLAN, 1 for management/business VLAN, and 1 for storage VLAN (optional). If you need to allocate "static IP" for Pods, you need to create sub-interfaces and allocate VLANs additionally.

IP

Network Ports

Port Requirements

Capacity Planning¶

CPU, Memory, Disk

Environment Preparation Checklist

Installation Steps (3 Physical Machines)¶

Install Prerequisites¶

Install Dependencies

Offline Installation¶

Start Installation

Precautions before installation:

• Select one of the three physical machines as the boostrap machine to execute the deployment of DCE 5.0. In the cluster configuration file ClusterConfig.yaml, the bootstrapNode parameter can specify the IP of the boostrap machine.

  apiVersion: provision.daocloud.io/v1alpha3
  kind: ClusterConfig
  metadata:
  spec:
    clusterName: my-cluster
  
    # The domain name or IP of the boostrap node, which is resolved to the IP of the default gateway of the boostrap node by default;
    # You can manually enter the IP or domain name, if it is a domain name, if it is unable to resolve, an automatic mapping between this domain name and the default IP of the boostrap node will be established
    # bootstrapNode: auto  ## Automatically resolved by default
    ...
  ...
  

• In the cluster configuration file ClusterConfig.yaml, configure the information of the 3 physical machines in masterNodes.

  ...
  apiVersion: provision.daocloud.io/v1alpha3
  kind: ClusterConfig
  metadata:
  spec:
    ...
    masterNodes:
      - nodeName: "g-master1" # Physical machine 1 acts as the control plane node + boostrap node
        ip: xx.xx.xx.xx
        ansibleUser: "root"
        ansiblePass: "dangerous"
        #ansibleSSHPort: "22"
        #ansibleExtraArgs: "" 
      - nodeName: "g-master2"
        ip: xx.xx.xx.xx
        ansibleUser: "root"
        ansiblePass: "dangerous"
        #ansibleSSHPort: "22"
        #ansibleExtraArgs: ""
      - nodeName: "g-master3"
        ip: xx.xx.xx.xx
        ansibleUser: "root"
        ansiblePass: "dangerous"
        #ansibleSSHPort: "22"
        #ansibleExtraArgs: ""
      ...
  ...
  

Comments