OpsAny Digital R&D Platform — Community Edition Deployment¶

Deploying the R&D Platform¶

The OpsAny Digital R&D Platform manages application resources, CI/CD pipelines, continuous deployment, and artifact repositories. It depends on third-party open-source tools — you must either prepare dedicated hosts for GitLab, Jenkins, Nexus, and StackStorm, or integrate the tools your organization already runs. Version compatibility matters, and there is a learning curve. If you are unfamiliar with DevOps, or your host has less than 16 GB of memory, do not deploy it. 【Life is short — don't go looking for trouble. — OpsAny】

Set the admin password

Before installing, check whether you have already changed the admin password. By default it is read from $INSTALL_PATH/conf/.passwd_env. If you have changed the password, update the corresponding value in that file.

INSTALL_PATH=/data/opsany
vim $INSTALL_PATH/conf/.passwd_env

Deploy the application platform with the automation script.

Before deploying the Digital R&D Platform, check the host's available memory. At least 4 GB must remain free to add the R&D Platform modules to an existing host. Alternatively, use 【Dedicated host deployment】 below to deploy the R&D Platform on its own host.

Same host

Deploy the application platform with the automation script.

# This command deploys four platforms: Application, Pipeline, Continuous Deployment, and Artifact Repository.
cd /opt/opsany-paas/install/
./saas-ce-install.sh dev

Refresh the Workbench, or sign out and sign in again, and the new platforms appear in the navigation menu.

OpsAny

Dedicated host

You can deploy the OpsAny Digital R&D Platform on a dedicated host. In the example below the original host is 192.168.56.11 and the new host is 192.168.56.12. The main change is pointing MySQL, Redis, and MongoDB at the original host.

Copy the installation package from the original host

# Run on the ORIGINAL host
$ scp -r /opt/opsany-paas root@192.168.56.12:/opt/

Configure the new host

# Edit the configuration file on the NEW host
vim /opt/opsany-paas/install/install.config
# Set LOCAL_IP to the new host's IP address
LOCAL_IP="192.168.56.12"
MYSQL_SERVER_IP="192.168.56.11"
REDIS_SERVER_IP="192.168.56.11"
MONGO_SERVER_IP="192.168.56.11"

# Create the installation directory on the NEW host
mkdir /data/opsany/

Copy the configuration directory from the original host to the new host, then update the Nginx configuration

scp -r /data/opsany/conf root@192.168.56.12:/data/opsany/
scp -r /data/opsany/esb root@192.168.56.12:/data/opsany/

# Change the IP addresses to the new host's IP address
vim /data/opsany/conf/nginx-conf.d/opsany_paas.conf
    upstream SAAS_DEVOPS {
        server 192.168.56.12:7009 max_fails=1  fail_timeout=30s;
    }
    upstream SAAS_PIPELINE {
        server 192.168.56.12:7017 max_fails=1  fail_timeout=30s;
    }
    upstream SAAS_DEPLOY {
        server 192.168.56.12:7018 max_fails=1  fail_timeout=30s;
    }
    upstream SAAS_REPO {
        server 192.168.56.12:7020 max_fails=1  fail_timeout=30s;
    }
    upstream SAAS_CODE {
        server 192.168.56.12:7010 max_fails=1  fail_timeout=30s;
    }
# Restart Nginx
docker restart opsany-base-openresty

Run the installation on the new host

cd /opt/opsany-paas/install/
source install.config
mkdir -p ${INSTALL_PATH}/logs/{devops,pipeline,repo,code,deploy,llmops}

# Start the container used to run Python scripts
docker run -d --restart=always --name opsany-paas-websocket \
-p 8004:8004 -v ${INSTALL_PATH}/logs:/opt/opsany/logs \
-v ${INSTALL_PATH}/uploads:/opt/opsany/uploads \
-v ${INSTALL_PATH}/conf/opsany-paas/websocket/settings_production.py.websocket:/opt/opsany/websocket/config/prod.py \
-v ${INSTALL_PATH}/conf/opsany-paas/websocket/settings_production.py.websocket.init:/opt/opsany/websocket/config/__init__.py \
-v ${INSTALL_PATH}/conf/opsany-paas/websocket/websocket.ini:/etc/supervisord.d/websocket.ini \
-v /usr/share/zoneinfo:/usr/share/zoneinfo \
-v /etc/localtime:/etc/localtime:ro \
${PAAS_DOCKER_REG}/opsany-paas-websocket:3.3.3

# Copy the initialization scripts into the container
docker cp ../saas/ opsany-paas-websocket:/opt/opsany/
docker cp ./init/ opsany-paas-websocket:/opt/opsany/

# Run the installation script
./saas-ce-install.sh dev

Open 【Platform Navigation】 → 【Pipeline / Continuous Deployment / Artifact Repository】 → 【System Settings】 to integrate the tools. If you do not have the tools yet, deploy them according to the instructions below. Note: GitLab and Jenkins use API tokens; Nexus currently uses username and password authentication.

Deploying the Application Platform Dependencies¶

Watch out for the port conflicts listed below and resolve them yourself. A dedicated host is recommended: 8 vCPU, 16 GB memory, 100 GB disk.

GitLab: version must be greater than 13.12. Listening ports: 80, 8080, and others.
Jenkins: required by Pipeline, version must be greater than 2.328. The GitLab plugin must be installed. Listening ports: 8008, 8009.
Nexus: required by Artifact Repository, version must be 3.x. Listening ports: 8014, 8015.
StackStorm: required by Continuous Deployment, version must be 3.6.0. Listening ports: 8005, 9100, 9102, 9202.
SonarQube: code scanning, version must be 9.9.6. Listening port: 8016.