vania-janet/multiturn-rag-retrieval-data huggingface dataset:
A GET request on a resource URL returns the canonical resource representation, PATCH updates a resource, PUT replaces a resource, and DELETE deletes a resource.



The schemas for request payloads to create and mutate resources SHOULD be consistent with the canonical representation of the resource returned by a GET on the resource URL and MUST NOT differ arbitrarily. Often, schemas for resource creation and mutation MAY represent a subset of the properties in a resource's canonical representation, omitting properties that are system-defined or immutable.

For example, consider a resource's canonical representation:

GET /keys/b34f2d29-25ff-40ac-8762-78bad7e3eea9
---
{
"id": "b34f2d29-25ff-40ac-8762-78bad7e3eea9",
"href": "https://service.example.com/keys/b34f2d29-25ff-40ac-8762-78bad7e3eea9",
"name": "my-key",
"value": "VGhlcmUgd2FzIG5vIHBvc3NpYmlsaXR5IG9mIHRha2luZyBhIHdhbGsgdGhhdCBkYXkuIFdlIGhhZCBiZWVuIHdhbmRlcmluZywgaW5kZWVkLCBpbiB0aGUgbGVhZmxlc3Mgc2hydWJiZXJ5IGFuIGhvdXIgaW4gdGhlIG1vcm5pbmc7IGJ1dCBzaW5jZSBkaW5uZXIgKE1ycy4gUmVlZCwgd2hlbiB0aGVyZSB3YXMgbm8gY29tcGFueSwgZGluZWQgZWFybHkpIHRoZSBjb2xkIHdpbnRlciB3aW5kIGhhZCBicm91Z2h0IHdpdGggaXQgY2xvdWRzIHNvIHNvbWJyZSwgYW5kIGEgcmFpbiBzbyBwZW5ldHJhdGluZywgdGhhdCBmdXJ0aGVyIG91dGRvb3IgZXhlcmNpc2Ugd2FzIG5vdyBvdXQgb2YgdGhlIHF1ZXN0aW9uLg=="
}

In such a resource type, id and href might be considered to be system-defined and thus omitted from the request schemas for POST /keys and PATCH /keys/{id}. Further, the key's value could be considered immutable, and thus be included in the request schema for POST /keys but omitted from the request schema for PATCH /keys/{id}.

Properties that are included in such schemas MUST be defined consistently with a resource's canonical representation. For example, a PATCH request to change the name for the key in the previous example would look like:

PATCH /keys/b34f2d29-25ff-40ac-8762-78bad7e3eea9
{
"name": "my-renamed-key"
}

... and MUST NOT look like:

PATCH /keys/b34f2d29-25ff-40ac-8762-78bad7e3eea9
{
Identifying LUNs 

Various reasons exist for why you would want to look up the LUN ID of the attached storage volumes on the Compute host. For example, you might have multiple storage devices that are mounted on the same host with the same volume sizes. You want to detach and decommission one of them. However, you are not sure how to correlate what you see on your Linux® host with what you see in the console. Another example might be that you have multiple Block Storage for Classic volumes that are attached to an esxi server. You want to expand the volume size of one of the LUNs, and you need to know the correct LUN ID of the storage to do that.



 Viewing the LUN ID in Linux® 



1. In the command line, run multipath -ll and look at the output.

root@server: multipath -l
3600a098038303845372b4a5232346e35 dm-0 NETAPP ,LUN C-Mode
size=12T features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='1 alua' wp=rw
-+- policy='round-robin 0' prio=50 status=active
- 1:0:0:0 sdc 8:32 active ready running
3600a098038304471562b4c4743384332 dm-1 NETAPP ,LUN C-Mode
size=12T features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='1 alua' wp=rw
-+- policy='round-robin 0' prio=10 status=active
- 3:0:0:1 sdd 8:48 active ready running

Note "1:0:0:0" and "3:0:0:1".
: Sophisticated AI-driven knowledge search system at the customer site and data processing where the data resides, eliminating the need to move data to cloud. Data is processed where the data resides, eliminating the need to move data to cloud.







 Manufacturing use cases for Satellite 

These use cases are applicable to the manufacturing industry.



 Internet of things (IoT) service platform 

An IoT service platform can be delivered on cloud or on-premises to meet the user’s (manufacturing plants) requirements. The IoT service platform can be distributed, managed, and controlled remotely for users (manufacturing plants) that are restricted from connecting to and using cloud.

Pain points:
: For plants with stringent security network requirements, it is impossible to deliver IoT services in the same way as cloud. For these plants, services must be built separately.

Satellite enables:
: IoT service platform that was previously only available on cloud to be deployed within the customer’s plant, benefiting from use of cloud-like services.





 Enabling the digital transformation of on-premises legacy systems at steel mills and other manufacturing plants 

Use of Satellite enables legacy host systems at each site to run on digital transformation service platforms built on containers through integration, with the added benefit of driving digital transformation at the isolated sites that have so far missed out on the advantages of cloud and container technology.

Pain points:
: Systems with strict on-premises requirements, such as z/HOST and sensitive data, prevent the move to cloud. Many applications cannot tolerate network latency. Lack of container skills in on-premises environment hampers digital transformation of site applications.

Satellite enables:
: Digital transformation service platform built on containers that was previously only available on cloud can now be deployed within the plant. It also enabled the delivery of cloud-like quality control, such as image analysis, and data lake related services at the plant.





 Establishing a service platform for point of sale (POS) or multi function printer (MFP) systems 

When providing platform-based management services and data services to store POS systems nationwide as well as MFP systems in corporate offices, it can be difficult to integrate with these customer systems. Using Satellite enables platform services to be delivered to a site that meets customer requirements.

Pain points:
For example, if you want to decrease the size of your dedicated host group, you can stop instances on one of the hosts and disable placement for the host that you want to decommission. Then, when you restart the instances they are started on another host in the group if capacity is available.





 How much instance storage is available on my dedicated host? 

In IBM Cloud console, if you look at the details page of a dedicated host that was provisioned with an instance storage profile, you see 6.4 TBs of instance storage. The description of the dedicated host shows 5.7 TBs. Because of the way virtual server instances and their associated profiles are packed on dedicated hosts, the most instance storage you can use on a dedicated host is 5.7 TBs. You are charged for 5.7 TBs of instance storage.





 What happens if my dedicated host fails? 

In case of a hardware failure, the dedicated host and the instances that are running on it are migrated to a new hardware node.

If a host hardware failure occurs, the instances that you initially provisioned to a dedicate host group might be migrated to another existing dedicated host in the group if capacity is available.

For more information, see [Viewing notifications](https://cloud.ibm.com/docs/get-support?topic=get-support-viewing-notifications) and [Host failure recovery policies](https://cloud.ibm.com/docs/vpc?topic=vpc-host-failure-recovery-policies&interface=ui).
While the vCenter Server instances enable the use of Software-Defined Networking (SDN), network overlays created within a VMware instance that include routing to internal subnets are not known by the IBM Cloud managed routers.

If you want to route between the overlay and underlay, you must deploy an IBM firewall device for the particular default private VLAN when the vCenter Server instance is deployed. This device allows the insertion of static routes and dynamic routing protocol peering with the overlay networking devices to allow routing between the underlay and overlay.

The private network connections are configured to use a jumbo frame MTU size of 9000 to improve performance for large data transfers, such as storage and vMotion. This value is the maximum MTU that is allowed within VMware and by IBM Cloud. The public network connections use a standard Ethernet MTU of 1500. This value must be maintained as any changes might cause packet fragmentation over the internet.









 Physical storage design 

Physical storage design consists of the configuration of the physical disks that are installed in the physical hosts and the configuration of the shared network-attached storage. This storage includes the operating system (vSphere ESXi) and the disks that are used for storage of the VMs. Storage for VMs can consist of local disks that are virtualized by VMware vSAN, shared file–level storage, or shared block-level storage.



 Operating system disks 

The vSphere ESXi hypervisor is installed in a persistent location. As a result, the physical hosts are consist of two disks in a RAID 1 configuration to support redundancy for the vSphere ESXi hypervisor.





 vSAN disks 

This design allows for the option of using either VMware vSAN or shared network-attached storage as the primary datastore for VMs. For VMware vSAN, it is configured by using an all–flash configuration. This design allows for several configuration options, including 2U and 4U chassis, various numbers of disks, and various disk sizes. All configurations use two vSAN disk groups, with one solid-state disk (SSD) for cache and one or more SSDs for capacity. All drives that are allocated for vSAN consumption are configured in single-disk RAID 0.
If enabled, logs are sent to syslog and you can [forward the logs to an external logging server](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging). By default, all storage classes are set to false to disable this logging feature.

ibm.io/debug-level
: The logging level that is set by the IBM Cloud Object Storage plug-in. All storage classes are set up with the WARN logging level.

ibm.io/iam-endpoint
: The API endpoint for IBM Cloud Identity and Access Management (IAM).

ibm.io/kernel-cache
: Enable or disable the kernel buffer cache for the volume mount point. If enabled, data that is read from IBM Cloud Object Storage is stored in the kernel cache to ensure fast read access to your data. If disabled, data is not cached and always read from IBM Cloud Object Storage. Kernel cache is enabled for standard and flex storage classes, and disabled for cold and vault storage classes.

ibm.io/multireq-max
: The maximum number of parallel requests that can be sent to the IBM Cloud Object Storage service instance to list files in a single directory. All storage classes are set up with a maximum of 20 parallel requests.

ibm.io/object-store-endpoint
: The API endpoint to use to access the bucket in your IBM Cloud Object Storage service instance. The endpoint is automatically set based on the region of your cluster. If you want to access an existing bucket that is located in a different region than the one where your cluster is in, you must create a custom storage class and use the API endpoint for your bucket.

ibm.io/object-store-storage-class
: The name of the storage class.

ibm.io/parallel-count
: The maximum number of parallel requests that can be sent to the IBM Cloud Object Storage service instance for a single read or write operation. Storage classes with perf in their name are set up with a maximum of 20 parallel requests. Storage classes without perf are set up with two parallel requests by default.

ibm.io/s3fs-fuse-retry-count
This value is computed when you link to an existing repo. 
 private_repo optional, immutable, Default: true Boolean private_repo Set this value to true to make the repo private when you create a repo, or when you clone or fork a repo. This parameter is not used when you link to an existing repo. 
 repo_id optional, immutable String repo_id The ID of the Git Repos and Issue Tracking project. 
 repo_name optional, immutable String repo_name The name of the Git Repos and Issue Tracking repo to create. This parameter is required when you create a repo, or clone or fork a repo. This value is computed when you link to to an existing repo. 
 repo_url optional, immutable String repo_url The URL of the Git Repos and Issue Tracking repo for this tool integration. This parameter is required when you link to an existing repo. This value is computed when you create a repo, or clone or fork a repo. 
 source_repo_url optional, immutable String source_repo_url The URL of the repo that you want to fork or clone. This parameter is required when you fork or clone a repo, but it is not used when you create a repo or link to an existing repo. 
 token_url optional, updatable String token_url The token URL that is used to authorize with the Git Repos and Issue Tracking server. 
 type required, immutable String type The operation to perform to initialize the new tool integration. Use new to create a Git repo, clone to clone an existing Git repo into a new Git repo, fork to fork an existing Git repo, or link to link to an existing Git repo. 







 Learn more about Git Repos and Issue Tracking
2. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg).
3. Select Delete Replica.
4. Select when to cancel. Choose Immediately or Anniversary Date, and click Continue.
5. This operation deletes the replica volume with all its data. Click the checkbox to acknowledge information, and click Delete.







 Canceling replication when the primary volume is deleted in the UI 

When a primary volume is canceled, the replication schedule and the volume in the replica data center are deleted. Replicas are canceled from the Block Storage for Classic page.

You can expect the volume to remain visible in your Storage list for at least 24 hours (immediate cancellation) or until the anniversary date. Certain features aren't going to be available any longer, but the volume remains visible until it is reclaimed. However, billing is stopped immediately after you click Delete/Cancel Replica.

Active replicas can block reclamation of the Storage volume. Make sure that the volume is no longer mounted, host authorizations are revoked, and replication is canceled before you attempt to cancel the original volume.





 Creating a duplicate of a replica 

You can create a duplicate of an existing IBM Cloud® Block Storage for Classic. The duplicate volume inherits the capacity and performance options of the original volume by default and has a copy of the data up to the point-in-time of a snapshot.

Duplicates can be created from both primary and replica volumes. The new duplicate is created in the same data center as the original volume. If you create a duplicate from a replica volume, the new volume is created in the same data center as the replica volume.

Duplicate volumes can be accessed by a host for read/write as soon as the storage is provisioned. However, snapshots and replication aren't allowed until the data copy from the original to the duplicate is complete.
This field defines the Cloud Resoiurce Name (CRN) of the resource on which the action is requested. For more information about the CRN format, see [Cloud Resource Names](https://cloud.ibm.com/docs/account?topic=account-crn).





 message (string) 

This field is set to the human-readable description of the event.

The format of this field is:

serviceName: {event description} [outcome]

Where



* servicename indicates the name of the service.
* {event description} provides a human-readable version of the what the event is reporting.
* outcome is optional and is only included when the outcome of the request is failure.







 observer.name (string) 

This field is set to the fixed value ActivityTracker.





 outcome (string) 

This field indicates the result of the action.

Valid values are: success, pending, or failure.





 Reason fields 

Reason fields provide information about the outcome of the request.



 reason.reasonCode (numeric) 

This field returns the HTTP response code of the action requested.

For example the reason.reasonCode field is set to:



* 403 to report forbidden access or unauthorized
* 409 to report conflict







 reason.reasonType (string) 

This field provides additional information about the result of the action requested.





 reason.reasonForFailure (string) 

This field provides additional information as to why the action has failed.







 requestData (JSON) 

When the field is available, it includes additional information about the request.

The information that is included in requestData is specific for each type of action. Check the [API documentation](https://cloud.ibm.com/docs?tab=api-docs&) of a request to learn about some of the fields that may be included.





 responseData (JSON) 

When the field is available, it includes additional information about the request.

The information that is included in responseData is specific for each type of action.
This field provides information that you can use to identify where the request originated.







 logSourceCRN (string) 

This field defines the Cloud Resoiurce Name (CRN) of the resource on which the action is requested. For more information about the CRN format, see [Cloud Resource Names](https://cloud.ibm.com/docs/account?topic=account-crn).





 message (string) 

This field is set to the human-readable description of the event.

The format of this field is:

serviceName: {event description} [outcome]

Where



* servicename indicates the name of the service.
* {event description} provides a human-readable version of the what the event is reporting.
* outcome is optional and is only included when the outcome of the request is failure.







 observer.name (string) 

This field is set to the fixed value ActivityTracker.





 outcome (string) 

This field indicates the result of the action.

Valid values are: success, pending, or failure.





 Reason fields 

Reason fields provide information about the outcome of the request.



 reason.reasonCode (numeric) 

This field returns the HTTP response code of the action requested.

For example the reason.reasonCode field is set to:



* 403 to report forbidden access or unauthorized
* 409 to report conflict







 reason.reasonType (string) 

This field provides additional information about the result of the action requested.





 reason.reasonForFailure (string) 

This field provides additional information as to why the action has failed.







 requestData (JSON) 

When the field is available, it includes additional information about the request.

The information that is included in requestData is specific for each type of action. Check the [API documentation](https://cloud.ibm.com/docs?tab=api-docs&) of a request to learn about some of the fields that may be included.





 responseData (JSON) 

When the field is available, it includes additional information about the request.

The information that is included in responseData is specific for each type of action.
ibmcloud ac collection list [--sort SORT] [--limit LIMIT] [--offset OFFSET] [--features FEATURES] [--properties PROPERTIES] [--tags TAGS] [--expand EXPAND] [--include INCLUDE]



 Command options 

--limit LIMIT (optional)
: Used for pagination. The number of records to retrieve.

--offset OFFSET (optional)
: Used for pagination. The number of records to skip.

--features FEATURES (optional)
: Filter collections by a list of comma-separated features.

--properties PROPERTIES (optional)
: Filter collections by a list of comma-separated properties.

--tags TAGS (optional)
: Filter based on the tags.

--sort SORT (optional)
: Sort the details based on the specified attribute.

--expand EXPAND (optional)
: Expanded view of the item.

--include INCLUDE (optional)
: Include feature and property details in the response.





 Example 

To list all collections, run the following command:

ibmcloud ac collection list



 Output 

The command returns the following output:

name collection_id
sample sampleId
GHz Inc ghzinc1









 ibmcloud ac collection create 

You can create a collection, by using the command:

ibmcloud ac collection create {--file FILE-PATH | --name NAME [--collection_id COLLECTION_ID] [--description DESCRIPTION] [--tags TAGS]}



 Command options 

--name NAME
: Collection name. Required field - input either as a flag or from file.

--collection_id COLLECTION_ID (optional)
: Collection ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION (optional)
: Description of the collection. Optional field - input either as a flag or from file.

--tags TAGS (optional)
: Tags associated with the collection. Optional field - input either as a flag or from file.

--file FILE
: Spectrum Scale product version was updated from 5.1.5.1 to 5.1.7.0.

Support automated public gateway creation when one is not associated with the subnets of an existing VPC
: When you choose to use an existing VPC, the automation associates the public gateway with all of the subnets if it is already part of the VPC. If the public gateway is not part of the VPC, then it creates a new public gateway and associates it with all subnets to allow internet access from the cluster nodes.

DNS functionality support
: Introduced use of DNS custom resolver for name resolution in place of static hostname to IP address mapping.





 February 2023 



 16 February 2023 

Bug fix
: Code fixes were applied to address an issue when creating new subnets with custom CIDR in an existing VPC range.







 January 2023 



 27 January 2023 

Bare metal server support for worker nodes
: You now have the option to use bare metal servers instead of virtual server instances for your cluster worker nodes.

Updated RHEL 8.4 custom images
: New RHEL 8.4 custom images that are used for deploying the compute nodes and Spectrum Scale storage nodes replace images that are provided in the previous release. The new images include several miscellaneous fixes.

Allow CIDR block specification
: You now have the option to either accept the default CIDR block or specify the CIDR block for the compute and storage cluster private subnet. This is helpful to avoid overlapping IP addresses, for example, if you are using a hybrid cloud environment.

Added valid Spectrum Symphony license check
: The solution now checks for a valid license that is associated with ibm_customer_number, which has been added as a required variable.







 October 2022 



 27 October 2022 

Windows® support
: You can now deploy Windows® worker nodes in your IBM Spectrum Symphony cluster.







 September 2022 



 23 September 2022 

Bug fix
: Code fixes were applied to address an issue that was seen in regions where instance storage profiles are not available even though Spectrum Scale is not selected as the storage option.

Updated RHEL stock image