- 17 May 2023
- 4 Minutes to read
Creating a Portal Instance
- Updated on 17 May 2023
- 4 Minutes to read
Use the following workflow to install CTERA Portal on each virtual machine.
- To get the image from CTERA support.
- To create the CTERA Portal server 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.
The portal image used to create the CTERA Portal instance is obtainable from CTERA support at http://support.ctera.com and needs to be moved to your Azure portal, using Azcopy.exe, available for download from https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10. The zip file contains the azcopy.exe program.
To get the image from CTERA support at http://support.ctera.com:
- Log in to your Azure portal and access the Storage Accounts service to display the images.The list of available storage accounts is displayed.
- Either create a new storage account for the image or click the storage account to use for the image.
- The storage account details are displayed.
- Click Access Keys under Security + Networking in the navigation menu and note the Storage account name and the Key 1 key value.
Note: Click Show keys to display the key.
- Click Storage browser (preview) in the navigation menu and then click Blob containers and select Add container.
The New container blade is displayed.
- Enter a name for the container and click Create.
- Click the container.
- Click Shared access signature a under Security + Networking in the navigation menu.
The Shared access signature page is displayed.
- Set the permissions and click Create.
- Copy the URI that is generated and save it.
The URI includes a shared access key.
To get the image:
- Run the following command from the folder where you saved AzCopy.exe:
AzCopy.exe cp "<source_uri>" "<destination_uri>"
source_uri – The source URI location and path of the image file obtained from CTERA.
destination_url – The destination URL - the storage account.
The image is copied to the container. This can take some time.
To create the CTERA Portal server instance:
Log in to your Azure portal and access the Images service to display the image obtained from CTERA support.The list of available images is displayed.
Click the image for the CTERA Portal.
The image details are displayed.
Click Create VM.
The Create a virtual machine blade is displayed.
Enter the following in the Basics tab for the virtual machine.
Resource group – The resource group to be used. The resource group must use premium storage.
Virtual machine name – A name to uniquely identify the virtual machine.
Region – The region to host the virtual machine.
Size – Click See all sizes to display the available VM sizes.
The Select a VM size blade is displayed.
Select a VM that matches your requirements.
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, 4 CPU cores and 110GB local hard disk drive. In a small or test environment, with a single server deployment, the requirement is a 64-bit virtual machine with minimum 8GB RAM, 2 CPU cores.
Preview servers require at least 16GB of RAM, 4 CPU cores, and 60GB of magnetic drive.
Authentication type – Choose Password.
Username – A name to access the virtual machine. This is an administrator name that can access the portal.
Note: Once the virtual machine has been fully configured, CTERA provides a user name and password, but this user name can also be used.
Password – Enter a password to access the instance.
Confirm password – Reenter the password.
Select inbound rules – Select HTTP (80) and HTTPS (443) from the drop-down list.
Licensing type – Select Other.
Leave the other values with their defaults.
Click the Networking tab.
Click the Review + create.
Note: If validation does not pass, click the Networking tab again and then click Review + create again.
Review the virtual machine details and click Create.
The machine is deployed and started automatically.The machine is started automatically.
Click Go to resource to display its details.
The virtual machine includes two default disks. The OS disk is used for root, and a data disk, which is used to store the CTERA Portal database.
To add disks, see Extending the CTERA Main Database Storage Pool.
Note the Public IP address.
Click Networking, under Settings in the navigation menu to add inbound and outbound port rules.
In the Inbound port rules tab, click Add inbound port rule.
The Add inbound security rule window is displayed.
Click Add inbound port rule to add the following inbound port rules, incrementing the Priority for each rule by 10 and clicking Add after adding each rule:
Service Destination port ranges Protocol Priority Name Notes Custom 995 TCP 330 CTTP DNS (UDP) - - 340 DNS PostgreSQL - - 350 PostgreSQL Does not need to be accessible from the Internet. Custom 18682 TCP 360 Preview Does not need to be accessible from the Internet.
Select the Outbound port rules tab and click Add outbound port rule.
The Add outbound security rule window is displayed.
Add the following ports.NoteYou need to change the Name field, ifit was used for the inbound port.
|Service||Destination port ranges||Protocol||Priority||Name||Notes|
|Custom||18682||TCP||130||Preview1||Does not need to be accessible from the Internet.|
|SMTP||-||-||160||SMTP||25 is the default SMTP port. You can define a custom port for a port used in your environment.|