vania-janet/multiturn-rag-retrieval-data huggingface dataset:
./cpd-cli upgrade --repo ./repo.yaml --assembly ibm-watson-gateway-operator --arch Cluster_architecture --namespace <Project> --transfer-image-to <Registry_location> --cluster-pull-prefix <Registry_from_cluster> --ask-pull-registry-credentials --ask-push-registry-credentials
* Upgrade Minio operator:

./cpd-cli upgrade --repo ./repo.yaml --assembly ibm-minio-operator --namespace <Project> --transfer-image-to <Registry_location> --cluster-pull-prefix <Registry_from_cluster> --ask-pull-registry-credentials --ask-push-registry-credentials
* Upgrade RabbitMQ operator:

./cpd-cli upgrade --repo ./repo.yaml --assembly ibm-rabbitmq-operator --namespace <Project> --transfer-image-to <Registry_location> --cluster-pull-prefix <Registry_from_cluster> --ask-pull-registry-credentials --ask-push-registry-credentials
* Upgrade etcd operator:

./cpd-cli upgrade --repo ./repo.yaml --assembly ibm-etcd-operator --namespace <Project> --transfer-image-to <Registry_location> --cluster-pull-prefix <Registry_from_cluster> --ask-pull-registry-credentials --ask-push-registry-credentials
* Upgrade model train classic operator:

./cpd-cli upgrade --repo ./repo.yaml --assembly modeltrain-classic --arch Cluster_architecture --namespace <Project> --transfer-image-to <Registry_location> --cluster-pull-prefix <Registry_from_cluster> --ask-pull-registry-credentials --ask-push-registry-credentials
* Upgrade Elasticsearch operator:
r006-3fa3bea4-7f9c-4eeb-8248-ab1f6e03185b ibm-centos-7-9-minimal-amd64-9 available amd64 centos-7-amd64 7.x - Minimal Install 1 public provider none Default
r006-c55167af-ea8c-4c27-871f-ccc9c868753e ibm-centos-stream-8-amd64-1 available amd64 centos-stream-8-amd64 8 2 public provider none Default
7. List all the available placement groups that you can associate with your instance.

ibmcloud is placement-groups

For this example, you see a response similar to the following output.

Listing placement groups for generation 2 compute in all resource groups and region us-east under account vpcdemo as user yaohaif@cn.ibm.com...
ID Name State Strategy Resource Group
c5f1f366-b92a-4080-991a-aa5c2e33d96b placement-group-region-us-east stable power_spread 5018a8564e8120570150b0764d39ebcc
placement-group-cccc-cccc-cccc-cccccccccccc vsi-placementGroup1 stable host_spread 5018a8564e8120570150b0764d39ebcc
placement-group-bbbb-bbbb-bbbb-bbbbbbbbbbbb vsi-placementGroup2 stable power_spread 5018a8564e8120570150b0764d39ebcc
placement-group-aaaa-aaaa-aaaa-aaaaaaaaaaaa vsi-placementGroup3 stable power_spread 1d18e482b282409e80eff354c919c6a2



After you know these values, use them to run the instance-template-create command. In addition to the information that you gathered, you must specify a name for the instance.
Example command to create a version 4.10 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-local --template-version 4.10 --param "auto-discover-devices=AUTO-DISCOVER-DEVICES" [--param "osd-device-path=OSD-DEVICE-PATH"] --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP" --param "kms-encryption=KMS-ENCRYPTION" [--param "kms-instance-name=KMS-INSTANCE-NAME"] [--param "kms-instance-id=KMS-INSTANCE-ID"] [--param "kms-base-url=KMS-BASE-URL"] [--param "kms-token-url=KMS-TOKEN-URL"] [--param "kms-root-key=KMS-ROOT-KEY"] [--param "kms-api-key=KMS-API-KEY"] --param "ignore-noobaa=IGNORE-NOOBAA"

Example command to create a version 4.11 configuration.
3m 3m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibm.io/ibmc-file", expecting that a volume for the claim is provisioned either manually or via external software
1m 1m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal ProvisioningSucceeded Successfully provisioned volume pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
4. To mount the storage to your deployment, create a configuration .yaml file and specify the PVC that binds the PV.

