vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Use scheduled scaling for VPC to schedule actions that automatically add or remove instance group capacity, based on daily, intermittent, or seasonal demand. You can create multiple scheduled actions that scale capacity monthly, weekly, daily, hourly, or even every set number of minutes. Explore the instance group [managers methods](https://cloud.ibm.com/apidocs/vpclist-instance-group-managers) and the new [manager actions methods](https://cloud.ibm.com/apidocs/vpclist-instance-group-manager-actions).







 30 March 2021 



 For all version dates 

Instance storage. New instance profiles can now optionally include a set of solid state disks. These instance storage disks provide temporary storage to improve the performance of cloud-native workloads that need scratch space, large data caches, or data replicated across availability zones.

The following API methods have been added:



* [List all disks on an instance](https://cloud.ibm.com/apidocs/vpclist-instance-disks) (GET /instances/{instance_id}/disks)
* [Retrieve an instance disk](https://cloud.ibm.com/apidocs/vpcget-instance-disk) (GET /instances/{instance_id}/disks/{id})
* [Update an instance disk](https://cloud.ibm.com/apidocs/vpcupdate-instance-disk) (PATCH /instances/{instance_id}/disks/{id})
* [List all disks on a dedicated host](https://cloud.ibm.com/apidocs/vpclist-dedicated-host-disks) (GET /dedicated_hosts/{dedicated_host_id}/disks)
* [Retrieve a dedicated host disk](https://cloud.ibm.com/apidocs/vpcget-dedicated-host-disk) (GET /dedicated_hosts/{dedicated_host_id}/disks/{id})
VPC flavors 

Review the VPC Gen 2 worker node flavors by metro.



 au-syd 



Table 1. Worker node flavors for Australia.

 Name Memory Network speed Cores Type OS Primary storage Secondary storage Secondary storage options 

 bx2.16x64 64GB 24Gbps 16 Virtual REDHAT_7_64 (default), REDHAT_8_64 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier, 2400gb.10iops-tier, 3000gb.10iops-tier, 4000gb.10iops-tier 
 bx2.2x8 8GB 4Gbps 2 Virtual REDHAT_7_64 (default), REDHAT_8_64 100GB BLOCK N/A N/A 
 bx2.32x128 128GB 25Gbps 32 Virtual REDHAT_7_64 (default), REDHAT_8_64 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier, 2400gb.10iops-tier, 3000gb.10iops-tier, 4000gb.10iops-tier 
 bx2.48x192 192GB 25Gbps 48 Virtual REDHAT_7_64 (default), REDHAT_8_64 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier, 2400gb.10iops-tier, 3000gb.10iops-tier, 4000gb.10iops-tier 
 bx2.4x16 16GB 8Gbps 4 Virtual REDHAT_7_64 (default), REDHAT_8_64 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
storageclass.beta.kubernetes.io/is-default-class: "true"
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-10iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 10iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-5iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
: Include the CRN ID of a standard IBM Cloud Object Storage instance to back up the internal registry of your cluster. To list the CRN of existing instances, run ibmcloud resource service-instances --long and find the ID of your object storage instance. To create a standard object storage instance, run ibmcloud resource service-instance-create <name> cloud-object-storage standard global and note its ID.

--workers <number>
: Specify at least 2 worker nodes to include in the cluster. For more information, see [What is the smallest size cluster that I can make?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqssmallest_cluster). This value is optional.

--operating-system SYSTEM
: Optional. The operating system of the worker nodes you want to provision in your cluster. For a list of available operating systems by cluster version, see [Red Hat OpenShift on IBM Cloud version information](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).
: If no option is specified, the default [operating system version that corresponds to the cluster version is used.

--cluster-security-group <group_ID>
: Optional. Specify additional security group IDs to apply to all workers on the cluster. You must include a separate --cluster-security-group option for each individual security group you want to add. To apply the IBM-created kube-clusterID, use --cluster-security-group cluster. If no value is specified, only the kube-clusterID and the default VPC security group are applied. A maximum of five security groups can be applied to workers, including the default security groups. Note that the VPC security group is only applied if no other security groups are specified. For more information, see [Adding VPC security groups to clusters and worker pools during create time](https://cloud.ibm.com/docs/containers?topic=containers-vpc-security-groupvpc-sg-cluster).
VPC: Setting up authorized IP addresses for IBM Cloud Object Storage 

Virtual Private Cloud

You can authorize your VPC Cloud Service Endpoint source IP addresses to access your IBM Cloud Object Storage bucket. When you set up authorized IP addresses, you can only access your bucket data from those IP addresses; for example, in an app pod.

Minimum required permissions
: Manager service access role for the Red Hat OpenShift on IBM Cloud service.
: Writer service access role for the IBM Cloud Object Storage service.



1. [Follow the instructions to install the ibmc Helm plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_install). Make sure to install the ibm-object-storage-plugin and set the bucketAccessPolicy option to true.
2. Create one Manager HMAC service credential and one Writer HMAC service credential for your IBM Cloud Object Storage instance.



* [Creating HMAC credentials from the console](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main).
* [Creating HMAC credentials from the CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-mainuhc-create-hmac-credentials-cli).



3. Encode the apikey from your IBM Cloud Object Storage Manager credentials to base64.

echo -n "<cos_manager_apikey>" | base64
4. Encode the access-key and secret-key from your IBM Cloud Object Storage Writer credentials to base64.

echo -n "<cos_writer_access-key>" | base64
echo -n "<cos_writer_secret-key>" | base64
5. Create a secret configuration file with the values that you encoded. For the access-key and secret-key, enter the base64 encoded access-key and secret-key from the Writer HMAC credentials that you created.
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-5iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
[10-39]GiB:[100-1000]
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
VPC flavors 

Review the VPC Gen 2 worker node flavors by metro.



 au-syd 



Table 1. Worker node flavors for Australia.

 Name Memory Network speed Cores Type OS Primary storage Secondary storage Secondary storage options 

 bx2.16x64 64GB 24Gbps 16 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier, 2400gb.10iops-tier, 3000gb.10iops-tier, 4000gb.10iops-tier 
 bx2.2x8 8GB 4Gbps 2 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 100GB BLOCK N/A N/A 
 bx2.32x128 128GB 25Gbps 32 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier, 2400gb.10iops-tier, 3000gb.10iops-tier, 4000gb.10iops-tier 
 bx2.48x192 192GB 25Gbps 48 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier, 2400gb.10iops-tier, 3000gb.10iops-tier, 4000gb.10iops-tier 
 bx2.4x16 16GB 8Gbps 4 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 100GB BLOCK N/A 900gb.5iops-tier, 1200gb.5iops-tier, 1600gb.5iops-tier
* Memory - Memory profiles are best for memory intensive workloads, such as database applications, and have a ratio 8 GiB of memory for every 1 vCPU of compute.



Online Transactional Processing (OLTP) typically involves inserting, updating, deleting small amounts of data in a database by large numbers of transactions by a large number of users. A recommended minimum for a production MS SQL OLTP environment is 4 vCore with 32 GB of memory from the Memory profile family, mx2-4x32. For larger requirements, the [Memory profile](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesmemory) extends up to the mx2-128x1024 which has 128vCPU, 1024 GiB RAM and a 80 Gbps network bandwidth cap.

SQL Server data warehouse environments often require greater memory to vCPU requirements than 8:1, therefore, you may have to over provision on vCPU to satisfy the memory requirements.

The Memory profile family includes profiles that are provisioned with instance storage. [Instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage) provides solid state drives directly attached to the virtual server instance when the instance is provisioned. Instance storage disk provides fast, temporary storage to improve performance of many workloads including transactional processing.





 Storage 

When planning your SQL Server on IBM Cloud VPC, there are three storage components to consider; boot volumes, data volumes and instance storage.



* Boot volumes - When virtual server is created, a 100 GB, 3 IOPS/GB boot volume is created from block storage and attached to the instance. By default, boot volumes are encrypted by IBM-managed encryption, however, customer-managed encryption is an option. Boot volumes can not be detached, deleted or increased or reduced in size. Boot volumes are always deleted when the virtual server is deleted. Boot volumes contain the operating system files.
* Data volumes - Data volumes leverage block storage for VPC and provides hypervisor-mounted, high-performance data storage that is stored redundantly across multiple physical disks in an Availability Zone (AZ) to prevent data loss due to failure of any single component.
Example output.

Name: ocscluster-vpc
Namespace:
Labels: <none>
Annotations: <none>
API Version: ocs.ibm.io/v1
Kind: OcsCluster
Metadata:
Creation Timestamp: 2021-03-23T20:56:51Z
Finalizers:
finalizer.ocs.ibm.io
Generation: 1
Managed Fields:
API Version: ocs.ibm.io/v1
Fields Type: FieldsV1
fieldsV1:
f:spec:
.:
f:billingType:
f:monSize:
f:monStorageClassName:
f:numOfOsd:
f:ocsUpgrade:
f:osdSize:
f:osdStorageClassName:
Manager: oc
Operation: Update
Time: 2021-03-23T20:56:51Z
API Version: ocs.ibm.io/v1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:finalizers:
.:
v:"finalizer.ocs.ibm.io":
f:status:
.:
f:storageClusterStatus:
Manager: manager
Operation: Update
Time: 2021-04-09T23:12:02Z
Resource Version: 11372332
Self Link: /apis/ocs.ibm.io/v1/ocsclusters/ocscluster-vpc
UID: aa11a1a1-111f-aace-afac-1fa1afe1111a
Spec:
Billing Type: hourly
Mon Size: 20Gi
Mon Storage Class Name: ibmc-vpc-block-10iops-tier
Num Of Osd: 1
Ocs Upgrade: false
Osd Size: 100Gi
Osd Storage Class Name: ibmc-vpc-block-10iops-tier
Status:
Storage Cluster Status:
To create an Object Storage bucket, see the [IBM Cloud Object Storage](https://cloud.ibm.com/catalog/services/cloud-object-storage) ordering page.

The Object Storage bucket must be a single-region bucket in the same region as the target resource. Additionally, it is recommended that you secure the bucket through IAM access groups and audit logging.
3. Authorize resources of type Flow Logs for VPC to use the Object Storage instance created in Step 2.

To do so, use the following steps:



* In the IBM Cloud console, click Manage > Access (IAM), then select Authorizations from the navigation pane.
* Click Create and complete the following information:

For Source service:



* Select VPC Infrastructure Services.
* Select Resources based on selected attributes.
* For Resource type, select Flow Logs for VPC.
* For Source service instance, select All instances.



For Target service:



* Select Cloud Object Storage.
* Select Resources based on selected attributes.
* For Service instance, select string equals > All instances.



For Service access, select the Writer role to assign access to the source service that accesses the target service.
* Click Authorize.



For more information, see [Using authorizations to grant access between services](https://cloud.ibm.com/docs/account?topic=account-serviceauthcreate-auth).







 Prerequisites from the CLI 

Before you create a flow log collector, make sure that you meet the following prerequisites:



1. Make sure that at least one VPC, a subnet, and a virtual server instance exist. For instructions, see [Creating a VPC and subnet](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolecreating-a-vpc-and-subnet) and [Creating a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolecreating-a-vsi).
2.
On the Block Storage for VPC provisioning page, enter the required information to define the new volume (see Table 2).



Table 2. Values for defining a Block Storage for VPC volume

 Field Value 

 Location The geography, region, and zone are inherited from the VPC (for example, North America, Dallas, Dallas-1). You can select a different zone in your location from the menu by clicking the pencil icon. 
 Name Specify a meaningful name for your volume. For example, provide a name that describes your compute or workload function. The volume name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. Volume names must be unique across the entire VPC infrastructure. You can later edit the name. 
 Resource Group Specify a [resource group](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-startedresources-and-resource-groups). 
 Tags Specify [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-user-tags) to organize your resources and for use by [backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about). 
 Access management tags Specify [access management tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-mgt-tags) that were created in IAM to help you manage access to your volumes. 
 Snapshot Optionally, click Select snapshot to create the volume with data from the selected snapshot. You can create data volumes with Nonbootable snapshots, and boot volumes with Bootable snapshots. For more information, see [Create a stand-alone Block Storage for VPC volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=uicreate-vol-from-snapshot-ui).
On the Block Storage for VPC provisioning page, enter the required information to define the new volume (see Table 2).



Table 2. Values for defining a Block Storage for VPC volume

 Field Value 

 Location The geography, region, and zone are inherited from the VPC (for example, North America, Dallas, Dallas-1). You can select a different zone in your location from the menu by clicking the pencil icon. 
 Name Specify a meaningful name for your volume. For example, provide a name that describes your compute or workload function. The volume name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. Volume names must be unique across the entire VPC infrastructure. You can later edit the name. 
 Resource Group Specify a [resource group](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-startedresources-and-resource-groups). 
 Tags Specify [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-user-tags) to organize your resources and for use by [backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about). 
 Access management tags Specify [access management tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-mgt-tags) that were created in IAM to help you manage access to your volumes. 
 Snapshot Optionally, click Select snapshot to create the volume with data from the selected snapshot. You can create data volumes with Nonbootable snapshots, and boot volumes with Bootable snapshots. For more information, see [Create a stand-alone Block Storage for VPC volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=clicreate-vol-from-snapshot-ui).
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 10iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-5iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
For more information about VPC tiered storage classes, see the [Block Storage for VPC Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-reference). N/A 
 osdSize Enter a size for your storage devices. Example: 100Gi. The total storage capacity of your ODF cluster is equivalent to the osdSize multiplied by the numOfOsd. N/A 
 numOfOsd Enter the number object storage daemons (OSDs) that you want to create. ODF creates three times the specified number. For example, if you enter 1, ODF creates 3 OSDs. 1 
 billingType Enter a billingType of either essentials or advanced for your OCS deployment. advanced 
 ocsUpgrade Enter a true or false to upgrade the major version of your ODF deployment. false 
 workerNodes Optional: Enter the names of the worker nodes that you want to use for your ODF deployment. Don't specify this parameter if you want to use all the worker nodes in your cluster. To retrieve your worker node name, run the oc get nodes command. N/A 
 clusterEncryption Available for add-on version 4.7.0 and later. Enter true or false to enable encryption. 
 autoDiscoverDevices Optional: Automatically discover the available disks on your worker nodes. Enter true or false. 
 hpcsServiceName Enter the name of your Hyper Protect Crypto Services or Key Protect instance. For example: Hyper-Protect-Crypto-Services-eugb. false 
 hpcsInstanceId Enter your Hyper Protect Crypto Services or Key Protect instance ID. For example: d11a1a43-aa0a-40a3-aaa9-5aaa63147aaa. false 
 hpcsSecretName Enter the name of the secret that you created by using your Hyper Protect Crypto Services or Key Protect credentials. For example: ibm-hpcs-secret. false
The Ultra High Memory profile offers the highest vCPU to memory ratios with 1 vCPU to 28 GiB of RAM, is hosted exclusively on the Intel® Xeon® Platinum Cascade Lake server, and includes instance storage for temporary swap space or cache 



Profiles with AMD manufactured processors are available in the Toronto region.



 Balanced 

The Balanced profile provides a good mix of performance and scalability for more common workloads.

The Balanced with instance storage profile provides a good mix of performance and scalability for more common workloads. The Balanced with instance storage profile provisions your host with the capability for hosting instances that include [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage). If you provision a dedicated host with a Balanced with instance storage profile, any virtual server instances that are provisioned on the dedicated host must also be provisioned with a Balanced profile that includes instance storage. Profiles with instance storage include d in the profile name, for example bx2d.

The Balanced profile family of dedicated hosts on Intel® x86-64 systems are deployed on either Intel®'s quad processor Xeon® Platinum 8260 Cascade Lake with 96 cores that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz or Intel®'s quad processor Xeon® Gold 6248 Cascade Lake with 80 cores that are running at a base speed of 2.5 GHz and an all-core turbo frequency of 3.1 GHz.

The following Balanced profiles are available for dedicated hosts.

Intel x86-64

AMD x86-64



Table 2. Intel x86-64 balanced profile for dedicated hosts
Dedicated Host Balanced profiles options for Intel® x86-64 virtual server instances.

 Dedicated host profile vCPU Cores GiB RAM Instance storage 

 bx2-host-152x608 152 76 608 <br><br> * <br><br><br> 
 bx2d-host-152x608 152 76 608 5700 GB 



For supported instance profiles in the Balanced family, see [balanced profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesbalanced).
* [Manage file share user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfs-add-tags-api).



To see information about the File Storage for VPC API methods, see the following section in the [API reference](https://cloud.ibm.com/apidocs/vpc-betalist-share-profiles).

File Storage for VPC regional API is available for customers with special approval to preview this feature.



 Rename a file share in the API 

Make a PATCH /shares/$share_id call to rename a specific file share. See the following example.

curl -X PATCH "$vpc_api_endpoint/v1/shares/$share_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer ${API_TOKEN}" -d '{
"name": "share-renamed1"
}'

A successful response looks like the following example.

{
"access_control_mode": "vpc",
"created_at": "2023-03-30T23:31:59Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"id": "0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"iops": 3000,
"lifecycle_state": "stable",
"name": "share-renamed1",
"profile": {
"href": "$vpc_api_endpoint/v1/share/profiles/tier-10iops",
"name": "tier-10iops",
"resource_type": "share_profile"
},