diff --git a/docs/evs/api-ref/.placeholder b/docs/evs/api-ref/.placeholder deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/evs/api-ref/ALL_META.TXT.json b/docs/evs/api-ref/ALL_META.TXT.json new file mode 100644 index 000000000..b09523367 --- /dev/null +++ b/docs/evs/api-ref/ALL_META.TXT.json @@ -0,0 +1,1812 @@ +[ + { + "uri":"evs_04_0001.html", + "product_code":"evs", + "code":"1", + "des":"Public cloud Application Programming Interfaces (APIs) comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource ", + "doc_type":"api", + "kw":"API Usage Guidelines,API Reference", + "title":"API Usage Guidelines", + "githuburl":"" + }, + { + "uri":"evs_04_0018.html", + "product_code":"evs", + "code":"2", + "des":"EVS APIs provide multiple versions. For the APIs offering same functions, you are recommended to use the v2 APIs.The current default microversion of v3 APIs is 3.0, and t", + "doc_type":"api", + "kw":"API Version Description and Usage Instructions,API Reference", + "title":"API Version Description and Usage Instructions", + "githuburl":"" + }, + { + "uri":"evs_04_0019.html", + "product_code":"evs", + "code":"3", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"API Version Query", + "title":"API Version Query", + "githuburl":"" + }, + { + "uri":"evs_04_0020.html", + "product_code":"evs", + "code":"4", + "des":"This API is used to query information of API versions.URI formatGET /GET /Example requestGET https://{endpoint}/Parameter descriptionParameterTypeDescriptionversionsArray", + "doc_type":"api", + "kw":"Querying Information of API Versions,API Version Query,API Reference", + "title":"Querying Information of API Versions", + "githuburl":"" + }, + { + "uri":"evs_04_0021.html", + "product_code":"evs", + "code":"5", + "des":"This API is used to query information of an API version.URI formatGET /{api_version}GET /{api_version}Parameter descriptionParameterTypeDescriptionapi_versionStringSpecif", + "doc_type":"api", + "kw":"Querying Information of an API Version,API Version Query,API Reference", + "title":"Querying Information of an API Version", + "githuburl":"" + }, + { + "uri":"evs_04_2001.html", + "product_code":"evs", + "code":"6", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"API v2 (Recommended)", + "title":"API v2 (Recommended)", + "githuburl":"" + }, + { + "uri":"evs_04_2002.html", + "product_code":"evs", + "code":"7", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk", + "title":"EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2013.html", + "product_code":"evs", + "code":"8", + "des":"This API is used to create one or multiple EVS disks.URI formatPOST /v2/{project_id}/cloudvolumesPOST /v2/{project_id}/cloudvolumesParameter descriptionParameterMandatory", + "doc_type":"api", + "kw":"Creating EVS Disks,EVS Disk,API Reference", + "title":"Creating EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_04_2005.html", + "product_code":"evs", + "code":"9", + "des":"This API is used to query details about all disks.URI formatGET /v2/{project_id}/cloudvolumes/detailGET /v2/{project_id}/cloudvolumes/detailParameter descriptionParameter", + "doc_type":"api", + "kw":"Querying Details About All Disks,EVS Disk,API Reference", + "title":"Querying Details About All Disks", + "githuburl":"" + }, + { + "uri":"evs_04_2008.html", + "product_code":"evs", + "code":"10", + "des":"This API is used to delete an EVS disk.URI formatDELETE /v2/{project_id}/cloudvolumes/{volume_id}DELETE /v2/{project_id}/cloudvolumes/{volume_id}Parameter descriptionPara", + "doc_type":"api", + "kw":"Deleting an EVS Disk,EVS Disk,API Reference", + "title":"Deleting an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2009.html", + "product_code":"evs", + "code":"11", + "des":"This API is used to update the name and description of an EVS disk.This API has been deprecated. Use another API. For details, see Updating an EVS Disk.URI formatPUT /v2/", + "doc_type":"api", + "kw":"Updating an EVS Disk (Deprecated),EVS Disk,API Reference", + "title":"Updating an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2010.html", + "product_code":"evs", + "code":"12", + "des":"This API is used to query details about all disks.URI formatGET /v2/{project_id}/os-vendor-volumes/detailGET /v2/{project_id}/os-vendor-volumes/detailParameter descriptio", + "doc_type":"api", + "kw":"Querying Details About All Disks (Deprecated),EVS Disk,API Reference", + "title":"Querying Details About All Disks (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2011.html", + "product_code":"evs", + "code":"13", + "des":"This API is used to query details about a disk.URI formatGET /v2/{project_id}/os-vendor-volumes/{volume_id}GET /v2/{project_id}/os-vendor-volumes/{volume_id}Parameter des", + "doc_type":"api", + "kw":"Querying Details About a Disk,EVS Disk,API Reference", + "title":"Querying Details About a Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2012.html", + "product_code":"evs", + "code":"14", + "des":"This API is used to query EVS disks and display the query results in a list.This API has been deprecated. Use another API. For details, see Querying EVS Disks.URI formatG", + "doc_type":"api", + "kw":"Querying EVS Disks (Deprecated),EVS Disk,API Reference", + "title":"Querying EVS Disks (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2014.html", + "product_code":"evs", + "code":"15", + "des":"This API is used to expand the capacity of an EVS disk.If the status of the to-be-expanded disk is available, there are no restrictions.If the status of the to-be-expande", + "doc_type":"api", + "kw":"Expanding Capacity of an EVS Disk (Deprecated),EVS Disk,API Reference", + "title":"Expanding Capacity of an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2015.html", + "product_code":"evs", + "code":"16", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Snapshot", + "title":"EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2022.html", + "product_code":"evs", + "code":"17", + "des":"This API is used to roll back a snapshot to an EVS disk.When you roll back a snapshot to a disk, you can only roll back the snapshot to the source disk. Rollback to a spe", + "doc_type":"api", + "kw":"Rolling Back a Snapshot to an EVS Disk,EVS Snapshot,API Reference", + "title":"Rolling Back a Snapshot to an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2024.html", + "product_code":"evs", + "code":"18", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Tag", + "title":"EVS Tag", + "githuburl":"" + }, + { + "uri":"evs_04_2025.html", + "product_code":"evs", + "code":"19", + "des":"This API is used to delete tags of an EVS resource by key.NoneURI formatDELETE /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}DELETE /v2/{project_id}/", + "doc_type":"api", + "kw":"Deleting Tags of an EVS Resource by Key,EVS Tag,API Reference", + "title":"Deleting Tags of an EVS Resource by Key", + "githuburl":"" + }, + { + "uri":"evs_04_2026.html", + "product_code":"evs", + "code":"20", + "des":"This API is used to obtain all tags of an EVS resource type.NoneURI formatGET /v2/{project_id}/os-vendor-tags/{resource_type}GET /v2/{project_id}/os-vendor-tags/{resource", + "doc_type":"api", + "kw":"Obtaining All Tags of an EVS Resource Type,EVS Tag,API Reference", + "title":"Obtaining All Tags of an EVS Resource Type", + "githuburl":"" + }, + { + "uri":"evs_04_2027.html", + "product_code":"evs", + "code":"21", + "des":"This API is used to batch add tags for the specified EVS disk.When adding tags, if a tag key is consistent with an existing one, the new tag will overwrite the existing t", + "doc_type":"api", + "kw":"Batch Adding Tags for the Specified EVS Disk,EVS Tag,API Reference", + "title":"Batch Adding Tags for the Specified EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2029.html", + "product_code":"evs", + "code":"22", + "des":"This API is used to batch delete tags for the specified EVS disk.NoneURI formatPOST /v2/{project_id}/os-vendor-volumes/{volume_id}/tags/actionPOST /v2/{project_id}/os-ven", + "doc_type":"api", + "kw":"Batch Deleting Tags for the Specified EVS Disk,EVS Tag,API Reference", + "title":"Batch Deleting Tags for the Specified EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2031.html", + "product_code":"evs", + "code":"23", + "des":"This API is used to query the tags of the specified EVS disk.NoneURI formatGET /v2/{project_id}/os-vendor-volumes/{volume_id}/tagsGET /v2/{project_id}/os-vendor-volumes/{", + "doc_type":"api", + "kw":"Querying Tags of an EVS Disk,EVS Tag,API Reference", + "title":"Querying Tags of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2032.html", + "product_code":"evs", + "code":"24", + "des":"This API is used to query the number of EVS disks by tag.NoneURI formatPOST /v2/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v2/{project_id}/os-vendor-vo", + "doc_type":"api", + "kw":"Querying the Number of EVS Disks by Tag,EVS Tag,API Reference", + "title":"Querying the Number of EVS Disks by Tag", + "githuburl":"" + }, + { + "uri":"evs_04_2034.html", + "product_code":"evs", + "code":"25", + "des":"This API is used to query the details of EVS disks by tag.NoneURI formatPOST /v2/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v2/{project_id}/os-vendor-v", + "doc_type":"api", + "kw":"Querying Details of EVS Disks by Tag,EVS Tag,API Reference", + "title":"Querying Details of EVS Disks by Tag", + "githuburl":"" + }, + { + "uri":"evs_04_2036.html", + "product_code":"evs", + "code":"26", + "des":"This API is used to add or update tags for an EVS resource.This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.A ", + "doc_type":"api", + "kw":"Adding or Updating Tags for an EVS Resource (Deprecated),EVS Tag,API Reference", + "title":"Adding or Updating Tags for an EVS Resource (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2037.html", + "product_code":"evs", + "code":"27", + "des":"This API is used to batch delete tags for an EVS resource.This API has been deprecated. Use another API. For details, see Batch Deleting Tags for the Specified EVS Disk.N", + "doc_type":"api", + "kw":"Batch Deleting Tags for an EVS Resource (Deprecated),EVS Tag,API Reference", + "title":"Batch Deleting Tags for an EVS Resource (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2038.html", + "product_code":"evs", + "code":"28", + "des":"This API is used to obtain the tags of a specified EVS resource.This API has been deprecated. Use another API. For details, see Querying Tags of an EVS Disk.NoneURI forma", + "doc_type":"api", + "kw":"Obtaining Tags of a Specified EVS Resource (Deprecated),EVS Tag,API Reference", + "title":"Obtaining Tags of a Specified EVS Resource (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2039.html", + "product_code":"evs", + "code":"29", + "des":"This API is used to query tags of an EVS resource by key.This API has been deprecated. Use another API. For details, see Querying Tags of an EVS Disk.NoneURI formatGET /v", + "doc_type":"api", + "kw":"Querying Tags of an EVS Resource by Key (Deprecated),EVS Tag,API Reference", + "title":"Querying Tags of an EVS Resource by Key (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2040.html", + "product_code":"evs", + "code":"30", + "des":"This API is used to reset the tags of an EVS resource, and the existing tags will be deleted.This API call exists for compatibility reasons only and has been deprecated.A", + "doc_type":"api", + "kw":"Resetting Tags of an EVS Resource (Deprecated),EVS Tag,API Reference", + "title":"Resetting Tags of an EVS Resource (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2041.html", + "product_code":"evs", + "code":"31", + "des":"This API is used to update tags of an EVS resource by key.This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.A t", + "doc_type":"api", + "kw":"Updating Tags of an EVS Resource by Key (Deprecated),EVS Tag,API Reference", + "title":"Updating Tags of an EVS Resource by Key (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2042.html", + "product_code":"evs", + "code":"32", + "des":"This API is used to query the EVS resources by tag.This API has been deprecated. Use another API. For details, see Querying Details of EVS Disks by Tag.NoneURI formatGET ", + "doc_type":"api", + "kw":"Querying EVS Resources by Tag (Deprecated),EVS Tag,API Reference", + "title":"Querying EVS Resources by Tag (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2043.html", + "product_code":"evs", + "code":"33", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Replication Pair (Deprecated)", + "title":"EVS Replication Pair (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2044.html", + "product_code":"evs", + "code":"34", + "des":"This API is used to create an EVS replication pair using a specified production disk and a disaster recovery (DR) disk. The production disk is in the primary AZ, and the ", + "doc_type":"api", + "kw":"Creating an EVS Replication Pair (Deprecated),EVS Replication Pair (Deprecated),API Reference", + "title":"Creating an EVS Replication Pair (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2045.html", + "product_code":"evs", + "code":"35", + "des":"This API is used to delete a specified EVS replication pair.This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.The to", + "doc_type":"api", + "kw":"Deleting an EVS Replication Pair (Deprecated),EVS Replication Pair (Deprecated),API Reference", + "title":"Deleting an EVS Replication Pair (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2046.html", + "product_code":"evs", + "code":"36", + "des":"This API is used to query all EVS replication pairs of the current tenant.This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Re", + "doc_type":"api", + "kw":"Querying All EVS Replication Pairs (Deprecated),EVS Replication Pair (Deprecated),API Reference", + "title":"Querying All EVS Replication Pairs (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2047.html", + "product_code":"evs", + "code":"37", + "des":"This API is used to query the details about an EVS replication pair, including the name, ID, and status of the replication pair.This API has been deprecated. To use this ", + "doc_type":"api", + "kw":"Querying Details About an EVS Replication Pair (Deprecated),EVS Replication Pair (Deprecated),API Re", + "title":"Querying Details About an EVS Replication Pair (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2048.html", + "product_code":"evs", + "code":"38", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Replication Consistency Group (Deprecated)", + "title":"Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2049.html", + "product_code":"evs", + "code":"39", + "des":"This API is used to create a replication consistency group for the specified EVS replication pairs.This API has been deprecated. To use this function, see Storage Disaste", + "doc_type":"api", + "kw":"Creating a Replication Consistency Group (Deprecated),Replication Consistency Group (Deprecated),API", + "title":"Creating a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2050.html", + "product_code":"evs", + "code":"40", + "des":"This API is used to delete a replication consistency group.This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.All EVS", + "doc_type":"api", + "kw":"Deleting a Replication Consistency Group (Deprecated),Replication Consistency Group (Deprecated),API", + "title":"Deleting a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2051.html", + "product_code":"evs", + "code":"41", + "des":"This API is used to query all replication consistency groups of the current tenant.This API has been deprecated. To use this function, see Storage Disaster Recovery Servi", + "doc_type":"api", + "kw":"Querying All Replication Consistency Groups (Deprecated),Replication Consistency Group (Deprecated),", + "title":"Querying All Replication Consistency Groups (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2052.html", + "product_code":"evs", + "code":"42", + "des":"This API is used to query the details about a replication consistency group, including the name, ID, and status of the consistency group.This API has been deprecated. To ", + "doc_type":"api", + "kw":"Querying Details About a Replication Consistency Group (Deprecated),Replication Consistency Group (D", + "title":"Querying Details About a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2053.html", + "product_code":"evs", + "code":"43", + "des":"This API is used to update a replication consistency group. An update includes the following operations:Update the name or description of the replication consistency grou", + "doc_type":"api", + "kw":"Updating a Replication Consistency Group (Deprecated),Replication Consistency Group (Deprecated),API", + "title":"Updating a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2054.html", + "product_code":"evs", + "code":"44", + "des":"This API is used to perform a failover for a replication consistency group. When an exception occurs in the primary AZ, a failover can be performed to change the primary ", + "doc_type":"api", + "kw":"Performing a Failover for a Replication Consistency Group (Deprecated),Replication Consistency Group", + "title":"Performing a Failover for a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2055.html", + "product_code":"evs", + "code":"45", + "des":"This API is used to synchronize the data between production disks and DR disks in all EVS replication pairs of a replication consistency group. After the synchronization ", + "doc_type":"api", + "kw":"Synchronizing a Replication Consistency Group (Deprecated),Replication Consistency Group (Deprecated", + "title":"Synchronizing a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2056.html", + "product_code":"evs", + "code":"46", + "des":"This API is used to perform a primary/secondary switchover for a replication consistency group. A switchover can be performed to switch the primary and secondary AZs of a", + "doc_type":"api", + "kw":"Performing a Primary/Secondary Switchover for a Replication Consistency Group (Deprecated),Replicati", + "title":"Performing a Primary/Secondary Switchover for a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2057.html", + "product_code":"evs", + "code":"47", + "des":"This API is used to pause a replication consistency group, that is, to pause the data synchronization in all EVS replication pairs of a replication consistency group.Befo", + "doc_type":"api", + "kw":"Pausing a Replication Consistency Group (Deprecated),Replication Consistency Group (Deprecated),API ", + "title":"Pausing a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2058.html", + "product_code":"evs", + "code":"48", + "des":"This API is used to reprotect a replication consistency group. After resources in a faulty AZ have been restored and functioned as DR resources, a reprotection can be per", + "doc_type":"api", + "kw":"Reprotecting a Replication Consistency Group (Deprecated),Replication Consistency Group (Deprecated)", + "title":"Reprotecting a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2059.html", + "product_code":"evs", + "code":"49", + "des":"This API is used to expand the EVS disks in one or multiple EVS replication pairs. In such an expansion operation, two EVS disks in one EVS replication pair are expanded ", + "doc_type":"api", + "kw":"Expanding EVS Disks in a Replication Consistency Group (Deprecated),Replication Consistency Group (D", + "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2063.html", + "product_code":"evs", + "code":"50", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"OpenStack Cinder API v2 (Recommended)", + "title":"OpenStack Cinder API v2 (Recommended)", + "githuburl":"" + }, + { + "uri":"evs_04_2064.html", + "product_code":"evs", + "code":"51", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk", + "title":"EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2065.html", + "product_code":"evs", + "code":"52", + "des":"This API is used to create one or multiple EVS disks.URI formatPOST /v2/{project_id}/volumesPOST /v2/{project_id}/volumesParameter descriptionParameterMandatoryDescriptio", + "doc_type":"api", + "kw":"Creating EVS Disks,EVS Disk,API Reference", + "title":"Creating EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_04_2066.html", + "product_code":"evs", + "code":"53", + "des":"This API is used to delete an EVS disk.URI formatDELETE /v2/{project_id}/volumes/{volume_id}DELETE /v2/{project_id}/volumes/{volume_id}Parameter descriptionParameterManda", + "doc_type":"api", + "kw":"Deleting an EVS Disk,EVS Disk,API Reference", + "title":"Deleting an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2067.html", + "product_code":"evs", + "code":"54", + "des":"This API is used to update the EVS disk information.URI formatPUT /v2/{project_id}/volumes/{volume_id}PUT /v2/{project_id}/volumes/{volume_id}Parameter descriptionParamet", + "doc_type":"api", + "kw":"Updating an EVS Disk,EVS Disk,API Reference", + "title":"Updating an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2068.html", + "product_code":"evs", + "code":"55", + "des":"This API is used to query EVS disks.URI formatGET /v2/{project_id}/volumesGET /v2/{project_id}/volumesParameter descriptionParameterMandatoryDescriptionproject_idYesSpeci", + "doc_type":"api", + "kw":"Querying EVS Disks,EVS Disk,API Reference", + "title":"Querying EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_04_2069.html", + "product_code":"evs", + "code":"56", + "des":"This API is used to query details about all disks.URI formatGET /v2/{project_id}/volumes/detailGET /v2/{project_id}/volumes/detailParameter descriptionParameterMandatoryD", + "doc_type":"api", + "kw":"Querying Details About All Disks,EVS Disk,API Reference", + "title":"Querying Details About All Disks", + "githuburl":"" + }, + { + "uri":"evs_04_2070.html", + "product_code":"evs", + "code":"57", + "des":"This API is used to query details about a disk.URI formatGET /v2/{project_id}/volumes/{volume_id}GET /v2/{project_id}/volumes/{volume_id}Parameter descriptionParameterMan", + "doc_type":"api", + "kw":"Querying Details About a Disk,EVS Disk,API Reference", + "title":"Querying Details About a Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2071.html", + "product_code":"evs", + "code":"58", + "des":"This API is used to query EVS disk types and display the query results in a list.URI formatGET /v2/{project_id}/typesGET /v2/{project_id}/typesParameter descriptionParame", + "doc_type":"api", + "kw":"Querying EVS Disk Types,EVS Disk,API Reference", + "title":"Querying EVS Disk Types", + "githuburl":"" + }, + { + "uri":"evs_04_2072.html", + "product_code":"evs", + "code":"59", + "des":"This API is used to query details about an EVS disk type.URI formatGET /v2/{project_id}/types/{type_id}GET /v2/{project_id}/types/{type_id}Parameter descriptionParameterM", + "doc_type":"api", + "kw":"Querying Details About an EVS Disk Type,EVS Disk,API Reference", + "title":"Querying Details About an EVS Disk Type", + "githuburl":"" + }, + { + "uri":"evs_04_2073.html", + "product_code":"evs", + "code":"60", + "des":"This API is used to query the details of tenant quotas.URI formatGET /v2/{project_id}/os-quota-sets/{target_project_id}?usage=TrueGET /v2/{project_id}/os-quota-sets/{targ", + "doc_type":"api", + "kw":"Querying Details of Tenant Quotas,EVS Disk,API Reference", + "title":"Querying Details of Tenant Quotas", + "githuburl":"" + }, + { + "uri":"evs_04_2074.html", + "product_code":"evs", + "code":"61", + "des":"This API is used to add or update the metadata of an EVS disk.URI formatPOST /v2/{project_id}/volumes/{volume_id}/metadataPOST /v2/{project_id}/volumes/{volume_id}/metada", + "doc_type":"api", + "kw":"Adding Metadata of an EVS Disk,EVS Disk,API Reference", + "title":"Adding Metadata of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2075.html", + "product_code":"evs", + "code":"62", + "des":"This API is used to query the metadata of an EVS disk.URI formatGET /v2/{project_id}/volumes/{volume_id}/metadataGET /v2/{project_id}/volumes/{volume_id}/metadataParamete", + "doc_type":"api", + "kw":"Querying Metadata of an EVS Disk,EVS Disk,API Reference", + "title":"Querying Metadata of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2076.html", + "product_code":"evs", + "code":"63", + "des":"This API is used to update the metadata of an EVS disk.URI formatPUT /v2/{project_id}/volumes/{volume_id}/metadataPUT /v2/{project_id}/volumes/{volume_id}/metadataParamet", + "doc_type":"api", + "kw":"Updating Metadata of an EVS Disk,EVS Disk,API Reference", + "title":"Updating Metadata of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2077.html", + "product_code":"evs", + "code":"64", + "des":"This API is used to query one piece of the EVS disk metadata.URI formatGET /v2/{project_id}/volumes/{volume_id}/metadata/{key}GET /v2/{project_id}/volumes/{volume_id}/met", + "doc_type":"api", + "kw":"Querying One Piece of Metadata for an EVS Disk,EVS Disk,API Reference", + "title":"Querying One Piece of Metadata for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2078.html", + "product_code":"evs", + "code":"65", + "des":"This API is used to update one piece of the EVS disk metadata.URI formatPUT /v2/{project_id}/volumes/{volume_id}/metadata/{key}PUT /v2/{project_id}/volumes/{volume_id}/me", + "doc_type":"api", + "kw":"Updating One Piece of Metadata for an EVS Disk,EVS Disk,API Reference", + "title":"Updating One Piece of Metadata for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2079.html", + "product_code":"evs", + "code":"66", + "des":"This API is used to delete one piece of the EVS disk metadata.URI formatDELETE /v2/{project_id}/volumes/{volume_id}/metadata/{key}DELETE /v2/{project_id}/volumes/{volume_", + "doc_type":"api", + "kw":"Deleting One Piece of Metadata for an EVS Disk,EVS Disk,API Reference", + "title":"Deleting One Piece of Metadata for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2080.html", + "product_code":"evs", + "code":"67", + "des":"This API is used to query extension APIs.URI formatGET /v2/{project_id}/extensionsGET /v2/{project_id}/extensionsParameter descriptionParameterMandatoryDescriptionproject", + "doc_type":"api", + "kw":"Querying Extension APIs,EVS Disk,API Reference", + "title":"Querying Extension APIs", + "githuburl":"" + }, + { + "uri":"evs_04_2081.html", + "product_code":"evs", + "code":"68", + "des":"This API is used to query all AZs.URI formatGET /v2/{project_id}/os-availability-zoneGET /v2/{project_id}/os-availability-zoneParameter descriptionParameterMandatoryDescr", + "doc_type":"api", + "kw":"Querying All AZs,EVS Disk,API Reference", + "title":"Querying All AZs", + "githuburl":"" + }, + { + "uri":"evs_04_2082.html", + "product_code":"evs", + "code":"69", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk Actions", + "title":"EVS Disk Actions", + "githuburl":"" + }, + { + "uri":"evs_04_2083.html", + "product_code":"evs", + "code":"70", + "des":"This API is used to expand the capacity of an EVS disk.If the status of the to-be-expanded disk is available, there are no restrictions.If the status of the to-be-expande", + "doc_type":"api", + "kw":"Expanding Capacity of an EVS Disk,EVS Disk Actions,API Reference", + "title":"Expanding Capacity of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2084.html", + "product_code":"evs", + "code":"71", + "des":"This API is used to set the bootable flag for an EVS disk.A data disk cannot be used as system disk for an ECS even if this API has been called to set the bootable flag f", + "doc_type":"api", + "kw":"Setting Bootable Flag for an EVS Disk,EVS Disk Actions,API Reference", + "title":"Setting Bootable Flag for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2085.html", + "product_code":"evs", + "code":"72", + "des":"This API is used to set the read-only flag for the EVS disk.URI formatPOST /v2/{project_id}/volumes/{volume_id}/actionPOST /v2/{project_id}/volumes/{volume_id}/actionPara", + "doc_type":"api", + "kw":"Setting Read-Only Flag for an EVS Disk,EVS Disk Actions,API Reference", + "title":"Setting Read-Only Flag for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_2086.html", + "product_code":"evs", + "code":"73", + "des":"This API is used to export the system disk data or data disk data as an IMS image. The exported image will be displayed in the IMS private image list and can be viewed an", + "doc_type":"api", + "kw":"Exporting EVS Disk Data as an Image,EVS Disk Actions,API Reference", + "title":"Exporting EVS Disk Data as an Image", + "githuburl":"" + }, + { + "uri":"evs_04_2087.html", + "product_code":"evs", + "code":"74", + "des":"This API is only used to change the EVS disk status from available to in-use.This API call exists for compatibility reasons only and is not meant to be used.Do not call t", + "doc_type":"api", + "kw":"Attaching an EVS Disk (Deprecated),EVS Disk Actions,API Reference", + "title":"Attaching an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2088.html", + "product_code":"evs", + "code":"75", + "des":"This API is only used to change the EVS disk status from in-use to available.This API call exists for compatibility reasons only and is not meant to be used.Do not call t", + "doc_type":"api", + "kw":"Detaching an EVS Disk (Deprecated),EVS Disk Actions,API Reference", + "title":"Detaching an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2089.html", + "product_code":"evs", + "code":"76", + "des":"This API is used to reserve an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v2/{project_id}/volumes/{volume_id", + "doc_type":"api", + "kw":"Reserving an EVS Disk (Deprecated),EVS Disk Actions,API Reference", + "title":"Reserving an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2090.html", + "product_code":"evs", + "code":"77", + "des":"This API is used to cancel the reservation of an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v2/{project_id}/", + "doc_type":"api", + "kw":"Canceling Reservation of an EVS Disk (Deprecated),EVS Disk Actions,API Reference", + "title":"Canceling Reservation of an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_2092.html", + "product_code":"evs", + "code":"78", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Snapshot", + "title":"EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2093.html", + "product_code":"evs", + "code":"79", + "des":"This API is used to create an EVS snapshot.URI formatPOST /v2/{project_id}/snapshotsPOST /v2/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionproje", + "doc_type":"api", + "kw":"Creating an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Creating an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2094.html", + "product_code":"evs", + "code":"80", + "des":"This API is used to delete an EVS snapshot.A snapshot can be deleted only when it is in the available or error state.URI formatDELETE /v2/{project_id}/snapshots/{snapshot", + "doc_type":"api", + "kw":"Deleting an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Deleting an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2095.html", + "product_code":"evs", + "code":"81", + "des":"This API is used to update an EVS snapshot.URI formatPUT /v2/{project_id}/snapshots/{snapshot_id}PUT /v2/{project_id}/snapshots/{snapshot_id}Parameter descriptionParamete", + "doc_type":"api", + "kw":"Updating an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Updating an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2096.html", + "product_code":"evs", + "code":"82", + "des":"This API is used to query the EVS snapshots.URI formatGET /v2/{project_id}/snapshotsGET /v2/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionprojec", + "doc_type":"api", + "kw":"Querying EVS Snapshots,EVS Snapshot,API Reference", + "title":"Querying EVS Snapshots", + "githuburl":"" + }, + { + "uri":"evs_04_2097.html", + "product_code":"evs", + "code":"83", + "des":"This API is used to query details about the EVS snapshots.URI formatGET /v2/{project_id}/snapshots/detailGET /v2/{project_id}/snapshots/detailParameter descriptionParamet", + "doc_type":"api", + "kw":"Querying Details About EVS Snapshots,EVS Snapshot,API Reference", + "title":"Querying Details About EVS Snapshots", + "githuburl":"" + }, + { + "uri":"evs_04_2098.html", + "product_code":"evs", + "code":"84", + "des":"This API is used to query details about an EVS snapshot.URI formatGET /v2/{project_id}/snapshots/{snapshot_id}GET /v2/{project_id}/snapshots/{snapshot_id}Parameter descri", + "doc_type":"api", + "kw":"Querying Details About an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Querying Details About an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2099.html", + "product_code":"evs", + "code":"85", + "des":"This API is used to add the metadata of an EVS snapshot.URI formatPOST /v2/{project_id}/snapshots/{snapshot_id}/metadataPOST /v2/{project_id}/snapshots/{snapshot_id}/meta", + "doc_type":"api", + "kw":"Adding Metadata of an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Adding Metadata of an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2100.html", + "product_code":"evs", + "code":"86", + "des":"This API is used to query the metadata of an EVS snapshot.URI formatGET /v2/{project_id}/snapshots/{snapshot_id}/metadataGET /v2/{project_id}/snapshots/{snapshot_id}/meta", + "doc_type":"api", + "kw":"Querying Metadata of an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Querying Metadata of an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2101.html", + "product_code":"evs", + "code":"87", + "des":"This API is used to update one piece of the EVS snapshot metadata.URI formatPUT /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}PUT /v2/{project_id}/snapshots/{sna", + "doc_type":"api", + "kw":"Updating One Piece of Metadata for an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Updating One Piece of Metadata for an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2102.html", + "product_code":"evs", + "code":"88", + "des":"This API is used to update the metadata of an EVS snapshot.URI formatPUT /v2/{project_id}/snapshots/{snapshot_id}/metadataPUT /v2/{project_id}/snapshots/{snapshot_id}/met", + "doc_type":"api", + "kw":"Updating Metadata of an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Updating Metadata of an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2103.html", + "product_code":"evs", + "code":"89", + "des":"This API is used to query one piece of the EVS snapshot metadata.URI formatGET /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}GET /v2/{project_id}/snapshots/{snap", + "doc_type":"api", + "kw":"Querying One Piece of Metadata for an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Querying One Piece of Metadata for an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2104.html", + "product_code":"evs", + "code":"90", + "des":"This API is used to delete one piece of the EVS snapshot metadata.URI formatDELETE /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}DELETE /v2/{project_id}/snapshot", + "doc_type":"api", + "kw":"Deleting One Piece of Metadata for an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Deleting One Piece of Metadata for an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_2105.html", + "product_code":"evs", + "code":"91", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk Transfer", + "title":"EVS Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_2106.html", + "product_code":"evs", + "code":"92", + "des":"This API is used to create a disk transfer. After the transfer has been created, a transfer ID and an authentication key are returned.After a disk transfer is created, th", + "doc_type":"api", + "kw":"Creating a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Creating a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_2107.html", + "product_code":"evs", + "code":"93", + "des":"This API is used to accept a disk transfer through the transfer ID and authentication key.Encrypted EVS disks cannot be transferred.EVS disks with backups and snapshots a", + "doc_type":"api", + "kw":"Accepting a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Accepting a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_2108.html", + "product_code":"evs", + "code":"94", + "des":"This API is used to delete a disk transfer. A disk transfer can be deleted if it is not accepted. Accepted disk transfers cannot be deleted.URI formatDELETE /v2/{project_", + "doc_type":"api", + "kw":"Deleting a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Deleting a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_2109.html", + "product_code":"evs", + "code":"95", + "des":"This API is used to query the details of a disk transfer, including the transfer creation time, transfer ID, and transfer name.URI formatGET /v2/{project_id}/os-volume-tr", + "doc_type":"api", + "kw":"Querying Details of a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Querying Details of a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_2110.html", + "product_code":"evs", + "code":"96", + "des":"This API is used to query all disk transfers of the current tenant.URI formatGET /v2/{project_id}/os-volume-transferGET /v2/{project_id}/os-volume-transferParameter descr", + "doc_type":"api", + "kw":"Querying All Disk Transfers,EVS Disk Transfer,API Reference", + "title":"Querying All Disk Transfers", + "githuburl":"" + }, + { + "uri":"evs_04_2111.html", + "product_code":"evs", + "code":"97", + "des":"This API is used to query the details of all disk transfers, including the transfer creation time, transfer IDs, and transfer names.URI formatGET /v2/{project_id}/os-volu", + "doc_type":"api", + "kw":"Querying Details of All Disk Transfers,EVS Disk Transfer,API Reference", + "title":"Querying Details of All Disk Transfers", + "githuburl":"" + }, + { + "uri":"evs_04_0063.html", + "product_code":"evs", + "code":"98", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Unrecommended APIs", + "title":"Unrecommended APIs", + "githuburl":"" + }, + { + "uri":"evs_04_3001.html", + "product_code":"evs", + "code":"99", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"API v3", + "title":"API v3", + "githuburl":"" + }, + { + "uri":"evs_04_3002.html", + "product_code":"evs", + "code":"100", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk", + "title":"EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3003.html", + "product_code":"evs", + "code":"101", + "des":"This API is used to create one or multiple EVS disks.URI formatPOST /v3/{project_id}/cloudvolumesPOST /v3/{project_id}/cloudvolumesParameter descriptionParameterMandatory", + "doc_type":"api", + "kw":"Creating EVS Disks,EVS Disk,API Reference", + "title":"Creating EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_04_3004.html", + "product_code":"evs", + "code":"102", + "des":"This API is used to query details about all disks.URI formatGET /v3/{project_id}/os-vendor-volumes/detailGET /v3/{project_id}/os-vendor-volumes/detailParameter descriptio", + "doc_type":"api", + "kw":"Querying Details About All EVS Disks (Deprecated),EVS Disk,API Reference", + "title":"Querying Details About All EVS Disks (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_3005.html", + "product_code":"evs", + "code":"103", + "des":"This API is used to query details about a disk.URI formatGET /v3/{project_id}/os-vendor-volumes/{volume_id}GET /v3/{project_id}/os-vendor-volumes/{volume_id}Parameter des", + "doc_type":"api", + "kw":"Querying Details About an EVS Disk (Deprecated),EVS Disk,API Reference", + "title":"Querying Details About an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_3006.html", + "product_code":"evs", + "code":"104", + "des":"This API is used to query the loading progress of a lazyloading disk.URI formatGET /v3/{project_id}/os-vendor-volumes/{volume_id}/internal-infoGET /v3/{project_id}/os-ven", + "doc_type":"api", + "kw":"Querying Loading Progress of a Lazyloading Disk,EVS Disk,API Reference", + "title":"Querying Loading Progress of a Lazyloading Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3007.html", + "product_code":"evs", + "code":"105", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Snapshot", + "title":"EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3008.html", + "product_code":"evs", + "code":"106", + "des":"This API is used to roll back a snapshot to an EVS disk.When you roll back a snapshot to a disk, you can only roll back the snapshot to the source disk. Rollback to a spe", + "doc_type":"api", + "kw":"Rolling Back a Snapshot to an EVS Disk,EVS Snapshot,API Reference", + "title":"Rolling Back a Snapshot to an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3010.html", + "product_code":"evs", + "code":"107", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Tag", + "title":"EVS Tag", + "githuburl":"" + }, + { + "uri":"evs_04_3011.html", + "product_code":"evs", + "code":"108", + "des":"This API is used to batch add tags for the specified EVS disk.When adding tags, if a tag key is consistent with an existing one, the new tag will overwrite the existing t", + "doc_type":"api", + "kw":"Batch Adding Tags for the Specified EVS Disk,EVS Tag,API Reference", + "title":"Batch Adding Tags for the Specified EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3013.html", + "product_code":"evs", + "code":"109", + "des":"This API is used to batch delete tags for the specified EVS disk.NoneURI formatPOST /v3/{project_id}/os-vendor-volumes/{volume_id}/tags/actionPOST /v3/{project_id}/os-ven", + "doc_type":"api", + "kw":"Batch Deleting Tags for the Specified EVS Disk,EVS Tag,API Reference", + "title":"Batch Deleting Tags for the Specified EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3015.html", + "product_code":"evs", + "code":"110", + "des":"This API is used to query the tags of the specified EVS disk.NoneURI formatGET /v3/{project_id}/os-vendor-volumes/{volume_id}/tagsGET /v3/{project_id}/os-vendor-volumes/{", + "doc_type":"api", + "kw":"Querying Tags of an EVS Disk,EVS Tag,API Reference", + "title":"Querying Tags of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3016.html", + "product_code":"evs", + "code":"111", + "des":"This API is used to query the number of EVS disks by tag.NoneURI formatPOST /v3/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v3/{project_id}/os-vendor-vo", + "doc_type":"api", + "kw":"Querying the Number of EVS Disks by Tag,EVS Tag,API Reference", + "title":"Querying the Number of EVS Disks by Tag", + "githuburl":"" + }, + { + "uri":"evs_04_3018.html", + "product_code":"evs", + "code":"112", + "des":"This API is used to query the details of EVS disks by tag.NoneURI formatPOST /v3/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v3/{project_id}/os-vendor-v", + "doc_type":"api", + "kw":"Querying Details of EVS Disks by Tag,EVS Tag,API Reference", + "title":"Querying Details of EVS Disks by Tag", + "githuburl":"" + }, + { + "uri":"evs_04_3027.html", + "product_code":"evs", + "code":"113", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"OpenStack Cinder API v3", + "title":"OpenStack Cinder API v3", + "githuburl":"" + }, + { + "uri":"evs_04_3028.html", + "product_code":"evs", + "code":"114", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk", + "title":"EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3029.html", + "product_code":"evs", + "code":"115", + "des":"This API is used to create one or multiple EVS disks.URI formatPOST /v3/{project_id}/volumesPOST /v3/{project_id}/volumesParameter descriptionParameterMandatoryDescriptio", + "doc_type":"api", + "kw":"Creating EVS Disks,EVS Disk,API Reference", + "title":"Creating EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_04_3030.html", + "product_code":"evs", + "code":"116", + "des":"This API is used to delete an EVS disk.URI formatDELETE /v3/{project_id}/volumes/{volume_id}DELETE /v3/{project_id}/volumes/{volume_id}Parameter descriptionParameterManda", + "doc_type":"api", + "kw":"Deleting an EVS Disk,EVS Disk,API Reference", + "title":"Deleting an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3031.html", + "product_code":"evs", + "code":"117", + "des":"This API is used to update the EVS disk information.URI formatPUT /v3/{project_id}/volumes/{volume_id}PUT /v3/{project_id}/volumes/{volume_id}Parameter descriptionParamet", + "doc_type":"api", + "kw":"Updating an EVS Disk,EVS Disk,API Reference", + "title":"Updating an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3032.html", + "product_code":"evs", + "code":"118", + "des":"This API is used to query EVS disks.URI formatGET /v3/{project_id}/volumesGET /v3/{project_id}/volumesParameter descriptionParameterMandatoryDescriptionproject_idYesSpeci", + "doc_type":"api", + "kw":"Querying EVS Disks,EVS Disk,API Reference", + "title":"Querying EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_04_3033.html", + "product_code":"evs", + "code":"119", + "des":"This API is used to query details about all disks.URI formatGET /v3/{project_id}/volumes/detailGET /v3/{project_id}/volumes/detailParameter descriptionParameterMandatoryD", + "doc_type":"api", + "kw":"Querying Details About All Disks,EVS Disk,API Reference", + "title":"Querying Details About All Disks", + "githuburl":"" + }, + { + "uri":"evs_04_3034.html", + "product_code":"evs", + "code":"120", + "des":"This API is used to query details about a disk.URI formatGET /v3/{project_id}/volumes/{volume_id}GET /v3/{project_id}/volumes/{volume_id}Parameter descriptionParameterMan", + "doc_type":"api", + "kw":"Querying Details About a Disk,EVS Disk,API Reference", + "title":"Querying Details About a Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3035.html", + "product_code":"evs", + "code":"121", + "des":"This API is used to query EVS disk types and display the query results in a list.URI formatGET /v3/{project_id}/typesGET /v3/{project_id}/typesParameter descriptionParame", + "doc_type":"api", + "kw":"Querying EVS Disk Types,EVS Disk,API Reference", + "title":"Querying EVS Disk Types", + "githuburl":"" + }, + { + "uri":"evs_04_3036.html", + "product_code":"evs", + "code":"122", + "des":"This API is used to query details about an EVS disk type.URI formatGET /v3/{project_id}/types/{type_id}GET /v3/{project_id}/types/{type_id}Parameter descriptionParameterM", + "doc_type":"api", + "kw":"Querying Details About an EVS Disk Type,EVS Disk,API Reference", + "title":"Querying Details About an EVS Disk Type", + "githuburl":"" + }, + { + "uri":"evs_04_3037.html", + "product_code":"evs", + "code":"123", + "des":"This API is used to query the details of tenant quotas.URI formatGET /v3/{project_id}/os-quota-sets/{target_project_id}?usage=TrueGET /v3/{project_id}/os-quota-sets/{targ", + "doc_type":"api", + "kw":"Querying Details of Tenant Quotas,EVS Disk,API Reference", + "title":"Querying Details of Tenant Quotas", + "githuburl":"" + }, + { + "uri":"evs_04_3038.html", + "product_code":"evs", + "code":"124", + "des":"This API is used to add or update the metadata of an EVS disk.URI formatPOST /v3/{project_id}/volumes/{volume_id}/metadataPOST /v3/{project_id}/volumes/{volume_id}/metada", + "doc_type":"api", + "kw":"Adding Metadata of an EVS Disk,EVS Disk,API Reference", + "title":"Adding Metadata of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3039.html", + "product_code":"evs", + "code":"125", + "des":"This API is used to query the metadata of an EVS disk.URI formatGET /v3/{project_id}/volumes/{volume_id}/metadataGET /v3/{project_id}/volumes/{volume_id}/metadataParamete", + "doc_type":"api", + "kw":"Querying Metadata of an EVS Disk,EVS Disk,API Reference", + "title":"Querying Metadata of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3040.html", + "product_code":"evs", + "code":"126", + "des":"This API is used to update the metadata of an EVS disk.URI formatPUT /v3/{project_id}/volumes/{volume_id}/metadataPUT /v3/{project_id}/volumes/{volume_id}/metadataParamet", + "doc_type":"api", + "kw":"Updating Metadata of an EVS Disk,EVS Disk,API Reference", + "title":"Updating Metadata of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3041.html", + "product_code":"evs", + "code":"127", + "des":"This API is used to query one piece of the EVS disk metadata.URI formatGET /v3/{project_id}/volumes/{volume_id}/metadata/{key}GET /v3/{project_id}/volumes/{volume_id}/met", + "doc_type":"api", + "kw":"Querying One Piece of Metadata for an EVS Disk,EVS Disk,API Reference", + "title":"Querying One Piece of Metadata for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3042.html", + "product_code":"evs", + "code":"128", + "des":"This API is used to update one piece of the EVS disk metadata.URI formatPUT /v3/{project_id}/volumes/{volume_id}/metadata/{key}PUT /v3/{project_id}/volumes/{volume_id}/me", + "doc_type":"api", + "kw":"Updating One Piece of Metadata for an EVS Disk,EVS Disk,API Reference", + "title":"Updating One Piece of Metadata for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3043.html", + "product_code":"evs", + "code":"129", + "des":"This API is used to delete one piece of the EVS disk metadata.URI formatDELETE /v3/{project_id}/volumes/{volume_id}/metadata/{key}DELETE /v3/{project_id}/volumes/{volume_", + "doc_type":"api", + "kw":"Deleting One Piece of Metadata for an EVS Disk,EVS Disk,API Reference", + "title":"Deleting One Piece of Metadata for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3044.html", + "product_code":"evs", + "code":"130", + "des":"This API is used to query extension APIs.URI formatGET /v3/{project_id}/extensionsGET /v3/{project_id}/extensionsParameter descriptionParameterMandatoryDescriptionproject", + "doc_type":"api", + "kw":"Querying Extension APIs,EVS Disk,API Reference", + "title":"Querying Extension APIs", + "githuburl":"" + }, + { + "uri":"evs_04_3045.html", + "product_code":"evs", + "code":"131", + "des":"This API is used to query all AZs.URI formatGET /v3/{project_id}/os-availability-zoneGET /v3/{project_id}/os-availability-zoneParameter descriptionParameterMandatoryDescr", + "doc_type":"api", + "kw":"Querying All AZs,EVS Disk,API Reference", + "title":"Querying All AZs", + "githuburl":"" + }, + { + "uri":"evs_04_3047.html", + "product_code":"evs", + "code":"132", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk Actions", + "title":"EVS Disk Actions", + "githuburl":"" + }, + { + "uri":"evs_04_3048.html", + "product_code":"evs", + "code":"133", + "des":"This API is used to expand the capacity of an EVS disk.If the status of the to-be-expanded disk is available, there are no restrictions.If the status of the to-be-expande", + "doc_type":"api", + "kw":"Expanding Capacity of an EVS Disk,EVS Disk Actions,API Reference", + "title":"Expanding Capacity of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3049.html", + "product_code":"evs", + "code":"134", + "des":"This API is used to set the bootable flag for an EVS disk.A data disk cannot be used as system disk for an ECS even if this API has been called to set the bootable flag f", + "doc_type":"api", + "kw":"Setting Bootable Flag for an EVS Disk,EVS Disk Actions,API Reference", + "title":"Setting Bootable Flag for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3050.html", + "product_code":"evs", + "code":"135", + "des":"This API is used to set the read-only flag for the EVS disk.URI formatPOST /v3/{project_id}/volumes/{volume_id}/actionPOST /v3/{project_id}/volumes/{volume_id}/actionPara", + "doc_type":"api", + "kw":"Setting Read-Only Flag for an EVS Disk,EVS Disk Actions,API Reference", + "title":"Setting Read-Only Flag for an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_3051.html", + "product_code":"evs", + "code":"136", + "des":"This API is used to export the system disk data or data disk data as an IMS image. The exported image will be displayed in the IMS private image list and can be viewed an", + "doc_type":"api", + "kw":"Exporting EVS Disk Data as an Image,EVS Disk Actions,API Reference", + "title":"Exporting EVS Disk Data as an Image", + "githuburl":"" + }, + { + "uri":"evs_04_3052.html", + "product_code":"evs", + "code":"137", + "des":"This API is used to reserve an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v3/{project_id}/volumes/{volume_id", + "doc_type":"api", + "kw":"Reserving an EVS Disk (Deprecated),EVS Disk Actions,API Reference", + "title":"Reserving an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_3053.html", + "product_code":"evs", + "code":"138", + "des":"This API is used to cancel the reservation of an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v3/{project_id}/", + "doc_type":"api", + "kw":"Canceling Reservation of an EVS Disk (Deprecated),EVS Disk Actions,API Reference", + "title":"Canceling Reservation of an EVS Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_3055.html", + "product_code":"evs", + "code":"139", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Snapshot", + "title":"EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3056.html", + "product_code":"evs", + "code":"140", + "des":"This API is used to create an EVS snapshot.URI formatPOST /v3/{project_id}/snapshotsPOST /v3/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionproje", + "doc_type":"api", + "kw":"Creating an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Creating an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3057.html", + "product_code":"evs", + "code":"141", + "des":"This API is used to delete an EVS snapshot.A snapshot can be deleted only when it is in the available or error state.URI formatDELETE /v3/{project_id}/snapshots/{snapshot", + "doc_type":"api", + "kw":"Deleting an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Deleting an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3058.html", + "product_code":"evs", + "code":"142", + "des":"This API is used to update an EVS snapshot.URI formatPUT /v3/{project_id}/snapshots/{snapshot_id}PUT /v3/{project_id}/snapshots/{snapshot_id}Parameter descriptionParamete", + "doc_type":"api", + "kw":"Updating an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Updating an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3059.html", + "product_code":"evs", + "code":"143", + "des":"This API is used to query the EVS snapshots.URI formatGET /v3/{project_id}/snapshotsGET /v3/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionprojec", + "doc_type":"api", + "kw":"Querying EVS Snapshots,EVS Snapshot,API Reference", + "title":"Querying EVS Snapshots", + "githuburl":"" + }, + { + "uri":"evs_04_3060.html", + "product_code":"evs", + "code":"144", + "des":"This API is used to query details about the EVS snapshots.URI formatGET /v3/{project_id}/snapshots/detailGET /v3/{project_id}/snapshots/detailParameter descriptionParamet", + "doc_type":"api", + "kw":"Querying Details About EVS Snapshots,EVS Snapshot,API Reference", + "title":"Querying Details About EVS Snapshots", + "githuburl":"" + }, + { + "uri":"evs_04_3061.html", + "product_code":"evs", + "code":"145", + "des":"This API is used to query details about an EVS snapshot.URI formatGET /v3/{project_id}/snapshots/{snapshot_id}GET /v3/{project_id}/snapshots/{snapshot_id}Parameter descri", + "doc_type":"api", + "kw":"Querying Details About an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Querying Details About an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3062.html", + "product_code":"evs", + "code":"146", + "des":"This API is used to add the metadata of an EVS snapshot.URI formatPOST /v3/{project_id}/snapshots/{snapshot_id}/metadataPOST /v3/{project_id}/snapshots/{snapshot_id}/meta", + "doc_type":"api", + "kw":"Adding Metadata of an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Adding Metadata of an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3063.html", + "product_code":"evs", + "code":"147", + "des":"This API is used to query the metadata of an EVS snapshot.URI formatGET /v3/{project_id}/snapshots/{snapshot_id}/metadataGET /v3/{project_id}/snapshots/{snapshot_id}/meta", + "doc_type":"api", + "kw":"Querying Metadata of an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Querying Metadata of an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3064.html", + "product_code":"evs", + "code":"148", + "des":"This API is used to update one piece of the EVS snapshot metadata.URI formatPUT /v3/{project_id}/snapshots/{snapshot_id}/metadata/{key}PUT /v3/{project_id}/snapshots/{sna", + "doc_type":"api", + "kw":"Updating One Piece of Metadata for an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Updating One Piece of Metadata for an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3065.html", + "product_code":"evs", + "code":"149", + "des":"This API is used to update the metadata of an EVS snapshot.URI formatPUT /v3/{project_id}/snapshots/{snapshot_id}/metadataPUT /v3/{project_id}/snapshots/{snapshot_id}/met", + "doc_type":"api", + "kw":"Updating Metadata of an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Updating Metadata of an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3066.html", + "product_code":"evs", + "code":"150", + "des":"This API is used to query one piece of the EVS snapshot metadata.URI formatGET /v3/{project_id}/snapshots/{snapshot_id}/metadata/{key}GET /v3/{project_id}/snapshots/{snap", + "doc_type":"api", + "kw":"Querying One Piece of Metadata for an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Querying One Piece of Metadata for an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3067.html", + "product_code":"evs", + "code":"151", + "des":"This API is used to delete one piece of the EVS snapshot metadata.URI formatDELETE /v3/{project_id}/snapshots/{snapshot_id}/metadata/{key}DELETE /v3/{project_id}/snapshot", + "doc_type":"api", + "kw":"Deleting One Piece of Metadata for an EVS Snapshot,EVS Snapshot,API Reference", + "title":"Deleting One Piece of Metadata for an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_3068.html", + "product_code":"evs", + "code":"152", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk Transfer", + "title":"EVS Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_3069.html", + "product_code":"evs", + "code":"153", + "des":"This API is used to create a disk transfer. After the transfer has been created, a transfer ID and an authentication key are returned.After a disk transfer is created, th", + "doc_type":"api", + "kw":"Creating a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Creating a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_3070.html", + "product_code":"evs", + "code":"154", + "des":"This API is used to accept a disk transfer through the transfer ID and authentication key.Encrypted EVS disks cannot be transferred.EVS disks with backups and snapshots a", + "doc_type":"api", + "kw":"Accepting a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Accepting a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_3071.html", + "product_code":"evs", + "code":"155", + "des":"This API is used to delete a disk transfer. A disk transfer can be deleted if it is not accepted. Accepted disk transfers cannot be deleted.URI formatDELETE /v3/{project_", + "doc_type":"api", + "kw":"Deleting a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Deleting a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_3072.html", + "product_code":"evs", + "code":"156", + "des":"This API is used to query the details of a disk transfer, including the transfer creation time, transfer ID, and transfer name.URI formatGET /v3/{project_id}/os-volume-tr", + "doc_type":"api", + "kw":"Querying Details of a Disk Transfer,EVS Disk Transfer,API Reference", + "title":"Querying Details of a Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_3073.html", + "product_code":"evs", + "code":"157", + "des":"This API is used to query all disk transfers of the current tenant.URI formatGET /v3/{project_id}/os-volume-transferGET /v3/{project_id}/os-volume-transferParameter descr", + "doc_type":"api", + "kw":"Querying All Disk Transfers,EVS Disk Transfer,API Reference", + "title":"Querying All Disk Transfers", + "githuburl":"" + }, + { + "uri":"evs_04_3074.html", + "product_code":"evs", + "code":"158", + "des":"This API is used to query the details of all disk transfers, including the transfer creation time, transfer IDs, and transfer names.URI formatGET /v3/{project_id}/os-volu", + "doc_type":"api", + "kw":"Querying Details of All Disk Transfers,EVS Disk Transfer,API Reference", + "title":"Querying Details of All Disk Transfers", + "githuburl":"" + }, + { + "uri":"evs_04_0053.html", + "product_code":"evs", + "code":"159", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"API v1", + "title":"API v1", + "githuburl":"" + }, + { + "uri":"evs_04_0054.html", + "product_code":"evs", + "code":"160", + "des":"This API is used to query the execution status of tasks, such as the status of disk creation, capacity expansion, and deletion.URI formatGET /v1/{project_id}/jobs/{job_id", + "doc_type":"api", + "kw":"Querying Task Status,API v1,API Reference", + "title":"Querying Task Status", + "githuburl":"" + }, + { + "uri":"evs_04_0050.html", + "product_code":"evs", + "code":"161", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"OpenStack Cinder API v1 (Deprecated)", + "title":"OpenStack Cinder API v1 (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_0051.html", + "product_code":"evs", + "code":"162", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk", + "title":"EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_04_0052.html", + "product_code":"evs", + "code":"163", + "des":"This API is used to query details about a disk.This API has been deprecated. Use another API. For details, see Querying Details About a Disk.URI formatGET /v1/{project_id", + "doc_type":"api", + "kw":"Querying Details About a Disk (Deprecated),EVS Disk,API Reference", + "title":"Querying Details About a Disk (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_0022.html", + "product_code":"evs", + "code":"164", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Permissions Policies and Supported Actions", + "title":"Permissions Policies and Supported Actions", + "githuburl":"" + }, + { + "uri":"evs_04_0023.html", + "product_code":"evs", + "code":"165", + "des":"This chapter describes fine-grained permissions management for your EVS resources. If your account does not need individual IAM users, you can skip this chapter.By defaul", + "doc_type":"api", + "kw":"Introduction,Permissions Policies and Supported Actions,API Reference", + "title":"Introduction", + "githuburl":"" + }, + { + "uri":"evs_04_0024.html", + "product_code":"evs", + "code":"166", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"API Version Query,Permissions Policies and Supported Actions,API Reference", + "title":"API Version Query", + "githuburl":"" + }, + { + "uri":"evs_04_0025.html", + "product_code":"evs", + "code":"167", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"Disk,Permissions Policies and Supported Actions,API Reference", + "title":"Disk", + "githuburl":"" + }, + { + "uri":"evs_04_0026.html", + "product_code":"evs", + "code":"168", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"Disk Action,Permissions Policies and Supported Actions,API Reference", + "title":"Disk Action", + "githuburl":"" + }, + { + "uri":"evs_04_0027.html", + "product_code":"evs", + "code":"169", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"Snapshot,Permissions Policies and Supported Actions,API Reference", + "title":"Snapshot", + "githuburl":"" + }, + { + "uri":"evs_04_0028.html", + "product_code":"evs", + "code":"170", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"Tag,Permissions Policies and Supported Actions,API Reference", + "title":"Tag", + "githuburl":"" + }, + { + "uri":"evs_04_0029.html", + "product_code":"evs", + "code":"171", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"Disk Transfer,Permissions Policies and Supported Actions,API Reference", + "title":"Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_04_0037.html", + "product_code":"evs", + "code":"172", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Appendix", + "title":"Appendix", + "githuburl":"" + }, + { + "uri":"evs_04_0038.html", + "product_code":"evs", + "code":"173", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Error Codes,Appendix,API Reference", + "title":"Error Codes", + "githuburl":"" + }, + { + "uri":"evs_04_0039.html", + "product_code":"evs", + "code":"174", + "des":"NormalStatus CodeDescription200OK201Created202Accepted204No ContentAbnormalStatus CodeDescription400Bad Request401Unauthorized403Forbidden404Not Found405Method Not Allowe", + "doc_type":"api", + "kw":"Status Codes,Appendix,API Reference", + "title":"Status Codes", + "githuburl":"" + }, + { + "uri":"evs_04_0040.html", + "product_code":"evs", + "code":"175", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Disk Status,Appendix,API Reference", + "title":"EVS Disk Status", + "githuburl":"" + }, + { + "uri":"evs_04_0041.html", + "product_code":"evs", + "code":"176", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Snapshot Status,Appendix,API Reference", + "title":"EVS Snapshot Status", + "githuburl":"" + }, + { + "uri":"evs_04_0042.html", + "product_code":"evs", + "code":"177", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"EVS Replication Pair Status (Deprecated),Appendix,API Reference", + "title":"EVS Replication Pair Status (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_0043.html", + "product_code":"evs", + "code":"178", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Replication Consistency Group Status (Deprecated),Appendix,API Reference", + "title":"Replication Consistency Group Status (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_0044.html", + "product_code":"evs", + "code":"179", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Details of EVS Replication failure_detail Values (Deprecated),Appendix,API Reference", + "title":"Details of EVS Replication failure_detail Values (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_04_0045.html", + "product_code":"evs", + "code":"180", + "des":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "doc_type":"api", + "kw":"API Actions,Appendix,API Reference", + "title":"API Actions", + "githuburl":"" + }, + { + "uri":"evs_04_0048.html", + "product_code":"evs", + "code":"181", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api", + "kw":"Change History,API Reference", + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/evs/api-ref/CLASS.TXT.json b/docs/evs/api-ref/CLASS.TXT.json new file mode 100644 index 000000000..4b59c946f --- /dev/null +++ b/docs/evs/api-ref/CLASS.TXT.json @@ -0,0 +1,1631 @@ +[ + { + "desc":"Public cloud Application Programming Interfaces (APIs) comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource ", + "product_code":"evs", + "title":"API Usage Guidelines", + "uri":"evs_04_0001.html", + "doc_type":"api", + "p_code":"", + "code":"1" + }, + { + "desc":"EVS APIs provide multiple versions. For the APIs offering same functions, you are recommended to use the v2 APIs.The current default microversion of v3 APIs is 3.0, and t", + "product_code":"evs", + "title":"API Version Description and Usage Instructions", + "uri":"evs_04_0018.html", + "doc_type":"api", + "p_code":"", + "code":"2" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"API Version Query", + "uri":"evs_04_0019.html", + "doc_type":"api", + "p_code":"", + "code":"3" + }, + { + "desc":"This API is used to query information of API versions.URI formatGET /GET /Example requestGET https://{endpoint}/Parameter descriptionParameterTypeDescriptionversionsArray", + "product_code":"evs", + "title":"Querying Information of API Versions", + "uri":"evs_04_0020.html", + "doc_type":"api", + "p_code":"3", + "code":"4" + }, + { + "desc":"This API is used to query information of an API version.URI formatGET /{api_version}GET /{api_version}Parameter descriptionParameterTypeDescriptionapi_versionStringSpecif", + "product_code":"evs", + "title":"Querying Information of an API Version", + "uri":"evs_04_0021.html", + "doc_type":"api", + "p_code":"3", + "code":"5" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"API v2 (Recommended)", + "uri":"evs_04_2001.html", + "doc_type":"api", + "p_code":"", + "code":"6" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk", + "uri":"evs_04_2002.html", + "doc_type":"api", + "p_code":"6", + "code":"7" + }, + { + "desc":"This API is used to create one or multiple EVS disks.URI formatPOST /v2/{project_id}/cloudvolumesPOST /v2/{project_id}/cloudvolumesParameter descriptionParameterMandatory", + "product_code":"evs", + "title":"Creating EVS Disks", + "uri":"evs_04_2013.html", + "doc_type":"api", + "p_code":"7", + "code":"8" + }, + { + "desc":"This API is used to query details about all disks.URI formatGET /v2/{project_id}/cloudvolumes/detailGET /v2/{project_id}/cloudvolumes/detailParameter descriptionParameter", + "product_code":"evs", + "title":"Querying Details About All Disks", + "uri":"evs_04_2005.html", + "doc_type":"api", + "p_code":"7", + "code":"9" + }, + { + "desc":"This API is used to delete an EVS disk.URI formatDELETE /v2/{project_id}/cloudvolumes/{volume_id}DELETE /v2/{project_id}/cloudvolumes/{volume_id}Parameter descriptionPara", + "product_code":"evs", + "title":"Deleting an EVS Disk", + "uri":"evs_04_2008.html", + "doc_type":"api", + "p_code":"7", + "code":"10" + }, + { + "desc":"This API is used to update the name and description of an EVS disk.This API has been deprecated. Use another API. For details, see Updating an EVS Disk.URI formatPUT /v2/", + "product_code":"evs", + "title":"Updating an EVS Disk (Deprecated)", + "uri":"evs_04_2009.html", + "doc_type":"api", + "p_code":"7", + "code":"11" + }, + { + "desc":"This API is used to query details about all disks.URI formatGET /v2/{project_id}/os-vendor-volumes/detailGET /v2/{project_id}/os-vendor-volumes/detailParameter descriptio", + "product_code":"evs", + "title":"Querying Details About All Disks (Deprecated)", + "uri":"evs_04_2010.html", + "doc_type":"api", + "p_code":"7", + "code":"12" + }, + { + "desc":"This API is used to query details about a disk.URI formatGET /v2/{project_id}/os-vendor-volumes/{volume_id}GET /v2/{project_id}/os-vendor-volumes/{volume_id}Parameter des", + "product_code":"evs", + "title":"Querying Details About a Disk", + "uri":"evs_04_2011.html", + "doc_type":"api", + "p_code":"7", + "code":"13" + }, + { + "desc":"This API is used to query EVS disks and display the query results in a list.This API has been deprecated. Use another API. For details, see Querying EVS Disks.URI formatG", + "product_code":"evs", + "title":"Querying EVS Disks (Deprecated)", + "uri":"evs_04_2012.html", + "doc_type":"api", + "p_code":"7", + "code":"14" + }, + { + "desc":"This API is used to expand the capacity of an EVS disk.If the status of the to-be-expanded disk is available, there are no restrictions.If the status of the to-be-expande", + "product_code":"evs", + "title":"Expanding Capacity of an EVS Disk (Deprecated)", + "uri":"evs_04_2014.html", + "doc_type":"api", + "p_code":"7", + "code":"15" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Snapshot", + "uri":"evs_04_2015.html", + "doc_type":"api", + "p_code":"6", + "code":"16" + }, + { + "desc":"This API is used to roll back a snapshot to an EVS disk.When you roll back a snapshot to a disk, you can only roll back the snapshot to the source disk. Rollback to a spe", + "product_code":"evs", + "title":"Rolling Back a Snapshot to an EVS Disk", + "uri":"evs_04_2022.html", + "doc_type":"api", + "p_code":"16", + "code":"17" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Tag", + "uri":"evs_04_2024.html", + "doc_type":"api", + "p_code":"6", + "code":"18" + }, + { + "desc":"This API is used to delete tags of an EVS resource by key.NoneURI formatDELETE /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}DELETE /v2/{project_id}/", + "product_code":"evs", + "title":"Deleting Tags of an EVS Resource by Key", + "uri":"evs_04_2025.html", + "doc_type":"api", + "p_code":"18", + "code":"19" + }, + { + "desc":"This API is used to obtain all tags of an EVS resource type.NoneURI formatGET /v2/{project_id}/os-vendor-tags/{resource_type}GET /v2/{project_id}/os-vendor-tags/{resource", + "product_code":"evs", + "title":"Obtaining All Tags of an EVS Resource Type", + "uri":"evs_04_2026.html", + "doc_type":"api", + "p_code":"18", + "code":"20" + }, + { + "desc":"This API is used to batch add tags for the specified EVS disk.When adding tags, if a tag key is consistent with an existing one, the new tag will overwrite the existing t", + "product_code":"evs", + "title":"Batch Adding Tags for the Specified EVS Disk", + "uri":"evs_04_2027.html", + "doc_type":"api", + "p_code":"18", + "code":"21" + }, + { + "desc":"This API is used to batch delete tags for the specified EVS disk.NoneURI formatPOST /v2/{project_id}/os-vendor-volumes/{volume_id}/tags/actionPOST /v2/{project_id}/os-ven", + "product_code":"evs", + "title":"Batch Deleting Tags for the Specified EVS Disk", + "uri":"evs_04_2029.html", + "doc_type":"api", + "p_code":"18", + "code":"22" + }, + { + "desc":"This API is used to query the tags of the specified EVS disk.NoneURI formatGET /v2/{project_id}/os-vendor-volumes/{volume_id}/tagsGET /v2/{project_id}/os-vendor-volumes/{", + "product_code":"evs", + "title":"Querying Tags of an EVS Disk", + "uri":"evs_04_2031.html", + "doc_type":"api", + "p_code":"18", + "code":"23" + }, + { + "desc":"This API is used to query the number of EVS disks by tag.NoneURI formatPOST /v2/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v2/{project_id}/os-vendor-vo", + "product_code":"evs", + "title":"Querying the Number of EVS Disks by Tag", + "uri":"evs_04_2032.html", + "doc_type":"api", + "p_code":"18", + "code":"24" + }, + { + "desc":"This API is used to query the details of EVS disks by tag.NoneURI formatPOST /v2/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v2/{project_id}/os-vendor-v", + "product_code":"evs", + "title":"Querying Details of EVS Disks by Tag", + "uri":"evs_04_2034.html", + "doc_type":"api", + "p_code":"18", + "code":"25" + }, + { + "desc":"This API is used to add or update tags for an EVS resource.This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.A ", + "product_code":"evs", + "title":"Adding or Updating Tags for an EVS Resource (Deprecated)", + "uri":"evs_04_2036.html", + "doc_type":"api", + "p_code":"18", + "code":"26" + }, + { + "desc":"This API is used to batch delete tags for an EVS resource.This API has been deprecated. Use another API. For details, see Batch Deleting Tags for the Specified EVS Disk.N", + "product_code":"evs", + "title":"Batch Deleting Tags for an EVS Resource (Deprecated)", + "uri":"evs_04_2037.html", + "doc_type":"api", + "p_code":"18", + "code":"27" + }, + { + "desc":"This API is used to obtain the tags of a specified EVS resource.This API has been deprecated. Use another API. For details, see Querying Tags of an EVS Disk.NoneURI forma", + "product_code":"evs", + "title":"Obtaining Tags of a Specified EVS Resource (Deprecated)", + "uri":"evs_04_2038.html", + "doc_type":"api", + "p_code":"18", + "code":"28" + }, + { + "desc":"This API is used to query tags of an EVS resource by key.This API has been deprecated. Use another API. For details, see Querying Tags of an EVS Disk.NoneURI formatGET /v", + "product_code":"evs", + "title":"Querying Tags of an EVS Resource by Key (Deprecated)", + "uri":"evs_04_2039.html", + "doc_type":"api", + "p_code":"18", + "code":"29" + }, + { + "desc":"This API is used to reset the tags of an EVS resource, and the existing tags will be deleted.This API call exists for compatibility reasons only and has been deprecated.A", + "product_code":"evs", + "title":"Resetting Tags of an EVS Resource (Deprecated)", + "uri":"evs_04_2040.html", + "doc_type":"api", + "p_code":"18", + "code":"30" + }, + { + "desc":"This API is used to update tags of an EVS resource by key.This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.A t", + "product_code":"evs", + "title":"Updating Tags of an EVS Resource by Key (Deprecated)", + "uri":"evs_04_2041.html", + "doc_type":"api", + "p_code":"18", + "code":"31" + }, + { + "desc":"This API is used to query the EVS resources by tag.This API has been deprecated. Use another API. For details, see Querying Details of EVS Disks by Tag.NoneURI formatGET ", + "product_code":"evs", + "title":"Querying EVS Resources by Tag (Deprecated)", + "uri":"evs_04_2042.html", + "doc_type":"api", + "p_code":"18", + "code":"32" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Replication Pair (Deprecated)", + "uri":"evs_04_2043.html", + "doc_type":"api", + "p_code":"6", + "code":"33" + }, + { + "desc":"This API is used to create an EVS replication pair using a specified production disk and a disaster recovery (DR) disk. The production disk is in the primary AZ, and the ", + "product_code":"evs", + "title":"Creating an EVS Replication Pair (Deprecated)", + "uri":"evs_04_2044.html", + "doc_type":"api", + "p_code":"33", + "code":"34" + }, + { + "desc":"This API is used to delete a specified EVS replication pair.This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.The to", + "product_code":"evs", + "title":"Deleting an EVS Replication Pair (Deprecated)", + "uri":"evs_04_2045.html", + "doc_type":"api", + "p_code":"33", + "code":"35" + }, + { + "desc":"This API is used to query all EVS replication pairs of the current tenant.This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Re", + "product_code":"evs", + "title":"Querying All EVS Replication Pairs (Deprecated)", + "uri":"evs_04_2046.html", + "doc_type":"api", + "p_code":"33", + "code":"36" + }, + { + "desc":"This API is used to query the details about an EVS replication pair, including the name, ID, and status of the replication pair.This API has been deprecated. To use this ", + "product_code":"evs", + "title":"Querying Details About an EVS Replication Pair (Deprecated)", + "uri":"evs_04_2047.html", + "doc_type":"api", + "p_code":"33", + "code":"37" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Replication Consistency Group (Deprecated)", + "uri":"evs_04_2048.html", + "doc_type":"api", + "p_code":"6", + "code":"38" + }, + { + "desc":"This API is used to create a replication consistency group for the specified EVS replication pairs.This API has been deprecated. To use this function, see Storage Disaste", + "product_code":"evs", + "title":"Creating a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2049.html", + "doc_type":"api", + "p_code":"38", + "code":"39" + }, + { + "desc":"This API is used to delete a replication consistency group.This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.All EVS", + "product_code":"evs", + "title":"Deleting a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2050.html", + "doc_type":"api", + "p_code":"38", + "code":"40" + }, + { + "desc":"This API is used to query all replication consistency groups of the current tenant.This API has been deprecated. To use this function, see Storage Disaster Recovery Servi", + "product_code":"evs", + "title":"Querying All Replication Consistency Groups (Deprecated)", + "uri":"evs_04_2051.html", + "doc_type":"api", + "p_code":"38", + "code":"41" + }, + { + "desc":"This API is used to query the details about a replication consistency group, including the name, ID, and status of the consistency group.This API has been deprecated. To ", + "product_code":"evs", + "title":"Querying Details About a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2052.html", + "doc_type":"api", + "p_code":"38", + "code":"42" + }, + { + "desc":"This API is used to update a replication consistency group. An update includes the following operations:Update the name or description of the replication consistency grou", + "product_code":"evs", + "title":"Updating a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2053.html", + "doc_type":"api", + "p_code":"38", + "code":"43" + }, + { + "desc":"This API is used to perform a failover for a replication consistency group. When an exception occurs in the primary AZ, a failover can be performed to change the primary ", + "product_code":"evs", + "title":"Performing a Failover for a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2054.html", + "doc_type":"api", + "p_code":"38", + "code":"44" + }, + { + "desc":"This API is used to synchronize the data between production disks and DR disks in all EVS replication pairs of a replication consistency group. After the synchronization ", + "product_code":"evs", + "title":"Synchronizing a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2055.html", + "doc_type":"api", + "p_code":"38", + "code":"45" + }, + { + "desc":"This API is used to perform a primary/secondary switchover for a replication consistency group. A switchover can be performed to switch the primary and secondary AZs of a", + "product_code":"evs", + "title":"Performing a Primary/Secondary Switchover for a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2056.html", + "doc_type":"api", + "p_code":"38", + "code":"46" + }, + { + "desc":"This API is used to pause a replication consistency group, that is, to pause the data synchronization in all EVS replication pairs of a replication consistency group.Befo", + "product_code":"evs", + "title":"Pausing a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2057.html", + "doc_type":"api", + "p_code":"38", + "code":"47" + }, + { + "desc":"This API is used to reprotect a replication consistency group. After resources in a faulty AZ have been restored and functioned as DR resources, a reprotection can be per", + "product_code":"evs", + "title":"Reprotecting a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2058.html", + "doc_type":"api", + "p_code":"38", + "code":"48" + }, + { + "desc":"This API is used to expand the EVS disks in one or multiple EVS replication pairs. In such an expansion operation, two EVS disks in one EVS replication pair are expanded ", + "product_code":"evs", + "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", + "uri":"evs_04_2059.html", + "doc_type":"api", + "p_code":"38", + "code":"49" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"OpenStack Cinder API v2 (Recommended)", + "uri":"evs_04_2063.html", + "doc_type":"api", + "p_code":"", + "code":"50" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk", + "uri":"evs_04_2064.html", + "doc_type":"api", + "p_code":"50", + "code":"51" + }, + { + "desc":"This API is used to create one or multiple EVS disks.URI formatPOST /v2/{project_id}/volumesPOST /v2/{project_id}/volumesParameter descriptionParameterMandatoryDescriptio", + "product_code":"evs", + "title":"Creating EVS Disks", + "uri":"evs_04_2065.html", + "doc_type":"api", + "p_code":"51", + "code":"52" + }, + { + "desc":"This API is used to delete an EVS disk.URI formatDELETE /v2/{project_id}/volumes/{volume_id}DELETE /v2/{project_id}/volumes/{volume_id}Parameter descriptionParameterManda", + "product_code":"evs", + "title":"Deleting an EVS Disk", + "uri":"evs_04_2066.html", + "doc_type":"api", + "p_code":"51", + "code":"53" + }, + { + "desc":"This API is used to update the EVS disk information.URI formatPUT /v2/{project_id}/volumes/{volume_id}PUT /v2/{project_id}/volumes/{volume_id}Parameter descriptionParamet", + "product_code":"evs", + "title":"Updating an EVS Disk", + "uri":"evs_04_2067.html", + "doc_type":"api", + "p_code":"51", + "code":"54" + }, + { + "desc":"This API is used to query EVS disks.URI formatGET /v2/{project_id}/volumesGET /v2/{project_id}/volumesParameter descriptionParameterMandatoryDescriptionproject_idYesSpeci", + "product_code":"evs", + "title":"Querying EVS Disks", + "uri":"evs_04_2068.html", + "doc_type":"api", + "p_code":"51", + "code":"55" + }, + { + "desc":"This API is used to query details about all disks.URI formatGET /v2/{project_id}/volumes/detailGET /v2/{project_id}/volumes/detailParameter descriptionParameterMandatoryD", + "product_code":"evs", + "title":"Querying Details About All Disks", + "uri":"evs_04_2069.html", + "doc_type":"api", + "p_code":"51", + "code":"56" + }, + { + "desc":"This API is used to query details about a disk.URI formatGET /v2/{project_id}/volumes/{volume_id}GET /v2/{project_id}/volumes/{volume_id}Parameter descriptionParameterMan", + "product_code":"evs", + "title":"Querying Details About a Disk", + "uri":"evs_04_2070.html", + "doc_type":"api", + "p_code":"51", + "code":"57" + }, + { + "desc":"This API is used to query EVS disk types and display the query results in a list.URI formatGET /v2/{project_id}/typesGET /v2/{project_id}/typesParameter descriptionParame", + "product_code":"evs", + "title":"Querying EVS Disk Types", + "uri":"evs_04_2071.html", + "doc_type":"api", + "p_code":"51", + "code":"58" + }, + { + "desc":"This API is used to query details about an EVS disk type.URI formatGET /v2/{project_id}/types/{type_id}GET /v2/{project_id}/types/{type_id}Parameter descriptionParameterM", + "product_code":"evs", + "title":"Querying Details About an EVS Disk Type", + "uri":"evs_04_2072.html", + "doc_type":"api", + "p_code":"51", + "code":"59" + }, + { + "desc":"This API is used to query the details of tenant quotas.URI formatGET /v2/{project_id}/os-quota-sets/{target_project_id}?usage=TrueGET /v2/{project_id}/os-quota-sets/{targ", + "product_code":"evs", + "title":"Querying Details of Tenant Quotas", + "uri":"evs_04_2073.html", + "doc_type":"api", + "p_code":"51", + "code":"60" + }, + { + "desc":"This API is used to add or update the metadata of an EVS disk.URI formatPOST /v2/{project_id}/volumes/{volume_id}/metadataPOST /v2/{project_id}/volumes/{volume_id}/metada", + "product_code":"evs", + "title":"Adding Metadata of an EVS Disk", + "uri":"evs_04_2074.html", + "doc_type":"api", + "p_code":"51", + "code":"61" + }, + { + "desc":"This API is used to query the metadata of an EVS disk.URI formatGET /v2/{project_id}/volumes/{volume_id}/metadataGET /v2/{project_id}/volumes/{volume_id}/metadataParamete", + "product_code":"evs", + "title":"Querying Metadata of an EVS Disk", + "uri":"evs_04_2075.html", + "doc_type":"api", + "p_code":"51", + "code":"62" + }, + { + "desc":"This API is used to update the metadata of an EVS disk.URI formatPUT /v2/{project_id}/volumes/{volume_id}/metadataPUT /v2/{project_id}/volumes/{volume_id}/metadataParamet", + "product_code":"evs", + "title":"Updating Metadata of an EVS Disk", + "uri":"evs_04_2076.html", + "doc_type":"api", + "p_code":"51", + "code":"63" + }, + { + "desc":"This API is used to query one piece of the EVS disk metadata.URI formatGET /v2/{project_id}/volumes/{volume_id}/metadata/{key}GET /v2/{project_id}/volumes/{volume_id}/met", + "product_code":"evs", + "title":"Querying One Piece of Metadata for an EVS Disk", + "uri":"evs_04_2077.html", + "doc_type":"api", + "p_code":"51", + "code":"64" + }, + { + "desc":"This API is used to update one piece of the EVS disk metadata.URI formatPUT /v2/{project_id}/volumes/{volume_id}/metadata/{key}PUT /v2/{project_id}/volumes/{volume_id}/me", + "product_code":"evs", + "title":"Updating One Piece of Metadata for an EVS Disk", + "uri":"evs_04_2078.html", + "doc_type":"api", + "p_code":"51", + "code":"65" + }, + { + "desc":"This API is used to delete one piece of the EVS disk metadata.URI formatDELETE /v2/{project_id}/volumes/{volume_id}/metadata/{key}DELETE /v2/{project_id}/volumes/{volume_", + "product_code":"evs", + "title":"Deleting One Piece of Metadata for an EVS Disk", + "uri":"evs_04_2079.html", + "doc_type":"api", + "p_code":"51", + "code":"66" + }, + { + "desc":"This API is used to query extension APIs.URI formatGET /v2/{project_id}/extensionsGET /v2/{project_id}/extensionsParameter descriptionParameterMandatoryDescriptionproject", + "product_code":"evs", + "title":"Querying Extension APIs", + "uri":"evs_04_2080.html", + "doc_type":"api", + "p_code":"51", + "code":"67" + }, + { + "desc":"This API is used to query all AZs.URI formatGET /v2/{project_id}/os-availability-zoneGET /v2/{project_id}/os-availability-zoneParameter descriptionParameterMandatoryDescr", + "product_code":"evs", + "title":"Querying All AZs", + "uri":"evs_04_2081.html", + "doc_type":"api", + "p_code":"51", + "code":"68" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk Actions", + "uri":"evs_04_2082.html", + "doc_type":"api", + "p_code":"50", + "code":"69" + }, + { + "desc":"This API is used to expand the capacity of an EVS disk.If the status of the to-be-expanded disk is available, there are no restrictions.If the status of the to-be-expande", + "product_code":"evs", + "title":"Expanding Capacity of an EVS Disk", + "uri":"evs_04_2083.html", + "doc_type":"api", + "p_code":"69", + "code":"70" + }, + { + "desc":"This API is used to set the bootable flag for an EVS disk.A data disk cannot be used as system disk for an ECS even if this API has been called to set the bootable flag f", + "product_code":"evs", + "title":"Setting Bootable Flag for an EVS Disk", + "uri":"evs_04_2084.html", + "doc_type":"api", + "p_code":"69", + "code":"71" + }, + { + "desc":"This API is used to set the read-only flag for the EVS disk.URI formatPOST /v2/{project_id}/volumes/{volume_id}/actionPOST /v2/{project_id}/volumes/{volume_id}/actionPara", + "product_code":"evs", + "title":"Setting Read-Only Flag for an EVS Disk", + "uri":"evs_04_2085.html", + "doc_type":"api", + "p_code":"69", + "code":"72" + }, + { + "desc":"This API is used to export the system disk data or data disk data as an IMS image. The exported image will be displayed in the IMS private image list and can be viewed an", + "product_code":"evs", + "title":"Exporting EVS Disk Data as an Image", + "uri":"evs_04_2086.html", + "doc_type":"api", + "p_code":"69", + "code":"73" + }, + { + "desc":"This API is only used to change the EVS disk status from available to in-use.This API call exists for compatibility reasons only and is not meant to be used.Do not call t", + "product_code":"evs", + "title":"Attaching an EVS Disk (Deprecated)", + "uri":"evs_04_2087.html", + "doc_type":"api", + "p_code":"69", + "code":"74" + }, + { + "desc":"This API is only used to change the EVS disk status from in-use to available.This API call exists for compatibility reasons only and is not meant to be used.Do not call t", + "product_code":"evs", + "title":"Detaching an EVS Disk (Deprecated)", + "uri":"evs_04_2088.html", + "doc_type":"api", + "p_code":"69", + "code":"75" + }, + { + "desc":"This API is used to reserve an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v2/{project_id}/volumes/{volume_id", + "product_code":"evs", + "title":"Reserving an EVS Disk (Deprecated)", + "uri":"evs_04_2089.html", + "doc_type":"api", + "p_code":"69", + "code":"76" + }, + { + "desc":"This API is used to cancel the reservation of an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v2/{project_id}/", + "product_code":"evs", + "title":"Canceling Reservation of an EVS Disk (Deprecated)", + "uri":"evs_04_2090.html", + "doc_type":"api", + "p_code":"69", + "code":"77" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Snapshot", + "uri":"evs_04_2092.html", + "doc_type":"api", + "p_code":"50", + "code":"78" + }, + { + "desc":"This API is used to create an EVS snapshot.URI formatPOST /v2/{project_id}/snapshotsPOST /v2/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionproje", + "product_code":"evs", + "title":"Creating an EVS Snapshot", + "uri":"evs_04_2093.html", + "doc_type":"api", + "p_code":"78", + "code":"79" + }, + { + "desc":"This API is used to delete an EVS snapshot.A snapshot can be deleted only when it is in the available or error state.URI formatDELETE /v2/{project_id}/snapshots/{snapshot", + "product_code":"evs", + "title":"Deleting an EVS Snapshot", + "uri":"evs_04_2094.html", + "doc_type":"api", + "p_code":"78", + "code":"80" + }, + { + "desc":"This API is used to update an EVS snapshot.URI formatPUT /v2/{project_id}/snapshots/{snapshot_id}PUT /v2/{project_id}/snapshots/{snapshot_id}Parameter descriptionParamete", + "product_code":"evs", + "title":"Updating an EVS Snapshot", + "uri":"evs_04_2095.html", + "doc_type":"api", + "p_code":"78", + "code":"81" + }, + { + "desc":"This API is used to query the EVS snapshots.URI formatGET /v2/{project_id}/snapshotsGET /v2/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionprojec", + "product_code":"evs", + "title":"Querying EVS Snapshots", + "uri":"evs_04_2096.html", + "doc_type":"api", + "p_code":"78", + "code":"82" + }, + { + "desc":"This API is used to query details about the EVS snapshots.URI formatGET /v2/{project_id}/snapshots/detailGET /v2/{project_id}/snapshots/detailParameter descriptionParamet", + "product_code":"evs", + "title":"Querying Details About EVS Snapshots", + "uri":"evs_04_2097.html", + "doc_type":"api", + "p_code":"78", + "code":"83" + }, + { + "desc":"This API is used to query details about an EVS snapshot.URI formatGET /v2/{project_id}/snapshots/{snapshot_id}GET /v2/{project_id}/snapshots/{snapshot_id}Parameter descri", + "product_code":"evs", + "title":"Querying Details About an EVS Snapshot", + "uri":"evs_04_2098.html", + "doc_type":"api", + "p_code":"78", + "code":"84" + }, + { + "desc":"This API is used to add the metadata of an EVS snapshot.URI formatPOST /v2/{project_id}/snapshots/{snapshot_id}/metadataPOST /v2/{project_id}/snapshots/{snapshot_id}/meta", + "product_code":"evs", + "title":"Adding Metadata of an EVS Snapshot", + "uri":"evs_04_2099.html", + "doc_type":"api", + "p_code":"78", + "code":"85" + }, + { + "desc":"This API is used to query the metadata of an EVS snapshot.URI formatGET /v2/{project_id}/snapshots/{snapshot_id}/metadataGET /v2/{project_id}/snapshots/{snapshot_id}/meta", + "product_code":"evs", + "title":"Querying Metadata of an EVS Snapshot", + "uri":"evs_04_2100.html", + "doc_type":"api", + "p_code":"78", + "code":"86" + }, + { + "desc":"This API is used to update one piece of the EVS snapshot metadata.URI formatPUT /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}PUT /v2/{project_id}/snapshots/{sna", + "product_code":"evs", + "title":"Updating One Piece of Metadata for an EVS Snapshot", + "uri":"evs_04_2101.html", + "doc_type":"api", + "p_code":"78", + "code":"87" + }, + { + "desc":"This API is used to update the metadata of an EVS snapshot.URI formatPUT /v2/{project_id}/snapshots/{snapshot_id}/metadataPUT /v2/{project_id}/snapshots/{snapshot_id}/met", + "product_code":"evs", + "title":"Updating Metadata of an EVS Snapshot", + "uri":"evs_04_2102.html", + "doc_type":"api", + "p_code":"78", + "code":"88" + }, + { + "desc":"This API is used to query one piece of the EVS snapshot metadata.URI formatGET /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}GET /v2/{project_id}/snapshots/{snap", + "product_code":"evs", + "title":"Querying One Piece of Metadata for an EVS Snapshot", + "uri":"evs_04_2103.html", + "doc_type":"api", + "p_code":"78", + "code":"89" + }, + { + "desc":"This API is used to delete one piece of the EVS snapshot metadata.URI formatDELETE /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}DELETE /v2/{project_id}/snapshot", + "product_code":"evs", + "title":"Deleting One Piece of Metadata for an EVS Snapshot", + "uri":"evs_04_2104.html", + "doc_type":"api", + "p_code":"78", + "code":"90" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk Transfer", + "uri":"evs_04_2105.html", + "doc_type":"api", + "p_code":"50", + "code":"91" + }, + { + "desc":"This API is used to create a disk transfer. After the transfer has been created, a transfer ID and an authentication key are returned.After a disk transfer is created, th", + "product_code":"evs", + "title":"Creating a Disk Transfer", + "uri":"evs_04_2106.html", + "doc_type":"api", + "p_code":"91", + "code":"92" + }, + { + "desc":"This API is used to accept a disk transfer through the transfer ID and authentication key.Encrypted EVS disks cannot be transferred.EVS disks with backups and snapshots a", + "product_code":"evs", + "title":"Accepting a Disk Transfer", + "uri":"evs_04_2107.html", + "doc_type":"api", + "p_code":"91", + "code":"93" + }, + { + "desc":"This API is used to delete a disk transfer. A disk transfer can be deleted if it is not accepted. Accepted disk transfers cannot be deleted.URI formatDELETE /v2/{project_", + "product_code":"evs", + "title":"Deleting a Disk Transfer", + "uri":"evs_04_2108.html", + "doc_type":"api", + "p_code":"91", + "code":"94" + }, + { + "desc":"This API is used to query the details of a disk transfer, including the transfer creation time, transfer ID, and transfer name.URI formatGET /v2/{project_id}/os-volume-tr", + "product_code":"evs", + "title":"Querying Details of a Disk Transfer", + "uri":"evs_04_2109.html", + "doc_type":"api", + "p_code":"91", + "code":"95" + }, + { + "desc":"This API is used to query all disk transfers of the current tenant.URI formatGET /v2/{project_id}/os-volume-transferGET /v2/{project_id}/os-volume-transferParameter descr", + "product_code":"evs", + "title":"Querying All Disk Transfers", + "uri":"evs_04_2110.html", + "doc_type":"api", + "p_code":"91", + "code":"96" + }, + { + "desc":"This API is used to query the details of all disk transfers, including the transfer creation time, transfer IDs, and transfer names.URI formatGET /v2/{project_id}/os-volu", + "product_code":"evs", + "title":"Querying Details of All Disk Transfers", + "uri":"evs_04_2111.html", + "doc_type":"api", + "p_code":"91", + "code":"97" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Unrecommended APIs", + "uri":"evs_04_0063.html", + "doc_type":"api", + "p_code":"", + "code":"98" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"API v3", + "uri":"evs_04_3001.html", + "doc_type":"api", + "p_code":"98", + "code":"99" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk", + "uri":"evs_04_3002.html", + "doc_type":"api", + "p_code":"99", + "code":"100" + }, + { + "desc":"This API is used to create one or multiple EVS disks.URI formatPOST /v3/{project_id}/cloudvolumesPOST /v3/{project_id}/cloudvolumesParameter descriptionParameterMandatory", + "product_code":"evs", + "title":"Creating EVS Disks", + "uri":"evs_04_3003.html", + "doc_type":"api", + "p_code":"100", + "code":"101" + }, + { + "desc":"This API is used to query details about all disks.URI formatGET /v3/{project_id}/os-vendor-volumes/detailGET /v3/{project_id}/os-vendor-volumes/detailParameter descriptio", + "product_code":"evs", + "title":"Querying Details About All EVS Disks (Deprecated)", + "uri":"evs_04_3004.html", + "doc_type":"api", + "p_code":"100", + "code":"102" + }, + { + "desc":"This API is used to query details about a disk.URI formatGET /v3/{project_id}/os-vendor-volumes/{volume_id}GET /v3/{project_id}/os-vendor-volumes/{volume_id}Parameter des", + "product_code":"evs", + "title":"Querying Details About an EVS Disk (Deprecated)", + "uri":"evs_04_3005.html", + "doc_type":"api", + "p_code":"100", + "code":"103" + }, + { + "desc":"This API is used to query the loading progress of a lazyloading disk.URI formatGET /v3/{project_id}/os-vendor-volumes/{volume_id}/internal-infoGET /v3/{project_id}/os-ven", + "product_code":"evs", + "title":"Querying Loading Progress of a Lazyloading Disk", + "uri":"evs_04_3006.html", + "doc_type":"api", + "p_code":"100", + "code":"104" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Snapshot", + "uri":"evs_04_3007.html", + "doc_type":"api", + "p_code":"99", + "code":"105" + }, + { + "desc":"This API is used to roll back a snapshot to an EVS disk.When you roll back a snapshot to a disk, you can only roll back the snapshot to the source disk. Rollback to a spe", + "product_code":"evs", + "title":"Rolling Back a Snapshot to an EVS Disk", + "uri":"evs_04_3008.html", + "doc_type":"api", + "p_code":"105", + "code":"106" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Tag", + "uri":"evs_04_3010.html", + "doc_type":"api", + "p_code":"99", + "code":"107" + }, + { + "desc":"This API is used to batch add tags for the specified EVS disk.When adding tags, if a tag key is consistent with an existing one, the new tag will overwrite the existing t", + "product_code":"evs", + "title":"Batch Adding Tags for the Specified EVS Disk", + "uri":"evs_04_3011.html", + "doc_type":"api", + "p_code":"107", + "code":"108" + }, + { + "desc":"This API is used to batch delete tags for the specified EVS disk.NoneURI formatPOST /v3/{project_id}/os-vendor-volumes/{volume_id}/tags/actionPOST /v3/{project_id}/os-ven", + "product_code":"evs", + "title":"Batch Deleting Tags for the Specified EVS Disk", + "uri":"evs_04_3013.html", + "doc_type":"api", + "p_code":"107", + "code":"109" + }, + { + "desc":"This API is used to query the tags of the specified EVS disk.NoneURI formatGET /v3/{project_id}/os-vendor-volumes/{volume_id}/tagsGET /v3/{project_id}/os-vendor-volumes/{", + "product_code":"evs", + "title":"Querying Tags of an EVS Disk", + "uri":"evs_04_3015.html", + "doc_type":"api", + "p_code":"107", + "code":"110" + }, + { + "desc":"This API is used to query the number of EVS disks by tag.NoneURI formatPOST /v3/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v3/{project_id}/os-vendor-vo", + "product_code":"evs", + "title":"Querying the Number of EVS Disks by Tag", + "uri":"evs_04_3016.html", + "doc_type":"api", + "p_code":"107", + "code":"111" + }, + { + "desc":"This API is used to query the details of EVS disks by tag.NoneURI formatPOST /v3/{project_id}/os-vendor-volumes/resource_instances/actionPOST /v3/{project_id}/os-vendor-v", + "product_code":"evs", + "title":"Querying Details of EVS Disks by Tag", + "uri":"evs_04_3018.html", + "doc_type":"api", + "p_code":"107", + "code":"112" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"OpenStack Cinder API v3", + "uri":"evs_04_3027.html", + "doc_type":"api", + "p_code":"98", + "code":"113" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk", + "uri":"evs_04_3028.html", + "doc_type":"api", + "p_code":"113", + "code":"114" + }, + { + "desc":"This API is used to create one or multiple EVS disks.URI formatPOST /v3/{project_id}/volumesPOST /v3/{project_id}/volumesParameter descriptionParameterMandatoryDescriptio", + "product_code":"evs", + "title":"Creating EVS Disks", + "uri":"evs_04_3029.html", + "doc_type":"api", + "p_code":"114", + "code":"115" + }, + { + "desc":"This API is used to delete an EVS disk.URI formatDELETE /v3/{project_id}/volumes/{volume_id}DELETE /v3/{project_id}/volumes/{volume_id}Parameter descriptionParameterManda", + "product_code":"evs", + "title":"Deleting an EVS Disk", + "uri":"evs_04_3030.html", + "doc_type":"api", + "p_code":"114", + "code":"116" + }, + { + "desc":"This API is used to update the EVS disk information.URI formatPUT /v3/{project_id}/volumes/{volume_id}PUT /v3/{project_id}/volumes/{volume_id}Parameter descriptionParamet", + "product_code":"evs", + "title":"Updating an EVS Disk", + "uri":"evs_04_3031.html", + "doc_type":"api", + "p_code":"114", + "code":"117" + }, + { + "desc":"This API is used to query EVS disks.URI formatGET /v3/{project_id}/volumesGET /v3/{project_id}/volumesParameter descriptionParameterMandatoryDescriptionproject_idYesSpeci", + "product_code":"evs", + "title":"Querying EVS Disks", + "uri":"evs_04_3032.html", + "doc_type":"api", + "p_code":"114", + "code":"118" + }, + { + "desc":"This API is used to query details about all disks.URI formatGET /v3/{project_id}/volumes/detailGET /v3/{project_id}/volumes/detailParameter descriptionParameterMandatoryD", + "product_code":"evs", + "title":"Querying Details About All Disks", + "uri":"evs_04_3033.html", + "doc_type":"api", + "p_code":"114", + "code":"119" + }, + { + "desc":"This API is used to query details about a disk.URI formatGET /v3/{project_id}/volumes/{volume_id}GET /v3/{project_id}/volumes/{volume_id}Parameter descriptionParameterMan", + "product_code":"evs", + "title":"Querying Details About a Disk", + "uri":"evs_04_3034.html", + "doc_type":"api", + "p_code":"114", + "code":"120" + }, + { + "desc":"This API is used to query EVS disk types and display the query results in a list.URI formatGET /v3/{project_id}/typesGET /v3/{project_id}/typesParameter descriptionParame", + "product_code":"evs", + "title":"Querying EVS Disk Types", + "uri":"evs_04_3035.html", + "doc_type":"api", + "p_code":"114", + "code":"121" + }, + { + "desc":"This API is used to query details about an EVS disk type.URI formatGET /v3/{project_id}/types/{type_id}GET /v3/{project_id}/types/{type_id}Parameter descriptionParameterM", + "product_code":"evs", + "title":"Querying Details About an EVS Disk Type", + "uri":"evs_04_3036.html", + "doc_type":"api", + "p_code":"114", + "code":"122" + }, + { + "desc":"This API is used to query the details of tenant quotas.URI formatGET /v3/{project_id}/os-quota-sets/{target_project_id}?usage=TrueGET /v3/{project_id}/os-quota-sets/{targ", + "product_code":"evs", + "title":"Querying Details of Tenant Quotas", + "uri":"evs_04_3037.html", + "doc_type":"api", + "p_code":"114", + "code":"123" + }, + { + "desc":"This API is used to add or update the metadata of an EVS disk.URI formatPOST /v3/{project_id}/volumes/{volume_id}/metadataPOST /v3/{project_id}/volumes/{volume_id}/metada", + "product_code":"evs", + "title":"Adding Metadata of an EVS Disk", + "uri":"evs_04_3038.html", + "doc_type":"api", + "p_code":"114", + "code":"124" + }, + { + "desc":"This API is used to query the metadata of an EVS disk.URI formatGET /v3/{project_id}/volumes/{volume_id}/metadataGET /v3/{project_id}/volumes/{volume_id}/metadataParamete", + "product_code":"evs", + "title":"Querying Metadata of an EVS Disk", + "uri":"evs_04_3039.html", + "doc_type":"api", + "p_code":"114", + "code":"125" + }, + { + "desc":"This API is used to update the metadata of an EVS disk.URI formatPUT /v3/{project_id}/volumes/{volume_id}/metadataPUT /v3/{project_id}/volumes/{volume_id}/metadataParamet", + "product_code":"evs", + "title":"Updating Metadata of an EVS Disk", + "uri":"evs_04_3040.html", + "doc_type":"api", + "p_code":"114", + "code":"126" + }, + { + "desc":"This API is used to query one piece of the EVS disk metadata.URI formatGET /v3/{project_id}/volumes/{volume_id}/metadata/{key}GET /v3/{project_id}/volumes/{volume_id}/met", + "product_code":"evs", + "title":"Querying One Piece of Metadata for an EVS Disk", + "uri":"evs_04_3041.html", + "doc_type":"api", + "p_code":"114", + "code":"127" + }, + { + "desc":"This API is used to update one piece of the EVS disk metadata.URI formatPUT /v3/{project_id}/volumes/{volume_id}/metadata/{key}PUT /v3/{project_id}/volumes/{volume_id}/me", + "product_code":"evs", + "title":"Updating One Piece of Metadata for an EVS Disk", + "uri":"evs_04_3042.html", + "doc_type":"api", + "p_code":"114", + "code":"128" + }, + { + "desc":"This API is used to delete one piece of the EVS disk metadata.URI formatDELETE /v3/{project_id}/volumes/{volume_id}/metadata/{key}DELETE /v3/{project_id}/volumes/{volume_", + "product_code":"evs", + "title":"Deleting One Piece of Metadata for an EVS Disk", + "uri":"evs_04_3043.html", + "doc_type":"api", + "p_code":"114", + "code":"129" + }, + { + "desc":"This API is used to query extension APIs.URI formatGET /v3/{project_id}/extensionsGET /v3/{project_id}/extensionsParameter descriptionParameterMandatoryDescriptionproject", + "product_code":"evs", + "title":"Querying Extension APIs", + "uri":"evs_04_3044.html", + "doc_type":"api", + "p_code":"114", + "code":"130" + }, + { + "desc":"This API is used to query all AZs.URI formatGET /v3/{project_id}/os-availability-zoneGET /v3/{project_id}/os-availability-zoneParameter descriptionParameterMandatoryDescr", + "product_code":"evs", + "title":"Querying All AZs", + "uri":"evs_04_3045.html", + "doc_type":"api", + "p_code":"114", + "code":"131" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk Actions", + "uri":"evs_04_3047.html", + "doc_type":"api", + "p_code":"113", + "code":"132" + }, + { + "desc":"This API is used to expand the capacity of an EVS disk.If the status of the to-be-expanded disk is available, there are no restrictions.If the status of the to-be-expande", + "product_code":"evs", + "title":"Expanding Capacity of an EVS Disk", + "uri":"evs_04_3048.html", + "doc_type":"api", + "p_code":"132", + "code":"133" + }, + { + "desc":"This API is used to set the bootable flag for an EVS disk.A data disk cannot be used as system disk for an ECS even if this API has been called to set the bootable flag f", + "product_code":"evs", + "title":"Setting Bootable Flag for an EVS Disk", + "uri":"evs_04_3049.html", + "doc_type":"api", + "p_code":"132", + "code":"134" + }, + { + "desc":"This API is used to set the read-only flag for the EVS disk.URI formatPOST /v3/{project_id}/volumes/{volume_id}/actionPOST /v3/{project_id}/volumes/{volume_id}/actionPara", + "product_code":"evs", + "title":"Setting Read-Only Flag for an EVS Disk", + "uri":"evs_04_3050.html", + "doc_type":"api", + "p_code":"132", + "code":"135" + }, + { + "desc":"This API is used to export the system disk data or data disk data as an IMS image. The exported image will be displayed in the IMS private image list and can be viewed an", + "product_code":"evs", + "title":"Exporting EVS Disk Data as an Image", + "uri":"evs_04_3051.html", + "doc_type":"api", + "p_code":"132", + "code":"136" + }, + { + "desc":"This API is used to reserve an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v3/{project_id}/volumes/{volume_id", + "product_code":"evs", + "title":"Reserving an EVS Disk (Deprecated)", + "uri":"evs_04_3052.html", + "doc_type":"api", + "p_code":"132", + "code":"137" + }, + { + "desc":"This API is used to cancel the reservation of an EVS disk.This API call exists for compatibility reasons only and is not meant to be used.URI formatPOST /v3/{project_id}/", + "product_code":"evs", + "title":"Canceling Reservation of an EVS Disk (Deprecated)", + "uri":"evs_04_3053.html", + "doc_type":"api", + "p_code":"132", + "code":"138" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Snapshot", + "uri":"evs_04_3055.html", + "doc_type":"api", + "p_code":"113", + "code":"139" + }, + { + "desc":"This API is used to create an EVS snapshot.URI formatPOST /v3/{project_id}/snapshotsPOST /v3/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionproje", + "product_code":"evs", + "title":"Creating an EVS Snapshot", + "uri":"evs_04_3056.html", + "doc_type":"api", + "p_code":"139", + "code":"140" + }, + { + "desc":"This API is used to delete an EVS snapshot.A snapshot can be deleted only when it is in the available or error state.URI formatDELETE /v3/{project_id}/snapshots/{snapshot", + "product_code":"evs", + "title":"Deleting an EVS Snapshot", + "uri":"evs_04_3057.html", + "doc_type":"api", + "p_code":"139", + "code":"141" + }, + { + "desc":"This API is used to update an EVS snapshot.URI formatPUT /v3/{project_id}/snapshots/{snapshot_id}PUT /v3/{project_id}/snapshots/{snapshot_id}Parameter descriptionParamete", + "product_code":"evs", + "title":"Updating an EVS Snapshot", + "uri":"evs_04_3058.html", + "doc_type":"api", + "p_code":"139", + "code":"142" + }, + { + "desc":"This API is used to query the EVS snapshots.URI formatGET /v3/{project_id}/snapshotsGET /v3/{project_id}/snapshotsParameter descriptionParameterMandatoryDescriptionprojec", + "product_code":"evs", + "title":"Querying EVS Snapshots", + "uri":"evs_04_3059.html", + "doc_type":"api", + "p_code":"139", + "code":"143" + }, + { + "desc":"This API is used to query details about the EVS snapshots.URI formatGET /v3/{project_id}/snapshots/detailGET /v3/{project_id}/snapshots/detailParameter descriptionParamet", + "product_code":"evs", + "title":"Querying Details About EVS Snapshots", + "uri":"evs_04_3060.html", + "doc_type":"api", + "p_code":"139", + "code":"144" + }, + { + "desc":"This API is used to query details about an EVS snapshot.URI formatGET /v3/{project_id}/snapshots/{snapshot_id}GET /v3/{project_id}/snapshots/{snapshot_id}Parameter descri", + "product_code":"evs", + "title":"Querying Details About an EVS Snapshot", + "uri":"evs_04_3061.html", + "doc_type":"api", + "p_code":"139", + "code":"145" + }, + { + "desc":"This API is used to add the metadata of an EVS snapshot.URI formatPOST /v3/{project_id}/snapshots/{snapshot_id}/metadataPOST /v3/{project_id}/snapshots/{snapshot_id}/meta", + "product_code":"evs", + "title":"Adding Metadata of an EVS Snapshot", + "uri":"evs_04_3062.html", + "doc_type":"api", + "p_code":"139", + "code":"146" + }, + { + "desc":"This API is used to query the metadata of an EVS snapshot.URI formatGET /v3/{project_id}/snapshots/{snapshot_id}/metadataGET /v3/{project_id}/snapshots/{snapshot_id}/meta", + "product_code":"evs", + "title":"Querying Metadata of an EVS Snapshot", + "uri":"evs_04_3063.html", + "doc_type":"api", + "p_code":"139", + "code":"147" + }, + { + "desc":"This API is used to update one piece of the EVS snapshot metadata.URI formatPUT /v3/{project_id}/snapshots/{snapshot_id}/metadata/{key}PUT /v3/{project_id}/snapshots/{sna", + "product_code":"evs", + "title":"Updating One Piece of Metadata for an EVS Snapshot", + "uri":"evs_04_3064.html", + "doc_type":"api", + "p_code":"139", + "code":"148" + }, + { + "desc":"This API is used to update the metadata of an EVS snapshot.URI formatPUT /v3/{project_id}/snapshots/{snapshot_id}/metadataPUT /v3/{project_id}/snapshots/{snapshot_id}/met", + "product_code":"evs", + "title":"Updating Metadata of an EVS Snapshot", + "uri":"evs_04_3065.html", + "doc_type":"api", + "p_code":"139", + "code":"149" + }, + { + "desc":"This API is used to query one piece of the EVS snapshot metadata.URI formatGET /v3/{project_id}/snapshots/{snapshot_id}/metadata/{key}GET /v3/{project_id}/snapshots/{snap", + "product_code":"evs", + "title":"Querying One Piece of Metadata for an EVS Snapshot", + "uri":"evs_04_3066.html", + "doc_type":"api", + "p_code":"139", + "code":"150" + }, + { + "desc":"This API is used to delete one piece of the EVS snapshot metadata.URI formatDELETE /v3/{project_id}/snapshots/{snapshot_id}/metadata/{key}DELETE /v3/{project_id}/snapshot", + "product_code":"evs", + "title":"Deleting One Piece of Metadata for an EVS Snapshot", + "uri":"evs_04_3067.html", + "doc_type":"api", + "p_code":"139", + "code":"151" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk Transfer", + "uri":"evs_04_3068.html", + "doc_type":"api", + "p_code":"113", + "code":"152" + }, + { + "desc":"This API is used to create a disk transfer. After the transfer has been created, a transfer ID and an authentication key are returned.After a disk transfer is created, th", + "product_code":"evs", + "title":"Creating a Disk Transfer", + "uri":"evs_04_3069.html", + "doc_type":"api", + "p_code":"152", + "code":"153" + }, + { + "desc":"This API is used to accept a disk transfer through the transfer ID and authentication key.Encrypted EVS disks cannot be transferred.EVS disks with backups and snapshots a", + "product_code":"evs", + "title":"Accepting a Disk Transfer", + "uri":"evs_04_3070.html", + "doc_type":"api", + "p_code":"152", + "code":"154" + }, + { + "desc":"This API is used to delete a disk transfer. A disk transfer can be deleted if it is not accepted. Accepted disk transfers cannot be deleted.URI formatDELETE /v3/{project_", + "product_code":"evs", + "title":"Deleting a Disk Transfer", + "uri":"evs_04_3071.html", + "doc_type":"api", + "p_code":"152", + "code":"155" + }, + { + "desc":"This API is used to query the details of a disk transfer, including the transfer creation time, transfer ID, and transfer name.URI formatGET /v3/{project_id}/os-volume-tr", + "product_code":"evs", + "title":"Querying Details of a Disk Transfer", + "uri":"evs_04_3072.html", + "doc_type":"api", + "p_code":"152", + "code":"156" + }, + { + "desc":"This API is used to query all disk transfers of the current tenant.URI formatGET /v3/{project_id}/os-volume-transferGET /v3/{project_id}/os-volume-transferParameter descr", + "product_code":"evs", + "title":"Querying All Disk Transfers", + "uri":"evs_04_3073.html", + "doc_type":"api", + "p_code":"152", + "code":"157" + }, + { + "desc":"This API is used to query the details of all disk transfers, including the transfer creation time, transfer IDs, and transfer names.URI formatGET /v3/{project_id}/os-volu", + "product_code":"evs", + "title":"Querying Details of All Disk Transfers", + "uri":"evs_04_3074.html", + "doc_type":"api", + "p_code":"152", + "code":"158" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"API v1", + "uri":"evs_04_0053.html", + "doc_type":"api", + "p_code":"98", + "code":"159" + }, + { + "desc":"This API is used to query the execution status of tasks, such as the status of disk creation, capacity expansion, and deletion.URI formatGET /v1/{project_id}/jobs/{job_id", + "product_code":"evs", + "title":"Querying Task Status", + "uri":"evs_04_0054.html", + "doc_type":"api", + "p_code":"159", + "code":"160" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"OpenStack Cinder API v1 (Deprecated)", + "uri":"evs_04_0050.html", + "doc_type":"api", + "p_code":"98", + "code":"161" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk", + "uri":"evs_04_0051.html", + "doc_type":"api", + "p_code":"161", + "code":"162" + }, + { + "desc":"This API is used to query details about a disk.This API has been deprecated. Use another API. For details, see Querying Details About a Disk.URI formatGET /v1/{project_id", + "product_code":"evs", + "title":"Querying Details About a Disk (Deprecated)", + "uri":"evs_04_0052.html", + "doc_type":"api", + "p_code":"162", + "code":"163" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Permissions Policies and Supported Actions", + "uri":"evs_04_0022.html", + "doc_type":"api", + "p_code":"", + "code":"164" + }, + { + "desc":"This chapter describes fine-grained permissions management for your EVS resources. If your account does not need individual IAM users, you can skip this chapter.By defaul", + "product_code":"evs", + "title":"Introduction", + "uri":"evs_04_0023.html", + "doc_type":"api", + "p_code":"164", + "code":"165" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"API Version Query", + "uri":"evs_04_0024.html", + "doc_type":"api", + "p_code":"164", + "code":"166" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"Disk", + "uri":"evs_04_0025.html", + "doc_type":"api", + "p_code":"164", + "code":"167" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"Disk Action", + "uri":"evs_04_0026.html", + "doc_type":"api", + "p_code":"164", + "code":"168" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"Snapshot", + "uri":"evs_04_0027.html", + "doc_type":"api", + "p_code":"164", + "code":"169" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"Tag", + "uri":"evs_04_0028.html", + "doc_type":"api", + "p_code":"164", + "code":"170" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"Disk Transfer", + "uri":"evs_04_0029.html", + "doc_type":"api", + "p_code":"164", + "code":"171" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Appendix", + "uri":"evs_04_0037.html", + "doc_type":"api", + "p_code":"", + "code":"172" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Error Codes", + "uri":"evs_04_0038.html", + "doc_type":"api", + "p_code":"172", + "code":"173" + }, + { + "desc":"NormalStatus CodeDescription200OK201Created202Accepted204No ContentAbnormalStatus CodeDescription400Bad Request401Unauthorized403Forbidden404Not Found405Method Not Allowe", + "product_code":"evs", + "title":"Status Codes", + "uri":"evs_04_0039.html", + "doc_type":"api", + "p_code":"172", + "code":"174" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Disk Status", + "uri":"evs_04_0040.html", + "doc_type":"api", + "p_code":"172", + "code":"175" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Snapshot Status", + "uri":"evs_04_0041.html", + "doc_type":"api", + "p_code":"172", + "code":"176" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"EVS Replication Pair Status (Deprecated)", + "uri":"evs_04_0042.html", + "doc_type":"api", + "p_code":"172", + "code":"177" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Replication Consistency Group Status (Deprecated)", + "uri":"evs_04_0043.html", + "doc_type":"api", + "p_code":"172", + "code":"178" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Details of EVS Replication failure_detail Values (Deprecated)", + "uri":"evs_04_0044.html", + "doc_type":"api", + "p_code":"172", + "code":"179" + }, + { + "desc":"This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information ", + "product_code":"evs", + "title":"API Actions", + "uri":"evs_04_0045.html", + "doc_type":"api", + "p_code":"172", + "code":"180" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Change History", + "uri":"evs_04_0048.html", + "doc_type":"api", + "p_code":"", + "code":"181" + } +] \ No newline at end of file diff --git a/docs/evs/api-ref/PARAMETERS.txt b/docs/evs/api-ref/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/evs/api-ref/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/evs/api-ref/evs_04_0001.html b/docs/evs/api-ref/evs_04_0001.html new file mode 100644 index 000000000..60c325e35 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0001.html @@ -0,0 +1,8 @@ + + +

API Usage Guidelines

+

Public cloud Application Programming Interfaces (APIs) comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Uniform Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL, uri indicates the resource path, that is, the API access path.

+

Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.

+

For details about how to use APIs, see API Usage Guidelines.

+
+ diff --git a/docs/evs/api-ref/evs_04_0018.html b/docs/evs/api-ref/evs_04_0018.html new file mode 100644 index 000000000..09622e16c --- /dev/null +++ b/docs/evs/api-ref/evs_04_0018.html @@ -0,0 +1,9 @@ + + +

API Version Description and Usage Instructions

+

EVS APIs provide multiple versions. For the APIs offering same functions, you are recommended to use the v2 APIs.

+

The current default microversion of v3 APIs is 3.0, and the maximum version is 3.50. You can specify the version number by adding OpenStack-API-Version:volume Version number to the request header. For example, add OpenStack-API-Version:volume 3.50.

+

v3 APIs are not recommended, especially non-OpenStack v3 APIs, which will be changed in the future. Therefore, v2 APIs are strongly recommended.

+
+
+ diff --git a/docs/evs/api-ref/evs_04_0019.html b/docs/evs/api-ref/evs_04_0019.html new file mode 100644 index 000000000..c7467a421 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0019.html @@ -0,0 +1,14 @@ + + +

API Version Query

+

+
+
+ +
+ diff --git a/docs/evs/api-ref/evs_04_0020.html b/docs/evs/api-ref/evs_04_0020.html new file mode 100644 index 000000000..b2ddef1e9 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0020.html @@ -0,0 +1,256 @@ + + +

Querying Information of API Versions

+

Function

This API is used to query information of API versions.

+
+

URI

+
+

Request

+
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: API Version Query
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0021.html b/docs/evs/api-ref/evs_04_0021.html new file mode 100644 index 000000000..3a8f1ccbe --- /dev/null +++ b/docs/evs/api-ref/evs_04_0021.html @@ -0,0 +1,217 @@ + + +

Querying Information of an API Version

+

Function

This API is used to query information of an API version.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: API Version Query
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0022.html b/docs/evs/api-ref/evs_04_0022.html new file mode 100644 index 000000000..33a7482e4 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0022.html @@ -0,0 +1,24 @@ + + +

Permissions Policies and Supported Actions

+

+
+
+ +
+ diff --git a/docs/evs/api-ref/evs_04_0023.html b/docs/evs/api-ref/evs_04_0023.html new file mode 100644 index 000000000..6dc50b4e0 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0023.html @@ -0,0 +1,21 @@ + + +

Introduction

+

This chapter describes fine-grained permissions management for your EVS resources. If your account does not need individual IAM users, you can skip this chapter.

+

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

+

You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

+

Policy-based authorization is useful if you want to allow or deny the access to an API.

+
+

An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries EVS disks using an API, the user must have been granted permissions that allow the evs:volumes:list action.

+

Supported Actions

EVS provides system-defined policies that can be directly used in IAM. You can also create custom policies and use them to supplement system-defined policies, implementing more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

+ +

EVS supports the following actions that can be defined in custom policies:

+ +
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0024.html b/docs/evs/api-ref/evs_04_0024.html new file mode 100644 index 000000000..8b58bd1ec --- /dev/null +++ b/docs/evs/api-ref/evs_04_0024.html @@ -0,0 +1,48 @@ + + +

API Version Query

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+ +
+ + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Query API versions (OpenStack Cinder API).

+

GET /

+

None

+

√

+

Query the API version (OpenStack Cinder API).

+

GET /{api_version}

+

None

+

√

+
+
+

If Action is None, no authorization is required.

+
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0025.html b/docs/evs/api-ref/evs_04_0025.html new file mode 100644 index 000000000..7862f1660 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0025.html @@ -0,0 +1,298 @@ + + +

Disk

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Create EVS disks.

+

POST /v2/{project_id}/cloudvolumes

+

evs:volumes:create

+

√

+

Create EVS disks (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes

+
  • Create empty EVS disks.

    evs:volumes:create

    +

    evs:volumes:get

    +
  • Create EVS disks from images.

    evs:volumes:create

    +

    ims:images:get

    +

    evs:volumes:get

    +
  • Create EVS disks from snapshots.

    evs:volumes:create

    +

    evs:snapshots:get

    +

    evs:volumes:get

    +
+

√

+

Expand the capacity of an EVS disk.

+

POST /v2/{project_id}/cloudvolumes/{volume_id}/action

+

evs:volumes:extend

+

√

+

Query EVS disks.

+

GET /v2/{project_id}/cloudvolumes

+

evs:volumes:list

+

√

+

Query EVS disks (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes

+

evs:volumes:list

+

√

+

Query details of all EVS disks.

+

GET /v2/{project_id}/cloudvolumes/detail

+

evs:volumes:list

+

√

+

Querying Details About All Disks

+

GET /v2/{project_id}/os-vendor-volumes/detail

+

evs:volumes:list

+

√

+

Query details of all EVS disks (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/detail

+

evs:volumes:list

+

√

+

Query details of an EVS disk.

+

GET /v2/{project_id}/os-vendor-volumes/{volume_id}

+

+

evs:volumes:get

+

√

+

Query details of an EVS disk (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/{volume_id}

+

evs:volumes:get

+

√

+

Query details of an EVS disk.

+

GET /v2/{project_id}/cloudvolumes/{volume_id}

+

evs:volumes:get

+

√

+

Delete an EVS disk.

+

DELETE /v2/{project_id}/cloudvolumes/{volume_id}

+

evs:volumes:delete

+

√

+

Delete an EVS disk (OpenStack Cinder API).

+

DELETE /v2/{project_id}/volumes/{volume_id}

+

evs:volumes:delete

+

evs:volumes:get

+

√

+

Update EVS disk information.

+

PUT /v2/{project_id}/cloudvolumes/{volume_id}

+

evs:volumes:update

+

√

+

Update EVS disk information (OpenStack Cinder API).

+

PUT /v2/{project_id}/volumes/{volume_id}

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Update one piece of EVS disk metadata (OpenStack Cinder API).

+

PUT /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Update the metadata of an EVS disk (OpenStack Cinder API).

+

PUT /v2/{project_id}/volumes/{volume_id}/metadata

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Query one piece of EVS disk metadata (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:get

+

√

+

Delete one piece of EVS disk metadata (OpenStack Cinder API).

+

DELETE /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:delete

+

evs:volumes:get

+

√

+

Query the metadata of an EVS disk (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:get

+

√

+

Add the metadata of an EVS disk (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes/{volume_id}/metadata

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Query EVS disk types (OpenStack Cinder API).

+

GET /v2/{project_id}/types

+

evs:types:get

+

√

+

Query details of an EVS disk type (OpenStack Cinder API).

+

GET /v2/{project_id}/types/{type_id}

+

evs:types:get

+

√

+

Query tenant quotas (OpenStack Cinder API).

+

GET /v2/{project_id}/os-quota-sets/{project_id}

+

evs:quotas:get

+

√

+

Query extension APIs (OpenStack Cinder API).

+

GET /v2/{project_id}/extensions

+

None

+

√

+

Query information of all AZs (OpenStack Cinder API).

+

GET /v2/{project_id}/os-availability-zone

+

None

+

√

+

Query loading progress of a lazyloading disk.

+

GET /v3/{project_id}/os-vendor-volumes/{volume_id}/internal-info

+

evs:volumes:get

+

√

+

Query EVS disks (OpenStack Cinder API).

+

GET /v3/{project_id}/volumes/summary

+

evs:volumes:get

+

evs:volumes:list

+

√

+
+
+

If Action is None, no authorization is required.

+
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0026.html b/docs/evs/api-ref/evs_04_0026.html new file mode 100644 index 000000000..d46097e33 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0026.html @@ -0,0 +1,117 @@ + + +

Disk Action

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Expand the capacity of an EVS disk (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-extend"

+

evs:volumes:extend

+

evs:volumes:get

+

√

+

Export the EVS disk data as an image (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-volume_upload_image"

+

evs:volumes:uploadImage

+

√

+

Attach an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-attach"

+

evs:volumes:attach

+

evs:volumes:get

+

√

+

Detach an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-detach"

+

evs:volumes:detach

+

evs:volumes:get

+

√

+

Reserve an EVS disk (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-reserve"

+

evs:volumes:attach

+

√

+

Cancel reservation of an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-unreserve"

+

evs:volumes:attach

+

√

+

Set the bootable flag for an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-set_bootable"

+

evs:volumes:update

+

√

+

Set the read-only attribute for an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-update_readonly_flag"

+

evs:volumes:update

+

√

+
+
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0027.html b/docs/evs/api-ref/evs_04_0027.html new file mode 100644 index 000000000..4ab27ff1a --- /dev/null +++ b/docs/evs/api-ref/evs_04_0027.html @@ -0,0 +1,213 @@ + + +

Snapshot

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Create an EVS snapshot (OpenStack Cinder API).

+

POST /v2/{project_id}/snapshots

+

evs:snapshots:create

+

evs:volumes:get

+

√

+

Create an EVS snapshot.

+

POST /v2/{project_id}/cloudsnapshots

+

evs:snapshots:create

+

√

+

Query EVS snapshots (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots

+

evs:snapshots:list

+

√

+

Query details of EVS snapshots (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots/detail

+

evs:snapshots:list

+

√

+

Query details about EVS snapshots.

+

GET /v2/{project_id}/cloudsnapshots/detail

+

evs:snapshots:list

+

√

+

Update an EVS snapshot (OpenStack Cinder API).

+

PUT /v2/{project_id}/snapshots/{snapshot_id}

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Update an EVS snapshot.

+

PUT /v2/{project_id}/cloudsnapshots/{snapshot_id}

+

evs:snapshots:update

+

√

+

Query details about a single EVS snapshot (OpenStack Cinder API).

+

+

GET /v2/{project_id}/snapshots/{snapshot_id}

+

evs:snapshots:get

+

+

√

+

Querying details about an EVS snapshot.

+

+

GET /v2/{project_id}/cloudsnapshots/{snapshot_id}

+

evs:snapshots:get

+

+

√

+

Delete an EVS snapshot (OpenStack Cinder API).

+

DELETE /v2/{project_id}/snapshots/{snapshot_id}

+

evs:snapshots:delete

+

evs:snapshots:get

+

evs:volumes:get

+

√

+

Deleting an EVS snapshot.

+

DELETE /v2/{project_id}/cloudsnapshots/{snapshot_id}

+

evs:snapshots:delete

+

√

+

Roll back a snapshot to an EVS disk.

+

POST /v2/{project_id}/cloudsnapshots/{snapshot_id}/rollback

+

evs:snapshots:rollback

+

√

+

Roll back a snapshot to an EVS disk.

+

POST /v2/{project_id}/os-vendor-snapshots/{snapshot_id}/rollback

+

evs:snapshots:rollback

+

evs:snapshots:get

+

evs:volumes:get

+

√

+

Add the metadata of an EVS snapshot (OpenStack Cinder API).

+

POST /v2/{project_id}/snapshots/{snapshot_id}/metadata

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Query the metadata of an EVS snapshot (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots/{snapshot_id}/metadata

+

evs:snapshots:get

+

√

+

Update one piece of EVS snapshot metadata (OpenStack Cinder API).

+

PUT /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Update the metadata of an EVS snapshot (OpenStack Cinder API).

+

PUT /v2/{project_id}/snapshots/{snapshot_id}/metadata

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Query one piece of EVS snapshot metadata (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}

+

evs:snapshots:get

+

√

+

Delete one piece of EVS snapshot metadata (OpenStack Cinder API).

+

DELETE /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}

+

evs:snapshots:delete

+

evs:snapshots:get

+

√

+
+
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0028.html b/docs/evs/api-ref/evs_04_0028.html new file mode 100644 index 000000000..a1b2ce171 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0028.html @@ -0,0 +1,220 @@ + + +

Tag

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Obtain all EVS tags of a tenant.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}

+
  • EVS disk: evs:volumeTags:list
  • Backup: evs:backupTags:list
  • Snapshot: evs:snapshotTags:list
+

√

+

Query EVS resources by tag.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}/resource_instances

+
  • EVS disk: evs:volumeTags:get
  • Backup: evs:backupTags:get
  • Snapshot: evs:snapshotTags:get
+

√

+

Add or update tags for an EVS resource.

+

POST /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}

+
  • EVS disk: evs:volumeTags:create
  • Backup: evs:backupTags:create
  • Snapshot: evs:snapshotTags:create
+

√

+

Obtain tags of an EVS resource.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}

+
  • EVS disk: evs:volumeTags:getById
  • Backup: evs:backupTags:getById
  • Snapshot: evs:snapshotTags:getById
+

√

+

Reset the tags of an EVS resource.

+

PUT /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}

+
  • EVS disk: evs:volumeTags:update
  • Backup: evs:backupTags:update
  • Snapshot: evs:snapshotTags:update
+

√

+

Batch delete the tags for an EVS resource.

+

POST /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/action

+
  • EVS disk: evs:volumeTags:delete

    evs:volumeTags:getById

    +
  • Backup: evs:backupTags:delete

    evs:backupTags:getById

    +
  • Snapshot: evs:snapshotTags:delete

    evs:snapshotTags:getById

    +
+

√

+

Delete the tags of an EVS resource by key.

+

DELETE /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

+
  • EVS disk: evs:volumeTags:getById

    evs:volumeTags:delete

    +
  • Backup: evs:backupTags:getById

    evs:backupTags:delete

    +
  • Snapshot: evs:snapshotTags:getById

    evs:snapshotTags:delete

    +
+

√

+

Update the tags of an EVS resource by key.

+

PUT /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

+
  • EVS disk: evs:volumeTags:update
  • Backup: evs:backupTags:update
  • Snapshot: evs:snapshotTags:update
+

√

+

Batch delete tags for a specified EVS disk.

+

POST /v2/{project_id}/os-vendor-volumes/{volume_id}/tags/action

+

evs:volumeTags:delete

+

√

+

Query the tags of an EVS disk.

+

GET /v2/{project_id}/os-vendor-volumes/{volume_id}/tags

+

evs:volumeTags:getById

+

√

+

Batch add tags for a specified EVS disk.

+

POST /v2/{project_id}/os-vendor-volumes/{volume_id}/tags/action

+

evs:volumeTags:create

+

√

+

Query details of EVS disks by tag.

+

POST /v2/{project_id}/os-vendor-volumes/resource_instances/action

+

evs:volumeTags:get

+

√

+

Query tags of an EVS resource by key.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

+

evs:volumeTags:getById

+

√

+

Query the number of EVS disks by tag.

+

POST /v2/{project_id}/os-vendor-volumes/resource_instances/action

+

evs:volumeTags:get

+

√

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Obtain all EVS tags of a tenant.

+

GET /v2/{project_id}/cloudvolumes/tags

+
  • EVS disk: evs:volumeTags:list
  • Backup: evs:backupTags:list
+

√

+

Batch add tags for a specified EVS disk.

+

POST /v2/{project_id}/cloudvolumes/{volume_id}/tags/action

+

evs:volumeTags:create

+

√

+

Batch delete tags for a specified EVS disk.

+

POST /v2/{project_id}/cloudvolumes/{volume_id}/tags/action

+

evs:volumeTags:delete

+

√

+

Query the tags of an EVS disk.

+

GET /v2/{project_id}/cloudvolumes/{volume_id}/tags

+

evs:volumeTags:getById

+

√

+

Query details of EVS disks by tag.

+

POST /v2/{project_id}/cloudvolumes/resource_instances/action

+

evs:volumeTags:get

+

√

+
+
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0029.html b/docs/evs/api-ref/evs_04_0029.html new file mode 100644 index 000000000..0f786cf4b --- /dev/null +++ b/docs/evs/api-ref/evs_04_0029.html @@ -0,0 +1,82 @@ + + +

Disk Transfer

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Create an EVS disk transfer (OpenStack Cinder API).

+

POST /v2/{project_id}/os-volume-transfer

+

evs:transfers:create

+

√

+

Query all EVS disk transfers of a tenant (OpenStack Cinder API).

+

GET /v2/{project_id}/os-volume-transfer

+

evs:transfers:list

+

√

+

Query details of all EVS disk transfers of a tenant (OpenStack Cinder API).

+

GET /v2/{project_id}/os-volume-transfer/detail

+

evs:transfers:list

+

√

+

Query details of an EVS disk transfer (OpenStack Cinder API).

+

GET /v2/{project_id}/os-volume-transfer/{transfer_id}

+

evs:transfers:get

+

√

+

Accept an EVS disk transfer (OpenStack Cinder API).

+

POST /v2/{project_id}/os-volume-transfer/{transfer_id}/accept

+

evs:transfers:accept

+

√

+

Delete an EVS disk transfer (OpenStack Cinder API).

+

DELETE /v2/{project_id}/os-volume-transfer/{transfer_id}

+

evs:transfers:delete

+

√

+
+
+
+
+
+
Parent topic: Permissions Policies and Supported Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0037.html b/docs/evs/api-ref/evs_04_0037.html new file mode 100644 index 000000000..260bc9e75 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0037.html @@ -0,0 +1,26 @@ + + +

Appendix

+

+
+
+ +
+ diff --git a/docs/evs/api-ref/evs_04_0038.html b/docs/evs/api-ref/evs_04_0038.html new file mode 100644 index 000000000..35132517f --- /dev/null +++ b/docs/evs/api-ref/evs_04_0038.html @@ -0,0 +1,1518 @@ + + +

Error Codes

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Status Code

+

Error Code

+

Error Message

+

Error Description

+

Solution

+

400

+

EVS.0001

+

invalid tenant id!

+

Incorrect tenant ID in the URI.

+

The tenant ID is actually the project ID.

+

Use the correct tenant ID.

+

400

+

EVS.0002

+

invalid token!

+

Header parameters in the HTTP request are incorrect.

+

Use the correct token.

+

403

+

EVS.0003

+

invalid token roles!

+

The token used is incorrect.

+

The account permission set is empty. Add the required permissions to this account.

+

400

+

EVS.1001

+

null volume!

+

The name and description formats set in the request to update the disk are incorrect.

+

Enter the disk name and description in the correct format.

+

400

+

EVS.1002

+

invalid volume id!

+

Incorrect disk ID.

+

Enter the disk ID in the correct format.

+

400

+

EVS.1003

+

invalid volume name!

+

Incorrect disk name format.

+

Enter the disk name in the correct format.

+

400

+

EVS.1004

+

invalid volume description!

+

Incorrect disk description format.

+

Enter the disk description in the correct format.

+

400

+

EVS.1005

+

size of metadata is too large!

+

The size of the metadata set in the request to create the disk exceeds the upper limit.

+

Check whether the metadata is too large. The metadata size must be smaller than 1048576 bytes.

+

400

+

EVS.1006

+

invalid backup id!

+

The ID of the backup used to create the disk is incorrect.

+

Enter the correct backup ID.

+

400

+

EVS.1007

+

volume name and description can not both be empty!

+

Parameters name and description are incorrect.

+

Enter the correct disk name and description.

+

400

+

EVS.1008

+

null createVolumeReq!

+

The format of the request to create the disk is incorrect.

+

Use the correct request format.

+

400

+

EVS.1009

+

invalid volumeForCreate!

+

The body of the request to create the disk is incorrect.

+

Check the body of the request used to create the disk.

+

400

+

EVS.1010

+

invalid volume size!

+

Parameter size set in the request to create the disk is invalid.

+

Enter a valid size value.

+

400

+

EVS.1011

+

null extendVolumeReq!

+

The format of the request to expand the disk capacity is incorrect.

+

Use the correct request format.

+

400

+

EVS.1012

+

temporary volume!

+

You do not have the permission to access this disk.

+

Do not perform operations for a temporary disk as it does not allow any operation.

+

400

+

EVS.1013

+

request transforming failed!

+

Request conversion error.

+

Check whether the request body is correct.

+

400

+

EVS.1014

+

volume can not be extended!

+

Failed to meet the capacity expansion requirements.

+

Ensure that the disk meets the expansion requirements.

+

400

+

EVS.1015

+

new volume Size must be greater than old Size!

+

The new size of the disk is incorrect.

+

Ensure that the new disk capacity is larger than the original disk capacity.

+

400

+

EVS.1016

+

Invalid input received: May specify only one of imageRef, snapshot_id, backup_id!

+

Only one data source among image, snapshot, and backup can be selected when creating a disk from a data source.

+

Select one data source.

+

400

+

EVS.1018

+

Type conversion error , parameter type is unexpected

+

Type conversion error. The parameter type is unexpected.

+

Check whether the input parameters are correct. See the parameter description in the Elastic Volume Service API Reference.

+

400

+

EVS.1020

+

invalid volume type!

+

The disk type set in the request to create the disk is incorrect.

+

Enter a valid disk type.

+

400

+

EVS.1021

+

the quantity of volume is invalid!

+

The disk quantity set in the request to batch create disks is incorrect.

+

Enter a valid disk quantity.

+

400

+

EVS.1022

+

the size param is less than backup size!

+

Parameter size set in the request to create the disk using a backup is incorrect.

+

Ensure that the entered disk size is larger than the backup size.

+

400

+

EVS.1023

+

invalid filter limit!

+

Parameter limit in the URL for querying the disk is incorrect.

+

Ensure that the limit value ranges from 1 to 1000. The default value is 1000.

+

400

+

EVS.1024

+

invalid filter marker!

+

Parameter marker in the URL for querying the disk is incorrect.

+

Ensure that the marker value is in the UUID format.

+

400

+

EVS.1025

+

url encoding failed!

+

Metadata decoding error.

+

Check whether parameter metadata is correctly specified.

+

403

+

EVS.1027

+

user role is not allowed for this action!

+

You do not have the rights to perform the operation.

+

Check whether the account has relevant permissions, or the account is in arrears, does not pass real-name authentication, or has violations.

+

400

+

EVS.1031

+

invalid resources status!

+

Input value of parameter resources status is invalid.

+

Specify a valid value for resources status.

+

400

+

EVS.1032

+

invalid resources ID!

+

Parameter resources id cannot be left empty.

+

Specify a valid value for resources id.

+

400

+

EVS.1033

+

query quota failed!

+

Failed to query the tenant quota.

+

Check whether the tenant quota is configured.

+

400

+

EVS.1034

+

volume count exceeded volume count quota!

+

Insufficient disk quantity quota assigned to the tenant.

+

Increase the disk quantity quota.

+

400

+

EVS.1036

+

invalid availability zone!

+

Parameter availability_zone set in the request to create the disk is incorrect.

+

Enter the correct AZ.

+

400

+

EVS.1039

+

invalid sort_key!

+

Input parameter sort_key is incorrect.

+

Check whether parameter sort_key is correctly specified.

+

400

+

EVS.1040

+

invalid sort_dir!

+

Parameter sort_dir in the URL for querying the disk is incorrect.

+

Ensure that the sort_dir value is desc or asc.

+

400

+

EVS.1041

+

invalid filter availablity-zone!

+

Parameter availability-zone in the URL for querying the disk is incorrect.

+

Check whether the AZ specified in the request is valid.

+

400

+

EVS.1042

+

volume gigabytes exceeded volume gigabytes quota!

+

Insufficient disk capacity quota assigned to the tenant.

+

Increase the disk capacity quota.

+

400

+

EVS.1043

+

encrypt and cmk and passthrougth in metadata is not support when create volume from snapshot or image!

+

Parameters __system__encrypted, __system__cmkid, and hw:passthrough are not supported when a disk is created from an image or a snapshot.

+

Check whether the request body is correct. For details, see the metadata field description for creating disks.

+

400

+

EVS.1044

+

backup status must be available when create a volume from it!

+

The backup cannot be used to create a disk.

+

The backup is unavailable.

+

400

+

EVS.1045

+

backupDetail returned by FSP is null!

+

Failed to query the backup details.

+

Check whether the backup exists. Contact customer service.

+

400

+

EVS.1046

+

volume status must be available, error, error_extending, error_restoring, error_rollbacking when delete volume!

+

Failed to delete the disk because the disk status is incorrect.

+

Contact customer service.

+

400

+

EVS.1047

+

snapshot status must be available or error when delete snapshot!

+

Failed to delete the snapshot because the snapshot status is incorrect.

+

Contact customer service.

+

400

+

EVS.1048

+

volume status must be available when extend volume!

+

Failed to expand the disk capacity because the disk status is incorrect.

+

Ensure that the disk status meets the expansion requirements.

+

400

+

EVS.1049

+

available-zone is not equal to backup available-zone!

+

The backup used to create the disk is in the incorrect AZ.

+

The backup and the disk to be created must in the same AZ.

+

400

+

EVS.1051

+

can not batch create volume from backup!

+

Batch creating disks from a backup is not available.

+

Batch creating disks from a backup is not available.

+

400

+

EVS.1052

+

invalid http body!

+

Request conversion error.

+

Check whether the request body is correct.

+

400

+

EVS.1053

+

the size of volumes to be deleted is too large!

+

Too many disks are specified in the request for batch deleting disks.

+

Reduce the number of disks specified in the batch.

+

400

+

EVS.1054

+

invalid shareable parameter!

+

Input parameter shareable is invalid.

+

Check whether parameter shareable is correctly specified.

+

400

+

EVS.1057

+

invalid hw:passthrough in metadata!

+

Input parameter hw:passthrough under metadata is invalid.

+

Check whether parameter hw:passthrough is correctly specified.

+

400

+

EVS.1058

+

invalid metadata filter!

+

Metadata decoding error.

+

Check whether parameter metadata is correctly specified.

+

400

+

EVS.1061

+

The Volume Tags is Exceed Max Limit Num.

+

The tag quantity of this EVS disk exceeds the upper limit.

+

Ensure that the tag quantity of the disk is within the upper limit.

+

400

+

EVS.1062

+

invalid tag!

+

Invalid tag.

+

Check the formats of the tag key and tag value and ensure that the formats are correct.

+

400

+

EVS.1063

+

invalid full_clone in metadata!

+

Input parameter full_clone under metadata is invalid.

+

Check whether parameter full_clone in metadata is correctly specified.

+

400

+

EVS.1064

+

volume status must be available or in-use when extending!

+

A disk can be expanded only when its status is available or in-use.

+

Ensure that the disk is in the available or in-use state before expansion.

+

400

+

EVS.1065

+

multiattach volume status must be available when extending!

+

A shared disk can be expanded only when its status is available.

+

Ensure that the shared disk is in the available state before expansion.

+

400

+

EVS.1066

+

status of ECS or BMS does not support volume online extension!

+

The ECS or BMS status does to meet the requirement of online disk expansion.

+

Ensure that the ECS or BMS status meets the requirement.

+

400

+

EVS.1070

+

invalid request.

+

Request conversion error.

+

Check whether the request body is correct.

+

500

+

EVS.2001

+

submit job failed!

+

Failed to submit the task.

+

Contact customer service.

+

500

+

EVS.2002

+

internal error!

+

The system is currently unavailable.

+

Contact customer service.

+

500

+

EVS.2005

+

client exception!

+

A connection exception occurs.

+

Contact customer service.

+

500

+

EVS.2007

+

update volume timeout!

+

Updating the metadata of the disk timed out.

+

Try again later or contact customer service.

+

500

+

EVS.2010

+

exchange token failed!

+

Failed to obtain the token for the tenant.

+

Check the user permissions.

+

500

+

EVS.2011

+

delete orderId and productId timeout!

+

Deleting order information from the disk metadata timed out.

+

Try again later or contact customer service.

+

500

+

EVS.2013

+

assume role error!

+

Failed to elevate the permissions.

+

Contact customer service.

+

500

+

EVS.2014

+

thread is interrupted when sleep!

+

Failed to escalate rights.

+

Try again later or contact customer service.

+

500

+

EVS.2019

+

snapshot is error_deleting!

+

Failed to delete the snapshot because the snapshot is in the error_deleting status.

+

Contact customer service.

+

500

+

EVS.2020

+

volume is error_deleting!

+

Failed to delete the disk because the disk is in the error_deleting status.

+

Contact customer service.

+

500

+

EVS.2021

+

volume is error_detaching!

+

The disk status is error_detaching.

+

Try again later or contact customer service.

+

500

+

EVS.2023

+

ConnectException happened!

+

Network connection timed out.

+

Try again. If the network fails, check the network status.

+

If the network status is normal, contact customer service.

+

500

+

EVS.2024

+

volume is error!

+

The status of the created disk is error.

+

Contact customer service.

+

500

+

EVS.2025

+

volume is error_restoring!

+

The status of the created disk is error_restoring.

+

Contact customer service.

+

500

+

EVS.2026

+

volume is error_extending!

+

Failed to expand the disk capacity because the disk is in the error_extending state.

+

Contact customer service.

+

500

+

EVS.2029

+

The size of joIdList and resultList are mismatched!

+

Incorrect subtask quantity.

+

Contact customer service.

+

500

+

EVS.2030

+

query context based on parent jobId exception!

+

Failed to submit the subtask again.

+

Contact customer service.

+

500

+

EVS.2031

+

result queried from context is null!

+

Failed to query the context.

+

Contact customer service.

+

500

+

EVS.2032

+

some volume count quota usage params are null!

+

Failed to query the disk quantity quota assigned to the tenant.

+

Try again later or contact customer service.

+

500

+

EVS.2033

+

some volume gigabytes quota usage params are null!

+

Failed to query the disk capacity quota assigned to the tenant.

+

Try again later or contact customer service.

+

500

+

EVS.2034

+

domainId decoded from token is null or empty!

+

Token resolution failure.

+

Check whether the account information is correct.

+

500

+

EVS.2035

+

domainName decoded from token is null or empty!

+

Token resolution failure.

+

Check whether the account information is correct.

+

500

+

EVS.2036

+

the result of decode token is null!

+

Empty token.

+

Check whether the account information is correct.

+

400

+

EVS.2040

+

The status of encrypt Key is not enable!

+

Incorrect key status.

+

Ensure that the key status is correct.

+

400

+

EVS.2041

+

The encrypt Param is invalid!

+

The input encryption parameter is invalid.

+

Check whether the encryption parameter in the request body is correct.

+

500

+

EVS.2042

+

Failed to create cmk.

+

Failed to create the CMK.

+

Try again later or contact customer service.

+

400

+

EVS.2043

+

The status of snapshot is not available or backing-up.

+

The snapshot status is in correct.

+

Ensure that the snapshot status is available or backing-up.

+

404

+

EVS.2044

+

Failed to check the role of kms.

+

Failed to check KMS.

+

Try again later or contact customer service.

+

400

+

EVS.2045

+

invalid snapshot_id!

+

Input parameter snapshot_id is invalid.

+

Ensure that the input snapshot_id value is correct.

+

400

+

EVS.2046

+

invalid imageRef!

+

Input parameter imageRef is invalid.

+

Ensure that the input imageRef value is correct.

+

400

+

EVS.2047

+

the metadata Param is not allowed to be updated!

+

The metadata field cannot be modified.

+

Ensure that the input metadata value is correct.

+

500

+

EVS.2050

+

set volume Qos failed!

+

Failed to set the disk QoS.

+

Ensure that the input qos value is correct.

+

400

+

EVS.2052

+

the job result using order id to query is invalid!

+

The job corresponding to the order ID is not unique.

+

Try again later or contact customer service.

+

400

+

EVS.2053

+

The az information from request is invalid!

+

Input parameter availability_zone is invalid.

+

Ensure that the input availability_zone value is correct.

+

400

+

EVS.2054

+

Cannot create volume from snapshot as the az is invalid!

+

When the disk is created from a snapshot, the input availability_zone value of the disk is inconsistent with that of the snapshot.

+

Ensure that the availability_zone value of the disk is consistent with that of the snapshot.

+

400

+

EVS.2055

+

can not create encrypt volume because hasn't xrole.

+

KMS access rights have not been granted to EVS.

+

Before you use the disk encryption function, KMS access rights need to be granted to EVS. Grant the KMS access rights to EVS on the management console. After the rights have been granted, EVS can obtain KMS keys to encrypt or decrypt EVS disks.

+

For details about how to grant the KMS access rights, see EVS Disk Encryption in the Elastic Volume Service User Guide.

+

403

+

EVS.2056

+

action in pdp check deny!

+

Fine-grained PDP authentication failed.

+

Check whether the account has relevant permissions, or the account is in arrears, does not pass real-name authentication, or has violations.

+

400

+

EVS.2068

+

operation failed because of volume be locked

+

Operations cannot be performed on locked resources.

+

Unlock the resource and then perform the operation.

+

400

+

EVS.2070

+

VolumeTypes are not supported !

+

Disk type does not exist.

+

Try again later or contact customer service.

+

400

+

EVS.2071

+

Invalid input received: Availability zone [%s] do not have volume type [%s]

+

This type of disks in the current AZ is sold out.

+

Try again later or contact customer service.

+

400

+

EVS.2072

+

Volume type [SSD] in availability zone [AZ1] is sold out !

+

Disks of the ultra-high I/O type in AZ1 are sold out.

+
NOTE:

The ultra-high I/O disk type and AZ1 are used as the sample disk type and AZ. The disk type and AZ vary depending on the actual condition.

+
+

Select another disk type or contact customer service.

+

400

+

EVS.2078

+

checkQuotaCapacity request body is invalid.

+

Request conversion error.

+

Check whether the request body is empty.

+

400

+

EVS.2083

+

AZ and volume type must not be empty or null!

+

The AZ or disk type parameter in the request is invalid.

+

Ensure that the input AZ and disk type parameters are correct.

+

400

+

EVS.2084

+

resource size must greater than zero!

+

The disk size parameter in the request is invalid.

+

Check whether the disk size specified in the request body is correct.

+

400

+

EVS.2085

+

when operation type is SPEC_CHG, resource id must not be empty or null!

+

The disk ID is invalid during expansion.

+

Check whether the disk ID specified in the request body is correct.

+

400

+

EVS.2087

+

retype failed. please make sure that type is supported and the new one is higher than origin

+

Invalid request parameter.

+

Ensure that the new type has higher specifications than the old type.

+

400

+

EVS.2089

+

operation failed because the volume is belong to SDRS

+

The disk is used by the SDRS service.

+

Free the disk from SDRS or select another disk.

+

400

+

EVS.2093

+

operation failed because the volume is not EVS

+

The disk is not an EVS disk.

+

This operation cannot be performed because the disk is not an EVS disk.

+

400

+

EVS.2094

+

system image is not support to create Multiattach/shareable volume !

+

A shared disk cannot be created from a system disk image.

+

A shared disk cannot be created from a system disk image.

+

400

+

EVS.2096

+

Target volumeType[%s] is not matched with snapshot[%s] !

+

When a disk is created from a snapshot, the disk type of the snapshot's source disk is inconsistent with that of the new disk.

+

Ensure that the disk type of the snapshot's source disk is consistent with that of the new disk.

+

500

+

EVS.2105

+

Volume can not be reverted, because the encrypt volume's __system__cmkid is not exist!

+

The ID of the CMK used to encrypt the disk does not exist, or has been deleted and cannot be restored.

+

Contact customer service.

+

400

+

EVS.2108

+

Request body is invalid.

+

Request conversion error.

+

Check whether the request body is correct.

+

400

+

EVS.2130

+

Volume is backing-up, forbidden deleting!

+

Failed to delete the disk because the snapshot is in the backing-up state when a disk backup is being created.

+

Wait until the backup is created or contact customer service.

+

400

+

EVS.2131

+

Query server info from ecs fail

+

Failed to query the server details.

+

Try again later or contact customer service.

+

400

+

EVS.2134

+

call ecs api - attach volume fail.

+

Failed to attach the disk.

+

Try again later or contact customer service.

+

400

+

EVS.2142

+

invalid filter limit, can not greater than 1000.

+

Request parameter limit cannot be greater than 1000.

+

Ensure that the limit value ranges from 1 to 1000. The default value is 1000.

+

401

+

EVS.2143

+

You need to create an agency for this project for the first time ever

+

The account does not have the encryption permission.

+

Create an agency.

+

403

+

EVS.2144

+

Your account is frozen and resources cannot be used.

+

Insufficient permission because the account is frozen.

+
Check whether either of the following conditions exists: (If no such condition exists, contact customer service.)
  • The account does not pass real-name authentication.
  • The account is in arrears.
+
+

403

+

EVS.2145

+

Your account is suspended and resources cannot be used.

+

Insufficient permission because the account is suspended.

+
Check whether any of the following conditions exists: (If no such condition exists, contact customer service.)
  • The account payment method is not complete.
  • The account does not pass real-name authentication.
  • The account is in arrears.
+
+

400

+

EVS.5400

+

Malformed request body.

+

Incorrect request body parameter and format.

+

Check whether the parameters and format of the request body are correct.

+

400

+

EVS.5400

+

Malformed request url.

+

Incorrect request URL parameter and format.

+

Check whether the parameters and format of the request URL are correct.

+

400

+

EVS.5400

+

Request body and URI mismatch.

+

Request body and URI mismatch.

+

Check whether the request body and URI belong to the same API.

+

400

+

EVS.5400

+

Invalid imageRef provided.

+

The image is unavailable.

+

Select another image.

+

400

+

EVS.5400

+

Must specify a valid status.

+

The disk status is incorrect.

+

Specify a disk that is in the correct state.

+

400

+

EVS.5400

+

offset param must be an integer.

+

The value of parameter offset must be an integer.

+

Set the value of parameter offset to an integer.

+

400

+

EVS.5400

+

limit param must be an integer.

+

The value of parameter limit must be set to an integer.

+

Set the value of parameter limit to an integer.

+

400

+

EVS.5400

+

limit param must be positive.

+

The value of parameter limit must be a positive number.

+

Ensure that the limit value is an integer ranging from 1 to 1000. The default value is 1000.

+

401

+

EVS.5401

+

Authentication required.

+

This operation is unauthorized.

+

Call the API after authorization.

+

403

+

EVS.5403

+

Policy check failed.

+

Insufficient permission.

+

Add the permission and try again.

+

403

+

EVS.5403

+

metadata can not be operated.

+

No operation permission.

+

Modifying parameter metadata is forbidden.

+

404

+

EVS.5404

+

Resource(Volume, Snapshot, Backup .etc) cound not be found.

+

Resources, such as the disk, snapshot, and backup, do not exist.

+

Check whether the resources are available.

+

413

+

EVS.5413

+

Insufficient volume quota.

+

Insufficient disk quotas.

+

Check whether the disk capacity and quantity quotas are sufficient.

+

500

+

EVS.5500

+

Internal server error.

+

Internal server error.

+

Try again later or contact customer service.

+

503

+

EVS.5503

+

Service unavailable.

+

The service is unavailable.

+

Try again later or contact customer service.

+

400

+

Common.0011

+

query job fail.

+

Incorrect tenant ID. The tenant ID is actually the project ID.

+

Use the correct tenant ID and ensure that the tenant has desired permissions. The tenant ID is actually the project ID.

+

400

+

Common.0011

+

No jobs found.

+

jobId is empty.

+

Enter the correct jobId value.

+

400

+

Common.0011

+

query job fail.

+

Failed to query JobVO using jobId.

+

Check whether the jobId value is correct. If the jobId value is correct, check whether the request is delivered to the target EVS service node. If the request has been delivered, contact customer service to locate the fault. If the request has not been delivered, contact customer service to deliver the request to the target EVS service node.

+

400

+

Common.0013

+

Invalid token in the header.

+

Failed to parse the token because the token expires or the token string is incomplete.

+

Obtain the token again and ensure that the token string is complete.

+

400

+

Common.0018

+

Invalid token in the header

+

The project ID in the URI is different from the project ID in the token.

+

Ensure that the project ID in the URI is the same as that in the token and try again.

+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0039.html b/docs/evs/api-ref/evs_04_0039.html new file mode 100644 index 000000000..612db3b37 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0039.html @@ -0,0 +1,131 @@ + + +

Status Codes

+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0040.html b/docs/evs/api-ref/evs_04_0040.html new file mode 100644 index 000000000..5fcfa7c0e --- /dev/null +++ b/docs/evs/api-ref/evs_04_0040.html @@ -0,0 +1,112 @@ + + +

EVS Disk Status

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

EVS Disk Status

+

Description

+

creating

+

The EVS disk is being created.

+

available

+

The EVS disk has not been attached to any server and can be attached.

+

in-use

+

The EVS disk is attached to a server and is in use.

+

error

+

An error occurs when you try to create an EVS disk.

+

attaching

+

The EVS disk is being attached.

+

detaching

+

The EVS disk is being detached.

+

restoring-backup

+

The EVS disk is being restored from a backup.

+

backing-up

+

The EVS disk is being created from a backup.

+

error_restoring

+

An error occurs when you try to restore the EVS disk from a backup.

+

uploading

+

Data on the EVS disk is being uploaded to an image. This status occurs when you create an image from a server.

+

downloading

+

Data is being downloaded from an image to the EVS disk. This status occurs when you create a server.

+

extending

+

The capacity of the EVS disk is being expanded.

+

error_extending

+

An error occurs when you try to expand the capacity of the EVS disk.

+

deleting

+

The EVS disk is being deleted.

+

error_deleting

+

An error occurs when you try to delete the EVS disk.

+

rollbacking

+

Data on the EVS disk is being restored from a snapshot.

+
NOTE:
  • When you roll back a snapshot to an EVS disk, you can only roll back the snapshot to the source EVS disk. Rollback to a specified disk is not possible.
  • You can roll back an EVS disk from a snapshot only when the disk is in the available or error_rollbacking state.
+
+

error_rollbacking

+

An error occurs when the EVS disk is being rolled back from a snapshot.

+

awaiting-transfer

+

The EVS disk is awaiting for a transfer.

+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0041.html b/docs/evs/api-ref/evs_04_0041.html new file mode 100644 index 000000000..0ef3e1d03 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0041.html @@ -0,0 +1,58 @@ + + +

EVS Snapshot Status

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +

EVS Snapshot Status

+

Description

+

creating

+

The EVS snapshot is being created.

+

available

+

The EVS snapshot is successfully created.

+

error

+

An error occurs when you try to create an EVS snapshot.

+

deleting

+

The EVS snapshot is being deleted.

+

error_deleting

+

An error occurs when you try to delete an EVS snapshot.

+

rollbacking

+

The EVS snapshot is rolling back data.

+
NOTE:
  • When you roll back a snapshot to an EVS disk, you can only roll back the snapshot to the source EVS disk. Rollback to a specified disk is not possible.
  • You can roll back an EVS disk from a snapshot only when the disk is in the available or error_rollbacking state.
+
+

backing-up

+

The EVS snapshot is being created from a backup via a native OpenStack API.

+

The system is automatically creating the EVS snapshot when an EVS disk is created from a backup via an API.

+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0042.html b/docs/evs/api-ref/evs_04_0042.html new file mode 100644 index 000000000..d44318ddf --- /dev/null +++ b/docs/evs/api-ref/evs_04_0042.html @@ -0,0 +1,80 @@ + + +

EVS Replication Pair Status (Deprecated)

+
+
+ + + + + + + + + + + + + + + + + + + +

EVS Replication Pair Status

+

Description

+

creating

+

The EVS replication pair is being created.

+

available

+

The EVS replication pair is successfully created and is available for use.

+

error

+

An error occurs when you try to create an EVS replication pair.

+

deleting

+

The EVS replication pair is being deleted.

+

error_deleting

+

An error occurs when you try to delete an EVS replication pair.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + +

EVS Replication Pair Replication Status

+

Description

+

active

+

The replication status of the EVS replication pair is normal, and the data in the production disk is consistent with the data in the DR disk.

+

active-stopped

+

The replication status of the EVS replication pair is paused, and the data in the production disk is consistent with the data in the DR disk.

+

copying

+

The data in the two disks of the EVS replication pair is being synchronized.

+

inactive

+

The replication status of the EVS replication pair is paused, or the data replication is interrupted. Data in the two disks is inconsistent and needs to be synchronized.

+

error

+

The replication status of the EVS replication pair becomes abnormal.

+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0043.html b/docs/evs/api-ref/evs_04_0043.html new file mode 100644 index 000000000..093fe37ff --- /dev/null +++ b/docs/evs/api-ref/evs_04_0043.html @@ -0,0 +1,110 @@ + + +

Replication Consistency Group Status (Deprecated)

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Replication Consistency Group Status

+

Description

+

creating

+

The replication consistency group is being created.

+

available

+

The replication consistency group is successfully created and is available for use.

+

error

+

An error occurs when you try to create a replication consistency group.

+

deleting

+

The replication consistency group is being deleted.

+

updating

+

The replication consistency group is being updated. The update includes adding EVS replication pairs to and deleting EVS replication pairs from the replication consistency group.

+

reversing

+

The replication consistency group is being migrated as planned.

+

error_reversing

+

An error occurs during a planned migration of the replication consistency group.

+

failovering

+

The failover of the replication consistency group is in progress.

+

failovered

+

The replication consistency group failover is successful.

+

error_failovering

+

An error occurs during a failover of the replication consistency group.

+

error_deleting

+

An error occurs during the deletion of the replication consistency group.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + +

Replication Consistency Group Replication Status

+

Description

+

active

+

The replication status of the replication consistency group is normal, and the data in production disks is consistent with the data in DR disks.

+

active-stopped

+

The replication status of the replication consistency group is paused, and the data between production disks and DR disks within the group is inconsistent.

+

copying

+

The data of the replication consistency group is being synchronized.

+

inactive

+

The replication status of the replication consistency group is paused. The data between production disks and DR disks within the group is inconsistent and needs to be synchronized.

+

error

+

The replication status of the replication consistency group becomes abnormal.

+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0044.html b/docs/evs/api-ref/evs_04_0044.html new file mode 100644 index 000000000..21d53a6fa --- /dev/null +++ b/docs/evs/api-ref/evs_04_0044.html @@ -0,0 +1,209 @@ + + +

Details of EVS Replication failure_detail Values (Deprecated)

+

EVS Replication Pair

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Details of the failure_detail values for EVS replication pairs

failure_detail Value

+

Description

+

Cause

+

Solution

+

37100041

+

Failed to create the EVS replication pair because the production disk capacity is inconsistent with the DR disk capacity.

+

The production disk capacity is inconsistent with the DR disk capacity.

+

Ensure that the capacities of the production and DR disks are consistent before you create the EVS replication pair.

+

37100043

+

+

The operation fails because messages failed to be sent to the peer AZ.

+

A communication error occurred.

+

Contact technical support to check whether the link status is normal.

+

37100044

+

Failed to create the EVS replication pair because the specified production disk is a lazyloading EVS disk.

+

Lazyloading EVS disks cannot be used as member disks of EVS replication pairs.

+

Wait until the lazyloading process is complete and try again. If the fault persists, contact technical support.

+

37100045

+

Failed to create the EVS replication pair because the specified DR disk is a lazyloading EVS disk.

+

Lazyloading EVS disks cannot be used as member disks of EVS replication pairs.

+

Wait until the lazyloading process is complete and try again. If the fault persists, contact technical support.

+

37100048

+

Failed to create the EVS replication pair because the specified production disk does not exist.

+

The specified production disk does not exist.

+

Specify an existing production disk.

+

37100050

+

Failed to create the EVS replication pair because the specified DR disk does not exist.

+

The specified DR disk does not exist.

+

Specify an existing DR disk.

+

37100053

+

Failed to create the EVS replication pair because the specified production disk has been used in another EVS replication pair.

+

The specified production disk is the member disk in another EVS replication pair.

+

Specify a production disk that has not been used by another EVS replication pair.

+

37100054

+

Failed to create the EVS replication pair because the specified DR disk has been used in another EVS replication pair.

+

The specified DR disk is the member disk in another EVS replication pair.

+

Specify a DR disk that has not been used by another EVS replication pair.

+

37100058

+

Failed to create the EVS replication pair because the DR disk has been attached to a server and the server is in the Running state.

+

The specified DR disk has been attached to a server and the server is in the Running state.

+

Stop the server , or specify a DR disk that has not been attached to any server.

+

37100177

+

Failed to create the EVS replication pair because the storage pool status of the primary AZ is abnormal.

+

The storage pool status of the primary AZ is abnormal.

+

Create the EVS replication pair when the storage pool status is normal. If the fault persists, contact technical support.

+

37100178

+

Failed to create the EVS replication pair because the storage pool status of the secondary AZ is abnormal.

+

The storage pool status of the secondary AZ is abnormal.

+

Create the EVS replication pair when the storage pool status is normal. If the fault persists, contact technical support.

+

37000212

+

System internal processing failure.

+

An internal system error occurred.

+

Contact technical support.

+

37000216

+

The system is busy. Try again later.

+

The system is busy. Try again later.

+

Try again later. If the fault persists, contact technical support.

+
+
+
+

Replication Consistency Group

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Details of the failure_detail values for replication consistency groups

failure_detail Value

+

Description

+

Cause

+

Solution

+

37100017

+

Failed to create the replication consistency group because the number of replication consistency groups in the primary AZ has reached the upper limit.

+

+

The number of replication consistency groups in the primary AZ has reached the upper limit.

+

+

Contact technical support.

+

37100043

+

+

The operation fails because messages failed to be sent to the peer AZ.

+

The communication between the primary AZ and secondary AZ fails.

+

Contact technical support to check whether the link status is normal.

+

37100159

+

+

Failed to create the replication consistency group because the number of replication consistency groups in the secondary AZ has reached the upper limit.

+

+

The number of replication consistency groups in the secondary AZ has reached the upper limit.

+

+

Contact technical support.

+

37000212

+

System internal processing failure.

+

An internal system error occurred.

+

Contact technical support.

+

37000216

+

The system is busy. Try again later.

+

The system is busy. Try again later.

+

Try again later. If the fault persists, contact technical support.

+
+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0045.html b/docs/evs/api-ref/evs_04_0045.html new file mode 100644 index 000000000..7b951ed6a --- /dev/null +++ b/docs/evs/api-ref/evs_04_0045.html @@ -0,0 +1,915 @@ + + +

API Actions

+

This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.

+

For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.

+

In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.

+

API Version Query

+
+ + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Query API versions (OpenStack Cinder API).

+

GET /

+

None

+

√

+

Query the API version (OpenStack Cinder API).

+

GET /{api_version}

+

None

+

√

+
+
+
+

EVS Disk

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Create EVS disks.

+

POST /v2/{project_id}/cloudvolumes

+

evs:volumes:create

+

√

+

Create EVS disks (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes

+
  • Create empty EVS disks.

    evs:volumes:create

    +

    evs:volumes:get

    +
  • Create EVS disks from images.

    evs:volumes:create

    +

    ims:images:get

    +

    evs:volumes:get

    +
  • Create EVS disks from snapshots.

    evs:volumes:create

    +

    evs:snapshots:get

    +

    evs:volumes:get

    +
+

√

+

Expand the capacity of an EVS disk.

+

POST /v2/{project_id}/cloudvolumes/{volume_id}/action

+

evs:volumes:extend

+

√

+

Query EVS disks.

+

GET /v2/{project_id}/cloudvolumes

+

evs:volumes:list

+

√

+

Query EVS disks (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes

+

evs:volumes:list

+

√

+

Query details of all EVS disks.

+

GET /v2/{project_id}/cloudvolumes/detail

+

evs:volumes:list

+

√

+

Querying Details About All Disks

+

GET /v2/{project_id}/os-vendor-volumes/detail

+

evs:volumes:list

+

√

+

Query details of all EVS disks (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/detail

+

evs:volumes:list

+

√

+

Query details of an EVS disk.

+

GET /v2/{project_id}/os-vendor-volumes/{volume_id}

+

+

evs:volumes:get

+

√

+

Query details of an EVS disk (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/{volume_id}

+

evs:volumes:get

+

√

+

Query details of an EVS disk.

+

GET /v2/{project_id}/cloudvolumes/{volume_id}

+

evs:volumes:get

+

√

+

Delete an EVS disk.

+

DELETE /v2/{project_id}/cloudvolumes/{volume_id}

+

evs:volumes:delete

+

√

+

Delete an EVS disk (OpenStack Cinder API).

+

DELETE /v2/{project_id}/volumes/{volume_id}

+

evs:volumes:delete

+

evs:volumes:get

+

√

+

Update EVS disk information.

+

PUT /v2/{project_id}/cloudvolumes/{volume_id}

+

evs:volumes:update

+

√

+

Update EVS disk information (OpenStack Cinder API).

+

PUT /v2/{project_id}/volumes/{volume_id}

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Update one piece of EVS disk metadata (OpenStack Cinder API).

+

PUT /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Update the metadata of an EVS disk (OpenStack Cinder API).

+

PUT /v2/{project_id}/volumes/{volume_id}/metadata

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Query one piece of EVS disk metadata (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:get

+

√

+

Delete one piece of EVS disk metadata (OpenStack Cinder API).

+

DELETE /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:delete

+

evs:volumes:get

+

√

+

Query the metadata of an EVS disk (OpenStack Cinder API).

+

GET /v2/{project_id}/volumes/{volume_id}/metadata/{key}

+

evs:volumes:get

+

√

+

Add the metadata of an EVS disk (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes/{volume_id}/metadata

+

evs:volumes:update

+

evs:volumes:get

+

√

+

Query EVS disk types (OpenStack Cinder API).

+

GET /v2/{project_id}/types

+

evs:types:get

+

√

+

Query details of an EVS disk type (OpenStack Cinder API).

+

GET /v2/{project_id}/types/{type_id}

+

evs:types:get

+

√

+

Query tenant quotas (OpenStack Cinder API).

+

GET /v2/{project_id}/os-quota-sets/{project_id}

+

evs:quotas:get

+

√

+

Query extension APIs (OpenStack Cinder API).

+

GET /v2/{project_id}/extensions

+

None

+

√

+

Query information of all AZs (OpenStack Cinder API).

+

GET /v2/{project_id}/os-availability-zone

+

None

+

√

+

Query loading progress of a lazyloading disk.

+

GET /v3/{project_id}/os-vendor-volumes/{volume_id}/internal-info

+

evs:volumes:get

+

√

+

Query EVS disks (OpenStack Cinder API).

+

GET /v3/{project_id}/volumes/summary

+

evs:volumes:get

+

evs:volumes:list

+

√

+
+
+
+

EVS Disk Actions

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Expand the capacity of an EVS disk (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-extend"

+

evs:volumes:extend

+

evs:volumes:get

+

√

+

Export the EVS disk data as an image (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-volume_upload_image"

+

evs:volumes:uploadImage

+

√

+

Attach an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-attach"

+

evs:volumes:attach

+

evs:volumes:get

+

√

+

Detach an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-detach"

+

evs:volumes:detach

+

evs:volumes:get

+

√

+

Reserve an EVS disk (OpenStack Cinder API).

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-reserve"

+

evs:volumes:attach

+

√

+

Cancel reservation of an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-unreserve"

+

evs:volumes:attach

+

√

+

Set the bootable flag for an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-set_bootable"

+

evs:volumes:update

+

√

+

Set the read-only attribute for an EVS disk (OpenStack Cinder API).

+

+

POST /v2/{project_id}/volumes/{volume_id}/action

+

action="os-update_readonly_flag"

+

evs:volumes:update

+

√

+
+
+
+

EVS Snapshot

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Create an EVS snapshot (OpenStack Cinder API).

+

POST /v2/{project_id}/snapshots

+

evs:snapshots:create

+

evs:volumes:get

+

√

+

Create an EVS snapshot.

+

POST /v2/{project_id}/cloudsnapshots

+

evs:snapshots:create

+

√

+

Query EVS snapshots (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots

+

evs:snapshots:list

+

√

+

Query details of EVS snapshots (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots/detail

+

evs:snapshots:list

+

√

+

Query details about EVS snapshots.

+

GET /v2/{project_id}/cloudsnapshots/detail

+

evs:snapshots:list

+

√

+

Update an EVS snapshot (OpenStack Cinder API).

+

PUT /v2/{project_id}/snapshots/{snapshot_id}

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Update an EVS snapshot.

+

PUT /v2/{project_id}/cloudsnapshots/{snapshot_id}

+

evs:snapshots:update

+

√

+

Query details about a single EVS snapshot (OpenStack Cinder API).

+

+

GET /v2/{project_id}/snapshots/{snapshot_id}

+

evs:snapshots:get

+

+

√

+

Querying details about an EVS snapshot.

+

+

GET /v2/{project_id}/cloudsnapshots/{snapshot_id}

+

evs:snapshots:get

+

+

√

+

Delete an EVS snapshot (OpenStack Cinder API).

+

DELETE /v2/{project_id}/snapshots/{snapshot_id}

+

evs:snapshots:delete

+

evs:snapshots:get

+

evs:volumes:get

+

√

+

Deleting an EVS snapshot.

+

DELETE /v2/{project_id}/cloudsnapshots/{snapshot_id}

+

evs:snapshots:delete

+

√

+

Roll back a snapshot to an EVS disk.

+

POST /v2/{project_id}/cloudsnapshots/{snapshot_id}/rollback

+

evs:snapshots:rollback

+

√

+

Roll back a snapshot to an EVS disk.

+

POST /v2/{project_id}/os-vendor-snapshots/{snapshot_id}/rollback

+

evs:snapshots:rollback

+

evs:snapshots:get

+

evs:volumes:get

+

√

+

Add the metadata of an EVS snapshot (OpenStack Cinder API).

+

POST /v2/{project_id}/snapshots/{snapshot_id}/metadata

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Query the metadata of an EVS snapshot (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots/{snapshot_id}/metadata

+

evs:snapshots:get

+

√

+

Update one piece of EVS snapshot metadata (OpenStack Cinder API).

+

PUT /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Update the metadata of an EVS snapshot (OpenStack Cinder API).

+

PUT /v2/{project_id}/snapshots/{snapshot_id}/metadata

+

evs:snapshots:update

+

evs:snapshots:get

+

√

+

Query one piece of EVS snapshot metadata (OpenStack Cinder API).

+

GET /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}

+

evs:snapshots:get

+

√

+

Delete one piece of EVS snapshot metadata (OpenStack Cinder API).

+

DELETE /v2/{project_id}/snapshots/{snapshot_id}/metadata/{key}

+

evs:snapshots:delete

+

evs:snapshots:get

+

√

+
+
+
+

EVS Tag

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Obtain all EVS tags of a tenant.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}

+
  • EVS disk: evs:volumeTags:list
  • Backup: evs:backupTags:list
  • Snapshot: evs:snapshotTags:list
+

√

+

Query EVS resources by tag.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}/resource_instances

+
  • EVS disk: evs:volumeTags:get
  • Backup: evs:backupTags:get
  • Snapshot: evs:snapshotTags:get
+

√

+

Add or update tags for an EVS resource.

+

POST /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}

+
  • EVS disk: evs:volumeTags:create
  • Backup: evs:backupTags:create
  • Snapshot: evs:snapshotTags:create
+

√

+

Obtain tags of an EVS resource.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}

+
  • EVS disk: evs:volumeTags:getById
  • Backup: evs:backupTags:getById
  • Snapshot: evs:snapshotTags:getById
+

√

+

Reset the tags of an EVS resource.

+

PUT /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}

+
  • EVS disk: evs:volumeTags:update
  • Backup: evs:backupTags:update
  • Snapshot: evs:snapshotTags:update
+

√

+

Batch delete the tags for an EVS resource.

+

POST /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/action

+
  • EVS disk: evs:volumeTags:delete

    evs:volumeTags:getById

    +
  • Backup: evs:backupTags:delete

    evs:backupTags:getById

    +
  • Snapshot: evs:snapshotTags:delete

    evs:snapshotTags:getById

    +
+

√

+

Delete the tags of an EVS resource by key.

+

DELETE /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

+
  • EVS disk: evs:volumeTags:getById

    evs:volumeTags:delete

    +
  • Backup: evs:backupTags:getById

    evs:backupTags:delete

    +
  • Snapshot: evs:snapshotTags:getById

    evs:snapshotTags:delete

    +
+

√

+

Update the tags of an EVS resource by key.

+

PUT /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

+
  • EVS disk: evs:volumeTags:update
  • Backup: evs:backupTags:update
  • Snapshot: evs:snapshotTags:update
+

√

+

Batch delete tags for a specified EVS disk.

+

POST /v2/{project_id}/os-vendor-volumes/{volume_id}/tags/action

+

evs:volumeTags:delete

+

√

+

Query the tags of an EVS disk.

+

GET /v2/{project_id}/os-vendor-volumes/{volume_id}/tags

+

evs:volumeTags:getById

+

√

+

Batch add tags for a specified EVS disk.

+

POST /v2/{project_id}/os-vendor-volumes/{volume_id}/tags/action

+

evs:volumeTags:create

+

√

+

Query details of EVS disks by tag.

+

POST /v2/{project_id}/os-vendor-volumes/resource_instances/action

+

evs:volumeTags:get

+

√

+

Query tags of an EVS resource by key.

+

GET /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

+

evs:volumeTags:getById

+

√

+

Query the number of EVS disks by tag.

+

POST /v2/{project_id}/os-vendor-volumes/resource_instances/action

+

evs:volumeTags:get

+

√

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Obtain all EVS tags of a tenant.

+

GET /v2/{project_id}/cloudvolumes/tags

+
  • EVS disk: evs:volumeTags:list
  • Backup: evs:backupTags:list
+

√

+

Batch add tags for a specified EVS disk.

+

POST /v2/{project_id}/cloudvolumes/{volume_id}/tags/action

+

evs:volumeTags:create

+

√

+

Batch delete tags for a specified EVS disk.

+

POST /v2/{project_id}/cloudvolumes/{volume_id}/tags/action

+

evs:volumeTags:delete

+

√

+

Query the tags of an EVS disk.

+

GET /v2/{project_id}/cloudvolumes/{volume_id}/tags

+

evs:volumeTags:getById

+

√

+

Query details of EVS disks by tag.

+

POST /v2/{project_id}/cloudvolumes/resource_instances/action

+

evs:volumeTags:get

+

√

+
+
+
+

EVS Disk Transfer

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Permission

+

API

+

Action

+

IAM Project

+

(Project)

+

Create an EVS disk transfer (OpenStack Cinder API).

+

POST /v2/{project_id}/os-volume-transfer

+

evs:transfers:create

+

√

+

Query all EVS disk transfers of a tenant (OpenStack Cinder API).

+

GET /v2/{project_id}/os-volume-transfer

+

evs:transfers:list

+

√

+

Query details of all EVS disk transfers of a tenant (OpenStack Cinder API).

+

GET /v2/{project_id}/os-volume-transfer/detail

+

evs:transfers:list

+

√

+

Query details of an EVS disk transfer (OpenStack Cinder API).

+

GET /v2/{project_id}/os-volume-transfer/{transfer_id}

+

evs:transfers:get

+

√

+

Accept an EVS disk transfer (OpenStack Cinder API).

+

POST /v2/{project_id}/os-volume-transfer/{transfer_id}/accept

+

evs:transfers:accept

+

√

+

Delete an EVS disk transfer (OpenStack Cinder API).

+

DELETE /v2/{project_id}/os-volume-transfer/{transfer_id}

+

evs:transfers:delete

+

√

+
+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0048.html b/docs/evs/api-ref/evs_04_0048.html new file mode 100644 index 000000000..9aa82f392 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0048.html @@ -0,0 +1,241 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Released On

+

Description

+

2022-04-15

+

Added the following content:

+ +

2021-09-12

+

Modified the following content:

+ +

2019-02-15

+

Modified the following content:

+ +

2018-11-30

+

Modified the following content:

+ +

2018-09-30

+

Added the following content:

+
  • Changes relate to the Queens upgrade are listed as follows:
    • Added seven parameters, such as bootable and with_count, in the request filter parameters and added response parameter count in Querying EVS Disks.
    • Added eight parameters, such as glance_metadata and with_count, in the request filter parameters and added response parameter count in Querying Details About All Disks.
    • Added five parameters, such as name~ and with_count, in the request filter parameters and added response parameter count in Querying EVS Snapshots.
    • Added six parameters, such as metadata and with_count, in the request filter parameters and added response parameters user_id and count in Querying Details About EVS Snapshots.
    +
+

2018-05-30

+

Added the following content:

+ +

Modified the following content:

+
  • Modified the constraints of tag keys and tag values.
+

2018-03-30

+

Added the following content:

+
  • Added support for v3 APIs.
  • Added sections Querying EVS Disk Details by Service and Querying Details About a Single EVS Disk.
  • Added sections Querying the Number of EVS Disks by Tag and Querying Details of EVS Disks by Tag.
+
Modified the following content:
  • Modified the constraints of tag keys and tag values.
+
+

2018-03-15

+

Modified the following content:

+ +

2018-02-23

+

Added the following content:

+ +

2018-02-08

+

Modified the following content:

+
  • Modified the reviewed issues in previous version.
+

2018-01-31

+

Added the following content:

+
  • Added section Exporting EVS Disk Data as an Image.
+

Modified the following content:

+
  • Modified the reviewed EVS replication issues.
  • Modified the reviewed EVS disk transfer issues.
+

2018-01-25

+

Added the following content:

+ +

2018-01-19

+

Added the following content:

+
  • Added chapter EVS Disk Transfer.
+

2017-12-01

+

Modified the following content:

+
  • Modified the reviewed EVS replication issues.
+

2017-11-30

+		 +

Modified the following content:

+
  • Modified the reviewed EVS replication issues.
+

2017-10-30

+

Added the following content:

+
  • Added support for EVS replication APIs.
+

2017-10-19

+

Modified the following content:

+
  • Deprecated the APIs in sections Attaching an EVS Disk (Native OpenStack API) and Detaching an EVS Disk (Native OpenStack API).
+

2017-09-30

+

Added the following content:

+
  • Added constraints on the expansion of In-use EVS disks.
+

2017-08-18

+

Modified the following content:

+
  • Changed the format of example requests and responses.
+

2017-07-30

+

Added the following content:

+
  • Added support for TMS APIs.
  • Added support for the co-p1 and uh-l1 EVS disk types.
+

2017-06-30

+

Modified the following content:

+
  • Modified the description about fields availability_zone, name, and volume_type of the API used for creating EVS disks.
+

2017-06-05

+

Added the following content:

+
  • Added the description that the __system__encrypted, __system__cmkid, and hw:passthrough fields are not supported if the EVS disk is created from a snapshot or an image.
  • Added the descriptions for the backup_id, source_volid, snapshot_id, and imageRef fields.
  • Added the description for the volume_type field used when EVS disks are created from snapshots.
+

2017-06-01

+

Added the following content:

+
  • Added the description that if the EVS disk is created from a snapshot or an image, the disk inherits the attributes from the source EVS disk of the snapshot or inherits the attributes from the image.
+

Modified the following content:

+
  • Modified parameter rollback to be mandatory.
+

2017-05-30

+

Added the following content:

+
  • Added support for some native OpenStack APIs.
+

2017-05-20

+

Added the following content:

+
  • Added the description about restrictions of parameter name for the EVS snapshot.
+

2017-05-10

+

Added the following content:

+
  • Added parameter snapshot_id in section Creating an EVS Disk.
+

2017-03-30

+

Added the following content:

+
  • Added chapter EVS Snapshot.
  • Added sections EVS Disk Status and EVS Snapshot Status.
  • Added the shared disk feature and added the parameter description for the multiattach parameter.
  • Added the SCSI feature and added the parameter description for the hw:passthrough parameter.
+

2017-02-22

+

Added the following content:

+
  • Added sections Querying EVS Disk Types (Native OpenStack API) and Querying Details About an EVS Disk Type (Native OpenStack API).
  • Added support for the encryption function and added metadata parameter descriptions in section Creating an EVS Disk.
+

2016-11-24

+

Modified the following content:

+
  • Modified the operation for generating the AK and SK.
+

2016-08-25

+

Modified the following content:

+
  • Modified the parameter description in section Updating EVS Information.
  • Modified the parameter description in section Querying Details About All EVS Disks.
  • Modified the parameter description in section Querying Details About a Single EVS Disk.
  • Modified the parameter description in section Querying Task Information.
+

2016-07-30

+

Modified the following content:

+
  • Modified the parameter description for volume_type in section Creating an EVS Disk.
+

2016-07-15

+

Added the following content:

+
  • Added the parameter description for shared disks in section Creating an EVS Disk.
+

2016-06-16

+

Modified the following content:

+
  • Modified the parameter description in section Updating EVS Information.
  • Modified the parameter description in section Querying Details About All EVS Disks.
  • Modified the parameter description in section Querying Details About a Single EVS Disk.
+

2016-06-02

+

Modified the following content:

+
  • Modified the parameter description in section Creating an EVS Disk.
+

2016-04-14

+

Modified the following content:

+
  • Modified the URL parameter description.
  • Modified the procedure for making API calls for token authentication.
+

2016-03-09

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0050.html b/docs/evs/api-ref/evs_04_0050.html new file mode 100644 index 000000000..11624ce2b --- /dev/null +++ b/docs/evs/api-ref/evs_04_0050.html @@ -0,0 +1,16 @@ + + +

OpenStack Cinder API v1 (Deprecated)

+

+
+
+ + +
+
Parent topic: Unrecommended APIs
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0051.html b/docs/evs/api-ref/evs_04_0051.html new file mode 100644 index 000000000..86f397502 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0051.html @@ -0,0 +1,16 @@ + + +

EVS Disk

+

+
+
+ + +
+
Parent topic: OpenStack Cinder API v1 (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0052.html b/docs/evs/api-ref/evs_04_0052.html new file mode 100644 index 000000000..5d6f37046 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0052.html @@ -0,0 +1,428 @@ + + +

Querying Details About a Disk (Deprecated)

+

Function

This API is used to query details about a disk.

+

This API has been deprecated. Use another API. For details, see Querying Details About a Disk.

+
+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0053.html b/docs/evs/api-ref/evs_04_0053.html new file mode 100644 index 000000000..c228218e4 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0053.html @@ -0,0 +1,16 @@ + + +

API v1

+

+
+
+ + +
+
Parent topic: Unrecommended APIs
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0054.html b/docs/evs/api-ref/evs_04_0054.html new file mode 100644 index 000000000..d880aa245 --- /dev/null +++ b/docs/evs/api-ref/evs_04_0054.html @@ -0,0 +1,376 @@ + + +

Querying Task Status

+

Function

This API is used to query the execution status of tasks, such as the status of disk creation, capacity expansion, and deletion.

+
+

URI

+
+

Request

The following example shows how to query the status of the task whose task ID is ff808081692a62c70169b4dcf9514264.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: API v1
+
+
+ diff --git a/docs/evs/api-ref/evs_04_0063.html b/docs/evs/api-ref/evs_04_0063.html new file mode 100644 index 000000000..041bf346e --- /dev/null +++ b/docs/evs/api-ref/evs_04_0063.html @@ -0,0 +1,18 @@ + + +

Unrecommended APIs

+

+
+
+ +
+ diff --git a/docs/evs/api-ref/evs_04_2001.html b/docs/evs/api-ref/evs_04_2001.html new file mode 100644 index 000000000..4b0c9a690 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2001.html @@ -0,0 +1,19 @@ + + +

API v2 (Recommended)

+
+
+ +
+ diff --git a/docs/evs/api-ref/evs_04_2002.html b/docs/evs/api-ref/evs_04_2002.html new file mode 100644 index 000000000..b6db5b687 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2002.html @@ -0,0 +1,29 @@ + + +

EVS Disk

+
+
+ + +
+
Parent topic: API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2005.html b/docs/evs/api-ref/evs_04_2005.html new file mode 100644 index 000000000..f154903d8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2005.html @@ -0,0 +1,532 @@ + + +

Querying Details About All Disks

+

Function

This API is used to query details about all disks.

+
+

URI

+
+

Request

The following example shows how to query the disks in the available state.
  • Example request
    GET https://{endpoint}/v2/{project_id}/cloudvolumes/detail?status=available
    +
+
+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2008.html b/docs/evs/api-ref/evs_04_2008.html new file mode 100644 index 000000000..03ec47cc8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2008.html @@ -0,0 +1,117 @@ + + +

Deleting an EVS Disk

+

Function

This API is used to delete an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2009.html b/docs/evs/api-ref/evs_04_2009.html new file mode 100644 index 000000000..0ea4356ed --- /dev/null +++ b/docs/evs/api-ref/evs_04_2009.html @@ -0,0 +1,495 @@ + + +

Updating an EVS Disk (Deprecated)

+

Function

This API is used to update the name and description of an EVS disk.

+

This API has been deprecated. Use another API. For details, see Updating an EVS Disk.

+
+
+

URI

+
+

Request

+ + +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2010.html b/docs/evs/api-ref/evs_04_2010.html new file mode 100644 index 000000000..b47fa6cad --- /dev/null +++ b/docs/evs/api-ref/evs_04_2010.html @@ -0,0 +1,672 @@ + + +

Querying Details About All Disks (Deprecated)

+

Function

This API is used to query details about all disks.

+
+

URI

+
+

Request

The following example shows how to query the shared disks in the available state.
  • Example request
    GET https://{endpoint}/v2/{project_id}/os-vendor-volumes/detail?status=available&multiattach=true
    +
+
+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2011.html b/docs/evs/api-ref/evs_04_2011.html new file mode 100644 index 000000000..ce5d40903 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2011.html @@ -0,0 +1,531 @@ + + +

Querying Details About a Disk

+

Function

This API is used to query details about a disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2012.html b/docs/evs/api-ref/evs_04_2012.html new file mode 100644 index 000000000..4e2c547dd --- /dev/null +++ b/docs/evs/api-ref/evs_04_2012.html @@ -0,0 +1,277 @@ + + +

Querying EVS Disks (Deprecated)

+

Function

This API is used to query EVS disks and display the query results in a list.

+

This API has been deprecated. Use another API. For details, see Querying EVS Disks.

+
+
+

URI

+
+

Request

The following example shows how to query the disks in the available state.
  • Example request
    GET https://{endpoint}/v2/{project_id}/cloudvolumes?status=available
    +
+
+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2013.html b/docs/evs/api-ref/evs_04_2013.html new file mode 100644 index 000000000..50f6450e3 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2013.html @@ -0,0 +1,374 @@ + + +

Creating EVS Disks

+

Function

This API is used to create one or multiple EVS disks.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2014.html b/docs/evs/api-ref/evs_04_2014.html new file mode 100644 index 000000000..2fbfffb4b --- /dev/null +++ b/docs/evs/api-ref/evs_04_2014.html @@ -0,0 +1,173 @@ + + +

Expanding Capacity of an EVS Disk (Deprecated)

+

Function

This API is used to expand the capacity of an EVS disk.

+
+ +

This API call exists for compatibility reasons only and is not meant to be used.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2015.html b/docs/evs/api-ref/evs_04_2015.html new file mode 100644 index 000000000..8653016e5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2015.html @@ -0,0 +1,15 @@ + + +

EVS Snapshot

+
+
+ + +
+
Parent topic: API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2022.html b/docs/evs/api-ref/evs_04_2022.html new file mode 100644 index 000000000..45d54f7a2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2022.html @@ -0,0 +1,210 @@ + + +

Rolling Back a Snapshot to an EVS Disk

+

Function

This API is used to roll back a snapshot to an EVS disk.

+
+

Constraints

+
+

URI

+ +
+

Request

+ + +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2024.html b/docs/evs/api-ref/evs_04_2024.html new file mode 100644 index 000000000..f08a9b917 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2024.html @@ -0,0 +1,41 @@ + + +

EVS Tag

+
+
+ + +
+
Parent topic: API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2025.html b/docs/evs/api-ref/evs_04_2025.html new file mode 100644 index 000000000..5d3d18a99 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2025.html @@ -0,0 +1,128 @@ + + +

Deleting Tags of an EVS Resource by Key

+

Function

This API is used to delete tags of an EVS resource by key.

+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2026.html b/docs/evs/api-ref/evs_04_2026.html new file mode 100644 index 000000000..11ea0618e --- /dev/null +++ b/docs/evs/api-ref/evs_04_2026.html @@ -0,0 +1,78 @@ + + +

Obtaining All Tags of an EVS Resource Type

+

Function

This API is used to obtain all tags of an EVS resource type.

+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2027.html b/docs/evs/api-ref/evs_04_2027.html new file mode 100644 index 000000000..e0e322d8d --- /dev/null +++ b/docs/evs/api-ref/evs_04_2027.html @@ -0,0 +1,133 @@ + + +

Batch Adding Tags for the Specified EVS Disk

+

Function

This API is used to batch add tags for the specified EVS disk.

+ +
+

Constraints

None

+
+

URI

+
+

Request

+
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2029.html b/docs/evs/api-ref/evs_04_2029.html new file mode 100644 index 000000000..391fab5ef --- /dev/null +++ b/docs/evs/api-ref/evs_04_2029.html @@ -0,0 +1,130 @@ + + +

Batch Deleting Tags for the Specified EVS Disk

+

Function

This API is used to batch delete tags for the specified EVS disk.

+
+

Constraints

None

+
+

URI

+
+

Request

+
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2031.html b/docs/evs/api-ref/evs_04_2031.html new file mode 100644 index 000000000..121c63705 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2031.html @@ -0,0 +1,109 @@ + + +

Querying Tags of an EVS Disk

+

Function

This API is used to query the tags of the specified EVS disk.

+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2032.html b/docs/evs/api-ref/evs_04_2032.html new file mode 100644 index 000000000..ede6c64af --- /dev/null +++ b/docs/evs/api-ref/evs_04_2032.html @@ -0,0 +1,262 @@ + + +

Querying the Number of EVS Disks by Tag

+

Function

This API is used to query the number of EVS disks by tag.

+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2034.html b/docs/evs/api-ref/evs_04_2034.html new file mode 100644 index 000000000..4b766ad45 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2034.html @@ -0,0 +1,435 @@ + + +

Querying Details of EVS Disks by Tag

+

Function

This API is used to query the details of EVS disks by tag.

+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2036.html b/docs/evs/api-ref/evs_04_2036.html new file mode 100644 index 000000000..4ccc8c368 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2036.html @@ -0,0 +1,160 @@ + + +

Adding or Updating Tags for an EVS Resource (Deprecated)

+

Function

This API is used to add or update tags for an EVS resource.

+

This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.

+
+
+

Constraints

+ +
+

URI

+
+

Request

+ +
+

If the request body contains an existing key of the resource, the original tag containing this key will be overwritten. For example, "key_1":"val_1" is an existing tag of the resource. If the request body contains "key_1":"val_11", the tag of key_1 for this resource is "key_1":"val_11".

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2037.html b/docs/evs/api-ref/evs_04_2037.html new file mode 100644 index 000000000..c85371f46 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2037.html @@ -0,0 +1,114 @@ + + +

Batch Deleting Tags for an EVS Resource (Deprecated)

+

Function

This API is used to batch delete tags for an EVS resource.

+

This API has been deprecated. Use another API. For details, see Batch Deleting Tags for the Specified EVS Disk.

+
+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2038.html b/docs/evs/api-ref/evs_04_2038.html new file mode 100644 index 000000000..1998686c2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2038.html @@ -0,0 +1,101 @@ + + +

Obtaining Tags of a Specified EVS Resource (Deprecated)

+

Function

This API is used to obtain the tags of a specified EVS resource.

+

This API has been deprecated. Use another API. For details, see Querying Tags of an EVS Disk.

+
+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2039.html b/docs/evs/api-ref/evs_04_2039.html new file mode 100644 index 000000000..e7cf91630 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2039.html @@ -0,0 +1,107 @@ + + +

Querying Tags of an EVS Resource by Key (Deprecated)

+

Function

This API is used to query tags of an EVS resource by key.

+

This API has been deprecated. Use another API. For details, see Querying Tags of an EVS Disk.

+
+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2040.html b/docs/evs/api-ref/evs_04_2040.html new file mode 100644 index 000000000..d863a14b9 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2040.html @@ -0,0 +1,156 @@ + + +

Resetting Tags of an EVS Resource (Deprecated)

+

Function

This API is used to reset the tags of an EVS resource, and the existing tags will be deleted.

+

This API call exists for compatibility reasons only and has been deprecated.

+
+
+

Constraints

+ +
+

URI

+
+

Request

+ +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2041.html b/docs/evs/api-ref/evs_04_2041.html new file mode 100644 index 000000000..357769bbd --- /dev/null +++ b/docs/evs/api-ref/evs_04_2041.html @@ -0,0 +1,163 @@ + + +

Updating Tags of an EVS Resource by Key (Deprecated)

+

Function

This API is used to update tags of an EVS resource by key.

+

This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.

+
+
+

Constraints

+ +
+

URI

+
+

Request

+ +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2042.html b/docs/evs/api-ref/evs_04_2042.html new file mode 100644 index 000000000..9ab829dfd --- /dev/null +++ b/docs/evs/api-ref/evs_04_2042.html @@ -0,0 +1,200 @@ + + +

Querying EVS Resources by Tag (Deprecated)

+

Function

This API is used to query the EVS resources by tag.

+

This API has been deprecated. Use another API. For details, see Querying Details of EVS Disks by Tag.

+
+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2043.html b/docs/evs/api-ref/evs_04_2043.html new file mode 100644 index 000000000..1a1d41cf1 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2043.html @@ -0,0 +1,21 @@ + + +

EVS Replication Pair (Deprecated)

+
+
+ + +
+
Parent topic: API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2044.html b/docs/evs/api-ref/evs_04_2044.html new file mode 100644 index 000000000..d29996799 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2044.html @@ -0,0 +1,330 @@ + + +

Creating an EVS Replication Pair (Deprecated)

+

Function

This API is used to create an EVS replication pair using a specified production disk and a disaster recovery (DR) disk. The production disk is in the primary AZ, and the DR disk is in the secondary AZ.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

+
+

URI

+
+

Request

+ + +
+

Response

+
+

Status Codes

+
+
+
+
+
Parent topic: EVS Replication Pair (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2045.html b/docs/evs/api-ref/evs_04_2045.html new file mode 100644 index 000000000..5583a7bb2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2045.html @@ -0,0 +1,146 @@ + + +

Deleting an EVS Replication Pair (Deprecated)

+

Function

This API is used to delete a specified EVS replication pair.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

+
+

URI

+
+

Request

None

+
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: EVS Replication Pair (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2046.html b/docs/evs/api-ref/evs_04_2046.html new file mode 100644 index 000000000..e4819f1fa --- /dev/null +++ b/docs/evs/api-ref/evs_04_2046.html @@ -0,0 +1,458 @@ + + +

Querying All EVS Replication Pairs (Deprecated)

+

Function

This API is used to query all EVS replication pairs of the current tenant.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

None

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+
+
+
+
Parent topic: EVS Replication Pair (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2047.html b/docs/evs/api-ref/evs_04_2047.html new file mode 100644 index 000000000..e149c2ee0 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2047.html @@ -0,0 +1,323 @@ + + +

Querying Details About an EVS Replication Pair (Deprecated)

+

Function

This API is used to query the details about an EVS replication pair, including the name, ID, and status of the replication pair.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+
+

Status Codes

+
+
+
+
+
Parent topic: EVS Replication Pair (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2048.html b/docs/evs/api-ref/evs_04_2048.html new file mode 100644 index 000000000..8b728d54c --- /dev/null +++ b/docs/evs/api-ref/evs_04_2048.html @@ -0,0 +1,35 @@ + + +

Replication Consistency Group (Deprecated)

+
+
+ + +
+
Parent topic: API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2049.html b/docs/evs/api-ref/evs_04_2049.html new file mode 100644 index 000000000..3845f4e0d --- /dev/null +++ b/docs/evs/api-ref/evs_04_2049.html @@ -0,0 +1,315 @@ + + +

Creating a Replication Consistency Group (Deprecated)

+

Function

This API is used to create a replication consistency group for the specified EVS replication pairs.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

+
+

URI

+
+

Request

+ + +
+

Response

+ +
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2050.html b/docs/evs/api-ref/evs_04_2050.html new file mode 100644 index 000000000..31c8bd766 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2050.html @@ -0,0 +1,146 @@ + + +

Deleting a Replication Consistency Group (Deprecated)

+

Function

This API is used to delete a replication consistency group.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

+
+

URI

+
+

Request

None

+
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2051.html b/docs/evs/api-ref/evs_04_2051.html new file mode 100644 index 000000000..89d9670a1 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2051.html @@ -0,0 +1,385 @@ + + +

Querying All Replication Consistency Groups (Deprecated)

+

Function

This API is used to query all replication consistency groups of the current tenant.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

None

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2052.html b/docs/evs/api-ref/evs_04_2052.html new file mode 100644 index 000000000..101113d20 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2052.html @@ -0,0 +1,268 @@ + + +

Querying Details About a Replication Consistency Group (Deprecated)

+

Function

This API is used to query the details about a replication consistency group, including the name, ID, and status of the consistency group.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+ +
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2053.html b/docs/evs/api-ref/evs_04_2053.html new file mode 100644 index 000000000..764cf361c --- /dev/null +++ b/docs/evs/api-ref/evs_04_2053.html @@ -0,0 +1,344 @@ + + +

Updating a Replication Consistency Group (Deprecated)

+

Function

This API is used to update a replication consistency group. An update includes the following operations:

+ +
+

Constraints

+
+

URI

+
+

Request

+ + +
+

Response

+ +
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2054.html b/docs/evs/api-ref/evs_04_2054.html new file mode 100644 index 000000000..dad053e23 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2054.html @@ -0,0 +1,174 @@ + + +

Performing a Failover for a Replication Consistency Group (Deprecated)

+

Function

This API is used to perform a failover for a replication consistency group. When an exception occurs in the primary AZ, a failover can be performed to change the primary site of a replication consistency group from the primary AZ to the secondary AZ and enable DR ECSs and DR disks in the secondary AZ to provide services.

+

After the failover, the replication_status value of the replication consistency group is active-stopped. In this case, EVS replication is available only after the primary AZ is restored and the replication consistency group is synchronized.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

If a fault occurs in the physical environment of the primary AZ due to force majeure and services become unavailable, perform a failover for the replication consistency group.

+
+

URI

+
+

Request

+ +
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2055.html b/docs/evs/api-ref/evs_04_2055.html new file mode 100644 index 000000000..3757b7a62 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2055.html @@ -0,0 +1,173 @@ + + +

Synchronizing a Replication Consistency Group (Deprecated)

+

Function

This API is used to synchronize the data between production disks and DR disks in all EVS replication pairs of a replication consistency group. After the synchronization is complete, the data in all EVS replication pairs of the replication consistency group is consistent.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2056.html b/docs/evs/api-ref/evs_04_2056.html new file mode 100644 index 000000000..453bd6515 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2056.html @@ -0,0 +1,174 @@ + + +

Performing a Primary/Secondary Switchover for a Replication Consistency Group (Deprecated)

+

Function

This API is used to perform a primary/secondary switchover for a replication consistency group. A switchover can be performed to switch the primary and secondary AZs of a replication consistency group, which means that the original secondary AZ will be switched to function as the primary AZ, and original DR ECSs and DR disks will be enabled.

+

After the primary/secondary switchover, the replication_status value of the replication consistency group is active. At this time, the data between production disks and DR disks in the primary and secondary AZs is consistent in real time, and EVS replication is working normally.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

The data synchronization of the replication consistency group is complete, and the replication consistency group is working normally.

+
+

URI

+
+

Request

+ +
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2057.html b/docs/evs/api-ref/evs_04_2057.html new file mode 100644 index 000000000..1c385bc9a --- /dev/null +++ b/docs/evs/api-ref/evs_04_2057.html @@ -0,0 +1,174 @@ + + +

Pausing a Replication Consistency Group (Deprecated)

+

Function

This API is used to pause a replication consistency group, that is, to pause the data synchronization in all EVS replication pairs of a replication consistency group.

+

Before deleting or updating a replication consistency group, you need to pause the replication consistency group.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2058.html b/docs/evs/api-ref/evs_04_2058.html new file mode 100644 index 000000000..86ff4cb27 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2058.html @@ -0,0 +1,174 @@ + + +

Reprotecting a Replication Consistency Group (Deprecated)

+

Function

This API is used to reprotect a replication consistency group. After resources in a faulty AZ have been restored and functioned as DR resources, a reprotection can be performed to synchronize data in all EVS replication pairs of a replication consistency group.

+

A reprotection can only be performed after the resources in the faulty primary AZ have been restored and can be used to synchronize data in all EVS replication pairs of a replication consistency group.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

+
+

URI

+
+

Request

+ +
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2059.html b/docs/evs/api-ref/evs_04_2059.html new file mode 100644 index 000000000..4e2ffe272 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2059.html @@ -0,0 +1,223 @@ + + +

Expanding EVS Disks in a Replication Consistency Group (Deprecated)

+

Function

This API is used to expand the EVS disks in one or multiple EVS replication pairs. In such an expansion operation, two EVS disks in one EVS replication pair are expanded together.

+

The status and replication_status values of the replication consistency group remain unchanged before and after capacity expansion. When 200 is returned, the capacity expansion is complete.

+

If the expansion fails, contact technical support engineers to locate and rectify the fault. After the fault is rectified, expand the disks again.

+

If the capacities of multiple EVS replication pairs in a protection group are expanded, an error indicating incorrect capacity will occur after the capacity expansion.

+

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

+
+
+

Constraints

+
+

URI

+
+

Request

+ + +
+

Response

None

+
+

Status Codes

+
+
+
+
+
Parent topic: Replication Consistency Group (Deprecated)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2063.html b/docs/evs/api-ref/evs_04_2063.html new file mode 100644 index 000000000..f9b45811a --- /dev/null +++ b/docs/evs/api-ref/evs_04_2063.html @@ -0,0 +1,17 @@ + + +

OpenStack Cinder API v2 (Recommended)

+
+
+ +
+ diff --git a/docs/evs/api-ref/evs_04_2064.html b/docs/evs/api-ref/evs_04_2064.html new file mode 100644 index 000000000..b99045ef1 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2064.html @@ -0,0 +1,47 @@ + + +

EVS Disk

+
+
+ + +
+
Parent topic: OpenStack Cinder API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2065.html b/docs/evs/api-ref/evs_04_2065.html new file mode 100644 index 000000000..8da9ff978 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2065.html @@ -0,0 +1,696 @@ + + +

Creating EVS Disks

+

Function

This API is used to create one or multiple EVS disks.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2066.html b/docs/evs/api-ref/evs_04_2066.html new file mode 100644 index 000000000..c0d97ce9e --- /dev/null +++ b/docs/evs/api-ref/evs_04_2066.html @@ -0,0 +1,136 @@ + + +

Deleting an EVS Disk

+

Function

This API is used to delete an EVS disk.

+
+

URI

+
+

Request

The following example shows how to delete a disk and all its snapshots.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2067.html b/docs/evs/api-ref/evs_04_2067.html new file mode 100644 index 000000000..7d89c87e1 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2067.html @@ -0,0 +1,549 @@ + + +

Updating an EVS Disk

+

Function

This API is used to update the EVS disk information.

+
+

URI

+
+

Request

+ + +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2068.html b/docs/evs/api-ref/evs_04_2068.html new file mode 100644 index 000000000..a857d0657 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2068.html @@ -0,0 +1,330 @@ + + +

Querying EVS Disks

+

Function

This API is used to query EVS disks.

+
+

URI

+
+

Request

The following example shows how to query the disks in the available state.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2069.html b/docs/evs/api-ref/evs_04_2069.html new file mode 100644 index 000000000..22ca32bac --- /dev/null +++ b/docs/evs/api-ref/evs_04_2069.html @@ -0,0 +1,612 @@ + + +

Querying Details About All Disks

+

Function

This API is used to query details about all disks.

+
+

URI

+
+

Request

The following example shows how to query details of the disks in the available state.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2070.html b/docs/evs/api-ref/evs_04_2070.html new file mode 100644 index 000000000..a269face8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2070.html @@ -0,0 +1,508 @@ + + +

Querying Details About a Disk

+

Function

This API is used to query details about a disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2071.html b/docs/evs/api-ref/evs_04_2071.html new file mode 100644 index 000000000..ada1064f4 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2071.html @@ -0,0 +1,242 @@ + + +

Querying EVS Disk Types

+

Function

This API is used to query EVS disk types and display the query results in a list.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2072.html b/docs/evs/api-ref/evs_04_2072.html new file mode 100644 index 000000000..7be984207 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2072.html @@ -0,0 +1,225 @@ + + +

Querying Details About an EVS Disk Type

+

Function

This API is used to query details about an EVS disk type.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2073.html b/docs/evs/api-ref/evs_04_2073.html new file mode 100644 index 000000000..98da001c2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2073.html @@ -0,0 +1,326 @@ + + +

Querying Details of Tenant Quotas

+

Function

This API is used to query the details of tenant quotas.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2074.html b/docs/evs/api-ref/evs_04_2074.html new file mode 100644 index 000000000..84a464f71 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2074.html @@ -0,0 +1,176 @@ + + +

Adding Metadata of an EVS Disk

+

Function

This API is used to add or update the metadata of an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2075.html b/docs/evs/api-ref/evs_04_2075.html new file mode 100644 index 000000000..c027a2dd8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2075.html @@ -0,0 +1,124 @@ + + +

Querying Metadata of an EVS Disk

+

Function

This API is used to query the metadata of an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2076.html b/docs/evs/api-ref/evs_04_2076.html new file mode 100644 index 000000000..b61d47470 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2076.html @@ -0,0 +1,176 @@ + + +

Updating Metadata of an EVS Disk

+

Function

This API is used to update the metadata of an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2077.html b/docs/evs/api-ref/evs_04_2077.html new file mode 100644 index 000000000..29eac89e8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2077.html @@ -0,0 +1,130 @@ + + +

Querying One Piece of Metadata for an EVS Disk

+

Function

This API is used to query one piece of the EVS disk metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2078.html b/docs/evs/api-ref/evs_04_2078.html new file mode 100644 index 000000000..6be0866fa --- /dev/null +++ b/docs/evs/api-ref/evs_04_2078.html @@ -0,0 +1,180 @@ + + +

Updating One Piece of Metadata for an EVS Disk

+

Function

This API is used to update one piece of the EVS disk metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2079.html b/docs/evs/api-ref/evs_04_2079.html new file mode 100644 index 000000000..a3e1537dc --- /dev/null +++ b/docs/evs/api-ref/evs_04_2079.html @@ -0,0 +1,119 @@ + + +

Deleting One Piece of Metadata for an EVS Disk

+

Function

This API is used to delete one piece of the EVS disk metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2080.html b/docs/evs/api-ref/evs_04_2080.html new file mode 100644 index 000000000..24d0e448a --- /dev/null +++ b/docs/evs/api-ref/evs_04_2080.html @@ -0,0 +1,346 @@ + + +

Querying Extension APIs

+

Function

This API is used to query extension APIs.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2081.html b/docs/evs/api-ref/evs_04_2081.html new file mode 100644 index 000000000..dae937d3a --- /dev/null +++ b/docs/evs/api-ref/evs_04_2081.html @@ -0,0 +1,160 @@ + + +

Querying All AZs

+

Function

This API is used to query all AZs.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2082.html b/docs/evs/api-ref/evs_04_2082.html new file mode 100644 index 000000000..8523c7e23 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2082.html @@ -0,0 +1,30 @@ + + +

EVS Disk Actions

+

+
+
+ + +
+
Parent topic: OpenStack Cinder API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2083.html b/docs/evs/api-ref/evs_04_2083.html new file mode 100644 index 000000000..7b9bda160 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2083.html @@ -0,0 +1,166 @@ + + +

Expanding Capacity of an EVS Disk

+

Function

This API is used to expand the capacity of an EVS disk.

+ +
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2084.html b/docs/evs/api-ref/evs_04_2084.html new file mode 100644 index 000000000..ed03ab6dc --- /dev/null +++ b/docs/evs/api-ref/evs_04_2084.html @@ -0,0 +1,166 @@ + + +

Setting Bootable Flag for an EVS Disk

+

Function

This API is used to set the bootable flag for an EVS disk.

+
+

Constraints

A data disk cannot be used as system disk for an ECS even if this API has been called to set the bootable flag for it.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2085.html b/docs/evs/api-ref/evs_04_2085.html new file mode 100644 index 000000000..2f496b887 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2085.html @@ -0,0 +1,164 @@ + + +

Setting Read-Only Flag for an EVS Disk

+

Function

This API is used to set the read-only flag for the EVS disk.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2086.html b/docs/evs/api-ref/evs_04_2086.html new file mode 100644 index 000000000..b9921377c --- /dev/null +++ b/docs/evs/api-ref/evs_04_2086.html @@ -0,0 +1,447 @@ + + +

Exporting EVS Disk Data as an Image

+

Function

This API is used to export the system disk data or data disk data as an IMS image. The exported image will be displayed in the IMS private image list and can be viewed and used.

+
+

Constraints

If the target disk is in the in-use state, stop the server where the disk has been attached before calling this API. If the target disk is a shared disk, stop all servers where the shared disk has been attached before calling this API.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2087.html b/docs/evs/api-ref/evs_04_2087.html new file mode 100644 index 000000000..0254d5891 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2087.html @@ -0,0 +1,196 @@ + + +

Attaching an EVS Disk (Deprecated)

+

Function

This API is only used to change the EVS disk status from available to in-use.

+

This API call exists for compatibility reasons only and is not meant to be used.

+
+
+

Constraints

Do not call this API to attach a disk. If you need to attach a disk, call the ECS Attach Volume API.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2088.html b/docs/evs/api-ref/evs_04_2088.html new file mode 100644 index 000000000..0e54fb5b8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2088.html @@ -0,0 +1,168 @@ + + +

Detaching an EVS Disk (Deprecated)

+

Function

This API is only used to change the EVS disk status from in-use to available.

+

This API call exists for compatibility reasons only and is not meant to be used.

+
+
+

Constraints

Do not call this API to detach a disk. If you need to detach a disk, call the ECS Detach Volume API.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2089.html b/docs/evs/api-ref/evs_04_2089.html new file mode 100644 index 000000000..a82273d03 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2089.html @@ -0,0 +1,141 @@ + + +

Reserving an EVS Disk (Deprecated)

+

Function

This API is used to reserve an EVS disk.

+

This API call exists for compatibility reasons only and is not meant to be used.

+
+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2090.html b/docs/evs/api-ref/evs_04_2090.html new file mode 100644 index 000000000..5605a0c38 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2090.html @@ -0,0 +1,141 @@ + + +

Canceling Reservation of an EVS Disk (Deprecated)

+

Function

This API is used to cancel the reservation of an EVS disk.

+

This API call exists for compatibility reasons only and is not meant to be used.

+
+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2092.html b/docs/evs/api-ref/evs_04_2092.html new file mode 100644 index 000000000..485aaa51d --- /dev/null +++ b/docs/evs/api-ref/evs_04_2092.html @@ -0,0 +1,37 @@ + + +

EVS Snapshot

+
+
+ + +
+
Parent topic: OpenStack Cinder API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2093.html b/docs/evs/api-ref/evs_04_2093.html new file mode 100644 index 000000000..4953687dd --- /dev/null +++ b/docs/evs/api-ref/evs_04_2093.html @@ -0,0 +1,312 @@ + + +

Creating an EVS Snapshot

+

Function

This API is used to create an EVS snapshot.

+
+

URI

+
+

Request

+ + +
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2094.html b/docs/evs/api-ref/evs_04_2094.html new file mode 100644 index 000000000..d2d3d6ace --- /dev/null +++ b/docs/evs/api-ref/evs_04_2094.html @@ -0,0 +1,114 @@ + + +

Deleting an EVS Snapshot

+

Function

This API is used to delete an EVS snapshot.

+
+

Constraints

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2095.html b/docs/evs/api-ref/evs_04_2095.html new file mode 100644 index 000000000..fe623368b --- /dev/null +++ b/docs/evs/api-ref/evs_04_2095.html @@ -0,0 +1,288 @@ + + +

Updating an EVS Snapshot

+

Function

This API is used to update an EVS snapshot.

+
+

URI

+
+

Request

+ + +
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2096.html b/docs/evs/api-ref/evs_04_2096.html new file mode 100644 index 000000000..45b654983 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2096.html @@ -0,0 +1,319 @@ + + +

Querying EVS Snapshots

+

Function

This API is used to query the EVS snapshots.

+
+

URI

+
+

Request

The following example shows how to query the snapshots in the available state.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2097.html b/docs/evs/api-ref/evs_04_2097.html new file mode 100644 index 000000000..aefb0ec07 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2097.html @@ -0,0 +1,316 @@ + + +

Querying Details About EVS Snapshots

+

Function

This API is used to query details about the EVS snapshots.

+
+

URI

+
+

Request

The following example shows how to query details of the snapshots in the available state.

+ +
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2098.html b/docs/evs/api-ref/evs_04_2098.html new file mode 100644 index 000000000..46c640a47 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2098.html @@ -0,0 +1,229 @@ + + +

Querying Details About an EVS Snapshot

+

Function

This API is used to query details about an EVS snapshot.

+
+

URI

+
+

Request

+
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2099.html b/docs/evs/api-ref/evs_04_2099.html new file mode 100644 index 000000000..41e4eac51 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2099.html @@ -0,0 +1,176 @@ + + +

Adding Metadata of an EVS Snapshot

+

Function

This API is used to add the metadata of an EVS snapshot.

+
+

URI

+
+

Request

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2100.html b/docs/evs/api-ref/evs_04_2100.html new file mode 100644 index 000000000..b1e405a2a --- /dev/null +++ b/docs/evs/api-ref/evs_04_2100.html @@ -0,0 +1,125 @@ + + +

Querying Metadata of an EVS Snapshot

+

Function

This API is used to query the metadata of an EVS snapshot.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2101.html b/docs/evs/api-ref/evs_04_2101.html new file mode 100644 index 000000000..ca2bb8857 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2101.html @@ -0,0 +1,180 @@ + + +

Updating One Piece of Metadata for an EVS Snapshot

+

Function

This API is used to update one piece of the EVS snapshot metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2102.html b/docs/evs/api-ref/evs_04_2102.html new file mode 100644 index 000000000..18a545f27 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2102.html @@ -0,0 +1,175 @@ + + +

Updating Metadata of an EVS Snapshot

+

Function

This API is used to update the metadata of an EVS snapshot.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2103.html b/docs/evs/api-ref/evs_04_2103.html new file mode 100644 index 000000000..a8ddbf0a2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2103.html @@ -0,0 +1,130 @@ + + +

Querying One Piece of Metadata for an EVS Snapshot

+

Function

This API is used to query one piece of the EVS snapshot metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2104.html b/docs/evs/api-ref/evs_04_2104.html new file mode 100644 index 000000000..80f42e9ce --- /dev/null +++ b/docs/evs/api-ref/evs_04_2104.html @@ -0,0 +1,120 @@ + + +

Deleting One Piece of Metadata for an EVS Snapshot

+

Function

This API is used to delete one piece of the EVS snapshot metadata.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2105.html b/docs/evs/api-ref/evs_04_2105.html new file mode 100644 index 000000000..30728c225 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2105.html @@ -0,0 +1,25 @@ + + +

EVS Disk Transfer

+
+
+ + +
+
Parent topic: OpenStack Cinder API v2 (Recommended)
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2106.html b/docs/evs/api-ref/evs_04_2106.html new file mode 100644 index 000000000..9095bd9b5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2106.html @@ -0,0 +1,204 @@ + + +

Creating a Disk Transfer

+

Function

This API is used to create a disk transfer. After the transfer has been created, a transfer ID and an authentication key are returned.

+

After a disk transfer is created, the disk status changes from available to awaiting-transfer. Once the disk transfer is accepted, the disk status changes to available again.

+
+

Constraints

A disk transfer can be created only when the disk status is available. The detailed constraints are as follows:

+ +

If the disk transfer is created using one of the unsupported disks, error code 400 will be returned.

+
+
+

URI

+
+

Request

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2107.html b/docs/evs/api-ref/evs_04_2107.html new file mode 100644 index 000000000..4f850c1a9 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2107.html @@ -0,0 +1,183 @@ + + +

Accepting a Disk Transfer

+

Function

This API is used to accept a disk transfer through the transfer ID and authentication key.

+
+

Constraints

+

If the disk transfer is created using one of the unsupported disks, error code 400 will be returned.

+
+
+

URI

+
+

Request

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2108.html b/docs/evs/api-ref/evs_04_2108.html new file mode 100644 index 000000000..8fce885c8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2108.html @@ -0,0 +1,51 @@ + + +

Deleting a Disk Transfer

+

Function

This API is used to delete a disk transfer. A disk transfer can be deleted if it is not accepted. Accepted disk transfers cannot be deleted.

+
+

URI

+
+

Request

+
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2109.html b/docs/evs/api-ref/evs_04_2109.html new file mode 100644 index 000000000..e3c7faeb1 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2109.html @@ -0,0 +1,136 @@ + + +

Querying Details of a Disk Transfer

+

Function

This API is used to query the details of a disk transfer, including the transfer creation time, transfer ID, and transfer name.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2110.html b/docs/evs/api-ref/evs_04_2110.html new file mode 100644 index 000000000..3801678ad --- /dev/null +++ b/docs/evs/api-ref/evs_04_2110.html @@ -0,0 +1,171 @@ + + +

Querying All Disk Transfers

+

Function

This API is used to query all disk transfers of the current tenant.

+
+

URI

+
+

Request

The following example shows how to query details of the disk transfers whose limit is no more than 50.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_2111.html b/docs/evs/api-ref/evs_04_2111.html new file mode 100644 index 000000000..1d4bf1a30 --- /dev/null +++ b/docs/evs/api-ref/evs_04_2111.html @@ -0,0 +1,183 @@ + + +

Querying Details of All Disk Transfers

+

Function

This API is used to query the details of all disk transfers, including the transfer creation time, transfer IDs, and transfer names.

+
+

URI

+
+

Request

The following example shows how to query details of the disk transfers whose limit is no more than 50.

+ +
+

Parameter description

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3001.html b/docs/evs/api-ref/evs_04_3001.html new file mode 100644 index 000000000..8751bed8c --- /dev/null +++ b/docs/evs/api-ref/evs_04_3001.html @@ -0,0 +1,20 @@ + + +

API v3

+

+
+
+ + +
+
Parent topic: Unrecommended APIs
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3002.html b/docs/evs/api-ref/evs_04_3002.html new file mode 100644 index 000000000..887a4a6a5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3002.html @@ -0,0 +1,22 @@ + + +

EVS Disk

+

+
+
+ + +
+
Parent topic: API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3003.html b/docs/evs/api-ref/evs_04_3003.html new file mode 100644 index 000000000..d5ed2a863 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3003.html @@ -0,0 +1,374 @@ + + +

Creating EVS Disks

+

Function

This API is used to create one or multiple EVS disks.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3004.html b/docs/evs/api-ref/evs_04_3004.html new file mode 100644 index 000000000..d67b60af5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3004.html @@ -0,0 +1,672 @@ + + +

Querying Details About All EVS Disks (Deprecated)

+

Function

This API is used to query details about all disks.

+
+

URI

+
+

Request

The following example shows how to query the shared disks in the available state.
  • Example request
    GET https://{endpoint}/v3/{project_id}/os-vendor-volumes/detail?status=available&multiattach=true
    +
+
+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3005.html b/docs/evs/api-ref/evs_04_3005.html new file mode 100644 index 000000000..23b1df441 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3005.html @@ -0,0 +1,537 @@ + + +

Querying Details About an EVS Disk (Deprecated)

+

Function

This API is used to query details about a disk.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3006.html b/docs/evs/api-ref/evs_04_3006.html new file mode 100644 index 000000000..8f2499d75 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3006.html @@ -0,0 +1,141 @@ + + +

Querying Loading Progress of a Lazyloading Disk

+

Function

This API is used to query the loading progress of a lazyloading disk.

+
+

URI

+
+

Request

None

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3007.html b/docs/evs/api-ref/evs_04_3007.html new file mode 100644 index 000000000..c3cb768d3 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3007.html @@ -0,0 +1,16 @@ + + +

EVS Snapshot

+

+
+
+ + +
+
Parent topic: API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3008.html b/docs/evs/api-ref/evs_04_3008.html new file mode 100644 index 000000000..225a955d0 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3008.html @@ -0,0 +1,210 @@ + + +

Rolling Back a Snapshot to an EVS Disk

+

Function

This API is used to roll back a snapshot to an EVS disk.

+
+

Constraints

+
+

URI

+ +
+

Request

+ + +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3010.html b/docs/evs/api-ref/evs_04_3010.html new file mode 100644 index 000000000..13667f1f3 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3010.html @@ -0,0 +1,24 @@ + + +

EVS Tag

+

+
+
+ + +
+
Parent topic: API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3011.html b/docs/evs/api-ref/evs_04_3011.html new file mode 100644 index 000000000..70514e567 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3011.html @@ -0,0 +1,133 @@ + + +

Batch Adding Tags for the Specified EVS Disk

+

Function

This API is used to batch add tags for the specified EVS disk.

+ +
+

Constraints

None

+
+

URI

+
+

Request

+
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3013.html b/docs/evs/api-ref/evs_04_3013.html new file mode 100644 index 000000000..1baa20cdd --- /dev/null +++ b/docs/evs/api-ref/evs_04_3013.html @@ -0,0 +1,130 @@ + + +

Batch Deleting Tags for the Specified EVS Disk

+

Function

This API is used to batch delete tags for the specified EVS disk.

+
+

Constraints

None

+
+

URI

+
+

Request

+
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3015.html b/docs/evs/api-ref/evs_04_3015.html new file mode 100644 index 000000000..3b61d5214 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3015.html @@ -0,0 +1,109 @@ + + +

Querying Tags of an EVS Disk

+

Function

This API is used to query the tags of the specified EVS disk.

+
+

Constraints

None

+
+

URI

+
+

Request

None

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3016.html b/docs/evs/api-ref/evs_04_3016.html new file mode 100644 index 000000000..1c3d2da92 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3016.html @@ -0,0 +1,262 @@ + + +

Querying the Number of EVS Disks by Tag

+

Function

This API is used to query the number of EVS disks by tag.

+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3018.html b/docs/evs/api-ref/evs_04_3018.html new file mode 100644 index 000000000..066e42b83 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3018.html @@ -0,0 +1,435 @@ + + +

Querying Details of EVS Disks by Tag

+

Function

This API is used to query the details of EVS disks by tag.

+
+

Constraints

None

+
+

URI

+
+

Request

+ +
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Tag
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3027.html b/docs/evs/api-ref/evs_04_3027.html new file mode 100644 index 000000000..cc47f2fa5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3027.html @@ -0,0 +1,22 @@ + + +

OpenStack Cinder API v3

+

+
+
+ + +
+
Parent topic: Unrecommended APIs
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3028.html b/docs/evs/api-ref/evs_04_3028.html new file mode 100644 index 000000000..5048a2dd5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3028.html @@ -0,0 +1,48 @@ + + +

EVS Disk

+

+
+
+ + +
+
Parent topic: OpenStack Cinder API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3029.html b/docs/evs/api-ref/evs_04_3029.html new file mode 100644 index 000000000..1c584c1c0 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3029.html @@ -0,0 +1,696 @@ + + +

Creating EVS Disks

+

Function

This API is used to create one or multiple EVS disks.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3030.html b/docs/evs/api-ref/evs_04_3030.html new file mode 100644 index 000000000..f7b355677 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3030.html @@ -0,0 +1,136 @@ + + +

Deleting an EVS Disk

+

Function

This API is used to delete an EVS disk.

+
+

URI

+
+

Request

The following example shows how to delete a disk and all its snapshots.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3031.html b/docs/evs/api-ref/evs_04_3031.html new file mode 100644 index 000000000..c0e421887 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3031.html @@ -0,0 +1,549 @@ + + +

Updating an EVS Disk

+

Function

This API is used to update the EVS disk information.

+
+

URI

+
+

Request

+ + +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3032.html b/docs/evs/api-ref/evs_04_3032.html new file mode 100644 index 000000000..89b591e7d --- /dev/null +++ b/docs/evs/api-ref/evs_04_3032.html @@ -0,0 +1,338 @@ + + +

Querying EVS Disks

+

Function

This API is used to query EVS disks.

+
+

URI

+
+

Request

The following example shows how to query the disks in the available state.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3033.html b/docs/evs/api-ref/evs_04_3033.html new file mode 100644 index 000000000..215947b5b --- /dev/null +++ b/docs/evs/api-ref/evs_04_3033.html @@ -0,0 +1,612 @@ + + +

Querying Details About All Disks

+

Function

This API is used to query details about all disks.

+
+

URI

+
+

Request

The following example shows how to query details of the disks in the available state.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3034.html b/docs/evs/api-ref/evs_04_3034.html new file mode 100644 index 000000000..e24756336 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3034.html @@ -0,0 +1,508 @@ + + +

Querying Details About a Disk

+

Function

This API is used to query details about a disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3035.html b/docs/evs/api-ref/evs_04_3035.html new file mode 100644 index 000000000..1335679e2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3035.html @@ -0,0 +1,242 @@ + + +

Querying EVS Disk Types

+

Function

This API is used to query EVS disk types and display the query results in a list.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3036.html b/docs/evs/api-ref/evs_04_3036.html new file mode 100644 index 000000000..1c550ce50 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3036.html @@ -0,0 +1,225 @@ + + +

Querying Details About an EVS Disk Type

+

Function

This API is used to query details about an EVS disk type.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3037.html b/docs/evs/api-ref/evs_04_3037.html new file mode 100644 index 000000000..b67b9ec35 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3037.html @@ -0,0 +1,326 @@ + + +

Querying Details of Tenant Quotas

+

Function

This API is used to query the details of tenant quotas.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3038.html b/docs/evs/api-ref/evs_04_3038.html new file mode 100644 index 000000000..33b71efa3 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3038.html @@ -0,0 +1,176 @@ + + +

Adding Metadata of an EVS Disk

+

Function

This API is used to add or update the metadata of an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3039.html b/docs/evs/api-ref/evs_04_3039.html new file mode 100644 index 000000000..249453008 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3039.html @@ -0,0 +1,124 @@ + + +

Querying Metadata of an EVS Disk

+

Function

This API is used to query the metadata of an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3040.html b/docs/evs/api-ref/evs_04_3040.html new file mode 100644 index 000000000..305890e3f --- /dev/null +++ b/docs/evs/api-ref/evs_04_3040.html @@ -0,0 +1,176 @@ + + +

Updating Metadata of an EVS Disk

+

Function

This API is used to update the metadata of an EVS disk.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3041.html b/docs/evs/api-ref/evs_04_3041.html new file mode 100644 index 000000000..3d28b1e5f --- /dev/null +++ b/docs/evs/api-ref/evs_04_3041.html @@ -0,0 +1,130 @@ + + +

Querying One Piece of Metadata for an EVS Disk

+

Function

This API is used to query one piece of the EVS disk metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3042.html b/docs/evs/api-ref/evs_04_3042.html new file mode 100644 index 000000000..2dd269e27 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3042.html @@ -0,0 +1,180 @@ + + +

Updating One Piece of Metadata for an EVS Disk

+

Function

This API is used to update one piece of the EVS disk metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3043.html b/docs/evs/api-ref/evs_04_3043.html new file mode 100644 index 000000000..31d57d34b --- /dev/null +++ b/docs/evs/api-ref/evs_04_3043.html @@ -0,0 +1,119 @@ + + +

Deleting One Piece of Metadata for an EVS Disk

+

Function

This API is used to delete one piece of the EVS disk metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3044.html b/docs/evs/api-ref/evs_04_3044.html new file mode 100644 index 000000000..f1fb70b30 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3044.html @@ -0,0 +1,346 @@ + + +

Querying Extension APIs

+

Function

This API is used to query extension APIs.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3045.html b/docs/evs/api-ref/evs_04_3045.html new file mode 100644 index 000000000..f869d06fb --- /dev/null +++ b/docs/evs/api-ref/evs_04_3045.html @@ -0,0 +1,160 @@ + + +

Querying All AZs

+

Function

This API is used to query all AZs.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3047.html b/docs/evs/api-ref/evs_04_3047.html new file mode 100644 index 000000000..4de5c947e --- /dev/null +++ b/docs/evs/api-ref/evs_04_3047.html @@ -0,0 +1,26 @@ + + +

EVS Disk Actions

+

+
+
+ + +
+
Parent topic: OpenStack Cinder API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3048.html b/docs/evs/api-ref/evs_04_3048.html new file mode 100644 index 000000000..75dddd4bd --- /dev/null +++ b/docs/evs/api-ref/evs_04_3048.html @@ -0,0 +1,166 @@ + + +

Expanding Capacity of an EVS Disk

+

Function

This API is used to expand the capacity of an EVS disk.

+ +
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3049.html b/docs/evs/api-ref/evs_04_3049.html new file mode 100644 index 000000000..115f83761 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3049.html @@ -0,0 +1,166 @@ + + +

Setting Bootable Flag for an EVS Disk

+

Function

This API is used to set the bootable flag for an EVS disk.

+
+

Constraints

A data disk cannot be used as system disk for an ECS even if this API has been called to set the bootable flag for it.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3050.html b/docs/evs/api-ref/evs_04_3050.html new file mode 100644 index 000000000..00e76757f --- /dev/null +++ b/docs/evs/api-ref/evs_04_3050.html @@ -0,0 +1,164 @@ + + +

Setting Read-Only Flag for an EVS Disk

+

Function

This API is used to set the read-only flag for the EVS disk.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3051.html b/docs/evs/api-ref/evs_04_3051.html new file mode 100644 index 000000000..bd3d5be98 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3051.html @@ -0,0 +1,445 @@ + + +

Exporting EVS Disk Data as an Image

+

Function

This API is used to export the system disk data or data disk data as an IMS image. The exported image will be displayed in the IMS private image list and can be viewed and used.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3052.html b/docs/evs/api-ref/evs_04_3052.html new file mode 100644 index 000000000..86be2846a --- /dev/null +++ b/docs/evs/api-ref/evs_04_3052.html @@ -0,0 +1,141 @@ + + +

Reserving an EVS Disk (Deprecated)

+

Function

This API is used to reserve an EVS disk.

+

This API call exists for compatibility reasons only and is not meant to be used.

+
+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3053.html b/docs/evs/api-ref/evs_04_3053.html new file mode 100644 index 000000000..251076059 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3053.html @@ -0,0 +1,141 @@ + + +

Canceling Reservation of an EVS Disk (Deprecated)

+

Function

This API is used to cancel the reservation of an EVS disk.

+

This API call exists for compatibility reasons only and is not meant to be used.

+
+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Actions
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3055.html b/docs/evs/api-ref/evs_04_3055.html new file mode 100644 index 000000000..d47f3767c --- /dev/null +++ b/docs/evs/api-ref/evs_04_3055.html @@ -0,0 +1,38 @@ + + +

EVS Snapshot

+

+
+
+ + +
+
Parent topic: OpenStack Cinder API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3056.html b/docs/evs/api-ref/evs_04_3056.html new file mode 100644 index 000000000..3123afd43 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3056.html @@ -0,0 +1,298 @@ + + +

Creating an EVS Snapshot

+

Function

This API is used to create an EVS snapshot.

+
+

URI

+
+

Request

+ + +
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3057.html b/docs/evs/api-ref/evs_04_3057.html new file mode 100644 index 000000000..9c23c94d3 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3057.html @@ -0,0 +1,114 @@ + + +

Deleting an EVS Snapshot

+

Function

This API is used to delete an EVS snapshot.

+
+

Constraints

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3058.html b/docs/evs/api-ref/evs_04_3058.html new file mode 100644 index 000000000..6f1688e33 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3058.html @@ -0,0 +1,288 @@ + + +

Updating an EVS Snapshot

+

Function

This API is used to update an EVS snapshot.

+
+

URI

+
+

Request

+ + +
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3059.html b/docs/evs/api-ref/evs_04_3059.html new file mode 100644 index 000000000..f32c9f542 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3059.html @@ -0,0 +1,383 @@ + + +

Querying EVS Snapshots

+

Function

This API is used to query the EVS snapshots.

+
+

URI

+
+

Request

The following example shows how to query the snapshots in the available state.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3060.html b/docs/evs/api-ref/evs_04_3060.html new file mode 100644 index 000000000..7f96ba79a --- /dev/null +++ b/docs/evs/api-ref/evs_04_3060.html @@ -0,0 +1,343 @@ + + +

Querying Details About EVS Snapshots

+

Function

This API is used to query details about the EVS snapshots.

+
+

URI

+
+

Request

The following example shows how to query details of the snapshots in the available state.

+ +
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3061.html b/docs/evs/api-ref/evs_04_3061.html new file mode 100644 index 000000000..4607d3275 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3061.html @@ -0,0 +1,236 @@ + + +

Querying Details About an EVS Snapshot

+

Function

This API is used to query details about an EVS snapshot.

+
+

URI

+
+

Request

+
+

Response

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3062.html b/docs/evs/api-ref/evs_04_3062.html new file mode 100644 index 000000000..6c553f5b8 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3062.html @@ -0,0 +1,176 @@ + + +

Adding Metadata of an EVS Snapshot

+

Function

This API is used to add the metadata of an EVS snapshot.

+
+

URI

+
+

Request

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3063.html b/docs/evs/api-ref/evs_04_3063.html new file mode 100644 index 000000000..5b11915c5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3063.html @@ -0,0 +1,125 @@ + + +

Querying Metadata of an EVS Snapshot

+

Function

This API is used to query the metadata of an EVS snapshot.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3064.html b/docs/evs/api-ref/evs_04_3064.html new file mode 100644 index 000000000..28cebaa31 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3064.html @@ -0,0 +1,180 @@ + + +

Updating One Piece of Metadata for an EVS Snapshot

+

Function

This API is used to update one piece of the EVS snapshot metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3065.html b/docs/evs/api-ref/evs_04_3065.html new file mode 100644 index 000000000..c5b770d94 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3065.html @@ -0,0 +1,175 @@ + + +

Updating Metadata of an EVS Snapshot

+

Function

This API is used to update the metadata of an EVS snapshot.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3066.html b/docs/evs/api-ref/evs_04_3066.html new file mode 100644 index 000000000..36503a518 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3066.html @@ -0,0 +1,128 @@ + + +

Querying One Piece of Metadata for an EVS Snapshot

+

Function

This API is used to query one piece of the EVS snapshot metadata.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3067.html b/docs/evs/api-ref/evs_04_3067.html new file mode 100644 index 000000000..ed784d647 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3067.html @@ -0,0 +1,120 @@ + + +

Deleting One Piece of Metadata for an EVS Snapshot

+

Function

This API is used to delete one piece of the EVS snapshot metadata.

+
+

URI

+
+

Request

+
+

Response

+ +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Snapshot
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3068.html b/docs/evs/api-ref/evs_04_3068.html new file mode 100644 index 000000000..788e6e8df --- /dev/null +++ b/docs/evs/api-ref/evs_04_3068.html @@ -0,0 +1,26 @@ + + +

EVS Disk Transfer

+

+
+
+ + +
+
Parent topic: OpenStack Cinder API v3
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3069.html b/docs/evs/api-ref/evs_04_3069.html new file mode 100644 index 000000000..ff0770b89 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3069.html @@ -0,0 +1,204 @@ + + +

Creating a Disk Transfer

+

Function

This API is used to create a disk transfer. After the transfer has been created, a transfer ID and an authentication key are returned.

+

After a disk transfer is created, the disk status changes from available to awaiting-transfer. Once the disk transfer is accepted, the disk status changes to available again.

+
+

Constraints

A disk transfer can be created only when the disk status is available. The detailed constraints are as follows:

+ +

If the disk transfer is created using one of the unsupported disks, error code 400 will be returned.

+
+
+

URI

+
+

Request

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3070.html b/docs/evs/api-ref/evs_04_3070.html new file mode 100644 index 000000000..f7f7f7af5 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3070.html @@ -0,0 +1,183 @@ + + +

Accepting a Disk Transfer

+

Function

This API is used to accept a disk transfer through the transfer ID and authentication key.

+
+

Constraints

+

If the disk transfer is created using one of the unsupported disks, error code 400 will be returned.

+
+
+

URI

+
+

Request

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3071.html b/docs/evs/api-ref/evs_04_3071.html new file mode 100644 index 000000000..c20c8b7c9 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3071.html @@ -0,0 +1,51 @@ + + +

Deleting a Disk Transfer

+

Function

This API is used to delete a disk transfer. A disk transfer can be deleted if it is not accepted. Accepted disk transfers cannot be deleted.

+
+

URI

+
+

Request

+
+

Response

None

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3072.html b/docs/evs/api-ref/evs_04_3072.html new file mode 100644 index 000000000..474b56cd2 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3072.html @@ -0,0 +1,136 @@ + + +

Querying Details of a Disk Transfer

+

Function

This API is used to query the details of a disk transfer, including the transfer creation time, transfer ID, and transfer name.

+
+

URI

+
+

Request

+
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3073.html b/docs/evs/api-ref/evs_04_3073.html new file mode 100644 index 000000000..03225bd30 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3073.html @@ -0,0 +1,171 @@ + + +

Querying All Disk Transfers

+

Function

This API is used to query all disk transfers of the current tenant.

+
+

URI

+
+

Request

The following example shows how to query details of the disk transfers whose limit is no more than 50.

+ +
+

Response

+
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/evs_04_3074.html b/docs/evs/api-ref/evs_04_3074.html new file mode 100644 index 000000000..1adc7f587 --- /dev/null +++ b/docs/evs/api-ref/evs_04_3074.html @@ -0,0 +1,183 @@ + + +

Querying Details of All Disk Transfers

+

Function

This API is used to query the details of all disk transfers, including the transfer creation time, transfer IDs, and transfer names.

+
+

URI

+
+

Request

The following example shows how to query details of the disk transfers whose limit is no more than 50.

+ +
+

Parameter description

+ + +
+

Status Codes

+
+

Error Codes

For details, see Error Codes.

+
+
+
+
+
Parent topic: EVS Disk Transfer
+
+
+ diff --git a/docs/evs/api-ref/public_sys-resources/ExpandCollapse.js b/docs/evs/api-ref/public_sys-resources/ExpandCollapse.js new file mode 100644 index 000000000..3f1b7db00 --- /dev/null +++ b/docs/evs/api-ref/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";var href="";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(href.substring(href.lastIndexOf("#")+1))}}catch(a){}}; \ No newline at end of file diff --git a/docs/evs/api-ref/public_sys-resources/caution_3.0-en-us.png b/docs/evs/api-ref/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 000000000..60f607621 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/evs/api-ref/public_sys-resources/commonltr.css b/docs/evs/api-ref/public_sys-resources/commonltr.css new file mode 100644 index 000000000..c5480b0ab --- /dev/null +++ b/docs/evs/api-ref/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/evs/api-ref/public_sys-resources/commonltr_print.css b/docs/evs/api-ref/public_sys-resources/commonltr_print.css new file mode 100644 index 000000000..a59823141 --- /dev/null +++ b/docs/evs/api-ref/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/evs/api-ref/public_sys-resources/commonrtl.css b/docs/evs/api-ref/public_sys-resources/commonrtl.css new file mode 100644 index 000000000..947a9a033 --- /dev/null +++ b/docs/evs/api-ref/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/evs/api-ref/public_sys-resources/danger_3.0-en-us.png b/docs/evs/api-ref/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 000000000..47a9c7235 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/evs/api-ref/public_sys-resources/delta.gif b/docs/evs/api-ref/public_sys-resources/delta.gif new file mode 100644 index 000000000..0d1b1f674 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/delta.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/deltaend.gif b/docs/evs/api-ref/public_sys-resources/deltaend.gif new file mode 100644 index 000000000..cc7da0fc8 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/deltaend.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-arrowdn.gif b/docs/evs/api-ref/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 000000000..84eec9be2 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-arrowrt.gif b/docs/evs/api-ref/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 000000000..39583d168 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-caution.gif b/docs/evs/api-ref/public_sys-resources/icon-caution.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-caution.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-danger.gif b/docs/evs/api-ref/public_sys-resources/icon-danger.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-danger.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-huawei.gif b/docs/evs/api-ref/public_sys-resources/icon-huawei.gif new file mode 100644 index 000000000..a31d60f89 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-huawei.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-note.gif b/docs/evs/api-ref/public_sys-resources/icon-note.gif new file mode 100644 index 000000000..31be2b039 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-note.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-notice.gif b/docs/evs/api-ref/public_sys-resources/icon-notice.gif new file mode 100644 index 000000000..409070650 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-notice.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-tip.gif b/docs/evs/api-ref/public_sys-resources/icon-tip.gif new file mode 100644 index 000000000..c47bae05c Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-tip.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/icon-warning.gif b/docs/evs/api-ref/public_sys-resources/icon-warning.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/icon-warning.gif differ diff --git a/docs/evs/api-ref/public_sys-resources/note_3.0-en-us.png b/docs/evs/api-ref/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 000000000..57a0e1f53 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/note_3.0-en-us.png differ diff --git a/docs/evs/api-ref/public_sys-resources/notice_3.0-en-us.png b/docs/evs/api-ref/public_sys-resources/notice_3.0-en-us.png new file mode 100644 index 000000000..fa4b64990 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/notice_3.0-en-us.png differ diff --git a/docs/evs/api-ref/public_sys-resources/popup.js b/docs/evs/api-ref/public_sys-resources/popup.js new file mode 100644 index 000000000..a550862ed --- /dev/null +++ b/docs/evs/api-ref/public_sys-resources/popup.js @@ -0,0 +1 @@ +var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/evs/api-ref/public_sys-resources/warning_3.0-en-us.png b/docs/evs/api-ref/public_sys-resources/warning_3.0-en-us.png new file mode 100644 index 000000000..def5c3565 Binary files /dev/null and b/docs/evs/api-ref/public_sys-resources/warning_3.0-en-us.png differ diff --git a/docs/evs/dev/ALL_META.TXT.json b/docs/evs/dev/ALL_META.TXT.json new file mode 100644 index 000000000..f7104c861 --- /dev/null +++ b/docs/evs/dev/ALL_META.TXT.json @@ -0,0 +1,92 @@ +[ + { + "uri":"evs_03_0001.html", + "product_code":"evs", + "code":"1", + "des":"This document describes how to call the Elastic Volume Service (EVS) APIs to use various EVS functions.This chapter describes the concepts related to EVS to help you quic", + "doc_type":"devg", + "kw":"Overview,Developer Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"evs_03_0002.html", + "product_code":"evs", + "code":"2", + "des":"You need to learn how to call the EVS APIs before you start. For details about how to call RESTful APIs, see API Usage Guidelines.", + "doc_type":"devg", + "kw":"Before You Start,Developer Guide", + "title":"Before You Start", + "githuburl":"" + }, + { + "uri":"evs_03_0003.html", + "product_code":"evs", + "code":"3", + "des":"This API is used to create one or multiple EVS disks.NoneQuery the AZs before you create EVS disks.If you need to create system disks, query the image information and obt", + "doc_type":"devg", + "kw":"Creating EVS Disks,Developer Guide", + "title":"Creating EVS Disks", + "githuburl":"" + }, + { + "uri":"evs_03_0004.html", + "product_code":"evs", + "code":"4", + "des":"For an EVS disk that has been created, you can call this API to expand the disk capacity if the disk space is insufficient.If the status of the to-be-expanded disk is ava", + "doc_type":"devg", + "kw":"Expanding the Capacity of an EVS Disk,Developer Guide", + "title":"Expanding the Capacity of an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_03_0005.html", + "product_code":"evs", + "code":"5", + "des":"If an EVS disk is no longer used, you can delete it to release virtual resources.An EVS disk can be deleted only when its status is available, error, error_extending, err", + "doc_type":"devg", + "kw":"Deleting an EVS Disk,Developer Guide", + "title":"Deleting an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_03_0006.html", + "product_code":"evs", + "code":"6", + "des":"You can create an EVS snapshot on the management console to save the disk data at a specific time point.A maximum of 7 snapshots can be created for an EVS disk.Query the ", + "doc_type":"devg", + "kw":"Creating an EVS Snapshot,Developer Guide", + "title":"Creating an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_03_0007.html", + "product_code":"evs", + "code":"7", + "des":"If an EVS snapshot is no longer used, you can delete it to release virtual resources.A snapshot can be deleted only when it is in the available or error state.Query the s", + "doc_type":"devg", + "kw":"Deleting an EVS Snapshot,Developer Guide", + "title":"Deleting an EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_03_0008.html", + "product_code":"evs", + "code":"8", + "des":"If the data in an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source EVS disk to restore the data.When you roll back a snapshot to", + "doc_type":"devg", + "kw":"Rolling Back a Snapshot to an EVS Disk,Developer Guide", + "title":"Rolling Back a Snapshot to an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_03_0010.html", + "product_code":"evs", + "code":"9", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"devg", + "kw":"Change History,Developer Guide", + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/evs/dev/CLASS.TXT.json b/docs/evs/dev/CLASS.TXT.json new file mode 100644 index 000000000..e901cf2f7 --- /dev/null +++ b/docs/evs/dev/CLASS.TXT.json @@ -0,0 +1,83 @@ +[ + { + "desc":"This document describes how to call the Elastic Volume Service (EVS) APIs to use various EVS functions.This chapter describes the concepts related to EVS to help you quic", + "product_code":"evs", + "title":"Overview", + "uri":"evs_03_0001.html", + "doc_type":"devg", + "p_code":"", + "code":"1" + }, + { + "desc":"You need to learn how to call the EVS APIs before you start. For details about how to call RESTful APIs, see API Usage Guidelines.", + "product_code":"evs", + "title":"Before You Start", + "uri":"evs_03_0002.html", + "doc_type":"devg", + "p_code":"", + "code":"2" + }, + { + "desc":"This API is used to create one or multiple EVS disks.NoneQuery the AZs before you create EVS disks.If you need to create system disks, query the image information and obt", + "product_code":"evs", + "title":"Creating EVS Disks", + "uri":"evs_03_0003.html", + "doc_type":"devg", + "p_code":"", + "code":"3" + }, + { + "desc":"For an EVS disk that has been created, you can call this API to expand the disk capacity if the disk space is insufficient.If the status of the to-be-expanded disk is ava", + "product_code":"evs", + "title":"Expanding the Capacity of an EVS Disk", + "uri":"evs_03_0004.html", + "doc_type":"devg", + "p_code":"", + "code":"4" + }, + { + "desc":"If an EVS disk is no longer used, you can delete it to release virtual resources.An EVS disk can be deleted only when its status is available, error, error_extending, err", + "product_code":"evs", + "title":"Deleting an EVS Disk", + "uri":"evs_03_0005.html", + "doc_type":"devg", + "p_code":"", + "code":"5" + }, + { + "desc":"You can create an EVS snapshot on the management console to save the disk data at a specific time point.A maximum of 7 snapshots can be created for an EVS disk.Query the ", + "product_code":"evs", + "title":"Creating an EVS Snapshot", + "uri":"evs_03_0006.html", + "doc_type":"devg", + "p_code":"", + "code":"6" + }, + { + "desc":"If an EVS snapshot is no longer used, you can delete it to release virtual resources.A snapshot can be deleted only when it is in the available or error state.Query the s", + "product_code":"evs", + "title":"Deleting an EVS Snapshot", + "uri":"evs_03_0007.html", + "doc_type":"devg", + "p_code":"", + "code":"7" + }, + { + "desc":"If the data in an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source EVS disk to restore the data.When you roll back a snapshot to", + "product_code":"evs", + "title":"Rolling Back a Snapshot to an EVS Disk", + "uri":"evs_03_0008.html", + "doc_type":"devg", + "p_code":"", + "code":"8" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Change History", + "uri":"evs_03_0010.html", + "doc_type":"devg", + "p_code":"", + "code":"9" + } +] \ No newline at end of file diff --git a/docs/evs/dev/PARAMETERS.txt b/docs/evs/dev/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/evs/dev/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/evs/dev/evs_03_0001.html b/docs/evs/dev/evs_03_0001.html new file mode 100644 index 000000000..e33ca9331 --- /dev/null +++ b/docs/evs/dev/evs_03_0001.html @@ -0,0 +1,18 @@ + + +

Overview

+

This document describes how to call the Elastic Volume Service (EVS) APIs to use various EVS functions.

+

This chapter describes the concepts related to EVS to help you quickly understand the service.

+

Elastic Volume Service

EVS offers scalable block storage for servers. With high reliability, high performance, and rich specifications, EVS disks can be used for distributed file systems, development and test environments, data warehouse applications, and high-performance computing (HPC) scenarios to meet diverse service requirements.

+

EVS disks are also referred to as disks in this document.

+
+

Basic Concepts

  • AZ

    An availability zone (AZ) is a physical location where resources use independent power supply and networks within a region. An AZ is insulated from failures in other AZs and provides inexpensive, low-latency network connectivity to other AZs in the same regions. A region can have more than one AZ. AZs are physically isolated but interconnected through an internal network.

    +
  • Project

    A project is used to group and isolate OpenStack resources, such as computing, storage, and network resources. A project can either be a department or a project team. You can access the Identity and Access Management (IAM) service with a security administrator to create projects in a region and perform isolated management of resources.

    +
  • Image

    An image must contain an OS and can also contain application software (such as database software) and software configuration.

    +

    Images can be public or private. Public images are provided by the system by default, and private images are manually created by users. You can create system disks using a public or private image.

    +
  • EVS snapshot

    An EVS snapshot is a complete copy or image of the disk data at a specific time point. As a major disaster recovery (DR) approach, you can use a snapshot to completely restore the data to the time point when the snapshot was created.

    +
  • EVS disk backup

    The EVS implements the backup function through Cloud Backup and Recovery (CBR). CBR allows you to create backups for EVS disks on the management console without stopping the servers. When data loss or data damage occurred due to virus invasion, misoperations, or software and hardware faults, you can use backups to restore the data, maximizing your data correctness and security.

    +
+
+
+ diff --git a/docs/evs/dev/evs_03_0002.html b/docs/evs/dev/evs_03_0002.html new file mode 100644 index 000000000..b3baebe89 --- /dev/null +++ b/docs/evs/dev/evs_03_0002.html @@ -0,0 +1,7 @@ + + +

Before You Start

+

You need to learn how to call the EVS APIs before you start. For details about how to call RESTful APIs, see API Usage Guidelines.

+
+
+ diff --git a/docs/evs/dev/evs_03_0003.html b/docs/evs/dev/evs_03_0003.html new file mode 100644 index 000000000..99d2678ed --- /dev/null +++ b/docs/evs/dev/evs_03_0003.html @@ -0,0 +1,262 @@ + + +

Creating EVS Disks

+

Scenarios

This API is used to create one or multiple EVS disks.

+
+

Constraints

None

+
+

Involved APIs

Query the AZs before you create EVS disks.

+

If you need to create system disks, query the image information and obtain the image ID.

+

If you need to create the disk from a data source, for example a snapshot or backup, query the snapshot or backup information and obtain the snapshot ID or backup ID.

+

Obtain the required information and then create the disk.

+

To meet the preceding requirements, call the following APIs:

+
+
  • Query AZs.
  • Query images.
  • Query EVS snapshots.
  • Query backups.
  • Create EVS disks.
+

Procedure

  1. Query the AZs.
    • API information

      URI format: GET /v3/{project_id}/os-availability-zone

      +

      For details, see OpenStack Cinder API v3 > EVS Disk > Querying Information About All AZs in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/9c53a566cb3443ab910cf0daebca90c4/os-availability-zone

      +
    • Example response
       {
+    "availabilityZoneInfo": [
+        {
+            "zoneState": {
+                "available": true
+            }, 
+            "zoneName": "az1.dc1"
+        }, 
+        {
+            "zoneState": {
+                "available": true
+            }, 
+            "zoneName": "vmware.az1"
+        }
+    ]
+}
      +
    +
  2. (Optional) Query the images if system disks are going to be created.
    • API information

      URI format: GET /v2/images

      +

      For details, see API > Image (Native OpenStack APIs) > Querying Images (Native OpenStack API) in the Image Management Service API Reference.

      +
    • Example request

      GET /v2/images

      +
    • Example response
      {
+    "images": [
+        {
+            "status": "queued", 
+            "name": "test", 
+            "tags": [
+                "test", 
+                "image"
+            ], 
+            "container_format": "bare", 
+            "created_at": "2014-12-16T01:22:05Z", 
+            "disk_format": "qcow2", 
+            "updated_at": "2014-12-16T01:22:05Z", 
+            "visibility": "private", 
+            "self": "/v2/images/4ca46bf1-5c61-48ff-b4f3-0ad4e5e3ba90", 
+            "min_disk": 1, 
+            "protected": false, 
+            "id": "4ca46bf1-5c61-48ff-b4f3-0ad4e5e3ba90", 
+            "file": "/v2/images/4ca46bf1-5c61-48ff-b4f3-0ad4e5e3ba90/file", 
+            "owner": "aed2c611711548a4a9c16fb8fe166af4", 
+            "min_ram": 1024, 
+            "schema": "/v2/schemas/image"
+        }, 
+        {
+            "status": "active", 
+            "name": "cirros", 
+            "tags": [
+                "new"
+            ], 
+            "container_format": "bare", 
+            "created_at": "2014-12-11T03:53:43Z", 
+            "size": 13147648, 
+            "disk_format": "qcow2", 
+            "updated_at": "2014-12-15T20:02:12Z", 
+            "visibility": "private", 
+            "self": "/v2/images/5155a22a-834e-4ffe-a95d-ed9665a8ed76", 
+            "min_disk": 0, 
+            "protected": false, 
+            "id": "5155a22a-834e-4ffe-a95d-ed9665a8ed76", 
+            "file": "/v2/images/5155a22a-834e-4ffe-a95d-ed9665a8ed76/file", 
+            "checksum": "d972013792949d0d3ba628fbe8685bce", 
+            "owner": "aed2c611711548a4a9c16fb8fe166af4", 
+            "min_ram": 0, 
+            "schema": "/v2/schemas/image"
+        }
+    ], 
+    "schema": "/v2/schemas/images", 
+    "first": "/v2/images"
+}
      +
    +
  3. (Optional) Query the EVS snapshots if the disk is going to be created from a snapshot.
    • API information

      URI format: GET /v3/{project_id}/snapshots

      +

      For details, see OpenStack Cinder API v3 > EVS Snapshot > Querying EVS Snapshots in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/9c53a566cb3443ab910cf0daebca90c4/snapshots

      +
    • Example response
      {
+    "snapshots": [
+        {
+            "created_at": "2016-02-16T16:54:14.981520", 
+            "description": null, 
+            "id": "b836dc3d-4e10-4ea4-a34c-8f6b0460a583", 
+            "metadata": { }, 
+            "name": "test01", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:19.475397", 
+            "description": null, 
+            "id": "83be494d-329e-4a78-8ac5-9af900f48b95", 
+            "metadata": { }, 
+            "name": "test02", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:24.367414", 
+            "description": null, 
+            "id": "dd360f46-7593-4d35-8f2c-5566fd0bd79e", 
+            "metadata": { }, 
+            "name": "test03", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:29.766740", 
+            "description": null, 
+            "id": "4c29796a-8cf4-4482-9afc-e66da9a81240", 
+            "metadata": { }, 
+            "name": "test04", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }
+    ], 
+    "snapshots_links": null
+}
      +
    +
  4. (Optional) Query the backups if the disk is going to be created from a backup.
    • API information

      URI format: GET /v3/{project_id}/backups

      +

      For details, see CBR APIs > Backups > Querying All Backups in the Cloud Backup and Recovery API Reference.

      +
    • Example request

      GET /v2/9c53a566cb3443ab910cf0daebca90c4/backups

      +
    • Example response
      {
+    "backups": [
+        {
+            "id": "1d1139d8-8989-49d3-8aa1-83eb691e6db2", 
+            "links": [
+                {
+                    "href": "http://192.168.82.222:8776/v2/b23b579f08c84228b9b4673c46f0c442/backups/1d1139d8-8989-49d3-8aa1-83eb691e6db2", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "http://192.168.82.222:8776/b23b579f08c84228b9b4673c46f0c442/backups/1d1139d8-8989-49d3-8aa1-83eb691e6db2", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": null
+        }, 
+        {
+            "id": "b3cf7a16-decc-4beb-8077-682737d94a58", 
+            "links": [
+                {
+                    "href": "http://192.168.82.222:8776/v2/b23b579f08c84228b9b4673c46f0c442/backups/b3cf7a16-decc-4beb-8077-682737d94a58", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "http://192.168.82.222:8776/b23b579f08c84228b9b4673c46f0c442/backups/b3cf7a16-decc-4beb-8077-682737d94a58", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": null
+        }
+    ], 
+    "backups_links": [
+        {
+            "href": "http://192.168.82.222:8776/b23b579f08c84228b9b4673c46f0c442/backups?limit=1&offset=1&marker=b3cf7a16-decc-4beb-8077-682737d94a58", 
+            "rel": "next"
+        }
+    ]
+}
      +
    +
  5. Create EVS disks.
    • API information

      URI format: POST /v3/{project_id}/volumes

      +

      For details, see OpenStack Cinder API v3 > EVS Disk > Creating EVS Disks in the Elastic Volume Service API Reference.

      +
    • Example request

      POST /v3/9c53a566cb3443ab910cf0daebca90c4/volumes

      +
      {
+    "volume": {
+        "name": "openapi_vol01", 
+        "imageRef": "027cf713-45a6-45f0-ac1b-0ccc57ac12e2", 
+        "availability_zone": "xxx", 
+        "description": "create for api test", 
+        "volume_type": "SATA", 
+        "metadata": {
+            "volume_owner": "openapi"
+        }, 
+        "consistencygroup_id": null, 
+        "OS-SCH-HNT:scheduler_hints": {
+            "dedicated_storage_id": "eddc1a3e-4145-45be-98d7-bf6f65af9767"
+        }, 
+        "source_volid": null, 
+        "snapshot_id": null, 
+        "shareable": "false", 
+        "multiattach": false, 
+        "source_replica": null, 
+        "size": 40
+    }
+}
      +
    • Example response
      {
+    "volume": {
+        "attachments": [ ], 
+        "availability_zone": "xxx", 
+        "bootable": "false", 
+        "consistencygroup_id": null, 
+        "created_at": "2016-05-25T02:38:40.392463", 
+        "description": "create for api test", 
+        "encrypted": false, 
+        "id": "8dd7c486-8e9f-49fe-bceb-26aa7e312b66", 
+        "links": [
+            {
+                "href": "https://volume.localdomain.com:8776/v2/5dd0b0056f3d47b6ab4121667d35621a/volumes/8dd7c486-8e9f-49fe-bceb-26aa7e312b66", 
+                "rel": "self"
+            }, 
+            {
+                "href": "https://volume.localdomain.com:8776/5dd0b0056f3d47b6ab4121667d35621a/volumes/8dd7c486-8e9f-49fe-bceb-26aa7e312b66", 
+                "rel": "bookmark"
+            }
+        ], 
+        "metadata": {
+            "volume_owner": "openapi"
+        }, 
+        "name": "openapi_vol01", 
+        "replication_status": "disabled", 
+        "shareable": false, 
+        "multiattach": false, 
+        "size": 40, 
+        "snapshot_id": null, 
+        "source_volid": null, 
+        "status": "creating", 
+        "updated_at": null, 
+        "user_id": "39f6696ae23740708d0f358a253c2637", 
+        "volume_type": "SATA"
+    }
+}
      +
      or
      {
+    "error": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
      In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:
      {
+    "badRequest": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
    +
+
+
+ diff --git a/docs/evs/dev/evs_03_0004.html b/docs/evs/dev/evs_03_0004.html new file mode 100644 index 000000000..a6ca1eea6 --- /dev/null +++ b/docs/evs/dev/evs_03_0004.html @@ -0,0 +1,97 @@ + + +

Expanding the Capacity of an EVS Disk

+

Scenarios

For an EVS disk that has been created, you can call this API to expand the disk capacity if the disk space is insufficient.

+
+

Constraints

  • If the status of the to-be-expanded disk is available, there are no restrictions.
  • If the status of the to-be-expanded disk is in-use, the restrictions are as follows:
    • A shared disk cannot be expanded, that is, the value of parameter multiattach must be false.
    • The status of the server to which the disk attached must be ACTIVE, PAUSED, SUSPENDED, or SHUTOFF.
    +
+
+

Involved APIs

Query the disk list, obtain the ID of the target disk, and then expand the disk capacity.

+

To meet the preceding requirements, call the following APIs:

+
+
  • Query EVS disks.
  • Expand the capacity of a disk.
+

Procedure

  1. Query EVS disks.
    • API information

      URI format: GET /v3/{project_id}/volumes

      +

      For details, see OpenStack Cinder API v3 > EVS Disk > Querying EVS Disks in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/000efdc5f9064584b718b181df137bd7/volumes

      +
    • Example response
      {
+    "volumes": [
+        {
+            "id": "6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }, 
+        {
+            "id": "2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }, 
+        {
+            "id": "3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }
+    ], 
+    "volumes_links": [
+        {
+            "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes?limit=3&marker=3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+            "rel": "next"
+        }
+    ]
+}
      +
    +
  2. Expand the capacity of an EVS disk.
    • API information

      URI format: POST /v3/{project_id}/volumes/{volume_id}/action

      +

      For details, see OpenStack Cinder API v3 > EVS Disk Actions > Expanding the Capacity of an EVS Disk in the Elastic Volume Service API Reference.

      +
    • Example request

      POST /v3/000efdc5f9064584b718b181df137bd7/ volumes/9ab74d89-61e7-4259-8546-465fdebe4944/ action

      +
      {
+    "os-extend": {
+        "new_size": 100
+    }
+}
      +
    • Example response

      None

      +
      or
      {
+    "error": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
      In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:
      {
+    "badRequest": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
    +
+
+
+
+ diff --git a/docs/evs/dev/evs_03_0005.html b/docs/evs/dev/evs_03_0005.html new file mode 100644 index 000000000..6b725f4b5 --- /dev/null +++ b/docs/evs/dev/evs_03_0005.html @@ -0,0 +1,94 @@ + + +

Deleting an EVS Disk

+

Scenarios

If an EVS disk is no longer used, you can delete it to release virtual resources.

+
+

Constraints

  • An EVS disk can be deleted only when its status is available, error, error_extending, error_restoring, or error_rollbacking.
  • Before deleting a shared EVS disk, ensure that the disk has been detached from all its servers.
+
  • When you delete an EVS disk, all the disk data including the snapshots created for this disk will be deleted. Exercise caution when performing this operation.
  • Deleted EVS disks cannot be recovered. Exercise caution when performing this operation.
+
+
+

Involved APIs

Query the disk list, obtain the ID of the target disk, and then delete the disk.

+

To meet the preceding requirements, call the following APIs:

+
+
  • Query EVS disks.
  • Delete an EVS disk.
+

Procedure

  1. Query EVS disks.
    • API information

      URI format: GET /v3/{project_id}/volumes

      +

      For details, see OpenStack Cinder API v3 > EVS Disk > Querying EVS Disks in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/000efdc5f9064584b718b181df137bd7/volumes

      +
    • Example response
      {
+    "volumes": [
+        {
+            "id": "6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }, 
+        {
+            "id": "2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }, 
+        {
+            "id": "3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }
+    ], 
+    "volumes_links": [
+        {
+            "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes?limit=3&marker=3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+            "rel": "next"
+        }
+    ]
+}
      +
    +
  2. Delete the disk.
    • API information

      URI format: DELETE /v3/{project_id}/volumes/{volume_id}

      +

      For details, see OpenStack Cinder API v3 > EVS Disk > Deleting an EVS Disk in the Elastic Volume Service API Reference.

      +
    • Example request

      DELETE /v3/000efdc5f9064584b718b181df137bd7/baremetalservers/5850a7e7-88dd-4d99-8439-347de8cc0dd7/volume/50ef9435-ca68-4b9b-a837-73377b9fdaa3?cascade=true

      +

      cascade=true indicates that the snapshots created for the disk will also be deleted.

      +
      +
    • Example response

      None

      +
      or
      {
+    "error": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
      In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:
      {
+    "badRequest": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
    +
+
+
+ diff --git a/docs/evs/dev/evs_03_0006.html b/docs/evs/dev/evs_03_0006.html new file mode 100644 index 000000000..b10850c0d --- /dev/null +++ b/docs/evs/dev/evs_03_0006.html @@ -0,0 +1,112 @@ + + +

Creating an EVS Snapshot

+

Scenarios

You can create an EVS snapshot on the management console to save the disk data at a specific time point.

+
+

Constraints

A maximum of 7 snapshots can be created for an EVS disk.

+
+

Involved APIs

Query the disk list, obtain the ID of the target disk, and then create the snapshot.

+

To meet the preceding requirements, call the following APIs:

+
+
  • Query EVS disks.
  • Create an EVS snapshot.
+

Procedure

  1. Query EVS disks.
    • API information

      URI format: GET /v3/{project_id}/volumes

      +

      For details, see OpenStack Cinder API v3 > EVS Disk > Querying EVS Disks in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/000efdc5f9064584b718b181df137bd7/volumes

      +
    • Example response
      {
+    "volumes": [
+        {
+            "id": "6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/6b604cef-9bd8-4f5a-ae56-45839e6e1f0a", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }, 
+        {
+            "id": "2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/2bce4552-9a7d-48fa-8484-abbbf64b206e", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }, 
+        {
+            "id": "3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+            "links": [
+                {
+                    "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes/3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+                    "rel": "self"
+                }, 
+                {
+                    "href": "https://volume.localdomain.com:8776/dd14c6ac581f40059e27f5320b60bf2f/volumes/3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+                    "rel": "bookmark"
+                }
+            ], 
+            "name": "zjb_u25_test"
+        }
+    ], 
+    "volumes_links": [
+        {
+            "href": "https://volume.localdomain.com:8776/v2/dd14c6ac581f40059e27f5320b60bf2f/volumes?limit=3&marker=3f1b98ec-a8b5-4e92-a727-88def62d5ad3", 
+            "rel": "next"
+        }
+    ]
+}
      +
    +
  2. Create the snapshot.
    • API information

      URI format: POST /v3/{project_id}/snapshots

      +

      For details, see OpenStack Cinder API v3 > EVS Snapshot > Creating an EVS Snapshot in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/000efdc5f9064584b718b181df137bd7/snapshots

      +
      {
+    "snapshot": {
+        "name": "snap-001", 
+        "description": "Daily backup", 
+        "volume_id": "5aa119a8-d25b-45a7-8d1b-88e127885635", 
+        "force": false, 
+        "metadata": { }
+    }
+}
      +
    • Example response
      {
+    "snapshot": {
+        "status": "creating", 
+        "description": "Daily backup", 
+        "created_at": "2013-02-25T03:56:53.081642", 
+        "metadata": { }, 
+        "volume_id": "5aa119a8-d25b-45a7-8d1b-88e127885635", 
+        "size": 1, 
+        "id": "ffa9bc5e-1172-4021-acaf-cdcd78a9584d", 
+        "name": "snap-001", 
+        "updated_at": "2013-02-25T03:56:53.081642"
+    }
+}
      +
      or
      {
+    "error": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
      In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:
      {
+    "badRequest": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
    +
+
+
+
+ diff --git a/docs/evs/dev/evs_03_0007.html b/docs/evs/dev/evs_03_0007.html new file mode 100644 index 000000000..a090b99fc --- /dev/null +++ b/docs/evs/dev/evs_03_0007.html @@ -0,0 +1,87 @@ + + +

Deleting an EVS Snapshot

+

Scenarios

If an EVS snapshot is no longer used, you can delete it to release virtual resources.

+
+

Constraints

  • A snapshot can be deleted only when it is in the available or error state.
+
+

Involved APIs

Query the snapshot list, obtain the ID of the target snapshot, and then delete the snapshot.

+

To meet the preceding requirements, call the following APIs:

+
  • Query EVS snapshots.
  • Delete an EVS snapshot.
+
+

Procedure

  1. Query the EVS snapshots.
    • API information

      URI format: GET /v3/{project_id}/snapshots

      +

      For details, see OpenStack Cinder API v3 > EVS Snapshot > Querying EVS Snapshots in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/000efdc5f9064584b718b181df137bd7/snapshots

      +
    • Example response
      {
+    "snapshots": [
+        {
+            "created_at": "2016-02-16T16:54:14.981520", 
+            "description": null, 
+            "id": "b836dc3d-4e10-4ea4-a34c-8f6b0460a583", 
+            "metadata": { }, 
+            "name": "test01", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:19.475397", 
+            "description": null, 
+            "id": "83be494d-329e-4a78-8ac5-9af900f48b95", 
+            "metadata": { }, 
+            "name": "test02", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:24.367414", 
+            "description": null, 
+            "id": "dd360f46-7593-4d35-8f2c-5566fd0bd79e", 
+            "metadata": { }, 
+            "name": "test03", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:29.766740", 
+            "description": null, 
+            "id": "4c29796a-8cf4-4482-9afc-e66da9a81240", 
+            "metadata": { }, 
+            "name": "test04", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }
+    ], 
+    "snapshots_links": null
+}
      +
    +
  2. Delete the snapshot.
    • API information

      URI format: DELETE /v3/{project_id}/snapshots/{snapshot_id}

      +

      For details, see OpenStack Cinder API v3 > EVS Snapshot > Deleting an EVS Snapshot in the Elastic Volume Service API Reference.

      +
    • Example request

      DELETE /v3/000efdc5f9064584b718b181df137bd7/snapshots/b836dc3d-4e10-4ea4-a34c-8f6b0460a583

      +
    • Example response

      None

      +
      or
      {
+    "error": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
      In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:
      {
+    "badRequest": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
    +
+
+
+ diff --git a/docs/evs/dev/evs_03_0008.html b/docs/evs/dev/evs_03_0008.html new file mode 100644 index 000000000..802039dd7 --- /dev/null +++ b/docs/evs/dev/evs_03_0008.html @@ -0,0 +1,98 @@ + + +

Rolling Back a Snapshot to an EVS Disk

+

Scenarios

If the data in an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source EVS disk to restore the data.

+
+

Constraints

  • When you roll back a snapshot to a disk, you can only roll back the snapshot to the source disk. Rollback to a specified disk is not supported.
  • You can roll back a disk from a snapshot only when the disk is in the available or error_rollbacking state.
  • Snapshots whose names started with prefix autobk_snapshot_ are automatically created by the system during backup creations. Do not use these snapshots to roll back the disk data.
+
+

Involved APIs

Query the snapshot list, obtain the ID of the snapshot and the ID of the snapshot's source disk, and then roll back the snapshot to the source disk.

+

To meet the preceding requirements, call the following APIs:

+
  • Query EVS snapshots.
  • Roll back a snapshot to an EVS disk.
+
+

Procedure

  1. Query the EVS snapshots.
    • API information

      URI format: GET /v3/{project_id}/snapshots

      +

      For details, see OpenStack Cinder API v3 > EVS Snapshot > Querying EVS Snapshots in the Elastic Volume Service API Reference.

      +
    • Example request

      GET /v3/000efdc5f9064584b718b181df137bd7/snapshots

      +
    • Example response
      {
+    "snapshots": [
+        {
+            "created_at": "2016-02-16T16:54:14.981520", 
+            "description": null, 
+            "id": "b836dc3d-4e10-4ea4-a34c-8f6b0460a583", 
+            "metadata": { }, 
+            "name": "test01", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:19.475397", 
+            "description": null, 
+            "id": "83be494d-329e-4a78-8ac5-9af900f48b95", 
+            "metadata": { }, 
+            "name": "test02", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:24.367414", 
+            "description": null, 
+            "id": "dd360f46-7593-4d35-8f2c-5566fd0bd79e", 
+            "metadata": { }, 
+            "name": "test03", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }, 
+        {
+            "created_at": "2016-02-16T16:54:29.766740", 
+            "description": null, 
+            "id": "4c29796a-8cf4-4482-9afc-e66da9a81240", 
+            "metadata": { }, 
+            "name": "test04", 
+            "size": 1, 
+            "status": "available", 
+            "volume_id": "ba5730ea-8621-4ae8-b702-ff0ffc12c209", 
+            "updated_at": null
+        }
+    ], 
+    "snapshots_links": null
+}
      +
    +
  2. Roll back the snapshot to the source disk.
    • API information

      URI format: POST /v3/{project_id}/os-vendor-snapshots/{snapshot_id}/rollback

      +

      For details, see API v3 > EVS Snapshot > Rolling Back a Snapshot to an EVS Disk in the Elastic Volume Service API Reference.

      +
    • Example request

      POST /v3/000efdc5f9064584b718b181df137bd7/os-vendor-snapshots/b836dc3d-4e10-4ea4-a34c-8f6b0460a583 /rollback

      +
      {
+    "rollback": {
+        "name": "test-001", 
+        "volume_id": "5aa119a8-d25b-45a7-8d1b-88e127885635"
+    }
+}
      +
    • Example response
      {
+    "rollback": {
+        "volume_id": "5aa119a8-d25b-45a7-8d1b-88e127885635"
+    }
+}
      +
      or
      {
+    "error": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
      In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:
      {
+    "badRequest": {
+        "message": "XXXX", 
+        "code": "XXX"
+    }
+}
      +
      +
    +
+
+
+
+ diff --git a/docs/evs/dev/evs_03_0010.html b/docs/evs/dev/evs_03_0010.html new file mode 100644 index 000000000..d9ec214af --- /dev/null +++ b/docs/evs/dev/evs_03_0010.html @@ -0,0 +1,20 @@ + + +

Change History

+
+
+ + + + + + + +

Release On

+

What's New

+

2018-11-08

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/evs/dev/public_sys-resources/ExpandCollapse.js b/docs/evs/dev/public_sys-resources/ExpandCollapse.js new file mode 100644 index 000000000..116ddaabf --- /dev/null +++ b/docs/evs/dev/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file diff --git a/docs/evs/dev/public_sys-resources/avgCompile.js b/docs/evs/dev/public_sys-resources/avgCompile.js new file mode 100644 index 000000000..327822688 --- /dev/null +++ b/docs/evs/dev/public_sys-resources/avgCompile.js @@ -0,0 +1 @@ +var name1=null;function test1(a){a=a.parentNode;a.className="test1"}function test2(a){a=a.parentNode;a.className="test2"}function test3(a){a=a.parentNode;a.className="test3"}function test4(a){a=a.parentNode;a.className="test4"}function test5(a){a=a.parentNode;a.className="test5"}function test6(a){a=a.parentNode;a.className="test6"}function test7(a){a=a.parentNode;a.className="test7"}function test8(a){a=a.parentNode;a.className="test8"}function test9(a){a=a.parentNode;a.className="test9"}function test10(a){a=a.parentNode;a.className="test10"}function test11(a){a=a.parentNode;a.className="test11"}function test12(a){a=a.parentNode;a.className="test12"}function test13(a){a=a.parentNode;a.className="test13"}function test2(a){a=a.parentNode;a.className="test2"}function test14(a){a=a.parentNode;a.className="test14"}function test15(a){a=a.parentNode;a.className="test15"}function test16(a){a=a.parentNode;a.className="test16"}function test17(a){a=a.parentNode;a.className="test17"}function test18(a){a=a.parentNode;a.className="test18"}function test19(a){a=a.parentNode;a.className="test19"}function test20(a){a=a.parentNode;a.className="test20"}function test21(a){a=a.parentNode;a.className="test21"}function test22(a){a=a.parentNode;a.className="test22"}function test23(a){a=a.parentNode;a.className="test23"}; \ No newline at end of file diff --git a/docs/evs/dev/public_sys-resources/caution_3.0-en-us.png b/docs/evs/dev/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 000000000..60f607621 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/evs/dev/public_sys-resources/commonltr.css b/docs/evs/dev/public_sys-resources/commonltr.css new file mode 100644 index 000000000..c5480b0ab --- /dev/null +++ b/docs/evs/dev/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/evs/dev/public_sys-resources/commonltr_print.css b/docs/evs/dev/public_sys-resources/commonltr_print.css new file mode 100644 index 000000000..a59823141 --- /dev/null +++ b/docs/evs/dev/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/evs/dev/public_sys-resources/commonrtl.css b/docs/evs/dev/public_sys-resources/commonrtl.css new file mode 100644 index 000000000..f261da752 --- /dev/null +++ b/docs/evs/dev/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +/*! Copyright (c) Huawei Technologies Co., Ltd. 2020-2022. All rights reserved. */.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/evs/dev/public_sys-resources/danger_3.0-en-us.png b/docs/evs/dev/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 000000000..47a9c7235 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/evs/dev/public_sys-resources/delta.gif b/docs/evs/dev/public_sys-resources/delta.gif new file mode 100644 index 000000000..0d1b1f674 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/delta.gif differ diff --git a/docs/evs/dev/public_sys-resources/deltaend.gif b/docs/evs/dev/public_sys-resources/deltaend.gif new file mode 100644 index 000000000..cc7da0fc8 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/deltaend.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-arrowdn.gif b/docs/evs/dev/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 000000000..84eec9be2 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-arrowrt.gif b/docs/evs/dev/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 000000000..39583d168 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-caution.gif b/docs/evs/dev/public_sys-resources/icon-caution.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-caution.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-danger.gif b/docs/evs/dev/public_sys-resources/icon-danger.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-danger.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-huawei.gif b/docs/evs/dev/public_sys-resources/icon-huawei.gif new file mode 100644 index 000000000..a31d60f89 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-huawei.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-note.gif b/docs/evs/dev/public_sys-resources/icon-note.gif new file mode 100644 index 000000000..31be2b039 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-note.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-notice.gif b/docs/evs/dev/public_sys-resources/icon-notice.gif new file mode 100644 index 000000000..409070650 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-notice.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-tip.gif b/docs/evs/dev/public_sys-resources/icon-tip.gif new file mode 100644 index 000000000..c47bae05c Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-tip.gif differ diff --git a/docs/evs/dev/public_sys-resources/icon-warning.gif b/docs/evs/dev/public_sys-resources/icon-warning.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/icon-warning.gif differ diff --git a/docs/evs/dev/public_sys-resources/note_3.0-en-us.png b/docs/evs/dev/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 000000000..57a0e1f53 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/note_3.0-en-us.png differ diff --git a/docs/evs/dev/public_sys-resources/notice_3.0-en-us.png b/docs/evs/dev/public_sys-resources/notice_3.0-en-us.png new file mode 100644 index 000000000..fa4b64990 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/notice_3.0-en-us.png differ diff --git a/docs/evs/dev/public_sys-resources/popup.js b/docs/evs/dev/public_sys-resources/popup.js new file mode 100644 index 000000000..a550862ed --- /dev/null +++ b/docs/evs/dev/public_sys-resources/popup.js @@ -0,0 +1 @@ +var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/evs/dev/public_sys-resources/warning_3.0-en-us.png b/docs/evs/dev/public_sys-resources/warning_3.0-en-us.png new file mode 100644 index 000000000..def5c3565 Binary files /dev/null and b/docs/evs/dev/public_sys-resources/warning_3.0-en-us.png differ diff --git a/docs/evs/umn/.placeholder b/docs/evs/umn/.placeholder deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/evs/umn/ALL_META.TXT.json b/docs/evs/umn/ALL_META.TXT.json new file mode 100644 index 000000000..0fb3f8a68 --- /dev/null +++ b/docs/evs/umn/ALL_META.TXT.json @@ -0,0 +1,1062 @@ +[ + { + "uri":"evs_01_0119.html", + "product_code":"evs", + "code":"1", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Overview", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0014580741.html", + "product_code":"evs", + "code":"2", + "des":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and rich specifications, EVS disks can be used for ", + "doc_type":"usermanual", + "kw":"What Is EVS?,Overview,User Guide", + "title":"What Is EVS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0014580744.html", + "product_code":"evs", + "code":"3", + "des":"EVS disks are classified based on the disk I/O performance. EVS disks differ in performance and price. Choose the disk type most appropriate for your applications.Common ", + "doc_type":"usermanual", + "kw":"Disk Types and Performance,Overview,User Guide", + "title":"Disk Types and Performance", + "githuburl":"" + }, + { + "uri":"en-us_topic_0052554220.html", + "product_code":"evs", + "code":"4", + "des":"There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).VBD is the default EVS device type. VBD EVS disks support only basic", + "doc_type":"usermanual", + "kw":"Device Types and Usage Instructions,Overview,User Guide", + "title":"Device Types and Usage Instructions", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032860759.html", + "product_code":"evs", + "code":"5", + "des":"Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multiple servers. Shared EVS disks feature multiple attach", + "doc_type":"usermanual", + "kw":"Shared EVS Disks and Usage Instructions,Overview,User Guide", + "title":"Shared EVS Disks and Usage Instructions", + "githuburl":"" + }, + { + "uri":"evs_01_0001.html", + "product_code":"evs", + "code":"6", + "des":"In case your services require encryption for the data stored on EVS disks, EVS provides you with the encryption function. You can encrypt newly created EVS disks.EVS uses", + "doc_type":"usermanual", + "kw":"EVS Disk Encryption,Overview,User Guide", + "title":"EVS Disk Encryption", + "githuburl":"" + }, + { + "uri":"evs_01_0021.html", + "product_code":"evs", + "code":"7", + "des":"Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while servers are running. If data loss or damage occurred d", + "doc_type":"usermanual", + "kw":"EVS Backup,Overview,User Guide", + "title":"EVS Backup", + "githuburl":"" + }, + { + "uri":"en-us_topic_0066809008.html", + "product_code":"evs", + "code":"8", + "des":"EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific ", + "doc_type":"usermanual", + "kw":"EVS Snapshot,Overview,User Guide", + "title":"EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0048.html", + "product_code":"evs", + "code":"9", + "des":"Both EVS disk backup and EVS snapshot provide redundancies for the EVS disk data to improve reliability. Table 1 lists the differences between them.", + "doc_type":"usermanual", + "kw":"Differences Between EVS Disk Backup and EVS Snapshot,Overview,User Guide", + "title":"Differences Between EVS Disk Backup and EVS Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0020.html", + "product_code":"evs", + "code":"10", + "des":"If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a p", + "doc_type":"usermanual", + "kw":"EVS Replication (Deprecated),Overview,User Guide", + "title":"EVS Replication (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0086.html", + "product_code":"evs", + "code":"11", + "des":"If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IA", + "doc_type":"usermanual", + "kw":"Permissions Management,Overview,User Guide", + "title":"Permissions Management", + "githuburl":"" + }, + { + "uri":"evs_01_0106.html", + "product_code":"evs", + "code":"12", + "des":"Figure 1 shows the relationships between EVS and other services.Relationships between EVS and other servicesECS: EVS disks can be attached to ECSs and used as scalable bl", + "doc_type":"usermanual", + "kw":"EVS and Other Services,Overview,User Guide", + "title":"EVS and Other Services", + "githuburl":"" + }, + { + "uri":"evs_01_0101.html", + "product_code":"evs", + "code":"13", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Basic Concepts", + "title":"Basic Concepts", + "githuburl":"" + }, + { + "uri":"evs_01_0097.html", + "product_code":"evs", + "code":"14", + "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "doc_type":"usermanual", + "kw":"Region and AZ,Basic Concepts,User Guide", + "title":"Region and AZ", + "githuburl":"" + }, + { + "uri":"evs_01_0120.html", + "product_code":"evs", + "code":"15", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started", + "title":"Getting Started", + "githuburl":"" + }, + { + "uri":"evs_01_0057.html", + "product_code":"evs", + "code":"16", + "des":"Figure 1 shows the basic EVS operation procedure.Basic operation procedure", + "doc_type":"usermanual", + "kw":"购买磁盘,购买块存储,购买数据盘,使用云硬盘,使用磁盘,挂载云硬盘,挂载磁盘,初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Basic Operation Procedure,Getting S", + "title":"Basic Operation Procedure", + "githuburl":"" + }, + { + "uri":"en-us_topic_0021738346.html", + "product_code":"evs", + "code":"17", + "des":"EVS disks can be used as system disks or data disks for servers.When a server is created, a system disk is automatically created and attached. You cannot create a system ", + "doc_type":"usermanual", + "kw":"购买磁盘,购买块存储,购买数据盘,Create an EVS Disk,Getting Started,User Guide", + "title":"Create an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0107.html", + "product_code":"evs", + "code":"18", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"挂载云硬盘,挂载磁盘", + "title":"Attach an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0036.html", + "product_code":"evs", + "code":"19", + "des":"Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this ", + "doc_type":"usermanual", + "kw":"挂载云硬盘,挂载磁盘,挂载非共享盘,挂载非共享磁盘,Attaching a Non-Shared Disk,Attach an EVS Disk,User Guide", + "title":"Attaching a Non-Shared Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0037.html", + "product_code":"evs", + "code":"20", + "des":"Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this ", + "doc_type":"usermanual", + "kw":"挂载云硬盘,挂载磁盘,挂载共享盘,挂载共享磁盘,Attaching a Shared Disk,Attach an EVS Disk,User Guide", + "title":"Attaching a Shared Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0058.html", + "product_code":"evs", + "code":"21", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘", + "title":"Initialize an EVS Data Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0038.html", + "product_code":"evs", + "code":"22", + "des":"After a disk is attached to a server, you need to log in to the server to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.Sy", + "doc_type":"usermanual", + "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,分区形式,GPT,MBR,更换分区形式,Introduction to Data Disk Initialization Scenarios and", + "title":"Introduction to Data Disk Initialization Scenarios and Partition Styles", + "githuburl":"" + }, + { + "uri":"evs_01_0108.html", + "product_code":"evs", + "code":"23", + "des":"This section uses Windows Server 2008 R2 Enterprise 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity support", + "doc_type":"usermanual", + "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Windows Data Disk (Windows Server 2008),Initialize an EVS D", + "title":"Initializing a Windows Data Disk (Windows Server 2008)", + "githuburl":"" + }, + { + "uri":"evs_01_0045.html", + "product_code":"evs", + "code":"24", + "des":"This section uses Windows Server 2016 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity supported by", + "doc_type":"usermanual", + "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Windows Data Disk (Windows Server 2016),Initialize an EVS D", + "title":"Initializing a Windows Data Disk (Windows Server 2016)", + "githuburl":"" + }, + { + "uri":"evs_01_0033.html", + "product_code":"evs", + "code":"25", + "des":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.The maximum disk ", + "doc_type":"usermanual", + "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Linux Data Disk (fdisk),Initialize an EVS Data Disk,User Gu", + "title":"Initializing a Linux Data Disk (fdisk)", + "githuburl":"" + }, + { + "uri":"evs_01_0034.html", + "product_code":"evs", + "code":"26", + "des":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.The maximum disk", + "doc_type":"usermanual", + "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Linux Data Disk (parted),Initialize an EVS Data Disk,User G", + "title":"Initializing a Linux Data Disk (parted)", + "githuburl":"" + }, + { + "uri":"evs_01_0087.html", + "product_code":"evs", + "code":"27", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Permissions Management", + "title":"Permissions Management", + "githuburl":"" + }, + { + "uri":"evs_01_0089.html", + "product_code":"evs", + "code":"28", + "des":"This chapter describes how to use IAM to implement fine-grained permissions control for your EVS resources. With IAM, you can:Create IAM users for employees based on your", + "doc_type":"usermanual", + "kw":"Creating a User and Granting EVS Permissions,Permissions Management,User Guide", + "title":"Creating a User and Granting EVS Permissions", + "githuburl":"" + }, + { + "uri":"evs_01_0090.html", + "product_code":"evs", + "code":"29", + "des":"Custom policies can be created to supplement the system-defined policies of EVS. For the actions supported for custom policies, see section \"Permissions Policies and Supp", + "doc_type":"usermanual", + "kw":"EVS Custom Policies,Permissions Management,User Guide", + "title":"EVS Custom Policies", + "githuburl":"" + }, + { + "uri":"evs_01_0059.html", + "product_code":"evs", + "code":"30", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足", + "title":"Disk Capacity Expansion", + "githuburl":"" + }, + { + "uri":"evs_01_0006.html", + "product_code":"evs", + "code":"31", + "des":"If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.Both system disks and data disks can be expanded. Curr", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容磁盘流程,磁盘扩容流程,在线扩容,不卸载磁盘扩容,离线扩容,卸载磁盘扩容,扩容数据盘,扩容系统盘,Expansion Overview,Disk ", + "title":"Expansion Overview", + "githuburl":"" + }, + { + "uri":"evs_01_0007.html", + "product_code":"evs", + "code":"32", + "des":"This section describes how to expand the capacity of an In-use EVS disk on the management console. The In-use status indicates that the disk has been attached to a server", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,在线扩容,不卸载磁盘扩容,扩容数据盘,扩容系统盘,Expanding Capacity for an In-use EVS Disk,Disk Cap", + "title":"Expanding Capacity for an In-use EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0008.html", + "product_code":"evs", + "code":"33", + "des":"This section describes how to expand the capacity of an Available EVS disk on the management console. The Available status indicates that the disk has not been attached t", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,离线扩容,卸载磁盘扩容,扩容数据盘,扩容系统盘,Expanding Capacity for an Available EVS Disk,Disk C", + "title":"Expanding Capacity for an Available EVS Disk", + "githuburl":"" + }, + { + "uri":"en-us_topic_0017616396.html", + "product_code":"evs", + "code":"34", + "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the ad", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容windows系统盘,扩容windows数据盘,Extending Disk Partitions and File Systems (Windo", + "title":"Extending Disk Partitions and File Systems (Windows Server 2008)", + "githuburl":"" + }, + { + "uri":"evs_01_0094.html", + "product_code":"evs", + "code":"35", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux数据盘,扩容linux系统盘", + "title":"Extending Disk Partitions and File Systems (Linux)", + "githuburl":"" + }, + { + "uri":"evs_01_0035.html", + "product_code":"evs", + "code":"36", + "des":"Before extending the disk partition and file system, you must check the disk partition style and file system format, and then select the appropriate operation accordingly", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux数据盘,扩容linux系统盘,Partition and File System Extension Preparations (Lin", + "title":"Partition and File System Extension Preparations (Linux)", + "githuburl":"" + }, + { + "uri":"evs_01_0072.html", + "product_code":"evs", + "code":"37", + "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux系统盘,Extending Partitions and File Systems for System Disks (Linux),E", + "title":"Extending Partitions and File Systems for System Disks (Linux)", + "githuburl":"" + }, + { + "uri":"evs_01_0109.html", + "product_code":"evs", + "code":"38", + "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux数据盘,Extending Partitions and File Systems for Data Disks (Linux),Ext", + "title":"Extending Partitions and File Systems for Data Disks (Linux)", + "githuburl":"" + }, + { + "uri":"evs_01_0018.html", + "product_code":"evs", + "code":"39", + "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", + "doc_type":"usermanual", + "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容SCSI磁盘,扩容SCSI数据盘,扩容SCSI云硬盘,扩容linux数据盘,Extending Partitions and File Syste", + "title":"Extending Partitions and File Systems for SCSI Disks (Linux)", + "githuburl":"" + }, + { + "uri":"evs_01_0002.html", + "product_code":"evs", + "code":"40", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"卸载磁盘", + "title":"Detaching an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0003.html", + "product_code":"evs", + "code":"41", + "des":"A system disk can only be detached offline, that is, its server must be in the Stopped state before the system disk is detached. Therefore, you need to first stop the ser", + "doc_type":"usermanual", + "kw":"卸载磁盘,离线卸载,Detaching a System Disk,Detaching an EVS Disk,User Guide", + "title":"Detaching a System Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0004.html", + "product_code":"evs", + "code":"42", + "des":"Data disks can be detached online or offline, which means that the server containing the to-be-detached data disk can either be in the Running or Stopped state.ECSDetach ", + "doc_type":"usermanual", + "kw":"卸载磁盘,在线卸载,离线卸载,Detaching a Data Disk,Detaching an EVS Disk,User Guide", + "title":"Detaching a Data Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0005.html", + "product_code":"evs", + "code":"43", + "des":"If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.Before deleting a disk, ensure that the disk status is Availa", + "doc_type":"usermanual", + "kw":"删除磁盘,Deleting an EVS Disk,User Guide", + "title":"Deleting an EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0009.html", + "product_code":"evs", + "code":"44", + "des":"The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:System disk encryption relates to the image tha", + "doc_type":"usermanual", + "kw":"Managing an Encrypted EVS Disk,User Guide", + "title":"Managing an Encrypted EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0010.html", + "product_code":"evs", + "code":"45", + "des":"You can create shared VBD disks or shared SCSI disks. It is recommended that you attach the shared disk to the ECSs in the same ECS group to improve service reliability.S", + "doc_type":"usermanual", + "kw":"Managing a Shared EVS Disk,User Guide", + "title":"Managing a Shared EVS Disk", + "githuburl":"" + }, + { + "uri":"evs_01_0110.html", + "product_code":"evs", + "code":"46", + "des":"EVS disk backups are created using the CBR service. For details, see Creating a Disk Backup Vault in the Cloud Backup and Recovery User Guide.This section describes how t", + "doc_type":"usermanual", + "kw":"Managing EVS Backup,User Guide", + "title":"Managing EVS Backup", + "githuburl":"" + }, + { + "uri":"evs_01_0111.html", + "product_code":"evs", + "code":"47", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Snapshots", + "title":"Managing Snapshots", + "githuburl":"" + }, + { + "uri":"evs_01_0098.html", + "product_code":"evs", + "code":"48", + "des":"EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific ", + "doc_type":"usermanual", + "kw":"Snapshot Overview,Managing Snapshots,User Guide", + "title":"Snapshot Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0066615262.html", + "product_code":"evs", + "code":"49", + "des":"You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.A maximum of 7 snapshots can be created for one disk.Snapshots", + "doc_type":"usermanual", + "kw":"Creating a Snapshot,Managing Snapshots,User Guide", + "title":"Creating a Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0011.html", + "product_code":"evs", + "code":"50", + "des":"If a snapshot is no longer needed, you can delete the snapshot to release the virtual resources. Snapshot deletion has the following constraints:The snapshot status must ", + "doc_type":"usermanual", + "kw":"Deleting a Snapshot,Managing Snapshots,User Guide", + "title":"Deleting a Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0012.html", + "product_code":"evs", + "code":"51", + "des":"If the data on an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source disk to restore data. Snapshot rollback has the following con", + "doc_type":"usermanual", + "kw":"Rolling Back Data from a Snapshot,Managing Snapshots,User Guide", + "title":"Rolling Back Data from a Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0013.html", + "product_code":"evs", + "code":"52", + "des":"This section describes how to create an EVS disk on the Snapshots page. Besides, you can also create an EVS disk from a snapshot by specifying the Create from snapshot pa", + "doc_type":"usermanual", + "kw":"Creating an EVS Disk from a Snapshot,Managing Snapshots,User Guide", + "title":"Creating an EVS Disk from a Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0023.html", + "product_code":"evs", + "code":"53", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing EVS Replication (Deprecated)", + "title":"Managing EVS Replication (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0060.html", + "product_code":"evs", + "code":"54", + "des":"For the EVS replication concepts, see EVS Replication (Deprecated). This chapter describes the basic functions and operations of EVS replication. Figure 1 shows the opera", + "doc_type":"usermanual", + "kw":"EVS Replication Operation Procedure (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"EVS Replication Operation Procedure (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0024.html", + "product_code":"evs", + "code":"55", + "des":"Before you create an EVS replication pair, create a DR ECS in the secondary AZ for the production ECS. The DR ECS parameters must be consistent with those of the producti", + "doc_type":"usermanual", + "kw":"Creating a DR ECS (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"Creating a DR ECS (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0026.html", + "product_code":"evs", + "code":"56", + "des":"Before you use EVS replication, bind a virtual IP address to the production server and DR server, respectively. Then configure the virtual IP address as the static IP add", + "doc_type":"usermanual", + "kw":"Configuring a Virtual IP Address for the Server (Deprecated),Managing EVS Replication (Deprecated),U", + "title":"Configuring a Virtual IP Address for the Server (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0025.html", + "product_code":"evs", + "code":"57", + "des":"This section is used to guide users to collect the production ECS and DR ECS information, including the ECS IDs and the IDs of the EVS disks attached the ECSs.Two EVS dis", + "doc_type":"usermanual", + "kw":"Collecting ECS Information (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"Collecting ECS Information (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0027.html", + "product_code":"evs", + "code":"58", + "des":"Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see EVS Replication Pair in the", + "doc_type":"usermanual", + "kw":"Creating an EVS Replication Pair (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"Creating an EVS Replication Pair (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0028.html", + "product_code":"evs", + "code":"59", + "des":"Currently, users need to make API calls to create replication consistency groups and add EVS replication pairs to the groups. For details, see Replication Consistency Gro", + "doc_type":"usermanual", + "kw":"Creating a Replication Consistency Group (Deprecated),Managing EVS Replication (Deprecated),User Gui", + "title":"Creating a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0029.html", + "product_code":"evs", + "code":"60", + "des":"Currently, EVS replication pairs can be added to or removed from replication consistency groups through APIs only. For details, see Updating a Replication Consistency Gro", + "doc_type":"usermanual", + "kw":"Updating a Replication Consistency Group (Deprecated),Managing EVS Replication (Deprecated),User Gui", + "title":"Updating a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0030.html", + "product_code":"evs", + "code":"61", + "des":"Production servers and production disks belong to the primary AZ, and DR servers and DR disks belong to the secondary AZ. Users can make API calls to perform a planned mi", + "doc_type":"usermanual", + "kw":"Planned Migration (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"Planned Migration (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0031.html", + "product_code":"evs", + "code":"62", + "des":"When the production servers and disks in the primary AZ become faulty due to force majeure, users can make API calls to perform a failover for the replication consistency", + "doc_type":"usermanual", + "kw":"Failover (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"Failover (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0032.html", + "product_code":"evs", + "code":"63", + "des":"When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide s", + "doc_type":"usermanual", + "kw":"Reprotection (Deprecated),Managing EVS Replication (Deprecated),User Guide", + "title":"Reprotection (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0043.html", + "product_code":"evs", + "code":"64", + "des":"Users can make an API call to expand the EVS disks in one or multiple EVS replication pairs of a replication consistency group. In such an expansion operation, two EVS di", + "doc_type":"usermanual", + "kw":"Expanding EVS Disks in a Replication Consistency Group (Deprecated),Managing EVS Replication (Deprec", + "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0042.html", + "product_code":"evs", + "code":"65", + "des":"Through EVS disk transfer, EVS disks can be transferred from one account to another. After the transfer succeeds, the ownerships of the EVS disks belong to the target acc", + "doc_type":"usermanual", + "kw":"Managing EVS Disk Transfer,User Guide", + "title":"Managing EVS Disk Transfer", + "githuburl":"" + }, + { + "uri":"evs_01_0112.html", + "product_code":"evs", + "code":"66", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing a Tag", + "title":"Managing a Tag", + "githuburl":"" + }, + { + "uri":"evs_01_0099.html", + "product_code":"evs", + "code":"67", + "des":"Tags identify EVS resources for purposes of easy categorization and quick search.", + "doc_type":"usermanual", + "kw":"Tag Overview,Managing a Tag,User Guide", + "title":"Tag Overview", + "githuburl":"" + }, + { + "uri":"evs_01_0014.html", + "product_code":"evs", + "code":"68", + "des":"This section is used to guide users to add a tag for an existing EVS disk. You can also add tags during the EVS disk creation. For details, see Create an EVS Disk.Tags ar", + "doc_type":"usermanual", + "kw":"Adding a Tag,Managing a Tag,User Guide", + "title":"Adding a Tag", + "githuburl":"" + }, + { + "uri":"evs_01_0015.html", + "product_code":"evs", + "code":"69", + "des":"You can change the value of a tag for an existing disk, but cannot change the key of a tag.The disk list page is displayed.The disk details page is displayed.The Edit Tag", + "doc_type":"usermanual", + "kw":"Modifying a Tag,Managing a Tag,User Guide", + "title":"Modifying a Tag", + "githuburl":"" + }, + { + "uri":"evs_01_0016.html", + "product_code":"evs", + "code":"70", + "des":"If an existing tag is no longer needed, you can delete it.The disk list page is displayed.The disk details page is displayed.The Delete Tag page is displayed.Return to th", + "doc_type":"usermanual", + "kw":"Deleting a Tag,Managing a Tag,User Guide", + "title":"Deleting a Tag", + "githuburl":"" + }, + { + "uri":"evs_01_0019.html", + "product_code":"evs", + "code":"71", + "des":"Tags can be used to categorize EVS disks, and users can quickly search for their desired EVS disks by tags. This section is used to guide users to search for EVS disk by ", + "doc_type":"usermanual", + "kw":"Searching Disks by Tags,Managing a Tag,User Guide", + "title":"Searching Disks by Tags", + "githuburl":"" + }, + { + "uri":"evs_01_0044.html", + "product_code":"evs", + "code":"72", + "des":"This section describes monitored metrics reported by EVS to Cloud Eye as well as their namespaces and dimensions. You can use console or APIs provided by Cloud Eye to que", + "doc_type":"usermanual", + "kw":"Viewing EVS Monitoring Data,User Guide", + "title":"Viewing EVS Monitoring Data", + "githuburl":"" + }, + { + "uri":"evs_faq_0001.html", + "product_code":"evs", + "code":"73", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"FAQ", + "title":"FAQ", + "githuburl":"" + }, + { + "uri":"evs_01_0081.html", + "product_code":"evs", + "code":"74", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"General", + "title":"General", + "githuburl":"" + }, + { + "uri":"evs_faq_0054.html", + "product_code":"evs", + "code":"75", + "des":"No.EVS disks must be attached to servers before you can use them.", + "doc_type":"usermanual", + "kw":"Can EVS Disks Be Used Alone?,General,User Guide", + "title":"Can EVS Disks Be Used Alone?", + "githuburl":"" + }, + { + "uri":"evs_faq_0048.html", + "product_code":"evs", + "code":"76", + "des":"No.The AZ of a disk cannot be changed after you have created the disk. If you want to change the AZ, delete the disk and create a new one.", + "doc_type":"usermanual", + "kw":"Can I Change the AZ of My Disk?,General,User Guide", + "title":"Can I Change the AZ of My Disk?", + "githuburl":"" + }, + { + "uri":"evs_faq_0014.html", + "product_code":"evs", + "code":"77", + "des":"If an error occurs, the disk may show one of the states listed in the following table. Take the measures described in the table to handle the exceptions.", + "doc_type":"usermanual", + "kw":"What Should I Do If an Error Occurs on My EVS Disk?,General,User Guide", + "title":"What Should I Do If an Error Occurs on My EVS Disk?", + "githuburl":"" + }, + { + "uri":"evs_faq_0021.html", + "product_code":"evs", + "code":"78", + "des":"EVS disks have two device types: VBD and SCSI. WWNs are used as the unique identifiers for SCSI EVS disks, and VBD EVS disks do not have WWNs.You can view the WWN of a SC", + "doc_type":"usermanual", + "kw":"Why Do Some of My EVS Disks Not Have WWN Information?,General,User Guide", + "title":"Why Do Some of My EVS Disks Not Have WWN Information?", + "githuburl":"" + }, + { + "uri":"evs_faq_0020.html", + "product_code":"evs", + "code":"79", + "des":"If the system displays a message indicating insufficient quota during an EVS replication pair creation or a replication consistency group creation or update, contact the ", + "doc_type":"usermanual", + "kw":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated),General,User Guide", + "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", + "githuburl":"" + }, + { + "uri":"evs_01_0077.html", + "product_code":"evs", + "code":"80", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Capacity Expansion", + "title":"Capacity Expansion", + "githuburl":"" + }, + { + "uri":"evs_faq_0026.html", + "product_code":"evs", + "code":"81", + "des":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", + "doc_type":"usermanual", + "kw":"Can I Reduce or Temporarily Expand the Disk Capacity?,Capacity Expansion,User Guide", + "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", + "githuburl":"" + }, + { + "uri":"evs_faq_0042.html", + "product_code":"evs", + "code":"82", + "des":"An EVS disk can be expanded either in the Available or In-use state. Expanding the disk capacity on the management console enlarges the disk capacity, but you still need ", + "doc_type":"usermanual", + "kw":"Do I Need to Restart the Server After Expanding the Disk Capacity?,Capacity Expansion,User Guide", + "title":"Do I Need to Restart the Server After Expanding the Disk Capacity?", + "githuburl":"" + }, + { + "uri":"evs_faq_0028.html", + "product_code":"evs", + "code":"83", + "des":"An expansion consists of two phases:Expand the disk capacity on the management console.A shared, in-use disk cannot be expanded. You must detach the shared disk from all ", + "doc_type":"usermanual", + "kw":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?,Capacity Expansion,User Guide", + "title":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?", + "githuburl":"" + }, + { + "uri":"evs_faq_0024.html", + "product_code":"evs", + "code":"84", + "des":"An EVS system disk can be as large as 1 TB (1024 GB). You can expand the capacity of a system disk to up to 1 TB.An EVS data disk can be as large as 32 TB (32768 GB).With", + "doc_type":"usermanual", + "kw":"What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?,Capacity Expansion,User Guide", + "title":"What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?", + "githuburl":"" + }, + { + "uri":"evs_faq_0027.html", + "product_code":"evs", + "code":"85", + "des":"After expanding disk capacity on the management console, you must log in to the server and extend the disk partition and file system for the extra capacity to become avai", + "doc_type":"usermanual", + "kw":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?,Capacity Expansion", + "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", + "githuburl":"" + }, + { + "uri":"evs_01_0078.html", + "product_code":"evs", + "code":"86", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Attachment", + "title":"Attachment", + "githuburl":"" + }, + { + "uri":"evs_faq_0006.html", + "product_code":"evs", + "code":"87", + "des":"A non-shared disk can only be attached to one server.A shared disk can be attached to up to 16 servers. Shared disks are a type of EVS disks that can be attached to multi", + "doc_type":"usermanual", + "kw":"Can I Attach a Disk to Multiple Servers?,Attachment,User Guide", + "title":"Can I Attach a Disk to Multiple Servers?", + "githuburl":"" + }, + { + "uri":"evs_faq_0036.html", + "product_code":"evs", + "code":"88", + "des":"No.Disks and the servers you attach the disks to must be in the same AZ. The same is true for shared disks. Shared disks can only be attached to the servers in the same A", + "doc_type":"usermanual", + "kw":"Can I Attach a Disk to a Server in Another AZ?,Attachment,User Guide", + "title":"Can I Attach a Disk to a Server in Another AZ?", + "githuburl":"" + }, + { + "uri":"evs_faq_0022.html", + "product_code":"evs", + "code":"89", + "des":"Symptom: A data disk has been attached to a Windows server on the management console, but the disk cannot be viewed on the server. For example, Volume (D:) was not shown ", + "doc_type":"usermanual", + "kw":"Why Can't I View the Attached Data Disk on the Server?,Attachment,User Guide", + "title":"Why Can't I View the Attached Data Disk on the Server?", + "githuburl":"" + }, + { + "uri":"evs_faq_0043.html", + "product_code":"evs", + "code":"90", + "des":"Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to", + "doc_type":"usermanual", + "kw":"How Can I Add a Data Disk to an Existing Server?,Attachment,User Guide", + "title":"How Can I Add a Data Disk to an Existing Server?", + "githuburl":"" + }, + { + "uri":"evs_01_0079.html", + "product_code":"evs", + "code":"91", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Detachment", + "title":"Detachment", + "githuburl":"" + }, + { + "uri":"evs_faq_0012.html", + "product_code":"evs", + "code":"92", + "des":"It depends on if the disk is encrypted or not.EncryptedCMK is disabled or scheduled for deletion.Before you detach an EVS disk encrypted by a CMK, check whether the CMK i", + "doc_type":"usermanual", + "kw":"If I Detach a Disk Will I Lose the Data on My Disk?,Detachment,User Guide", + "title":"If I Detach a Disk Will I Lose the Data on My Disk?", + "githuburl":"" + }, + { + "uri":"evs_faq_0056.html", + "product_code":"evs", + "code":"93", + "des":"EVS disks can be used as system disks or data disks, but the way you detach each one is different.System disks: A system disk can only be detached offline. You must first", + "doc_type":"usermanual", + "kw":"Why Can't I Detach My Disk?,Detachment,User Guide", + "title":"Why Can't I Detach My Disk?", + "githuburl":"" + }, + { + "uri":"evs_01_0082.html", + "product_code":"evs", + "code":"94", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Capacity", + "title":"Capacity", + "githuburl":"" + }, + { + "uri":"evs_faq_0031.html", + "product_code":"evs", + "code":"95", + "des":"The maximum capacity supported for a system disk is 1024 GB.The maximum capacity supported for a data disk is 32768 GB.", + "doc_type":"usermanual", + "kw":"What Is the Maximum Capacity Supported for the System and Data Disks?,Capacity,User Guide", + "title":"What Is the Maximum Capacity Supported for the System and Data Disks?", + "githuburl":"" + }, + { + "uri":"evs_faq_0032.html", + "product_code":"evs", + "code":"96", + "des":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server.Expand the capacity of the existing disk. Both system disks and data disks can", + "doc_type":"usermanual", + "kw":"What Should I Do If My Disk Starts to Run Out of Space?,Capacity,User Guide", + "title":"What Should I Do If My Disk Starts to Run Out of Space?", + "githuburl":"" + }, + { + "uri":"evs_faq_0035.html", + "product_code":"evs", + "code":"97", + "des":"If your disk capacity is greater than 2 TB, do not use fdisk to partition the disk. Or any space in excess of 2 TB will be unable to be displayed after the disk is partit", + "doc_type":"usermanual", + "kw":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TB and Then the Space in Excess o", + "title":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TB and Then the Space in Excess of 2 TB Cannot Be Displayed?", + "githuburl":"" + }, + { + "uri":"evs_faq_0053.html", + "product_code":"evs", + "code":"98", + "des":"You can view your disk usages in either of the following ways:Install Agent to View Disk UsageView disk usages manually.The details depend on the OS. This FAQ uses Window", + "doc_type":"usermanual", + "kw":"How Can I View My Disk Usage?,Capacity,User Guide", + "title":"How Can I View My Disk Usage?", + "githuburl":"" + }, + { + "uri":"evs_01_0084.html", + "product_code":"evs", + "code":"99", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Sharing", + "title":"Sharing", + "githuburl":"" + }, + { + "uri":"evs_faq_0039.html", + "product_code":"evs", + "code":"100", + "des":"Yes.If you simply attach a shared disk to multiple servers, files cannot be shared between the servers. If the rules for reading and writing data are not mutually agreed ", + "doc_type":"usermanual", + "kw":"Do I Have to Deploy a Cluster to Use Shared Disks?,Sharing,User Guide", + "title":"Do I Have to Deploy a Cluster to Use Shared Disks?", + "githuburl":"" + }, + { + "uri":"evs_faq_0037.html", + "product_code":"evs", + "code":"101", + "des":"A shared disk can be attached to up to 16 servers.", + "doc_type":"usermanual", + "kw":"How Many Servers Can I Attach a Shared Disk to?,Sharing,User Guide", + "title":"How Many Servers Can I Attach a Shared Disk to?", + "githuburl":"" + }, + { + "uri":"evs_01_0039.html", + "product_code":"evs", + "code":"102", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Appendix", + "title":"Appendix", + "githuburl":"" + }, + { + "uri":"evs_01_0040.html", + "product_code":"evs", + "code":"103", + "des":"An EVS disk has several statuses. Table 1 lists the EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS ", + "doc_type":"usermanual", + "kw":"EVS Disk Status,Appendix,User Guide", + "title":"EVS Disk Status", + "githuburl":"" + }, + { + "uri":"evs_01_0041.html", + "product_code":"evs", + "code":"104", + "des":"An EVS snapshot has several statuses. Table 1 lists the EVS snapshot statuses, the meaning of each status, and the operations a snapshot in each status allows.Snapshot st", + "doc_type":"usermanual", + "kw":"EVS Snapshot Status,Appendix,User Guide", + "title":"EVS Snapshot Status", + "githuburl":"" + }, + { + "uri":"evs_01_0114.html", + "product_code":"evs", + "code":"105", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + }, + { + "uri":"evs_01_0115.html", + "product_code":"evs", + "code":"106", + "des":"For details about the terms involved in this document, see Glossary.", + "doc_type":"usermanual", + "kw":"Glossary,User Guide", + "title":"Glossary", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/evs/umn/CLASS.TXT.json b/docs/evs/umn/CLASS.TXT.json new file mode 100644 index 000000000..a6c7a5393 --- /dev/null +++ b/docs/evs/umn/CLASS.TXT.json @@ -0,0 +1,956 @@ +[ + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Overview", + "uri":"evs_01_0119.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and rich specifications, EVS disks can be used for ", + "product_code":"evs", + "title":"What Is EVS?", + "uri":"en-us_topic_0014580741.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"2" + }, + { + "desc":"EVS disks are classified based on the disk I/O performance. EVS disks differ in performance and price. Choose the disk type most appropriate for your applications.Common ", + "product_code":"evs", + "title":"Disk Types and Performance", + "uri":"en-us_topic_0014580744.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).VBD is the default EVS device type. VBD EVS disks support only basic", + "product_code":"evs", + "title":"Device Types and Usage Instructions", + "uri":"en-us_topic_0052554220.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"4" + }, + { + "desc":"Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multiple servers. Shared EVS disks feature multiple attach", + "product_code":"evs", + "title":"Shared EVS Disks and Usage Instructions", + "uri":"en-us_topic_0032860759.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"5" + }, + { + "desc":"In case your services require encryption for the data stored on EVS disks, EVS provides you with the encryption function. You can encrypt newly created EVS disks.EVS uses", + "product_code":"evs", + "title":"EVS Disk Encryption", + "uri":"evs_01_0001.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"6" + }, + { + "desc":"Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while servers are running. If data loss or damage occurred d", + "product_code":"evs", + "title":"EVS Backup", + "uri":"evs_01_0021.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"7" + }, + { + "desc":"EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific ", + "product_code":"evs", + "title":"EVS Snapshot", + "uri":"en-us_topic_0066809008.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"8" + }, + { + "desc":"Both EVS disk backup and EVS snapshot provide redundancies for the EVS disk data to improve reliability. Table 1 lists the differences between them.", + "product_code":"evs", + "title":"Differences Between EVS Disk Backup and EVS Snapshot", + "uri":"evs_01_0048.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"9" + }, + { + "desc":"If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a p", + "product_code":"evs", + "title":"EVS Replication (Deprecated)", + "uri":"evs_01_0020.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"10" + }, + { + "desc":"If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IA", + "product_code":"evs", + "title":"Permissions Management", + "uri":"evs_01_0086.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"11" + }, + { + "desc":"Figure 1 shows the relationships between EVS and other services.Relationships between EVS and other servicesECS: EVS disks can be attached to ECSs and used as scalable bl", + "product_code":"evs", + "title":"EVS and Other Services", + "uri":"evs_01_0106.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"12" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Basic Concepts", + "uri":"evs_01_0101.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"13" + }, + { + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "product_code":"evs", + "title":"Region and AZ", + "uri":"evs_01_0097.html", + "doc_type":"usermanual", + "p_code":"13", + "code":"14" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Getting Started", + "uri":"evs_01_0120.html", + "doc_type":"usermanual", + "p_code":"", + "code":"15" + }, + { + "desc":"Figure 1 shows the basic EVS operation procedure.Basic operation procedure", + "product_code":"evs", + "title":"Basic Operation Procedure", + "uri":"evs_01_0057.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"16" + }, + { + "desc":"EVS disks can be used as system disks or data disks for servers.When a server is created, a system disk is automatically created and attached. You cannot create a system ", + "product_code":"evs", + "title":"Create an EVS Disk", + "uri":"en-us_topic_0021738346.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"17" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Attach an EVS Disk", + "uri":"evs_01_0107.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"18" + }, + { + "desc":"Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this ", + "product_code":"evs", + "title":"Attaching a Non-Shared Disk", + "uri":"evs_01_0036.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"19" + }, + { + "desc":"Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this ", + "product_code":"evs", + "title":"Attaching a Shared Disk", + "uri":"evs_01_0037.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"20" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Initialize an EVS Data Disk", + "uri":"evs_01_0058.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"21" + }, + { + "desc":"After a disk is attached to a server, you need to log in to the server to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.Sy", + "product_code":"evs", + "title":"Introduction to Data Disk Initialization Scenarios and Partition Styles", + "uri":"evs_01_0038.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"22" + }, + { + "desc":"This section uses Windows Server 2008 R2 Enterprise 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity support", + "product_code":"evs", + "title":"Initializing a Windows Data Disk (Windows Server 2008)", + "uri":"evs_01_0108.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"23" + }, + { + "desc":"This section uses Windows Server 2016 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity supported by", + "product_code":"evs", + "title":"Initializing a Windows Data Disk (Windows Server 2016)", + "uri":"evs_01_0045.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"24" + }, + { + "desc":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.The maximum disk ", + "product_code":"evs", + "title":"Initializing a Linux Data Disk (fdisk)", + "uri":"evs_01_0033.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"25" + }, + { + "desc":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.The maximum disk", + "product_code":"evs", + "title":"Initializing a Linux Data Disk (parted)", + "uri":"evs_01_0034.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"26" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Permissions Management", + "uri":"evs_01_0087.html", + "doc_type":"usermanual", + "p_code":"", + "code":"27" + }, + { + "desc":"This chapter describes how to use IAM to implement fine-grained permissions control for your EVS resources. With IAM, you can:Create IAM users for employees based on your", + "product_code":"evs", + "title":"Creating a User and Granting EVS Permissions", + "uri":"evs_01_0089.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"28" + }, + { + "desc":"Custom policies can be created to supplement the system-defined policies of EVS. For the actions supported for custom policies, see section \"Permissions Policies and Supp", + "product_code":"evs", + "title":"EVS Custom Policies", + "uri":"evs_01_0090.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"29" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Disk Capacity Expansion", + "uri":"evs_01_0059.html", + "doc_type":"usermanual", + "p_code":"", + "code":"30" + }, + { + "desc":"If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.Both system disks and data disks can be expanded. Curr", + "product_code":"evs", + "title":"Expansion Overview", + "uri":"evs_01_0006.html", + "doc_type":"usermanual", + "p_code":"30", + "code":"31" + }, + { + "desc":"This section describes how to expand the capacity of an In-use EVS disk on the management console. The In-use status indicates that the disk has been attached to a server", + "product_code":"evs", + "title":"Expanding Capacity for an In-use EVS Disk", + "uri":"evs_01_0007.html", + "doc_type":"usermanual", + "p_code":"30", + "code":"32" + }, + { + "desc":"This section describes how to expand the capacity of an Available EVS disk on the management console. The Available status indicates that the disk has not been attached t", + "product_code":"evs", + "title":"Expanding Capacity for an Available EVS Disk", + "uri":"evs_01_0008.html", + "doc_type":"usermanual", + "p_code":"30", + "code":"33" + }, + { + "desc":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the ad", + "product_code":"evs", + "title":"Extending Disk Partitions and File Systems (Windows Server 2008)", + "uri":"en-us_topic_0017616396.html", + "doc_type":"usermanual", + "p_code":"30", + "code":"34" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Extending Disk Partitions and File Systems (Linux)", + "uri":"evs_01_0094.html", + "doc_type":"usermanual", + "p_code":"30", + "code":"35" + }, + { + "desc":"Before extending the disk partition and file system, you must check the disk partition style and file system format, and then select the appropriate operation accordingly", + "product_code":"evs", + "title":"Partition and File System Extension Preparations (Linux)", + "uri":"evs_01_0035.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"36" + }, + { + "desc":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", + "product_code":"evs", + "title":"Extending Partitions and File Systems for System Disks (Linux)", + "uri":"evs_01_0072.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"37" + }, + { + "desc":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", + "product_code":"evs", + "title":"Extending Partitions and File Systems for Data Disks (Linux)", + "uri":"evs_01_0109.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"38" + }, + { + "desc":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", + "product_code":"evs", + "title":"Extending Partitions and File Systems for SCSI Disks (Linux)", + "uri":"evs_01_0018.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"39" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Detaching an EVS Disk", + "uri":"evs_01_0002.html", + "doc_type":"usermanual", + "p_code":"", + "code":"40" + }, + { + "desc":"A system disk can only be detached offline, that is, its server must be in the Stopped state before the system disk is detached. Therefore, you need to first stop the ser", + "product_code":"evs", + "title":"Detaching a System Disk", + "uri":"evs_01_0003.html", + "doc_type":"usermanual", + "p_code":"40", + "code":"41" + }, + { + "desc":"Data disks can be detached online or offline, which means that the server containing the to-be-detached data disk can either be in the Running or Stopped state.ECSDetach ", + "product_code":"evs", + "title":"Detaching a Data Disk", + "uri":"evs_01_0004.html", + "doc_type":"usermanual", + "p_code":"40", + "code":"42" + }, + { + "desc":"If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.Before deleting a disk, ensure that the disk status is Availa", + "product_code":"evs", + "title":"Deleting an EVS Disk", + "uri":"evs_01_0005.html", + "doc_type":"usermanual", + "p_code":"", + "code":"43" + }, + { + "desc":"The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:System disk encryption relates to the image tha", + "product_code":"evs", + "title":"Managing an Encrypted EVS Disk", + "uri":"evs_01_0009.html", + "doc_type":"usermanual", + "p_code":"", + "code":"44" + }, + { + "desc":"You can create shared VBD disks or shared SCSI disks. It is recommended that you attach the shared disk to the ECSs in the same ECS group to improve service reliability.S", + "product_code":"evs", + "title":"Managing a Shared EVS Disk", + "uri":"evs_01_0010.html", + "doc_type":"usermanual", + "p_code":"", + "code":"45" + }, + { + "desc":"EVS disk backups are created using the CBR service. For details, see Creating a Disk Backup Vault in the Cloud Backup and Recovery User Guide.This section describes how t", + "product_code":"evs", + "title":"Managing EVS Backup", + "uri":"evs_01_0110.html", + "doc_type":"usermanual", + "p_code":"", + "code":"46" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Managing Snapshots", + "uri":"evs_01_0111.html", + "doc_type":"usermanual", + "p_code":"", + "code":"47" + }, + { + "desc":"EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific ", + "product_code":"evs", + "title":"Snapshot Overview", + "uri":"evs_01_0098.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"48" + }, + { + "desc":"You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.A maximum of 7 snapshots can be created for one disk.Snapshots", + "product_code":"evs", + "title":"Creating a Snapshot", + "uri":"en-us_topic_0066615262.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"49" + }, + { + "desc":"If a snapshot is no longer needed, you can delete the snapshot to release the virtual resources. Snapshot deletion has the following constraints:The snapshot status must ", + "product_code":"evs", + "title":"Deleting a Snapshot", + "uri":"evs_01_0011.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"50" + }, + { + "desc":"If the data on an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source disk to restore data. Snapshot rollback has the following con", + "product_code":"evs", + "title":"Rolling Back Data from a Snapshot", + "uri":"evs_01_0012.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"51" + }, + { + "desc":"This section describes how to create an EVS disk on the Snapshots page. Besides, you can also create an EVS disk from a snapshot by specifying the Create from snapshot pa", + "product_code":"evs", + "title":"Creating an EVS Disk from a Snapshot", + "uri":"evs_01_0013.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"52" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Managing EVS Replication (Deprecated)", + "uri":"evs_01_0023.html", + "doc_type":"usermanual", + "p_code":"", + "code":"53" + }, + { + "desc":"For the EVS replication concepts, see EVS Replication (Deprecated). This chapter describes the basic functions and operations of EVS replication. Figure 1 shows the opera", + "product_code":"evs", + "title":"EVS Replication Operation Procedure (Deprecated)", + "uri":"evs_01_0060.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"54" + }, + { + "desc":"Before you create an EVS replication pair, create a DR ECS in the secondary AZ for the production ECS. The DR ECS parameters must be consistent with those of the producti", + "product_code":"evs", + "title":"Creating a DR ECS (Deprecated)", + "uri":"evs_01_0024.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"55" + }, + { + "desc":"Before you use EVS replication, bind a virtual IP address to the production server and DR server, respectively. Then configure the virtual IP address as the static IP add", + "product_code":"evs", + "title":"Configuring a Virtual IP Address for the Server (Deprecated)", + "uri":"evs_01_0026.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"56" + }, + { + "desc":"This section is used to guide users to collect the production ECS and DR ECS information, including the ECS IDs and the IDs of the EVS disks attached the ECSs.Two EVS dis", + "product_code":"evs", + "title":"Collecting ECS Information (Deprecated)", + "uri":"evs_01_0025.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"57" + }, + { + "desc":"Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see EVS Replication Pair in the", + "product_code":"evs", + "title":"Creating an EVS Replication Pair (Deprecated)", + "uri":"evs_01_0027.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"58" + }, + { + "desc":"Currently, users need to make API calls to create replication consistency groups and add EVS replication pairs to the groups. For details, see Replication Consistency Gro", + "product_code":"evs", + "title":"Creating a Replication Consistency Group (Deprecated)", + "uri":"evs_01_0028.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"59" + }, + { + "desc":"Currently, EVS replication pairs can be added to or removed from replication consistency groups through APIs only. For details, see Updating a Replication Consistency Gro", + "product_code":"evs", + "title":"Updating a Replication Consistency Group (Deprecated)", + "uri":"evs_01_0029.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"60" + }, + { + "desc":"Production servers and production disks belong to the primary AZ, and DR servers and DR disks belong to the secondary AZ. Users can make API calls to perform a planned mi", + "product_code":"evs", + "title":"Planned Migration (Deprecated)", + "uri":"evs_01_0030.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"61" + }, + { + "desc":"When the production servers and disks in the primary AZ become faulty due to force majeure, users can make API calls to perform a failover for the replication consistency", + "product_code":"evs", + "title":"Failover (Deprecated)", + "uri":"evs_01_0031.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"62" + }, + { + "desc":"When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide s", + "product_code":"evs", + "title":"Reprotection (Deprecated)", + "uri":"evs_01_0032.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"63" + }, + { + "desc":"Users can make an API call to expand the EVS disks in one or multiple EVS replication pairs of a replication consistency group. In such an expansion operation, two EVS di", + "product_code":"evs", + "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", + "uri":"evs_01_0043.html", + "doc_type":"usermanual", + "p_code":"53", + "code":"64" + }, + { + "desc":"Through EVS disk transfer, EVS disks can be transferred from one account to another. After the transfer succeeds, the ownerships of the EVS disks belong to the target acc", + "product_code":"evs", + "title":"Managing EVS Disk Transfer", + "uri":"evs_01_0042.html", + "doc_type":"usermanual", + "p_code":"", + "code":"65" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Managing a Tag", + "uri":"evs_01_0112.html", + "doc_type":"usermanual", + "p_code":"", + "code":"66" + }, + { + "desc":"Tags identify EVS resources for purposes of easy categorization and quick search.", + "product_code":"evs", + "title":"Tag Overview", + "uri":"evs_01_0099.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"67" + }, + { + "desc":"This section is used to guide users to add a tag for an existing EVS disk. You can also add tags during the EVS disk creation. For details, see Create an EVS Disk.Tags ar", + "product_code":"evs", + "title":"Adding a Tag", + "uri":"evs_01_0014.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"68" + }, + { + "desc":"You can change the value of a tag for an existing disk, but cannot change the key of a tag.The disk list page is displayed.The disk details page is displayed.The Edit Tag", + "product_code":"evs", + "title":"Modifying a Tag", + "uri":"evs_01_0015.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"69" + }, + { + "desc":"If an existing tag is no longer needed, you can delete it.The disk list page is displayed.The disk details page is displayed.The Delete Tag page is displayed.Return to th", + "product_code":"evs", + "title":"Deleting a Tag", + "uri":"evs_01_0016.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"70" + }, + { + "desc":"Tags can be used to categorize EVS disks, and users can quickly search for their desired EVS disks by tags. This section is used to guide users to search for EVS disk by ", + "product_code":"evs", + "title":"Searching Disks by Tags", + "uri":"evs_01_0019.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"71" + }, + { + "desc":"This section describes monitored metrics reported by EVS to Cloud Eye as well as their namespaces and dimensions. You can use console or APIs provided by Cloud Eye to que", + "product_code":"evs", + "title":"Viewing EVS Monitoring Data", + "uri":"evs_01_0044.html", + "doc_type":"usermanual", + "p_code":"", + "code":"72" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"FAQ", + "uri":"evs_faq_0001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"73" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"General", + "uri":"evs_01_0081.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"74" + }, + { + "desc":"No.EVS disks must be attached to servers before you can use them.", + "product_code":"evs", + "title":"Can EVS Disks Be Used Alone?", + "uri":"evs_faq_0054.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"75" + }, + { + "desc":"No.The AZ of a disk cannot be changed after you have created the disk. If you want to change the AZ, delete the disk and create a new one.", + "product_code":"evs", + "title":"Can I Change the AZ of My Disk?", + "uri":"evs_faq_0048.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"76" + }, + { + "desc":"If an error occurs, the disk may show one of the states listed in the following table. Take the measures described in the table to handle the exceptions.", + "product_code":"evs", + "title":"What Should I Do If an Error Occurs on My EVS Disk?", + "uri":"evs_faq_0014.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"77" + }, + { + "desc":"EVS disks have two device types: VBD and SCSI. WWNs are used as the unique identifiers for SCSI EVS disks, and VBD EVS disks do not have WWNs.You can view the WWN of a SC", + "product_code":"evs", + "title":"Why Do Some of My EVS Disks Not Have WWN Information?", + "uri":"evs_faq_0021.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"78" + }, + { + "desc":"If the system displays a message indicating insufficient quota during an EVS replication pair creation or a replication consistency group creation or update, contact the ", + "product_code":"evs", + "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", + "uri":"evs_faq_0020.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"79" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Capacity Expansion", + "uri":"evs_01_0077.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"80" + }, + { + "desc":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", + "product_code":"evs", + "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", + "uri":"evs_faq_0026.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"81" + }, + { + "desc":"An EVS disk can be expanded either in the Available or In-use state. Expanding the disk capacity on the management console enlarges the disk capacity, but you still need ", + "product_code":"evs", + "title":"Do I Need to Restart the Server After Expanding the Disk Capacity?", + "uri":"evs_faq_0042.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"82" + }, + { + "desc":"An expansion consists of two phases:Expand the disk capacity on the management console.A shared, in-use disk cannot be expanded. You must detach the shared disk from all ", + "product_code":"evs", + "title":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?", + "uri":"evs_faq_0028.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"83" + }, + { + "desc":"An EVS system disk can be as large as 1 TB (1024 GB). You can expand the capacity of a system disk to up to 1 TB.An EVS data disk can be as large as 32 TB (32768 GB).With", + "product_code":"evs", + "title":"What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?", + "uri":"evs_faq_0024.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"84" + }, + { + "desc":"After expanding disk capacity on the management console, you must log in to the server and extend the disk partition and file system for the extra capacity to become avai", + "product_code":"evs", + "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", + "uri":"evs_faq_0027.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"85" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Attachment", + "uri":"evs_01_0078.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"86" + }, + { + "desc":"A non-shared disk can only be attached to one server.A shared disk can be attached to up to 16 servers. Shared disks are a type of EVS disks that can be attached to multi", + "product_code":"evs", + "title":"Can I Attach a Disk to Multiple Servers?", + "uri":"evs_faq_0006.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"87" + }, + { + "desc":"No.Disks and the servers you attach the disks to must be in the same AZ. The same is true for shared disks. Shared disks can only be attached to the servers in the same A", + "product_code":"evs", + "title":"Can I Attach a Disk to a Server in Another AZ?", + "uri":"evs_faq_0036.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"88" + }, + { + "desc":"Symptom: A data disk has been attached to a Windows server on the management console, but the disk cannot be viewed on the server. For example, Volume (D:) was not shown ", + "product_code":"evs", + "title":"Why Can't I View the Attached Data Disk on the Server?", + "uri":"evs_faq_0022.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"89" + }, + { + "desc":"Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to", + "product_code":"evs", + "title":"How Can I Add a Data Disk to an Existing Server?", + "uri":"evs_faq_0043.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"90" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Detachment", + "uri":"evs_01_0079.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"91" + }, + { + "desc":"It depends on if the disk is encrypted or not.EncryptedCMK is disabled or scheduled for deletion.Before you detach an EVS disk encrypted by a CMK, check whether the CMK i", + "product_code":"evs", + "title":"If I Detach a Disk Will I Lose the Data on My Disk?", + "uri":"evs_faq_0012.html", + "doc_type":"usermanual", + "p_code":"91", + "code":"92" + }, + { + "desc":"EVS disks can be used as system disks or data disks, but the way you detach each one is different.System disks: A system disk can only be detached offline. You must first", + "product_code":"evs", + "title":"Why Can't I Detach My Disk?", + "uri":"evs_faq_0056.html", + "doc_type":"usermanual", + "p_code":"91", + "code":"93" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Capacity", + "uri":"evs_01_0082.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"94" + }, + { + "desc":"The maximum capacity supported for a system disk is 1024 GB.The maximum capacity supported for a data disk is 32768 GB.", + "product_code":"evs", + "title":"What Is the Maximum Capacity Supported for the System and Data Disks?", + "uri":"evs_faq_0031.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"95" + }, + { + "desc":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server.Expand the capacity of the existing disk. Both system disks and data disks can", + "product_code":"evs", + "title":"What Should I Do If My Disk Starts to Run Out of Space?", + "uri":"evs_faq_0032.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"96" + }, + { + "desc":"If your disk capacity is greater than 2 TB, do not use fdisk to partition the disk. Or any space in excess of 2 TB will be unable to be displayed after the disk is partit", + "product_code":"evs", + "title":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TB and Then the Space in Excess of 2 TB Cannot Be Displayed?", + "uri":"evs_faq_0035.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"97" + }, + { + "desc":"You can view your disk usages in either of the following ways:Install Agent to View Disk UsageView disk usages manually.The details depend on the OS. This FAQ uses Window", + "product_code":"evs", + "title":"How Can I View My Disk Usage?", + "uri":"evs_faq_0053.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"98" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Sharing", + "uri":"evs_01_0084.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"99" + }, + { + "desc":"Yes.If you simply attach a shared disk to multiple servers, files cannot be shared between the servers. If the rules for reading and writing data are not mutually agreed ", + "product_code":"evs", + "title":"Do I Have to Deploy a Cluster to Use Shared Disks?", + "uri":"evs_faq_0039.html", + "doc_type":"usermanual", + "p_code":"99", + "code":"100" + }, + { + "desc":"A shared disk can be attached to up to 16 servers.", + "product_code":"evs", + "title":"How Many Servers Can I Attach a Shared Disk to?", + "uri":"evs_faq_0037.html", + "doc_type":"usermanual", + "p_code":"99", + "code":"101" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Appendix", + "uri":"evs_01_0039.html", + "doc_type":"usermanual", + "p_code":"", + "code":"102" + }, + { + "desc":"An EVS disk has several statuses. Table 1 lists the EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS ", + "product_code":"evs", + "title":"EVS Disk Status", + "uri":"evs_01_0040.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"103" + }, + { + "desc":"An EVS snapshot has several statuses. Table 1 lists the EVS snapshot statuses, the meaning of each status, and the operations a snapshot in each status allows.Snapshot st", + "product_code":"evs", + "title":"EVS Snapshot Status", + "uri":"evs_01_0041.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"104" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"Change History", + "uri":"evs_01_0114.html", + "doc_type":"usermanual", + "p_code":"", + "code":"105" + }, + { + "desc":"For details about the terms involved in this document, see Glossary.", + "product_code":"evs", + "title":"Glossary", + "uri":"evs_01_0115.html", + "doc_type":"usermanual", + "p_code":"", + "code":"106" + } +] \ No newline at end of file diff --git a/docs/evs/umn/PARAMETERS.txt b/docs/evs/umn/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/evs/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/evs/umn/en-us_image_0000001119238510.png b/docs/evs/umn/en-us_image_0000001119238510.png new file mode 100644 index 000000000..a2e38990a Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001119238510.png differ diff --git a/docs/evs/umn/en-us_image_0000001242362390.jpg b/docs/evs/umn/en-us_image_0000001242362390.jpg new file mode 100644 index 000000000..fe5814aed Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001242362390.jpg differ diff --git a/docs/evs/umn/en-us_image_0044524671.png b/docs/evs/umn/en-us_image_0044524671.png new file mode 100644 index 000000000..70d184cba Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524671.png differ diff --git a/docs/evs/umn/en-us_image_0044524678.png b/docs/evs/umn/en-us_image_0044524678.png new file mode 100644 index 000000000..aa2fa75ca Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524678.png differ diff --git a/docs/evs/umn/en-us_image_0044524683.png b/docs/evs/umn/en-us_image_0044524683.png new file mode 100644 index 000000000..5819dd577 Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524683.png differ diff --git a/docs/evs/umn/en-us_image_0044524701.png b/docs/evs/umn/en-us_image_0044524701.png new file mode 100644 index 000000000..d2b12f109 Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524701.png differ diff --git a/docs/evs/umn/en-us_image_0044524709.png b/docs/evs/umn/en-us_image_0044524709.png new file mode 100644 index 000000000..1e76e01ca Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524709.png differ diff --git a/docs/evs/umn/en-us_image_0044524713.png b/docs/evs/umn/en-us_image_0044524713.png new file mode 100644 index 000000000..0194b3e0c Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524713.png differ diff --git a/docs/evs/umn/en-us_image_0044524716.png b/docs/evs/umn/en-us_image_0044524716.png new file mode 100644 index 000000000..c46fe6354 Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524716.png differ diff --git a/docs/evs/umn/en-us_image_0044524739.png b/docs/evs/umn/en-us_image_0044524739.png new file mode 100644 index 000000000..56d36e254 Binary files /dev/null and b/docs/evs/umn/en-us_image_0044524739.png differ diff --git a/docs/evs/umn/en-us_image_0090103571.png b/docs/evs/umn/en-us_image_0090103571.png new file mode 100644 index 000000000..26f1ec931 Binary files /dev/null and b/docs/evs/umn/en-us_image_0090103571.png differ diff --git a/docs/evs/umn/en-us_image_0094231725.png b/docs/evs/umn/en-us_image_0094231725.png new file mode 100644 index 000000000..ef3e64741 Binary files /dev/null and b/docs/evs/umn/en-us_image_0094231725.png differ diff --git a/docs/evs/umn/en-us_image_0095024494.png b/docs/evs/umn/en-us_image_0095024494.png new file mode 100644 index 000000000..48cdcc7bd Binary files /dev/null and b/docs/evs/umn/en-us_image_0095024494.png differ diff --git a/docs/evs/umn/en-us_image_0097597141.png b/docs/evs/umn/en-us_image_0097597141.png new file mode 100644 index 000000000..95c8e1e1c Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597141.png differ diff --git a/docs/evs/umn/en-us_image_0097597143.png b/docs/evs/umn/en-us_image_0097597143.png new file mode 100644 index 000000000..39b706b91 Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597143.png differ diff --git a/docs/evs/umn/en-us_image_0097597145.png b/docs/evs/umn/en-us_image_0097597145.png new file mode 100644 index 000000000..85eee0cce Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597145.png differ diff --git a/docs/evs/umn/en-us_image_0097597147.png b/docs/evs/umn/en-us_image_0097597147.png new file mode 100644 index 000000000..1cc4d8129 Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597147.png differ diff --git a/docs/evs/umn/en-us_image_0097597149.png b/docs/evs/umn/en-us_image_0097597149.png new file mode 100644 index 000000000..5663a2fb6 Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597149.png differ diff --git a/docs/evs/umn/en-us_image_0097597151.png b/docs/evs/umn/en-us_image_0097597151.png new file mode 100644 index 000000000..c6fb1fa87 Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597151.png differ diff --git a/docs/evs/umn/en-us_image_0097597153.png b/docs/evs/umn/en-us_image_0097597153.png new file mode 100644 index 000000000..2036a6b5b Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597153.png differ diff --git a/docs/evs/umn/en-us_image_0097597155.png b/docs/evs/umn/en-us_image_0097597155.png new file mode 100644 index 000000000..23cc5221f Binary files /dev/null and b/docs/evs/umn/en-us_image_0097597155.png differ diff --git a/docs/evs/umn/en-us_image_0107917672.png b/docs/evs/umn/en-us_image_0107917672.png new file mode 100644 index 000000000..db7d76b14 Binary files /dev/null and b/docs/evs/umn/en-us_image_0107917672.png differ diff --git a/docs/evs/umn/en-us_image_0107919973.png b/docs/evs/umn/en-us_image_0107919973.png new file mode 100644 index 000000000..dfac6213d Binary files /dev/null and b/docs/evs/umn/en-us_image_0107919973.png differ diff --git a/docs/evs/umn/en-us_image_0125151939.png b/docs/evs/umn/en-us_image_0125151939.png new file mode 100644 index 000000000..76b073a22 Binary files /dev/null and b/docs/evs/umn/en-us_image_0125151939.png differ diff --git a/docs/evs/umn/en-us_image_0129867556.png b/docs/evs/umn/en-us_image_0129867556.png new file mode 100644 index 000000000..7fb145297 Binary files /dev/null and b/docs/evs/umn/en-us_image_0129867556.png differ diff --git a/docs/evs/umn/en-us_image_0129867577.png b/docs/evs/umn/en-us_image_0129867577.png new file mode 100644 index 000000000..532383165 Binary files /dev/null and b/docs/evs/umn/en-us_image_0129867577.png differ diff --git a/docs/evs/umn/en-us_image_0132359404.png b/docs/evs/umn/en-us_image_0132359404.png new file mode 100644 index 000000000..3e864f5b5 Binary files /dev/null and b/docs/evs/umn/en-us_image_0132359404.png differ diff --git a/docs/evs/umn/en-us_image_0132360430.png b/docs/evs/umn/en-us_image_0132360430.png new file mode 100644 index 000000000..caf35a81a Binary files /dev/null and b/docs/evs/umn/en-us_image_0132360430.png differ diff --git a/docs/evs/umn/en-us_image_0132368216.png b/docs/evs/umn/en-us_image_0132368216.png new file mode 100644 index 000000000..11698423b Binary files /dev/null and b/docs/evs/umn/en-us_image_0132368216.png differ diff --git a/docs/evs/umn/en-us_image_0133519241.png b/docs/evs/umn/en-us_image_0133519241.png new file mode 100644 index 000000000..8d0fac7fa Binary files /dev/null and b/docs/evs/umn/en-us_image_0133519241.png differ diff --git a/docs/evs/umn/en-us_image_0139105429.png b/docs/evs/umn/en-us_image_0139105429.png new file mode 100644 index 000000000..8f8c370ee Binary files /dev/null and b/docs/evs/umn/en-us_image_0139105429.png differ diff --git a/docs/evs/umn/en-us_image_0152639916.png b/docs/evs/umn/en-us_image_0152639916.png new file mode 100644 index 000000000..1e1e0b088 Binary files /dev/null and b/docs/evs/umn/en-us_image_0152639916.png differ diff --git a/docs/evs/umn/en-us_image_0152701021.png b/docs/evs/umn/en-us_image_0152701021.png new file mode 100644 index 000000000..925a05981 Binary files /dev/null and b/docs/evs/umn/en-us_image_0152701021.png differ diff --git a/docs/evs/umn/en-us_image_0152754019.png b/docs/evs/umn/en-us_image_0152754019.png new file mode 100644 index 000000000..f316ade77 Binary files /dev/null and b/docs/evs/umn/en-us_image_0152754019.png differ diff --git a/docs/evs/umn/en-us_image_0152754508.png b/docs/evs/umn/en-us_image_0152754508.png new file mode 100644 index 000000000..710c0102f Binary files /dev/null and b/docs/evs/umn/en-us_image_0152754508.png differ diff --git a/docs/evs/umn/en-us_image_0152756082.png b/docs/evs/umn/en-us_image_0152756082.png new file mode 100644 index 000000000..2ec0e0859 Binary files /dev/null and b/docs/evs/umn/en-us_image_0152756082.png differ diff --git a/docs/evs/umn/en-us_image_0154391346.png b/docs/evs/umn/en-us_image_0154391346.png new file mode 100644 index 000000000..c032754e6 Binary files /dev/null and b/docs/evs/umn/en-us_image_0154391346.png differ diff --git a/docs/evs/umn/en-us_image_0163801385.png b/docs/evs/umn/en-us_image_0163801385.png new file mode 100644 index 000000000..231e8177a Binary files /dev/null and b/docs/evs/umn/en-us_image_0163801385.png differ diff --git a/docs/evs/umn/en-us_image_0163801956.png b/docs/evs/umn/en-us_image_0163801956.png new file mode 100644 index 000000000..90915aa32 Binary files /dev/null and b/docs/evs/umn/en-us_image_0163801956.png differ diff --git a/docs/evs/umn/en-us_image_0169137709.png b/docs/evs/umn/en-us_image_0169137709.png new file mode 100644 index 000000000..ed446eb7a Binary files /dev/null and b/docs/evs/umn/en-us_image_0169137709.png differ diff --git a/docs/evs/umn/en-us_image_0169137710.png b/docs/evs/umn/en-us_image_0169137710.png new file mode 100644 index 000000000..a101fc539 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169137710.png differ diff --git a/docs/evs/umn/en-us_image_0169137711.png b/docs/evs/umn/en-us_image_0169137711.png new file mode 100644 index 000000000..a687679a5 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169137711.png differ diff --git a/docs/evs/umn/en-us_image_0169138641.png b/docs/evs/umn/en-us_image_0169138641.png new file mode 100644 index 000000000..9faea927e Binary files /dev/null and b/docs/evs/umn/en-us_image_0169138641.png differ diff --git a/docs/evs/umn/en-us_image_0169139666.png b/docs/evs/umn/en-us_image_0169139666.png new file mode 100644 index 000000000..eb9384ae8 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169139666.png differ diff --git a/docs/evs/umn/en-us_image_0169140345.png b/docs/evs/umn/en-us_image_0169140345.png new file mode 100644 index 000000000..01c7b3f57 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169140345.png differ diff --git a/docs/evs/umn/en-us_image_0169142103.png b/docs/evs/umn/en-us_image_0169142103.png new file mode 100644 index 000000000..b699ef7a9 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169142103.png differ diff --git a/docs/evs/umn/en-us_image_0169142386.png b/docs/evs/umn/en-us_image_0169142386.png new file mode 100644 index 000000000..576bc91bf Binary files /dev/null and b/docs/evs/umn/en-us_image_0169142386.png differ diff --git a/docs/evs/umn/en-us_image_0169142986.png b/docs/evs/umn/en-us_image_0169142986.png new file mode 100644 index 000000000..40c1ddbc9 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169142986.png differ diff --git a/docs/evs/umn/en-us_image_0169144806.png b/docs/evs/umn/en-us_image_0169144806.png new file mode 100644 index 000000000..ed1b18030 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144806.png differ diff --git a/docs/evs/umn/en-us_image_0169144807.png b/docs/evs/umn/en-us_image_0169144807.png new file mode 100644 index 000000000..b8a0aa400 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144807.png differ diff --git a/docs/evs/umn/en-us_image_0169144808.png b/docs/evs/umn/en-us_image_0169144808.png new file mode 100644 index 000000000..27b0e725a Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144808.png differ diff --git a/docs/evs/umn/en-us_image_0169144809.png b/docs/evs/umn/en-us_image_0169144809.png new file mode 100644 index 000000000..27216e177 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144809.png differ diff --git a/docs/evs/umn/en-us_image_0169144810.png b/docs/evs/umn/en-us_image_0169144810.png new file mode 100644 index 000000000..d72514e93 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144810.png differ diff --git a/docs/evs/umn/en-us_image_0169144811.png b/docs/evs/umn/en-us_image_0169144811.png new file mode 100644 index 000000000..41a73abec Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144811.png differ diff --git a/docs/evs/umn/en-us_image_0169144812.png b/docs/evs/umn/en-us_image_0169144812.png new file mode 100644 index 000000000..cad68e287 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144812.png differ diff --git a/docs/evs/umn/en-us_image_0169144813.png b/docs/evs/umn/en-us_image_0169144813.png new file mode 100644 index 000000000..348b6a840 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144813.png differ diff --git a/docs/evs/umn/en-us_image_0169144814.png b/docs/evs/umn/en-us_image_0169144814.png new file mode 100644 index 000000000..dbb9c3043 Binary files /dev/null and b/docs/evs/umn/en-us_image_0169144814.png differ diff --git a/docs/evs/umn/en-us_image_0171882862.png b/docs/evs/umn/en-us_image_0171882862.png new file mode 100644 index 000000000..73a5b03f0 Binary files /dev/null and b/docs/evs/umn/en-us_image_0171882862.png differ diff --git a/docs/evs/umn/en-us_image_0175083503.png b/docs/evs/umn/en-us_image_0175083503.png new file mode 100644 index 000000000..7f80d998d Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083503.png differ diff --git a/docs/evs/umn/en-us_image_0175083504.png b/docs/evs/umn/en-us_image_0175083504.png new file mode 100644 index 000000000..1e591003d Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083504.png differ diff --git a/docs/evs/umn/en-us_image_0175083507.png b/docs/evs/umn/en-us_image_0175083507.png new file mode 100644 index 000000000..b2f4f1f82 Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083507.png differ diff --git a/docs/evs/umn/en-us_image_0175083508.png b/docs/evs/umn/en-us_image_0175083508.png new file mode 100644 index 000000000..a248f9a38 Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083508.png differ diff --git a/docs/evs/umn/en-us_image_0175083509.png b/docs/evs/umn/en-us_image_0175083509.png new file mode 100644 index 000000000..0e734750c Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083509.png differ diff --git a/docs/evs/umn/en-us_image_0175083510.png b/docs/evs/umn/en-us_image_0175083510.png new file mode 100644 index 000000000..f7465ad17 Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083510.png differ diff --git a/docs/evs/umn/en-us_image_0175083511.png b/docs/evs/umn/en-us_image_0175083511.png new file mode 100644 index 000000000..e0db172fc Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083511.png differ diff --git a/docs/evs/umn/en-us_image_0175083512.png b/docs/evs/umn/en-us_image_0175083512.png new file mode 100644 index 000000000..cf9abaa9f Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083512.png differ diff --git a/docs/evs/umn/en-us_image_0175083513.png b/docs/evs/umn/en-us_image_0175083513.png new file mode 100644 index 000000000..55cd3fb1c Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083513.png differ diff --git a/docs/evs/umn/en-us_image_0175083515.png b/docs/evs/umn/en-us_image_0175083515.png new file mode 100644 index 000000000..e93f9d9f3 Binary files /dev/null and b/docs/evs/umn/en-us_image_0175083515.png differ diff --git a/docs/evs/umn/en-us_image_0184026531.png b/docs/evs/umn/en-us_image_0184026531.png new file mode 100644 index 000000000..1303a51c2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0184026531.png differ diff --git a/docs/evs/umn/en-us_image_0187937488.png b/docs/evs/umn/en-us_image_0187937488.png new file mode 100644 index 000000000..34a782fa8 Binary files /dev/null and b/docs/evs/umn/en-us_image_0187937488.png differ diff --git a/docs/evs/umn/en-us_image_0187940206.png b/docs/evs/umn/en-us_image_0187940206.png new file mode 100644 index 000000000..5d5b7e723 Binary files /dev/null and b/docs/evs/umn/en-us_image_0187940206.png differ diff --git a/docs/evs/umn/en-us_image_0187940368.png b/docs/evs/umn/en-us_image_0187940368.png new file mode 100644 index 000000000..60cb9dad8 Binary files /dev/null and b/docs/evs/umn/en-us_image_0187940368.png differ diff --git a/docs/evs/umn/en-us_image_0197136031.png b/docs/evs/umn/en-us_image_0197136031.png new file mode 100644 index 000000000..99e9a17be Binary files /dev/null and b/docs/evs/umn/en-us_image_0197136031.png differ diff --git a/docs/evs/umn/en-us_image_0205523160.png b/docs/evs/umn/en-us_image_0205523160.png new file mode 100644 index 000000000..9820353f7 Binary files /dev/null and b/docs/evs/umn/en-us_image_0205523160.png differ diff --git a/docs/evs/umn/en-us_image_0205531351.png b/docs/evs/umn/en-us_image_0205531351.png new file mode 100644 index 000000000..1c2df0088 Binary files /dev/null and b/docs/evs/umn/en-us_image_0205531351.png differ diff --git a/docs/evs/umn/en-us_image_0228748662.png b/docs/evs/umn/en-us_image_0228748662.png new file mode 100644 index 000000000..36e6d3231 Binary files /dev/null and b/docs/evs/umn/en-us_image_0228748662.png differ diff --git a/docs/evs/umn/en-us_image_0237893718.png b/docs/evs/umn/en-us_image_0237893718.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0237893718.png differ diff --git a/docs/evs/umn/en-us_image_0238263087.png b/docs/evs/umn/en-us_image_0238263087.png new file mode 100644 index 000000000..f4e325b3c Binary files /dev/null and b/docs/evs/umn/en-us_image_0238263087.png differ diff --git a/docs/evs/umn/en-us_image_0238263232.png b/docs/evs/umn/en-us_image_0238263232.png new file mode 100644 index 000000000..ad1a41d4b Binary files /dev/null and b/docs/evs/umn/en-us_image_0238263232.png differ diff --git a/docs/evs/umn/en-us_image_0238263336.png b/docs/evs/umn/en-us_image_0238263336.png new file mode 100644 index 000000000..a503fad87 Binary files /dev/null and b/docs/evs/umn/en-us_image_0238263336.png differ diff --git a/docs/evs/umn/en-us_image_0238263421.jpg b/docs/evs/umn/en-us_image_0238263421.jpg new file mode 100644 index 000000000..c95d289b7 Binary files /dev/null and b/docs/evs/umn/en-us_image_0238263421.jpg differ diff --git a/docs/evs/umn/en-us_image_0238302626.png b/docs/evs/umn/en-us_image_0238302626.png new file mode 100644 index 000000000..4e7be6a72 Binary files /dev/null and b/docs/evs/umn/en-us_image_0238302626.png differ diff --git a/docs/evs/umn/en-us_image_0269609232.png b/docs/evs/umn/en-us_image_0269609232.png new file mode 100644 index 000000000..e3201cb3a Binary files /dev/null and b/docs/evs/umn/en-us_image_0269609232.png differ diff --git a/docs/evs/umn/en-us_topic_0014580741.html b/docs/evs/umn/en-us_topic_0014580741.html new file mode 100644 index 000000000..9e6c0e037 --- /dev/null +++ b/docs/evs/umn/en-us_topic_0014580741.html @@ -0,0 +1,70 @@ + + +

What Is EVS?

+

Overview

Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and rich specifications, EVS disks can be used for distributed file systems, development and testing environments, data warehouse applications, and high-performance computing (HPC) scenarios to meet diverse service requirements. Servers that EVS supports include Elastic Cloud Servers (ECSs) and Bare Metal Servers (BMSs).

+

EVS disks are sometimes just referred to as disks in this document.

+
Figure 1 EVS architecture
+
+

EVS Advantages

EVS has the following advantages:

+
  • Various disk types

    EVS provides various disk types for you to choose from, and EVS disks can be used as data disks and system disks for servers. You may select the disk type based on your budget and service requirements.

    +
  • Elastic scalability

    The EVS disk capacity ranges from 10 GB to 32 TB. When it no longer meets your needs, you can expand the disk capacity up to 32 TB in increments of 1 GB, without interrupting your applications.

    +

    Besides the disk capacity limit, the additional space you can add cannot exceed the remaining quota. You can increase the quota if the remaining quota is insufficient.

    +
  • High security and reliability
    • Both system disks and data disks support data encryption to ensure data security.
    • Data protection functions, such as backups and snapshots, safeguard the disk data, preventing incorrect data caused by application exceptions or attacks.
    +
  • Real-time monitoring

    On Cloud Eye, you can monitor the disk health and operating status at any time.

    +
+
+

Differences Among EVS, SFS, and OBS

Currently, there are three data storage services available for you to choose from: EVS, Scalable File Service (SFS), and Object Storage Service (OBS). The differences are described in the following table.

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 Differences among EVS, SFS, and OBS

Service

+

Overall Introduction

+

Typical Application Scenarios

+

Storage Capacity

+

EVS

+

EVS provides scalable block storage that features high reliability, high performance, and rich specifications for servers.

+
  • Enterprise office applications
  • Development and testing
  • Enterprise applications, including SAP, Microsoft Exchange, and Microsoft SharePoint
  • Distributed file systems
  • Various databases, including MongoDB, Oracle, SQL Server, MySQL, and PostgreSQL
+

EVS disks start at 10 GB and can be expanded as required in 1 GB increments to up to 32 TB.

+

SFS

+

SFS provides completely hosted sharable file storage for ECSs. Compatible with the Network File System (NFS) protocol, SFS is expandable to petabytes and seamlessly handles data-intensive and bandwidth-intensive applications.

+
  • HPC scenarios, such as gene sequencing, animation rendering, and CAD/CAE
  • File sharing
  • Media processing
  • Content management and web services
  • Offline file backup
+

SFS storage capacity is available on demand and can be expanded to 10 PB at most.

+

OBS

+

OBS provides cloud storage for unstructured data, such as files, pictures, and videos. With multiple options for migration to the cloud, OBS provides low-cost, reliable storage access for massive data and supports online multimedia processing.

+
  • Enterprise backup and archive
  • Big data analysis
  • Enterprise cloud box
  • Static website hosting
  • Native cloud applications
+

OBS provides limitless storage capacity, and storage resources are available for linear and nearly infinite expansion.

+
+
+
+

User Permissions

Users with resource management permissions can control the operations performed on cloud service resources. For EVS, a user with the Server Administrator permission can perform operations on EVS resources, including creating disks, deleting disks, and creating snapshots.

+

For details about user permissions, see Permissions.

+
+

Project

A project is used to group and isolate OpenStack resources, including compute, storage, and network resources. A project can be a department or a project team. You can access IAM with a security administrator to create projects in a region and perform isolated management of resources. For details about projects, see Managing Projects.

+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0014580744.html b/docs/evs/umn/en-us_topic_0014580744.html new file mode 100644 index 000000000..f3a448166 --- /dev/null +++ b/docs/evs/umn/en-us_topic_0014580744.html @@ -0,0 +1,117 @@ + + +

Disk Types and Performance

+

EVS disks are classified based on the disk I/O performance. EVS disks differ in performance and price. Choose the disk type most appropriate for your applications.

+

Application Scenarios

  • Common I/O: EVS disks of this type deliver a maximum of 1,000 IOPS. This disk type is suitable for application scenarios that require large capacity, a medium read/write speed, and fewer transactions, such as enterprise office applications and small-scale testing.
  • High I/O: EVS disks of this type deliver a maximum of 3,000 IOPS and a minimum of 6 ms read/write latency. This disk type is designed to meet the needs of mainstream high-performance, high-reliability application scenarios, such as enterprise applications, large-scale development and testing, and web server logs.
  • Ultra-high I/O: EVS disks of this type deliver a maximum of 20,000 IOPS and a minimum of 1 ms read/write latency. This disk type is excellent for ultra-high I/O, ultra-high bandwidth, and read/write-intensive application scenarios, such as distributed file systems in HPC scenarios or NoSQL/relational databases in I/O-intensive scenarios.
  • High I/O (Performance optimized I): EVS disks of this type deliver a maximum of 550 MB/s throughput, which is higher than high I/O EVS disks. They are cost-effective and provide higher performance, optimizing both IOPS and bandwidth. Such disks are particularly suitable for hybrid load scenarios consisting of online analytical processing (OLAP) and online transaction processing (OLTP) or consisting of large and small HPC files.
  • Ultra-high I/O (Latency optimized): EVS disks of this type deliver a maximum of 1 GB/s throughput and a minimum of 1 ms read/write latency. They can be used for enterprise key services, such as SAP HANA.

    Currently, high I/O (performance optimized I) and ultra-high I/O (latency optimized) EVS disks can be attached to SAP HANA ECSs or HL1 ECSs only.

    +
    +
+
+

EVS Disk Performance

EVS disk performance metrics include:
  • IOPS: Number of read/write operations performed by an EVS disk per second
  • Throughput: Amount of data read from and written into an EVS disk per second
  • Read/write I/O latency: Minimum interval between two consecutive read/write operations on an EVS disk
+
+

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 EVS disk performance data

Parameter

+

Common I/O

+

High I/O

+

Ultra-high I/O

+

High I/O (Performance optimized I)

+

Ultra-high I/O (Latency optimized)

+

IOPS per GB/EVS disk

+

1

+

3

+

50

+

3

+

50

+

Min. IOPS/EVS disk

+

100

+

100

+

100

+

100

+

100

+

Max. IOPS/EVS disk

+

1,000

+

3,000

+

20,000

+

3,000

+

30,000

+

IOPS burst limit/EVS disk

+

1,000

+

3,000

+

10,000

+

3,000

+

15,000

+

Max. throughput

+

40 MB/s

+

120 MB/s

+

320 MB/s

+

550 MB/s

+

1 GB/s

+

Read/write I/O latency

+
NOTE:

This parameter specifies the single-queue access latencies of EVS disks.

+
+

10 ms to 15 ms

+

6 ms to 10 ms

+

1 ms to 3 ms

+

6 ms to 10 ms

+

1 ms

+
+
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0017616396.html b/docs/evs/umn/en-us_topic_0017616396.html new file mode 100644 index 000000000..f8f2943cc --- /dev/null +++ b/docs/evs/umn/en-us_topic_0017616396.html @@ -0,0 +1,81 @@ + + +

Extending Disk Partitions and File Systems (Windows Server 2008)

+

Scenarios

After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.

+

In Windows, you must allocate the additional space to an existing partition or a new partition.

+
This section uses Windows Server 2008 R2 Enterprise 64bit as the sample OS to describe the expansion methods: +
+
The method for allocating the additional space varies with the server OS. This section is used for reference only. For detailed operations and differences, see the corresponding OS documents.

Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using backups or snapshots before expansion. For details about backups, see Managing EVS Backup. For details about snapshots, see Creating a Snapshot.

+
+
+
+

Prerequisites

+
+

System Disk: Add Additional Space to Volume (C:)

In this example, the system disk has 50 GB originally, and 22 GB is added on the management console. The following procedure describes how to add this 22 GB to volume (C:) on the server. After the operation is complete, volume (C:) will have 72 GB of capacity and can be used as a system volume.

+
  1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

    The Server Manager window is displayed.

    +

  2. In the navigation tree, choose Storage > Disk Management.

    The Disk Management window is displayed.

    +
    Figure 1 Disk Management (system disk)
    +

    If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

    +
    +

  3. On the Disk Management page, select the disk and volume that you want to extend. The current volume size and unallocated space are displayed.
  4. Right-click the target volume and choose Extend Volume.

    Figure 2 Choosing Extend Volume
    +

  5. On the displayed Extend Volume Wizard window, click Next.

    Figure 3 Extend Volume Wizard
    +

  6. In the text box to the right of Select the amount of space in MB, enter the amount of the additional space and click Next.

    Figure 4 Selecting space
    +

  7. Click Finish.

    After the expansion succeeded, the partition size is larger than the original size.
    Figure 5 Capacity expansion succeeded
    +
    +

+
+

System Disk: Create New Volume (F:) with Additional Space

In this example, the system disk has 40 GB originally, and 60 GB is added on the management console. The following procedure describes how to use this 60 GB to create a new volume, for example volume (F:), on the server. After the operation is complete, new volume (F:) has 60 GB of capacity and can be used as a data volume.

+
  1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

    The Server Manager window is displayed.

    +

  2. In the navigation tree, choose Storage > Disk Management.

    The Disk Management window is displayed.
    Figure 6 Refresh (system disk)
    +
    +

  3. If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

    After the refresh, the additional space is displayed in the right area and is unallocated.

    +
    Figure 7 Unallocated disk space (system disk)
    +

  4. In the Unallocated area of Disk 0, right-click the blank area and choose New Simple Volume.

    Figure 8 New Simple Volume (system disk)
    +

  5. On the displayed New Simple Volume Wizard window, click Next.

    Figure 9 New Simple Volume Wizard (system disk)
    +

  6. On the displayed Specify Volume Size page, set Simple volume size in MB and click Next. In this example, the default size is used.

    Figure 10 Specify Volume Size (system disk)
    +

  7. On the displayed Assign Drive Letter and Path page, click Assign the following drive letter, select a drive letter, and click Next. In this example, drive letter F is selected.

    Figure 11 Assign Driver Letter or Path (system disk)
    +

  8. On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.

    Figure 12 Format Partition (system disk)
    +

  9. Click Finish.

    After the expansion succeeded, new volume (F:) is displayed.
    Figure 13 Completing the New Simple Volume Wizard (new volume F:)
    +
    Figure 14 New Volume (F:)
    +
    +

+
+

Data Disk: Add Additional Space to Volume (D:)

In this example, the data disk has 100 GB originally, and 50 GB is added on the management console. The following procedure describes how to add this 50 GB to volume (D:) on the server. After the operation is complete, volume (D:) has 150 GB of capacity and can be used as a data volume.

+
  1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

    The Server Manager window is displayed.

    +

  2. In the navigation tree, choose Storage > Disk Management.

    The Disk Management window is displayed.
    Figure 15 Disk Management (data disk)
    +

    If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

    +
    +
    +

  3. On the Disk Management page, select the disk and volume that you want to extend. The current volume size and unallocated space are displayed.
  4. Right-click the target volume and choose Extend Volume.

    Figure 16 Choosing Extend Volume (Windows Server 2008)
    +

  5. On the displayed Extend Volume Wizard window, click Next.

    Figure 17 Extend Volume Wizard (Windows Server 2008)
    +

  6. In the text box to the right of Select the amount of space in MB, enter the amount of the additional space and click Next.

    Figure 18 Selecting space (Windows Server 2008)
    +

  7. Click Finish.

    After the expansion succeeded, the partition size is larger than the original size.
    Figure 19 Capacity expansion succeeded (Windows Server 2008)
    +
    +

+
+

Data Disk: Create New Volume (E:) with Additional Space

In this example, the data disk has 40 GB originally, and 60 GB is added on the management console. The following procedure describes how to use this 60 GB to create a new volume, for example volume (E:), on the server. After the operation is complete, new volume (E:) has 60 GB of capacity and can be used as a data volume.

+
  1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

    The Server Manager window is displayed.

    +

  2. In the navigation tree, choose Storage > Disk Management.

    The Disk Management window is displayed.
    Figure 20 Refresh (data disk)
    +
    +

  3. If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

    After the refresh, the additional space is displayed in the right area and is unallocated.

    +
    Figure 21 Unallocated disk space (data disk)
    +

  4. In the Unallocated area of Disk 1, right-click the blank area and choose New Simple Volume.

    Figure 22 New Simple Volume (data disk)
    +

  5. On the displayed New Simple Volume Wizard window, click Next.

    Figure 23 New Simple Volume Wizard (data disk)
    +

  6. On the displayed Specify Volume Size page, set Simple volume size in MB and click Next. In this example, the default size is used.

    Figure 24 Specify Volume Size (data disk)
    +

  7. On the displayed Assign Drive Letter and Path page, click Assign the following drive letter, select a drive letter, and click Next. In this example, drive letter E is selected.

    Figure 25 Assign Driver Letter or Path (data disk)
    +

  8. On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.

    Figure 26 Format Partition (data disk)
    +

  9. Click Finish.

    After the expansion succeeded, new volume (E:) is displayed.
    Figure 27 Completing the New Simple Volume Wizard (new volume E:)
    +
    Figure 28 New Volume (E:)
    +
    +

+
+
+
+
+
Parent topic: Disk Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0021738346.html b/docs/evs/umn/en-us_topic_0021738346.html new file mode 100644 index 000000000..15893f652 --- /dev/null +++ b/docs/evs/umn/en-us_topic_0021738346.html @@ -0,0 +1,187 @@ + + +

Create an EVS Disk

+

Scenarios

EVS disks can be used as system disks or data disks for servers.

+
  • When a server is created, a system disk is automatically created and attached. You cannot create a system disk separately. The maximum size of a system disk is 1024 GB.
  • Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to the server. If you create data disks after the server creation, you need to manually attach the data disks. The maximum size of a data disk is 32768 GB.
+

This section describes how to separately create disks on the EVS console.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. Click Create Disk.

    • Figure 1 shows the parameter setting of non-encrypted disks.
      Figure 1 Non-encrypted disks
      +
    • Figure 2 shows the parameter setting of encrypted disks.
      Figure 2 Encrypted disks
      +
    +

  5. Configure basic disk information according to Table 1.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Region

    +

    Mandatory

    +

    Resources are region-specific and cannot be used across regions through internal network connections. For low network latency and quick resource access, select the nearest region.

    +

    eu-de

    +

    AZ

    +

    Mandatory

    +

    Specifies the availability zone (AZ) where you want to create the disk.

    +
    NOTE:
    • Disks can only be attached to the servers in the same AZ.
    • The AZ of a disk cannot be changed after the disk has been created.
    +
    +

    eu-de-1

    +

    Disk Type

    +

    Mandatory

    +
    • Common I/O
    • High I/O
    • Ultra-high I/O
    • High I/O (Performance optimized I)
    • Ultra-high I/O (Latency optimized)
    +
    NOTE:
    • When disks are created from backups:

      If the disk type of the backup's source disk is common I/O, high I/O, or ultra-high I/O, you can create disks of any of these types.

      +

      If the disk type of the backup's source disk is high I/O (performance optimized I) or ultra-high I/O (latency optimized), you can create disks of any of the two types.

      +
    • When a disk is created from a snapshot, the disk type of the newly created disk will be consistent with that of the snapshot's source disk.
    • For details about disk types, see Disk Types and Performance.
    +
    +

    Common I/O

    +

    Capacity (GB)

    +

    Mandatory

    +

    Specifies the disk size. Only data disks can be created on the current page, and the disk capacity ranges from 10 GB to 32768 GB.

    +
    NOTE:
    • When you use a backup to create a disk, the disk capacity must be greater than or equal to the backup size. In the condition that you do not specify the disk capacity, if the backup size is smaller than 10 GB, the default capacity 10 GB will be used as the disk capacity; if the backup size is greater than 10 GB, the disk capacity will be consistent with the backup size.
    • When you use a snapshot to create a disk, the disk capacity must be greater than or equal to the snapshot size. In the condition that you do not specify the disk capacity, if the snapshot size is smaller than 10 GB, the default capacity 10 GB will be used as the disk capacity; if the snapshot size is greater than 10 GB, the disk capacity will be consistent with the snapshot size.
    +
    +

    20 GB

    +

    Create from backup

    +

    Optional

    +

    Specifies to create the disk from a backup.

    +

    Click Select Data Source and choose Create from backup. On the displayed page, select the target backup and click OK.

    +
    NOTE:
    • You can select a backup created by the current tenant or shared with the current tenant by another tenant.
    • One backup cannot be used for concurrent disk creation operations at the same time. For example, if you are creating disk A from a backup, this backup can be used to create another disk only after disk A has been created.
    • If a disk is created from a backup of a system disk, the new disk can be used as a data disk only.
    +
    +

    autobackup-001

    +

    Create from snapshot

    +

    Optional

    +

    Specifies to create the disk from a snapshot.

    +

    Click Select Data Source and choose Create from snapshot. On the displayed page, select the target snapshot and click OK.

    +
    NOTE:
    • The disk type of the new disk is the same as that of the snapshot's source disk.
    • The device type of the new disk is the same as that of the snapshot's source disk.
    • The encryption attribute of the new disk is the same as that of the snapshot's source disk.
    +

    For details about the disk creation from snapshots, see Creating an EVS Disk from a Snapshot.

    +
    +

    snapshot-001

    +

    Auto Backup

    +

    Optional

    +

    If auto backup is enabled, the system automatically creates backups for the disk data at specified time points and deletes outdated backups according to the configured backup policy.

    +

    When Enable is selected, a backup policy must be configured. You can either use the default backup policy or customize the policy based on your service requirements.

    +
    NOTE:

    For details about the backup policy, see Managing EVS Backup.

    +
    +

    -

    +

    Share

    +

    Optional

    +
    • If Share is not selected, a common disk is created.
    • If Share is selected, a shared disk is created, and the shared disk can be attached to multiple servers.
    +

    If both SCSI and Share are selected, a shared SCSI disk is created.

    +
    NOTE:

    The sharing attribute of a disk cannot be changed after the disk has been created.

    +

    For details about shared EVS disks, see Managing a Shared EVS Disk.

    +
    +

    -

    +

    SCSI

    +

    Optional

    +
    • If SCSI is not selected, a VBD disk is created. VBD is the default device type of EVS disks.
    • If SCSI is selected, a SCSI disk is created. Such disks allow the server OS to directly access the underlying storage media and send SCSI commands to the disks.
    +
    NOTE:

    The device type of a disk cannot be changed after the disk has been created.

    +

    For details about the ECS types, OSs, and ECS software supported by SCSI EVS disks, see Device Types and Usage Instructions.

    +
    +

    -

    +

    Encryption

    +

    Optional

    +

    Disk encryption is used for data disk encryption only. For system disk encryption, see the Image Management Service User Guide.

    +

    To use the disk encryption function, select Encryption. The displayed dialog box contains the following parameters:

    +
    • Create Agency

      An agency is a trust relationship between two tenants or services. A tenant can create an agency to grant resource access rights to another tenant or service. If the KMS access rights are not granted to EVS, the Create Agency dialog box will be displayed. Otherwise, it will not be displayed.

      +

      Click Yes to grant the KMS access rights to EVS. After the rights have been granted, EVS can obtain KMS keys to encrypt or decrypt EVS disks.

      +

      After the KMS access rights have been granted, follow-up operations do not require the rights to be granted again.

      +
    +
    • KMS Key Name
      NOTE:

      KMS Key Name is displayed only after the KMS access rights have been granted. For details, see "Create Agency" above.

      +
      +
      KMS Key Name is the identifier of the key, and you can use KMS Key Name to specify the KMS key that is to be used for encryption. One of the following keys can be used:
      • Default Master Key: After the KMS access rights have been granted to EVS, the system automatically creates a Default Master Key and names it evs/default.
      • CMKs: Existing or newly created CMKs. For details, see Management > Creating a CMK in the Key Management Service User Guide.
      +
      +
    +
    NOTE:
    • Before you use the EVS disk encryption function, KMS access rights need to be granted to EVS. If you have the right to grant the permission, grant the KMS access rights to EVS directly. If you do not have this permission, contact a user with the security administrator rights to grant KMS access rights to EVS, then repeat the preceding operations.
    • The encryption attribute of a disk cannot be changed after the disk has been created.
    +

    For details, see EVS Disk Encryption.

    +
    +

    -

    +

    Tag

    +

    Optional

    +

    During the EVS disk creation, you can tag the EVS resources. Tags identify cloud resources for purposes of easy categorization and quick search.

    +
    A tag is composed of a key-value pair.
    • Key: Mandatory if the disk is going to be tagged
      • Must be unique for each resource.
      • Can contain a maximum of 36 characters.
      • Can contain only digits, letters, hyphens (-), and underscores (_).
      +
    • Value: Optional if the disk is going to be tagged
      • Can contain a maximum of 43 characters.
      • Can contain only digits, letters, hyphens (-), and underscores (_).
      +
    +
    NOTE:
    • A maximum of 10 tags can be added for an EVS disk.
    • Tag keys of the same EVS disk must be unique.
    • Except for tagging the disk during disk creation, you can also add, modify, or delete tags for existing disks. For details, see Managing a Tag.
    +

    For details about tags, see the Tag Management Service User Guide.

    +
    +
    +

    -

    +

    Disk Name

    +

    Mandatory

    +
    • If you create disks individually, this parameter value is used as the actual disk name.

      The name can contain a maximum of 64 characters.

      +
    • If you create disks in a batch, this parameter value is used as the prefix of disk names, and one disk name will be composed of this parameter value and a four-digit number.

      The name can contain a maximum of 59 characters.

      +
    +

    For example, if you create two disks and set volume for Disk Name, the EVS disk names will be volume-0001 and volume-0002.

    +

    Quantity

    +

    Optional

    +

    Specifies the number of disks to be created. The default value is set to 1, which means only one disk is created. Currently, you can create up to 100 disks at a time.

    +
    NOTE:
    • If the disk is created from a backup, batch creation is not possible, and this parameter must be set to 1.
    • If the disk is created from a snapshot, batch creation is not possible, and this parameter must be set to 1.
    +
    +

    1

    +
    +
    +

  6. Click Create Now.
  7. On the Details page, check the disk details.

    • If you do not need to modify the specifications, click Submit to start the creation.
    • If you need to modify the specifications, click Previous to modify parameters.
    +

  8. Go back to the disk list page and view the disk status.

    When the disk status changes to Available, the disk is successfully created.

    +

+
+
+
+
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0032860759.html b/docs/evs/umn/en-us_topic_0032860759.html new file mode 100644 index 000000000..4bf098aed --- /dev/null +++ b/docs/evs/umn/en-us_topic_0032860759.html @@ -0,0 +1,42 @@ + + +

Shared EVS Disks and Usage Instructions

+

What Are Shared EVS Disks?

Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multiple servers. Shared EVS disks feature multiple attachments, high-concurrency, high-performance, and high-reliability. They are usually used for enterprise business-critical applications that require cluster deployment. Multiple servers can access the same shared EVS disk at the same time.

+

A shared EVS disk can be attached to a maximum of 16 servers. Servers that EVS supports include ECSs and BMSs. To achieve file sharing, you need to deploy a shared file system or a cluster management system, such as Windows MSCS, Veritas VCS, or CFS.

+

To use shared EVS disks, you must set up a shared file system or similar cluster management system. If you directly attach EVS disks to multiple servers, the EVS disks cannot be shared and data may be overwritten.

+
+
+
Figure 1 Application scenario of shared EVS disks
+

Usage Precautions

Most common clusters, such as Windows MSCS and Veritas VCS and CFS, require SCSI reservations. Therefore, you are advised to use shared SCSI EVS disks for clusters. If a SCSI EVS disk is attached to a Xen ECS for use, you must install the driver. For details, see Device Types and Usage Instructions.

+
You can create shared VBD disks or shared SCSI disks. It is recommended that you attach the shared disk to the ECSs in the same ECS group to improve service reliability.
  • Shared VBD EVS disks: The device type of a newly created shared EVS disk is VBD by default. Such disks can be used as virtual block storage devices, but do not support SCSI reservations. If SCSI reservations are required for your applications, create shared SCSI EVS disks.
  • Shared SCSI EVS disks: These EVS disks support SCSI reservations.
    • To improve data security, you are advised to use SCSI reservations together with the anti-affinity policy of an ECS group. That said, ensure that shared SCSI EVS disks are only attached to ECSs in the same anti-affinity ECS group.
    • If an ECS does not belong to any anti-affinity ECS group, you are advised not to attach shared SCSI EVS disks to this ECS. Otherwise, SCSI reservations may not work properly, which may put your data at risk.
    +
    +

    Concepts of the anti-affinity ECS group and SCSI reservations:

    +
    • The anti-affinity policy of an ECS group allows ECSs to be created on different physical servers to improve service reliability.

      For details about ECS groups, see Managing ECS Groups in the Elastic Cloud Server User Guide.

      +
    • The SCSI reservation mechanism uses a SCSI reservation command to perform SCSI reservation operations. If an ECS sends such a command to an EVS disk, the disk is displayed as locked to other ECSs, preventing the data damage that may be caused by simultaneous read/write operations to the disk from multiple ECSs.
    • ECS groups and SCSI reservations have the following relationship: A SCSI reservation on a single EVS disk cannot differentiate multiple ECSs on the same physical host. For that reason, if multiple ECSs that use the same shared EVS disk are running on the same physical host, SCSI reservations will not work properly. Therefore, you are advised to use SCSI reservations only on ECSs that are in the same ECS group, thus having a working anti-affinity policy.
    +
+
+
+

Advantages

  • Multiple attachments: A shared EVS disk can be attached to a maximum of 16 servers.
  • High-performance: When multiple servers concurrently access a shared ultra-high I/O EVS disk, random read/write IOPS can reach up to 160,000.
  • High-reliability: Shared EVS disks support both manual and automatic backup, delivering highly reliable data storage.
  • Wide application scenarios: Shared EVS disks can be used for Linux RHCS clusters where only VBD EVS disks are needed. Whereas, they can also be used for Windows MSCS and Veritas VCS clusters that require SCSI reservations.
+
+

Specifications and Performance

The specifications and performance of shared EVS disks are the same as those of non-shared EVS disks. For details, see Disk Types and Performance.

+
+

Data Sharing Principle and Common Usage Mistakes

A shared EVS disk is essentially the disk that can be attached to multiple servers for use, which is similar to a physical disk in that the disk can be attached to multiple physical servers, and each server can read data from and write data into any space on the disk. If the data read/write rules, such as the read/write sequence and meaning, between these servers are not defined, data read/write interference between servers or other unpredictable errors may occur.

+

Though shared EVS disks are block storage devices that provide shared access for servers, shared EVS disks do not have the cluster management capability. Therefore, you need to deploy a cluster system to manage shared EVS disks. Common cluster management systems include Windows MSCS, Linux RHCS, Veritas VCS, and Veritas CFS.

+
If shared EVS disks are not managed by a cluster system, the following issues may occur:
  • Data inconsistency caused by read/write conflicts

    When a shared EVS disk is attached to two servers (server A and server B), server A cannot recognize the disk spaces allocated to server B, vice versa. That said, a disk space allocated to server A may be already used by server B. In this case, repeated disk space allocation occurs, which leads to data errors.

    +

    For example, a shared EVS disk has been formatted into the ext3 file system and attached to server A and server B. Server A has written metadata into the file system in space R and space G. Then server B has written metadata into space E and space G. In this case, the data written into space G by server A will be replaced. When the metadata in space G is read, an error will occur.

    +
  • Data inconsistency caused by data caching

    When a shared EVS disk is attached to two servers (server A and server B), the application on server A has read the data in space R and space G, then cached the data. At that time, other processes and threads on server A would then read this data directly from the cache. At the same time, if the application on server B has modified the data in space R and space G, the application on server A cannot detect this data change and still reads this data from the cache. As a result, the user cannot view the modified data on server A.

    +

    For example, a shared EVS disk has been formatted into the ext3 file system and attached to server A and server B. Both servers have cached the metadata in the file system. Then server A has created a new file (file F) on the shared disk, but server B cannot detect this modification and still reads data from its cached data. As a result, the user cannot view file F on server B.

    +
+
+

Before you attach a shared EVS disk to multiple servers, the disk device type needs to be determined. The device type can be either VBD or SCSI. Shared SCSI EVS disks support SCSI reservations. Before using SCSI reservations, you need to install a driver in the server OS and ensure that the OS image is included in the compatibility list.

+

For details about the usages of shared EVS disks, see Managing a Shared EVS Disk.

+

If you simply attach a shared EVS disk to multiple servers, files cannot be shared between the servers as shared EVS disks do not have the cluster capability. Therefore, build a shared file system or deploy a cluster management system if you need to share files between servers.

+
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0052554220.html b/docs/evs/umn/en-us_topic_0052554220.html new file mode 100644 index 000000000..5338b1ea0 --- /dev/null +++ b/docs/evs/umn/en-us_topic_0052554220.html @@ -0,0 +1,55 @@ + + +

Device Types and Usage Instructions

+

What Device Types Are Available?

There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).
  • VBD is the default EVS device type. VBD EVS disks support only basic read/write SCSI commands.
  • SCSI EVS disks support transparent SCSI command transmission and allow the server OS to directly access the underlying storage media. Besides basic read/write SCSI commands, SCSI disks support advanced SCSI commands.
+
+

Device type is configured during creation. It cannot be changed after the disk has been created.

+
+

Common Application Scenarios and Usage Instructions of SCSI EVS Disks

  • BMSs support only SCSI EVS disks.
  • Shared SCSI EVS disks: Shared SCSI EVS disks must be used together with a distributed file system or cluster software. Because most cluster applications, such as Windows MSCS, Veritas VCS, and Veritas CFS, require the usage of SCSI reservations, you are advised to use shared EVS disks with SCSI.

    SCSI reservations take effect only when shared SCSI EVS disks are attached to ECSs in the same ECS group. For more information about shared EVS disks, see Shared EVS Disks and Usage Instructions.

    +
+
+

Do I Need to Install a Driver for SCSI EVS Disks?

To use SCSI EVS disks, you need to install a driver for certain server OSs.
  • BMS

    Both the Windows and Linux images for BMSs are pre-installed with the required SDI card driver. Therefore, no driver needs to be installed.

    +
  • KVM ECS

    You are advised to use SCSI EVS disks with KVM ECSs. Linux images and Windows images for KVM ECSs already have the required driver. Therefore, no driver needs to be installed for KVM ECSs.

    +

    ECS virtualization types are categorized into KVM and Xen. For details, see ECS Types.

    +
    +
  • Xen ECS

    Due to driver limitations, you are advised not to use SCSI EVS disk with Xen ECSs.

    +
    However, a few images support SCSI EVS disks on Xen ECSs. For the supported images, see Table 1.

    After confirming that the OS images of Xen ECSs support SCSI EVS disks, determine whether you need to install the driver:

    +
    • Public Windows images are preinstalled with the Paravirtual SCSI (PVSCSI) driver. Therefore, no driver needs to be installed.
    • Private Windows images are not preinstalled with the PVSCSI driver. You need to download and install it explicitly.

      For details, see (Optional) Optimizing Windows Private Images in the Image Management Service User Guide.

      +
    • Linux images are not preinstalled with the PVSCSI driver. You need to obtain the source code of the open-source Linux driver at https://github.com/UVP-Tools/SAP-HANA-Tools.

      Note that this driver is different from the PVSCSI drivers attached to some Linux distributions.

      +
    +
    +
    +
    +
    + + + + + + + + + + + +
    Table 1 OSs supporting SCSI EVS disks

    Virtualization Type

    +

    OS

    +

    Xen

    +

    Windows

    +

    See the Windows images listed on the Public Images page.

    +

    Log in to the management console, choose Image Management Service, click the Public Images tab, and select ECS image and Windows from the drop-down lists, respectively.

    +

    Linux

    +
    • SUSE Linux Enterprise Server 11 SP4 64bit (The kernel version is 3.0.101-68-default or 3.0.101-80-default.)
    • SUSE Linux Enterprise Server 12 64bit (The kernel version is 3.12.51-52.31-default.)
    • SUSE Linux Enterprise Server 12 SP1 64bit (The kernel version is 3.12.67-60.64.24-default.)
    • SUSE Linux Enterprise Server 12 SP2 64bit (The kernel version is 4.4.74-92.35.1-default.)
    +
    +
    +
    +
+
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0066615262.html b/docs/evs/umn/en-us_topic_0066615262.html new file mode 100644 index 000000000..8f7758dfa --- /dev/null +++ b/docs/evs/umn/en-us_topic_0066615262.html @@ -0,0 +1,81 @@ + + +

Creating a Snapshot

+

Scenarios

You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.

+
+

Constraints

  • A maximum of 7 snapshots can be created for one disk.
  • Snapshots can be created for both system disks and data disks.
+
+

Creating a Snapshot on the Disks Page

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the disk list, locate the row that contains the target disk, click More in the Operation column, and choose Create Snapshot.

    Configure the basic settings for the snapshot according to Table 1.

    + +
    + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Snapshot Name

    +

    Mandatory

    +

    The name can contain a maximum of 64 characters.

    +

    snapshot-01

    +
    +
    +

  5. Click Create Now.
  6. Return to the Snapshots page to view the snapshot creation information.

    When the snapshot status changes to Available, the snapshot has been created.

    +

+
+

Creating a Snapshot on the Snapshots Page

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the navigation pane on the left, choose Elastic Volume Service > Snapshots.

    On the Snapshots page, click Create Snapshot.

    +

    Configure the basic settings for the snapshot according to Table 2.

    + +
    + + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Region

    +

    Mandatory

    +

    After you select a region, disks in the selected region will be displayed for you to choose.

    +

    -

    +

    Snapshot Name

    +

    Mandatory

    +

    The name can contain a maximum of 64 characters.

    +

    snapshot-01

    +

    Select Disk

    +

    Mandatory

    +

    Select a disk based on which the snapshot is to be created.

    +

    volume-01

    +
    +
    +

  5. Click Create Now.
  6. Return to the Snapshots page to view the snapshot creation information.

    When the snapshot status changes to Available, the snapshot has been created.

    +

+
+
+
+
+
Parent topic: Managing Snapshots
+
+
+ diff --git a/docs/evs/umn/en-us_topic_0066809008.html b/docs/evs/umn/en-us_topic_0066809008.html new file mode 100644 index 000000000..fd205fccc --- /dev/null +++ b/docs/evs/umn/en-us_topic_0066809008.html @@ -0,0 +1,25 @@ + + +

EVS Snapshot

+

What Is EVS Snapshot?

EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific time point. As a major disaster recovery (DR) approach, you can use a snapshot to completely restore the data to the time point when the snapshot was created.

+

EVS snapshots are sometimes referred to as snapshots in this document.

+

You can create snapshots to rapidly save the disk data at specified time points. In addition, you can use snapshots to create new disks so that the created disks will contain the snapshot data in the beginning.

+
+

Application Scenarios

The snapshot function helps address your following needs:

+
  • Routine data backup

    You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data loss or data inconsistency occurred due to misoperations, viruses, or attacks.

    +
  • Rapid data restoration

    You can create a snapshot or multiple snapshots before an application software upgrade or a service data migration. If an exception occurs during the upgrade or migration, service data can be rapidly restored to the time point when the snapshot was created.

    +

    For example, a fault occurred on system disk A of server A, and therefore server A cannot be started. Because system disk A is already faulty, the data on system disk A cannot be restored by rolling back snapshots. However, you can create disk B using an existing snapshot of system disk A and attach disk B to a properly running server, for example server B. In this case, server B can read the data of system disk A from disk B.

    +

    Currently, when rolling back data from snapshots, the snapshot data can be rolled back only to its source EVS disk, and a rollback to another EVS disk is not possible.

    +
    +
  • Multi-service quick deployment

    You can use a snapshot to create multiple disks containing the same initial data, and these disks can be used as data resources for various services, for example data mining, report query, and development and testing. This method protects the initial data and creates disks rapidly, meeting the diversified service data requirements.

    +
+
+

Usage Instructions

For details about the snapshot usages, see Managing Snapshots.

+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0001.html b/docs/evs/umn/evs_01_0001.html new file mode 100644 index 000000000..670f3a6be --- /dev/null +++ b/docs/evs/umn/evs_01_0001.html @@ -0,0 +1,67 @@ + + +

EVS Disk Encryption

+

What Is EVS Disk Encryption?

In case your services require encryption for the data stored on EVS disks, EVS provides you with the encryption function. You can encrypt newly created EVS disks.

+

EVS uses the industry-standard XTS-AES-256 encryption algorithm and keys to encrypt EVS disks. Keys used by encrypted EVS disks are provided by the Key Management Service (KMS), which is secure and convenient. Therefore, you do not need to establish and maintain the key management infrastructure. KMS uses the Hardware Security Module (HSM) that complies with FIPS 140-2 level 3 requirements to protect keys. All user keys are protected by the root key in HSM to prevent key exposure.

+
+

Keys Used for EVS Disk Encryption

The keys provided by KMS include a Default Master Key and Customer Master Keys (CMKs).
  • Default Master Key: A key that is automatically created by EVS through KMS and named evs/default.

    The Default Master Key cannot be disabled and does not support scheduled deletion.

    +
  • CMKs: Keys created by users. You may use existing CMKs or create new CMKs to encrypt disks. For details, see Management > Creating a CMK in the Key Management Service User Guide.
+
+
If disks are encrypted using CMKs and a CMK is then disabled or scheduled for deletion, the disks encrypted by this CMK can no longer be read from or written to and data on these disks may never be restored. See Table 1 for more information. +
+ + + + + + + + + + + + + + + +
Table 1 Impact of CMK unavailability

CMK Status

+

Impact

+

How to Restore

+

Disabled

+
  • For an encrypted disk already attached:

    The disk cannot be accessed after a period of time, or the disk data can never be restored. If the disk is detached later, it cannot be attached again.

    +
  • For an encrypted disk not attached:

    The disk cannot be attached anymore.

    +
+

Enable the CMK. For details, see Managing CMKs > Enabling One or More CMKs in the Key Management Service User Guide.

+

Scheduled deletion

+

Cancel the scheduled deletion for the CMK. For details, see Managing CMKs > Canceling the Scheduled Deletion of One or More CMKs in the Key Management Service User Guide.

+

Deleted

+

Data on the disks can never be restored.

+
+
+
+
+

Who Can Use the Disk Encryption Function?

  • The security administrator (having the Security Administrator rights) can grant the KMS access rights to EVS for using the disk encryption function.
  • When a common user who does not have the Security Administrator rights needs to use the disk encryption function, the condition varies depending on whether the user is the first one ever in the current region or project to use this feature.
    • If the common user is the first one ever in the current region or project to use the feature, the user must contact a user having the Security Administrator rights to grant the KMS access rights to EVS. Then, the common user can use the disk encryption function.
    • If the common user is not the first one ever in the current region or project to use the feature, the common user can use the disk encryption function directly.
    +
+

From the perspective of a tenant, as long as the KMS access rights have been granted to EVS in a region, all the users in the same region can directly use the disk encryption function.

+

If there are multiple projects in the current region, the KMS access rights need to be granted to each project in this region.

+
+

Application Scenarios of EVS Disk Encryption

Figure 1 shows the user relationships under regions and projects from the perspective of a tenant. The following example uses region B to describe the two application scenarios of the disk encryption function.

+
Figure 1 User relationships
+
  • If the security administrator uses the encryption function for the first time ever, the operation process is as follows:
    1. Grant the KMS access rights to EVS.

      After the KMS access rights have been granted, the system automatically creates a Default Master Key and names it evs/default. DMK can be used for disk encryption.

      +

      The EVS disk encryption relies on KMS. When the encryption function is used for the first time ever, the KMS access rights need to be granted to EVS. After the KMS access rights have been granted, all users in this region can use the encryption function, without requiring the KMS access rights to be granted again.

      +
      +
    2. Select a key.
      You can select one of the following keys:
      • DMK: evs/default
      • CMKs: Existing or newly created CMKs. For details, see Creating a CMK in the Key Management Service User Guide.
      +
      +
    +

    After the security administrator has used the disk encryption function, all users in Region B can directly use the encryption function.

    +
  • If User E (common user) uses the encryption function for the first time ever, the operation process is as follows:
    1. When user E uses the encryption function, and the system prompts a message indicating that the KMS access rights have not been granted to EVS.
    2. Contact the security administrator to grant the KMS access rights to EVS.
    +

    After the KMS access rights have been granted to EVS, User E as well as all users in Region B can directly use the disk encryption function and do not need to contact the security administrator to grant the KMS access rights to EVS again.

    +
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0002.html b/docs/evs/umn/evs_01_0002.html new file mode 100644 index 000000000..76b42714d --- /dev/null +++ b/docs/evs/umn/evs_01_0002.html @@ -0,0 +1,13 @@ + + +

Detaching an EVS Disk

+
+ + diff --git a/docs/evs/umn/evs_01_0003.html b/docs/evs/umn/evs_01_0003.html new file mode 100644 index 000000000..8267fd3b3 --- /dev/null +++ b/docs/evs/umn/evs_01_0003.html @@ -0,0 +1,25 @@ + + +

Detaching a System Disk

+

Scenarios

A system disk can only be detached offline, that is, its server must be in the Stopped state before the system disk is detached. Therefore, you need to first stop the server and then detach the system disk.

+
For the system disk attached to a server, the disk function is displayed as System disk, and the disk status is displayed as In-use in the disk list. After a system disk is detached from the server, the disk function changes to Bootable disk, and the status changes to Available.

Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the device name selected.

+
+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Compute, click Elastic Cloud Server.

    The Elastic Cloud Server page is displayed.

    +

  4. In the server list, locate the row that contains the server whose system disk is to be detached, click More in the Operation column, and choose Stop.

    When the server status changes to Stopped, the server has been stopped.

    +

  5. Click the name of this server.

    The server details page is displayed.

    +

  6. Click the Disks tab to view the system disk attached to the server.
  7. Locate the row that contains the system disk and click Detach.

    The Detach Disk dialog box is displayed, as shown in Figure 1.
    Figure 1 Detach Disk (system disk)
    +
    +

  8. Click Yes to detach the disk.

    After the operation had succeeded, the detached system disk is no longer displayed under the Disks tab.

    +

+
+

Related Operations

For more detachment FAQs, see Detachment.

+
+
+
+
+
Parent topic: Detaching an EVS Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0004.html b/docs/evs/umn/evs_01_0004.html new file mode 100644 index 000000000..a1fc6d3bd --- /dev/null +++ b/docs/evs/umn/evs_01_0004.html @@ -0,0 +1,47 @@ + + +

Detaching a Data Disk

+

Scenarios

Data disks can be detached online or offline, which means that the server containing the to-be-detached data disk can either be in the Running or Stopped state.
  • ECS

    Detach a disk online. For details, see Storage > Detaching an EVS Disk from a Running ECS in the Elastic Cloud Server User Guide.

    +
  • BMS

    SCSI disks can be attached to BMSs and used as data disks. You can detach a data disk either from a running or stopped BMS.

    +
+
+

For a data disk attached to a server, the disk function is displayed as Data disk, and the disk status is displayed as In-use in the disk list. After the data disk has been detached from the server, the disk function remains unchanged, the disk status changes to Available for a non-shared data disk, and the disk status changes to Available for a shared data disk after it is detached from all its servers.

+
+

Prerequisites

  • Before detaching an EVS disk from a running Windows ECS, ensure that no program is reading data from or writing data to the disk. Otherwise, data will be lost.
+
  • Before detaching an EVS disk from a running Linux ECS, you must log in to the ECS and run the umount command to cancel the association between the disk and the file system. In addition, ensure that no program is reading data from or writing data to the disk. Otherwise, detaching the disk will fail.
+
+

Detaching a Non-shared Disk

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. Determine whether to view the server information before detaching the disk.

    • If you need to view the server information, perform the following procedure:
      1. In the disk list, click the name of the to-be-detached disk.

        The disk details page is displayed.

        +
      2. Click the Attachments tab to view the server where the target disk has been attached.
      3. Click to select the server and click Detach Disk.
        The Detach Disk dialog box is displayed, as shown in Figure 1.
        Figure 1 Detach Disk
        +
        +
      4. Click Yes to detach the disk.
      +
    • If you do not need to view the server information, perform the following procedure:
      1. In the disk list, locate the row that contains the target disk and choose More > Detach in the Operation column.
        The Detach Disk dialog box is displayed, as shown in Figure 2.
        Figure 2 Detach Disk dialog box
        +
        +
      2. Click Yes to detach the disk.
      +
    +

    The disk list is displayed. The disk status is Detaching, indicating that the disk is being detached from the server.

    +

    When the status changes to Available, the disk is successfully detached.

    +

+
+

Detaching a Shared Disk

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. Determine whether to view the server information before detaching the disk.

    • If you need to view the server information, perform the following procedure:
      1. In the disk list, click the name of the to-be-detached disk.

        The disk details page is displayed.

        +
      2. Click the Attachments tab to view the servers where the target disk has been attached.
      3. Click to select the server and click Detach Disk.

        Shared EVS disks support batch detachment so that you can select multiple servers at a time.

        +
        The Detach Disk dialog box is displayed, as shown in Figure 3.
        Figure 3 Detaching a shared disk
        +
        +
      4. Click Yes to detach the disk.
      +
    • If you do not need to view the server information, perform the following procedure:
      1. In the disk list, locate the row that contains the target disk and choose More > Detach in the Operation column.
        The Detach Disk dialog box is displayed, as shown in Figure 4.
        Figure 4 Detaching a shared disk dialog box
        +
        +
      2. Click to select the server.

        Shared EVS disks support batch detachment so that you can select multiple servers at a time.

        +
      3. Click Yes to detach the disk.
      +
    +

    The disk list page is displayed. The disk status is Detaching, indicating that the disk is being detached from the server.

    +

    If the shared EVS disk has been attached to multiple servers and needs to be detached from only some of its servers, the disk status will go back to In-use after the disk has been detached from the target servers. The disk status changes to Available only when it has been detached from all the servers.

    +

+
+
+
+
+
Parent topic: Detaching an EVS Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0005.html b/docs/evs/umn/evs_01_0005.html new file mode 100644 index 000000000..d406b4c96 --- /dev/null +++ b/docs/evs/umn/evs_01_0005.html @@ -0,0 +1,13 @@ + + +

Deleting an EVS Disk

+

Scenarios

If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.

+
  • Before deleting a disk, ensure that the disk status is Available, Error, Expansion failed, Restoration failed, or Rollback failed.
  • Before deleting a shared disk, ensure that the disk has been detached from all its servers.
+
+
  • When you delete a disk, all the disk data including the snapshots created for this disk will be deleted. Exercise caution when performing this operation.
  • A deleted disk cannot be recovered.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the disk list, locate the row that contains the target disk, click More in the Operation column, and choose Delete.
  5. (Optional) If multiple disks are to be deleted, select in front of each disk and click Delete in the upper area of the list.
  6. In the displayed dialog box, confirm the information and click Yes.
+
+
+ diff --git a/docs/evs/umn/evs_01_0006.html b/docs/evs/umn/evs_01_0006.html new file mode 100644 index 000000000..553c67817 --- /dev/null +++ b/docs/evs/umn/evs_01_0006.html @@ -0,0 +1,49 @@ + + +

Expansion Overview

+

What Is Capacity Expansion?

If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.

+

Both system disks and data disks can be expanded. Currently, disk capacities can be expanded only. Capacity reduction is not supported.

+
+

How to Expand the Disk Capacity?

A capacity expansion operation includes the following steps:

+
  1. Expand the disk capacity on the management console.
  2. Log in to the server and extend the disk partition and file system.
+
Figure 1 Capacity expansion procedure
+
+

Expand the Disk Capacity on the Management Console

Choose a proper expansion method based on the disk status. +
+
+

Log In to the Server and Extend the Disk Partition and File System

After the disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the server and extend the disk partition and file system. For details, see Table 1. +
+ + + + + + + + + + +
Table 1 Extending the disk partition and file system

Capacity After Expansion

+

Extend Disk Partition and File System

+

Disk capacity ≤ 2 TB

+		 +

Disk capacity > 2 TB

+		 +
+
+
+
+

Related Operations

For more expansion FAQs, see Capacity Expansion.

+
+
+
+
+
Parent topic: Disk Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_01_0007.html b/docs/evs/umn/evs_01_0007.html new file mode 100644 index 000000000..0d897c532 --- /dev/null +++ b/docs/evs/umn/evs_01_0007.html @@ -0,0 +1,31 @@ + + +

Expanding Capacity for an In-use EVS Disk

+

Scenarios

This section describes how to expand the capacity of an In-use EVS disk on the management console. The In-use status indicates that the disk has been attached to a server. You do not need to detach the disk when expanding an In-use disk.

+
+

Constraints

  • Currently, disk capacities can only be expanded, but cannot be reduced.
  • When expanding an In-use disk, the server containing this disk must be in the Running or Stopped state.
  • A shared disk cannot be expanded in the In-use state. To expand a shared In-use disk, you must detach it from all its servers, wait until its status changes to Available, and then expand its capacity. For more information, see Expanding Capacity for an Available EVS Disk.
  • Only some server OSs support capacity expansion of In-use disks. For details, see the official document of the corresponding OS.

    If the server OS does not support capacity expansion of In-use disks, detach the disk and then expand its capacity. Otherwise, you may need to stop and then start the server after the expansion to make the additional space available.

    +
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. Determine whether to view the server information before expanding the disk.

    • If you need to view the server information, perform the following procedure:
      1. In the disk list, click the name of the to-be-expanded disk.

        The disk details page is displayed.

        +
      2. Click the Attachments tab to view the server where the target disk has been attached.
      3. Click Expand Capacity in the upper right corner of the page.

        The expansion page is displayed.

        +
      +
    • If you do not need to view the server information, perform the following procedure:
      1. In the disk list, locate the row that contains the target disk and click Expand Capacity in the Operation column.

        The expansion page is displayed.

        +
      +
    +

  5. Set the Add Capacity (GB) parameter and click Next.
  6. On the Details page, check the disk information again.

    • If you do not need to modify the specifications, click Submit to start the expansion.
    • If you need to modify the specifications, click Previous to modify parameters.
    +

    After the specifications are submitted, go back to the disk list page.

    +

  7. In the disk list, view the capacity of the target disk.

    When the disk status changes from Expanding to In-use and the disk capacity increases, the expansion has succeeded.

    +

    If the expansion fails, technical support personnel will contact you and help you handle this error. Do not perform any operations on the disk before the technical support personnel contact you. If you require that the error be handled as soon as possible, contact our technical support personnel. The disk will no longer be charged after its status changes to Expansion failed.

    +
    +

  8. After a disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the server and extend the disk partition and file system.

    The operation method varies depending on the server OS.

    + +

+
+
+
+
+
Parent topic: Disk Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_01_0008.html b/docs/evs/umn/evs_01_0008.html new file mode 100644 index 000000000..1cffd7476 --- /dev/null +++ b/docs/evs/umn/evs_01_0008.html @@ -0,0 +1,25 @@ + + +

Expanding Capacity for an Available EVS Disk

+

Scenarios

This section describes how to expand the capacity of an Available EVS disk on the management console. The Available status indicates that the disk has not been attached to any server.

+
+

Constraints

  • Currently, disk capacities can only be expanded, but cannot be reduced.
  • A shared disk cannot be expanded in the In-use state. To expand a shared In-use disk, you must detach it from all its servers, wait until its status changes to Available, and then expand its capacity.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the disk list, locate the row that contains the target disk and click Expand Capacity in the Operation column.

    The expansion page is displayed.

    +

  5. Set the Add Capacity (GB) parameter and click Next.
  6. On the Details page, check the disk information again.

    • If you do not need to modify the specifications, click Submit to start the expansion.
    • If you need to modify the specifications, click Previous to modify parameters.
    +

    After the specifications are submitted, go back to the disk list page.

    +

  7. In the disk list, view the capacity of the target disk.

    When the disk status changes from Expanding to Available and the disk capacity increases, the expansion has succeeded.

    +

    If the expansion fails, technical support personnel will contact you and help you handle this error. Do not perform any operations on the disk before the technical support personnel contact you. If you require that the error be handled as soon as possible, contact our technical support personnel. The disk will no longer be charged after its status changes to Expansion failed.

    +
    +

  8. Attach the disk to the server. For details, see Attach an EVS Disk.
  9. After a disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the server and extend the disk partition and file system.

    The operation method varies depending on the server OS.

    + +

+
+
+
+
+
Parent topic: Disk Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_01_0009.html b/docs/evs/umn/evs_01_0009.html new file mode 100644 index 000000000..6d4dcbd8f --- /dev/null +++ b/docs/evs/umn/evs_01_0009.html @@ -0,0 +1,18 @@ + + +

Managing an Encrypted EVS Disk

+

Relationships Between Encrypted Disks, Backups and Snapshots

The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:
  • System disk encryption relates to the image that is used to create the server.
    • If an encrypted image is used to create the server, encryption is enabled for the system disk by default, and the system disk and image share the same encryption method. For details, see Managing Private Images > Encrypting Images in the Image Management Service User Guide.
    • If a non-encrypted image is used to create the server, determine whether to encrypt the system disk during the server creation. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.
    +
  • If an empty disk is created, you can determine whether to encrypt the disk or not. The encryption attribute of the disk cannot be changed after the disk has been created.
  • If a disk is created from a snapshot, the encryption attribute of the disk will be the same as that of the snapshot's source disk.
  • If a disk is created from a backup, the encryption attribute of the disk does not need to be the same as that of the backup.
  • If a snapshot is created for a disk, the encryption attribute of the snapshot is the same as that of the disk.
+
+
+

Creating an Encrypted EVS Disk

Before you use the disk encryption function, KMS access rights need to be granted to EVS. If you have the Security Administrator rights, grant the KMS access rights to EVS directly. If you do not have this permission, contact a user with the security administrator rights to grant KMS access rights to EVS, then repeat the preceding operations.

+

For details about how to create an encrypted disk, see Create an EVS Disk.

+
+

Detaching an Encrypted EVS Disk

Before you detach an EVS disk encrypted by a CMK, check whether the CMK is disabled or scheduled for deletion. If the CMK is unavailable, the disk can still be used, but there is no guarantee how long it will be usable. If the disk is detached, it will not be possible to re-attach it later. In this case, do not detach the disk without a working CMK.

+

The restoration method varies depending on the current CMK status. For details, see EVS Disk Encryption.

+

If the CMK is available, the disk can be detached and re-attached, and data on the disk will not be lost.

+

For details about how to detach an encrypted disk, see Detaching a Data Disk.

+
+
+
+ diff --git a/docs/evs/umn/evs_01_0010.html b/docs/evs/umn/evs_01_0010.html new file mode 100644 index 000000000..71f9eac23 --- /dev/null +++ b/docs/evs/umn/evs_01_0010.html @@ -0,0 +1,23 @@ + + +

Managing a Shared EVS Disk

+

How to Use Shared VBD and SCSI Disks?

You can create shared VBD disks or shared SCSI disks. It is recommended that you attach the shared disk to the ECSs in the same ECS group to improve service reliability.
  • Shared VBD EVS disks: The device type of a newly created shared EVS disk is VBD by default. Such disks can be used as virtual block storage devices, but do not support SCSI reservations. If SCSI reservations are required for your applications, create shared SCSI EVS disks.
  • Shared SCSI EVS disks: These EVS disks support SCSI reservations.
    • To improve data security, you are advised to use SCSI reservations together with the anti-affinity policy of an ECS group. That said, ensure that shared SCSI EVS disks are only attached to ECSs in the same anti-affinity ECS group.
    • If an ECS does not belong to any anti-affinity ECS group, you are advised not to attach shared SCSI EVS disks to this ECS. Otherwise, SCSI reservations may not work properly, which may put your data at risk.
    +
    +

    Concepts of the anti-affinity ECS group and SCSI reservations:

    +
    • The anti-affinity policy of an ECS group allows ECSs to be created on different physical servers to improve service reliability.

      For details about ECS groups, see Managing ECS Groups in the Elastic Cloud Server User Guide.

      +
    • The SCSI reservation mechanism uses a SCSI reservation command to perform SCSI reservation operations. If an ECS sends such a command to an EVS disk, the disk is displayed as locked to other ECSs, preventing the data damage that may be caused by simultaneous read/write operations to the disk from multiple ECSs.
    • ECS groups and SCSI reservations have the following relationship: A SCSI reservation on a single EVS disk cannot differentiate multiple ECSs on the same physical host. For that reason, if multiple ECSs that use the same shared EVS disk are running on the same physical host, SCSI reservations will not work properly. Therefore, you are advised to use SCSI reservations only on ECSs that are in the same ECS group, thus having a working anti-affinity policy.
    +
+
+
+

Attaching a Shared EVS Disk

A common EVS disk can only be attached to one server, whereas a shared EVS disk can be attached to up to 16 servers.

+

For details about how to attach a shared EVS disk, see Attaching a Shared Disk.

+
+

Deleting a Shared EVS Disk

Because a shared EVS disk can be attached to multiple servers, ensure that the shared EVS disk is detached from all the servers before deletion.

+

For details about how to delete a shared EVS disk, see Deleting an EVS Disk.

+
+

Expanding a Shared EVS Disk

Shared EVS disks must be expanded when they are in the Available state. For details, see Expanding Capacity for an Available EVS Disk.

+
+

Related Operations

For more disk sharing FAQs, see Sharing.

+
+
+ diff --git a/docs/evs/umn/evs_01_0011.html b/docs/evs/umn/evs_01_0011.html new file mode 100644 index 000000000..f95e35fa5 --- /dev/null +++ b/docs/evs/umn/evs_01_0011.html @@ -0,0 +1,18 @@ + + +

Deleting a Snapshot

+

Scenarios

If a snapshot is no longer needed, you can delete the snapshot to release the virtual resources. Snapshot deletion has the following constraints:

+
+

Constraints

  • The snapshot status must be Available or Error.
  • If a disk is deleted, all the snapshots created for this disk will also be deleted.
  • If a snapshot is deleted, disks rolled back and created from this snapshot are not affected.
  • If you have reinstalled or changed the server OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.
  4. In the navigation tree on the left, choose Elastic Volume Service > Snapshots.

    The snapshot list page is displayed.

    +

  5. In the snapshot list, locate the row that contains the target snapshot and click Delete in the Operation column.
  6. (Optional) If multiple snapshots are to be deleted, select in front of each snapshot and click Delete in the upper area of the list.
  7. In the displayed dialog box, confirm the information and click Yes.

    If the snapshot is no longer displayed in the snapshot list, the snapshot is deleted successfully.

    +

+
+
+
+
+
Parent topic: Managing Snapshots
+
+
+ diff --git a/docs/evs/umn/evs_01_0012.html b/docs/evs/umn/evs_01_0012.html new file mode 100644 index 000000000..28e86bbb8 --- /dev/null +++ b/docs/evs/umn/evs_01_0012.html @@ -0,0 +1,17 @@ + + +

Rolling Back Data from a Snapshot

+

Scenarios

If the data on an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source disk to restore data. Snapshot rollback has the following constraints:

+
+

Constraints

  • A snapshot can be rolled back only to its source disk. Rollback to another disk is not possible.
  • A snapshot can be rolled back only when the snapshot status is Available and the source disk status is Available (not attached to any server) or Rollback failed.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.
  4. In the navigation tree on the left, choose Elastic Volume Service > Snapshots.

    The snapshot list page is displayed.

    +

  5. In the snapshot list, locate the row that contains the target snapshot and click Roll Back Disk in the Operation column.
  6. In the displayed dialog box, click Yes.
  7. The snapshot list is displayed. After the snapshot status changes from Rolling back to Available, the data rollback is successful.
+
+
+
+
+
Parent topic: Managing Snapshots
+
+
+ diff --git a/docs/evs/umn/evs_01_0013.html b/docs/evs/umn/evs_01_0013.html new file mode 100644 index 000000000..fa7b13267 --- /dev/null +++ b/docs/evs/umn/evs_01_0013.html @@ -0,0 +1,21 @@ + + +

Creating an EVS Disk from a Snapshot

+

Scenarios

This section describes how to create an EVS disk on the Snapshots page. Besides, you can also create an EVS disk from a snapshot by specifying the Create from snapshot parameter on the disk creation page. For details, see Create an EVS Disk.

+
+

Constraints

  • The disk type of the new disk is the same as that of the snapshot's source disk.
  • The device type of the new disk is the same as that of the snapshot's source disk.
  • The encryption attribute of the new disk is the same as that of the snapshot's source disk.
  • A maximum of 128 disks can be created from this snapshot.
  • Batch disk creation is not possible, and the quantity parameter must be set to 1.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.
  4. In the navigation tree on the left, choose Elastic Volume Service > Snapshots.

    The snapshot list page is displayed.

    +

  5. In the snapshot list, locate the row that contains the target snapshot and click Create Disk in the Operation column.
  6. Set the EVS disk parameters. For details, see parameter descriptions and operations provided in Create an EVS Disk.

    A maximum of 128 disks can be created from a snapshot.

    +

    If you create a disk from a snapshot, the disk capacity must be greater than or equal to the snapshot size. In the condition that you do not specify the disk capacity, if the snapshot size is smaller than 10 GB, the default capacity 10 GB will be used as the disk capacity; if the snapshot size is greater than 10 GB, the disk capacity will be consistent with the snapshot size.

    +
    +

  7. Click Create Now.
  8. Go back to the disk list page and view the disk status.

    When the disk status changes to Available, the disk is successfully created.

    +

+
+
+
+
+
Parent topic: Managing Snapshots
+
+
+ diff --git a/docs/evs/umn/evs_01_0014.html b/docs/evs/umn/evs_01_0014.html new file mode 100644 index 000000000..21c041aa9 --- /dev/null +++ b/docs/evs/umn/evs_01_0014.html @@ -0,0 +1,24 @@ + + +

Adding a Tag

+

Scenarios

This section is used to guide users to add a tag for an existing EVS disk. You can also add tags during the EVS disk creation. For details, see Create an EVS Disk.

+

Tags are used to identify the cloud resources for purposes of easy categorization and quick search.

+
+
  • A tag is composed of a key-value pair.
    • Key:
      • Must be unique for each resource.
      • Can contain a maximum of 36 characters.
      • Can contain only digits, letters, hyphens (-), and underscores (_).
      +
    • Value:
      • Can contain a maximum of 43 characters.
      • Can contain only digits, letters, hyphens (-), and underscores (_).
      +
    +
  • A maximum of 10 tags can be added for an EVS disk.
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the disk list, locate the target disk and click the disk name.

    The disk details page is displayed.

    +

  5. Click the Tags tab.
  6. Click Add Tag.

    The Add Tag page is displayed.

    +

  7. Enter a key and a value for a tag and click OK.

    • Key: This parameter is mandatory.
    • Value: This parameter is optional.
    +

    The Tags tab is displayed, and you can view the newly added tag.

    +

+
+
+
+
+
Parent topic: Managing a Tag
+
+
+ diff --git a/docs/evs/umn/evs_01_0015.html b/docs/evs/umn/evs_01_0015.html new file mode 100644 index 000000000..d666d6a72 --- /dev/null +++ b/docs/evs/umn/evs_01_0015.html @@ -0,0 +1,18 @@ + + +

Modifying a Tag

+

Scenarios

You can change the value of a tag for an existing disk, but cannot change the key of a tag.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the disk list, locate the target disk and click on the disk name.

    The disk details page is displayed.

    +

  5. Click the Tags tab.
  6. Locate the target tag and click Edit in the Operation column.

    The Edit Tag page is displayed.

    +

  7. Change the value of the tag and click OK.

    Return to the tag list. If the tag value is changed, the modification is complete.

    +

+
+
+
+
+
Parent topic: Managing a Tag
+
+
+ diff --git a/docs/evs/umn/evs_01_0016.html b/docs/evs/umn/evs_01_0016.html new file mode 100644 index 000000000..a2cd11e02 --- /dev/null +++ b/docs/evs/umn/evs_01_0016.html @@ -0,0 +1,18 @@ + + +

Deleting a Tag

+

Scenarios

If an existing tag is no longer needed, you can delete it.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the disk list, locate the target disk and click the disk name.

    The disk details page is displayed.

    +

  5. Click the Tags tab.
  6. Locate the target tag and click Delete in the Operation column.

    The Delete Tag page is displayed.

    +

  7. Confirm the information and click Yes.

    Return to the tag list. If the tag is no longer displayed in the tag list, the deletion is successful.

    +

+
+
+
+
+
Parent topic: Managing a Tag
+
+
+ diff --git a/docs/evs/umn/evs_01_0018.html b/docs/evs/umn/evs_01_0018.html new file mode 100644 index 000000000..e09363918 --- /dev/null +++ b/docs/evs/umn/evs_01_0018.html @@ -0,0 +1,423 @@ + + +

Extending Partitions and File Systems for SCSI Disks (Linux)

+

Scenarios

After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.

+

In Linux, you must allocate the additional space to an existing partition or a new partition.

+
This section uses CentOS 7.4 64bit as the sample OS to describe how to extend an MBR partition of a SCSI data disk. The method for allocating the additional space varies depending on the server OS. This document is used for reference only. For detailed operations and differences, see the corresponding OS documents. +
+

Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using backups or snapshots before expansion. For details about backups, see Managing EVS Backup. For details about snapshots, see Creating a Snapshot.

+
+
+

Prerequisites

+
+

Creating a New MBR Partition

Originally, data disk /dev/sda has 50 GB and one partition (/dev/sda1), and then 50 GB is added to the disk. The following procedure shows you how to create a new MBR partition /dev/sda2 with this 50 GB.

+
  1. Run the following command to view the disk partition information:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-scsi ~]# fdisk -l
+
+Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+
+Disk /dev/sda: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x915ffe6a
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/sda1            2048   104857599    52427776   83  Linux
    +
    +
    View the /dev/sda capacity and check whether the additional space is included.
    • If the additional space is not included, refresh the capacity according to 2.
    • If the additional space is included, go to 3.
    +
    +

  2. (Optional) Run the following command to update the capacity of the SCSI data disk:

    1. Run the following command to update the disk capacity on the server:

      echo 1 > /sys/class/scsi_device/%d:%d:%d:%d/device/rescan &

      +

      In the command, %d:%d:%d:%d indicates a folder in the /sys/class/scsi_device/ directory and can be obtained using ll /sys/class/scsi_device/.

      +
      Information similar to the following is displayed: (2:0:0:0 indicates the folder to be obtained.)
      cs-xen-02:/sys/class/scsi_device # ll /sys/class/scsi_device/
+total 0
+lrwxrwxrwx 1 root root 0 Sep 26 11:37 2:0:0:0 -> ../../devices/xen/vscsi-2064/host2/target2:0:0/2:0:0:0/scsi_device/2:0:0:0
      +
      +

      In this example, run the following command:

      +

      echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan &

      +
    2. After the disk capacity is updated, run the following command to view the disk partition information again:

      fdisk -l

      +

      If the additional space is included, go to 3.

      +
    +

  3. Run the following command to enter fdisk:

    fdisk Disk

    +

    In this example, run the following command:

    +

    fdisk /dev/sda

    +
    Information similar to the following is displayed:
    [root@ecs-scsi ~]# fdisk /dev/sda
+Welcome to fdisk (util-linux 2.23.2).
+
+Changes will remain in memory only, until you decide to write them.
+Be careful before using the write command.
+
+
+Command (m for help):
    +
    +

  4. Enter n and press Enter to create a new partition.

    Information similar to the following is displayed:
    Command (m for help): n
+Partition type:
+   p   primary (1 primary, 0 extended, 3 free)
+   e   extended
+Select (default p):
    +
    +
    There are two types of disk partitions:
    • Choosing p creates a primary partition.
    • Choosing e creates an extended partition.
    +

    If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.

    +

    Disk partitions created using GPT are not categorized.

    +
    +
    +

  5. In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.

    Information similar to the following is displayed:
    Select (default p): p
+Partition number (2-4, default 2):
    +
    +

    Partition number indicates the serial number of the primary partition. Because partition number 1 has been used, the value ranges from 2 to 4.

    +

  6. Enter the serial number of the primary partition and press Enter. Partition number 2 is used in this example. Therefore, enter 2 and press Enter.

    Information similar to the following is displayed:
    Partition number (2-4, default 2): 2
+First sector (104857600-209715199, default 104857600):
    +
    +

    First sector indicates the start sector. The value ranges from 104857600 to 209715199, and the default value is 104857600.

    +

  7. Enter the new partition's start sector and press Enter. In this example, the default start sector is used.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    First sector (104857600-209715199, default 104857600):
+Using default value 104857600
+Last sector, +sectors or +size{K,M,G} (104857600-209715199, default 209715199):
    +
    +

    Last sector indicates the end sector. The value ranges from 104857600 to 209715199, and the default value is 209715199.

    +

  8. Enter the new partition's end sector and press Enter. In this example, the default end sector is used.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    Last sector, +sectors or +size{K,M,G} (104857600-209715199, default 209715199):
+Using default value 209715199
+Partition 2 of type Linux and of size 50 GiB is set
+
+Command (m for help):
    +
    +

  9. Enter p and press Enter to view the new partition.

    Information similar to the following is displayed:
    Command (m for help): p
+
+Disk /dev/sda: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x915ffe6a
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/sda1            2048   104857599    52427776   83  Linux
+/dev/sda2       104857600   209715199    52428800   83  Linux
+
+Command (m for help):
    +
    +

  10. Enter w and press Enter to write the changes to the partition table.

    Information similar to the following is displayed:
    Command (m for help): w
+The partition table has been altered!
+
+Calling ioctl() to re-read partition table.
+
+WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
+The kernel still uses the old table. The new table will be used at
+the next reboot or after you run partprobe(8) or kpartx(8)
+Syncing disks.
    +
    +

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

    +
    +

  11. Run the following command to synchronize the new partition table to the OS:

    partprobe

    +

  12. Run the following command to set the file system format for the new partition:

    mkfs -t File system Disk partition

    +
    • Sample command of the ext* file system:

      mkfs -t ext4 /dev/sda2

      +
      Information similar to the following is displayed:
      [root@ecs-scsi ~]# mkfs -t ext4 /dev/sda2
+mke2fs 1.42.9 (28-Dec-2013)
+Filesystem label=
+OS type: Linux
+Block size=4096 (log=2)
+Fragment size=4096 (log=2)
+Stride=0 blocks, Stripe width=0 blocks
+3276800 inodes, 13107200 blocks
+655360 blocks (5.00%) reserved for the super user
+First data block=0
+Maximum filesystem blocks=2162163712
+400 block groups
+32768 blocks per group, 32768 fragments per group
+8192 inodes per group
+Superblock backups stored on blocks:
+        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
+        4096000, 7962624, 11239424
+
+Allocating group tables: done
+Writing inode tables: done
+Creating journal (32768 blocks): done
+Writing superblocks and filesystem accounting information: done
      +
      +
    +
    • Sample command of the xfs file system:

      mkfs -t xfs /dev/sda2

      +

      Information similar to the following is displayed:

      +
      [root@ecs-scsi ~]# mkfs -t xfs /dev/sda2
+meta-data=/dev/sda2              isize=512     agcount=4, agsize=3276800 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, sparse=0
+data     =                       bsize=4096    blocks=13107200, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal log           bsize=4096    blocks=6400, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
      +
    +

    The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

    +

  13. (Optional) Run the following command to create a mount point:

    Perform this step if you want to mount the partition on a new mount point.

    +

    mkdir Mount point

    +

    In this example, run the following command to create the /mnt/test mount point:

    +

    mkdir /mnt/test

    +

  14. Run the following command to mount the new partition:

    mount Disk partition Mount point

    +

    In this example, run the following command to mount the new partition /dev/sda2 on /mnt/test:

    +

    mount /dev/sda2 /mnt/test

    +

    If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

    +
    +

  15. Run the following command to view the mount result:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-scsi ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  2.0G   39G   5% /
+devtmpfs       devtmpfs  509M     0  509M   0% /dev
+tmpfs          tmpfs     520M     0  520M   0% /dev/shm
+tmpfs          tmpfs     520M  7.2M  513M   2% /run
+tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
+tmpfs          tmpfs     104M     0  104M   0% /run/user/0
+/dev/sda1      ext4       53G   55M   50G   1% /mnt/sdc
+/dev/sda2      ext4       53G   55M   50G   1% /mnt/test
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +
    +

+
+

Extending an Existing MBR Partition

If the additional space is allocated to an existing partition, data on the disk will not be cleared but you must use umount to unmount the existing partition. In this case, services will be affected.

+
+

Originally, SCSI data disk /dev/sda has 100 GB and two partitions (/dev/sda1 and /dev/sda2), and then 50 GB is added to the disk. The following procedure shows you how to add this 50 GB to the existing MBR partition /dev/sda2.

+

During an expansion, the additional space is added to the end of the disk. Therefore, if the disk has multiple partitions, the additional space can only be allocated to the partition at the disk end.

+
  1. Run the following command to view the disk partition information:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-scsi ~]# fdisk -l
+
+Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+
+Disk /dev/sda: 161.1 GB, 161061273600 bytes, 314572800 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x915ffe6a
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/sda1            2048   104857599    52427776   83  Linux
+/dev/sda2       104857600   209715199    52428800   83  Linux
    +
    +

    In the command output, take note of the partition's start and end sectors. In this example, /dev/sda2's start sector is 104857600, and its end sector is 209715199.

    +
    View the /dev/sda capacity and check whether the additional space is included.
    • If the additional space is not included, refresh the capacity according to 2.
    • If the additional space is included, take note of the start and end sectors of the target partition and then go to 3. These values will be used in the subsequent operations.
    +
    +

  2. (Optional) Run the following command to update the capacity of the SCSI data disk:

    1. Run the following command to update the disk capacity on the server:

      echo 1 > /sys/class/scsi_device/%d:%d:%d:%d/device/rescan &

      +

      In the command, %d:%d:%d:%d indicates a folder in the /sys/class/scsi_device/ directory and can be obtained using ll /sys/class/scsi_device/.

      +
      Information similar to the following is displayed: (2:0:0:0 indicates the folder to be obtained.)
      cs-xen-02:/sys/class/scsi_device # ll /sys/class/scsi_device/
+total 0
+lrwxrwxrwx 1 root root 0 Sep 26 11:37 2:0:0:0 -> ../../devices/xen/vscsi-2064/host2/target2:0:0/2:0:0:0/scsi_device/2:0:0:0
      +
      +

      In this example, run the following command:

      +

      echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan &

      +
    2. After the disk capacity is updated, run the following command to view the disk partition information again:

      fdisk -l

      +

      If the additional space is included, take note of the start and end sectors of the target partition and then go to 3. These values will be used in the subsequent operations.

      +
    +

  3. Run the following command to unmount the partition:

    umount Disk partition

    +

    In this example, run the following command:

    +

    umount /dev/sda2

    +

  4. Run the following command to enter fdisk:

    fdisk Disk

    +

    In this example, run the following command:

    +

    fdisk /dev/sda

    +
    Information similar to the following is displayed:
    [root@ecs-scsi ~]# fdisk /dev/sda
+Welcome to fdisk (util-linux 2.23.2).
+
+Changes will remain in memory only, until you decide to write them.
+Be careful before using the write command.
+
+
+Command (m for help):
    +
    +

  5. Run the following command to delete the partition to be extended:

    1. Enter d and press Enter to delete the partition.
      Information similar to the following is displayed:
      Command (m for help): d
+Partition number (1,2, default 2):
      +
      +
    2. Enter the partition number and press Enter to delete the partition. In this example, enter 2.
      Information similar to the following is displayed:
      Partition number (1,2, default 2): 2
+Partition 2 is deleted
+
+Command (m for help):
      +
      +

      After deleting the partition, recreate the partition according to the following steps, and data on this disk will not be lost.

      +
      +
    +

  6. Enter n and press Enter to create a new partition.

    Information similar to the following is displayed:
    Command (m for help): n
+Partition type:
+   p   primary (1 primary, 0 extended, 3 free)
+   e   extended
+Select (default p):
    +
    +
    There are two types of disk partitions:
    • Choosing p creates a primary partition.
    • Choosing e creates an extended partition.
    +

    If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.

    +

    Disk partitions created using GPT are not categorized.

    +
    +
    +

  7. Ensure that the entered partition type is the same as the partition had before. In this example, a primary partition is used. Therefore, enter p and press Enter to create a primary partition.

    Information similar to the following is displayed:
    Select (default p): p
+Partition number (2-4, default 2):
    +
    +

    Partition number indicates the serial number of the primary partition.

    +

  8. Ensure that entered partition number is the same as the partition had before. In this example, partition number 2 is used. Therefore, enter 2 and press Enter.

    Information similar to the following is displayed:
    Partition number (2-4, default 2): 2
+First sector (104857600-314572799, default 104857600):
    +
    +

    In the command output, First sector specifies the start sector.

    +
    Data will be lost if the following operations are performed:
    • Select a start sector other than the partition had before.
    • Select an end sector smaller than the partition had before.
    +
    +
    +

  9. Ensure that the entered start sector is the same as the partition had before. In this example, start sector 104857600 is recorded in 1 or 2. Therefore, enter 104857600 and press Enter.

    Information similar to the following is displayed:
    First sector (104857600-314572799, default 104857600):
+Using default value 104857600
+Last sector, +sectors or +size{K,M,G} (104857600-314572799, default 314572799):
    +
    +

    In the command output, Last sector specifies the end sector.

    +

  10. Ensure that the entered end sector is larger than or equal to the end sector recorded in 1 or 2. In this example, the recorded end sector is 209715199, and the default end sector is used. Therefore, enter 314572799 and press Enter.

    Information similar to the following is displayed:
    Last sector, +sectors or +size{K,M,G} (104857600-314572799, default 314572799):
+Using default value 314572799
+Partition 2 of type Linux and of size 100 GiB is set
+
+Command (m for help):
    +
    +

    The partition is created.

    +

  11. Enter p and press Enter to view the partition details.

    Information similar to the following is displayed:

    +
    Command (m for help): p
+
+Disk /dev/sda: 161.1 GB, 161061273600 bytes, 314572800 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x915ffe6a
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/sda1            2048   104857599    52427776   83  Linux
+/dev/sda2       104857600   314572799    104857600  83  Linux
+
+Command (m for help):
    +

  12. Enter w and press Enter to write the changes to the partition table.

    Information similar to the following is displayed: (The partition is successfully created.)
    Command (m for help): w
+The partition table has been altered!
+
+Calling ioctl() to re-read partition table.
+
+WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
+The kernel still uses the old table. The new table will be used at
+the next reboot or after you run partprobe(8) or kpartx(8)
+Syncing disks.
    +
    +

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

    +
    +

  13. Run the following command to synchronize the new partition table to the OS:

    partprobe

    +

  14. Perform the following operations based on the file system of the disk:

    • For the ext* file system
      1. Run the following command to check the correctness of the file system on the partition:

        e2fsck -f Disk partition

        +

        In this example, run the following command:

        +

        e2fsck -f /dev/sda2

        +
        Information similar to the following is displayed:
        [root@ecs-scsi ~]# e2fsck -f /dev/sda2
+e2fsck 1.42.9 (28-Dec-2013)
+Pass 1: Checking inodes, blocks, and sizes
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+/dev/sda2: 11/3276800 files (0.0% non-contiguous), 251790/13107200 blocks
        +
        +
      2. Run the following command to extend the file system of the partition:

        resize2fs Disk partition

        +

        In this example, run the following command:

        +

        resize2fs /dev/sda2

        +
        Information similar to the following is displayed:
        [root@ecs-scsi ~]# resize2fs /dev/sda2
+resize2fs 1.42.9 (28-Dec-2013)
+Resizing the filesystem on /dev/sda2 to 26214400 (4k) blocks.
+The filesystem on /dev/sda2 is now 26214400 blocks long.
        +
        +
      3. (Optional) Run the following command to create a mount point:

        Perform this step if you want to mount the partition on a new mount point.

        +

        mkdir Mount point

        +

        In this example, run the following command to create the /mnt/test mount point:

        +

        mkdir /mnt/test

        +
      4. Run the following command to mount the partition:

        mount Disk partition Mount point

        +

        In this example, run the following command to mount the partition /dev/sda2 on /mnt/test:

        +

        mount /dev/sda2 /mnt/test

        +

        If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

        +
        +
      +
    • For the xfs file system
      1. (Optional) Run the following command to create a mount point:

        Perform this step if you want to mount the partition on a new mount point.

        +

        mkdir Mount point

        +

        In this example, run the following command to create the /mnt/test mount point:

        +

        mkdir /mnt/test

        +
      2. Run the following command to mount the partition:

        mount Disk partition Mount point

        +

        In this example, run the following command to mount the partition /dev/sda2 on /mnt/test:

        +

        mount /dev/sda2 /mnt/test

        +

        If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

        +
        +
      3. Run the following command to extend the file system of the partition:

        sudo xfs_growfs Disk partition

        +

        In this example, run the following command:

        +

        sudo xfs_growfs /dev/sda2

        +

        Information similar to the following is displayed:

        +
        [root@ecs-scsi ~]# sudo xfs_growfs /dev/sda2
+meta-data=/dev/sda2              isize=512     agcount=4, agsize=3276800 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, spinodes=0
+data     =                       bsize=4096    blocks=13107200, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal               bsize=4096    blocks=6400, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
+data blocks changed from 13107200 to 26214400df .
        +
      +
    +

  15. Run the following command to view the mount result:

    df -TH

    +

    Information similar to the following is displayed:

    +
    [root@ecs-scsi ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  2.0G   39G   5% /
+devtmpfs       devtmpfs  509M     0  509M   0% /dev
+tmpfs          tmpfs     520M     0  520M   0% /dev/shm
+tmpfs          tmpfs     520M  7.2M  513M   2% /run
+tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
+tmpfs          tmpfs     104M     0  104M   0% /run/user/0
+/dev/sda1      ext4       53G   55M   50G   1% /mnt/sdc
+/dev/sda2      ext4      106G   63M  101G   1% /mnt/test
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +

+
+

Setting Automatic Mounting at System Start

Modify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.

+

The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.

+

UUID is the unique character string for disk partitions in a Linux system.

+
+
  1. Run the following command to query the partition UUID:

    blkid Disk partition

    +

    In this example, run the following command to query the UUID of the /dev/vdb1 partition:

    +

    blkid /dev/vdb1

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
    +

    The UUID of the /dev/vdb1 partition is displayed.

    +

  2. Run the following command to open the fstab file using the vi editor:

    vi /etc/fstab

    +

  3. Press i to enter the editing mode.
  4. Move the cursor to the end of the file and press Enter. Then, add the following information:

    UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
    +

  5. Press Esc, enter :wq, and press Enter.

    The system saves the configurations and exits the vi editor.

    +

  6. Perform the following operations to verify the automatic mounting function:

    1. Run the following command to unmount the partition:

      umount Disk partition

      +

      In this example, run the following command:

      +

      umount /dev/vdb1

      +
    2. Run the following command to reload all the content in the /etc/fstab file:

      mount -a

      +
    3. Run the following command to query the file system mounting information:

      mount | grep Mount point

      +

      In this example, run the following command:

      +

      mount | grep /mnt/sdc

      +

      If information similar to the following is displayed, the automatic mounting function takes effect:

      +
      root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
      +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0019.html b/docs/evs/umn/evs_01_0019.html new file mode 100644 index 000000000..e1efc3a49 --- /dev/null +++ b/docs/evs/umn/evs_01_0019.html @@ -0,0 +1,19 @@ + + +

Searching Disks by Tags

+

Scenarios

Tags can be used to categorize EVS disks, and users can quickly search for their desired EVS disks by tags. This section is used to guide users to search for EVS disk by existing tags.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the upper area of the disk list, click Search by Tag.

    The Search by Tag page is displayed.

    +

  5. Enter or select an existing tag in the text box under Search by Tag.
  6. (Optional) If disks containing multiple tags need to be queried, click to add tags.

    A maximum of 10 tags can be added at a time.

    +

    For the added tags, you can delete them individually or click Reset to clear all of them.

    +

  7. After the tags are added, click Search.

    Disks owning the added tags are displayed in the list, and the search is complete.

    +

+
+
+
+
+
Parent topic: Managing a Tag
+
+
+ diff --git a/docs/evs/umn/evs_01_0020.html b/docs/evs/umn/evs_01_0020.html new file mode 100644 index 000000000..2a43614a9 --- /dev/null +++ b/docs/evs/umn/evs_01_0020.html @@ -0,0 +1,20 @@ + + +

EVS Replication (Deprecated)

+

What Is EVS Replication

If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a production disk in another AZ and use the production disk and DR disk to create an EVS replication pair. The data on these two disks will be consistent in real time. If a large number of physical resources in the primary AZ are faulty due to force majeure, you can use the DR disks in the secondary AZ to ensure the service availability and continuity.
  • The server with the production disk attached is referred to as the production server, and the AZ containing the production server is the primary AZ.
  • The server with the DR disk attached is referred to as the DR server, and the AZ containing the DR server is the secondary AZ.
+
+
+

Application Scenarios

The replication function helps address your following needs:
  • Data in DR disks is consistent with that in production disks in real time. You can perform a planned migration based on your service needs, that is, migrate the services from the primary AZ to the secondary AZ without data loss.
  • If large-scale physical resources in the primary AZ become faulty due to force majeure, you can use DR disks in the secondary AZ to lower the impact exerted on services.
+
+
+

Usage Instructions

For more use methods of EVS replication, see Managing EVS Replication (Deprecated).

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0021.html b/docs/evs/umn/evs_01_0021.html new file mode 100644 index 000000000..e45afe36a --- /dev/null +++ b/docs/evs/umn/evs_01_0021.html @@ -0,0 +1,17 @@ + + +

EVS Backup

+

What Is EVS Backup?

Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while servers are running. If data loss or damage occurred due to virus invasions, misoperations, or software and hardware faults, you can use backups to restore data, guaranteeing your data integrity and security.

+

For more information, see the Cloud Backup and Recovery User Guide.

+
+

Application Scenarios

Create and apply backup policies to schedule periodic backups for your EVS disks. You can use the backup data to create new EVS disks or restore to source disks.

+
+

Usage Instructions

For how to back up EVS disks, see Managing EVS Backup or the Cloud Backup and Recovery User Guide.

+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0023.html b/docs/evs/umn/evs_01_0023.html new file mode 100644 index 000000000..29cd332c4 --- /dev/null +++ b/docs/evs/umn/evs_01_0023.html @@ -0,0 +1,31 @@ + + +

Managing EVS Replication (Deprecated)

+
+ + diff --git a/docs/evs/umn/evs_01_0024.html b/docs/evs/umn/evs_01_0024.html new file mode 100644 index 000000000..28fb68b19 --- /dev/null +++ b/docs/evs/umn/evs_01_0024.html @@ -0,0 +1,120 @@ + + +

Creating a DR ECS (Deprecated)

+

Scenarios

Before you create an EVS replication pair, create a DR ECS in the secondary AZ for the production ECS. The DR ECS parameters must be consistent with those of the production ECS. The parameters include the ECS specifications and the parameters of the production ECS's EVS disks, subnet, and security group.

+

If a large number of physical resources in the primary AZ are faulty due to force majeure, you can attach DR disks in the secondary AZ to DR ECSs and use DR disks to ensure the service availability and continuity.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.

    The Elastic Cloud Server page is displayed.

    +

  4. Click the name of the production ECS.

    The ECS details page is displayed.

    +

  5. Take note of the production ECS information, including the ECS specifications, details of the EVS disks attached to the ECS, private IP address, and security group, as shown in Table 1.

    The listed parameter values are for reference only.

    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Information to be collected

    Production Resource

    +

    Parameter

    +

    Example Value

    +

    ECS

    +

    VPC

    +

    vpc-001

    +

    ECS type

    +

    General-purpose

    +

    Specification

    +

    s2.xlarge.2

    +

    vCPU

    +

    4 cores

    +

    Memory

    +

    8 GB

    +

    Image

    +

    CentOS 7.2 64bit

    +

    AZ

    +

    AZ1

    +

    EVS disk

    +

    Quantity

    +
    • System disk: 1
    • Data disk: 1
    +

    Capacity

    +
    • System disk: 500 GB
    • Data disk: 2000 GB
    +

    Disk type

    +
    • System disk: common I/O
    • Data disk: ultra-high I/O
    +

    Disk sharing

    +
    • System disk: non-shared disk
    • Data disk: non-shared disk
    +

    Device type

    +
    • System disk: VBD
    • Data disk: SCSI
    +

    Others

    +

    Private IP address

    +

    192.168.12.2

    +

    Security group

    +

    Sys-default

    +

    Virtual IP address

    +

    192.168.12.23

    +
    +
    +

  6. Create the DR ECS using the information of the production ECS.

    For details, see Creating an ECS in the Elastic Cloud Server User Guide.

    +

    Check the parameter values carefully and ensure that information of the DR ECS and production ECS is consistent.

    +
    +

  7. After the DR ECS has been created, locate the DR ECS and stop it.

    Stopping the DR ECS prevents it from being incorrectly used.

    +

    When the DR ECS is not stopped and its system disk is used to create an EVS replication pair, the DR ECS status will change to REBUILDING. In this state, you cannot stop the DR ECS, detach EVS disks from it, or expand its EVS disks.

    +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0025.html b/docs/evs/umn/evs_01_0025.html new file mode 100644 index 000000000..bb6c0bf2a --- /dev/null +++ b/docs/evs/umn/evs_01_0025.html @@ -0,0 +1,27 @@ + + +

Collecting ECS Information (Deprecated)

+

Scenarios

This section is used to guide users to collect the production ECS and DR ECS information, including the ECS IDs and the IDs of the EVS disks attached the ECSs.

+

Two EVS disks form an EVS replication pair. Therefore, the production disk ID, DR disk ID, and EVS replication pair ID can be used to identify disks and the EVS replication pair.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.

    The Elastic Cloud Server page is displayed.

    +

  4. Click the name of the production ECS.

    The ECS details page is displayed.

    +

  5. Perform the following operations to take note of the production ECS information:

    1. Take note of the production ECS ID.

      Example ID: 4686b400-5a53-42f9-96f6-d2fe32bb9542

      +
    2. Click the Disks tab. Click to view the details of the corresponding disk and take note of all the production disk IDs.

      You need to take note of the IDs of all the system disks and data disks attached to the production ECS.

      +

      Example ID: ce86f381-99dc-422c-bb10-8014604cf5b9

      +
    3. Click the NICs tab. Click to view the private IP address, elastic IP address (EIP), virtual IP address, and MAC address of a production NIC and take note of the private IP addresses, EIPs, virtual IP addresses, and MAC addresses of all NICs accordingly.

      You need to take note of IP addresses of all NICs bound to the production ECS.

      +

      Example addresses: 192.168.xx.xx, 10.154.xx.xx, 192.168.xx.xx, {mac}

      +

      Replace {mac} with the MAC address during operation.

      +
      +
    +

  6. Take note of the DR ECS information. For details, see 4 to 5.
+
+
+ + diff --git a/docs/evs/umn/evs_01_0026.html b/docs/evs/umn/evs_01_0026.html new file mode 100644 index 000000000..d4848f1f0 --- /dev/null +++ b/docs/evs/umn/evs_01_0026.html @@ -0,0 +1,81 @@ + + +

Configuring a Virtual IP Address for the Server (Deprecated)

+

Scenarios

Before you use EVS replication, bind a virtual IP address to the production server and DR server, respectively. Then configure the virtual IP address as the static IP address for the servers. This virtual IP address is used to access applications on servers.

+ +
+

Prerequisites

You have obtained the VPC, subnet, MAC address, and virtual IP address of the production server. For details, see Collecting ECS Information (Deprecated).

+
+

Procedure

The following operations are for reference only. For details, see Assigning a Virtual IP Address in the Virtual Private Cloud User Guide.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.

    The Elastic Cloud Server page is displayed.

    +

  4. In the ECS list, locate the production ECS and click the ECS name.

    The ECS details page is displayed.

    +

  5. On the ECS details page, locate the VPC and click the VPC name.

    The Virtual Private Cloud page is displayed.

    +

  6. In the VPC list, locate the VPC of the production ECS and click the VPC name.

    The VPC details page is displayed.

    +

  7. On the Subnets tab, locate the subnet of the production ECS and click the subnet name.

    The subnet details page is displayed.

    +

  8. Click the Virtual IP Addresses tab and check whether the production ECS is bound with a virtual IP address.

    • If yes, perform the following operation:
      1. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the DR server.

        After the virtual IP address is bound with the DR server, the subnet details page is displayed.

        +
      +
    • If no, perform the following operations:
      1. Click Assign Virtual IP Address.

        After the application succeeds, you can view the virtual IP address in the virtual IP address list.

        +

        When assigning the virtual IP address, you can select the Automatic or Manual mode based on your service requirements.

        +
        +
      2. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the production server.

        After the virtual IP address is bound with the production server, the subnet details page is displayed.

        +
      3. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the DR server.

        After the virtual IP address is bound with the DR server, the subnet details page is displayed.

        +
      +
    +

  9. On the subnet details page, take note of the subnet and the IP address of the server's NIC where the virtual IP address has been bound.

    An example is provided as follows:
    • Subnet: 192.168.0.0/24
    • Bound server (NIC): ecs-001 (192.168.0.176)
    +
    +

  10. After a virtual IP address is bound with a server, perform the following substeps to configure the bound IP address as the static IP address:

    The following example uses CentOS 7.2 64bit as the sample OS.

    The configuration method varies depending on the server OS. This document is used for reference only. For the detailed operations and differences, see the corresponding OS documents.

    +

    For the Windows OS, see the Microsoft official documentation.

    +
    +
    1. Log in to the server as user root.
    2. Run the following command to check the name of the NIC bound with the virtual IP address in the server:

      ifconfig

      +

      You can obtain the NIC name using the NIC IP address recorded in 9. In this example, the NIC name is eth0.

      +
    3. Run the following command to switch to the directory containing NIC configuration files:

      cd /etc/sysconfig/network-scripts

      +
    4. Run the following command to copy NIC configuration file eth0 and change its name to eth0:1:

      cp eth0 eth0:1

      +
    5. Perform the following operations to modify the configuration parameters of eth0:1 using the vi editor:
      1. Run the following command to open the ifcfg-eth0:1 file:

        vi ifcfg-eth0:1

        +
      2. Press i to enter editing mode.
      3. Configure the parameters according to the following example:
        BOOTPROTO=static
+DEVICE=eth0:1
+NAME=eth0:1
+ONBOOT=yes
+TYPE=Ethernet
+USERCTL=no
+IPADDR=192.168.0.176
+NETMASK=255.255.255.0
        +
        Configuration descriptions of the NAME, IPADDR, and NETMASK fields:
        • NAME: Specifies the NIC name recorded in 10.b.
        • IPADDR: Specifies the NIC IP address recorded in 9.
        • NETMASK: Specifies the subnet recorded in 9.

          In this example, the subnet mask has 24 bits. Therefore, enter 255.255.255.0 for NETMASK.

          +
        +
        +
      4. Press Esc, enter :wq, and press Enter.

        The system saves the configurations and exits the vi editor.

        +
      +
    6. Run the following command to delete unnecessary NIC files from the /etc/sysconfig/network-scripts directory:

      rm Name of the unnecessary NIC file

      +

      For example, run the following command:

      +

      rm ifcfg-eth1

      +

      Before deleting the unnecessary NIC files, you are advised to back up the files.

      +

      If multiple unnecessary NIC files exist, delete them individually. Ensure that the /etc/sysconfig/network-scripts directory contains only the in-use NIC file.

      +
      +
    7. Run the following command to check whether the 70-persistent-ipoib.rules file exists in the /etc/udev/rules.d/ directory:
      ls /etc/udev/rules.d/70-persistent-ipoib.rules
      • If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.
        1. Run the following command to open the 70-persistent-ipoib.rules file:

          vi /etc/udev/rules.d/70-persistent-ipoib.rules

          +
        2. Press i to enter editing mode.
        3. Add NIC information for the DR server based on that of the production server. For details, see the following example:
          ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0" 
+ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth1"
+
+ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0" 
+ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth1"
          +

          Configuration descriptions of the ATTR{address} and NAME fields:

          +
          • ATTR{address}: specifies the MAC address of server's NIC.
          • NAME: Specifies the NIC name recorded in 10.b.

            a. Ensure that the NAME (NIC name) values of the production and DR servers are consistent. The ATTR{address} (MAC address) value can be obtained in Collecting ECS Information (Deprecated).

            +

            b. Replace {mac} with the MAC address during operation.

            +
            +
          +
        4. Press Esc, enter :wq, and press Enter.

          The system saves the configurations and exits the vi editor.

          +
        +
      • If no, go to 10.h.
      +
      +
    8. Run the following command to restart the network service for the configuration to take effect:

      service network restart

      +
    +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0027.html b/docs/evs/umn/evs_01_0027.html new file mode 100644 index 000000000..343b59010 --- /dev/null +++ b/docs/evs/umn/evs_01_0027.html @@ -0,0 +1,22 @@ + + +

Creating an EVS Replication Pair (Deprecated)

+

Scenarios

Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see EVS Replication Pair in the Elastic Volume Service API Reference.

+

If a production disk needs to be deleted after it has been used together with its DR disk to create an EVS replication pair, delete the EVS replication pair first and then delete the production disk and DR disk. For details, see Deleting an EVS Replication Pair in the Elastic Volume Service API Reference.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Procedure

  1. Create an EVS replication pair using the production disk and DR disk.

    For details, see Creating an EVS Replication Pair in the Elastic Volume Service API Reference.

    +

  2. Query the details about the EVS replication pair.

    For details, see Querying Details About an EVS Replication Pair in the Elastic Volume Service API Reference.

    +

    If the EVS replication pair status changes to available, the creation is successful.

    +

  3. Take note of the production disk ID, DR disk ID, EVS replication pair ID, and the primary site of the EVS replication pair, which is the AZ containing the production disk.

    Two EVS disks form an EVS replication pair. Therefore, the production disk ID, DR disk ID, and EVS replication pair ID can be used to identify disks and the EVS replication pair.

    +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0028.html b/docs/evs/umn/evs_01_0028.html new file mode 100644 index 000000000..b15c8b8a3 --- /dev/null +++ b/docs/evs/umn/evs_01_0028.html @@ -0,0 +1,29 @@ + + +

Creating a Replication Consistency Group (Deprecated)

+

Scenarios

Currently, users need to make API calls to create replication consistency groups and add EVS replication pairs to the groups. For details, see Replication Consistency Group in the Elastic Volume Service API Reference.

+

A replication consistency group is composed of EVS replication pairs from a group of servers. These servers may run applications that are strongly correlated with each other and require unified management and application consistency. In this case, you can first create EVS replication pairs using the disks attached to these servers, then add these EVS replication pairs to a replication consistency group to facilitate management and consistency. Figure 1 shows the relationship between EVS replication pairs and replication consistency groups. If you have performed an operation to a replication consistency group, all EVS replication pairs in this group are affected.

+
Figure 1 Relationship between EVS replication pairs and replication consistency groups
+

Existing EVS replication pairs can be added to a replication consistency group upon the group creation. To add EVS replication pairs to or remove them from a replication consistency group after the group creation, see Updating a Replication Consistency Group (Deprecated).

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Procedure

  1. Create a replication consistency group and add all EVS replication pairs of a server to the group.

    For details, see Creating a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

  2. Query the details about the replication consistency group.

    For details, see Querying Details About a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

    When the consistency group status changes to available, the creation is successful.

    +

  3. Take note of the production server ID, DR server ID, replication consistency group ID, EVS replication pair IDs in the replication consistency group, and primary site of the replication consistency group, which is the AZ containing production disks.

    For details about how to obtain the production server ID and DR server ID, see Collecting ECS Information (Deprecated).

    +
    +

  4. Synchronize the data of a replication consistency group, which means that the data of all EVS replication pairs within the group is synchronized.

    For details, see Synchronizing a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

  5. Query the data synchronization status of the replication consistency group.

    For details, see Querying Details About a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

    When the replication status of the replication consistency group changes to active, the data in all EVS replication pairs of this group has been synchronized.

    +

    The time required for the initial data synchronization within a replication consistency group varies depending on the number of the EVS replication pairs in the group, EVS disk capacity, and actual data amount. Normally, the initial data synchronization takes a relative long period of time. Please wait patiently.

    +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0029.html b/docs/evs/umn/evs_01_0029.html new file mode 100644 index 000000000..21089bd54 --- /dev/null +++ b/docs/evs/umn/evs_01_0029.html @@ -0,0 +1,26 @@ + + +

Updating a Replication Consistency Group (Deprecated)

+

Scenarios

Currently, EVS replication pairs can be added to or removed from replication consistency groups through APIs only. For details, see Updating a Replication Consistency Group in the Elastic Volume Service API Reference.

+

If an EVS replication pair needs to be deleted after it has been added to a replication consistency group, remove this EVS replication pair from the group first, delete this EVS replication pair, and then delete the production disk and DR disk. For details, see Deleting an EVS Replication Pair and Deleting a Replication Consistency Group in the Elastic Volume Service API Reference.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Prerequisites

The replication consistency group status is available.

+
+

Procedure

  1. Pause the replication consistency group you need to update.

    For details, see Pausing a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

    Pausing a replication consistency group means that the data synchronization within the group is paused. Therefore, the data between production disks and DR disks will be temporarily inconsistent and needs to be synchronized after the replication consistency group update is complete.

    +
    +

  2. Update the replication consistency group, that is, add EVS replication pairs to or remove EVS replication pairs from the group.

    For details, see Updating a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

  3. Synchronize the data of a replication consistency group, which means that the data of all EVS replication pairs within the group is synchronized.

    For details, see Synchronizing a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

  4. Query the data synchronization status of the replication consistency group.

    For details, see Querying Details About a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

    When the replication status of the replication consistency group changes to active, the data in all EVS replication pairs of this group has been synchronized.

    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0030.html b/docs/evs/umn/evs_01_0030.html new file mode 100644 index 000000000..479704450 --- /dev/null +++ b/docs/evs/umn/evs_01_0030.html @@ -0,0 +1,22 @@ + + +

Planned Migration (Deprecated)

+

Scenarios

Production servers and production disks belong to the primary AZ, and DR servers and DR disks belong to the secondary AZ. Users can make API calls to perform a planned migration, for example, perform a primary/secondary AZ switchover for the replication consistency group and enable the servers and disks in the secondary AZ.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Prerequisites

  • The production server status is normal, and the deployed services are running properly.
  • The target production servers have been temporarily stopped.
  • The replication status of the replication consistency group is active, which means that data synchronization in all EVS replication pairs of the replication consistency group is complete.
+
+

Procedure

  1. Perform a primary/secondary AZ switchover for the replication consistency group.

    For details, see Performing a Primary/Secondary Switchover for a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

    Performing a primary/secondary switchover for a replication consistency group takes a relative long period of time, and it takes about 10 seconds for the system to respond the request.

    +
    +

  2. If Elastic Load Balancing (ELB) or EIPs are used, unbind the ELB or EIPs with the production servers and bind them to the DR servers.

    • For details about ELB, see Backend Server (Enhanced Load Balancer) in the Elastic Load Balancing User Guide.
    • For details about EIPs, see Elastic IP Address in the Virtual Private Cloud User Guide.
    +

  3. Verify that the DR server OSs can be normally started, deployed services are available, and the data is complete.
+
+
+ + diff --git a/docs/evs/umn/evs_01_0031.html b/docs/evs/umn/evs_01_0031.html new file mode 100644 index 000000000..00af3ee3e --- /dev/null +++ b/docs/evs/umn/evs_01_0031.html @@ -0,0 +1,20 @@ + + +

Failover (Deprecated)

+

Scenarios

When the production servers and disks in the primary AZ become faulty due to force majeure, users can make API calls to perform a failover for the replication consistency group and enable the DR servers and disks in the secondary AZ to ensure the service continuity.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Prerequisites

Confirm with the customer service that servers and disks in the production AZ are faulty, and the deployed services are unavailable.

+
+

Procedure

  1. Perform a failover for the replication consistency group.

    For details, see Performing a Failover for a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

  2. If Elastic Load Balancing (ELB) or EIPs are used, unbind the ELB or EIPs with the production servers and bind them to the DR servers.

    • For details about ELB, see Backend Server (Enhanced Load Balancer) in the Elastic Load Balancing User Guide.
    • For details about EIPs, see Elastic IP Address in the Virtual Private Cloud User Guide.
    +

  3. Verify that the DR server OSs can be normally started, deployed services are available, and the data is complete.
+
+
+ + diff --git a/docs/evs/umn/evs_01_0032.html b/docs/evs/umn/evs_01_0032.html new file mode 100644 index 000000000..b0853d00e --- /dev/null +++ b/docs/evs/umn/evs_01_0032.html @@ -0,0 +1,23 @@ + + +

Reprotection (Deprecated)

+

Scenarios

When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide services. After the fault in the faulty AZ has been restored, users can make API calls to reprotect a replication consistency group, that is, to enable the restored resources in the faulty AZ to function as DR servers and DR disks.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Prerequisites

  • A failover for the replication consistency group has been performed.
  • The faulty AZ has been restored.
  • The replication consistency group status is available.
  • The restored production server has been stopped.
+
+

Procedure

  1. Perform the reprotection for the replication consistency group to synchronize the disk data of the DR servers to the servers in the faulty AZ.

    For details, see Reprotecting a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

  2. Query the details about the replication consistency group.

    For details, see Querying Details About a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

    After the request has been delivered, the replication status of the replication consistency group changes to copying. Once the replication status changes to active, the data synchronization is complete.

    +

    The time required for the data synchronization within a replication consistency group varies depending on the number of EVS replication pairs in the group, EVS disk capacity, and amount of differential data generated after a primary AZ fault occurred. Normally, the data synchronization of a reprotection takes a relative long period of time. Please wait patiently.

    +
    +

  3. (Optional) If the services need to be migrated back to the restored primary AZ, you need to perform a planned migration. For details, see Planned Migration (Deprecated).
+
+
+ + diff --git a/docs/evs/umn/evs_01_0033.html b/docs/evs/umn/evs_01_0033.html new file mode 100644 index 000000000..b268d1fcc --- /dev/null +++ b/docs/evs/umn/evs_01_0033.html @@ -0,0 +1,186 @@ + + +

Initializing a Linux Data Disk (fdisk)

+

Scenarios

This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.

+

The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+

The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.

+
+

Prerequisites

  • A data disk has been attached to a server and has not been initialized.
  • You have logged in to the server.
    • For how to log in to an ECS, see the Elastic Cloud Server User Guide.
    • For how to log in to a BMS, see the Bare Metal Server User Guide.
    +
+
+

Creating and Mounting a Partition

The following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. The primary partition will be created using fdisk, and MBR is the default partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured with automatic mounting at system start.

+
+
  1. Run the following command to query information about the new data disk:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
+
+Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+
+Disk /dev/vdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
    +
    +

    In the command output, the server contains two disks. /dev/vda is the system disk, and /dev/vdb is the new data disk.

    +

  2. Run the following command to enter fdisk to partition the new data disk:

    fdisk New data disk

    +

    In this example, run the following command:

    +

    fdisk /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk /dev/vdb
+Welcome to fdisk (util-linux 2.23.2).
+
+Changes will remain in memory only, until you decide to write them.
+Be careful before using the write command.
+
+Device does not contain a recognized partition table
+Building a new DOS disklabel with disk identifier 0x38717fc1.
+
+Command (m for help):
    +
    +

  3. Enter n and press Enter to create a new partition.

    Information similar to the following is displayed:
    Command (m for help): n
+Partition type:
+   p   primary (0 primary, 0 extended, 4 free)
+   e   extended
    +
    +
    There are two types of disk partitions:
    • Choosing p creates a primary partition.
    • Choosing e creates an extended partition.
    +

    If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.

    +

    Disk partitions created using GPT are not categorized.

    +
    +
    +

  4. In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.

    Information similar to the following is displayed:
    Select (default p): p
+Partition number (1-4, default 1):
    +
    +

    Partition number indicates the serial number of the primary partition. The value ranges from 1 to 4.

    +

  5. Enter the serial number of the primary partition and press Enter. Primary partition number 1 is used in this example. One usually starts with partition number 1 when partitioning an empty disk.

    Information similar to the following is displayed:
    Partition number (1-4, default 1): 1
+First sector (2048-209715199, default 2048):
    +
    +

    First sector indicates the start sector. The value ranges from 2048 to 209715199, and the default value is 2048.

    +

  6. Select the default start sector 2048 and press Enter.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    First sector (2048-209715199, default 2048):
+Using default value 2048
+Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
    +
    +

    Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.

    +

  7. Select the default end sector 209715199 and press Enter.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +

    Information similar to the following is displayed:

    +
    Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
+Using default value 209715199
+Partition 1 of type Linux and of size 100 GiB is set
+
+Command (m for help):
    +

    A primary partition has been created for the new data disk.

    +

  8. Enter p and press Enter to view details about the new partition.

    Information similar to the following is displayed:
    Command (m for help): p
+
+Disk /dev/vdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x38717fc1
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vdb1            2048   209715199   104856576   83  Linux
+
+Command (m for help):
    +
    +

    Details about the /dev/vdb1 partition are displayed.

    +

  9. Enter w and press Enter to write the changes to the partition table.

    Information similar to the following is displayed:
    Command (m for help): w
+The partition table has been altered!
+
+Calling ioctl() to re-read partition table.
+Syncing disks.
    +
    +

    The partition is created.

    +

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

    +
    +

  10. Run the following command to synchronize the new partition table to the OS:

    partprobe

    +

  11. Run the following command to set the file system format for the new partition:

    mkfs -t File system format /dev/vdb1

    +

    In this example, run the following command to set the ext4 file system for the new partition:

    +

    mkfs -t ext4 /dev/vdb1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
+mke2fs 1.42.9 (28-Dec-2013)
+Filesystem label=
+OS type: Linux
+Block size=4096 (log=2)
+Fragment size=4096 (log=2)
+Stride=0 blocks, Stripe width=0 blocks
+6553600 inodes, 26214144 blocks
+1310707 blocks (5.00%) reserved for the super user
+First data block=0
+Maximum filesystem blocks=2174746624
+800 block groups
+32768 blocks per group, 32768 fragments per group
+8192 inodes per group
+Superblock backups stored on blocks:
+        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
+        4096000, 7962624, 11239424, 20480000, 23887872
+
+Allocating group tables: done
+Writing inode tables: done
+Creating journal (32768 blocks): done
+Writing superblocks and filesystem accounting information: done
    +
    +

    The formatting takes a period of time. Observe the system running status and do not exit.

    +

    The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.

    +
    +

  12. Run the following command to create a mount point:

    mkdir Mount point

    +

    In this example, run the following command to create the /mnt/sdc mount point:

    +

    mkdir /mnt/sdc

    +

  13. Run the following command to mount the new partition on the created mount point:

    mount Disk partition Mount point

    +

    In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:

    +

    mount /dev/vdb1 /mnt/sdc

    +

  14. Run the following command to view the mount result:

    df -TH

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.1M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
    +

    New partition /dev/vdb1 is mounted on /mnt/sdc.

    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +

+

Setting Automatic Mounting at System Start

Modify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.

+

The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.

+

UUID is the unique character string for disk partitions in a Linux system.

+
+
  1. Run the following command to query the partition UUID:

    blkid Disk partition

    +

    In this example, run the following command to query the UUID of the /dev/vdb1 partition:

    +

    blkid /dev/vdb1

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
    +

    The UUID of the /dev/vdb1 partition is displayed.

    +

  2. Run the following command to open the fstab file using the vi editor:

    vi /etc/fstab

    +

  3. Press i to enter the editing mode.
  4. Move the cursor to the end of the file and press Enter. Then, add the following information:

    UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
    +

  5. Press Esc, enter :wq, and press Enter.

    The system saves the configurations and exits the vi editor.

    +

  6. Perform the following operations to verify the automatic mounting function:

    1. Run the following command to unmount the partition:

      umount Disk partition

      +

      In this example, run the following command:

      +

      umount /dev/vdb1

      +
    2. Run the following command to reload all the content in the /etc/fstab file:

      mount -a

      +
    3. Run the following command to query the file system mounting information:

      mount | grep Mount point

      +

      In this example, run the following command:

      +

      mount | grep /mnt/sdc

      +

      If information similar to the following is displayed, the automatic mounting function takes effect:

      +
      root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
      +
    +

+
+
+
+
+
Parent topic: Initialize an EVS Data Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0034.html b/docs/evs/umn/evs_01_0034.html new file mode 100644 index 000000000..11a37c746 --- /dev/null +++ b/docs/evs/umn/evs_01_0034.html @@ -0,0 +1,174 @@ + + +

Initializing a Linux Data Disk (parted)

+

Scenarios

This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.

+

The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+

The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.

+
+

Prerequisites

  • A data disk has been attached to a server and has not been initialized.
  • You have logged in to the server.
    • For how to log in to an ECS, see the Elastic Cloud Server User Guide.
    • For how to log in to a BMS, see the Bare Metal Server User Guide.
    +
+
+

Creating and Mounting a Partition

The following example shows you how a new partition can be created on a new data disk that has been attached to a server. The partition will be created using parted, and GPT is used as the partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured automatic mounting at system start.

+
+
  1. Run the following command to query information about the new data disk:

    lsblk

    +
    Information similar to the following is displayed:
    root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  100G  0 disk
    +
    +

    In the command output, the server contains two disks. /dev/vda is the system disk, and /dev/vdb is the new data disk.

    +

  2. Run the following command to enter parted to partition the new data disk:

    parted New data disk

    +

    In this example, run the following command:

    +

    parted /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# parted /dev/vdb
+GNU Parted 3.1
+Using /dev/vdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted)
    +
    +

  3. Enter p and press Enter to view the current disk partition style.

    Information similar to the following is displayed:
    (parted) p
+Error: /dev/vdb: unrecognised disk label
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 107GB
+Sector size (logical/physical): 512B/512B
+Partition Table: unknown
+Disk Flags:
+(parted)
    +
    +

    In the command output, the Partition Table value is unknown, indicating that no partition style is set for the new disk.

    +

  4. Run the following command to set the disk partition style:

    mklabel Disk partition style

    +

    In this example, run the following command to set the partition style to GPT: (Disk partition styles can be MBR or GPT.)

    +

    mklabel gpt

    +

    The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.

    +

    If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.

    +
    +

  5. Enter p and press Enter to view the disk partition style.

    Information similar to the following is displayed:
    (parted) mklabel gpt
+(parted) p
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 107GB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start  End  Size  File system  Name  Flags
+
+(parted)
    +
    +

    In the command output, the Partition Table value is gpt, indicating that the disk partition style is GPT.

    +

  6. Enter unit s and press Enter to set the measurement unit of the disk to sector.
  7. Run the following command and press Enter:

    mkpart Partition name Start sector End sector

    +

    In this example, run the following command:

    +

    mkpart test 2048s 100%

    +

    In this example, one partition is created for the new data disk. Variable 2048s indicates the disk start sector, and variable 100% indicates the disk end sector. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.

    +
    Information similar to the following is displayed:
    (parted) mkpart opt 2048s 100%
+(parted)
    +
    +

  8. Enter p and press Enter to view details about the new partition.

    Information similar to the following is displayed:
    (parted) p
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 209715200s
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start  End         Size        File system  Name  Flags
+ 1      2048s  209713151s  209711104s               test
+
+(parted)
    +
    +

  9. Enter q and press Enter to exit parted.

    Information similar to the following is displayed:
    (parted) q
+Information: You may need to update /etc/fstab.
    +
    +

    You can set automatic disk mounting by updating the /etc/fstab file. Before updating the file, set the file system format for the partition and mount the partition on the mount point.

    +

  10. Run the following command to view the disk partition information:

    lsblk

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  100G  0 disk
+└─vdb1 253:17   0  100G  0 part
    +
    +

    In the command output, /dev/vdb1 is the partition you created.

    +

  11. Run the following command to set the file system format for the new partition:

    mkfs -t File system format /dev/vdb1

    +

    In this example, run the following command to set the ext4 file system for the new partition:

    +

    mkfs -t ext4 /dev/vdb1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
+mke2fs 1.42.9 (28-Dec-2013)
+Filesystem label=
+OS type: Linux
+Block size=4096 (log=2)
+Fragment size=4096 (log=2)
+Stride=0 blocks, Stripe width=0 blocks
+6553600 inodes, 26213888 blocks
+1310694 blocks (5.00%) reserved for the super user
+First data block=0
+Maximum filesystem blocks=2174746624
+800 block groups
+32768 blocks per group, 32768 fragments per group
+8192 inodes per group
+Superblock backups stored on blocks:
+        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
+        4096000, 7962624, 11239424, 20480000, 23887872
+
+Allocating group tables: done
+Writing inode tables: done
+Creating journal (32768 blocks): done
+Writing superblocks and filesystem accounting information: done
    +
    +

    The formatting takes a period of time. Observe the system running status and do not exit.

    +

    The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.

    +
    +

  12. Run the following command to create a mount point:

    mkdir Mount point

    +

    In this example, run the following command to create the /mnt/sdc mount point:

    +

    mkdir /mnt/sdc

    +

  13. Run the following command to mount the new partition on the created mount point:

    mount Disk partition Mount point

    +

    In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:

    +

    mount /dev/vdb1 /mnt/sdc

    +

  14. Run the following command to view the mount result:

    df -TH

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.0M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
    +

    New partition /dev/vdb1 is mounted on /mnt/sdc.

    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +

+

Setting Automatic Mounting at System Start

Modify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.

+

The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.

+

UUID is the unique character string for disk partitions in a Linux system.

+
+
  1. Run the following command to query the partition UUID:

    blkid Disk partition

    +

    In this example, run the following command to query the UUID of the /dev/vdb1 partition:

    +

    blkid /dev/vdb1

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
    +

    The UUID of the /dev/vdb1 partition is displayed.

    +

  2. Run the following command to open the fstab file using the vi editor:

    vi /etc/fstab

    +

  3. Press i to enter the editing mode.
  4. Move the cursor to the end of the file and press Enter. Then, add the following information:

    UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
    +

  5. Press Esc, enter :wq, and press Enter.

    The system saves the configurations and exits the vi editor.

    +

  6. Perform the following operations to verify the automatic mounting function:

    1. Run the following command to unmount the partition:

      umount Disk partition

      +

      In this example, run the following command:

      +

      umount /dev/vdb1

      +
    2. Run the following command to reload all the content in the /etc/fstab file:

      mount -a

      +
    3. Run the following command to query the file system mounting information:

      mount | grep Mount point

      +

      In this example, run the following command:

      +

      mount | grep /mnt/sdc

      +

      If information similar to the following is displayed, the automatic mounting function takes effect:

      +
      root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
      +
    +

+
+
+
+
+
Parent topic: Initialize an EVS Data Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0035.html b/docs/evs/umn/evs_01_0035.html new file mode 100644 index 000000000..0974fb4b9 --- /dev/null +++ b/docs/evs/umn/evs_01_0035.html @@ -0,0 +1,170 @@ + + +

Partition and File System Extension Preparations (Linux)

+

Before extending the disk partition and file system, you must check the disk partition style and file system format, and then select the appropriate operation accordingly.

+
  1. To view the disk partition style, see the following methods: +
  2. To select the appropriate operation, see Table 1. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Disk partition and file system extension scenarios

    Disk

    +

    Scenario

    +

    Method

    +

    System disk

    +

    Create a new MBR partition with the additional space.

    +

    Creating a New MBR Partition

    +

    Allocate the additional space to an existing MBR partition.

    +    		 +

    Data disk

    +

    Create a new MBR partition with the additional space.

    +

    Creating a New MBR Partition

    +

    Allocate the additional space to an existing MBR partition.

    +

    Extending an Existing MBR Partition

    +

    Create a new GPT partition with the additional space.

    +

    Creating a New GPT Partition

    +

    Allocate the additional space to an existing GPT partition.

    +

    Extending an Existing GPT Partition

    +

    SCSI data disk

    +

    Create a new MBR partition with the additional space.

    +

    Creating a New MBR Partition

    +

    Allocate the additional space to an existing MBR partition.

    +

    Extending an Existing MBR Partition

    +
    +
    +

    The maximum disk capacity that MBR supports is 2 TB, and the disk space exceeding 2 TB cannot be used.

    +

    If your disk uses MBR and you need to expand the disk capacity to over 2 TB, change the partition style from MBR to GPT. Ensure that the disk data has been backed up before changing the partition style because services will be interrupted and data on the disk will be cleared during this change.

    +
    +
+

Method 1: Check Partition Style and File System Format Using fdisk

  1. Run the following command to view all the disks attached to the server:

    lsblk

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  150G  0 disk
+└─vdb1 253:17   0  100G  0 part /mnt/sdc
    +
    +

    In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GB added has not been allocated yet. Therefore, /dev/vdb has 150 GB, and /dev/vdb1 has 100 GB.

    +

  2. Run the following command to view the current disk partition style:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
+
+Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+
+Disk /dev/vdb: 161.1 GB, 161061273600 bytes, 314572800 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x38717fc1
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vdb1            2048   209715199   104856576   83  Linux
    +
    +

    The value in the System column indicates the disk partition style. Value Linux indicates the MBR partition style. Value GPT indicates the GPT partition style.

    +
    • If the disk partitions displayed are inconsistent with those obtained in 1, the partition that is not displayed uses the GPT partition style and has unallocated space. In this case, you cannot query all the partition information using the fdisk -l command. Go to Method 2: Check Partition Style and File System Format Using parted.
    • If the disk partitions displayed are consistent with those obtained in 1, continue with the following operations.
    +

  3. Run the following command to view the partition's file system format:

    blkid Disk partition

    +

    In this example, run the following command:

    +

    blkid /dev/vdb1

    +

    In the command output, the TYPE value is ext4, indicating that /dev/vdb1's file system format is ext4.

    +

  4. Run the following command to view the file system status:

    ext*: e2fsck -n Disk partition

    +

    xfs: xfs_repair -n Disk partition

    +

    In this example, the ext4 file system is used. Therefore, run the following command:

    +

    e2fsck -n /dev/vdb1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# e2fsck -n /dev/vdb1
+e2fsck 1.42.9 (28-Dec-2013)
+Warning!  /dev/vdb1 is mounted.
+Warning: skipping journal recovery because doing a read-only filesystem check.
+/dev/vdb1: clean, 11/6553600 files, 459544/26214144 blocks
    +
    +

    If the file system status is clean, the file system status is normal. Otherwise, rectify the faulty and then perform the capacity expansion.

    +

+
+

Method 2: Check Partition Style and File System Format Using parted

  1. Run the following command to view all the disks attached to the server:

    lsblk

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  150G  0 disk
+└─vdb1 253:17   0  100G  0 part /mnt/sdc
    +
    +

    In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GB added has not been allocated yet. Therefore, /dev/vdb has 150 GB, and /dev/vdb1 has 100 GB.

    +

  2. Run the following command and enter p to view the disk partition style:

    parted Disk

    +

    For example, run the following command to view /dev/vdb's partition style:

    +

    parted /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# parted /dev/vdb
+GNU Parted 3.1
+Using /dev/vdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted) p
+Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the
+disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
+Fix/Ignore/Cancel? Fix
+Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 104857600
+blocks) or continue with the current setting?
+Fix/Ignore? Fix
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 161GB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start   End    Size   File system  Name  Flags
+ 1      1049kB  107GB  107GB  ext4         test
+
+(parted)
    +
    +
    In the command output, parameter Partition Table indicates the disk partition style. Value msdos indicates the MBR partition style, and value gpt indicates the GPT partition style.
    • If the following error information is displayed, enter Fix.
      Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the
+disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
      +

      The GPT partition table information is stored at the start of the disk. To reduce the risk of damage, a backup of the information is saved at the end of the disk. When you expand the disk capacity, the end of the disk changes accordingly. In this case, enter Fix to move the backup file of the information to new disk end.

      +
    • If the following warning information is displayed, enter Fix.
      Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 104857600
+blocks) or continue with the current setting?
+Fix/Ignore? Fix
      +

      Enter Fix as prompted. The system automatically sets the GPT partition style for the additional space.

      +
    +
    +

  3. Enter q and press Enter to exit parted.
+
+
+ + diff --git a/docs/evs/umn/evs_01_0036.html b/docs/evs/umn/evs_01_0036.html new file mode 100644 index 000000000..584ca2858 --- /dev/null +++ b/docs/evs/umn/evs_01_0036.html @@ -0,0 +1,22 @@ + + +

Attaching a Non-Shared Disk

+

Scenarios

Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the data disks to servers for use.

+
A system disk must be created during a server creation and is automatically attached. In the disk list, the function of such disks is displayed as System disk, and the status is displayed as In-use. After a system disk is detached from a server, the disk function changes to Bootable disk, and the status changes to Available.

Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the device name selected.

+
+
+

This section describes how to attach a non-shared disk. A non-shared disk can be attached to one server only.

+
+

Attaching the Disk on the EVS Console

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. Locate the target disk in the list and click Attach.

    The Attach Disk dialog box is displayed, as shown in Figure 1.
    Figure 1 Attach Disk dialog box
    +
    +

  5. Select the server and then select a device name from the drop-down list. Ensure that the disk and server are in the same AZ.
  6. Click OK to return to the disk list page. The status of the disk is Attaching, indicating that the disk is being attached to the server. When the disk status changes to In-use, the disk is successfully attached.
  7. Initialize the disk.

    After the disk has been attached to a server, the disk can be used only after you have initialized it. For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

    +

+
+
+
+
+
Parent topic: Attach an EVS Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0037.html b/docs/evs/umn/evs_01_0037.html new file mode 100644 index 000000000..b0a25cf5b --- /dev/null +++ b/docs/evs/umn/evs_01_0037.html @@ -0,0 +1,25 @@ + + +

Attaching a Shared Disk

+

Scenarios

Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the data disks to servers for use.

+

This section describes how to attach a shared disk.

+
+

Constraints

  • A shared disk can be attached to a maximum of 16 servers. These servers and the shared disk must be in the same AZ within a region.
  • If a shared disk is in the In-use state, ensure that the maximum number of servers that the disk can be attached to has not been reached.
  • All the servers of a shared disk must run either Windows or Linux no matter the disk is attached to them in a batch or individually.

    For example, if you attach a shared disk to multiple Windows servers in a batch and then detach it from all its servers, the disk cannot be attached to Linux servers later. This is because Windows and Linux support different file systems and cannot identify the original file system on the disk. Improper operations may damage the original file system.

    +
+
  • A shared disk can only be used as a data disk. It cannot be used as a system disk.
+
+

Attaching the Disk on the EVS Console

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. Locate the target disk in the list and click Attach.

    The Attach Disk dialog box is displayed.

    +
    Shared disks support batch attachment so that you can attach a shared disk to multiple servers at a time. The left area in the Attach Disk dialog box shows the server list. After you select the target servers, the selected servers will be displayed in the right area.
    Figure 1 Attach Disk
    +
    +

  5. Select the target servers and then select a device name from the drop-down list for each server you selected. Ensure that the disk and servers are in the same AZ.
  6. Click OK to return to the disk list page. The status of the disk is Attaching, indicating that the disk is being attached to the servers. When the disk status changes to In-use, the disk is successfully attached.

    If you simply attach a shared disk to multiple servers, files cannot be shared between the servers as shared disks do not have the cluster capability. Therefore, build a shared file system or deploy a cluster management system to share files between servers.

    +
    +

+
+
+
+
+
Parent topic: Attach an EVS Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0038.html b/docs/evs/umn/evs_01_0038.html new file mode 100644 index 000000000..bf10c355e --- /dev/null +++ b/docs/evs/umn/evs_01_0038.html @@ -0,0 +1,59 @@ + + +

Introduction to Data Disk Initialization Scenarios and Partition Styles

+

Scenarios

After a disk is attached to a server, you need to log in to the server to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.
  • System disk

    A system disk does not require manual initialization because it is automatically created and initialized upon server creation. The default disk partition style is master boot record (MBR).

    +
  • Data disk
    • If a data disk is created along with a server, it will be automatically attached to the server.
    • If a data disk is created separately, you need to manually attach it to a server.
    +

    In both cases, you must initialize the data disk before using it. Choose a proper disk partition style based on your service plan.

    +
+
+
+

Constraints

A disk created from a data source does not need to be initialized. Such a disk contains the data of the data source in the beginning. Initializing the disk may clear the initial data on this disk.

+
+

Disk Partition Styles

Table 1 lists the common disk partition styles. In Linux, different disk partition styles require different partitioning tools.

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Disk partition styles

Disk Partition Style

+

Maximum Disk Capacity Supported

+

Maximum Number of Partitions Supported

+

Linux Partitioning Tool

+

Master Boot Record (MBR)

+

2 TB

+
  • 4 primary partitions
  • 3 primary partitions and 1 extended partition
+
With MBR, one may create several primary partitions and an extended partition. An extended partition must be divided into several logical partitions before use. For example, if 6 partitions need to be created, you can create the partitions in the following two ways:
  • 3 primary partitions and 1 extended partition, with the extended partition divided into 3 logical partitions
  • 1 primary partition and 1 extended partition, with the extended partition divided into 5 logical partitions
+
+
  • fdisk
  • parted
+

GUID Partition Table (GPT)

+

18 EB

+

1 EB = 1048576 TB

+

Unlimited

+

Disk partitions created using GPT are not categorized.

+

parted

+
+
+

The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.

+

If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.

+
+
+
+
+
+
Parent topic: Initialize an EVS Data Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0039.html b/docs/evs/umn/evs_01_0039.html new file mode 100644 index 000000000..ca8e11c8b --- /dev/null +++ b/docs/evs/umn/evs_01_0039.html @@ -0,0 +1,17 @@ + + + +

Appendix

+ +

+
+ + + diff --git a/docs/evs/umn/evs_01_0040.html b/docs/evs/umn/evs_01_0040.html new file mode 100644 index 000000000..3e83fdee4 --- /dev/null +++ b/docs/evs/umn/evs_01_0040.html @@ -0,0 +1,149 @@ + + +

EVS Disk Status

+
An EVS disk has several statuses. Table 1 lists the EVS disk statuses, the meaning of each status, and the operations a disk in each status allows. +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Disk status details

EVS Disk Status

+

Description

+

Allowed Operation

+

In-use

+

The EVS disk is attached to a server and is in use.

+
  • Detaching
  • Creating backups
  • Expanding
    NOTE:

    If a shared EVS disk is in the In-use state, the disk can be attached.

    +

    If a shared EVS disk is in the In-use state, the disk cannot be expanded.

    +
    +
+

Available

+

The EVS disk has not been attached to any server and can be attached.

+
  • Attaching
  • Expanding
  • Deleting
  • Creating backups
  • Rolling back snapshots to EVS disks
+

Creating

+

The EVS disk is being created.

+

None

+

Attaching

+

The EVS disk is being attached to a server.

+

None

+

Detaching

+

The EVS disk is being detached from a server.

+

None

+

Deleting

+

The EVS disk is being deleted.

+

None

+

Restoring

+

A backup is being used to restore the EVS disk.

+

None

+

Expanding

+

The capacity of the EVS disk is being expanded.

+

None

+

Uploading

+

Data on the EVS disk is being uploaded to an image. This state occurs when you create an image from a server.

+

None

+

Downloading

+

Data is being downloaded from an image to the EVS disk. This state occurs when you create a server.

+

None

+

Error

+

An error occurs when you try to create an EVS disk.

+

Deleting

+

Deletion failed

+

An error occurs when you try to delete the EVS disk.

+

None

+

Expansion failed

+

An error occurs when you try to expand the capacity of the EVS disk.

+

Deleting

+

Restoration failed

+

An error occurs when you try to restore the EVS disk from a backup.

+

Deleting

+

Rolling back

+

Data on the EVS disk is being restored from a snapshot.

+
NOTE:
  • When you roll back a snapshot to an EVS disk, you can only roll back the snapshot to the source EVS disk. Rollback to a specified disk is not supported.
  • You can roll back an EVS disk from a snapshot only when the disk is in the Available or Rollback failed state.
+
+

None

+

Rollback failed

+

An error occurs when the EVS disk is rolled back from a snapshot.

+
  • Deleting
  • Rolling back snapshots to EVS disks
+

Awaiting transfer

+

The EVS disk is awaiting for a transfer.

+

None

+
+
+

If an EVS disk status is Error, Deletion failed, Expansion failed, Restoration failed, or Rollback failed, you can rectify the error by following the steps provided in What Should I Do If an Error Occurs on My EVS Disk?.

+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/umn/evs_01_0041.html b/docs/evs/umn/evs_01_0041.html new file mode 100644 index 000000000..339ca6127 --- /dev/null +++ b/docs/evs/umn/evs_01_0041.html @@ -0,0 +1,76 @@ + + +

EVS Snapshot Status

+
An EVS snapshot has several statuses. Table 1 lists the EVS snapshot statuses, the meaning of each status, and the operations a snapshot in each status allows. +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Snapshot status details

Snapshot Status

+

Description

+

Allowed Operation

+

Creating

+

The snapshot is being created.

+

No operations are allowed.

+

Available

+

The snapshot is successfully created.

+
  • Creating EVS disks using snapshots
  • Deleting snapshots
  • Rolling back snapshots to source EVS disks
+

Deleting

+

The snapshot is being deleted.

+

No operations are allowed.

+

Error

+

An error occurs when you try to create a snapshot.

+

Deleting

+

Deletion failed

+

An error occurs when you try to delete a snapshot.

+

No operations are allowed.

+

Rolling back

+

The snapshot is rolling back data.

+
NOTE:
  • When you roll back a snapshot to an EVS disk, you can only roll back the snapshot to the source EVS disk. Rollback to a specified disk is not supported.
  • You can roll back an EVS disk from a snapshot only when the disk is in the Available or Rollback failed state.
+
+

No operations are allowed.

+

Backing up

+

This status is available only to temporary snapshots. When you create a backup for an EVS disk, a temporary snapshot is automatically created. This status indicates that a temporary snapshot is being created during the backup creation.

+
NOTE:

Temporary snapshots are created through the CBR service. Do not perform any operation on these snapshots.

+
+

No operations are allowed.

+
+
+
+
+
+
+
Parent topic: Appendix
+
+
+ diff --git a/docs/evs/umn/evs_01_0042.html b/docs/evs/umn/evs_01_0042.html new file mode 100644 index 000000000..2b28f180e --- /dev/null +++ b/docs/evs/umn/evs_01_0042.html @@ -0,0 +1,19 @@ + + +

Managing EVS Disk Transfer

+

Scenarios

Through EVS disk transfer, EVS disks can be transferred from one account to another. After the transfer succeeds, the ownerships of the EVS disks belong to the target account only. Currently, only data disks can be transferred.

+

Currently, users can use the disk transfer function via API only. For details, see chapter "EVS Disk Transfer" in the Elastic Volume Service API Reference.

+
+

Constraints

  • Encrypted EVS disks cannot be transferred.
  • EVS disks with backups and snapshots available cannot be transferred.
  • EVS disks associated with backup policies cannot be transferred.
  • EVS disks used as system disks cannot be transferred.
  • EVS disks in EVS replication pairs cannot be transferred.
+
+

Procedure

The following example shows you how to transfer an EVS disk from account A to account B. User A belongs to account A, and user B belongs to account B. User A creates the transfer. User B accepts the transfer through the transfer ID (transfer_id) and authentication key (auth_key). After the transfer has been accepted, the transfer is complete. Figure 1 shows the basic transfer process.
  • transfer_id specifies the disk transfer ID. Each EVS disk transfer has a transfer ID, and user B uses this ID to accept the disk transfer.
  • auth_key specifies the identity authentication key of the disk transfer. Each EVS disk transfer has an authentication key, and user B uses this key for authentication when accepting the disk transfer.
+
+
Figure 1 EVS disk transfer process
+
+
  1. User A creates the transfer. For details, see "Creating a Disk Transfer" in the Elastic Volume Service API Reference.

    After the transfer is successfully created, transfer_id and auth_key are returned.

    +

  2. (Optional) User A views the disk transfer. For details, see "Querying Details of a Disk Transfer" in the Elastic Volume Service API Reference. If multiple disk transfers have been created, user A can query all disk transfers. For details, see "Querying All Disk Transfers" or "Querying Details of All Disk Transfers" in the Elastic Volume Service API Reference.
  3. User A delivers the returned transfer_id and auth_key to user B.
  4. Check whether user B is going to accept the disk transfer.

    • If yes, go to 5.
    • If no, no further action is required.

      User A can delete the unaccepted disk transfer. For details, see "Deleting a Disk Transfer" in the Elastic Volume Service API Reference.

      +
    +

  5. User B accepts transfer_id and auth_key.
  6. User B accepts the transfer through transfer_id and auth_key. For details, see "Accepting a Disk Transfer" in the Elastic Volume Service API Reference.
+
+
+ diff --git a/docs/evs/umn/evs_01_0043.html b/docs/evs/umn/evs_01_0043.html new file mode 100644 index 000000000..5fcc744b9 --- /dev/null +++ b/docs/evs/umn/evs_01_0043.html @@ -0,0 +1,21 @@ + + +

Expanding EVS Disks in a Replication Consistency Group (Deprecated)

+

Scenarios

Users can make an API call to expand the EVS disks in one or multiple EVS replication pairs of a replication consistency group. In such an expansion operation, two EVS disks in one EVS replication pair are expanded together.

+

The status and replication_status values of the replication consistency group remain unchanged before and after capacity expansion.

+

If the expansion fails, contact customer service to locate and rectify the fault. After the fault is rectified, expand the disks again.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+

Prerequisites

  • The status value of replication consistency group must be available, which means that the group status is normal.
  • The replication_status value of the replication consistency group is not error.
+
+

Procedure

  1. Make an API call to expand the EVS disks in one or multiple EVS replication pairs of the replication consistency group.

    For details, see Expanding EVS Disks a Replication Consistency Group in the Elastic Volume Service API Reference.

    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0044.html b/docs/evs/umn/evs_01_0044.html new file mode 100644 index 000000000..e317fcc02 --- /dev/null +++ b/docs/evs/umn/evs_01_0044.html @@ -0,0 +1,106 @@ + + +

Viewing EVS Monitoring Data

+

Description

This section describes monitored metrics reported by EVS to Cloud Eye as well as their namespaces and dimensions. You can use console or APIs provided by Cloud Eye to query the metrics of the monitored objects and alarms generated for EVS.

+
+

Namespace

SYS.EVS

+
+

Metrics

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 EVS metrics

Metric ID

+

Metric Name

+

Description

+

Value Range

+

Monitored Object

+

Monitoring Period (Raw Data)

+

disk_device_read_bytes_rate

+

Disk Read Bandwidth

+

Number of bytes read from the monitored disk per second

+

Unit: Bytes/s

+

≥ 0 bytes/s

+

EVS disk

+

5 minutes

+

disk_device_write_bytes_rate

+

Disk Write Bandwidth

+

Number of bytes written to the monitored disk per second

+

Unit: Bytes/s

+

≥ 0 bytes/s

+

EVS disk

+

5 minutes

+

disk_device_read_requests_rate

+

Disk Read IOPS

+

Number of read requests sent to the monitored disk per second

+

Unit: Requests/s

+

≥ 0 Requests/s

+

EVS disk

+

5 minutes

+

disk_device_write_requests_rate

+

Disk Write IOPS

+

Number of write requests sent to the monitored disk per second

+

Unit: Requests/s

+

≥ 0 Requests/s

+

EVS disk

+

5 minutes

+
+
+
+

Dimension

+
+ + + + + + + +

Key

+

Value

+

disk_name

+

Server ID-drive letter, for example, 6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d-vda (vda is the drive letter)

+
+
+
+

Viewing Monitoring Data

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Storage, click Elastic Volume Service.

    The disk list page is displayed.

    +

  4. In the EVS disk list, click the name of the disk you want to view the monitoring data.

    The disk details page is displayed.

    +

  5. On the Attachments tab, locate the row that contains the server and click View Monitoring Data in the Operation column.

    The monitoring graphs page is displayed.

    +

  6. You can view the disk monitoring data by metric or monitored duration.

    For more information about Cloud Eye, see the Cloud Eye User Guide.

    +

+
+
+ diff --git a/docs/evs/umn/evs_01_0045.html b/docs/evs/umn/evs_01_0045.html new file mode 100644 index 000000000..6c5590403 --- /dev/null +++ b/docs/evs/umn/evs_01_0045.html @@ -0,0 +1,48 @@ + + +

Initializing a Windows Data Disk (Windows Server 2016)

+

Scenarios

This section uses Windows Server 2016 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.

+

The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. For details about disk partition styles, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+

The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.

+
+

Prerequisites

  • A data disk has been attached to a server and has not been initialized.
  • You have logged in to the server.
    • For how to log in to an ECS, see the Elastic Cloud Server User Guide.
    • For how to log in to a BMS, see the Bare Metal Server User Guide.
    +
+
+

Procedure

  1. On the desktop of the server, click the start icon in the lower left corner.

    The Windows Server window is displayed.

    +

  2. Click Server Manager.

    The Server Manager window is displayed.

    +
    Figure 1 Server Manager
    +

  3. In the upper right corner, choose Tools > Computer Management.

    The Computer Management window is displayed.

    +
    Figure 2 Computer Management
    +

  4. Choose Storage > Disk Management.

    Disks are displayed in the right pane. If there is a disk that is not initialized, the system will prompt you with the Initialize Disk dialog box.
    Figure 3 Disk list
    +
    +

  5. In the Initialize Disk dialog box, the to-be-initialized disk is selected. Select a disk partition style and click OK. In this example, GPT (GUID Partition Table) is selected.

    The Computer Management window is displayed.
    Figure 4 Computer Management (Windows Server 2016)
    +
    +

    The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.

    +

    If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.

    +
    +
    +

  6. Right-click at the unallocated disk space and choose New Simple Volume from the shortcut menu.

    The New Simple Volume Wizard window is displayed.
    Figure 5 New Simple Volume Wizard (Windows Server 2016)
    +
    +

  7. Follow the prompts and click Next.

    The Specify Volume Size page is displayed.
    Figure 6 Specify Volume Size (Windows Server 2016)
    +
    +

  8. Specify the volume size and click Next. The system selects the maximum volume size by default. You can specify the volume size as required. In this example, the default setting is used.

    The Assign Drive Letter or Path page is displayed.
    Figure 7 Assign Driver Letter or Path (Windows Server 2016)
    +
    +

  9. Assign a drive letter or path to your partition and click Next. The system assigns drive letter D by default. In this example, the default setting is used.

    The Format Partition page is displayed.

    +
    Figure 8 Format Partition (Windows Server 2016)
    +

  10. Specify format settings and click Next. The system selects the NTFS file system by default. You can specify the file system type as required. In this example, the default setting is used.

    The Completing the New Simple Volume Wizard page is displayed.
    Figure 9 Completing the New Simple Volume Wizard (Windows Server 2016)
    +

    The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.

    +
    +
    +

  11. Click Finish.

    Wait for the initialization to complete. When the volume status changes to Healthy, the initialization has finished successfully, as shown in Figure 10.
    Figure 10 Disk initialization succeeded (Windows Server 2016)
    +
    +

  12. After the volume is created, click on the task bar and check whether a new volume appears in This PC. In this example, New Volume (D:) is the new volume.

    If New Volume (D:) appears, the disk is successfully initialized and no further action is required.
    Figure 11 This PC (Windows Server 2016)
    +
    +

+
+
+
+
+
Parent topic: Initialize an EVS Data Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0048.html b/docs/evs/umn/evs_01_0048.html new file mode 100644 index 000000000..122e6063c --- /dev/null +++ b/docs/evs/umn/evs_01_0048.html @@ -0,0 +1,51 @@ + + +

Differences Between EVS Disk Backup and EVS Snapshot

+

Both EVS disk backup and EVS snapshot provide redundancies for the EVS disk data to improve reliability. Table 1 lists the differences between them.

+ +
+ + + + + + + + + + + + + + + + + + + +
Table 1 Differences between backups and snapshots

Item

+

Storage Solution

+

Data Synchronization

+

DR Range

+

Service Recovery

+

Backup

+

Backup data is stored in OBS, instead of disks. This ensures data restoration upon disk data loss or corruption.

+

A backup is the data copy of a disk at a given point in time. CBR supports automatic backup by configuring backup policies. Deleting a disk will not clear its backups.

+

A backup and its source disk reside in the same AZ.

+

Data can be recovered and services can be restored by restoring the backup data to original disks or creating new disks from backups, ensuring excellent data reliability.

+

Snapshot

+

Snapshot data is stored with disk data.

+
NOTE:

Creating a backup requires a certain amount of time because data needs to be transferred. Therefore, creating or rolling back a snapshot consumes less time than creating a backup.

+
+

A snapshot is the state of a disk at a specific point in time. If a disk is deleted, all the snapshots created for this disk will also be deleted. If you have reinstalled or changed the server OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.

+

A snapshot and its source disk reside in the same AZ.

+

You can use a snapshot to roll back its original disk or create a disk for data restoration and service recovery.

+
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0057.html b/docs/evs/umn/evs_01_0057.html new file mode 100644 index 000000000..b7791d85a --- /dev/null +++ b/docs/evs/umn/evs_01_0057.html @@ -0,0 +1,12 @@ + + +

Basic Operation Procedure

+
Figure 1 shows the basic EVS operation procedure.
Figure 1 Basic operation procedure
+
+
+
+
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/evs/umn/evs_01_0058.html b/docs/evs/umn/evs_01_0058.html new file mode 100644 index 000000000..62d1cfccb --- /dev/null +++ b/docs/evs/umn/evs_01_0058.html @@ -0,0 +1,24 @@ + + +

Initialize an EVS Data Disk

+

+
+ + diff --git a/docs/evs/umn/evs_01_0059.html b/docs/evs/umn/evs_01_0059.html new file mode 100644 index 000000000..01658f649 --- /dev/null +++ b/docs/evs/umn/evs_01_0059.html @@ -0,0 +1,19 @@ + + +

Disk Capacity Expansion

+
+ + diff --git a/docs/evs/umn/evs_01_0060.html b/docs/evs/umn/evs_01_0060.html new file mode 100644 index 000000000..7c200ffb5 --- /dev/null +++ b/docs/evs/umn/evs_01_0060.html @@ -0,0 +1,18 @@ + + +

EVS Replication Operation Procedure (Deprecated)

+
For the EVS replication concepts, see EVS Replication (Deprecated). This chapter describes the basic functions and operations of EVS replication. Figure 1 shows the operation procedure.
  1. Performing pre-configuration operations before using EVS replication: Create DR servers, configure the virtual IP address for servers, and collect server information.
  2. Creating EVS replication pairs: Specify production disks in the primary AZ and DR disks in the secondary AZ to create EVS replication pairs.
  3. Creating replication consistency groups: Specify EVS replication pairs to create replication consistency groups.
  4. After EVS replication pairs and replication consistency groups are created, you can perform the following operations as required:
    • Updating a replication consistency group:
      1. Pause the replication consistency group if the group status is not paused.
      2. Add or remove EVS replication pairs from the replication consistency group.
      3. Synchronize the data in EVS replication pairs of the replication consistency group.
      +
    • Performing a planned migration: Switch the secondary AZ to the primary AZ and enable resources such as the DR servers and DR disks in the secondary AZ.
    • Performing a failover:
      1. If a fault occurred in the primary AZ, switch the secondary AZ to the primary AZ and enable the resources such as the DR servers and DR disks in the secondary AZ.
      2. After the fault in the faulty AZ has been restored, reprotect the replication consistency group to enable the restored resources in the faulty AZ to function as DR servers and DR disks.
      +
    • Expanding EVS disks in a replication consistency group: Expand EVS disks in one or multiple EVS replication pairs of the replication consistency group.
    +
    Figure 1 Operation procedure (EVS replication)
    +

    EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

    +
    +
+
+
+ + diff --git a/docs/evs/umn/evs_01_0072.html b/docs/evs/umn/evs_01_0072.html new file mode 100644 index 000000000..695e60dd9 --- /dev/null +++ b/docs/evs/umn/evs_01_0072.html @@ -0,0 +1,320 @@ + + +

Extending Partitions and File Systems for System Disks (Linux)

+

Scenarios

After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.

+

In Linux, you must allocate the additional space to an existing partition or a new partition.

+

This section uses CentOS 7.4 64bit and CentOS 6.5 64bit as the sample OSs to describe how to extend the disk partition using growpart and fdisk. The method for allocating the additional space varies with the server OS. This document is used for reference only. For detailed operations and differences, see the corresponding OS documents.

+

For how to query the Linux kernel version, see Querying the Linux Kernel Version.

+ +

Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using backups or snapshots before expansion. For details about backups, see Managing EVS Backup. For details about snapshots, see Creating a Snapshot.

+
+
+

Prerequisites

+
+

Querying the Linux Kernel Version

Run the following command to query the Linux kernel version:

+

uname -a

+
Then, perform corresponding operations depending on whether the Linux kernel version is later than 3.6.0.
  • For CentOS 7.4 64bit, information similar to the following is displayed:
    Linux ecs-test-0001 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64
    +

    The kernel version is 3.10.0, which is later than 3.6.0. For subsequent operations, see Extending an Existing MBR Partition (Kernel Version Later Than 3.6.0).

    +
  • For CentOS 6.5 64bit, information similar to the following is displayed:
    Linux ecs-test-0002 2.6.32-754.10.1.el6.x86_64 #1 SMP Tue Jan 15 17:07:28 UTC 2019 x86_64
    +

    The kernel version is 2.6.32, which is earlier than 3.6.0. In this case, the disk partition and file system extension take effect only after a server reboot. For subsequent operations, see Extending an Existing MBR Partition (Kernel Version Earlier Than 3.6.0).

    +
+
+
+

Extending an Existing MBR Partition (Kernel Version Later Than 3.6.0)

CentOS 7.4 64bit is used as the sample OS. Originally, system disk /dev/vda has 40 GB and one partition (/dev/vda1), and then 60 GB is added to the disk. The following procedure shows you how to allocate the additional 60 GB to the existing MBR partition /dev/vda1.

+
  1. (Optional) Run the following command to install the growpart tool:

    yum install cloud-utils-growpart

    +

    You can run the growpart command to check whether the growpart tool has been installed. If the command output displays the tool usage instructions, the tool has been installed and you do not need to install it separately.

    +
    +

  2. Run the following command to view the total capacity of the /dev/vda system disk:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
+
+Disk /dev/vda: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
    +
    +

    +

  3. Run the following command to view the capacity of the /dev/vda1 partition:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  2.0G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.0M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
    +
    +

    +

  4. Run the following command to extend the partition using growpart:

    growpart System disk Partition number

    +

    In this example, run the following command:

    +

    growpart /dev/vda 1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# growpart /dev/vda 1
+CHANGED: partition=1 start=2048 old: size=83884032 end=83886080 new: size=209713119,end=209715167
    +
    +

    +

  5. Run the following command to extend the file system of the partition:

    resize2fs Disk partition

    +

    In this example, run the following command:

    +

    resize2fs /dev/vda1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# resize2fs /dev/vda1
+resize2fs 1.42.9 (28-Dec-2013)
+Filesystem at /dev/vda1 is mounted on /; on-line resizing required
+old_desc_blocks = 5, new_desc_blocks = 13
+The filesystem on /dev/vda1 is now 26214139 blocks long.
    +
    +

    +

  6. Run the following command to view the new capacity of the /dev/vda1 partition:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4      106G  2.0G   99G   2% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.0M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
    +
    +

+
+

Extending an Existing MBR Partition (Kernel Version Earlier Than 3.6.0)

If the OS kernel version is earlier than 3.6.0, the extension of an existing MBR disk partition and file system takes effect only after a server reboot, and services will be interrupted.

+
+

CentOS 6.5 64bit is used as the sample OS. Originally, system disk /dev/vda has 40 GB and one partition (/dev/vda1), and then 60 GB is added to the disk. The following procedure shows you how to allocate the additional 60 GB to the existing MBR partition /dev/vda1.

+
  1. (Optional) Run the following command to install the growpart tool:

    yum install cloud-utils-growpart

    +

    You can run the growpart command to check whether the growpart tool has been installed. If the command output displays the tool usage instructions, the tool has been installed and you do not need to install it separately.

    +
    +

  2. Run the following command to install the dracut-modules-growroot tool:

    yum install cloud-utils-growpart

    +
    Information similar to the following is displayed:
    [root@ecs-test-0002 ~]# yum install cloud-utils-growpart
+Loaded plugins: fastestmirror, security
+Setting up Install Process
+Determining fastest mirrors
+...
+Package cloud-utils-growpart-0.27-10.el6.x86_64 already installed and latest version
+Nothing to do
    +
    +

  3. Run the following command to regenerate the initramfs file:

    dracut -f

    +

  4. Run the following command to view the total capacity of the /dev/vda system disk:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-test-0002 ~]# fdisk -l
+
+Disk /dev/vda: 107.4 GB, 107374182400 bytes
+255 heads, 63 sectors/track, 13054 cylinders
+Units = cylinders of 16065 * 512 = 8225280 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk identifier: 0x0004e0be
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *           1        5222    41942016   83  Linux
    +
    +

  5. Run the following command to view the capacity of the /dev/vda1 partition:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0002 ~]# df -TH
+Filesystem     Type   Size  Used Avail Use% Mounted on
+/dev/vda1      ext4    43G  1.7G   39G   5% /
+tmpfs          tmpfs  2.1G     0  2.1G   0% /dev/shm
    +
    +

  6. Run the following command to extend the partition using growpart:

    growpart System disk Partition number

    +

    In this example, run the following command:

    +

    growpart /dev/vda 1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0002 ~]# growpart /dev/vda 1
+CHANGED: partition=1 start=2048 old: size=83884032 end=83886080 new: size=209710462,end=209712510
    +
    +

  7. Run the following command to restart the server:

    reboot

    +

    After the server is restarted, reconnect to the server and perform the following steps.

    +

  8. Run the following command to extend the file system of the partition:

    resize2fs Disk partition

    +

    In this example, run the following command:

    +

    resize2fs /dev/vda1

    +
    Information similar to the following is displayed:
    [root@ecs-test-0002 ~]# resize2fs /dev/vda1
+resize2fs 1.41.12 (17-May-2010)
+The filesystem is already 26213807 blocks long.  Nothing to do!
    +
    +

  9. Run the following command to view the new capacity of the /dev/vda1 partition:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0002 ~]# df -TH
+Filesystem     Type   Size  Used Avail Use% Mounted on
+/dev/vda1      ext4   106G  1.7G   99G   2% /
+tmpfs          tmpfs  2.1G     0  2.1G   0% /dev/shm
    +
    +

+
+

Creating a New MBR Partition

Originally, system disk /dev/vda has 40 GB and one partition (/dev/vda1), and then 40 GB is added to the disk. The following procedure shows you how to create a new MBR partition /dev/vda2 with this 40 GB.

+
  1. Run the following command to view the disk partition information:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-2220 ~]# fdisk -l
+
+Disk /dev/vda: 85.9 GB, 85899345920 bytes, 167772160 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x0008d18f
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
    +
    +

    In the command output, the capacity of the dev/vda system disk is 80 GB, in which the in-use dev/vda1 partition takes 40 GB and the additional 40 GB has not been allocated.

    +

  2. Run the following command to enter fdisk:

    fdisk /dev/vda

    +
    Information similar to the following is displayed:
    [root@ecs-2220 ~]# fdisk /dev/vda
+Welcome to fdisk (util-linux 2.23.2).
+
+Changes will remain in memory only, until you decide to write them.
+Be careful before using the write command.
+
+
+Command (m for help):
    +
    +

  3. Enter n and press Enter to create a new partition.

    Information similar to the following is displayed:
    Command (m for help): n
+Partition type:
+   p   primary (1 primary, 0 extended, 3 free)
+   e   extended
    +
    +
    There are two types of disk partitions:
    • Choosing p creates a primary partition.
    • Choosing e creates an extended partition.
    +

    If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.

    +

    Disk partitions created using GPT are not categorized.

    +
    +
    +

  4. In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.

    Information similar to the following is displayed:
    Select (default p): p
+Partition number (2-4, default 2):
    +
    +

  5. Partition number 2 is used in this example. Therefore, enter 2 and press Enter.

    Information similar to the following is displayed:
    Partition number (2-4, default 2): 2
+First sector (83886080-167772159, default 83886080):
    +
    +

  6. Enter the new partition's start sector and press Enter. In this example, the default start sector is used.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    First sector (83886080-167772159, default 83886080):
+Using default value 83886080
+Last sector, +sectors or +size{K,M,G} (83886080-167772159,default 167772159):
    +
    +

  7. Enter the new partition's end sector and press Enter. In this example, the default end sector is used.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    Last sector, +sectors or +size{K,M,G} (83886080-167772159,
+default 167772159):
+Using default value 167772159
+Partition 2 of type Linux and of size 40 GiB is set
+
+Command (m for help):
    +
    +

  8. Enter p and press Enter to view the new partition.

    Information similar to the following is displayed:
    Command (m for help): p
+
+Disk /dev/vda: 85.9 GB, 85899345920 bytes, 167772160 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x0008d18f
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+/dev/vda2        83886080   167772159    41943040   83  Linux
+Command (m for help):
    +
    +

  9. Enter w and press Enter to write the changes to the partition table.

    Information similar to the following is displayed:
    Command (m for help): w
+The partition table has been altered!
+
+Calling ioctl() to re-read partition table.
+
+WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
+The kernel still uses the old table. The new table will be used at
+the next reboot or after you run partprobe(8) or kpartx(8)
+Syncing disks.
    +
    +

    The partition is created.

    +

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

    +
    +

  10. Run the following command to synchronize the new partition table to the OS:

    partprobe

    +

  11. Run the following command to set the file system format for the new partition:

    mkfs -t File system Disk partition

    +
    • Sample command of the ext* file system:

      (The ext4 file system is used in this example.)

      +

      mkfs -t ext4 /dev/vda2

      +
      Information similar to the following is displayed:
      [root@ecs-2220 ~]# mkfs -t ext4 /dev/vda2
+mke2fs 1.42.9 (28-Dec-2013)
+Filesystem label=
+OS type: Linux
+Block size=4096 (log=2)
+Fragment size=4096 (log=2)
+Stride=0 blocks, Stripe width=0 blocks
+2621440 inodes, 10485760 blocks
+524288 blocks (5.00%) reserved for the super user
+First data block=0
+Maximum filesystem blocks=2157969408
+320 block groups
+32768 blocks per group, 32768 fragments per group
+8192 inodes per group
+Superblock backups stored on blocks:
+        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
+        4096000, 7962624
+
+Allocating group tables: done
+Writing inode tables: done
+Creating journal (32768 blocks): done
+Writing superblocks and filesystem accounting information: done
      +
      +
    +
    • Sample command of the xfs file system:

      mkfs -t xfs /dev/vda2

      +

      Information similar to the following is displayed:

      +
      [root@ecs-2220 ~]# mkfs -t xfs /dev/vda2 
+meta-data=/dev/vda2              isize=512     agcount=4, agsize=2621440 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, sparse=0
+data     =                       bsize=4096    blocks=10485760, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal log           bsize=4096    blocks=5120, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
      +
    +

    The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

    +

  12. (Optional) Run the following command to create a mount point:

    Perform this step if you want to mount the partition on a new mount point.

    +

    mkdir Mount point

    +

    In this example, run the following command to create the /opt mount point:

    +

    mkdir /opt

    +

  13. Run the following command to mount the new partition:

    mount Disk partition Mount point

    +

    In this example, run the following command to mount the new partition /dev/vda2 on /opt:

    +

    mount /dev/vda2 /opt

    +

    If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

    +
    +

  14. Run the following command to view the mount result:

    df -TH

    +

    Information similar to the following is displayed:

    +
    [root@ecs-2220 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  2.0G   39G   5% /
+devtmpfs       devtmpfs  509M     0  509M   0% /dev
+tmpfs          tmpfs     520M     0  520M   0% /dev/shm
+tmpfs          tmpfs     520M  7.2M  513M   2% /run
+tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
+tmpfs          tmpfs     104M     0  104M   0% /run/user/0
+/dev/vda2      ext4       43G   51M   40G   1% /opt
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +

+
+

Setting Automatic Mounting at System Start

Modify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.

+

The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.

+

UUID is the unique character string for disk partitions in a Linux system.

+
+
  1. Run the following command to query the partition UUID:

    blkid Disk partition

    +

    In this example, run the following command to query the UUID of the /dev/vdb1 partition:

    +

    blkid /dev/vdb1

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
    +

    The UUID of the /dev/vdb1 partition is displayed.

    +

  2. Run the following command to open the fstab file using the vi editor:

    vi /etc/fstab

    +

  3. Press i to enter the editing mode.
  4. Move the cursor to the end of the file and press Enter. Then, add the following information:

    UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
    +

  5. Press Esc, enter :wq, and press Enter.

    The system saves the configurations and exits the vi editor.

    +

  6. Perform the following operations to verify the automatic mounting function:

    1. Run the following command to unmount the partition:

      umount Disk partition

      +

      In this example, run the following command:

      +

      umount /dev/vdb1

      +
    2. Run the following command to reload all the content in the /etc/fstab file:

      mount -a

      +
    3. Run the following command to query the file system mounting information:

      mount | grep Mount point

      +

      In this example, run the following command:

      +

      mount | grep /mnt/sdc

      +

      If information similar to the following is displayed, the automatic mounting function takes effect:

      +
      root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
      +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0077.html b/docs/evs/umn/evs_01_0077.html new file mode 100644 index 000000000..8fbb59a58 --- /dev/null +++ b/docs/evs/umn/evs_01_0077.html @@ -0,0 +1,24 @@ + + +

Capacity Expansion

+

+
+ + diff --git a/docs/evs/umn/evs_01_0078.html b/docs/evs/umn/evs_01_0078.html new file mode 100644 index 000000000..bcbdd9379 --- /dev/null +++ b/docs/evs/umn/evs_01_0078.html @@ -0,0 +1,22 @@ + + +

Attachment

+

+
+ + diff --git a/docs/evs/umn/evs_01_0079.html b/docs/evs/umn/evs_01_0079.html new file mode 100644 index 000000000..f076538ce --- /dev/null +++ b/docs/evs/umn/evs_01_0079.html @@ -0,0 +1,18 @@ + + +

Detachment

+

+
+ + diff --git a/docs/evs/umn/evs_01_0081.html b/docs/evs/umn/evs_01_0081.html new file mode 100644 index 000000000..6e3289e29 --- /dev/null +++ b/docs/evs/umn/evs_01_0081.html @@ -0,0 +1,24 @@ + + +

General

+

+
+ + diff --git a/docs/evs/umn/evs_01_0082.html b/docs/evs/umn/evs_01_0082.html new file mode 100644 index 000000000..7f4a99c79 --- /dev/null +++ b/docs/evs/umn/evs_01_0082.html @@ -0,0 +1,22 @@ + + +

Capacity

+

+
+ + diff --git a/docs/evs/umn/evs_01_0084.html b/docs/evs/umn/evs_01_0084.html new file mode 100644 index 000000000..c9ff6f78b --- /dev/null +++ b/docs/evs/umn/evs_01_0084.html @@ -0,0 +1,18 @@ + + +

Sharing

+

+
+ + diff --git a/docs/evs/umn/evs_01_0086.html b/docs/evs/umn/evs_01_0086.html new file mode 100644 index 000000000..854995f79 --- /dev/null +++ b/docs/evs/umn/evs_01_0086.html @@ -0,0 +1,181 @@ + + +

Permissions Management

+

If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.

+

With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some management personnel in your enterprise need to view EVS resources but should not be allowed to delete the resources or perform any high-risk operations. In this scenario, you can create IAM users for the management personnel and grant them only the permissions required for viewing EVS resources.

+

If your account does not need individual IAM users for permissions management, you may skip this chapter.

+

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see section "Service Overview" in the Identity and Access Management User Guide.

+

EVS Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

+

EVS is a project-level service deployed and accessed in specific physical regions. To assign EVS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing EVS, the users need to switch to a region where they have been authorized to use this service. When accessing EVS, users need to switch to a region where they have been authorized to use EVS.

+
You can grant users permissions by using roles and policies.
  • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
  • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by EVS, see section "Permissions Policies and Supported Actions" in the Elastic Volume Service API Reference.
+
+
Table 1 lists all the system-defined roles and policies supported by EVS. +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 System-defined roles and policies supported by EVS

Role/Policy Name

+

Description

+

Type

+

Dependency

+

EVS FullAccess

+

Full permissions for EVS. Users granted these permissions can create, attach, detach, query, and delete EVS resources, and expand capacity of EVS disks.

+

System-defined policy

+

None

+

EVS ReadOnlyAccess

+

Read-only permissions for EVS. Users granted these permissions can view EVS resource data only.

+

System-defined policy

+

None

+

Server Administrator

+

Full permissions for EVS

+

System role

+

None

+
+
+

The EVS Admin and EVS FullAccess roles have the same permissions, and EVS Admin will be deprecated later. The EVS Viewer and EVS ReadOnlyAccess roles have the same permissions, and EVS Viewer will be deprecated later.

+
+
+
Table 2 lists the common operations supported by each system-defined policy or role of EVS. Select the policies or roles as required. +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Common operations supported by each system-defined policy or role of EVS

Operation

+

EVS FullAccess

+

EVS ReadOnlyAccess

+

Creating disks

+

√

+

x

+

Viewing disk list

+

√

+

√

+

Viewing disk details

+

√

+

√

+

Attaching disks

+

√

+

x

+

Detaching disks

+

√

+

x

+

Deleting disks

+

√

+

x

+

Expanding disk capacities

+

√

+

x

+

Creating snapshots

+

√

+

x

+

Deleting snapshots

+

√

+

x

+

Rolling back snapshot data

+

√

+

x

+

Creating disks from snapshots

+

√

+

x

+

Adding tags for disks

+

√

+

x

+

Modifying tags

+

√

+

x

+

Deleting tags

+

√

+

x

+

Searching for disks by tag

+

√

+

√

+
+
+
+
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0087.html b/docs/evs/umn/evs_01_0087.html new file mode 100644 index 000000000..76247dd93 --- /dev/null +++ b/docs/evs/umn/evs_01_0087.html @@ -0,0 +1,14 @@ + + +

Permissions Management

+

+
+ + diff --git a/docs/evs/umn/evs_01_0089.html b/docs/evs/umn/evs_01_0089.html new file mode 100644 index 000000000..304e74012 --- /dev/null +++ b/docs/evs/umn/evs_01_0089.html @@ -0,0 +1,23 @@ + + +

Creating a User and Granting EVS Permissions

+

This chapter describes how to use IAM to implement fine-grained permissions control for your EVS resources. With IAM, you can:

+
  • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing EVS resources.
  • Grant only the permissions required for users to perform a specific task.
  • Entrust an account or cloud service to perform efficient O&M on your EVS resources.
+

If your account does not require individual IAM users, skip this chapter.

+

This section describes the procedure for granting permissions (see Figure 1).

+

Prerequisites

Learn about the permissions (see section "Permissions Management" in the Elastic Volume Service User Guide) supported by EVS and choose policies or roles according to your requirements.

+
+

Process Flow

Figure 1 Process for granting EVS permissions
+
  1. Create a user group and assign permissions to it.

    Create a user group on the IAM console, and attach the EVS ReadOnlyAccess policy to the group.

    +
  2. Create a user and add it to a user group.

    Create a user on the IAM console and add the user to the group created in 1.

    +
  3. Log in and verify permissions.

    Log in to the EVS console by using the user created in 2, and verify that the user only has read permissions for EVS.

    +
    • In Service List, choose Elastic Volume Service. On the EVS console, click Create Disk in the upper right corner. If a message appears indicating that you have insufficient permissions to perform the operation, the EVS ReadOnlyAccess policy has already taken effect.
    • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the EVS ReadOnlyAccess policy has already taken effect.
    +
+
+
+
+
+
Parent topic: Permissions Management
+
+
+ diff --git a/docs/evs/umn/evs_01_0090.html b/docs/evs/umn/evs_01_0090.html new file mode 100644 index 000000000..84fd8c9b4 --- /dev/null +++ b/docs/evs/umn/evs_01_0090.html @@ -0,0 +1,51 @@ + + +

EVS Custom Policies

+

Custom policies can be created to supplement the system-defined policies of EVS. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in the Elastic Volume Service API Reference.

+

You can create custom policies in either of the following ways:

+
  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
    Figure 1 Create Custom Policy
    +
  • JSON: Edit JSON policies from scratch or based on an existing policy.

    For operation details, see section "Creating a Custom Policy" in the Identity and Access Management User Guide. The following section contains examples of common EVS custom policies.

    +
+

Example Custom Policies

  • Example 1: Allowing users to create disks.
    {
+        "Version": "1.1",
+        "Statement": [
+                {
+                        "Action": [
+                                "evs:volumes:list",
+                                "evs:volumes:get",
+                                "evs:quotas:get",
+                                "evs:volumeTags:list",
+                                "evs:types:get",
+                                "evs:volumes:create",
+                                "ecs:cloudServerFlavors:get",
+                                "ecs:cloudServers:list",
+                                "bss:balance:view",
+                                "bss:order:pay",
+                                "bss:order:update"
+                        ],
+                        "Effect": "Allow"
+                }
+        ]
+}
    +
  • Example 2: Denying disk deletion

    A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    +

    The following method can be used if you need to assign permissions of the EVS FullAccess policy to a user but you want to prevent the user from deleting EVS disks. Create a custom policy for denying disk deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on disks except deleting disks. The following is an example of a deny policy:

    +
    {
+        "Version": "1.1",
+        "Statement": [
+                {
+                        "Effect": "Deny",
+                        "Action": [
+                                "evs:volumes:delete"
+                        ]
+                }
+        ]
+}
    +
+
+
+
+
+
Parent topic: Permissions Management
+
+
+ diff --git a/docs/evs/umn/evs_01_0094.html b/docs/evs/umn/evs_01_0094.html new file mode 100644 index 000000000..0e3e1039f --- /dev/null +++ b/docs/evs/umn/evs_01_0094.html @@ -0,0 +1,22 @@ + + +

Extending Disk Partitions and File Systems (Linux)

+

+
+ + diff --git a/docs/evs/umn/evs_01_0097.html b/docs/evs/umn/evs_01_0097.html new file mode 100644 index 000000000..e6e321c61 --- /dev/null +++ b/docs/evs/umn/evs_01_0097.html @@ -0,0 +1,22 @@ + + +

Region and AZ

+

Concept

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

+
  • A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
  • An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
+

Figure 1 shows the relationship between regions and AZs.

+
Figure 1 Regions and AZs
+
+

Selecting a Region

Select a region closest to your target users for lower network latency and quick access.

+
+

Selecting an AZ

When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.

+
  • For high DR capability, deploy resources in different AZs within the same region.
  • For lower network latency, deploy resources in the same AZ.
+
+

Regions and Endpoints

Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.

+
+
+
+
+
Parent topic: Basic Concepts
+
+
+ diff --git a/docs/evs/umn/evs_01_0098.html b/docs/evs/umn/evs_01_0098.html new file mode 100644 index 000000000..fa5e8d8d6 --- /dev/null +++ b/docs/evs/umn/evs_01_0098.html @@ -0,0 +1,27 @@ + + +

Snapshot Overview

+

What Is EVS Snapshot?

EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific time point. As a major disaster recovery (DR) approach, you can use a snapshot to completely restore the data to the time point when the snapshot was created.

+

EVS snapshots are sometimes referred to as snapshots in this document.

+

You can create snapshots to rapidly save the disk data at specified time points. In addition, you can use snapshots to create new disks so that the created disks will contain the snapshot data in the beginning.

+
+

Application Scenarios

The snapshot function helps address your following needs:

+
  • Routine data backup

    You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data loss or data inconsistency occurred due to misoperations, viruses, or attacks.

    +
  • Rapid data restoration

    You can create a snapshot or multiple snapshots before an application software upgrade or a service data migration. If an exception occurs during the upgrade or migration, service data can be rapidly restored to the time point when the snapshot was created.

    +

    For example, a fault occurred on system disk A of server A, and therefore server A cannot be started. Because system disk A is already faulty, the data on system disk A cannot be restored by rolling back snapshots. However, you can create disk B using an existing snapshot of system disk A and attach disk B to a properly running server, for example server B. In this case, server B can read the data of system disk A from disk B.

    +

    Currently, when rolling back data from snapshots, the snapshot data can be rolled back only to its source EVS disk, and a rollback to another EVS disk is not possible.

    +
    +
  • Multi-service quick deployment

    You can use a snapshot to create multiple disks containing the same initial data, and these disks can be used as data resources for various services, for example data mining, report query, and development and testing. This method protects the initial data and creates disks rapidly, meeting the diversified service data requirements.

    +
+
+

Operation Overview

You can create snapshots according to Creating a Snapshot to rapidly save the disk data at specified points in time.

+

If data lost occurs, you may choose to roll back the disk data to the snapshot creation time based on Rolling Back Data from a Snapshot. In addition, you may create a new disk from the snapshot so that the disk will contain the snapshot data in the beginning. For details, see Creating an EVS Disk from a Snapshot.

+

When a snapshot is no longer needed, delete it according to Deleting a Snapshot to release the virtual resources.

+
+
+
+
+
Parent topic: Managing Snapshots
+
+
+ diff --git a/docs/evs/umn/evs_01_0099.html b/docs/evs/umn/evs_01_0099.html new file mode 100644 index 000000000..0b1372d27 --- /dev/null +++ b/docs/evs/umn/evs_01_0099.html @@ -0,0 +1,41 @@ + + +

Tag Overview

+

Tags identify EVS resources for purposes of easy categorization and quick search.

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Tag overview

Operation

+

Scenario

+

Adding a Tag

+

Add tags for existing disks or during disk creations.

+

Modifying a Tag

+

Change tag values for existing disks. Tag keys of existing disks cannot be changed.

+

Deleting a Tag

+

Delete tags that are no longer needed for existing disks.

+

Searching Disks by Tags

+

After tags are added, search for disks by tags.

+
+
+
+
+
+
Parent topic: Managing a Tag
+
+
+ diff --git a/docs/evs/umn/evs_01_0101.html b/docs/evs/umn/evs_01_0101.html new file mode 100644 index 000000000..cb701824d --- /dev/null +++ b/docs/evs/umn/evs_01_0101.html @@ -0,0 +1,19 @@ + + + +

Basic Concepts

+ +

+
+ +
+ + +
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0106.html b/docs/evs/umn/evs_01_0106.html new file mode 100644 index 000000000..dac2a246c --- /dev/null +++ b/docs/evs/umn/evs_01_0106.html @@ -0,0 +1,13 @@ + + +

EVS and Other Services

+
Figure 1 shows the relationships between EVS and other services.
Figure 1 Relationships between EVS and other services
+
+
  • ECS: EVS disks can be attached to ECSs and used as scalable block storage devices.
  • BMS: SCSI EVS disks can be attached to BMSs and used as scalable block storage devices.
  • CBR: The CBR service can be used to back up EVS disk data to ensure the reliability and security of the server data.
  • KMS: EVS disk encryption depends on the KMS service. You can use the keys provided by KMS to encrypt EVS disks (including both system and data disks), thus improving EVS disk data security.
  • Cloud Eye: After enabling EVS, you can view the status of monitored performance metrics through Cloud Eye without installing any additional plug-in. The monitored metrics include Disk Read Rate, Disk Write Rate, Disk Read Requests, and Disk Write Requests.
  • Cloud Trace Service (CTS): CTS records operations of EVS resources, facilitating user query, audit, and backtracking.
  • Tag Management Service (TMS): Tags are used to identify the EVS resources for purposes of easy categorization and quick search.
+
+
+
+
Parent topic: Overview
+
+
+ diff --git a/docs/evs/umn/evs_01_0107.html b/docs/evs/umn/evs_01_0107.html new file mode 100644 index 000000000..5b2302059 --- /dev/null +++ b/docs/evs/umn/evs_01_0107.html @@ -0,0 +1,17 @@ + + +

Attach an EVS Disk

+
+ + diff --git a/docs/evs/umn/evs_01_0108.html b/docs/evs/umn/evs_01_0108.html new file mode 100644 index 000000000..8e74c76ad --- /dev/null +++ b/docs/evs/umn/evs_01_0108.html @@ -0,0 +1,41 @@ + + +

Initializing a Windows Data Disk (Windows Server 2008)

+

Scenarios

This section uses Windows Server 2008 R2 Enterprise 64bit to describe how to initialize a data disk attached to a server running Windows.

+

The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. For details about disk partition styles, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+

The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.

+
+

Prerequisites

  • A data disk has been attached to a server and has not been initialized.
  • You have logged in to the server.
    • For how to log in to an ECS, see the Elastic Cloud Server User Guide.
    • For how to log in to a BMS, see the Bare Metal Server User Guide.
    +
+
+

Procedure

  1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

    The Server Manager window is displayed.

    +

  2. In the navigation tree, choose Storage > Disk Management.

    The Disk Management window is displayed.
    • If Figure 1 is displayed, the new disk is offline. Go to 3.
    • If Figure 4 is displayed, the Initialize Disk window is prompted. Go to 5.
    +
    +
    Figure 1 Disk Management
    +

  3. Disks are displayed in the right pane. In the Disk 1 area, right-click Offline and choose Online from the shortcut menu to online the disk.

    Figure 2 Online the disk
    +

    If the disk is offline, you need to online the disk before initializing it.

    +
    +

  4. After making the disk online, the disk status changes from Offline to Not Initialized. Right-click the disk status and choose Initialize Disk from the shortcut menu, as shown in Figure 3.

    Figure 3 Initialize Disk
    +

  5. In the Initialize Disk dialog box, select the target disk, click MBR (Master Boot Record) or GPT (GUID Partition Table), and click OK, as shown in Figure 4.

    Figure 4 Unallocated space
    +

    The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.

    +

    If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.

    +
    +
    +

  6. Right-click at the unallocated space and choose New Simple Volume from the shortcut menu, as shown in Figure 5.

    Figure 5 New Simple Volume
    +

  7. On the displayed New Simple Volume Wizard window, click Next.

    Figure 6 New Simple Volume Wizard
    +

  8. Specify the volume size and click Next. The default value is the maximum size.

    Figure 7 Specify Volume Size
    +

  9. Assign the driver letter and click Next.

    Figure 8 Assign Driver Letter or Path
    +

  10. Select Format this volume with the following settings, set parameters based on the actual requirements, and select Perform a quick format. Then, click Next.

    Figure 9 Format Partition
    +
    Figure 10 Completing the partition creation
    +

    The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.

    +
    +

  11. Click Finish. Wait for the initialization to complete. When the volume status changes to Healthy, the initialization has finished successfully, as shown in Figure 11.

    Figure 11 Disk initialization succeeded
    +

+
+
+
+
+
Parent topic: Initialize an EVS Data Disk
+
+
+ diff --git a/docs/evs/umn/evs_01_0109.html b/docs/evs/umn/evs_01_0109.html new file mode 100644 index 000000000..d8abfe0d4 --- /dev/null +++ b/docs/evs/umn/evs_01_0109.html @@ -0,0 +1,707 @@ + + +

Extending Partitions and File Systems for Data Disks (Linux)

+

Scenarios

After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.

+

In Linux, you must allocate the additional space to an existing partition or a new partition.

+

This section uses CentOS 7.4 64bit as the sample OS to describe how to extend an MBR or GPT partition. The method for allocating the additional space varies depending on the server OS. This document is used for reference only. For detailed operations and differences, see the corresponding OS documents.

+ +

Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using backups or snapshots before expansion. For details about backups, see Managing EVS Backup. For details about snapshots, see Creating a Snapshot.

+
+
+

Prerequisites

+
+

Creating a New MBR Partition

Originally, data disk /dev/vdb has 100 GB and one partition (/dev/vdb1), and then 50 GB is added to the disk. The following procedure shows you how to create a new MBR partition /dev/vdb2 with this 50 GB.

+
  1. Run the following command to view the disk partition information:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
+
+Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+
+Disk /dev/vdb: 161.1 GB, 161061273600 bytes, 314572800 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x38717fc1
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vdb1            2048   209715199   104856576   83  Linux
    +
    +

  2. Run the following command to enter fdisk:

    fdisk Disk

    +

    In this example, run the following command:

    +

    fdisk /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk /dev/vdb
+Welcome to fdisk (util-linux 2.23.2).
+
+Changes will remain in memory only, until you decide to write them.
+Be careful before using the write command.
+
+
+Command (m for help):
    +
    +

  3. Enter n and press Enter to create a new partition.

    Information similar to the following is displayed:
    Command (m for help): n
+Partition type:
+   p   primary (1 primary, 0 extended, 3 free)
+   e   extended
+Select (default p):
    +
    +
    There are two types of disk partitions:
    • Choosing p creates a primary partition.
    • Choosing e creates an extended partition.
    +

    If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.

    +

    Disk partitions created using GPT are not categorized.

    +
    +
    +

  4. In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.

    Information similar to the following is displayed:
    Select (default p): p
+Partition number (2-4, default 2):
    +
    +

    Partition number indicates the serial number of the primary partition. Because partition number 1 has been used, the value ranges from 2 to 4.

    +

  5. Enter the serial number of the primary partition and press Enter. Partition number 2 is used in this example. Therefore, enter 2 and press Enter.

    Information similar to the following is displayed:
    Partition number (2-4, default 2): 2
+First sector (209715200-314572799, default 209715200):
    +
    +

    First sector indicates the start sector. The value ranges from 209715200 to 314572799, and the default value is 209715200.

    +

  6. Enter the new partition's start sector and press Enter. In this example, the default start sector is used.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    First sector (209715200-314572799, default 209715200):
+Using default value 209715200
+Last sector, +sectors or +size{K,M,G} (209715200-314572799, default 314572799):
    +
    +

    Last sector indicates the end sector. The value ranges from 209715200 to 314572799, and the default value is 314572799.

    +

  7. Enter the new partition's end sector and press Enter. In this example, the default end sector is used.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +
    Information similar to the following is displayed:
    Last sector, +sectors or +size{K,M,G} (209715200-314572799, default 314572799):
+Using default value 314572799
+Partition 2 of type Linux and of size 50 GiB is set
+
+Command (m for help):
    +
    +

  8. Enter p and press Enter to view the new partition.

    Information similar to the following is displayed:
    Command (m for help): p
+
+Disk /dev/vdb: 161.1 GB, 161061273600 bytes, 314572800 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x38717fc1
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vdb1            2048   209715199   104856576   83  Linux
+/dev/vdb2       209715200   314572799    52428800   83  Linux
+
+Command (m for help):
    +
    +

  9. Enter w and press Enter to write the changes to the partition table.

    Information similar to the following is displayed:
    Command (m for help): w
+The partition table has been altered!
+
+Calling ioctl() to re-read partition table.
+
+WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
+The kernel still uses the old table. The new table will be used at
+the next reboot or after you run partprobe(8) or kpartx(8)
+Syncing disks.
    +
    +

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

    +
    +

  10. Run the following command to synchronize the new partition table to the OS:

    partprobe

    +

  11. Run the following command to set the file system format for the new partition:

    mkfs -t File system Disk partition
    • Sample command of the ext* file system:

      mkfs -t ext4 /dev/vdb2

      +
      Information similar to the following is displayed:
      [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb2
+mke2fs 1.42.9 (28-Dec-2013)
+Filesystem label=
+OS type: Linux
+Block size=4096 (log=2)
+Fragment size=4096 (log=2)
+Stride=0 blocks, Stripe width=0 blocks
+3276800 inodes, 13107200 blocks
+655360 blocks (5.00%) reserved for the super user
+First data block=0
+Maximum filesystem blocks=2162163712
+400 block groups
+32768 blocks per group, 32768 fragments per group
+8192 inodes per group
+Superblock backups stored on blocks:
+        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
+        4096000, 7962624, 11239424
+
+Allocating group tables: done
+Writing inode tables: done
+Creating journal (32768 blocks): done
+Writing superblocks and filesystem accounting information: done
      +
      +
    +
    +
    • Sample command of the xfs file system:

      mkfs -t xfs /dev/vdb2

      +

      Information similar to the following is displayed:

      +
      [root@ecs-test-0001 ~]# mkfs -t xfs /dev/vdb2 
+meta-data=/dev/vdb2              isize=512     agcount=4, agsize=3276800 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, sparse=0
+data     =                       bsize=4096    blocks=13107200, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal log           bsize=4096    blocks=6400, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
      +
    +

    The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

    +

  12. (Optional) Run the following command to create a mount point:

    Perform this step if you want to mount the partition on a new mount point.

    +

    mkdir Mount point

    +

    In this example, run the following command to create the /mnt/test mount point:

    +

    mkdir /mnt/test

    +

  13. Run the following command to mount the new partition:

    mount Disk partition Mount point

    +

    In this example, run the following command to mount the new partition /dev/vdb2 on /mnt/test:

    +

    mount /dev/vdb2 /mnt/test

    +

    If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

    +
    +

  14. Run the following command to view the mount result:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.1M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
+/dev/vdb2      ext4       53G   55M   50G   1% /mnt/test
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +
    +

+
+

Extending an Existing MBR Partition

If the additional space is allocated to an existing partition, data on the disk will not be cleared but you must use umount to unmount the existing partition. In this case, services will be affected.

+
+

Originally, data disk /dev/vdb has 150 GB and two partitions (/dev/vdb1 and /dev/vdb2), and then 80 GB is added to the disk. The following procedure shows you how to add this 80 GB to the existing MBR partition /dev/vdb2.

+

During an expansion, the additional space is added to the end of the disk. Therefore, if the disk has multiple partitions, the additional space can only be allocated to the partition at the disk end.

+
+
  1. Run the following command to view the disk partition information:

    fdisk -l

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
+
+Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x000bcb4e
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vda1   *        2048    83886079    41942016   83  Linux
+
+Disk /dev/vdb: 247.0 GB, 246960619520 bytes, 482344960 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x38717fc1
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vdb1            2048   209715199   104856576   83  Linux
+/dev/vdb2       209715200   314572799    52428800   83  Linux
    +
    +

    In the command output, take note of the partition's start and end sectors. In this example, /dev/vdb2's start sector is 209715200, and its end sector is 314572799.

    +
    View the /dev/vdb capacity and check whether the additional space is included.
    • If the additional space is not included, refresh the capacity according to Extending Partitions and File Systems for SCSI Disks (Linux).
    • If the additional space is included, take note of the start and end sectors of the target partition and then go to 2. These values will be used in the subsequent operations.
    +
    +

  2. Run the following command to unmount the partition:

    umount Disk partition

    +

    In this example, run the following command:

    +

    umount /dev/vdb2

    +

  3. Run the following command to enter fdisk:

    fdisk Disk

    +

    In this example, run the following command:

    +

    fdisk /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk /dev/vdb
+Welcome to fdisk (util-linux 2.23.2).
+
+Changes will remain in memory only, until you decide to write them.
+Be careful before using the write command.
+
+
+Command (m for help):
    +
    +

  4. Run the following command to delete the partition to be extended:

    1. Enter d and press Enter to delete the partition.
      Information similar to the following is displayed:
      Command (m for help): d
+Partition number (1,2, default 2):
      +
      +
    2. Enter the partition number and press Enter to delete the partition. In this example, enter 2.
      Information similar to the following is displayed:
      Partition number (1,2, default 2): 2
+Partition 2 is deleted
+
+Command (m for help):
      +
      +

      After deleting the partition, recreate the partition according to the following steps, and data on this disk will not be lost.

      +
      +
    +

  5. Enter n and press Enter to create a new partition.

    Information similar to the following is displayed:
    Command (m for help): n
+Partition type:
+   p   primary (1 primary, 0 extended, 3 free)
+   e   extended
+Select (default p):
    +
    +
    There are two types of disk partitions:
    • Choosing p creates a primary partition.
    • Choosing e creates an extended partition.
    +

    If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.

    +

    Disk partitions created using GPT are not categorized.

    +
    +
    +

  6. Ensure that the entered partition type is the same as the partition had before. In this example, a primary partition is used. Therefore, enter p and press Enter to create a primary partition.

    Information similar to the following is displayed:
    Select (default p): p
+Partition number (2-4, default 2):
    +
    +

    Partition number indicates the serial number of the primary partition.

    +

  7. Ensure that entered partition number is the same as the partition had before. In this example, partition number 2 is used. Therefore, enter 2 and press Enter.

    Information similar to the following is displayed:
    Partition number (2-4, default 2): 2
+First sector (209715200-482344959, default 209715200):
    +
    +

    In the command output, First sector specifies the start sector.

    +
    Data will be lost if the following operations are performed:
    • Select a start sector other than the partition had before.
    • Select an end sector smaller than the partition had before.
    +
    +
    +

  8. Ensure that the entered start sector is the same as the partition had before. In this example, start sector 209715200 is recorded in 1. Therefore, enter 209715200 and press Enter.

    Information similar to the following is displayed:
    First sector (209715200-482344959, default 209715200):
+Using default value 209715200
+Last sector, +sectors or +size{K,M,G} (209715200-482344959, default 482344959):
    +
    +

    In the command output, Last sector specifies the end sector.

    +

  9. Ensure that the entered end sector is larger than or equal to the end sector recorded in 1. In this example, the recorded end sector is 314572799, and the default end sector is used. Therefore, enter 482344959 and press Enter.

    Information similar to the following is displayed:
    Using default value 209715200
+Last sector, +sectors or +size{K,M,G} (209715200-482344959, default 482344959):
+Using default value 482344959
+Partition 2 of type Linux and of size 130 GiB is set
+
+Command (m for help):
    +
    +

    The partition is created.

    +

  10. Enter p and press Enter to view the partition details.

    Information similar to the following is displayed:
    Command (m for help): p
+
+Disk /dev/vdb: 247.0 GB, 246960619520 bytes, 482344960 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disk label type: dos
+Disk identifier: 0x38717fc1
+
+   Device Boot      Start         End      Blocks   Id  System
+/dev/vdb1            2048   209715199   104856576   83  Linux
+/dev/vdb2       209715200   482344959   136314880   83  Linux
+
+Command (m for help):
    +
    +

  11. Enter w and press Enter to write the changes to the partition table.

    Information similar to the following is displayed:
    Command (m for help): w
+The partition table has been altered!
+
+Calling ioctl() to re-read partition table.
+
+WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
+The kernel still uses the old table. The new table will be used at
+the next reboot or after you run partprobe(8) or kpartx(8)
+Syncing disks.
    +
    +

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

    +
    +

  12. Run the following command to synchronize the new partition table to the OS:

    partprobe

    +

  13. Perform the following operations based on the file system of the disk:

    • For the ext* file system
      1. Run the following command to check the correctness of the file system on the partition:

        e2fsck -f Disk partition

        +

        In this example, run the following command:

        +

        e2fsck -f /dev/vdb2

        +
        Information similar to the following is displayed:
        [root@ecs-test-0001 ~]# e2fsck -f /dev/vdb2
+e2fsck 1.42.9 (28-Dec-2013)
+Pass 1: Checking inodes, blocks, and sizes
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+/dev/vdb2: 11/3276800 files (0.0% non-contiguous), 251790/13107200 blocks
        +
        +
      2. Run the following command to extend the file system of the partition:

        resize2fs Disk partition

        +

        In this example, run the following command:

        +

        resize2fs /dev/vdb2

        +
        Information similar to the following is displayed:
        [root@ecs-test-0001 ~]# resize2fs /dev/vdb2
+resize2fs 1.42.9 (28-Dec-2013)
+Resizing the filesystem on /dev/vdb2 to 34078720 (4k) blocks.
+The filesystem on /dev/vdb2 is now 34078720 blocks long.
        +
        +
      3. (Optional) Run the following command to create a mount point:

        Perform this step if you want to mount the partition on a new mount point.

        +

        mkdir Mount point

        +

        In this example, run the following command to create the /mnt/test mount point:

        +

        mkdir /mnt/test

        +
      4. Run the following command to mount the partition:

        mount Disk partition Mount point

        +

        In this example, run the following command to the mount partition /dev/vdb2 on /mnt/test:

        +

        mount /dev/vdb2 /mnt/test

        +

        If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

        +
        +
      +
    • For the xfs file system
      1. (Optional) Run the following command to create a mount point:

        Perform this step if you want to mount the partition on a new mount point.

        +

        mkdir Mount point

        +

        In this example, run the following command to create the /mnt/test mount point:

        +

        mkdir /mnt/test

        +
      2. Run the following command to mount the partition:

        mount Disk partition Mount point

        +

        In this example, run the following command to the mount partition /dev/vdb2 on /mnt/test:

        +

        mount /dev/vdb2 /mnt/test

        +

        If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

        +
        +
      3. Run the following command to extend the file system of the partition:

        sudo xfs_growfs Disk partition

        +

        In this example, run the following command:

        +

        sudo xfs_growfs /dev/vdb2

        +

        Information similar to the following is displayed:

        +
        [root@ecs-test-0001 ~]# sudo xfs_growfs /dev/vdb2 
+meta-data=/dev/vdb2              isize=512     agcount=4, agsize=3276800 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, spinodes=0
+data     =                       bsize=4096    blocks=13107200, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal               bsize=4096    blocks=6400, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
+data blocks changed from 13107200 to 34078720.
        +
      +
    +

  14. Run the following command to view the mount result:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.1M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
+/dev/vdb2      ext4      138G   63M  131G   1% /mnt/test
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +
    +

+
+

Creating a New GPT Partition

Originally, data disk /dev/vdb has 100 GB and one partition (/dev/vdb1), and then 50 GB is added to the disk. The following procedure shows you how to create a new GPT partition /dev/vdb2 with this 50 GB.

+
  1. Run the following command to view the disk partition information:

    lsblk

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  150G  0 disk
+└─vdb1 253:17   0  100G  0 part /mnt/sdc
    +
    +

  2. Run the following command to enter parted:

    parted Disk

    +

    In this example, run the following command:

    +

    parted /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# parted /dev/vdb
+GNU Parted 3.1
+Using /dev/vdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted)
    +
    +

  3. Enter unit s and press Enter to set the measurement unit of the disk to sector.
  4. Enter p and press Enter to view the disk partition information.

    Information similar to the following is displayed:
    (parted) unit s
+(parted) p
+Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the
+disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
+Fix/Ignore/Cancel? Fix
+Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 104857600
+blocks) or continue with the current setting?
+Fix/Ignore? Fix
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 314572800s
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start  End         Size        File system  Name  Flags
+ 1      2048s  209713151s  209711104s  ext4         test
+
+(parted)
    +
    +
    In the command output, take note of the partition's end sector. In this example, the end sector of the /dev/vdb1 partition is 209713151s.
    • If the following error information is displayed, enter Fix.
      Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the
+disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
      +

      The GPT partition table information is stored at the start of the disk. To reduce the risk of damage, a backup of the information is saved at the end of the disk. When you expand the disk capacity, the end of the disk changes accordingly. In this case, enter Fix to move the backup file of the information to new disk end.

      +
    • If the following warning information is displayed, enter Fix.
      Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 104857600
+blocks) or continue with the current setting?
+Fix/Ignore? Fix
      +

      Enter Fix as prompted. The system automatically sets the GPT partition style for the additional space.

      +
    +
    +

  5. Run the following command and press Enter:

    mkpart Partition name Start sector End sector

    +

    In this example, run the following command:

    +

    mkpart data 209713152s 100%

    +

    In this example, the additional space is used to create a new partition. In 4, the end sector of partition dev/vdb1 is 209713151s. Therefore, the start sector of the new partition dev/vdb2 is set to 209713152s and the end sector 100%. This start and end sectors are for reference only. You can plan the number of partitions and partition size based on service requirements.

    +
    Information similar to the following is displayed:
    (parted) mkpart data 209713152s 100%
+(parted)
    +
    +

    The maximum sector can be obtained in either of the following ways:

    +
    • Query the disk's maximum end sector. For details, see 2 to 4.
    • Enter -1s or 100%, and the value displayed is the maximum end sector.
    +
    +

  6. Enter p and press Enter to view the new partition.

    Information similar to the following is displayed:
    (parted) p
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 314572800s
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start       End         Size        File system  Name  Flags
+ 1      2048s       209713151s  209711104s  ext4         test
+ 2      209713152s  314570751s  104857600s               data
+
+(parted)
    +
    +

  7. Enter q and press Enter to exit parted.

    Information similar to the following is displayed:
    (parted) q
+Information: You may need to update /etc/fstab.
    +
    +

    You can set automatic disk mounting by updating the /etc/fstab file. Before updating the file, set the file system format for the partition and mount the partition on the mount point.

    +

  8. Run the following command to set the file system format for the new partition:

    mkfs -t File system Disk partition

    +
    • Sample command of the ext* file system:

      mkfs -t ext4 /dev/vdb2

      +

      Information similar to the following is displayed:

      +
      [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb2
+mke2fs 1.42.9 (28-Dec-2013)
+Filesystem label=
+OS type: Linux
+Block size=4096 (log=2)
+Fragment size=4096 (log=2)
+Stride=0 blocks, Stripe width=0 blocks
+3276800 inodes, 13107200 blocks
+655360 blocks (5.00%) reserved for the super user
+First data block=0
+Maximum filesystem blocks=2162163712
+400 block groups
+32768 blocks per group, 32768 fragments per group
+8192 inodes per group
+Superblock backups stored on blocks:
+        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
+        4096000, 7962624, 11239424
+
+Allocating group tables: done
+Writing inode tables: done
+Creating journal (32768 blocks): done
+Writing superblocks and filesystem accounting information: done
      +
    +
    • Sample command of the xfs file system:

      mkfs -t xfs /dev/vdb2

      +

      Information similar to the following is displayed:

      +
      [root@ecs-test-0001 ~]# mkfs -t xfs /dev/vdb2 
+meta-data=/dev/vdb2              isize=512     agcount=4, agsize=3276800 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, sparse=0
+data     =                       bsize=4096    blocks=13107200, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal log           bsize=4096    blocks=6400, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
      +
    +

    The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

    +

  9. (Optional) Run the following command to create a mount point:

    Perform this step if you want to mount the partition on a new mount point.

    +

    mkdir Mount point

    +

    In this example, run the following command to create the /mnt/test mount point:

    +

    mkdir /mnt/test

    +

  10. Run the following command to mount the new partition:

    mount Disk partition Mount point

    +

    In this example, run the following command to mount the new partition /dev/vdb2 on /mnt/test:

    +

    mount /dev/vdb2 /mnt/test

    +

    If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

    +
    +

  11. Run the following command to view the mount result:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.1M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
+/dev/vdb2      ext4       53G   55M   50G   1% /mnt/test
    +
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +

+
+

Extending an Existing GPT Partition

If the additional space is allocated to an existing partition, data on the disk will not be cleared but you must use umount to unmount the existing partition. In this case, services will be affected.

+
+

Originally, data disk /dev/vdb has 150 GB and two partitions (/dev/vdb1 and /dev/vdb2), and then 80 GB is added to the disk. The following procedure shows you how to add this 80 GB to the existing GPT partition /dev/vdb2.

+

During an expansion, the additional space is added to the end of the disk. Therefore, if the disk has multiple partitions, the additional space can only be allocated to the partition at the disk end.

+
  1. Run the following command to view the disk partition information:

    lsblk

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  230G  0 disk
+├─vdb1 253:17   0  100G  0 part /mnt/sdc
+└─vdb2 253:18   0   50G  0 part /mnt/test
    +
    +
    View the /dev/vdb capacity and check whether the additional space is included. +
    +

  2. Run the following command to unmount the partition:

    umount Disk partition

    +

    In this example, run the following command:

    +

    umount /dev/vdb2

    +

  3. Run the following command to view the unmount result:

    lsblk

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0  230G  0 disk
+├─vdb1 253:17   0  100G  0 part /mnt/sdc
+└─vdb2 253:18   0   50G  0 part
    +
    +

  4. Run the following command to enter parted:

    parted Disk

    +

    In this example, run the following command:

    +

    parted /dev/vdb

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# parted /dev/vdb
+GNU Parted 3.1
+Using /dev/vdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted)
    +
    +

  5. Enter unit s and press Enter to set the measurement unit of the disk to sector.
  6. Enter p and press Enter to view the disk partition information.

    Information similar to the following is displayed:
    (parted) unit s
+(parted) p
+Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the
+disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
+Fix/Ignore/Cancel? Fix
+Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 167772160
+blocks) or continue with the current setting?
+Fix/Ignore? Fix
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 482344960s
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start       End         Size        File system  Name  Flags
+ 1      2048s       209713151s  209711104s  ext4         test
+ 2      209713152s  314570751s  104857600s  ext4         data
+
+(parted)
    +
    +
    Take note of the start and end sectors of the /dev/vdb2 partition. These values will be used during the partition recreation. In this example, the partition's start sector is 209713152s, and its end sector is 314570751s.
    • If the following error information is displayed, enter Fix.
      Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the
+disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
      +

      The GPT partition table information is stored at the start of the disk. To reduce the risk of damage, a backup of the information is saved at the end of the disk. When you expand the disk capacity, the end of the disk changes accordingly. In this case, enter Fix to move the backup file of the information to new disk end.

      +
    • If the following warning information is displayed, enter Fix.
      Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 104857600
+blocks) or continue with the current setting?
+Fix/Ignore? Fix
      +

      Enter Fix as prompted. The system automatically sets the GPT partition style for the additional space.

      +
    +
    +

  7. Enter rm and the partition number, and then press Enter. In this example, partition number 2 is used.

    Information similar to the following is displayed:
    (parted) rm
+Partition number? 2
+(parted)
    +
    +

  8. Run the following command to recreate the partition and press Enter:

    mkpart Partition name Start sector End sector

    +

    In this example, run the following command:

    +

    mkpart data 209713152s 100%

    +
    • Ensure that the entered start sector is the same as the partition had before. In this example, start sector 209713152s is recorded in 6. Therefore, enter 209713152s.
    • Ensure that the entered end sector is greater than the partition had before. In this example, the end sector recorded in 6 is 314570751s, and all the additional space needs to be allocated to dev/vdb2. Therefore, enter 100%.
    +
    Information similar to the following is displayed:
    (parted) mkpart data 209713152s 100%
+(parted)
    +
    +
    Data will be lost if the following operations are performed:
    • Select a start sector other than the partition had before.
    • Select an end sector smaller than the partition had before.
    +
    +
    +

  9. Enter p and press Enter to view the partition information.

    Information similar to the following is displayed:
    (parted) p
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdb: 482344960s
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+
+Number  Start       End         Size        File system  Name  Flags
+ 1      2048s       209713151s  209711104s  ext4         test
+ 2      209713152s  482342911s  272629760s  ext4         data
+
+(parted)
    +
    +

  10. Enter q and press Enter to exit parted.

    Information similar to the following is displayed:
    (parted) q
+Information: You may need to update /etc/fstab.
    +
    +

    You can set automatic disk mounting by updating the /etc/fstab file. Before updating the file, set the file system format for the partition and mount the partition on the mount point.

    +

  11. Perform the following operations based on the file system of the disk:

    • For the ext* file system
      1. Run the following command to check the correctness of the file system on the partition:

        e2fsck -f Disk partition

        +

        In this example, run the following command:

        +

        e2fsck -f /dev/vdb2

        +
        Information similar to the following is displayed:
        [root@ecs-test-0001 ~]# e2fsck -f /dev/vdb2
+e2fsck 1.42.9 (28-Dec-2013)
+Pass 1: Checking inodes, blocks, and sizes
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+/dev/vdb2: 11/3276800 files (0.0% non-contiguous), 251790/13107200 blocks
        +
        +
      2. Run the following command to extend the file system of the partition:

        resize2fs Disk partition

        +

        In this example, run the following command:

        +

        resize2fs /dev/vdb2

        +
        Information similar to the following is displayed:
        [root@ecs-test-0001 ~]# resize2fs /dev/vdb2
+resize2fs 1.42.9 (28-Dec-2013)
+Resizing the filesystem on /dev/vdb2 to 34078720 (4k) blocks.
+The filesystem on /dev/vdb2 is now 34078720 blocks long.
        +
        +
      3. (Optional) Run the following command to create a mount point:

        Perform this step if you want to mount the partition on a new mount point.

        +

        mkdir Mount point

        +

        In this example, run the following command to create the /mnt/test mount point:

        +

        mkdir /mnt/test

        +
      4. Run the following command to mount the partition:

        mount Disk partition Mount point

        +

        In this example, run the following command to the mount partition /dev/vdb2 on /mnt/test:

        +

        mount /dev/vdb2 /mnt/test

        +

        If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

        +
        +
      +
    • For the xfs file system
      1. (Optional) Run the following command to create a mount point:

        Perform this step if you want to mount the partition on a new mount point.

        +

        mkdir Mount point

        +

        In this example, run the following command to create the /mnt/test mount point:

        +

        mkdir /mnt/test

        +
      2. Run the following command to mount the partition:

        mount Disk partition Mount point

        +

        In this example, run the following command to the mount partition /dev/vdb2 on /mnt/test:

        +

        mount /dev/vdb2 /mnt/test

        +

        If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

        +
        +
      3. Run the following command to extend the file system of the partition:

        sudo xfs_growfs Disk partition

        +

        In this example, run the following command:

        +

        sudo xfs_growfs /dev/vdb2

        +

        Information similar to the following is displayed:

        +
        [root@ecs-test-0001 ~]# sudo xfs_growfs /dev/vdb2 
+meta-data=/dev/vdb2              isize=512     agcount=4, agsize=3276800 blks
+         =                       sectsz=512    attr=2, projid32bit=1
+         =                       crc=1         finobt=0, spinodes=0
+data     =                       bsize=4096    blocks=13107200, imaxpct=25
+         =                       sunit=0       swidth=0 blks
+naming   =version2               bsize=4096    ascii-ci=0 ftype=1
+log      =internal               bsize=4096    blocks=6400, version=2
+         =                       sectsz=512    sunit=0 blks, lazy-count=1
+realtime =none                   extsz=4096    blocks=0, rtextents=0
+data blocks changed from 13107200 to 34078720.
        +
      +
    +

  12. Run the following command to view the mount result:

    df -TH

    +
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.1M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
+/dev/vdb2      ext4      138G   63M  131G   1% /mnt/test
    +

    If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.

    +
    +
    +

+
+

Setting Automatic Mounting at System Start

Modify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.

+

The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.

+

UUID is the unique character string for disk partitions in a Linux system.

+
+
  1. Run the following command to query the partition UUID:

    blkid Disk partition

    +

    In this example, run the following command to query the UUID of the /dev/vdb1 partition:

    +

    blkid /dev/vdb1

    +

    Information similar to the following is displayed:

    +
    [root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
    +

    The UUID of the /dev/vdb1 partition is displayed.

    +

  2. Run the following command to open the fstab file using the vi editor:

    vi /etc/fstab

    +

  3. Press i to enter the editing mode.
  4. Move the cursor to the end of the file and press Enter. Then, add the following information:

    UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
    +

  5. Press Esc, enter :wq, and press Enter.

    The system saves the configurations and exits the vi editor.

    +

  6. Perform the following operations to verify the automatic mounting function:

    1. Run the following command to unmount the partition:

      umount Disk partition

      +

      In this example, run the following command:

      +

      umount /dev/vdb1

      +
    2. Run the following command to reload all the content in the /etc/fstab file:

      mount -a

      +
    3. Run the following command to query the file system mounting information:

      mount | grep Mount point

      +

      In this example, run the following command:

      +

      mount | grep /mnt/sdc

      +

      If information similar to the following is displayed, the automatic mounting function takes effect:

      +
      root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
      +
    +

+
+
+ + diff --git a/docs/evs/umn/evs_01_0110.html b/docs/evs/umn/evs_01_0110.html new file mode 100644 index 000000000..96d0ff135 --- /dev/null +++ b/docs/evs/umn/evs_01_0110.html @@ -0,0 +1,21 @@ + + +

Managing EVS Backup

+

Scenarios

EVS disk backups are created using the CBR service. For details, see Creating a Disk Backup Vault in the Cloud Backup and Recovery User Guide.

+

+

This section describes how to configure a backup policy for disks. With backup policies configured, data on EVS disks can be periodically backed up to improve data security.

+
+

a Disk Backup Vault and Configuring the Backup Policy

  1. Log in to the CBR console.

    1. Log in to the management console.
    2. Click in the upper left corner and select the desired region and project.
    3. Choose Storage > Cloud Backup and Recovery > Cloud Disk Backup.
    +

  2. In the upper right corner, click Create Disk Backup Vault.
  3. (Optional) Select the disks you want to back up in the disk list. Selected disks will appear in the right area.

    Figure 1 Selecting disks
    +
    • Only the Available or In-use disks can be selected.
    • You can associate desired disks with the vault you created later if you skip this step.
    +
    +

  4. Specify the vault capacity. This capacity indicates the total size of the disks that you want to associate with this vault. Therefore, specify a vault capacity that is greater than or equal to the total size of the disks you want to back up. The value ranges from the total size of the disks to 10,485,760 in the unit of GB.
  5. Determine whether to configure auto backup.

    • If you select Configure, you must then select an existing backup policy or create a new one. After the vault is created, the system applies this backup policy to the vault, and all disks associated with this vault will be automatically backed up based on this policy.
    • If you select Skip, disks associated with this vault are not automatically backed up.
    +

  6. Specify the vault name.

    A name must contain 1 to 64 characters including digits, letters, underscores (_), and hyphens (-), for example, vault-612c.

    +

    You can use the default name, which is in the format of vault_xxxx.

    +
    +

  7. Click Next.
  8. Complete the creation as prompted.
  9. Go back to the disk backup page. The vault you created is displayed in the list.

    You can associate disks to the new vault or create backups for disks. For details, see Vault Management in the Cloud Backup and Recovery User Guide.

    +

+
+
+
+ diff --git a/docs/evs/umn/evs_01_0111.html b/docs/evs/umn/evs_01_0111.html new file mode 100644 index 000000000..ef7f525a3 --- /dev/null +++ b/docs/evs/umn/evs_01_0111.html @@ -0,0 +1,19 @@ + + +

Managing Snapshots

+
+ + diff --git a/docs/evs/umn/evs_01_0112.html b/docs/evs/umn/evs_01_0112.html new file mode 100644 index 000000000..8f1f56111 --- /dev/null +++ b/docs/evs/umn/evs_01_0112.html @@ -0,0 +1,19 @@ + + +

Managing a Tag

+
+ + diff --git a/docs/evs/umn/evs_01_0114.html b/docs/evs/umn/evs_01_0114.html new file mode 100644 index 000000000..5e30b729e --- /dev/null +++ b/docs/evs/umn/evs_01_0114.html @@ -0,0 +1,270 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Release Date

+

What's New

+

2022-04-15

+

Added the following content:

+ +

2021-12-27

+

Modified the following content:

+
  • Optimized the descriptions of the impacts brought by an unavailable CMK in EVS Disk Encryption.
+

2020-08-15

+

Added the following content:

+ +

2019-04-09

+

Accepted in OTC-4.0/Agile-04.2019.

+

2019-02-15

+

Modified the following content:

+
  • Deprecated the content of EVS replication as EVS replication APIs have been deprecated.
+
Modified the following content:
  • Updated the screenshot of non-encrypted disks in Create an EVS Disk based on the tag parameter changes made on the EVS console.
+
+

2018-11-30

+

Added the following content:

+ +

2018-05-14

+

Modified the following content:

+
  • Modified the reviewed issues.
+

2018-02-28

+

Added the following content:

+
  • Added Expanding EVS Disks in a Replication Consistency Group.
+

Modified the following content:

+
  • Modified the EVS replication flowchart and added some contents.
+

2018-02-24

+

Modified the following content:

+
  • Modified Configuring a Virtual IP Address for the Server.
  • Modified the reviewed issues.
+

2018-01-31

+

Added the following content:

+
  • Added Configuring a Virtual IP Address for the Server.
+

2018-01-25

+

Modified the following content:

+
  • Modified the reviewed issues.
  • Changed a prerequisite for performing planned migrations and reprotections to that only production servers need to be stopped but EVS disks no longer need to be detached.
+

2018-01-19

+

Modified the following content:

+ +

2017-12-01

+

Modified the following content:

+
  • Modified the reviewed EVS replication issues.
+

2017-11-30

+

Modified the following content:

+
  • Modified the reviewed EVS replication issues.
+

2017-10-28

+

Added the following content:

+
  • Added descriptions about EVS replication.
+

2017-10-25

+

Modified the following content:

+ +

2017-10-20

+

Modified the following content:

+
  • Changed the maximum capacity of a system disk to 1024 GB in Create an EVS Disk.
  • Added the description that a maximum of 7 snapshots can be created for an EVS disk in Creating a Snapshot.
+

2017-10-13

+

Added the following content:

+
  • Enabled the function of rolling back data from snapshots and added the relevant content in the document.
  • Added the content of searching EVS resources by tags in Searching Disks by Tags.
+

Modified the following content:

+ +

2017-09-30

+

Added the following content:

+ +

Modified the following content:

+ +

2017-09-28

+

Modified the following content:

+
  • Adjusted the outline of the document.
  • Modified the reviewed issues in the document.
+

2017-09-08

+

Added the following content:

+
  • Added support for the disk creation using a backup shared by another tenant in Create an EVS Disk.
+

Modified the following content:

+
  • Removed the Restore Data button from the EVS console, and deleted or modified the related descriptions from the document.
+

2017-08-22

+

Modified the following content:

+
  • Modified the reviewed issues in the document.
+

2017-07-30

+

Added the following content:

+
  • Added support for the EVS snapshot function.
  • Added support for the TMS tag function.
  • Added support for the High I/O (Performance optimized I) and Ultra-high I/O (Latency optimized) EVS disk types.
  • Added support for the multi-project function.
+

2017-06-15

+

Added the following content:

+
  • Added the description that SCSI EVS disks can only be attached to BMSs.
+

2017-06-08

+

Modified the following content:

+ +

2017-06-06

+

Added the following content:

+ +

2017-06-05

+

Added the following content:

+ +

Modified the following content:

+
  • Modified the disk attachment description from attaching EVS disks to ECSs to attaching EVS disks to servers. Servers can be either ECSs or BMSs.
+

2017-06-01

+

Added the following content:

+ +

2017-05-22

+

Modified the following content:

+
  • Made modifications in Create an EVS Disk according to the adjustments made on the Create Disk page.
    • Adjusted the sequence of parameters Disk Name and AZ.
    • Adjusted the location of parameter Create from backup.
    +
+

2017-05-05

+

Added the following content:

+
  • Added SCSI and VBD to the glossary.
+

2017-04-30

+

Added the following content:

+
  • Added Windows public images and ECS types supported by shared SCSI EVS disks.
+

2017-03-30

+

Added the following content:

+ +

2017-02-08

+

Modified the following content:

+
  • Modified the description for parameters Create Xrole and Xrole Name:EVSAccessKMS in Create an EVS Disk.
+

2017-02-03

+

Added the following content:

+
  • Added the description that batch creation is not supported when EVS disks are created from backups in Create an EVS Disk.
  • Added the description for parameters Create Xrole and Xrole Name:EVSAccessKMS in Create an EVS Disk.
+

Modified the following content:

+ +

2017-01-23

+

Added the following content:

+
  • Added the impact on encrypted EVS disks caused by the disabled and schedule deleted CMKs.
+

2017-01-20

+

Added the following content:

+
  • Added the key encryption function of EVS disks.
+

2016-10-28

+

Added the following content:

+ +

Modified the following content:

+
  • Updates the format of Steps in the document.
  • Updated the figure for Step 9 in Initializing a Windows Data Disk (Windows Server 2008).
  • Changes the value of Number of Cloud Server Mount Points from 11 to 14 in the EVS row of Table 3-1.
  • Updates the NOTE descriptions in Step 13 of "Expand Capacity of an EVS Disk (Windows)" and Step 12 of "Expand Capacity of an EVS Disk (Linux)": indicating that the new disks must be initialized.
  • Added double quotation marks to "Creating a VBS Backup" to indicate quotation in Managing EVS Backup.
  • Updated the description of EVS disk specifications to be consistent with descriptions in previous sections in Disk Types and Performance.
  • Updated the section names in NOTE to be consistent with section 4.10 in EVS Disk Status.
+

Deleted the following content:

+
  • Deleted the Monitored Object column from Table 1-1 in EVS and Other Services.
  • Deletes the unnecessary table of Mapping between mount points and EVS disk names.
  • Deletes the comma before "or Restoration failed" in the section of Delete an EVS disk.
  • Deletes sections 4.1, 4.2, and 4.3 from FAQs, because the three sections have been contained in the Overview chapter.
+

2016-09-23

+

Added the following content:

+
  • Adds the details about three disk types.
  • Adds information about how to handle deletion or restoration failures to the notice for the section of Delete an EVS Disk.
+

Modified the following content:

+
  • Updates the link names in step 20 and the note in the section of Expand Capacity of an EVS Disk (Linux).
+

Deleted the following content:

+
  • Deletes part of the AZ parameter description from the table.
+

2016-09-18

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/evs/umn/evs_01_0115.html b/docs/evs/umn/evs_01_0115.html new file mode 100644 index 000000000..213e502c6 --- /dev/null +++ b/docs/evs/umn/evs_01_0115.html @@ -0,0 +1,7 @@ + + +

Glossary

+

For details about the terms involved in this document, see Glossary.

+
+
+ diff --git a/docs/evs/umn/evs_01_0119.html b/docs/evs/umn/evs_01_0119.html new file mode 100644 index 000000000..d0f25d8b3 --- /dev/null +++ b/docs/evs/umn/evs_01_0119.html @@ -0,0 +1,33 @@ + + +

Overview

+
+ + diff --git a/docs/evs/umn/evs_01_0120.html b/docs/evs/umn/evs_01_0120.html new file mode 100644 index 000000000..404aa3a7a --- /dev/null +++ b/docs/evs/umn/evs_01_0120.html @@ -0,0 +1,17 @@ + + +

Getting Started

+
+ + diff --git a/docs/evs/umn/evs_faq_0001.html b/docs/evs/umn/evs_faq_0001.html new file mode 100644 index 000000000..9b081a557 --- /dev/null +++ b/docs/evs/umn/evs_faq_0001.html @@ -0,0 +1,21 @@ + + +

FAQ

+
+ + diff --git a/docs/evs/umn/evs_faq_0006.html b/docs/evs/umn/evs_faq_0006.html new file mode 100644 index 000000000..8de2af2e8 --- /dev/null +++ b/docs/evs/umn/evs_faq_0006.html @@ -0,0 +1,13 @@ + + +

Can I Attach a Disk to Multiple Servers?

+
  • A non-shared disk can only be attached to one server.
  • A shared disk can be attached to up to 16 servers.
    • Shared disks are a type of EVS disks that can be attached to multiple servers.
    • To use shared disks, you must set up a shared file system or cluster management system. If you directly attach a disk to multiple servers, the disk sharing attribute does not work and data may be overwritten.
    +
    +
+
+
+
+
Parent topic: Attachment
+
+
+ diff --git a/docs/evs/umn/evs_faq_0012.html b/docs/evs/umn/evs_faq_0012.html new file mode 100644 index 000000000..4156fa8bb --- /dev/null +++ b/docs/evs/umn/evs_faq_0012.html @@ -0,0 +1,23 @@ + + +

If I Detach a Disk Will I Lose the Data on My Disk?

+

It depends on if the disk is encrypted or not.

+
  • Encrypted
    • CMK is disabled or scheduled for deletion.

      Before you detach an EVS disk encrypted by a CMK, check whether the CMK is disabled or scheduled for deletion. If the CMK is unavailable, the disk can still be used, but there is no guarantee how long it will be usable. If the disk is detached, it will not be possible to re-attach it later. In this case, do not detach the disk without a working CMK.

      +

      The restoration method varies depending on the CMK status. For details, see EVS Disk Encryption.

      +
    • CMK is available.

      If the CMK is available, the disk can be detached and re-attached, and data on the disk will not be lost.

      +

      To ensure your data safety, you are advised to follow the instructions described in Disk detachment process.

      +
    +
  • Non-encrypted

    Data on a disk will not be lost after the disk is detached, and the disk can be re-attached later if needed.

    +

    To ensure your data safety, you are advised to follow the instructions described in Disk detachment process.

    +
+

Disk detachment process

  • For disks not supporting online detachment:
    1. Stop the server where the disk was attached.
    2. After the server has stopped, detach the disk.
    +
  • For disks supporting online detachment:

    Detach the disk from a running ECS. For details, see Management > Detaching an EVS Disk from a Running ECS in the Elastic Cloud Server User Guide.

    +
+
+
+
+
+
Parent topic: Detachment
+
+
+ diff --git a/docs/evs/umn/evs_faq_0014.html b/docs/evs/umn/evs_faq_0014.html new file mode 100644 index 000000000..00b36ca5c --- /dev/null +++ b/docs/evs/umn/evs_faq_0014.html @@ -0,0 +1,51 @@ + + +

What Should I Do If an Error Occurs on My EVS Disk?

+

If an error occurs, the disk may show one of the states listed in the following table. Take the measures described in the table to handle the exceptions.

+ +
+ + + + + + + + + + + + + + + + + + + +
Table 1 Solutions for disk errors

Error Status

+

Handling Suggestion

+

Error

+

Delete the disk in the Error state and create another one.

+

The disk will no longer be charged after an error has occurred.

+

Deletion failed

+

Contact customer service.

+

The disk will no longer be charged after its status changes to Deletion failed.

+

Expansion failed

+

Our customer service personnel will contact you and help you handle this error. Do not perform any operations on the disk before the customer service personnel contact you. If the issue is urgent, you can contact our customer service personnel directly.

+

The disk will no longer be charged after its status changes to Expansion failed.

+

Restoration failed

+

Our customer service personnel will contact you and help you handle this error. Do not perform any operations on the disk before the customer service personnel contact you. If the issue is urgent, you can contact our customer service personnel directly.

+

The disk will no longer be charged after its status changes to Restoration failed.

+

Rollback failed

+

You can roll back the snapshot data to the disk again.

+

The disk will no longer be charged after its status changes to Rollback failed.

+
+
+
+
+
+
Parent topic: General
+
+
+ diff --git a/docs/evs/umn/evs_faq_0020.html b/docs/evs/umn/evs_faq_0020.html new file mode 100644 index 000000000..c7849ff12 --- /dev/null +++ b/docs/evs/umn/evs_faq_0020.html @@ -0,0 +1,13 @@ + + +

What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)

+

If the system displays a message indicating insufficient quota during an EVS replication pair creation or a replication consistency group creation or update, contact the administrator to handle this issue.

+

EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

+
+
+
+
+
Parent topic: General
+
+
+ diff --git a/docs/evs/umn/evs_faq_0021.html b/docs/evs/umn/evs_faq_0021.html new file mode 100644 index 000000000..53619c988 --- /dev/null +++ b/docs/evs/umn/evs_faq_0021.html @@ -0,0 +1,17 @@ + + +

Why Do Some of My EVS Disks Not Have WWN Information?

+

EVS disks have two device types: VBD and SCSI. WWNs are used as the unique identifiers for SCSI EVS disks, and VBD EVS disks do not have WWNs.

+

You can view the WWN of a SCSI EVS disk on the management console. The details are as follows:

+
  • If the SCSI EVS disk is brand new, you can view the disk WWN on the disk details page.
    Figure 1 shows the query result.
    Figure 1 Queried WWN information
    +
    +
  • If the SCSI EVS disk was created before the WWN feature rollout, the disk WWN will fail to be obtained.

    Figure 2 shows the query result.

    +
    Figure 2 No WWN information
    +
+
+
+
+
Parent topic: General
+
+
+ diff --git a/docs/evs/umn/evs_faq_0022.html b/docs/evs/umn/evs_faq_0022.html new file mode 100644 index 000000000..a8ea081f7 --- /dev/null +++ b/docs/evs/umn/evs_faq_0022.html @@ -0,0 +1,64 @@ + + +

Why Can't I View the Attached Data Disk on the Server?

+

Windows data disk

Symptom: A data disk has been attached to a Windows server on the management console, but the disk cannot be viewed on the server. For example, Volume (D:) was not shown in This PC of a Windows server running Windows Server 2012. Normally, Volume (D:) appears, as shown in Figure 1.

+
Figure 1 Volume (D:) appears
+

Solution: New data disks are not formatted and partitioned by default. Only formatted and partitioned drives show up in This PC. You must manually initialize the disk before it can be viewed here.

+

For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+
+

Linux data disk

Symptom: A data disk has been attached to a Linux server on the management console, but the disk cannot be viewed on the server.

+

Run df -TH to view the disk information. CentOS 7.4 is used in this example. The normal command output is as follows:

+
[root@ecs-test-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  1.9G   39G   5% /
+devtmpfs       devtmpfs  2.0G     0  2.0G   0% /dev
+tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
+tmpfs          tmpfs     2.0G  9.1M  2.0G   1% /run
+tmpfs          tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
+tmpfs          tmpfs     398M     0  398M   0% /run/user/0
+/dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc
+
+

Unlike the normal command output, only system disk /dev/vda1 is visible, but data disk /dev/vdb1 is missing from the command output.

+

Solution

+
  • Method 1: New data disks are not formatted and partitioned by default, and an unformatted disk will not be listed in the command output. You must manually initialize the disk.

    For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

    +
  • Method 2: If the data disk cannot be found after the server is restarted, automatic partition mounting at system start may not be configured. Perform the following steps:
    1. Run the following command to mount the partition again:

      mount Disk partition Mount point

      +

      In this example, run the following command:

      +

      mount /dev/vdb1 /mnt/sdc

      +

      Perform the following steps to enable automatic partition mounting at system start:

      +
    2. Run the following command to query the partition UUID:

      blkid Disk partition

      +

      In this example, run the following command to query the UUID of the /dev/vdb1 partition:

      +

      blkid /dev/vdb1

      +

      Information similar to the following is displayed:

      +
      [root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
      +

      The UUID of the /dev/vdb1 partition is displayed.

      +
    3. Run the following command to open the fstab file using the vi editor:

      vi /etc/fstab

      +

      Press i to enter editing mode.

      +
    4. Move the cursor to the end of the file and press Enter. Then, add the following information:
      UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
      +
      The preceding content is used for reference only. Add the information that is used in the environment. The parameters are described as follows:
      • The first column indicates the partition UUID obtained in 2.
      • The second column indicates the directory on which the partition is mounted. You can query the mount point using the df -TH command.
      • The third column indicates the file system format of the partition. You can query the file system format using the df -TH command.
      • The fourth column indicates the partition mount option. Normally, this parameter is set to defaults.
      • The fifth column indicates the Linux dump backup option.
        • 0: No Linux dump backup is used. This is the default setting. You can set this parameter to 0.
        • 1: Linux dump backup is used.
        +
      • The sixth column indicates the fsck option, that is, whether to use fsck to check the attached disk during startup.
        • 0: not use fsck.
        • If the mount point is the root partition (/), this parameter must be set to 1.

          When this parameter is set to 1 for the root partition, this parameter for other partitions must start with 2 because the system checks the partitions in the ascending order of the values.

          +
        +
      +
      +
    5. Press Esc, enter :wq, and press Enter.

      The system saves the configurations and exits the vi editor.

      +
      Perform the following operations to verify the automatic mounting function:
      1. Run the following command to unmount the partition:

        umount Disk partition

        +

        In this example, run the following command:

        +

        umount /dev/vdb1

        +
      2. Run the following command to reload all the content in the /etc/fstab file:

        mount -a

        +
      3. Run the following command to query the file system mounting information:

        mount | grep Mount point

        +

        In this example, run the following command:

        +

        mount | grep /mnt/sdc

        +

        If information similar to the following is displayed, automatic mounting has been configured:

        +
        root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
        +
      +
      +
    +
+
+
+
+
Parent topic: Attachment
+
+
+ diff --git a/docs/evs/umn/evs_faq_0024.html b/docs/evs/umn/evs_faq_0024.html new file mode 100644 index 000000000..8ba63ab63 --- /dev/null +++ b/docs/evs/umn/evs_faq_0024.html @@ -0,0 +1,19 @@ + + +

What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?

+

An EVS system disk can be as large as 1 TB (1024 GB). You can expand the capacity of a system disk to up to 1 TB.

+
An EVS data disk can be as large as 32 TB (32768 GB).
  • With MBR, any disk space in excess of 2 TB cannot be allocated and used, because the maximum disk capacity supported by MBR is 2 TB (2048 GB).

    In this case, if you want to expand the disk capacity to over 2 TB, change the partition style from MBR to GPT. Ensure that the disk data has been backed up before changing the partition style because services will be interrupted and data on the disk will be deleted during this change.

    +
+ +
+
+
+
+
Parent topic: Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_faq_0026.html b/docs/evs/umn/evs_faq_0026.html new file mode 100644 index 000000000..7185edf8a --- /dev/null +++ b/docs/evs/umn/evs_faq_0026.html @@ -0,0 +1,11 @@ + + +

Can I Reduce or Temporarily Expand the Disk Capacity?

+

No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.

+
+
+
+
Parent topic: Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_faq_0027.html b/docs/evs/umn/evs_faq_0027.html new file mode 100644 index 000000000..ab9063502 --- /dev/null +++ b/docs/evs/umn/evs_faq_0027.html @@ -0,0 +1,13 @@ + + +

Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?

+

After expanding disk capacity on the management console, you must log in to the server and extend the disk partition and file system for the extra capacity to become available. Otherwise, you cannot view the additional space on the server.

+
To extend disk partitions and file systems, see the following sections: +
+
+
+
+
Parent topic: Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_faq_0028.html b/docs/evs/umn/evs_faq_0028.html new file mode 100644 index 000000000..291e520c2 --- /dev/null +++ b/docs/evs/umn/evs_faq_0028.html @@ -0,0 +1,16 @@ + + +

Do I Need to Detach an EVS Disk Before Expanding Its Capacity?

+
An expansion consists of two phases:
  1. Expand the disk capacity on the management console.
    • A shared, in-use disk cannot be expanded. You must detach the shared disk from all its servers and then expand its capacity.
    • A non-shared, in-use disk can be expanded, and you can leave the disk attached during expansion as long as the following conditions are met:
      • The disk's server is in the Running or Stopped state.
      • The disk's server OS supports the expansion of In-use disks.
      +
    +
  2. Log in to the server and create a new partition or allocate the additional space to one that is already there.
    • In Windows, there are no partition extensions that require the partition to be unmounted first.
    • In Linux:
      • When allocating the additional space to an existing partition, that is, extending an existing partition, you must use the umount command to unmount the partition first.
      • When allocating the additional space to a new partition, that is, creating a new partition, you do not need to unmount the existing partition.
      +
    +
+
+
+
+
+
Parent topic: Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_faq_0031.html b/docs/evs/umn/evs_faq_0031.html new file mode 100644 index 000000000..fc3c67e24 --- /dev/null +++ b/docs/evs/umn/evs_faq_0031.html @@ -0,0 +1,12 @@ + + +

What Is the Maximum Capacity Supported for the System and Data Disks?

+

The maximum capacity supported for a system disk is 1024 GB.

+

The maximum capacity supported for a data disk is 32768 GB.

+
+
+
+
Parent topic: Capacity
+
+
+ diff --git a/docs/evs/umn/evs_faq_0032.html b/docs/evs/umn/evs_faq_0032.html new file mode 100644 index 000000000..f5d925790 --- /dev/null +++ b/docs/evs/umn/evs_faq_0032.html @@ -0,0 +1,12 @@ + + +

What Should I Do If My Disk Starts to Run Out of Space?

+
If your disk space starts to fill up, you can:
  • Create a new disk and attach it to the server.
  • Expand the capacity of the existing disk. Both system disks and data disks can be expanded.
+
+
+
+
+
Parent topic: Capacity
+
+
+ diff --git a/docs/evs/umn/evs_faq_0035.html b/docs/evs/umn/evs_faq_0035.html new file mode 100644 index 000000000..1abf23b76 --- /dev/null +++ b/docs/evs/umn/evs_faq_0035.html @@ -0,0 +1,13 @@ + + +

What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TB and Then the Space in Excess of 2 TB Cannot Be Displayed?

+

If your disk capacity is greater than 2 TB, do not use fdisk to partition the disk. Or any space in excess of 2 TB will be unable to be displayed after the disk is partitioned.

+

In this case, use parted to repartition the disk and choose the GPT partition style because MBR does not support disks over 2 TB.

+

For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+
+
+
+
Parent topic: Capacity
+
+
+ diff --git a/docs/evs/umn/evs_faq_0036.html b/docs/evs/umn/evs_faq_0036.html new file mode 100644 index 000000000..0202716ca --- /dev/null +++ b/docs/evs/umn/evs_faq_0036.html @@ -0,0 +1,12 @@ + + +

Can I Attach a Disk to a Server in Another AZ?

+

No.

+

Disks and the servers you attach the disks to must be in the same AZ. The same is true for shared disks. Shared disks can only be attached to the servers in the same AZ.

+
+
+
+
Parent topic: Attachment
+
+
+ diff --git a/docs/evs/umn/evs_faq_0037.html b/docs/evs/umn/evs_faq_0037.html new file mode 100644 index 000000000..1d2175276 --- /dev/null +++ b/docs/evs/umn/evs_faq_0037.html @@ -0,0 +1,11 @@ + + +

How Many Servers Can I Attach a Shared Disk to?

+

A shared disk can be attached to up to 16 servers.

+
+
+
+
Parent topic: Sharing
+
+
+ diff --git a/docs/evs/umn/evs_faq_0039.html b/docs/evs/umn/evs_faq_0039.html new file mode 100644 index 000000000..15ab17548 --- /dev/null +++ b/docs/evs/umn/evs_faq_0039.html @@ -0,0 +1,13 @@ + + +

Do I Have to Deploy a Cluster to Use Shared Disks?

+

Yes.

+

If you simply attach a shared disk to multiple servers, files cannot be shared between the servers. If the rules for reading and writing data are not mutually agreed upon, the read and write operations may interfere with each other, or other unpredictable errors may occur.

+

Shared EVS disks do not have cluster management capabilities. You need to build a cluster system for data sharing, such as Windows MSCS, Veritas VCS, and Veritas CFS clusters.

+
+
+
+
Parent topic: Sharing
+
+
+ diff --git a/docs/evs/umn/evs_faq_0042.html b/docs/evs/umn/evs_faq_0042.html new file mode 100644 index 000000000..7b13ed42d --- /dev/null +++ b/docs/evs/umn/evs_faq_0042.html @@ -0,0 +1,13 @@ + + +

Do I Need to Restart the Server After Expanding the Disk Capacity?

+

An EVS disk can be expanded either in the Available or In-use state. Expanding the disk capacity on the management console enlarges the disk capacity, but you still need to log in to the server and extend the disk partitions and file systems to make that additional space usable. You may need to restart the server during the partition and file system extension. The details are as follows:

+
  • After expanding an In-use disk on the management console, log in to the server and view the disk capacity.
    • If the additional space can be viewed, you can extend the partition and file system and a restart is not required.
    • If the additional space cannot be viewed, the server OS may not be included in the compatibility list. In this case, you should stop and then start the server (do not restart the server). When the additional space can be viewed, extend the partition and file system.
    +
  • After expanding an Available disk on the management console, attach the disk to the server and extend the partition and file system on the server. In this case, a server restart is not required.
+
+
+
+
Parent topic: Capacity Expansion
+
+
+ diff --git a/docs/evs/umn/evs_faq_0043.html b/docs/evs/umn/evs_faq_0043.html new file mode 100644 index 000000000..781e461bd --- /dev/null +++ b/docs/evs/umn/evs_faq_0043.html @@ -0,0 +1,15 @@ + + +

How Can I Add a Data Disk to an Existing Server?

+

Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to the server. If you create data disks after the server creation, you need to attach them manually.

+
  • On a Windows server:
    • If a data disk is created along with the server, you need to log in to the server and initialize the disk. The data disk can be viewed after the initialization succeeds.
    • If a data disk is not created along with the server, you need to create a data disk and attach it to the server. Then, you can log in to the server and initialize the disk. The data disk will be visible after the initialization succeeds.
    +
  • On a Linux server:
    • If a data disk is created along with the server, you need to log in to the server and initialize the disk. The data disk can be viewed after the initialization succeeds and the disk has been mounted via the mount command.
    • If a data disk is not created along with the server, you need to create a data disk and attach it to the server. Then, you can log in to the server and initialize the disk. The data disk will be visible after the initialization succeeds and the disk has been mounted via the mount command.
    +
+

For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

+
+
+
+
Parent topic: Attachment
+
+
+ diff --git a/docs/evs/umn/evs_faq_0048.html b/docs/evs/umn/evs_faq_0048.html new file mode 100644 index 000000000..c9e5059e7 --- /dev/null +++ b/docs/evs/umn/evs_faq_0048.html @@ -0,0 +1,12 @@ + + +

Can I Change the AZ of My Disk?

+

No.

+

The AZ of a disk cannot be changed after you have created the disk. If you want to change the AZ, delete the disk and create a new one.

+
+
+
+
Parent topic: General
+
+
+ diff --git a/docs/evs/umn/evs_faq_0053.html b/docs/evs/umn/evs_faq_0053.html new file mode 100644 index 000000000..57ffb3ab4 --- /dev/null +++ b/docs/evs/umn/evs_faq_0053.html @@ -0,0 +1,132 @@ + + +

How Can I View My Disk Usage?

+

You can view your disk usages in either of the following ways:

+ +

Install Agent to View Disk Usage

Some disk monitoring metrics require that the agent to be installed.

+
  • For instructions about how to install the agent on a Windows ECS, see "Installing and Configuring the Agent (Windows)" in the Cloud Eye User Guide.
  • For instructions about how to install the agent on a Linux ECS, see "Installing and Configuring the Agent (Linux)" in the Cloud Eye User Guide.
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Disk metrics

Metric

+

Parameter

+

Description

+

Value Range

+

Monitored Object

+

Monitoring Period (Raw Data)

+

mountPointPrefix_disk_free

+

(Agent) Available Disk Space

+

Free space on the disks

+

Unit: GB

+
  • Linux: Run the df -h command to check the value in the Avail column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
  • Windows: Use the WMI interface to call GetDiskFreeSpaceExW API to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
+

≥ 0

+

ECS

+

1 minute

+

mountPointPrefix_disk_total

+

(Agent) Disk Storage Capacity

+

Total space on the disks, including used and free

+

Unit: GB

+
  • Linux: Run the df -h command to check the value in the Size column.

    The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).

    +
  • Windows: Use the WMI interface to call GetDiskFreeSpaceExW API to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
+

≥ 0

+

ECS

+

1 minute

+

mountPointPrefix_disk_used

+

(Agent) Used Disk Space

+

Used space on the disks

+

Unit: GB

+
  • Linux: Run the df -h command to check the value in the Used column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
  • Windows: Use the WMI interface to call GetDiskFreeSpaceExW API to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
+

≥ 0

+

ECS

+

1 minute

+

mountPointPrefix_disk_usedPercent

+

(Agent) Disk Usage

+

Percentage of total disk space that is used, which is calculated as follows: Disk Usage = Used Disk Space/Disk Storage Capacity

+

Unit: percent

+
  • Linux: It is calculated as follows: Used/Size. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
  • Windows: Use the WMI interface to call GetDiskFreeSpaceExW API to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
+

0-100

+

ECS

+

1 minute

+
+
+
+

Windows Server 2008

In this section, Windows Server 2008 R2 Enterprise 64bit is used as an example.

+
  1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

    The Server Manager window is displayed.

    +

  2. In the navigation tree on the left, choose Storage > Disk Management.

    The sizes and available spaces of the volumes on the current disk are displayed in the middle pane.

    +
    Figure 1 Disk Management page
    +

+
+

Windows Server 2016

In this section, Windows Server 2016 Standard 64bit is used as an example.

+
  1. On the desktop of the server, click the start icon in the lower left corner.

    The Windows Server window is displayed.

    +

  2. Click Server Manager.

    The Server Manager window is displayed.

    +
    Figure 2 Server Manager page
    +

  3. In the upper right corner, choose Tools > Computer Management.
  4. Choose Storage > Disk Management.

    In the middle pane, you can view the sizes and available spaces of the volumes on the disk.

    +
    Figure 3 Disk list page
    +

+
+

Linux

In this section, CentOS 7.4 64bit is used as an example. The details depend on if you need to view the available space or not.

+
  • To query the total capacity only, run lsblk.
    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# lsblk
+NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+vda    253:0    0   40G  0 disk
+└─vda1 253:1    0   40G  0 part /
+vdb    253:16   0   40G  0 disk
+└─vdb1 253:17   0   40G  0 part
    +
    +

    In the command output, the server has two disks, /dev/vda and /dev/vdb. System disk /dev/vda has 40 GB of capacity, as does data disk /dev/vdb.

    +
  • To query the total capacity and display the space available as well, run df -TH. Ensure that the disk has been attached and initialized before running this command.

    Information similar to the following is displayed:

    +
    [root@ecs-0001 ~]# df -TH
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/vda1      ext4       43G  2.0G   39G   5% /
+devtmpfs       devtmpfs  509M     0  509M   0% /dev
+tmpfs          tmpfs     520M     0  520M   0% /dev/shm
+tmpfs          tmpfs     520M  7.2M  513M   2% /run
+tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
+tmpfs          tmpfs     104M     0  104M   0% /run/user/0
+/dev/vdb1      ext4       43G   51M   40G   1% /mnt/sdc
    +

    In the command output, the server has two partitions, /dev/vda1 and /dev/vdb1. Partition /dev/vda1 is used to deploy the OS, and its total capacity, used capacity, and available capacity are 43 GB, 2 GB, and 39 GB, respectively. Partition /dev/vdb1's total capacity, used capacity, and available capacity are 43 GB, 51 MB, and 40 GB, respectively.

    +
+
+
+
+
+
Parent topic: Capacity
+
+
+ diff --git a/docs/evs/umn/evs_faq_0054.html b/docs/evs/umn/evs_faq_0054.html new file mode 100644 index 000000000..8d562a667 --- /dev/null +++ b/docs/evs/umn/evs_faq_0054.html @@ -0,0 +1,12 @@ + + +

Can EVS Disks Be Used Alone?

+

No.

+

EVS disks must be attached to servers before you can use them.

+
+
+
+
Parent topic: General
+
+
+ diff --git a/docs/evs/umn/evs_faq_0056.html b/docs/evs/umn/evs_faq_0056.html new file mode 100644 index 000000000..58691b201 --- /dev/null +++ b/docs/evs/umn/evs_faq_0056.html @@ -0,0 +1,17 @@ + + +

Why Can't I Detach My Disk?

+

EVS disks can be used as system disks or data disks, but the way you detach each one is different.

+
  • System disks: A system disk can only be detached offline. You must first stop the server that uses this system disk and then detach the disk.

    In Linux, a system disk is typically mounted on /dev/vda. In Windows, a system disk is normally Volume (C:).

    +
    +
  • Data disks: A data disk can be detached regardless of whether it is offline or online.

    In Linux, a data disk is typically mounted on a mount point other than /dev/vda. In Windows, a data disk is normally a volume other than Volume (C:).

    +
    +
    • Offline: The server must be in the Stopped state. If it is not, stop the server and then detach the data disk.
    • Online: Some OSs support online detachment. In this case, you do not need to stop the server before detaching the data disk. For more information, see Storage > Detaching an EVS Disk from a Running ECS in the Elastic Cloud Server User Guide.
    +
+
+
+
+
Parent topic: Detachment
+
+
+ diff --git a/docs/evs/umn/public_sys-resources/ExpandCollapse.js b/docs/evs/umn/public_sys-resources/ExpandCollapse.js new file mode 100644 index 000000000..3f1b7db00 --- /dev/null +++ b/docs/evs/umn/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";var href="";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(href.substring(href.lastIndexOf("#")+1))}}catch(a){}}; \ No newline at end of file diff --git a/docs/evs/umn/public_sys-resources/caution_3.0-en-us.png b/docs/evs/umn/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 000000000..60f607621 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/evs/umn/public_sys-resources/commonltr.css b/docs/evs/umn/public_sys-resources/commonltr.css new file mode 100644 index 000000000..c5480b0ab --- /dev/null +++ b/docs/evs/umn/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/evs/umn/public_sys-resources/commonltr_print.css b/docs/evs/umn/public_sys-resources/commonltr_print.css new file mode 100644 index 000000000..a59823141 --- /dev/null +++ b/docs/evs/umn/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/evs/umn/public_sys-resources/commonrtl.css b/docs/evs/umn/public_sys-resources/commonrtl.css new file mode 100644 index 000000000..947a9a033 --- /dev/null +++ b/docs/evs/umn/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/evs/umn/public_sys-resources/danger_3.0-en-us.png b/docs/evs/umn/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 000000000..47a9c7235 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/evs/umn/public_sys-resources/delta.gif b/docs/evs/umn/public_sys-resources/delta.gif new file mode 100644 index 000000000..0d1b1f674 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/delta.gif differ diff --git a/docs/evs/umn/public_sys-resources/deltaend.gif b/docs/evs/umn/public_sys-resources/deltaend.gif new file mode 100644 index 000000000..cc7da0fc8 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/deltaend.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-arrowdn.gif b/docs/evs/umn/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 000000000..84eec9be2 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-arrowrt.gif b/docs/evs/umn/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 000000000..39583d168 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-caution.gif b/docs/evs/umn/public_sys-resources/icon-caution.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-caution.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-danger.gif b/docs/evs/umn/public_sys-resources/icon-danger.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-danger.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-huawei.gif b/docs/evs/umn/public_sys-resources/icon-huawei.gif new file mode 100644 index 000000000..a31d60f89 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-huawei.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-note.gif b/docs/evs/umn/public_sys-resources/icon-note.gif new file mode 100644 index 000000000..31be2b039 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-note.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-notice.gif b/docs/evs/umn/public_sys-resources/icon-notice.gif new file mode 100644 index 000000000..409070650 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-notice.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-tip.gif b/docs/evs/umn/public_sys-resources/icon-tip.gif new file mode 100644 index 000000000..c47bae05c Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-tip.gif differ diff --git a/docs/evs/umn/public_sys-resources/icon-warning.gif b/docs/evs/umn/public_sys-resources/icon-warning.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/icon-warning.gif differ diff --git a/docs/evs/umn/public_sys-resources/note_3.0-en-us.png b/docs/evs/umn/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 000000000..57a0e1f53 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/note_3.0-en-us.png differ diff --git a/docs/evs/umn/public_sys-resources/notice_3.0-en-us.png b/docs/evs/umn/public_sys-resources/notice_3.0-en-us.png new file mode 100644 index 000000000..fa4b64990 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/notice_3.0-en-us.png differ diff --git a/docs/evs/umn/public_sys-resources/popup.js b/docs/evs/umn/public_sys-resources/popup.js new file mode 100644 index 000000000..a550862ed --- /dev/null +++ b/docs/evs/umn/public_sys-resources/popup.js @@ -0,0 +1 @@ +var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/evs/umn/public_sys-resources/warning_3.0-en-us.png b/docs/evs/umn/public_sys-resources/warning_3.0-en-us.png new file mode 100644 index 000000000..def5c3565 Binary files /dev/null and b/docs/evs/umn/public_sys-resources/warning_3.0-en-us.png differ