vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[AC-2 (2) - Removal of Temporary / Emergency Accounts](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.2ac-2.2)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.2control-requirements)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.2nist-supplemental-guidance)



[AC-2 (3) - Disable Inactive Accounts](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.3ac-2.3)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.3control-requirements)



[AC-2 (4) - Automated Audit Actions](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.4ac-2.4)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.4control-requirements)
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.4implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-2.4scc-fs-cloud-profile)
The ledger, Ledger x in the illustration above, is maintained by distributed peers. These peers are deployed with [Couch DB](https://hyperledger-fabric.readthedocs.io/en/release-2.2/couchdb_as_state_database.html)) as the state database in a separate container associated with the peer. This database holds the current value of all "state" (as represented by key-value pairs). For example, saying that Org1 (a value) is the current owner of a bank asset (the key). The blockchain, the list of transactions, is stored locally on the peer.
* One channel: channel1
Channels allow sets of organizations to transact without exposing their data to organizations that are not members of the channel. Each channel has its own ledger, collectively managed by the peers joined to that channel. The tutorial creates one channel that is joined by both organizations, and shows how to instantiate a smart contract on the channel that the organizations can use to transact.



This configuration isn't mandatory. The IBM Blockchain Platform is highly customizable. If you have resources available in your Kubernetes cluster, you can use the console to deploy components in an endless array of configurations. This tutorial provides the steps that you need to build your own network, with references to topics that provide a deeper dive into the IBM Blockchain Platform and the console.

You can deploy multiple peers that belong to the same organization MSP and multiple orderers that belong to a different organization MSP. But the console does not prevent you from configuring peers and ordering nodes that belong to a single same organization MSP. While it might seem that a single organization MSP for all your nodes would greatly simplify deployment of your network, this configuration is problematic. Because the process to renew certificates is different for peer and ordering nodes, when the renewal process is attempted after the node certificates expire in one year, certificate renewal will fail. For that reason, using the same MSP for your peers and ordering nodes is strongly discouraged.
Make a GET /instances/{id} to view details of a single instance and locate its boot volume ID.

The response shows the ID of the boot volume under volume_attachments:

"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"
}
},
You can also tell whether the instance is running by making a GET /volumes/{id} call and specifying the boot volume ID.
Checking the status of Ingress components 

Virtual Private Cloud

Classic infrastructure



 Getting the status and message 

To check the overall health and status of your cluster's Ingress components:

ibmcloud oc ingress status-report get -c <cluster_name_or_ID>

The state of the Ingress components are reported in an Ingress Status and Ingress Message.

Example output

Ingress Status: healthy
Message: All Ingress components are healthy.

Cluster Status
ingress-operator healthy
route-admission healthy

Subdomain Status
example-ae7743ca70a399d9cff4eaf617434c72-0000.us-south.containers.appdomain.cloud healthy

Router Status
router-default healthy

Secret Namespace Status
example-ae7743ca70a399d9cff4eaf617434c72-0000 ibm-cert-store healthy
example-ae7743ca70a399d9cff4eaf617434c72-0000 openshift-ingress healthy

The Ingress Status and Ingress Message fields are also returned in the output of the ibmcloud oc cluster get command.





 Ingress statuses 

The Ingress Status reflects the overall health of the Ingress components.



Ingress statuses

 Ingress status Description 

 healthy The Ingress components are healthy. 
 warning Some Ingress components might not function properly. 
 critical Some Ingress components are malfunctioning. 
 disabled Ingress status reporting is disabled. You can turn it on using the ibmcloud oc ingress status-report enable command. 
 unsupported Ingress status reporting is not available for unsupported cluster versions. 
 unknown The system is unable to calculate the Ingress status. 







 Ingress messages 

The Ingress message provides details of what operation is in progress or information about any components that are unhealthy. Each status and message is described in the following tables.



Ingress messages

 Ingress message Description 

 The Ingress Operator is missing from the cluster. (ERRIONF).
