vania-janet/multiturn-rag-retrieval-data huggingface dataset:
--if-match=2022-05-27T10:13:31Z 
--output json
* Output

The command returns the output similar to the following example:

ETag
2022-05-27T10:14:13Z
{
"id": "3dab42dc-6941-4841-8d27-4dabcc5aa09e",
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"template": {
"id": "93777bca-baef-4070-b9b5-a2e6079df1b4",
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE"
},
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{
"method": "enc-zero",
"value": "DDFA4A"
}
],
"activation_date": "2027-04-18",
"expiration_date": "2028-06-29",
"tags": [
{
"name": "first-tag",
"value": "for-ibm"
}
],
"created_at": "2022-03-09T11:26:01Z",
drag","t0":0}]},{"name":"x","qubits":10],"sequence":{"ch":"d10","label":"Xp_d10","name":"parametric_pulse","parameters":{"amp":0.17802780203597496,0],"beta":0.2965933095460568,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0}]},{"name":"x","qubits":11],"sequence":{"ch":"d11","label":"Xp_d11","name":"parametric_pulse","parameters":{"amp":0.20721712486331753,0],"beta":-0.8603575655285178,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0}]},{"name":"x","qubits":12],"sequence":{"ch":"d12","label":"Xp_d12","name":"parametric_pulse","parameters":{"amp":0.15361679760766664,0],"beta":-0.8316746390488242,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0}]},{"name":"
changes_done Number of documents compacted. 
 phase Reports the stage of compaction. 
 total_changes Number of documents in the database. 



In the phase field, the value indicates the stage that was reached by compaction:

ids
: Document compaction is in progress.

views
: View compaction is in progress.





 Specific response fields for replication tasks 



Table 3. Response fields for replication tasks

 Name Description 

 changes_pending Number of documents that need to be changed in the target database, expressed as an integer. 
 continuous Boolean value that indicates whether the replication is continuous. 
 docs_read Number of documents that are read from the source database, expressed as an integer. 
 replication_id Unique identifier string of the replication that can be used to cancel the task. 
 revisions_checked Number of document revisions that were checked to verify whether they're already in the target database. 
 source An obfuscated URL string that indicates the database from which the task is replicating. 
 target An obfuscated URL string that indicates the database to which the task is replicating. 
 user User who started the replication, expressed as a string, or null if the replication was not initiated by a user. 







 Specific response fields for indexing tasks 



Table 4. Response fields for indexing tasks

 Name Description 

 changes_done Number of document revisions that are processed by this task. A document can have one or more revisions. 
 design_document The design document that includes the view or index function or functions. 
 total_changes The number of unindexed changes to process. This count includes deleted documents, although these documents are automatically skipped by the indexer.
The list items must match the regular expression /^-?[a-z0-9_.\[\],-]+$/.

--name (string)
: Optional. Return only vaults whose names begin with the string. The length must be between 1 and 100 characters. The value must match the regular expression /.+/.

--description (string)
: Optional. Return only vaults whose description contains the string. The length is must be between 1 and 200 characters. The value must match the regular expression /.+/.

--all-pages (bool)
: Optional. Invoke multiple requests to display all pages of the collection for vaults.
* Example

ibmcloud hpcs uko vaults --output json
* Output

The command returns the output similar to the following example:

