Installing CTERA Portal Instances
  • 15 Dec 2022
  • 4 Minutes to read
  • Dark
    Light
  • PDF

Installing CTERA Portal Instances

  • Dark
    Light
  • PDF

Use the following workflow to install CTERA Portal.

  1. Creating a Portal Instance using a CTERA Portal image obtainable from CTERA support.
  2. Logging In to the Server to Create the Storage.
  3. Configuring Network Settings.
  4. Optionally, configure a default gateway
  5. Additional Installation Instructions for Customers Without Internet Access.
  6. For the first server you install, follow the steps in Configuring the Primary Server.
  7. 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.
  8. Make sure that you replicate the database, as described in Configuring the CTERA Portal Database for Backup.
  9. Backup the server as described in Backing Up the CTERA Portal Servers and Storage.
Note

You can use block-storage-level snapshots for backup, but snapshots are periodical in nature, configured to run every few hours. Therefore, you cannot recover the metadata to any point-in-time, and can lose a significant amount of data on failure. Also, many storage systems do not support block-level snapshots and replication, or do not do so efficiently.

Creating a Portal Instance

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:

  1. Log in to the OpenStack console and access Admin > Images.
    image.png
  2. Click Create Image.
    The Create An Image screen is displayed.
    image.png
  3. Specify the details for the image.
    Name – A unique name to identify the image.
    Description – An optional description of the image.
    Image Source – Select Image File.
    Image File – Browse to the OpenStack image received from CTERA.
    Format – Select QCOW2 - QEMU Emulator.
    Architecture – Leave blank.
    Minimum Disk – See General Requirements. The disk requirement is 100GB. Prior to going to production, contact CTERA support to evaluate whether the attached drive's performance meets CTERA's performance requirements.
    Minimum RAM – See General Requirements.
    Leave both Public and Protected checkboxes with their default values.
  4. Click Create Image.
    The image is created. This can take a few minutes.
  5. Access Project > Compute > Instances.
    image.png
  6. Click Launch Instance.
    The Launch Instance screen is displayed.
    image.png
  7. 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 the flavor that meets the requirements. See Requirements.
    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.
  8. Click the Network tab and drag the ‘internal_network‘ option to Selected networks.
    image.png
  9. Click Launch.
    image.png
  10. For the portal instance, under Actions select Associate Floating IP.
    image.png
    The Manage Floating IP Associations window is displayed.
    image.png
  11. Select an IP address and click Associate.
    Refreshing the Instances screen displays the portal with the selected IP.
  12. Access Project > Compute > Volumes.
  13. Click Create Volume.
    The Create Volume screen is displayed.
    image.png
  14. Specify the details for the image.
    Volume Name – A unique name to identify the volume.
    Description – An optional description of the volume.
    Volume Source – Select ‘No source, empty volume‘
    Type – Select iscsi
    Size – See General Requirements.
    Availability Zone – Select the same availability zone used for the image.
  15. Click Create Volume.
    The volume is created. This can take a few minutes.
  16. For the new volume, under Actions select Manage Attachments.
    image.png
    The Manage Volume Attachments window is displayed.
    image.png
  17. Select the portal instance and click Attach Volume.
  18. Note the location of the storage.
    image.png
  19. For the primary database server and secondary, replication, server, access Project > Compute > Volumes.
    1. Click Create Volume.
      The Create Volume screen is displayed.
    2. Specify the details for the image.
      Volume Name – A unique name to identify the volume.
      Description – An optional description of the volume.
      Volume Source – Select ‘No source, empty volume‘
      Type – Select iscsi
      Size – See General Requirements.
      Availability Zone – Select the same availability zone used for the image.
    3. Click Create Volume.
      The volume is created. This can take a few minutes.
    4. For the new volume, under Actions select Manage Attachments.
      The Manage Volume Attachments window is displayed.
    5. Select the portal instance and click Attach Volume.
    6. Note the location of the storage.
  20. Continue with Logging in to the Server to Create the Storage.

Logging in to the Server to Create the Storage

You need to create a data pool and on the primary database server, and when PostgreSQL streaming replication is required, also on the secondary, replication, server, an archive pool. See Using PostgreSQL Streaming Replication for details about PostgreSQL streaming replication.

Access the new portal machine, using SSH, with the floating IP.

To log in to the portal server:

  • Log in as the root user using SSH.
    The default password is ctera321

You are prompted to change the password on your first login.

To create the data and archive pools:

  1. Log in as the root user using SSH.
  2. Run fdisk -l to identify the disks to use for the data and archive pools.
  3. Run the following command to create the data pool: portal-storage-util.sh create_storage Device
    where Device is the Device name of the disk to use for the data pool.
  4. Run the following command to create the archive pool: portal-storage-util.sh create_db_archive_pool Device
    Where Device is the Device name of the disk to use for the archive pool.
  5. Start CTERA Portal services, by running the following command: portal-manage.sh start

Was this article helpful?