vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Multitiered landing zone with IAM and resource group access for a catalog offering](https://github.com/Cloud-Schematics/gcat-landing-zone-catalog) Provision a resource group, a VPC in the resource group, IAM access groups, and invites users to those access groups. This module configures the environment using a JSON object stored in Cloud Object Storage to allow users to configure and update complex environments as part of a catalog offering. This template do not use complex datatype. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/gcat-landing-zone-catalog&terraform_version=terraform_v1.0) <br> 
 [Multi-zone VPC with bastion using subnet](https://github.com/Cloud-Schematics/gcat-multizone-vpc-bastion-subnet) Provision multi-zone VPC with a bastion subnet in one zone by reusing a multitiered VPC template. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/gcat-multizone-vpc-bastion-subnet&terraform_version=terraform_v1.0) <br>
(https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 Create Terraform execution plan ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.]
Schematics 



 Resources Data sources 

 <br><br> * [ibm_schematics_action](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/schematics_action)<br> * [ibm_schematics_inventory](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/schematics_inventory)<br> * [ibm_schematics_job](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/schematics_job)<br> * [ibm_schematics_resource_query](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/schematics_resource_query)<br> * [ibm_schematics_workspace](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/schematics_workspace)<br><br><br> <br><br> * [ibm_schematics_action]
Image ID to use for region VSIs -Bastion Server<br><br><br><br> * App Server<br> * Web Server<br> * Db Server <br> Images are region-specific. To find the image IDs for your region, open the IBM Cloud shell and enter ibmcloud target -r < region_name > to set your region, then ibmcloud is images to see a list of images for that region.<br><br><br> 



4. Set the optional deployment variables. These variables include information for optional features, such as:



 Component Parameter value needed 

 Auto scale App VSI parameters <br><br> * Min server<br> * Max servers<br> * CPU threshold<br><br><br> 
 Auto scale web VSI parameters <br><br> * Min server<br> * Max servers<br> * CPU threshold<br><br><br> 
 Specific hardware configuration profile for the VSIs. For example, if you want to use a specific compute profile for your app server. For example, cx2-2x4 or cx2d-2x4. 
 VSI Strategy (anti-affinity) Host spread or power spread 



5. Accept the license agreement and select Install.

During installation, you are redirected to the Jobs tab of the Schematics page.



If you need to adjust any of your parameters, go to the Settings tab of the Schematics page to see all of the parameters that you can modify. After you modify a parameter, select Apply plan.





 Customizing a three-tier highly available infrastructure VPC in a multi-zone region with Schematics 

To use the files in the GitHub repo in Schematics, you need a personal access token. When you create the token, copy it to a text file for future use. When you leave the create token page, you can no longer view the token.



1. Go to the [MZR GitHub repository](https://github.ibm.com/workload-eng-services/ha-mzr).
2. Select Settings from your account icon menu.
3.
<br> <br>Resources <br><br><br><br> * ibm_dl_gateway<br> * ibm_dl_virtual_connection<br> * ibm_is_vpc<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-direct-link) 







 Event Streams templates 



 Name Description and resources Code 

 ibm-event-streams Create a communication through an Event Streams instance, topic instance, or Kafka consumer application to connect an existing event stream instances and its topic instance by using IBM Cloud Schematics workspace. <br> <br>Resources <br><br><br><br> * ibm_resource_instance<br> * ibm_event_streams_topic<br> * kafka_consumer_app<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-event-streams) 







 Functions templates 



 Name Description and resources Code 

 ibm-function-cloudant-trigger Create a Cloudant NoSQL service instance and a Python app deployment that creates the database demo database in your service instance. Then, you create an action with IBM Cloud functions that is triggered when you add or edit documents to your database. <br> <br>Resources <br><br><br><br> * null_resource<br> * ibm_service_instance<br> * ibm_service_key<br> * ibm_app_route<br> * ibm_app<br> * ibm_function_package<br> * ibm_function_action<br> * ibm_function_trigger<br> * ibm_function_rule<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-function-cloudant-trigger) 







 Identity & Access (IAM) templates 



 Name Description and resources Code
Auto scale App VSI parameters <br><br> * Min server<br> * Max servers<br> * CPU threshold<br><br><br> 
 Auto scale web VSI parameters <br><br> * Min server<br> * Max servers<br> * CPU threshold<br><br><br> 
 VSI spread strategy (host or power spread) <br><br> * App spread strategy<br> * web spread strategy<br> * Db spread strategy<br><br><br> 
 File share <br><br> * share_size<br> * share_profile<br> * enableFileShare<br> * replica_zone<br> * replica_profile: this should match share_profile value, either tier-3iops, tier-5iops, or tier-10iops<br><br><br> 