{
"total_count": 2,
"limit": 20,
"offset": 0,
"first": {
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults?limit=20&limit=20&offset=0"
},
"last": {
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults?limit=20&limit=20&offset=0&offset=0"
},
"vaults": [
{
"id": "d0564770-1422-420c-945f-10803a2e24de",
"name": "EXAMPLE_VAULT_NAME",
"description": "API Test Vault description update.",
"created_on": "2022-03-07T09:39:17Z",
"updated_on": "2022-03-07T14:31:09Z",
"created_by": "IBMid-1308197YB4",
The value must match the regular expression /(.|\n)/.
* Example

ibmcloud hpcs uko managed-key-update 
--id=21a7498e-2ae4-47ee-85ac-a19bf64e92fa 
--uko-vault=eb66ebbd-7230-4cde-89bf-17282cda5faa 
--if-match=2022-05-26T14:18:10Z 
--description="updated description" 
--output json
* Output

The command returns the output similar to the following example:

ETag
2022-05-26T14:26:39Z
{
"id": "3dab42dc-6941-4841-8d27-4dabcc5aa09e",
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"template": {
"id": "93777bca-baef-4070-b9b5-a2e6079df1b4",
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE"
},
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{
"method": "enc-zero",
"value": "DDFA4A"
}
],
AwardJudge 
 AwardNominee 
 AwardPresentingOrganization 
 AwardWinner 
 BasketballConference 
 BasketballDivision 
 BasketballPlayer 
 BasketballTeam 
 Bassist 
 Beer 
 Belief 
 Beverage 
 BicycleManufacturer 
 BipropellantRocketEngine 
 Blog 
 Blogger 
 BoardMember 
 BoardMemberTitle 
 BodyOfWater 
 Bone 
 Book 
 BookEdition 
 BoxingWeightDivision 
 Brand 
 Bridge 
 BritishRoyalty 
 Broadcast 
 BroadcastArtist 
 BroadcastContent 
 BroadcastDistributor 
 Building 
 BuildingComplex 
 BuildingFunction 
 CameraFormat 
 CanadianAboriginalGroup 
 CandyBar 
 CandyBarManufacturer 
 Cardinal 
 CauseOfDeath 
 Cave 
 Celebrity 
 CelestialObject 
 Chancellor 
 CharacterOccupation 
 CharacterRank 
 CharacterSpecies 
 Cheese 
 Chef 
 ChemicalCompound 
 ChemicalElement 
 ChineseEthnicGroup 
 ChristianBishop 
 CityTown 
 Club 
 Collector 
 College 
 CollegeCoach 
 CollegeUniversity 
 Comedian 
 ComicBookCreator 
 ComicBookIssue 
 ComicBookPublisher 
 ComicBookSeries 
 ComicBookStory 
 ComicBookStoryArc 
 ComicStripArtist 
 ComicStripSyndicate 
 Company 
 CompanyFounder 
 CompanyShareholder 
 Competition 
 CompetitiveSpace 
 Composer 
 Composition 
 CompositionalForm 
 ComputerPeripheral 
 ComputingPlatform 
 ConcertFilm 
 ConcertTour 
 ConductedEnsemble 
 Conductor 
 Conference 
 ConferenceSeries 
 ConsumerProduct 
 ContentLicense 
 Continent 
 Country 
 CranialNerve 
 CreativeWork 
 CricketAdministrativeBody 
 CricketTournamentEvent 
 Criminal 
 CriminalOffense 
 Cuisine 
 CulinaryMeasure 
 CulinaryTool 
 DedicatedWork 
 Dedicatee 
 Dedicator 
 Degree 
 Deity 
 DietFollower 
 DigitalCamera 
 DisasterSurvivor 
 Disease 
 DiseaseCause 
 DiseaseOrMedicalCondition
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Security Tag Edit ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Selector Extensions: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Selector Extensions: View !
--catalog CATALOG
: The catalog name or ID.

--offering OFFERING_NAME
: : The product name or ID.

--zipurl URL (optional)
: URL pointing to the .zip file of the product.

--target-version APP_VERSION (optional)
: The application version of the "tgz" being imported.

--include-config (optional)
: If provided, all configurations values are included and available when you import the new version.

--vpc-body BODY (optional)
: Provide the information to import a virtual server image for VPC, including a name, label, install kind, target kind, version, sha, tags, and metadata.





 Virtual server image for VPC example 

Import a virtual server image for VPC to an existing offerng with to a catalog with ID 51c9e0db-2911-45a6-adb0-ac5332d27cf2 and offering ID 97cdaf1b-62b2-48e2-8589-10b31023866d.

ibmcloud catalog offering import-version --catalog 51c9e0db-2911-45a6-adb0-ac5332d27cf2 --offering 97cdaf1b-62b2-48e2-8589-10b31023866d --vpc-body '{
"name": "virtual-server-image",
"label": "virtual server image",
"install_kind": "instance",
"target_kinds": ["vpc-x86"],
"version": "0.0.10",
"sha": "64245e5f3f1e9c4048b18db3abd1450d4b6f9e263ac1b33df6fc1ae96fcbdebb",
"tags": ["virtualservers"],
"metadata": {
"operating_system": {
"dedicated_host_only": false,
"vendor": "CentOS",
ibmcloud ac segment update {--file FILE-PATH | --name NAME --segment_id SEGMENT_ID --description DESCRIPTION --tags TAGS --rules RULES}



 Command options 

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

--segment_id SEGMENT_ID
: Segment ID. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the segment. Required field - input either as a flag or from file.

--rules RULES
: List of rules that determine whether the entity is part of the segment. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the segment. Required field - input either as a flag or from file.

--file FILE
: Input through a file. File format Supported - JSON





 Example 

To update description a segment with ID ibm_employees using flags ([click here](https://cloud.ibm.com/docs/cli?topic=cli-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac segment update --name "IBM India Employees" --segment_id "ibm_employees" --description "IBM India Employees" --tags "ibm" --rules '[{"attribute_name": "email", "operator": "endsWith", "values": "@in.ibm.com"]}]'



 Output 

The command returns the following output:

description IBM India Employees
created_time 2021-02-02T19:04:22Z
updated_time 2021-02-02T19:10:01Z
name IBM India Employees
segment_id ibm_employees









 ibmcloud ac segment delete 

You can delete a segment, by using the command:

ibmcloud ac segment delete --segment_id SEGMENT_ID



 Command options 

--segment_id SEGMENT_ID
: Segment ID





 Example
)","t0":160},{"ch":"u41","name":"fc","phase":"-(P1)","t0":320}]},{"name":"u3","qubits":21],"sequence":{"ch":"d21","name":"fc","phase":"-(P2)","t0":0},{"ch":"d21","label":"X90p_d21","name":"parametric_pulse","parameters":{"amp":0.10054543378303288,0.00519756763842647],"beta":1.9474086217974163,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0},{"ch":"d21","name":"fc","phase":"-(P0)","t0":160},{"ch":"d21","label":"X90m_d21","name":"parametric_pulse","parameters":{"amp":-0.10054543378303288,-0.005197567638426471],"beta":1.9474086217974163,"duration":160,"sigma":40},"pulse_shape":"drag","t0":160},{"ch":"d21","name":"fc","phase":"-(P1)","t0":320},{"
PUT /some-bucket/multipart-object-123?partNumber=1&uploadId=0000015a-df89-51d0-2790-dee1ac994053 HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
x-amz-content-sha256: STREAMING-AWS4-HMAC-SHA256-PAYLOAD
Content-Encoding: aws-chunked
x-amz-decoded-content-length: 13374550
Content-Type: application/pdf
Host: s3.us.cloud-object-storage.appdomain.cloud
Content-Length: 13374550

Example response

HTTP/1.1 200 OK
Date: Sat, 18 Mar 2017 03:56:41 GMT
X-Clv-Request-Id: 17ba921d-1c27-4f31-8396-2e6588be5c6d
Accept-Ranges: bytes
Server: Cleversafe/3.9.1.114
X-Clv-S3-Version: 2.5
ETag: "7417ca8d45a71b692168f0419c17fe2f"
Content-Length: 0

--------------------





 List parts 

A GET given a path to a multipart object with an active UploadID specified as a query parameter returns a list of all of the object's parts.

Not all operations are supported in Satellite environments. For details, see [supported Satellite APIs](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-apis-cos-satellite)

Syntax
"href": "https://us-south-1.cloud.ibm.com/v1/share/profiles/tier-3iops",
"name": "tier-3iops",
"resource_type": "share_profile"
},
"replication_role": "none",
"replication_status": "none",
"replication_status_reasons": [],
"resource_group": {
"crn": "crn": "crn:[...]",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/86ccf0a1315646d4bc719fe34ff4d1e3",
"id": "86ccf0a1315646d4bc719fe34ff4d1e3",
"name": "Default"
},
"resource_type": "share",
"size": 100,
"mount_targets": [],
"user_tags": [
"ut8",
"ut9"
],
"zone": {
"href": "https://us-south-1.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}





 Modify file share user tags with ETag verification 

To ensure that updates to a file share are valid, you can obtain an ETag hash string value and specify it in the If-Match header in the PATCH /shares/{share_id} call. That confirms that no change happened to the share object between the last observed state and the state at the time of the PATCH call.

To modify existing user tags that are added to a file share, you first make a GET /shares/{share_id} call and copy the hash value from ETag property in the response header.
* [attestationPublicKey](https://cloud.ibm.com/docs/vpc?topic=vpc-about-attestationattest_pubkey) is an optional section. You can provide a public RSA key as part of the contract, which is used to encrypt the attestation document and the attribute must be named as attestationPublicKey.
* envWorkloadSignature is an optional section and contains the signature of the other sections of the contract.



The two primary sections in a contract are the workload and env sections. These two sections are needed because the information that is added into the contract comes from two different personas, namely the "workload" and the "deployer" persona.

The workload persona provides information about the container (or workload) that needs to be brought up on the Hyper Protect Virtual Servers for VPC instance. It includes information about the name of the container, the container registry where it resides, credentials of the container registry, the image digest, the notary server information (required for image validation), the environment variables that need to be passed to the container, and the docker compose file or Pod descriptors with the container information.

If you use a docker compose file, only one container is supported. Pod descriptors support one or multiple containers.

The deployer persona works closely with IBM Cloud. This persona receives the workload information (preferably an encrypted workload section) from the workload persona. The deployer then creates the env section of the contract. The env section has information that is specific to the IBM Cloud environment. Usually, it is information that the workload persona does not have and does not need to know. An example is information about the IBM Cloud Logging instance, which the deployer persona creates, before adding information to the env section of the contract.





 The workload section 

This is one of the most important sections of the contract. The workload section can have multiple subsections and the purpose of the subsections is to provide information that is required for bringing up the workload. The workload section is the parent section that can have the following subsections:



* type: workload.
DUTCH TRANSLATION OF COLLECTD DEBCONF TEMPLATES. [collectd-core],
FILE BINDINGS/PERL/LIB/COLLECTD/PLUGINS/MONITORUS.PM [collectd-core],
FILE BINDINGS/PERL/LIB/COLLECTD/PLUGINS/OPENVZ.PM [collectd-core],
FILE CONTRIB/COLLECTD2HTML.PL [collectd-core],
FILE CONTRIB/COLLECTD_NETWORK.PY [collectd-core],
FILE CONTRIB/COLLECTD_UNIXSOCK.PY [collectd-core],
FILE CONTRIB/NETWORK-PROXY.PY [collectd-core],
FILE CONTRIB/SNMP-PROBE-HOST.PX [collectd-core],
FILE DEBIAN/INCLUDE/NET/IP_VS.H [collectd-core],
FILE SRC/APACHE.C [collectd-core],
FILE SRC/APCUPS.C [collectd-core],
FILE SRC/AQUAERO.C [collectd-core],
FILE SRC/CPU.C [collectd-core],
FILE SRC/CURL.C [collectd-core],
FILE SRC/CURL_XML.C [collectd-core],
FILE SRC/DF.C [collectd-core],
FILE SRC/DNS.C [collectd-core],
FILE SRC/ETHSTAT.C [collectd-core],
FILE SRC/EXEC.C [collectd-core],
FILE SRC/FILECOUNT.C [collectd-core],
FILE SRC/FSCACHE.C [collectd-core],
FILE SRC/HDDTEMP.C [collectd-core],
FILE SRC/IPC.C [collectd-core],
FILE SRC/IPMI.C [collectd-core],
FILE SRC/IPTABLES.C [collectd-core],
FILE SRC/IPVS.C [collectd-core],
Read contracts 

The Contracts enrichment identifies contract-related elements in a document.

To use the Contracts enrichment, create a Document Retrieval project type and select the Apply contracts enrichment option. When you make this selection, a Document Retrieval for Contracts project is created.

Only users of installed deployments (IBM Cloud Pak for Data) or Premium or Enterprise plan managed deployments can create a Document Retrieval for Contract project type.

To see the elements that are identified by the Contracts enrichment, complete the following steps:



1. From the Improve and Customize page, submit a search query.

You can submit any keyword you want or pick one of the suggested keyword search terms.
2. Click View passage in document for one of the search results that are displayed for the document that you want to review.
3. Do one of the following things:

IBM Cloud



1. Click Open advanced view to see the Contract Data page.

Zoom

![Shows the Contract Data page for a PDF file.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/contracts-cloud-sla.png)

Figure 1. Contract Data view



IBM Cloud Pak for Data



1. Click Contract Data.



A list of the elements that the Contracts enrichment identified in the document is displayed.





 Contract schema information 

Contract enrichments are applied to the html field of documents that are added to the project.

After a document is processed by the Contracts enrichment, the service generates JSON output in the following schema:

{
"elements": [
{
"location": {
"begin": int,
"end": int
},
"text": string,
"types":
{
"label": { "nature": string, "party": string },
"provenance_ids": string, string, ...]
...
]
}
...
],
discovery.document.update Update one document by ingesting new or modified content for a document given a document ID, or by changing the label for a specified document ID. 
 discovery.document-annotation.read Read document annotations. 
 discovery.document-results.read Search collections for relevant documents. 
 discovery.entity-extractor.create Create an entity extractor. 
 discovery.entity-extractor.delete Delete an entity extractor. 
 discovery.entity-extractor.read Read an entity extractor. 
 discovery.entity-extractor.update Update an entity extractor. 
 discovery.event.create Add a click event to a query. 
 discovery.expansions.create Add synonyms to a collection. 
 discovery.expansions.delete Delete synonyms from a collection. 
 discovery.expansions.read Get synonyms for a collection. 
 discovery.fields.read Get fields for a collection. 
 discovery.label.create Create a collection label. 
 discovery.label.delete Delete one or multiple documents from one or multiple collections based on a label. 
 discovery.label.read Read a collection label. 
 discovery.label.update Update a collection label. 
 discovery.logs.read Get logs for a collection. 
 discovery.metric.read Request a metric. 
 discovery.model.export Export a model. 
 discovery.model.import Import a model. 
 discovery.multi-collection-training-status.read Get the training status of a multi-collection training. 
 discovery.notices.read Get notices for a collection. 
 discovery.page.read Read document pages. 
 discovery.page-annotation.add Add document page annotation. 
 discovery.page-prediction.read Read document page predictions. 
 discovery.page-view.read Read document page view. 
 discovery.project.create Create a project. 
 discovery.project.delete Delete a project. 
 discovery.project-notices.read Get notices for a project. 
 discovery.stopwords.create Add stopwords to a collection. 
 discovery.stopwords.delete Delete stopwords from a collection. 
 discovery.stopwords.read Get stopwords for a collection.
* [Update your peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsupdate-your-peers)
* [Upgrading nodes from Fabric v1.4 to v2.5](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade-v14-v25)
* [Step one: Back up your ledger (optional)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade-step-one-ledger)
* [Step two: Upgrade your nodes one at a time](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade-step-two-rolling-upgrade)
* [Step three: Update SDKs and smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade-step-three)
* [Step four: Update capabilities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade-step-four-rolling-upgrade)



* [Deleting components](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-delete)



[Operating nodes with operations service](https://cloud.ibm.com/docs/blockchain?topic=blockchain-operations_serviceoperations_service)



* [Considerations and limitations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-operations_serviceoperations_service_consideration_limitation)
* A functional two-node RHEL HA Add-On cluster for HANA system replication.
* Both nodes are active.
* Cluster is started on NODE1 and NODE2.
* Cluster Resource SAPHana_${SID}_${INSTNO} is configured with AUTOMATED_REGISTER=true.
* Check SAP HANA System Replication status:



* Primary SAP HANA database is running on NODE1
* Secondary SAP HANA database is running on NODE2
* HANA System Replication is activated and in sync









 Test4 - Test procedure 

Move SAP HANA primary to other node by using the pcs resource move command.

On NODE1, run the following command.

pcs resource move SAPHana_${SID}_${INSTNO}-clone





 Test4 - Expected behavior 



* The cluster creates location constraints to move the resource.
* The cluster triggers a takeover to the secondary HANA database.
* If an application, such as SAP NetWeaver, is connected to a tenant database of SAP HANA, the application automatically reconnects to the new primary.







 Test4 - Recovery procedure 

The automatically created location constraints must be removed to allow automatic failover in the future.

Wait until the primary HANA instance is active and remove the constraints.

The cluster registers and starts the HANA database as new secondary instance.

On NODE1, run the following command.

pcs constraint

pcs resource clear SAPHana_${SID}_${INSTNO}-clone

pcs constraint

pcs status --full