Installing a CTERA Secured Enterprise File Services Platform Instance

Creating a Portal Instance

To create a CTERA Secured Enterprise File Services Platform:

1. Log in to the IBM Cloud console.
   
2. Search for CTERA or Secured Enterprise File Services Platform.
   
3. Click Secured Enterprise File Services Platform.
   The Secured Enterprise File Services Platform page is displayed.
   
   The CTERA Secured Enterprise File Services Platform is created using a Terraform template in a CTERA specific workspace.
4. Scroll down and under Review your pricing plans you see that you need a license which you get from CTERA support.
   Note

   You enter the license after the installation completes. Without a license you can continue using a 30 day trial license that is included with the Secured Enterprise File Services Platform.

5. Under Configure your workspace provide a name for the workspace and the Location for the workspace.
   
6. Scroll down and specify the Secured Enterprise File Services Platform details under Set the input variables.
   
   instance_name – The name you want for Secured Enterprise File Services Platform.
   profile – The size of the virtual instance. In a small or test environment, with a single server deployment, bx2-2x8 is sufficient. In a production environment, with a multi-node deployment, the primary database servers requires** bx2-4x16**. When an application server will handle up to the maximum 10,000 clients, CTERA recommends bx2-8x32.
   region – The region where the VPC is located.
   security_group – The name you want forthe security group.
   ssh_key_name – The name of the SSH key. For details, see Verifying the IBM Cloud Environment.
   subnet_id – The ID of the subnet that you want to use for the Secured Enterprise File Services Platform. The specified subnet is what determines the VPC that is used. For details, see Verifying the IBM Cloud Environment.
7. Confirm reading the CTERA EULA and click Install.
   
8. After the installation has completed, click VPC Infrastructure > Virtual server instances.
   
   The Virtual server instances for VPC page is displayed.
   
9. Click the virtual server instance just created.
   
10. Scroll down to Network interfaces.
    
11. Click the pencil icon to the right of the network interface to edit the interface to add an external, floating, IP.
    
12. In the Floating IP box, select Reserve a new floating IP.
    
13. Click Save.
    
14. For the primary database server and secondary, replication, server, click the virtual server instance.
    
    1. Scroll down to Storage volumes.
    2. Click Attach.
       
    3. Click in Block Volumes and select Create a data volume.
       
    4. Enter the following:
       Name – A name to uniquely identify the archive pool disk.
       Size – The size of the archive pool disk.
       Note

       The minimum archive pool should be 200GB but it should be sized around 2% of the expected global file system size.

       Profile – Use the smallest tier: 3 IOPS/GB (General Piurpose).
    5. Click Save.
       
       The server instance is defined with a floating, public, IP that can be used to access the CTERA Portal.
       
15. 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 an archive pool.

On the primary database server and when PostgreSQL streaming replication is required, also on the secondary, replication, server, create an archive pool.

To create the data and archive pools:

1. Click the 3 vertical dots to the right of the instance and select Open VNC console.
2. Log in to the CTERA Portal as root, with the password ctera321.
3. Run the following command: fdisk –l.
4. Run the following command to create the data pool: portal-storage-util.sh create_storage Device
   Where Device is the name of the non-boot volume listed when fdisk -l was run. For example, portal-storage-util.sh create_storage vdd
   This command creates both a logical volume and an LVM volume group using the specified device. Therefore, multiple devices can be specified if desired. For example: `portal-storage-util.sh create_db_archive_pool vdd vde vdf'
5. 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.
   For example: portal-storage-util.sh create_db_archive_pool vde
6. Run the following command to start the portal: portal-manage.sh start