Deploy Volumez on PostgreSQL
  • 22 Dec 2024
  • 1 Minute to read
  • Dark
    Light

Deploy Volumez on PostgreSQL

  • Dark
    Light

Article summary

Launching a New Deployment on OCI Stacks

The Stack will automatically execute the following high-level tasks:

  1. Deploy OCI instances with the selected specifications (OCPUs, RAM, etc.) to meet performance targets.

  2. Create and provide access a new Volumez account.

  3. Install PostgreSQL in the specified version.

First, click on the Volumez offering in the OCI Marketplace:


Step 1: Configure the Deployment Variables

  1. Navigate to the Stacks OCI Console by clicking Launch Stack in the Volumez OCI Marketplace.

  2. Click Next

  3. Select the Stack and go to Resources > Variables.

  1. Click Edit Variables and configure the following:

    • Choose the Availability Domain where instances will be deployed.

    • Provide your email address and set a password for logging into the Volumez DIaaS platform.

    • Select the desired deployment size (Medium / Large) and PostgreSQL version (13 through 16).

  2. Click Next.

  1. Check the "Run Apply" box and click Save Changes.

  1. Under Application Information:

Note: The deployment process will take approximately 5 minutes. Once completed, you can view details in the Application Information tab.

  1. When the deployment is finished the following details can be viewed:


Step 2: Connect to the Application Node Running PostgreSQL

To connect to the application node:

  1. Navigate to the Application Information tab and note the following details:

    • IP Address

    • SSH Key

  1. Save the SSH key file from the OCI Stacks output as key.pem.

  2. Modify the key file's permissions:

    chmod 600 key.pem
    
  3. Use the SSH key to connect to the application node:

    ssh -i key.pem <username>@<AppNode_Public_IP>
    

Example:

ssh -i key.pem ubuntu@192.0.0.1

Note:

In case a deployment runs for longer than 10 minutes, an error “operation timeout” will appear and the deployment job will fail.

If in case the last state: ‘Provisioning’, no VM was available during the deployment time.

Solution: deploy the stack again choosing a different AD (Availability Domain).


Was this article helpful?