Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

For Luma Automation On-Premise Agent deployment, the following components should be installed on the on-premise server:

  • itas_mule_adaptor

  • itas_connectors

  • itas_service_bus

  • sa_tunneling_service

Use 'lumauser' to execute all the docker container, deployment scripts, and all the docker commands instead of sudo user. 

Pre-Deployment Actions

Perform the following Pre-deployment actions:

  1. Set up artifacts

    1. Download and transfer itas-deployment-2.0.0-onprem.zip to /platform/deployment directory and unzip

      cd /platform/deployment
unzip itas-deployment-2.0.0-onprem.zip -d itas-deployment-2.0.0-onprem

2. Set up "master.properties"

  1. Populate master.properties file located under /platform/deployment/itas-deployment-2.0.0-onprem/itas-deployment-2.0.0/deploy directory. Most of the properties are self explanatory; if in doubt, please contact Serviceaide Support.

  2. Configure system ulimits in file /etc/security/limits.conf

    centos       soft    nproc           16384      
centos       hard    nproc           16384
centos       soft    nofile          65536
centos       hard    nofile          65536
lumauser     soft    nproc           16384 
lumauser     hard    nproc           16384
lumauser     soft    nofile          65536
lumauser     hard    nofile          65536
root         soft    nproc           16384
root         hard    nproc           16384
root         soft    nofile          65536
root         hard    nofile          65536

  3. Login to dockerhub using the below command:

    docker login https://registry-1.docker.io -u serviceaideindia
# use the dockerhub password provided separately

  4. Setup directory structure

    sudo mkdir -p /platform/data/logs/itas/itas_mule_adaptor
sudo mkdir -p /platform/data/logs/itas/itas_db_migration
sudo mkdir -p /platform/data/logs/itas/itas_service_bus
sudo chmod -R 777 /platform/data/logs/itas
sudo mkdir -p /platform/data/attachment_store/itas
sudo mdir -p /platform/data/servicebus_store/itas
sudo chown -R 1000:1000 /platform/data/servicebus_store/itas
sudo chown -R 1000:1000 /platform/data/attachment_store/itas

  5. Install mule_run (one time activity, not required if you are upgrading / already have mule_run installed)

    cd /tmp
sudo wget -q https://repository.mulesoft.org/nexus/content/repositories/public/org/mule/distributions/mule-standalone/3.9.0-hf2/mule-standalone-3.9.0-hf2.zip
sudo unzip -qq mule-standalone-3.9.0-hf2.zip
sudo mv mule-standalone-3.9.0-hf2 /platform/data/mule_run
sudo chown -R 1000:1000 /platform/data/mule_run

Start installation

Execute below commands to start installation

cd /platform/deployment/itas-deployment-2.0.0-onprem/itas-deployment-2.0.0/deploy
chmod +x onprem_stack.sh
./onprem_stack.sh deployall

Post Deployment Actions

Run the below command to clean up older unused volumes, images, etc after deployment.

#run command to delete all the unused docker images (This command will not delete docker images that are in use)
docker rmi -f $(docker images | awk '{ print $3 }') > /dev/null 2>&1

#cleanup unsed volume, cache etc.
docker system prune

To check logs 

sudo tail -f `docker inspect --format='{{.LogPath}}' itas_muledb_migration`

Troubleshoot Errors

  1. If we get the below "permission denied error" : Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.37/containers/redis/stop: dial unix /var/run/docker.sock: connect: permission denied.

    [lumauser@lumatrialweb01 deploy]$ docker ps --> If permission denied comes then execute below command.

[lumauser@lumatrialweb01 deploy]$ sudo setfacl -m user:lumauser:rw /var/run/docker.sock

[lumauser@lumatrialweb01 deploy]$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES 

[lumauser@lumatrialweb01 deploy]$ docker login (Enter docker credentials)

  • Ensuring that if the deployment is completed or not :   
     Whenever we enter "Docker ps" command then we can see the status of the containers, If any container's status is less than 1 minute then focus on that and wait 1 or 2 minutes and issue again the same 'docker ps' command , if we see the same container's status is less than a minute then we can ensure that there will be some issue and later we can go ahead with "docker logs [container_name]"  

    deploy]$ docker ps
CONTAINER ID   IMAGE                                                         COMMAND                  CREATED        STATUS        PORTS                                                                                              NAMES
f265d8a51ccc   registry-1.docker.io/serviceaide/sa_tunneling_service:1.0.0   "sh -c /opt/app/starâ¦"   19 hours ago   Up 18 hours   0.0.0.0:2504->2504/tcp, 0.0.0.0:4504->4504/tcp, 0.0.0.0:10095->10095/tcp                           sa_tunneling_service
4c778259bf49   registry-1.docker.io/serviceaide/itas_mule_adaptor:1.0.0      "sh -c /opt/app/starâ¦"   19 hours ago   Up 19 hours   0.0.0.0:7502->7502/tcp, 0.0.0.0:2106->2502/tcp, 0.0.0.0:2206->4502/tcp                             itas_mule_adaptor
a1bdb2668b05   registry-1.docker.io/serviceaide/itas_service_bus:1.0.0       "sh -c /opt/app/starâ¦"   19 hours ago   Up 19 hours   0.0.0.0:7505->7505/tcp, 0.0.0.0:61516->61516/tcp, 0.0.0.0:2102->2505/tcp, 0.0.0.0:2202->4505/tcp   itas_service_bus
7d759c5efb61   mule_run:1.0.0                                                "sh -c /opt/app/starâ¦"   20 hours ago   Up 19 hours                                                                                                      mule_run
  • No labels