getting-started-software.md

copyright	lastupdated	keywords	subcollection
years 2017, 2024	2024-08-29	get started with schematics, infrastructure management, infrastructure as code, iac, schematics cloud environment, schematics infrastructure, schematics terraform, terraform provider	schematics

{{site.data.keyword.attribute-definition-list}}

Software deployment in {{site.data.keyword.bplong_notm}}

{: #get-started-software}

Try out one of the {{site.data.keyword.IBM}} provided software templates to quickly spin up a classic Virtual Server Instance (VSI), and automatically configure the instance to connect to an {{site.data.keyword.databases-for-postgresql_full}} instance. {: shortdesc}

With {{site.data.keyword.bplong_notm}}, you can choose from a wide variety of software and infrastructure templates{: external} that you can use to set up {{site.data.keyword.cloud_notm}} services, and to install {{site.data.keyword.IBM_notm}} and Third party software. The templates are applied by using the built-in Terraform, Ansible, Helm, CloudPak, and Operator capabilities in {{site.data.keyword.bpshort}}.

As part of this getting started tutorial, you create a {{site.data.keyword.bpshort}} workspace that points to the VSI database{: external} template. Then, you run this template and watch {{site.data.keyword.bpshort}} provision your VSI and your {{site.data.keyword.databases-for-postgresql_full_notm}} instance. {{site.data.keyword.databases-for-postgresql_full_notm}} is a fully managed database offering in {{site.data.keyword.cloud_notm}} that supports storing of non-relational and relational data types. For more information about this offering, see What is PostgreSQL?{: external}.

This getting started tutorial incurs costs. You must have an {{site.data.keyword.cloud_notm}} Pay-As-You-Go or Subscription{: external} account to proceed. Make sure that you review pricing information for classic VSIs{: external} and PostgreSQL{: external}. {: important}

Before you begin

{: #vsi-postgres-prereq}

Before you can use this template, you must complete the following tasks.

• Make sure that you have the permissions to create classic virtual servers.
• Create a classic API key and retrieve your classic infrastructure username. This username and API key are used to verify that you have sufficient permissions to create classic infrastructure.
• Make sure that you have the permissions to create an {{site.data.keyword.databases-for-postgresql_full_notm}} instance.

Setting up and configuring a classic VSI to run PostgreSQL with {{site.data.keyword.bpshort}}

{: #vsi-postgres}

Use one of the IBM provided software templates to set up and configure a classic VSI so that you can store data in an instance of {{site.data.keyword.databases-for-postgresql_full_notm}}. {: shortdesc}

1. Login to your {{site.data.keyword.cloud_notm}} account.

2. Open the VSI database software template from the {{site.data.keyword.cloud_notm}} catalog.

   Observe {{site.data.keyword.cloud_notm}} is specified in Select your deployment target and Terraform Version 1.5.0 or Terraform Version 2.0.0 is displayed in Select a delivery method. {: note}

3. In the Configure your workspace section, enter Name for your {{site.data.keyword.bpshort}} workspace, select your Resource group, and the Location where you want to create the workspace.

4. Check Override default Terraform version to configure the template to support your Terraform version.

5. In the Set the deployment values section, enter the following information.

   • Click Yes toggle button to enter value for admin-password as user123, and db-user-password as user123 that you want to use to log in to your PostgreSQL instance.

     The admin-password and db-user-password must be between 10 and 32 characters long and do not support any special characters. {: note}

   • Enter the iaas_classic_username as <your classic_username> that you retrieved earlier. For more information about how to retrieve this information, see Creating a classic infrastructure API key.

   • Select the resource group where you want to provision your virtual server and PostgresSQL instance.

6. Accept the license agreement, and click Install. You are redirected to the {{site.data.keyword.bpshort}} workspace Activity page where you can monitor the progress of your VSI and PostgreSQL setup. Note that it takes a few minutes for the setup to complete.

7. Verify your virtual server and PostgreSQL setup.

   • From the workspace Resources page, find the virtual server and PostgreSQL instance that were created for you.
   • Click the link to see the details of your instances.

8. Optional: Remove your {{site.data.keyword.bpshort}} workspace and all related {{site.data.keyword.cloud_notm}} resources.

   • Select the Actions drop down list, click Delete.
   • Select the Delete workspace and Delete all associated resources option.
   • Enter the name of your workspace, and click Delete.

You used the capabilities of {{site.data.keyword.bpshort}} to provision {{site.data.keyword.cloud_notm}} infrastructure and database services, and automatically configured your services to allow network communication.

What's next?

{: #whats-next}

• Explore the capabilities of {{site.data.keyword.databases-for-postgresql_full_notm}}.
• Browse other software and infrastructure templates{: external} that you can apply with {{site.data.keyword.bpshort}}.
• Learn more about the built-in capabilities in {{site.data.keyword.bpshort}}.
• Import your {{site.data.keyword.bpshort}} templates and create your private {{site.data.keyword.cloud_notm}} catalog.
• Set up the {{site.data.keyword.bpshort}} CLI or API to start automating the provisioning and management of {{site.data.keyword.cloud_notm}} resources.