If you have an app that requires a non-root user to write to the persistent storage, or an app that requires that the mount path is owned by the root user, see [Adding non-root user access to NFS File Storage for Classic](https://cloud.ibm.com/docs/containers?topic=containers-nonroot).

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment_name>
labels:
app: <deployment_label>
spec:
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
containers:
- image: <image_name>
name: <container_name>
volumeMounts:
- name: <volume_name>
mountPath: /<file_path>
volumes:
- name: <volume_name>
persistentVolumeClaim:
claimName: <pvc_name>
Show more

app
: In the metadata section, enter a label for the deployment.
Run the preinstallation script for a product with a version locator number of b636d651-8489-4425-bd6a-f30af1603577.18aad484-c78b-4269-808b-52027621abd4 in cluster with ID bn5ebho206o7fg45f2e0 in the namespace called test-namespace.

ibmcloud catalog offering version preinstall --version-locator b636d651-8489-4425-bd6a-f30af1603577.18aad484-c78b-4269-808b-52027621abd4 --cluster bn5ebho206o7fg45f2e0 --namespace test-namespace







 ibmcloud catalog offering version preinstall-status 

Run the following command to get the status of an ongoing preinstallation.

ibmcloud catalog offering version preinstall-status --version-locator VERSION_NUMBER --cluster CLUSTER_ID --namespace NAME [--output FORMAT]



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product and version that you'd like to use.

--cluster CLUSTER_ID
: Provide the cluster ID of the cluster where the preinstallation was run.

--namespace NAME
: Provide the namespace used for the preinstallation.

--output FORMAT (optional)
: Specifies output format. The default is terminal compatible and the only supported alternative is JSON, for example, --output json.







 ibmcloud catalog offering version validate 

Run the following command to validate a new version of a product in your private catalog. Products must be validated to ensure that they work as expected before they can be published to the account for other users to create an instance from the private catalog.
"status": "running",
"status_reasons": [],
"vcpu": {
"architecture": "amd64",
"count": 2
},
"volume_attachments": [
{
"device": {
"id": "a8a15363-a6f7-4f01-af60-715e85b28141"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/e402fa1b-96f6-4aa2-a8d7-703aac843651/volume_attachments/7389-a8a15363-a6f7-4f01-af60-715e85b28141",
"id": "a8a15363-a6f7-4f01-af60-715e85b28141",
"name": "my-boot-volume-attachment",
"volume": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/49c5d61b-41e7-4c01-9b7a-1a97366c6916",
"id": "49c5d61b-41e7-4c01-9b7a-1a97366c6916",
"name": "my-boot-volume"
}
},
{
"device": {
"id": "e77125cb-4df0-4988-a878-531ae0ae0b70"
},
[RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-about-migration-infrarackware-migration) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg) 
 [DIY automation](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-about-migration-infraDIY-automation) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg)
Partitioning inventory for CC pipeline 

By default, the Continuous Compliance (CC) pipeline runs all compliance checks and tests for each artifact that is listed in the inventory. It is also possible to run the checks and tests only against a subset of the inventory entries.

To run the checks and tests against a subset of inventory entries, complete these steps:



1.  Provide a comma-separated list of entries that you want to include to the inventory-include environment property. For example, entry-a or entry-a,entry-b.
2.  Provide a comma-separated list of entries that you want to exclude to the inventory-exclude environment property. For example, entry-a or entry-a,entry-b.



If inventory-include is used, only the entries that are provided in that environment property are scanned and tested within the pipeline. Entries that are provided in inventory-exclude are excluded from scanning or testing. If both inventory-include and inventory-exclude are present, inventory-include takes precedence, and then inventory-exclude excludes items from the subset that is defined by the inclusion list. It is also possible to define entries by using glob patterns.

For more information about glob patterns, see the [glob](https://man7.org/linux/man-pages/man7/glob.7.html) manual.



  Example 

The following inventory is available:



*  service-a/entry-a
*  service-a/entry-b
*  service-a/entry-c
*  service-b/entry-a
*  service-b/entry-b



If you want to have two separate pipelines for artifacts of service-a and service-b, you can create two triggers where you set inventory-include to service-a// to include only the artifacts of service-a. Then, set service-b// on the second trigger to include only the artifacts of service-b.

When you decide that you also need an extra pipeline for service-a/entry-c, you then can exclude that entry from the previous pipeline by setting inventory-exclude to service-a/entry-c. Then, create another trigger with inventory-include set to service-a/entry-c.
Example command to create a version 4.12 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-local --template-version 4.12 --param "auto-discover-devices=AUTO-DISCOVER-DEVICES" [--param "osd-device-path=OSD-DEVICE-PATH"] --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP" --param "kms-encryption=KMS-ENCRYPTION" [--param "kms-instance-name=KMS-INSTANCE-NAME"] [--param "kms-instance-id=KMS-INSTANCE-ID"] [--param "kms-base-url=KMS-BASE-URL"] [--param "kms-token-url=KMS-TOKEN-URL"] [--param "kms-root-key=KMS-ROOT-KEY"] [--param "kms-api-key=KMS-API-KEY"] --param "ignore-noobaa=IGNORE-NOOBAA"
6. Customize the command based on the settings that you want to use.
7. Run the command to create a configuration.
8. Verify your configuration was created.
3m 3m 1 {ibm.io/ibmc-vpc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibmc-vpc-file-retain-5iops-tier ", expecting that a volume for the claim is provisioned either manually or via external software
1m 1m 1 {ibm.io/ibmc-vpc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal ProvisioningSucceeded Successfully provisioned volume pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
4. To mount the storage to your deployment, create a configuration .yaml file and specify the PVC that binds the PV.

If you have an app that requires a non-root user to write to the persistent storage, or an app that requires that the mount path is owned by the root user, see [Adding non-root user access to NFS File Storage for VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-nonroot).

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment_name>
labels:
app: <deployment_label>
spec:
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
containers:
- image: <image_name>
name: <container_name>
volumeMounts:
- name: <volume_name>
mountPath: /<file_path>
volumes:
- name: <volume_name>
persistentVolumeClaim:
claimName: PVC-NAME
Show more

metadata.labels.app
You can specify the Coverage runner (such as JaCoCo, and Cobertura), the location of the Coverage result file, and the Coverage result directory, relative to the Working directory. 
 Gradle (Artifactory, Nexus, or SonarQube) Builds and deploys by using Gradle with a Nexus or Artifactory repository. Gradle also integrates with SonarQube. Pipeline image version: Runs in a container by using a built-in docker image, which provides various built-in commands. To adopt newer versions of those commands, use a newer image version.<br><br>Repository tool integration instance: The name of the repository tool integration instance to use with this build job.<br><br>Repository tool integration type: The type of tool integration to get Gradle information from.<br><br>SonarQube integration instance: The name of the SonarQube integration instance to use with this build job.<br><br>Build command: The build command to run whenever the job runs. In the Script field, enter a script or reference scripts that are stored in your project’s source control.<br><br>Working directory: Specifies the directory where the script is run.<br><br>Build archive directory: Specifies the directory that contains the job's output to archive for use by a subsequent stage. 
 Maven (Artifactory, Nexus, or SonarQube) Builds and deploys by using Maven with a Nexus or Artifactory repository. Maven also integrates with SonarQube. Pipeline image version: Runs in a container by using a built-in docker image, which provides various built-in commands. To adopt newer versions of those commands, use a newer image version.<br><br>Repository tool integration instance: Name of the repository tool integration instance to use with this build job.<br><br>Repository tool integration type: Type of tool integration to get Gradle information from.<br><br>SonarQube integration instance: Name of the SonarQube integration instance to use with this build job.<br><br>Build command: Build command to run whenever the job runs.
To identify parents, children, siblings, and spouses, use the parentOf, siblingOf, and spouseOf relations. 
 residesIn Exists between a Person and a place where they live or previously lived. 
 shareholdersOf Exists between a Person or Organization, and an Organization of which the first entity is a shareholder. 
 siblingOf Exists between a Person and their sibling or stepsibling. 
 spokespersonFor Exists between a Person and an Facility, Organization, or Person that he or she represents. 
 spouseOf Exists between two Persons that are spouses. 
 subsidiaryOf Exists between two Organizations when the first is a subsidiary of the second.
3m 3m 1 {ibm.io/ibmc-vpc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibmc-vpc-file-retain-5iops-tier ", expecting that a volume for the claim is provisioned either manually or via external software
1m 1m 1 {ibm.io/ibmc-vpc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal ProvisioningSucceeded Successfully provisioned volume pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
4. To mount the storage to your deployment, create a configuration .yaml file and specify the PVC that binds the PV.

If you have an app that requires a non-root user to write to the persistent storage, or an app that requires that the mount path is owned by the root user, see [Adding non-root user access to NFS File Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-nonroot).

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment_name>
labels:
app: <deployment_label>
spec:
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
containers:
- image: <image_name>
name: <container_name>
volumeMounts:
- name: <volume_name>
mountPath: /<file_path>
volumes:
- name: <volume_name>
persistentVolumeClaim:
claimName: PVC-NAME
Show more

metadata.labels.app
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancers/r018-808fedde-2650-46cc-9cd1-4b828b92970a/pools/r018-df11657f-63cf-49b5-af0f-6eeab32b3559",
"id": "r018-df11657f-63cf-49b5-af0f-6eeab32b3559",
"name": "pool1"
},
{
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancers/r018-808fedde-2650-46cc-9cd1-4b828b92970a/pools/r018-733df056-2a46-4b5a-8889-9a787e60871d",
"id": "r018-733df056-2a46-4b5a-8889-9a787e60871d",
"name": "pool2"
}
],
"private_ips": [
{
"address": "10.242.128.5"
},
{
"address": "10.242.128.6"
}
],
"profile": {
"family": "Network",
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancer/profiles/network-fixed",
"name": "network-fixed"
},
"provisioning_status": "active",
"public_ips": [
{
"address": "158.176.168.61"
},
{
"address": "158.176.172.132"
}
],
00276eb58065b5da94-part3" -p "mon-device-path=/dev/disk/by-id/scsi-3600605b00d87b43027b3bc310a64c6c9-part1,/dev/disk/by-id/scsi-3600605b00d87b43027b3bbf306bc28a7-part1,/dev/disk/by-id/scsi-3600062b206ba6f00276eb58065b5da94-part1" -p "num-of-osd=2" -p "worker-nodes=169.48.170.83,169.48.170.88,169.48.170.90" -p "ibm-cos-endpoint=<ibm-cos-endpoint>" -p "ibm-cos-location=<ibm-cos-location>" -p "ibm-cos-access-key=<ibm-cos-access-key>" -p "ibm-cos-secret-key=<ibm-cos-secret-key>"
2. Create a new assignment for this configuration :

ibmcloud sat storage assignment create --name ocs-sub2 --group test-group2 --config ocs-config2





 Scaling your ODF configuration with auto-discover-devices 

If you set the auto-discover-devices parameter to true in your ODF configuration, you can scale your configuration by increasing the num-of-osd parameter value in the following command.

ibmcloud sat storage config param set --config <config-name> -p num-of-osd=2 --apply







 Upgrading your ODF version 

To upgrade the ODF version of your configuration, delete your existing assignment and create a new configuration with the newer version. When you create the new configuration, you can set the odf-upgrade parameter to true to upgrade the installed version of ODF when the new configuration is assigned.



1. Get the details of your ODF configuration and save the configuration details.
Understanding your device status 

In the device list status column, you can quickly see the power state or status of your devices. See the following table for status definitions.



Table 1. Device state or status definitions

 Status                   Definition                                                                                                              

 Migrating                Device is migrating to a new host.                                                                                      
 Pending reclaim          Device is in a hold state in preparation of the reclaim process.                                                        
 Processing               New device approval pending.                                                                                            
 Provisioning             Device is being prepared for use.                                                                                       
 Reclaiming               Device is being reclaimed.                                                                                              
 Reloading                Device operating system is reloading.                                                                                   
 Running                  Device is powered on.                                                                                                   
 Stopped                  Device is powered off.                                                                                                  
 Stopped (Suspended)      Device is powered down and billing is suspended. For more information about suspend billing, see [Suspend billing](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-requirements).   
 Unavailable              Unable to determine the state of your device.                                                                           
 Updating                 Device running automated task such as firmware or BIOS update.
12@sha256:ff4053b0bca784d6d105fee1d008cfb20db206011453071e86b69ca3fde706a4
script: 
!/usr/bin/env bash
echo "Please insert any required pre-build tasks in this stage."





 test 

Define this stage to run the test cases of the app.

test:
abort_on_failure: false
image: icr.io/continuous-delivery/pipeline/pipeline-base-image:2. 12@sha256:ff4053b0bca784d6d105fee1d008cfb20db206011453071e86b69ca3fde706a4
script: 
!/usr/bin/env bash
cd ../"$(load_repo app-repo path)"
npm ci
npm test
source test/test.sh





 static-scan 

Define this stage to run static scan on the code.

static-scan:
dind: true
image: icr.io/continuous-delivery/pipeline/pipeline-base-image:2.12@sha256:ff4053b0bca784d6d105fee1d008cfb20db206011453071e86b69ca3fde706a4
script: 
!/usr/bin/env bash
echo "Please insert script to invoke/execute static scan tool like SonarQube on the application source code."





 containerize 

Define this stage to build and containerize your app.

containerize:
dind: true
image: icr.io/continuous-delivery/pipeline/pipeline-base-image:2. 12@sha256:ff4053b0bca784d6d105fee1d008cfb20db206011453071e86b69ca3fde706a4
script:
* [Database and replica sets](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-CA-replica-sets)
* [Deployment zone selection](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-ca-k8s-zone)
* [Sizing a CA during creation](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-CA-sizing-creation)
* [Customizing a CA configuration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-ca-customization)



* [Peer deployment](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-peer)



* [State database](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-level-couch)
* [Deployment zone selection](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-peer-k8s-zone)
* [Sizing a peer during creation](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-peers-sizing-creation)