Creating a Portal Instance
You can install the CTERA Portal on Nutanix AHV via the Nutanix Prism Central console.
To install the CTERA Portal Server in Nutanix:
1 Log in to the Nutanix Prism Central console.
The dashboard is displayed.
2 Click Home > Settings in the top bar.
The Settings page is displayed.
3 Click Image Configuration in the navigation pane.
The Image Configuration page is displayed.
4 Click Upload Image.
The Create Image window is displayed.
5 Specify the details for the portal image.
Name – A unique name to identify the image.
Annotation – An optional description of the image.
Image Type– Set to DISK.
Storage Container – Select the storage container.
6 Choose the Upload a file option and browse to the qcow2 image file from CTERA support.
7 Click Save.
The progress of the image creation is displayed in the page under the top bar.
8 Click Settings > VM in the top bar.
The VM page is displayed.
9 If necessary, change the view from Overview to Table, to list all the VMs.
10 Click Create VM.
The Create VM window is displayed.
11 Specify the details for the VM.
Name – A unique name to identify the portal.
Description – An optional description of the portal.
Timezone – The timezone for the VM. The default is the local timezone.
Use this VM as an agent VM – Leave unchecked.
vCPU(s) – The number of vCPUs.
Note: In a production environment, with a multi-node deployment, the application and database servers each require a 64-bit virtual machine with minimum 4 CPU cores. In a small or test environment, with a single server deployment, the requirement is a 64-bit virtual machine with minimum 2 CPU cores.
Number Of Cores Per vCPU – The number of cores per vCPU. Leave the default value.
12 Scroll down to complete the details for the VM.
Memory – The memory usage.
Note: In a production environment, with a multi-node deployment, the application and database servers each require a 64-bit virtual machine with minimum 16GB RAM. In a small or test environment, with a single server deployment, the requirement is a 64-bit virtual machine with minimum 8GB RAM.
Disks – Add a disk. The minimum disk requirement is 110GB. When deploying a main database server or a catalog node to production, it is recommended to attach a disk sized 2% of the overall cloud storage you intend to allocate for the service. Prior to going to production, contact CTERA Support to evaluate whether the attached drive's performance meets CTERA's main database and catalog node performance requirements.
a Click Add New Disk.
The Add Disk window is displayed.
b Specify the details for the disk.
Type – The type of disk. Select DISK.
Operation – Select the Clone from Image Service from the drop-down list.
Image – Select the CTERA portal image from the drop-down list.
c Leave the other fields with the default values and click Add.
13 Under Boot Configuration, choose the Legacy BIOS option and select the added disk to be the boot device in the Set Boot Priority text box.
14 Add a second disk for the portal database data.
a Click Add New Disk.
The Add Disk window is displayed.
b Specify the details for the disk.
Type – The type of disk. Select DISK.
Operation – Select the Allocate from Storage Container from the drop-down list.
Storage Container – Select the storage container from the drop-down list.
Size (GiB) – The disk size. The minimum disk requirement is 110GB. When deploying a main database server or a catalog node to production, it is recommended to attach a disk sized 2% of the overall cloud storage you intend to allocate for the service. Prior to going to production, contact CTERA Support to evaluate whether the attached drive's performance meets CTERA's main database and catalog node performance requirements.
c Leave the other fields with the default values and click Add.
Note: In a production environment, when creating the database server you need two disks (the second added disk is for the archive). When creating the preview server you need to add one disk.
15 Optionally, follow your site best practices to ensure optimal performance of the VM on the cluster, in cases of node failure.
The Set VM Host Affinity window is displayed.
a Under VM Host Affinity, click Set Affinity to enable the VM to another host in the cluster.
b Select the hosts under which the VM will run in the case of a node failure.
c Click Save.
16 Click Save.
The VM is created.
17 From the list of virtual machines (Table view), select the new virtual machine and scroll down to display details of the VM.
18 Click Power On.
The VM is powered on and the Launch Console option is enabled.