Understanding data portability for Schematics
Data portability involves a set of tools and procedures that enable customers to export the digital artifacts that are needed to implement similar workload and data processing on different service providers or on-premises software. It includes procedures for copying and storing the service customer content, including the related configuration that is used by the service to store and process the data, on the customer's own location.
Responsibilities
IBM Cloud services provide interfaces and instructions to guide the customer to copy and store the service customer content, including the related configuration, on their own selected location.
The customer is responsible for the use of the exported data and configuration for data portability to other infrastructures, that includes:
- The planning and execution for setting up alternative infrastructure on different cloud providers or on-premises software that provide similar capabilities to the IBM services.
- The planning and execution for the porting of the required application code on the alternative infrastructure, including the adaptation of customer's application code, deployment automation.
- The conversion of the exported data and configuration to the format that is required by the alternative infrastructure and adapted applications.
For more information about your responsibilities for IBM Cloud Schematics, see Shared responsibilities for IBM Cloud Schematics.
Data export procedures
IBM Cloud Schematics provides the mechanisms to export your content that is uploaded, stored, and processed when you use the service.
In addition, IBM Cloud Schematics provides mechanisms to export settings and configurations that are used to process the customer's content. For more details, see Accessing workspace state and outputs.
Exported data formats
You can access information about the resources that you manage in a workspace from other workspaces in your account by using the ibm_schematics_output
and ibm_schematics_state
data
sources.
IBM Cloud® uses the local
built-in Terraform state support and does not use Terraform backend support. No additional configuration
is required within your Terraform configs
to enable IBM Cloud® remote state management. Schematics does not use the Terraform remote_state
data source, instead you use the ibm_schematics_output
data source
to access the information.
Data ownership
All exported data is classified as customer content and is therefore applied to them full customer ownership and licensing rights, as stated in IBM Cloud Service Agreement.