Help Center> ROMA Connect> User Guide> Instances> Creating a ROMA Site Collaborative Instance> Preparing Required Resources
View PDF

Preparing Required Resources

Overview

Before using a ROMA Site instance, you need to prepare VM resources, install Docker, mount disks, and check whether the VM can communicate with ROMA Site, IEF, SWR, OBS, or AOM.

Containerized applications that use IEF need to be charged separately. The billing modes are as follows:
  • Package billing mode: A package is purchased. Fees are deducted from the package based on the actual usage.
  • Pay-per-use billing mode: No package is purchased. Fees are deducted based on the actual usage.

For details, see Intelligent EdgeFabric (IEF).

You can prepare VM resources based on the following scenarios:

  • Creating a ROMA Site instance for the first time, which requires you to apply for a new VM based on the ROMA Site instance resource requirements
  • Creating another ROMA Site instance on the VM where the instance has been deleted

Creating a ROMA Site Instance for the First Time

  1. ROMA Site instances are classified into basic and professional instances. Before creating a ROMA Site instance, prepare VM resources of basic or professional instances as required. For details, see the following table.
    Table 1 VM resources

    Edition

    VM Quantity

    VIP

    CPU

    Total Memory (GB)

    Disk I/O (Read+Write) (MB/s)

    System Disk Space (GB)

    Data Disk Space (GB)

    System Architecture

    glibc Version

    Bandwidth Performance

    Number of IEF Containerized Applications

    Basic

    3

    1

    ≥ 16

    ≥ 64

    ≥ 350

    >= 100

    ≥ 500

    x86_64 architecture:

    • CentOS 7.x
    • EulerOS (V2.0SP5/V2.0SP9)

    ARM64 architecture:

    • CentOS 7.x

    The glibc version must be later than 2.17.

    Bandwidth during installation:

    ≥ 10 MB/s

    Bandwidth during running:

    ≥ 5 Mbit/s

    23

    Professional

    8

    1

    ≥ 8

    >= 32

    ≥ 350

    >= 100

    >= 600

    27

    The planned VIP must be bound to the first two VMs of the edge node. For example, two VMs numbered node-xxxx-000 and node-xxxx-001 or node-xxxx-001 and node-xxxx-002.

  2. Install Docker.

    The Docker version must be later than 17.06. Docker 18.06.3 is recommended. Do not use Docker 18.09.0. If you have used this version, upgrade it at the earliest.

    After Docker installation is complete, run the docker -v command to check whether Docker is installed properly. If the following information is displayed, Docker is installed properly.

    # docker -v 
Docker version 18.06.3, build 48a66213fee
  3. Mount a disk.

    Perform the following operations on each VM:

    1. Log in to the VM as user root.
    2. Check the disk status. 
      fdisk -l

      If information similar to the following is displayed, the system has two disks. One is a 300 GB disk whose drive letter is /dev/vdb, and the other is a 200 GB disk whose drive letter is /dev/vdc. The 300 GB disk /dev/vdb needs to be mounted to the /opt/roma/data directory, and the 200 GB disk /dev/vdc needs to be mounted to the /opt/roma/logs directory.

      Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1bec7a05

Device     Boot Start      End  Sectors Size Id Type
/dev/vda1  *     2048 83886079 83884032  40G 83 Linux


Disk /dev/vdb: 300 GiB, 322122547200 bytes, 629145600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/vdc: 200 GiB, 214748364800 bytes, 419430400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
    3. Format disks.

      mkfs.ext4 /dev/vdb

      mkfs.ext4 /dev/vdc

    4. Create a mount directory.

      mkdir -p /opt/roma/data

      mkdir -p /opt/roma/logs

    5. Mount the disks to the directory.

      mount /dev/vdb /opt/roma/data

      mount /dev/vdc /opt/roma/logs

    6. Configure automatic mounting for disk partitions.

      vi /etc/fstab

      Add the following configurations:

      /dev/vdb                    /opt/roma/data           ext4       defaults              0 0
/dev/vdc                    /opt/roma/logs           ext4       defaults              0 0
    7. Check whether the directory is mounted successfully.

      df -hT

      If information similar to the following is displayed, the directory is mounted successfully:

      Filesystem      Size  Used Avail Use% Mounted on
devtmpfs         63G     0   63G   0% /dev
tmpfs            63G     0   63G   0% /dev/shm
tmpfs            63G  8.6M   63G   1% /run
tmpfs            63G     0   63G   0% /sys/fs/cgroup
/dev/vda1        40G  7.9G   30G  22% /
tmpfs            13G     0   13G   0% /run/user/0
/dev/vdb        295G   65M  280G   1% /opt/roma/data
/dev/vdc        196G   61M  186G   1% /opt/roma/logs
  4. Synchronize the time.

    The time of the edge node must be the same as the UTC+8 time. Otherwise, the monitoring data and logs of the edge node may be inaccurate. You can select a proper NTP server for time synchronization to ensure time consistency. For details about the configuration method, see How Do I Synchronize Time with the NTP Server?

  5. Check whether the ports required by ROMA Site are enabled.

    After preparing VM resources, you need to check whether the ports required by each component are enabled on the VM. The port information is as follows:

    The external service ports are 80, 443, 9092, 9094, 1883, and 8443. Ensure that these ports can communicate with external networks and other ports can communicate with internal networks.

    Table 2 Ports opened by each component

    Component

    Port

    FDI

    9101, 9011, 9031, 9051, 9061, 9071, 9111, 9121, 9131, 9141, 9171, 9271, 9281, 9351, 9451, 9461, 9471, 9561, 9571, 9611, 9641, 9642, 9651, 9652, 9681, 9682, 9802, 9541, 9551, 9581, 9591

    APIC

    80, 443, 1026, 1027, 22379, 8086, 8084, 2379, 4001, 2380, 6800, 26800

    MQS

    9091, 9092, 9094, 2181, 3888, 2888, 8001, 8002, 8003, 9080, 12345, 12346, 9776, 20911, 19091, 19092, 19094, 12181, 13888, 12888, 18001

    LINK

    7443, 30006, 1883, 8443, 8491

    ABM

    13003, 13204, 13103, 12003, 14003, 9103, 11003, 15003, 9200, 6899, 26899

    BFS

    30613, 30605, 30003, 30608, 30618, 39607, 123, 22, 68

    Compose

    7080, 7090, 7181, 7182, 8480, 8000, 30008
    NOTE:

    FDI, APIC, MQS, and LINK are mandatory components. ABM, BFS, and Compose are optional components for enhancement.
  6. Check the communication with IEF, SWR, OBS, and AOM services. If an air gap or network restriction is configured in the environment where your VM node is located, configure the IP address. For details, see How Do I Obtain the IP Addresses of IEF Cloud Services?

Creating Another ROMA Site Instance

If you want to create another ROMA Site instance on the VM where the instance has been deleted, perform the following operations:

  1. Log in to all VMs as user root.
  2. Run the following commands to clear the remaining data of the deleted instance:

    # rm -rf /opt/roma/data/dms

    # rm -rf /opt/roma/data/kafka