"document_id": "46b52fdc-3a72-4700-9849-ac217532b373",
"relevance": 3
}
]
}
Show more
4. Check the status of the training by using the [List collection details](https://cloud.ibm.com/apidocs/discoveryget-collection-details) method and looking at the value of the "training"/"available" field. When you add enough queries and examples to meet the training requirements, the value of the field returns as true, and the service automatically begins to use the training data.

curl -u "4ba1624f-48b6-484a-8e32-18d1c205c1fa":"qUy3B0CbGf9G" "{url}/v1/environments/a56dd9b4-040b-4ea3-a736-c1e7a467e191/collections/99040100-fe6a-4782-a4f5-28f9eee30850?version=2019-04-30"

Replace {url} with your URL.

The JSON that is returned is in the following format:

{
"collection_id": "99040100-fe6a-4782-a4f5-28f9eee30850",
"name": "democollection",
"configuration_id": "def9bd08-8472-470f-ab5a-e377f77e9300",
"language": "en_us",
"status": "available",
"description": "this is a demo collection",
"created": "2015-08-24T18:42:25.324Z",
"updated": "2015-08-24T18:42:25.324Z",
"document_counts": {
"available": 1000,
"processing": 20,
"failed": 180
},
Checking the status of Ingress components 

Virtual Private Cloud

Classic infrastructure



 Getting the status and message 

To check the overall health and status of your cluster's Ingress components:

ibmcloud ks ingress status-report get -c <cluster_name_or_ID>

The state of the Ingress components are reported in an Ingress Status and Ingress Message.

Example output

Ingress Status: healthy
Message: All Ingress components are healthy.

Cluster Status
ingress-controller-configmap healthy
alb-healthcheck-ingress healthy

Subdomain Status
example-ae7743ca70a399d9cff4eaf617434c72-0000.us-south.containers.appdomain.cloud healthy

ALB Status
public-crad7rd4m219nv1vtgdivg-alb1 healthy

Secret Namespace Status
example-ae7743ca70a399d9cff4eaf617434c72-0000 ibm-cert-store healthy
example-ae7743ca70a399d9cff4eaf617434c72-0000 default healthy
example-ae7743ca70a399d9cff4eaf617434c72-0000 kube-system healthy

The Ingress Status and Ingress Message fields are also returned in the output of the ibmcloud ks cluster get command.





 Ingress statuses 

The Ingress Status reflects the overall health of the Ingress components.



Ingress statuses

 Ingress status Description 

 healthy The Ingress components are healthy. 
 warning Some Ingress components might not function properly. 
 critical Some Ingress components are malfunctioning. 
 disabled Ingress status reporting is disabled. You can turn it on using the ibmcloud ks ingress status-report enable command. 
 unsupported Ingress status reporting is not available for unsupported cluster versions. 
 unknown The system is unable to calculate the Ingress status. 







 Ingress messages
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. From the Virtual server instances page, click New instance.
3. You can either select a profile configuration from Popular profiles or click All profiles to view more configurations.







 Viewing instance profiles from the CLI 

To view the list of available instance profiles by using the CLI, run the following command:

ibmcloud is instance-profiles





 Viewing instance profiles with the API 

To view the list of available instance profiles by using the API, you can call the [List all instance profiles API](https://cloud.ibm.com/apidocs/vpclist-instance-profiles).

The following request example lists the available instance profiles. When you call the API, replace the API endpoint and IAM token with the values from your enterprise. For more information about the $vpc_api_endpoint and $iam_token variables, see the Authentication and Endpoint URLs sections in [Virtual Private Cloud API Introduction](https://cloud.ibm.com/apidocs/vpcabout-vpc-api).

curl -X GET "$vpc_api_endpoint/v1/instance/profiles?version=2021-02-23&generation=2" -H "Authorization: $iam_token"







 Block storage volume notes for profiles 

When you create secondary data volumes, you select a volume profile that best meets your requirements. Volume profiles are available as three predefined [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) or as a [custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom). These volume profiles relate to virtual server instance profiles:
For a tutorial on how this process is handled by the console, check out [Deploy a smart contract using Fabric v2.x](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2).

For information about to take advantage of the new lifecycle when writing a smart contract, check out [Writing powerful smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-write-powerful-smart-contracts).





 How can I check and interpret the status of my components through the Kubernetes command line? 

To check the status of your component, run the following command:

kubectl get <CUSTOM_RESOURCE_TYPE> <CUSTOM_RESOURCE_NAME> -n <NAMESPACE> -o yaml



* Replace <CUSTOM_RESOURCE_TYPE> with the custom resource type of your component (ibpca, ibppeer, ibporderer, or ibpconsole).
* Replace <CUSTOM_RESOURCE_NAME> with the name of your component.
* Replace <NAMESPACE> with the name of your IBM Support for Hyperledger Fabric deployment namespace or OpenShift project.



The spec.status field will contain details of your component's status:



* errorCode
* lastHeartbeatTime: when the controller last reconciled the component
* message: long explanation of the status type
* reason: short explanation of the status
* status: "true" or "false" based on if status is valid
* version: the product (IBP) version of the component
* versions: the operand version of the component
* type: describes the current status of the component



* Deploying: component pod(s) spinning up but not yet running and ready
* Deployed: component pod(s) are running
* Precreated: (specific to the Orderer) Orderer is waiting for the genesis block to be created
* Error: component hit an error during reconcile, or a certificate has expired
* Warning: one or more of the component's certificate will be expiring within 30 days (by default)
Ready true 10s
RoutesReady true 10s

Instances:
Name Revision Running Status Restarts Age
myapp-atfte-2-deployment-7cb45cdf67-qc7sb myapp-atfte-2 2/2 Running 0 52s
myapp-atfte-2-deployment-7cb45cdf67-sp9fr myapp-atfte-2 2/2 Running 0 52s

If you want more fine-grained details about your app, use the --o yaml option with the app get command; for example, ibmcloud ce app get --name myapp --o yaml. This option is useful to show more detailed information in the CLI for the app.
3. Display the logs of instances of your app.



* To display the logs of a specific instance of your app, use the [ibmcloud ce app logs --instance INSTANCE_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-logs) command; for example,

ibmcloud ce app logs --instance myapp-atfte-2-deployment-7cb45cdf67-qc7sb

Example output

Getting logs for application instance 'myapp-atfte-2-deployment-7cb45cdf67-qc7sb'...
OK

myapp-atfte-2-deployment-7cb45cdf67-qc7sb/user-container:
Server running at http://0.0.0.0:8080/
* To display the logs for all the instances of your app, use the [app logs --application APP_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-logs) command; for example,

ibmcloud ce app logs --app myapp

Example output

Getting logs for all instances of application 'myapp'...
OK

myapp-atfte-2-deployment-7cb45cdf67-qc7sb/user-container:
Viewing your Delivery Pipeline activity 

The IBM Cloud® DevOps Insights Overview page automatically displays historical data from all of the IBM Cloud® Continuous Delivery within your toolchain for the US-south and EU-gb locations. You can view data about the last two weeks for stage failures, total time that is consumed by all stage runs, and the total number of jobs.

Zoom

![Example of auto-filled data provided by the DevOps Insights Overview page](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/pipeline_data_overview_page.png)

Figure 1. An example of the automatically filled data that is taken from the IBM Cloud® Continuous Delivery attached to the same toolchain as this instance of the DevOps Insights Overview page.

Viewing the status of your pipelines at a glance helps you to understand which jobs and stages are running into problems more often, and which runs are taking the longest time. You can troubleshoot and resolve issues with your pipelines to increase velocity for your deployments and better control of your processes.



 Before you begin 

You must have at least one IBM Cloud® Continuous Delivery in your toolchain and an instance of DevOps Insights. For more information, see [Adding DevOps Insights to your toolchain](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-add-devops-insights).

DevOps Insights is free for Continuous Delivery users with Delivery Pipelines or a hosted Git.





 Viewing pipeline analytics 



1. From the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg) and select DevOps.
2. Select your toolchain on the Toolchains page.
3.
curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognitions?timestamps=true"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognitions?timestamps=true"

The service returns a status of processing to indicate that it is already processing the job, along with the creation time, the job ID, and the URL for getting information about the job.

{
"created": "2016-08-17T19:13:23.622Z",
"id": "4bb1dca0-f6b1-11e5-80bc-71fb7b058b20",
"url": "{url}/v1/recognitions/4bb1dca0-f6b1-11e5-80bc-71fb7b058b20",
"status": "processing"
}







 Checking the status and retrieving the results of a job 

You call the GET /v1/recognitions/{id} method to check the status of the job that is specified with the id path parameter. The response always includes the ID and status of the job and its creation and update times. If the status is completed, the response also includes the results of the recognition request.

The GET /v1/recognitions/{id} method is the only way to retrieve job results if



* The job was submitted without a callback URL.
* The job was submitted with a callback URL but without specifying the recognitions.completed_with_results event.
* The job is not one of the 100 latest outstanding jobs. When you omit the id path parameter, only the 100 latest jobs are returned.
export RoutingTableId=<your_routing_table_id>
3. View details of a routing table:

curl -X GET "$vpc_api_endpoint/v1/vpcs/$VpcId/routing_tables/$RoutingTableId?version=$api_version&generation=2" -H "Authorization: $iam_token"

To view the routing table that is attached to a subnet:

export SubnetId=<your_subnet_id>
curl -X GET "$vpc_api_endpoint/v1/subnets/$SubnetId/routing_table?version=$api_version&generation=2" -H "Authorization: $iam_token"
"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"
}
},
You can also tell whether the instance is running by making a GET /volumes/{id} call and specifying the boot volume ID. If you see active = true in the response, the instance is running.<-- </section "id="section-ifv-locate-instance" "> --><-- <section "id="section-ifv-stop-instance" "> --> Step 2 - Stopping the running instance Stop the running instance by specifying the stop action in a POST /instances call: curl -X POST "$vpc_api_endpoint/v1/instances/{instance-id}/gen/actions?version=2021-05-20"
$iam_token" -d
'{
"type":"stop"
}'
<-- </section "id="section-ifv-stop-instance" "> --><-- <section "id="section-ifv-create-image-boot-id" "> --> Step 3 - Creating an image and providing the ID of the boot volume image Create an image with a POST /images request and pass the boot volume ID of the instance. curl -X POST "$vpc_api_endpoint/v1/images?version=2021-05-20"
$iam_token" -d
{
"name": "test-ifv-boot-volume",
"source_volume": {
"id": "4fec84ef-baf9-405d-bf3b-9d5a60e068f7"
}
}
Inside the Kubernetes dashboard, use the left navigation Namespace drop-down list to change to the namespace for your IBM Blockchain Platform service instance that you discovered above.
4. On the left navigation, click Pods to view the list of node pods that you have deployed.
5. Click on a pod. Then click the View logs icon on the top menu to open the logs of your node. Above the logs, you can use the drop-down menu after Logs from to view the logs from the different containers within the pod. For example, your peer and the state database (CouchDB for example) run in different containers and generate different logs.







 Viewing nodes logs on a Red Hat OpenShift 4.x cluster 

