Skip to content

Latest commit

 

History

History
68 lines (43 loc) · 3.5 KB

data-portability.md

File metadata and controls

68 lines (43 loc) · 3.5 KB
Raw
copyright lastupdated keywords subcollection
years
2024
2024-11-14
DNS Services
dns-svcs

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

Understanding data portability for DNS Services

{: #data-portability}

Data Portability{: term} 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. {: shortdesc}

Responsibilities

{: #data-portability-responsibilities}

{{site.data.keyword.cloud_notm}} 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, which includes:

  • The planning and execution for setting up alternative infrastructure on different cloud providers or on-premises software that provide similar capabilities to the {{site.data.keyword.IBM_notm}} 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, and so on.
  • The conversion of the exported data and configuration to the format that's required by the alternative infrastructure and adapted applications.

For more information about your responsibilities for DNS Services, see Understanding your responsibilities when using DNS Services.

Data export procedures

{: #data-portability-procedures}

DNS Services provides the mechanisms to export your content that's uploaded, stored, and processed when you use the service.

In addition, DNS Services provides mechanisms to export settings and configurations that are used to process the customer's content. For more information, see Exporting your DNS Services configuration.

Exported data formats

{: #data-portability-data-formats}

DNS Services supports the following data format and schema of the exported data, configuration, and application:

  • Export in JSON format only

    Example command using the DNS Services CLI:

    ibmcloud dns zone ZONE_ID [-i, --instance INSTANCE] [--output json]

    Example request using the DNS Services API:

    curl -X GET   https://api.dns-svcs.cloud.ibm.com/v1/instances/1407a753-a93f-4bb0-9784-bcfc269ee1b3/dnszones/2d0f862b-67cc-41f3-b6a2-59860d0aa90e \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer xxxxxx'

DNS Services doesn't support the export of other data formats and other schema of the exported data, configuration, and application, including the following:

Data ownership

{: #data-portability-ownership}

All exported data is classified as customer content. Apply the full customer ownership and licensing rights, as stated in the IBM Cloud Service Agreement{: external}.