- 17 May 2023
- 3 Minutes to read
Creating a Portal Instance
- Updated on 17 May 2023
- 3 Minutes to read
Use the following workflow to install CTERA Portal on each virtual machine in a GCP environment.
- Creating a Portal Instance.
- Configuring a Default Gateway.
- For the first server you install, follow all of the steps in Configuring the CTERA Portal Primary Server.
- For any additional servers besides the primary server, configure the server as an additional server as described in Installing Additional CTERA Portal Servers.
- Make sure that you replicate the database, as described in Backing Up the Database
To access the CTERA Portal disk image you must supply CTERA support with the email address you use to access GCP.
You do not need to provide CTERA support with any passwords.
To create the CTERA Portal server instance in Google Cloud:
- Log in to your Google Cloud Platform as a user with rights to deploy images and create virtual machines and storage.
- Select a project from the Select a project drop-down.
- Click Compute Engine > VM instances in the Navigation menu.
Note: If the Compute Engine API is not enabled for the project, click ENABLE.
The VM Instances page is displayed.
- Click CREATE INSANCE.
The Create an instance page is displayed.
- Specify the portal virtual machine configuration.
Name – A unique name to identify the portal virtual machine.
Region – The location you want to host the virtual machine.
Zone – The zone within the location to host the virtual machine.
- Under Machine Configuration, select the Machine family and Series. CTERA recommends using the General-purpose family and the E2 series.
- Under Machine type, select the Custom option from the drop-down and specify the cores and memory.
Cores – The number of CPUs. 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.
Memory – The machine RAM. 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.
- Click Change under Boot disk to select the CTERA Portal image.
The Boot disk window is displayed.
- Click Custom images, and from the Show images from drop-down select the project supplied by CTERA support to choose the portal image.
- Select the image from the Image drop-down.
- For production, CTERA recommends changing the Book disk type to SSD persistent disk
- Change Size (GB) to 110 and click Select.
- Under Firewall, check Allow HTTP traffic and Allow HTTPS traffic.
- Click the Management, security, disks, networking, sole tenancy link and click the Disks tab.
- Click Add new disk.
- Specify the following disk configuration.
Name – A unique name to identify the disk.
Description – An optional description of the disk.
Type – The type of disk. For production, CTERA recommends SSD persistent disk.
Size (GB) – The disk 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.
- Click Done.
- Leave all the other settings with their defaults and click Create.
The VM is created and powered on.Note the Zone and External IP address. The external IP is the address you use to access the portal.
- Click SSH to log in to the virtual machine using the account SSH user and key and switch to root by running sudo -i.
You have to configure the CTERA portal to recognize the storage datapool defined in steps 15 to 16.
- List the disks to identify the name of the added disk.
- Create the CTERA Portal logical volume from the disk:
portal-storage-util.sh create_storage /dev/sdb
where /dev/sdb is the disk for the portal data.A volume group and logical volume called DataPool are created.
- Edit /etc/ctera/portal.cfg and add the Google Cloud Platform zone specified in step 5 as the value for the CTERA_GC_REGION parameter.
# CTERA portal Google specific parameters
### Google Parameters ###
# CTERA_GC_REGION - Google Availability Zone
- start the portal server: # portal-manage.sh start
The portal starts.