Installing CTERA Portal Instances
  • 30 Nov 2022
  • 4 Minutes to read
  • Dark
    Light
  • PDF

Installing CTERA Portal Instances

  • Dark
    Light
  • PDF

Use the following workflow to install CTERA Portal in a GCP environment.

  1. Creating a Portal Instance.
  2. Optionally, configure a default gateway.
  3. For the first server you install, follow the steps in Configuring the Primary Server.
  4. For any additional servers beside the primary server, install the server as described below and configure it as an additional server, as described in Installing and Configuring Additional CTERA Portal Servers.
  5. Make sure that you replicate the database, as described in Configuring the CTERA Portal Database for Backup.
  6. Backup the server as described in Backing Up the CTERA Portal Servers and Storage.

Creating a Portal Instance

To access the CTERA Portal disk image you must supply CTERA support with the email address you use to access GCP.

Note

You do not need to provide CTERA support with any passwords.

To create the CTERA Portal server instance in Google Cloud:

  1. Create an SSH key to access the instance from another instance. This is required when defining additional severs.
  2. Log in to your Google Cloud Platform as a user with rights to deploy images and create virtual machines and storage.
    image.png
  3. Select a project from the Select a project drop-down.
  4. Click Compute Engine > Snapshots in the navigation menu.
    The Snapshots page is displayed.
    image.png
  5. Click CREATE SNAPSHOT SCHEDULE.
    Note

    If the CREATE SNAPSHOT SCHEDULE is not displayed, click the three vertical dots to display it.

    The Create a Snapshot schedule page is displayed.
    image.png
  6. Name the schedule and provide the following:
    Region – The region for this schedule. This should be the same region as the VM instance.
    Schedule frequency – The frequency for taking the snapshots.
    Start time – The start time to take each snapshot.
    Autodelete snapshots after – How long to keep each snapshots.
  7. Select the Deletion rule.
  8. Leave all the other settings with their defaults and click CREATE.
  9. 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.
    image.png
  10. Click CREATE INSTANCE.
    The Create an instance page is displayed.
    image.png
  11. 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.
  12. 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.
    Note

    The number of cores and memory depends on the type of server you want. For details, see Requirements

    Cores – The number of CPUs.
    Memory – The machine RAM.
    image.png
  13. Click CHANGE under Boot disk to select the CTERA Portal image.
    The Boot disk window is displayed.
    image.png
  14. Click CUSTOM IMAGES.
  15. Select the project supplied by CTERA Support, to be able to select the portal image.
  16. Select the image from the Image drop-down.
  17. For production, CTERA recommends changing the Boot disk type to SSD persistent disk.
  18. Change Size (GB) to 110.
  19. Click SELECT.
  20. Under Firewall, check Allow HTTP traffic and Allow HTTPS traffic.
  21. Click the NETWORKING, DISKS, SECURITY, MANAGEMENT, SOLE-TENANCY link and click Disks.
    image.png
  22. Click ADD NEW DISK.
  23. Specify the following disk configuration.
    Name – A unique name to identify the disk.
    Description – An optional description of the disk.
    Disk type – The type of disk. For production, CTERA recommends SSD persistent disk.
    Size – The disk size. The minimum disk requirement is 110GB. See Requirements. Prior to going to production, contact CTERA Support to evaluate whether the attached drive's performance meets CTERA's main database performance requirements.
    Snapshot schedule (Recommended) – Select the snapshot schedule defined in step 8.
  24. Leave all the other settings with their defaults and click SAVE.
  25. Click Security.
  26. Click MANAGE ACCESS.
  27. Click ADD ITEM.
  28. Paste the generated public key in Public key.
    Note

    The content of the public key file typically starts with ssh-rsa and ends with your user ID.

  29. Leave all the other settings with their defaults and click CREATE.
    The VM is created and powered on.
    image.png
    Note the Zone and External IP address. The external IP is the address you use to access the portal.
  30. 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 data pool defined previously.
  31. List the disks to identify the name of the added disk: fdisk -l
    image.png
  32. Create the CTERA Portal data disk: portal-storage-util.sh create_xfs_storage sdb
    where sdb is the disk for the portal data.
  33. Edit /etc/ctera/portal.cfg and add the Google Cloud Platform zone specified in step 11 as the value for the CTERA_GC_REGION parameter.
    # CTERA portal Google specific parameters
    ### Google Parameters ###
    # CTERA_GC_REGION - Google Availability Zone
    CTERA_GC_REGION=<enter_zone_from_step_11>
    
  34. start the portal server: portal-manage.sh start
    The data disk is mounted to the portal data folder /usr/local/lib/ctera and the portal starts.

Was this article helpful?