How to Install Runtime Fabric in Linux 7.8 (localhost)

As, we have cloud and on-prem version of runtime, which can be used to deploy mule applications. In addition, MuleSoft provides a customer hosting solution, which we can use to automate and orchestrate integration services within an organization.

Tutorial

Step 1

Prepare infrastructure with pre-requisite recommendations, by MuleSoft. 

Runtime fabric Pre-requisites

Step 2

Create fabric in Runtime manager in the required environment. [Which will be in an inactive state]

Note: Please, copy and keep activation data safe as it will be required in configuration script.

Step 3

Adhere to the following:

To perform a manual installation of Runtime fabric application on localhost, below keys need to be assigned with value in the generate config.sh file ... 

• * RTF_CONTROLLER_IPS.
• * RTF_WORKER_IPS
• * RTF_ACTIVATION_DATA 
• * RTF_DOCKER_DEVICE 
• * RTF_ETCD_DEVICE 
• and 
• * RTF_MULE_LICENSE

Step 5

Below are the configurations for controller instance.

                                   [Controller required minimum 2 CUPs ] 

[root@localhost manual]# fdisk -l 

Disk /dev/sdc: 21.5 GB, 21474836480 bytes, 41943040 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 label type: dos Disk identifier: 0x0001cf67 

   Device Boot      Start         End      Blocks   Id  System /dev/sdc1   *        2048     2099199     1048576   83  Linux /dev/sdc2         2099200    41943039    19921920   8e  Linux LVM 

Disk /dev/sdb: 107.4 GB, 107374182400 bytes, 209715200 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/sda: 128.8 GB, 128849018880 bytes, 251658240 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 label type: dos Disk identifier: 0xdd338791 

   Device Boot      Start         End      Blocks   Id  System /dev/sda1            2048   251658239   125828096   83  Linux 

Disk /dev/mapper/rhel-root: 18.2 GB, 18249416704 bytes, 35643392 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/mapper/rhel-swap: 2147 MB, 2147483648 bytes, 4194304 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 

[root@localhost manual]# 

[root@localhost manual]# df -h Filesystem           

  Size  Used Avail Use% Mounted on devtmpfs              

  4.3G     0  4.3G   0% /dev tmpfs                 

 4.3G     0  4.3G   0% /dev/shm tmpfs                  

 4.3G  8.9M  4.3G   1% /run tmpfs                 

 4.3G     0  4.3G   0% /sys/fs/cgroup /dev/mapper/rhel-root   

17G  5.3G   12G  31% / tmpfs                  

870M     0  870M   0% /run/user/1000 /dev/sda1              

120G   11G  110G  10% /var/lib/gravity /dev/sdc1            

 1014M  159M  856M  16% /var/lib/gravity/planet/etcd tmpfs                 

 870M     0  870M   0% /run/user/0 [root@localhost manual]#

* It required to ensure that while creating file system below partitions should not be mounted with directories (filesystems).

• # RTF_DOCKER_DEVICE:    (default /dev/xvdb)
• RTF_DOCKER_DEVICE='/dev/sdb1'
• # RTF_ETCD_DEVICE:    (default /dev/xvdc)
• RTF_ETCD_DEVICE='/dev/sdc1'

*Although Runtime fabric manages chrony service installation on server but to be sure, if it should be installed as pre-requisite and enabled before starting init.sh script. (Chrony is an implementation of the Network Time Protocol). 

Step 5

Now execute init.sh file to install in the controller server. 

Below are a few initial logs.

Few sections of the final execution output of init.sh script.

Once we are in the final execution of init.sh process. which takes a few moments to start fabric, please be patient, it will be available and active in a few moments.

It's up now in Runtime Fabric (Anypoint Runtime manager Control panel) with status active.

Learning: If resources are available with required configurations, rest actions and processes will be taken care of by script which is provided by MuleSoft and even there is no single correction or changes required in the script to accommodate the installation.

Observation: Runtime fabric validates required resources availability before moving forward to install it to the server instance. It reserves some extra resources with it to avoid any performance degradation. Hence do not worry if assigning it an extra resource for future use.

Hope it helps.