Overview

ROMA Site is the edge form of ROMA Connect and has the same data integration, service integration, and message integration capabilities as ROMA Connect. ROMA Site can be deployed in users IDCs and third-party public clouds and is reversely connected to ROMA Connect in the cloud, without damaging the security boundaries of enterprises.

A ROMA Site instance is an independent resource space. Resources of different instances are isolated from each other. You can use one or more ROMA Site instances based on service requirements.

Prerequisites

• You have prepared VM resources by referring to Preparing Required Resources.
• You have purchased the IEF service when preparing required resources. For details about IEF, see Intelligent EdgeFabric (IEF).
• If the prepared VM cannot access IEF through the public network, access IEF through the private network. Private network access must meet the following requirement:

  You have connected to IEF through Direct Connect or VPN.

Procedure

1. Enable the edge-cloud channel.
   The ROMA Site edge-cloud channel is used for ROMA Site–to-cloud and ROMA Site–to-ROMA Site communication. You must enable this channel before creating a ROMA Site instance.

   1. Log in to the ROMA Connect console. In the navigation pane on the left, choose Site Instances.
   2. On the Site Instances page, click Enable Edge-Cloud Channel.
   3. The Enable ROMA Site Function page that appears on the right shows the ROMA Site functions and fees. Click Enable Now.
   4. On the Confirm page that is displayed, confirm Resource and Price, and read the Customer Agreement and Privacy Statement carefully.
   5. After you confirm the order information, select I have read and agree to the Customer Agreement and Privacy Statement, and click Submit.
   6. On the Buy ROMA page, select a payment method and click Pay. After the payment is complete, the message "Payment processed successfully" is displayed. The edge-cloud channel is enabled successfully.
2. After the edge-cloud channel is enabled, click Create Site Instance > Collaborative Edition on the Site Instances page. The Create a Collaborative Edition configuration item is added to the page. For details about the configuration, see the following table.

   Table 1 Creating a ROMA Site instance

   Parameter	Description
   Name	Name of a custom ROMA Site instance.
   Site Type	Self-built Site: Enterprises build their own edge nodes and use VMs in their equipment rooms. Intelligent EdgeSite: IES nodes

3. After the configuration is complete, click OK. Then, click Create Site. The following table describes the parameters for creating a site.

   Table 2 Creating a site

   Parameter	Description
   Deployment Type	Hybrid
   Site Specification	Select Lite for ROMA Site basic instances, and select Standard for ROMA Site professional instances. Lite: with three built-in edge nodes; lightweight, requiring fewer resources; ideal for ROMA Site basic instances Standard: with eight built-in edge nodes; high availability and stability; ideal for ROMA Site professional instances
   CPU Architecture	Select x86_64 or arm64 based on the CPU architecture supported by the current environment.
   Private Network Address	Enter the ingress floating IP address of the load balancer of the site instance. If the built-in LB is used, configure the two VMs bound to the floating IP address as the first two edge nodes.
   NIC	Enter the network adapter name. The default value is eth0. You can run the ip a command to view the specific NIC name.
   Proxy	Enable this option if you want to allow the site to communicate with the ROMA Connect management plane through a public network.
   Proxy Address	This parameter is mandatory only when Proxy is enabled. Enter the proxy address of the edge node. HTTP and SOCKS5 are supported. The proxy formats are as follows: HTTP proxy: http://user:password@IP:PORT SOCKS5 proxy: socks5://user:password@IP:PORT In the preceding information, user and password indicate the username and password for connecting to the proxy, and IP and PORT indicate the IP address and port number of the proxy.

4. After the configuration is complete, click Create. The system automatically creates sites and edge nodes based on the site configuration.

   

5. After an edge node is created, click Download to download the configuration file that contains information such as the edge node key.
6. Back up the node.tar.gz file in the downloaded configuration file to the local host.
   

   Use the backup node.tar.gz file when a user VM is faulty and needs to be reset.

7. After the configuration file is downloaded, the system connects the edge node to the cloud. After the connection is complete, click Download the Core Software Installation Tool to download and install the corresponding tool.
   

   Currently, x86_64 and arm64 are supported. Download the corresponding installation program.

8. Back up the edge-installer_1.0.14_x86_64.tar.gz file in the core software installation tool package to the local host.
   

   Use the backup edge-installer_1.0.14_x86_64.tar.gz file when a user VM is faulty and needs to be reset.

   In the preceding command, 1.0.14 indicates the installation tool version, and x86_64 indicates the CPU architecture type. Use the actual tool version and architecture as required.

9. Decompress the configuration file and upload it to the corresponding node based on the file name sequence.
   • Create the /opt/IEF/Cert directory and decompress the edge node configuration file to this directory.

     sudo mkdir -p /opt/IEF/Cert 
     sudo tar -zxvf nodeName.tar.gz. -C /opt/IEF/Cert

     Replace nodeName with the name of the edge node configuration file on the corresponding node.

   • Decompress the core software installation tool.

     sudo tar -zxvf edge-installer_1.0.14_x86_64.tar.gz -C /opt

     In the preceding command, 1.0.14 indicates the installation tool version, and x86_64 indicates the CPU architecture type. Use the actual tool version and architecture as required.

10. Run the following commands to connect the edge node to the cloud.

    cd /opt/edge-installer 
    sudo ./installer -op=install

11. After the edge node is registered, click Next: Deploy Site Instance. The Buy ROMA Site Instance page is displayed.
12. On the Buy ROMA Site Instance page, enter the instance configuration information. The following table describes the parameters.

    Table 3 Parameters for purchasing a ROMA Site instance

    Parameter	Description
    Billing Mode	Billing mode, which can be Yearly/Monthly.
    Deployment Type	Hybrid
    Edition	Specifications of a ROMA Site instance to be purchased. Basic: 25 connections, suitable for small enterprises. Professional: 80 connections, suitable for small- and medium-sized enterprises. If you need to increase the quota, click Increase quota.
    Instance Name	Name of the instance configured in step 1. It can be changed.
    Description	Description of the purchased ROMA Site instance.
    MQS SASL_SSL	Whether to enable SASL authentication and SSL encryption for message transmission. After this function is enabled, data will be encrypted before transmission for higher security, but performance will be degraded.
    Private Network Access	Whether to enable private network access. If the prepared VM cannot access IEF through the public network, access IEF through the private network. Connect IEF through a private line or VPN.
    VPC	This parameter is required when Private network access is enabled. Select the VPC and subnet associated with the instance.
    Required Duration	Validity period for the instance. The minimum duration is 1 month. If you select Auto renew, monthly subscriptions are renewed each month and yearly subscriptions are renewed each year.

13. After the configuration is complete and the bill is confirmed, click Next. The purchase confirmation page is displayed.
14. Confirm the purchase information, select I have read and agree to the Customer Agreement and Privacy Statement, and click Submit.
15. On the Buy ROMA page, select a payment method and click Pay.