5. Accept the license agreement and select Install.

During installation, you are redirected to the Jobs tab of the Schematics page.



If you need to adjust any of your parameters, go to the Settings tab of the Schematics page to see all of the parameters that you can modify. After you modify a parameter, select Apply plan.





 Customizing a three-tier highly available infrastructure VPC in a single availability zone with Schematics 

To use the files in the GitHub repo in Schematics, you need a personal access token. When you create the token, copy it to a text file for future use. When you leave the create token page, you can no longer view the token.



1. Go to the [SAZ GitHub repository](https://github.ibm.com/workload-eng-services/ha-saz).
2. Select Settings from your account icon menu.
3. Select Developer settings.
4. Select Personal Access Tokens.
5. Select Generate new token.
6. Copy the new token and save it in a text file.



After you have your access token, use Schematics to create your infrastructure.



1.
With version control, you can revert to previous versions, audit changes, and share code with multiple teams. If you do not want to store your files in GitHub, provide your template by uploading a [tape archive file or .tar](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) from your local machine instead. If you want to clone, see [allowed and blocked file extensions](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqclone-file-extension) for cloning.

The directory structure of the Terraform template in the GitHub repository is listed in the table with the latest updated time.



Terraform template directory structure

 File Description 

 README.md Create README.md 
 main.tf Create main.tf 
 output.tf Create output.tf 
 provider.tf Create provider.tf 
 variables.tf Create variables.tf
* [June 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesjun-2020)



* Review the release notes for June 2020.
* [26 June 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jun262020)



* Ansible provisioner support



* [25 June 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jun252020)



* Version 1.8.0 of the IBM Cloud Provider plug-in available



* [22 June 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jun222020)



* Upload Terraform templates as TAR files





* [May 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesmay-2020)



* Review the release notes for May 2020.
* [8 May 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-may82020)



* New EU API endpoint





* [April 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesapril-2020)



* Review the release notes for April 2020.
* [17 April 2020](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-apr172020)



* Terraform v0.12 support
* New workspace creation flow











 Configuring the CLI and API
Enter terraform_v1.1 to use Terraform version 1.1,terraform_v1.0 to use Terraform version 1.0, and similarly, terraform_v0.15, terraform_v0.14, terraform_v0.13, terraform_v0.12. For example, when you specify terraform_v1.1 means users can have template that are of Terraform v1.1.0, v1.1.1, or v1.1.2, so on. Make sure that your Terraform config files are compatible with the Terraform version that you specify. This is a required variable. If the Terraform version is not specified, By default, Schematics selects the version from your template. Schematics supports Terraform_v1.x and also plans to make releases available after 30 to 45 days of HashiCorp Configuration Language (HCL) release. 
 location Optional Enter the location where you want to create your workspace. The location determines where your Schematics Actions run and where your workspace data is stored. If you do not enter a location, Schematics determines the location based on the IBM Cloud region that you targeted. To view the region that you targeted, run ibmcloud target --output json and look at the region field. To target a different region, run ibmcloud target -r <region>. If you enter a location, make sure that the location matches the IBM Cloud region that you targeted. 
 description Optional Enter a description for your workspace. 
 template_repo.url Optional Enter the URL to the GitHub or GitLab repository where your Terraform configuration files are stored. 
 template_repo.branch Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. Now, in template_repo, you can also update URL with more parameters as shown in the block. 
 template_repo.datafolder Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. 
 template_repo.release Optional Enter the GitHub or GitLab release that points to your Terraform configuration files.
For example, when you specify terraform_v1.1 means users can have template that are of Terraform v1.1.0, v1.1.1, or v1.1.2, so on. Make sure that your Terraform config files are compatible with the Terraform version that you specify. This is a required variable. If the Terraform version is not specified, By default, Schematics selects the version from your template. Schematics supports Terraform_v1.x and also plans to make releases available after 30 to 45 days of HashiCorp Configuration Language (HCL) release. 
 location Optional Enter the location where you want to create your workspace. The location determines where your Schematics Actions run and where your workspace data is stored. If you do not enter a location, Schematics determines the location based on the IBM Cloud region that you targeted. To view the region that you targeted, run ibmcloud target --output json and look at the region field. To target a different region, run ibmcloud target -r <region>. If you enter a location, make sure that the location matches the IBM Cloud region that you targeted. 
 description Optional Enter a description for your workspace. 
 template_repo.url Optional Enter the URL to the GitHub or GitLab repository where your Terraform configuration files are stored. 
 template_repo.branch Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. Now, in template_repo, you can also update URL with more parameters as shown in the block. 
 template_repo.datafolder Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. 
 template_repo.release Optional Enter the GitHub or GitLab release that points to your Terraform configuration files. 
 github_source_repo_url Optional Enter the link to your GitHub repository. The link can point to the master branch, a different branch, or a subdirectory. If you choose to create your workspace without a GitHub repository, your workspace is created with a draft state.
(https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_action)<br> * [ibm_schematics_inventory](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_inventory)<br> * [ibm_schematics_job](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_job)<br> * [ibm_schematics_output](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_output)<br> * [ibm_schematics_resource_query](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_resource_query)<br> * [ibm_schematics_state](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_state)<br> * [ibm_schematics_workspace](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/schematics_workspace)<br><br><br> 







 Secrets manager 



 Resources Data sources 

 <br><br> * N/A<br><br><br> <br><br> * [ibm_secrets_manager_secret](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/secrets_manager_secret)<br> * [ibm_secrets_manager_secrets](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/secrets_manager_secrets)<br><br><br> 







 Security and Compliance Center 



 Resources Data sources
_note](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_si_note)<br> * [ibm_scc_si_occurrence](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_si_occurrence)<br> * [ibm_scc_template](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_template)<br> * [ibm_scc_template_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_template_attachment)<br><br><br> <br><br> * [ibm_scc_account_location](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_account_location)<br> * [ibm_account_location_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_account_location_settings)<br> * [ibm_scc_account_locations](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_account_locations)<br> * [ibm_scc_account_notification_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_account_notification_settings)<br> * [ibm_scc_posture_collector](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_posture_collector)
When you create a private network endpoint, you must specify the following settings.



 Device type 

