Creating a Portal Instance
- 21 Mar 2022
- 2 Minutes to read
- Print
- DarkLight
- PDF
Creating a Portal Instance
- Updated on 21 Mar 2022
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
You can install the CTERA Portal on KVM via the OpenStack console or another console. The following instructions describe how to install a CTERA Portal using the OpenStack console.
To install the CTERA Portal Server in OpenStack:
- Log in to the OpenStack console and access Admin > Images.
- Click Create Image.
The Create An Image screen is displayed. - Specify the details for the image.
Name – A unique name to identify the image.
Description – An optional description of the image.
Image Source – SelectImage File.
Image File – Browse to the OpenStack image received from CTERA.
Format – SelectQCOW2 - QEMU Emulator.
Architecture – Leave blank.
Minimum Disk – The minimum disk requirement is 110GB. When deploying a main database server 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 performance requirements.
Minimum RAM – For production CTERA recommends 16192MB. In a production environment, with a multi-node deployment, the application and database servers each require a 64-bit virtual machine with minimum 16192MB RAM. In a small or test environment, with a single server deployment, the requirement is a 64-bit virtual machine with minimum 8096MB RAM.
Leave both Public and Protected checkboxes with their default values. - Click Create Image.
The image is created. This can take a few minutes. - Access Project > Compute > Instances.
- Click Launch Instance.
The Launch Instance screen is displayed. - Specify the details for the image.
Availability Zone – Select the availability zone for the instance.
Instance Name – A unique name for the instance.
Flavor – Select a flavor with at least 8GB RAM and 2 CPUs, such asm2.medium.
In a production environment, with a multi-node deployment, CTERA recommends the application and database servers each require a minimum16GB RAM and 4 CPU cores. In a small or test environment, with a single server deployment, the minimum is 8GB RAM and 2 CPUs.
Instance Count – Leave the default value, 1.
Instance Boot Source – Select Boot from image.
Image Name – Select the image you created for the CTERA Portal. - Click the Network tab and drag the internal_network option to Selected networks.
- Click Launch.
- For the portal instance, under Actions select Associate Floating IP.
The Manage Floating IP Associations dialog is displayed. - Select an IP address and click Associate.
Refreshing the Instances screen displays the portal with the selected IP. - Access Project > Compute > Volumes.
- Click Create Volume.
The Create Volume screen is displayed. - Specify the details for the image.
Volume Name – A unique name to identify the volume.
Description – An optional description of the volume.
Volume Source – SelectNo source, empty volume.
Type – Selectiscsi.
Size – The minimum disk requirement is 110GB. When deploying a main database server 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 performance requirements.
Availability Zone – Select the same availability zone used for the image. - Click Create Volume.
The volume is created. This can take a few minutes. - For the new volume, under Actions select Manage Attachments.
The Manage Volume Attachments dialog is displayed. - Select the portal instance and click Attach Volume.
- Note the location of the storage.
Access the new portal machine, using SSH, with the floating IP.
Was this article helpful?