Contents x
How to deploy Corezoid on VMware Fusion
  • 10 Sep 2021
  • 1 Minute to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF
Contents

How to deploy Corezoid on VMware Fusion

  • Updated on 10 Sep 2021
  • 1 Minute to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF

Requirements

VMware Fusion version (Activated) 11 or later
CPU 4 (minimum) - 6 (recommended)
RAM 6GB (minimum) - 10GB (recommended)
HDD minimum 20GB free

Installation

Before installing image make sure you have installed and activated a paid version of VMware Fusion.

You won’t be able to deploy Corezoid on Trial version of VMware Fusion

  1. Go to Preferences and add a new Network interface:

image.png

image.png

image.png

If you have troubles with setting Subnet IP and Subnet Mask parameters, see the Troubleshooting section.

  1. To create a new virtual machine you need to drag your **.ovf file to Select the Installation Method modal window:

image.png

Select your existing virtual machine and click the Continue button:

image.png

  1. The installation will start:

image.png

  1. Click the Customize Settings button:

image.png

  1. Select the Network Adapter item in the list:

image.png

  1. Select your network interface:

image.png

  1. Start up your virtual machine:

image.png

  1. Finish the deployment:

image.png

Launching

A few minutes later, after the successful launch of the system, you can open a Corezoid in your browser.

Web access: https://172.16.0.254/ (or your value)
login: admin@corezoid.loc
password: Middleware2020-

SSH access:
Login: support
Password: corezoid
Get the superuser rights by using the command: sudo -i

Additional Information

After the image is installed, the IP address of the server is 172.16.0.254. If necessary, you can change the IP address.

To change the web endpoint (domain or IP), you must run a script which is located in: /root/fix_domain_crz.sh

SSH access:
Login: support
Password: corezoid
Get superuser by command: sudo -i

Monitoring and restarting

You can also monitor and restart applications via the monit:

Output of all the monitoring processes:

sudo monit status

Disabling monitoring of monit applications:

monit unmonitor all

Enabling the monitoring:

monit monitor all

If monit is used to start / stop the application, then stop / start the application using the monit
commands:

monit stop conveyor_api_multipart
monit start conveyor_api_multipart

Troubleshooting

If the following error occurs when starting the virtual machine:

image.png

You need to perform the following actions in the system security settings (System Preferences > Security & Privacy):

image.png

If you get these errors when configuring the subnet, set the Subnet Mask to 255.255.255.0 and Subnet IP value to 172.16.0.0.
Then you can change the Subnet Mask value to 255.255.255.192 and Subnet IP to 172.16.0.192:

image.png

image.png

What's Next