If the time displayed is incorrect, use the following command to adjust time for timezone as necessary (Otherwise, you might face SSL certificate problems later).įor instance if your timezone is 4:30:00 ahead of UTC, then run the following command in VM. The Date/Time would sometimes be incorrect as it uses local time as UTC To verify the change in Network Device Name, run the following command: Poweroff the machine by using Poweroff command and start again. Sample output cat ifcfg-ens34: DEVICE="ens34" Repeat the steps for enp0s8 and enp0s9 respectively.Add a new parameter with the MAC Address HWADDR=.Record the MAC addresses and go to the following directory: Use the following command to get your Network Device MAC address (Shown after link/ether) As the network is setup using DHCP, IP changes are bound to happen during restart, static IP configuration could be harder to maintain as it may not work for different VM with different network setups.The Network Device names may not be the exact same as listed above, for example, enp0s8, enp0s9, enp0s17 instead of enp0s3, enp0s8, enp0s9.You need to change the Network Device Name from enp0s3, enp0s8, enp0s9 to ens32, ens33 and ens34: Open the VM console, and login with the below credentials.īecome the root user by running this: sudo su -įor Oracle VM VirtualBox Users ONLY: Click here to expand the preboarding procedure. For VMware related troubleshooting, please refer to VM Documents.Import the OVA image by referring to these instructions.
The procedure to install CORTX on OVA is mentioned below.ĭownload the CORTX OVA file from our release page. For the same reason, please do not update the operating system in the image as that also might cause it to fail. Important: If you are running the VM in any of the VMWare hypervisors, it is not recommended to use VMware Tools, as CORTX may break due to kernel dependencies. If you are interested in development, please instead use these instructions Build CORTX from Source Code using Docker Recommended HypervisorsĪll of the following hypervisors should work: VMware ESX Server, Package Managers such as yum will not work in the OVA. Note: This is intended for simple testing to evaluate the CORTX system for the "look and feel" and for some basic functionality testing it is not intended for development purposes.
For our Japanese community, this document has been translated and is available here. The minimum recommended system should have at least 4 CPU cores, at least 8 GB of RAM, and at least 120 GB of local storage.
This document describes how to use a CORTX OVA for the purposes of single-node CORTX testing. An Open Virtual Appliance (OVA) is a Virtual Machine (VM) image that consists of a pre-installed and pre-configured operating system as well as one or more applications packaged for easy deployment and testing.