See the Red Hat OpenShift [documentation](https://docs.openshift.com/container-platform/4.3/logging/cluster-logging-viewing.htmlcluster-logging-viewing-logs-console_cluster-logging-viewing).







 Viewing your smart contract container logs 

If you encounter issues with your smart contract, you can view the smart contract logs to debug an issue. The process to view the logs depends on whether your peer is running a Fabric v1.4 or v2.x image. The Fabric version that the peer is running is visible when you click on a peer node in the console:

Zoom

![How to find peer fabric version](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/peerversion.png)

Figure 1.How to find peer fabric version



 Hyperledger Fabric v2.x peer image 

!
* UI
* CLI
* API







 Listing flow log collectors 

You can list your flow log collectors by using the UI, the CLI, or the API.



 Using the UI 

To list your flow log collectors by using the IBM Cloud console:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) on the upper left of the page, then click VPC Infrastructure > Flow logs in the Network section. If available, a list of provisioned flow log collectors shows.



Flow log collector attributes shown in the table are as follows:



* Status - The status of the flow log collector (Example: Stable, Failed, Pending).
* Active - On/Off flag for the flow log. If Active, the flow log collector is set to write log files. If Suspended, the collector is deactivated and not writing log files.
* Name - The flow log name.
* Target - The specified resource the collector logs traffic for.
* Date Created - The date the flow log collector was provisioned.
* Object Storage Bucket - The selected IBM Cloud Object Storage bucket where the system saves flow log files.



Notice that the page includes tabbed views, which show flow log collectors that were created with that target type.



* VPC - Shows flow log collectors that are attached directly to a VPC.
* Subnet - Shows flow log collectors that are attached directly to a subnet within the specified VPC.
* Instance - Shows all flow log collectors that are attached directly to a virtual server instance within the specified VPC.
* Interface - Shows all flow log collectors that are attached directly to a network interface of a virtual server instance within the specified VPC.







 Using the CLI 

To list all your flow logs, run the following command:

ibmcloud is flow-logs [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME]
[--json]
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Organization vDC: View ACL ![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) ![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) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Organization vDC: View CPU and Memory Reservation !