vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The VPC landing zone deployable architectures use [Terraform](https://www.terraform.io/) to specify the infrastructure and [IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started) to manage the deployment.
* How do I estimate costs?

You can view and estimate of starting costs for a variation of the deployable architecture from the IBM Cloud catalog details page. When you deploy by using IBM Cloud® projects, the starting costs for the project are estimated from the validation window after your changes to the configuration are saved and validated.
* Are new releases compatible with previous ones?

Changes adhere to semantic versioning, with releases labeled as {major}.{minor}.{patch}. For more information, see the [release compatiblity](https://terraform-ibm-modules.github.io/documentation//versioning) in the IBM Cloud Terraform modules documentation.



Storage Block Storage - Classic



* How many instances can share the use of a Block Storage for Classic volume?

The default limit for the number of authorizations per block volume is eight. That means that up to eight hosts can be authorized to access the Block Storage for Classic LUN. Customers who use Block Storage for Classic in their VMware® deployment can request the authorization limit to be increased to 64. To request a limit increase, contact your sales representative or raise a [Support case](https://cloud.ibm.com/unifiedsupport/cases/add).

If multiple hosts mount the same Block Storage for Classic volume without being cooperatively managed, your data is at risk for corruption. Volume corruption can occur if changes are made to the volume by multiple hosts at the same time. You need a cluster-aware, shared-disk file system to prevent data loss such as Microsoft® Cluster Shared Volumes (CSV), Red Hat Global File System (GFS2), VMware® VMFS, and others. For more information, see your host's OS Documentation.
* Our compute hosts have multiple network cards with different IP addresses for network redundancy and expanded bandwidth.
The blueprint (resource) maintains the record of operations run, job status, the cloud resources deployed, and the [blueprint template](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb2). It defines the infrastructure architecture and the unique input values that are used to configure the environment.

A blueprint is created with a [blueprint configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb3). The set of cloud resources deployed by a blueprint is referred to as a [blueprint environment](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb4).





 Blueprint template 

A [blueprint template](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templates) defines the infrastructure architecture, topology, and cloud resources for a solution architecture. The template implements the desired architecture from reusable [modules](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb5) that are written in Terraform. Template files are written to a [YAML schema](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-template-schema-yaml) and specify the Terraform [automation modules](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb5) to be used, their versions, Git source libraries, and the relationships and dependencies between modules. Template files versioned and sourced from a version control system, GitHub or GitLab.





 Blueprint configuration 

A blueprint configuration is the initial definition that the user provides to create a blueprint.
* UI
* CLI
* API







 Deleting Schematics data 

IBM Cloud® Schematics stores your data in a highly available and secure environment. All your data such as automation code, input configuration data, input credentials, and the runtime data are stored in Object Storage. This data-at-rest is encrypted using AES GCM 256 with an envelope encryption technique. As the IBM Cloud account owner, you can control access to the IBM Cloud® Schematics objects in your account. You can choose to delete your data, by using the Schematics API, UI, or CLI as described.

When you delete these Schematics objects, the corresponding data in Object Storage is marked for deletion. The soft delete option enable you to recover the Schematics data by raising a [support ticket](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-help). Further, your data will automatically be purged after 7 days of soft delete.

Also, Schematics service maintains a backup copy of your data in a separate Object Storage bucket. This backup copy is automatically overwritten, every 30 days. Hence, all backup copy of your data will be purged in 30 days.



 Scope 

The scope of deletion is limited to data stored in Schematics service and its backup.

Following points does not include in the scope of deletion of Schematics objects.



* The deletion or removal of the IBM Cloud resources that were provisioned by using Schematics.
* The data stored by the IBM Cloud resources provisioned by the Schematics.
* At the time of Schematics object deletion, you will be provided with the option to destroy the Cloud resources. However, it is suggested to independently confirm and destroy the Cloud resources from the Cloud Services. You can explore the list of Cloud resources, from the [IBM Cloud resource list](https://cloud.ibm.com/resources) page.







 Deleting Schematics objects from UI 

You can delete Schematics objects by using IBM Cloud console.
The inputs to the mustache templates are defined in the [tft_parameters](/docs/schematics?topic=schematics-bp-template-schema-yamlbp-modules-tft-parameters) section. Refer to the .tf files in the [Cloud-Schematics/tf-templates/ibm](https://github.com/Cloud-Schematics/tf-templates/tree/main/ibm) folder to determine the supported input parameters for the Terraform language definitions. For the IBM® Terraform provider the example required inputs are:

          - name: provider_version
            value: 1.38.2
          - name: provider_source
            value: IBM-Cloud/ibm
          - name: region
            value: us-south

With the example inputs, the generated output files are:

tf_ibm_versions_override.tf

terraform {
   required_providers {
     ibm = {
       source  = "IBM-Cloud/ibm"
       version = "1.38.2"
     }
   }
 }

tf_ibm_provider_override.tf

provider "ibm" {
   region = "us-south"
}







 Next steps 

In this section you have learned about using Terraform modules with blueprints.



* Explore [understanding blueprint templates and configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templates) to create templates containing modules.
* Looking for blueprint samples using modules? Check out the [IBM Cloud Schematics GitHub repository](https://github.com/orgs/Cloud-Schematics/repositories/?q=topic:blueprint). Check the Readme files of the examples for further customization and usage for each sample.
Currently only JSON file format is supported. 
 --region or -r Optional Specify the region, such as eu, us, eu-gb, eu-de, us-south, or us-east. 



Example

ibmcloud schematics workspace list --limit 10 --offset 20 --json





 ibmcloud schematics workspace new 

Create an Schematics Workspaces that points to your Terraform template in GitHub or GitLab. If you want to provide your Terraform template by uploading a tape archive file (.tar), you can create the workspace without a connection to a GitHub repository and then use the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command to provide the template.

Schematics does not support passing .tar file to create a workspace.

IBM Cloud Schematics supports 50 API requests per minute, per host, and per customer. The location can be us-east, us-south, eu-gb, or eu-de region. You need to wait before calling the command again.

To create a workspace, you can specify your workspace settings in a JSON file. Make sure that the JSON file follows the structure as outlined in this command. Also ensure the location and the url endpoint are pointing to the same region when you create or update workspaces and actions. For more information about location and endpoint, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location).

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).

Syntax
: The Schematics [command-line plug-in v1.8.1](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.





 18 April 2022 

Support array of injectable Terraform blocks in create workspace API
: The Schematics supports array of injectable Terraform block to inject the parameters with the values to an existing Terraform template to provision through [Schematics create workspace API](https://cloud.ibm.com/apidocs/schematics/schematicscreate-workspace).

Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.9.1](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.





 12 April 2022 

Schematics command-line supports private Schematics endpoint
: The Schematics command line [supports private Schematics endpoint](https://cloud.ibm.com/docs/schematics?topic=schematics-private-endpointsprivate-cse).

Support .JSON and .tfvars file extension for Schematics plan and apply commands
: The Schematics command line supports .JSON and .tfvars file extension in Schematics plan and apply commands.

Enhance resources tabular data view for resources.
: The Schematics command line lists the provisioned resources from your workspace in a tabular data view output with Resource, Type, State, Resource group, URL, and Tags fields. For example, use [ibmcloud schematics state list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencestate-list) command to list the resources provisioned in your workspace.

Deprecate and warning message when using ibmcloud terraform command.
: The Schematics ibmcloud terraform command usage displays warning and deprecation message as Alias 'terraform' will be deprecated.
IBM Cloud Schematics Agent beta-1 delivers a simplified agent installation process and policy for agent assignment.. You can review the [beta-1 release](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotes&interface=clischematics-mar2223) documentation and explore.



 Beta-1 code for Schematics Agent 

The agent level of code is considered beta-1 code as there will be changes in function and capabilities between now and the General Availability (GA) date.

Although agent usage has no cost involved during beta, it will have a cost eventually in the GA timeframe. You will be updated in the documentation with the usage and the charges.

Join our beta program, post a question in the [IBM Cloud Schematics users Slack](https://ibm-argonauts.slack.com/archives/CLKR4FE90), and engage with the Schematics team. If you do not have access to this Slack, [request an invitation to this Slack](https://cloud.ibm.com/schematics/slack).

Join the schematics-users slack channel and post a message include the following information.



* Your name
* email address
* Your Company/Organization name
* Your level of experience with cloud automation, specifically regarding Terraform, Ansible, or IBM Cloud Schematics
* Any initial questions or comments



You can come back any time to your created thread to add information, ask questions, or give feedback.



 Beta-1 release limitations for Agent 

There will be multiple beta releases in short window period, this requires the users to update the Agent infrastructure and Agent services in your environment.



Beta-1 release limitations

 Limitation Resolved Date 

 The cluster and COS bucket must be in the same resource group 
 Only IKS clusters are supported at this time. ROKS support is planned for the future 
 UI capabilities are not final and will be updated throughout the beta process. 
 Support to [store or persist user-defined](https://cloud.ibm.com/docs/schematics?topic=schematics-general-faqpersist-file) files is not available in Agents.
](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-resources-datasource-list)[Browse Terraform templates Explore the sample Terraform templates, onboard them to your private catalogs, and try them using Schematics.](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatesample-templates)[Create Kubernetes and OpenShift clusters Learn how to create single and multizone IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud clusters with Terraform.](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-tutorial-tf-clusters)[Create a virtual server in a VPC Use Terraform on IBM Cloud to provision a VPC, set up networking for your VPC, and provision a virtual server for VPC in your IBM Cloud account.](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-sample_vpc_config)[Create a classic virtual server instance See how you can use Terraform on IBM Cloud to provision a classic virtual server instance. ](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-sample_infrastructure_config)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/?q=terraform)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>!
* IBM Cloud Schematics deprecates Terraform v0.11
* Terraform v0.15 support
* Ansible v2.9.23 API and command-line support



* [19 July 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jul192021)



* Support parallelism and other environment variables in IBM Cloud Schematics





* [June 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesjune-2021)



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



* Support taint and untaint feature enhancement in IBM Cloud Schematics
* Documentation support to deploy resources in specific region or across multiple region
* Documentation support to create workspace by using IBM Cloud Schematics resources
* One page view to create workspace by using UI, CLI, API, and Terraform switcher documentation
* Temporarily IBM Cloud Schematics Workspaces stop activity API is deactivated





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



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



* Version constraints support in IBM Cloud Schematics
* Troubleshooting guide support
* Schematics supports sample solutions





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



* Review the release notes for April 2021.
Workspaces 

Answers to common questions about the IBM Cloud Schematics Workspaces are classified into following section.



 Why are files removed from Terraform, or Ansible templates? 

To protect from malicious users Schematics removes files from imported Git repositories.

When creating Schematics Workspaces or action IBM Cloud Schematics takes a copy of the Terraform, or Ansible template from your Git repository and stores in a secured location. Before the template files are saved, Schematics analyses the files and are removed, based on the following conditions:



* The allowed file extensions are .cer, .cfg, .conf, .crt, .der, .gitignore, .html, .j2, .jacl, .js, .json, .key, .md, .netrc, .pem, .properties, .ps1, .pub, .py, .service, .sh, .tf, .tf.json, .tfvars, .tmpl, .tpl, .txt, .yaml, .yml, .zip, _rsa, license.
* The allowed image extensions are .bmp, .gif, .jpeg, .jpg, .png, .so .tif, .tiff.
* The files that are removed are .asa, .asax, .exe, .php5, .pht, .phtml, .shtml, .swf, .tfstate, .tfstate.backup, .xap.
* All files that are larger than 500 KB are removed. This file size limit does not apply for the allowed image files.
* The folder name starts with a (period) . is treated as vulnerable.



The allowed extension list is continuously monitored and updated in every release. You can raise a [support ticket](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-help) with the justification to add a file extension to the list.





 How do I save files between operations?
If you provided your Terraform template by uploading a tape archive file (.tar) and you want to update your template, you must use the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command.

Syntax

ibmcloud schematics workspace update --id WORKSPACE_ID [--file FILE_NAME] [--github-token GITHUB_TOKEN] [--pull-latest] [--output OUTPUT] [--json]

Pull-latest flag is not supported for workspaces created by using templates from IBM Cloud catalogs.

Command options



Schematics Workspaces update flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace for which you want to update the instance or resource. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --file or -f Optional The relative path to a JSON file on your local machine that includes the updated parameters for your workspace. For more information about the sample JSON file with the details, see [JSON file update template](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencejson-file-update-template). 
 --github-token or -g Optional Enter the GitHub token value to access private Git repository. 
 --pull-latest or --pl Optional Pull the latest changes from your GitHub repository into workspace. If this flag is set --file flag is ignored. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 
 --json or -j Deprecated Prints the output in the JSON format. 





 Update file template in JSON format 

You can create the JSON as shared in the example.json file for workspace update and pass the file path along with the file name in --file flag.
Or Terraform by using IBM container worker pool zone attachment resource. For more information, see [ibm_container_worker_pool_zone_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_worker_pool_zone_attachment).
* Where can I view the list of public and private allowed IP addresses of us-south, us-east, eu-gb, and eu-de regions?

You can view the list of public and private allowed IP addresses of us-south, us-east, eu-gb, and eu-de regions in [Schematics allowed IP addresses](https://cloud.ibm.com/docs/schematics?topic=schematics-allowed-ipaddresses).
* Can I manually add, or remove a resource from the service dashboard directly?

When you provision resources with IBM Cloud Schematics, the state of your resources is stored in a local IBM Cloud Schematics state file. This state file is the single source of truth for IBM Cloud Schematics to determine what resources are provisioned in your IBM Cloud account. If you manually add a resource without IBM Cloud Schematics, this resource is not stored in the IBM Cloud Schematics state file, and as a consequence cannot be managed with IBM Cloud Schematics.

When you manually remove a resource that you provisioned with IBM Cloud Schematics, the state file is not updated automatically and becomes out of sync. When you create your next Terraform execution plan or apply a new template version, Schematics verifies that the IBM Cloud resources in the state file exist in your IBM Cloud account with the state that is captured in your state file. If the resource is not found, the state file is updated, and the Terraform execution plan are changed.

To keep your IBM Cloud Schematics state file and the IBM Cloud resources in your account in sync, use IBM Cloud Schematics to provision, or remove your resources.
* What changes can I make to my resources?

You can choose to add, modify, or remove infrastructure code in your Terraform template through GitHub, or update variable values from the Schematics Workspaces dashboard.
Managing and monitoring the deployment 

For deployment process monitoring, IBM Cloud Schematics monitoring interfaces are used. The same interface is used to audit and capture all user actions and relevant security events.

For more information, see [Getting started: IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started), [Monitoring Schematics services by using IBM Cloud Monitoring](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instances) and [Auditing events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_events).



  Infrastructure and landscape management and monitoring after deployment 

For monitoring and management of provisioned resources, VPC and PowerVS interfaces are used. The same interface is used to audit and capture all user actions and relevant security events.

For more information, see [IBM Cloud VPC documentation](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc) and [IBM Cloud PowerVS documentation](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started).





  Lifecycle management 

Lifecycle management with PowerVS workspace and VPC service provisioning by using deployable architectures is limited to initial landscape deployments. Landscape update is not supported and must be done manually.
* Connect the [Schematics Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-register-agent) through UI to register the Agent to the Schematics service instance.
* Use the [Schematics Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-using-agent) through UI to bind the Schematics Workspaces to the Agent.
* Uninstall [Schematics Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-uninstall-agent) to clean up the Agent infrastructure and Agent services.
* [FAQs](https://cloud.ibm.com/docs/schematics?topic=schematics-faqs-agent) and [Troubleshooting guide](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-crn-not-found) for any challenges and questions on Agents.
* [Beta code for Schematics Agents](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-beta-limitations) to engage with the agents beta level code and provide feedback.



Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.12.0](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.





 8 July 2022 

Schematics Blueprints beta release in production.
: Schematics announces its [beta release](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitations) of Schematics Blueprints to deploy large-scale and complex application environments from a reusable building blocks. Check the following content to learn about Schematics Blueprints beta releases.



* [Landing page](https://cloud.ibm.com/docs/schematics) to start your Schematics Blueprints engagement.