Select from the following device type options:



* Multitenant
* Dedicated with 1 Gbps uplinks
* Dedicated with 10 Gbps uplinks



You are not charged for the multitenant option.





 Allowlisted IP addresses and subnets 

Add the IP addresses or subnets that you want to have access to the private network endpoint.







 Monthly cost 

Based on your selected configuration for the private network endpoint, the estimated monthly cost is instantly generated and displayed.

You can also add the provisioned resources to the IBM Cloud estimate tool, by clicking Add to estimate. The tool is useful if you want to estimate the price of the selected VMware Shared resources together with other IBM Cloud resources that you might consider purchasing.





 Procedure to create a private network endpoint for a virtual data center 



1. From the IBM Cloud for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2. In the VMware Shared table, expand the site and click the virtual data center where you want to create a private network endpoint.
3. Click the Services tab.
4. Under Private network endpoint on the recommended services page, click Create a private network endpoint.
5. Complete the following configuration in the Create new private network endpoint pane.



1. Select the device type.
2. Provide the IP addresses or subnets to allowlist.
3. Click Order.





For more information about creating a private network endpoint and to review an example of a successful configuration, see [vCD - Order a Private Network Endpoint (PNE) to connect your IBM account to your VMware Shared virtual datacenter (vDC)](https://mlwiles.github.io/vmwaresolutions/vcd/order-pne/).





 Results after you create a private network endpoint for a virtual data center 



1. The status of the private network endpoint is changed to Creating.
2. When the private network endpoint is created, the status changes to ReadyToUse.
VPC Resource Quota Overview [VPC quota metrics definitions](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-quota-metrics) 



To see a list of Cloud services outside of VPC that offer monitoring, see [Cloud services](https://cloud.ibm.com/docs/monitoring?topic=monitoring-cloud_services).





 View a specific monitoring dashboard 



1. To view a specific dashboard on the monitoring, first go to the [monitoring UI](https://cloud.ibm.com/observe/monitoring). For more information, see [Navigating to the web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch) for Monitoring.
2. In the Monitoring UI, select the instance that you want to view monitoring metrics for. Then, select Open Dashboard.
3. Select the Dashboards tile, the Dashboards menu expands.
4. Under DASHBOARD TEMPLATES, expand the IBM tab to select the dashboard you want to access. The names of available dashboards are detailed in Table 1.
* [VPC CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencecustom-routes-section)
* [VPC API reference](https://cloud.ibm.com/apidocs/vpc)
* [Activity Tracker events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-custom-routes)
* [Routing tables for VPC infrastructure resources for Terraform](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc_routing_table) (VPC infrastructure > Resources)
* [Required permissions for routing tables and routes](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls)
* [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasrouting-tables-routes-quotas)
* Ingress traffic sources: IBM Cloud [Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl) and [Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started)
Table 14. VPC B Networks

 IP Origin 

 10.100.0.0/24 from VPC A subnet 
 13.100.0.0/24 from VPC A subnet 
 13.111.0.0/24 from Classic through Transit Gateway 



VPC A Default (Egress) Routing Table



Table 15. VPC A Default (Egress) Routing Table

 Destination Action Next Hop Location 

 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 1 
 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 2 
 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 3 









 Related links 

To learn about these offerings:



* [Get started with IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)
* [Get started with IBM Cloud Transit Gateway](https://cloud.ibm.com/docs/transit-gateway)
* [Get started with VPN for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn)
B1.32x64 32 64 GB SAN 
 B1.32x128 32 128 GB SAN 
 B1.48x192 48 192 GB SAN 





 Storage notes 



* SAN primary boot disk (25 or 100 GB) with more disks available, up to 2 TB each (five total disks allowed).
* Pricing for public virtual servers that use SAN storage includes virtual CPU, memory, and minimum primary boot disk. Extra disk prices depend on the disk size and quantity that you select.



All supported operating systems (such as RHEL, CentOS, Windows, Ubuntu, and others), databases that are supported, and software add-ons are also available with this offering.







 Balanced local storage 

The balanced local storage profiles are primarily for large database workloads that require high I/O performance with low latency. Network performance ranges from standard to premium.



 Local HDD 



Table 3. Balanced local storage profiles using local HDD

 Profile vCPU RAM Secondary disks Storage type 

 BL1.1x2 1 2 GB 25, 100 GB Local HDD 
 BL1.1x4 1 4 GB 25, 100 GB Local HDD 
 BL1.2x4 2 4 GB 100, 200 GB Local HDD 
 BL1.2x8 2 8 GB 100, 200 GB Local HDD 
 BL1.4x8 4 8 GB 150, 300 GB Local HDD 
 BL1.4x16 4 16 GB 150, 300 GB Local HDD 
 BL1.8x16 8 16 GB 250 GB, (2 x 250 GB) Local HDD 
 BL1.8x32 8 32 GB 250 GB, (2 x 250 GB) Local HDD 
 BL1.16x32 16 32 GB 300 GB, (2 x 300 GB) Local HDD 
 BL1.16x64 16 64 GB 300 GB, (2 x 300 GB) Local HDD 
 BL1.32x64 32 64 GB 400 GB, (2 x 400 GB) Local HDD 
 BL1.32x128 32 128 GB 400 GB, (2 x 400 GB) Local HDD 





 Storage notes 



* Balanced local profiles automatically come with a 100 GB local storage boot disk.
: ibmc-vpc-block-retain-custom: Retain
: ibmc-vpc-block-metro-custom: Delete
: ibmc-vpc-block-metro-retain-custom: Retain
: ibmc-vpcblock-odf-custom: Delete
: ibmc-vpcblock-odf-ret-custom: Retain

Billing
: Hourly





 General purpose 

Name
: ibmc-vpc-block-general-purpose
: ibmc-vpc-block-retain-general-purpose
: ibmc-vpc-block-metro-general-purpose
: ibmc-vpc-block-metro-retain-general-purpose
: ibmc-vpcblock-odf-ret-general
: ibmc-vpcblock-odf-general

File system
: ext4

Corresponding Block Storage for VPC tier
: [3 IOPS/GB](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers)

Volume binding mode
: ibmc-vpc-block-general-purpose: Immediate
: ibmc-vpc-block-retain-general-purpose: Immediate
: ibmc-vpc-block-metro-general-purpose: WaitforFirstConsumer
: ibmc-vpc-block-metro-retain-general-purpose: WaitForFirstConsumer
: ibmc-vpcblock-odf-ret-general: WaitForFirstConsumer
: ibmc-vpcblock-odf-general: WaitForFirstConsumer

Reclaim policy
: ibmc-vpc-block-general-purpose: Delete
: ibmc-vpc-block-retain-general-purpose: Retain
: ibmc-vpc-block-metro-general-purpose: Delete
: ibmc-vpc-block-metro-retain-general-purpose: Retain
: ibmc-vpcblock-odf-ret-general: Retain
: ibmc-vpcblock-odf-general: Delete

Billing
: Hourly