vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Auditing events for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-at_events). 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilities for change management
The first column describes the task that the customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Provisioning. It is the responsibility of IBM to provision the service. 
 Deprovisioning. It is the responsibility of IBM to deprovision the service. 
 Update package versions. It is your responsibility to update package versions inside container images. You can use Vulnerability Advisor to identify the required updates. For more information, see [Managing image security with Vulnerability Advisor](https://cloud.ibm.com/docs/Registry?topic=Registry-va_index&interface=ui). 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.



Table 3. Responsibilities for identity and access management
The first column describes the task that the customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Authentication It is the responsibility of IBM to implement authentication. 
 Process access policies It is the responsibility of IBM to ensure that the policies are processed. 
 Set up access policies It is your responsibility to set up access policies. For more information, see [Creating policies](https://cloud.ibm.com/docs/Registry?topic=Registry-usercreate). 
 Access to back-end resources It is the responsibility of IBM to access to back-end resources. 
 Access to namespaces It is your responsibility to set up access to namespaces.
Understanding your responsibilities when you use IBM Cloudant 

Learn about the management responsibilities, and terms and conditions, that you own when you use IBM® Cloudant® for IBM Cloud®. For a high-level view of the service types in IBM Cloud®, and the breakdown of responsibilities between the customer and IBM® for each type, see [Shared responsibilities for using IBM Cloud offerings](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).

Review the following sections to understand the specific responsibilities between you and IBM when you use IBM Cloudant. For the overall terms of use, see [IBM Cloud Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).



 Incident and operations management 

Incident and operations management includes tasks such as monitoring, event management, high availability, problem determination, recovery, and full state backup and recovery.



Table 1. Responsibilities for incident and operations
The first column describes the task that the customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 HA/DR (multi-zone region) IBM Cloudant stores all documents in triplicate on separate servers that are spread across three separate availability zones by default. 
 HA/DR (single-zone region) IBM Cloudant stores all documents in triplicate on three separate physical servers within the availability zone by default. 
 Back up and restore Customer is responsible for backup and restore of data to roll back to a previous state in the database. See [IBM Cloudant backup and recovery](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloudant-backup-and-recovery) documentation for recommended tooling. 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilities for change management
The first column describes the task that the customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities
[Genesys transfer widget](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-transfer-widget.png)



1. Select the queue you want to use.
2. In the toolbox, click the Disconnect widget and drag it into the action after Failure. (This disconnects the call if the transfer fails.)
3. Click the three dots under Reusable tasks and click Set this as the starting task. You can remove the Initial Greeting, because your assistant will speak before handing off the call.
4. Click Publish in the menu bar to make this transfer live.
5. Return to the main Genesys Cloud console.
6. Click Admin and then navigate to Call Routing in the Routing section.
7. Give the route a descriptive name (for example, Escalate to Agent).
8. Under Regular Routing, for all calls, select your new flow.
9. Assign the DID number you previously created.
10. Click Save.



4. Make sure your assistant is configured with at least one dialog node that transfers calls to an agent. For more information about how to do this, see [Transferring a call to a human agent](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-voice-actionsdialog-voice-actions-transfer).

For the transferTarget parameter, use the DID number you created in Genesys Cloud, as well as the inbound SIP URI from your Genesys trunk. Use the following format:

sip:+18883334444\@example.com

Make sure you use the \ escape characters so Watson Assistant does not misinterpret the @ as part of the entity shorthand syntax.
5. Make a test call and say something that initiates a transfer to an agent. In your Genesys Cloud console, you should see the transfer take place.
Infrastructure monitoring and notification Forward to the client all network intrusion notifications detected. Send notification upon hardware failures. Implement monitoring system and integrate with virtualization management. Determine the impact of each notification reported. Engage IBM support as required. 
 Workload monitoring Monitor and respond to OS or software failures. 
 Infrastructure management Implement monitoring and management system that is integrated with virtualization management. 
 Incident management Unplanned incidents with customer impact are communicated through the CIE process. Impacted customers can obtain a report about the incident upon request. 









 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



 Change management for VMware Shared 

The following table describes the responsibilities that are related to change management for VMware Shared.



Table 3. Responsibilities for change management for VMware Shared
The rows are read from left to right. The first column describes the task that a customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM responsibilities Your responsibilities 

 Updates, fixes, and new features Regular updates, bug fixes, and new features are provided, following a continuous delivery model in a way that is transparent to you. Notifications are posted for changes that impact you. Set preferences to receive email notifications. Monitor the IBM Cloud status page for general announcements. 
 Scaling Scale the customer VMware infrastructure as requested and to meet the capacity that you selected. Choose the capacity for your VMware Solutions instances. 







 Change management for VMware Solutions offerings (other than VMware Shared) 

The following table describes the responsibilities that are related to change management for all VMware Solutions offerings, other than VMware Shared.



Table 4. Responsibilities for change management for VMware Solutions offerings (other than VMware Shared)
The rows are read from left to right. The first column describes the task that a customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM responsibilities Your responsibilities 

 Scaling Scale your VMware infrastructure as requested.
* Running the following wget command.

 {: pre}
wget https://<apihost>/api/v1/web/<namespace_ID>/demo/hello.text/response/name?name=Jane


Example output

Jane

In standard actions, query parameters, form data, and JSON object body entities are all treated as dictionaries, and their values are directly accessible as action input properties. This behavior is not the case for web actions, which handle HTTP request entities, or when the web action receives an entity that is not a JSON object.

f. You can set the Content-Type by using one of the following methods.

* Running the following cURL command.

 {: pre}
curl https://<apihost>/api/v1/web/<namespace_ID>/demo/hello.json -H 'Content-Type: text/plain' -d "Jane"

* Running the following wget command.

 {: pre}
wget https://<apihost>/api/v1/web/<namespace_ID>/demo/hello.json -H 'Content-Type: text/plain' -d "Jane"


Example output

{
"response": {
"__ow_method": "post",
"__ow_headers": {
"accept": "/",
"connection": "close",
"content-length": "4",
"content-type": "text/plain",
"host": "172.17.0.1",
"user-agent": "curl/7.43.0"
},
"__ow_path": "",
"__ow_body": "Jane"
}
}









 Securing web actions 

By default, anyone can invoke a web action by using the invocation URL.
Access control of the service instance through IAM <br><br> * Verify the user's permissions on the service instance before allowing access.<br><br><br> <br><br> * Maintain responsibility for any service roles that you create for your instances.<br><br><br> 







 Security and regulation compliance 

Security and regulation compliance includes tasks such as security controls implementation and compliance certification.



Table 4. Responsibilities for security and regulation compliance
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 General <br><br> * Maintain controls commensurate to various industry compliance standards.<br> * Monitor, isolate, and recover instances.<br> * Monitor and report the health of instances in the various interfaces.<br> * Secure cluster access through TLS/SSH (data plane in the IBM Services account).<br> * Integrate IBM Analytics Engine with IBM Cloud Identity and Access Management (IAM).<br><br><br> <br><br> * Set up and maintain security and regulation compliance for the IBM Analytics Engine instances.<br><br><br> 







 Disaster recovery 

Disaster recovery includes tasks such as providing dependencies on disaster recovery sites, provision disaster recovery environments, data and configuration backup, replicating data and configuration to the disaster recovery environment, and failover on disaster events.



Table 5. Responsibilities for disaster recovery
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities
Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilities for change management
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Instance provisioning <br><br> * Order hardware (data plane in the IBM services account).<br> * Open the Spark cluster to the internet (data plane in the IBM Services account).<br> * Ensure network isolation of the Spark cluster nodes from other clusters (data plane in the IBM Services account).<br> * Patch the cluster hosts (data plane in the IBM Services account).<br> * Ensure safe erasure of data from removed node or deleted cluster nodes.<br> * Delete hardware (data plane in the IBM Services account)<br><br><br> <br><br> * No change management responsibilities<br><br><br> 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.



Table 3. Responsibilities for identity and access management
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Access control of the service instance through IAM <br><br> * Verify the user's permissions on the service instance before allowing access.<br><br><br> <br><br> * Maintain responsibility for any service roles that you create for your instances.<br><br><br> 







 Security and regulation compliance 

Security and regulation compliance includes tasks such as security controls implementation and compliance certification.



Table 4. Responsibilities for security and regulation compliance
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for.
The replica file share is read-only until you break the replication relationship, creating two independent file shares, or fail over to the replica file share. For more information about setting up replication, see [Creating replica file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create-replication&interface=ui).





 How do I schedule replication? 

You can choose the frequency of replication by creating a schedule with a cronspec and can replicate as frequently as every hour. Set up replication from the UI, CLI, or by calling the API.





 I want to set up replication. Is there automatic failover? 

No, choosing to fail over to the replica site is a manual operation, and you must reconcile your data after the failover to the replica share is done. For more information about how failover works for disaster recovery, see [Failover for disaster recovery](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover&interface=uifs-failover-dr).





 Can I add tags to my file shares? 

Yes. You can specify user and access management tags when you create a file share or update an existing file share. Adding user tags to a file share or replica share can make organizing your resources easier. For more information, see [Add user tags to a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-add-user-tags). File Storage for VPC also supports access management tags. For more information, see [Access management tags for file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-aboutfs-about-mgt-tags).





 What is the dp2 profile? 

The dp2 profile is the latest file storage profile, offering greater capacity and performance for your file shares. With this profile, ou can specify the total IOPS for the file share within the range for a specific file share size.
You can configure the vSphere Web Client to scan VMs, virtual appliances, and vSphere ESXi hosts at specific times or at intervals that are convenient for you.



1. Using the vSphere Web Client, select an object from the inventory. All child objects of the object that you select are also scanned.
2. Select the Monitor tab and click Task & Events.
3. Select Scheduled Tasks and click Schedule a New Task.
4. Select Scan for Updates from the list that appears.
5. On the Edit Settings page, select the types of updates to scan the inventory object for. You must select at least one scan type. On the Scheduling options page, describe and schedule the scan task.
6. Enter a unique name, and optionally, a description for the scan task. Click Change to set the frequency and the start time for the scan task. Click OK.



The scan task is listed in the Scheduled Tasks view of the vSphere Web Client.





 Related links 



* [VMware HCX solution architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx-archi-introhcx-archi-intro)
* [VMware Solutions on IBM Cloud Digital Technical Engagement](https://www.ibm.com/demos/collection/IBM-Cloud-for-VMware-Solutions/) (demonstrations)
(https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/geographic-redundancy.svg)

Figure 2. Local, regional, and global geographic redundancy





 Technical redundancy 

Most public clouds have standardized geographic redundancy, although the various vendors do it in slightly different ways. But technical redundancy is not provided by the cloud vendors. Instead, they provide the tools for customers to build their own technical redundancy. Rather than go into the myriad complexities around technical redundancy, which is a key area for the technical teams building systems, there are a couple of key things to keep in mind when thinking about technical redundancy.

The first is that higher level of availability typically requires higher levels of replication. Thus, in well-designed systems, those with double, triple, and quadruple redundancy, show improvements in availability as the degree of redundancy goes up. “Well designed” hides a lot of complexity in highly available system design.

The second key aspect of technical redundancy that is worth remembering is that more copies does not automatically mean higher availability. There are two reasons for this. First, if there is a design defect, all your copies are likely to fail in a similar way when faced with similar conditions. In the computer world, design defects are normally called software bugs, and they are not rare. The second reason that more copies do not always lead to higher availability is that you need to know when a copy has broken so you can stop using it. If you don't or can't do that, more copies will actually decrease the apparent availability of the system.

The sorts of problems that arise can be seen with a couple of different examples. The first is the old style of home smoke detector that didn’t have a feature to indicate low battery. Without that feature, the homeowner did not have a way of knowing if the detector would work in the case of a fire. This omission could be worked around, and people would replace the battery once a year whether it needed it or not.
NeuralSeek extension setup 

[NeuralSeek](https://neuralseek.com) by [Cerebral Blue](https://cerebralblue.com/) is a combined search and natural-language generation system that is designed to [make conversational AI feel more conversational](https://garrettrowe.medium.com/making-conversational-ai-feel-more-conversational-8748009b3fda). It requires that you load all your content into [IBM Watson® Discovery](https://cloud.ibm.com/catalog/services/watson-discovery). Then, when a user asks a question, it has Discovery search for multiple relevant documents and then it generates a natural-language answer that uses the contents of those documents. In some cases, the answer might be taken directly from a single document, and in others, the answer can include information from multiple sources that are combined into a single coherent statement. For each query, NeuralSeek returns a single answer and a confidence score. In most cases, it also returns a URL of a document that influenced the answer, which might be one of several documents.

To set up the extension for NeuralSeek search:



 Set up IBM Watson® Discovery 



1. You need an instance of [IBM Watson® Discovery](https://cloud.ibm.com/catalog/services/watson-discovery). Because NeuralSeek can modify your data as needed to make it more effective, make sure it is not an instance with important data that you are using for other purposes.
2. In Discovery, create a project and load the documents that you want to use.







 Get the NeuralSeek OpenAPI specification and API Key 



1. You also need an instance of [NeuralSeek on IBM Cloud](https://cloud.ibm.com/catalog/services/neuralseek).
2. In NeuralSeek, open the Configure page and enter your information in the Discovery instance details section.
3. On the Integrate page, and click the OpenAPI file link to download the NeuralSeek.json OpenAPI specification file configured for your instance.
4.
If the buffer in the producer fills up, the producer's send call is delayed, but ultimately might fail with an exception.





 Delivery semantics 

Kafka offers the following multiple different message delivery semantics:



* At most once: Messages might get lost and do not get redelivered.
* At least once: Messages are never lost but there might be duplicates.
* Exactly once: Messages are never lost and there are no duplicates.



The delivery semantics are determined by the following settings:



* acks
* retries
* enable.idempotence



By default, Kafka uses at least once semantics.

To enable exactly once semantics, you must use the idempotent or transactional producers. The idempotent producer is enabled by setting enable.idempotence to true and guarantees that exactly one copy of each message is written to Kafka, even if it retries. The transactional producer enables the sending of data to multiple partitions such that either all messages are successfully delivered, or none of them are. That is, a transaction is either fully committed or fully discarded. You can also include offsets in transactions to build applications that read, process, and write messages to Kafka.





 Code snippets 

These code snippets are at a high level to illustrate the concepts involved. For complete examples, see the Event Streams samples in [GitHub](https://github.com/ibm-messaging/event-streams-samples).

To connect to Event Streams, you first need to build the set of configuration properties. All connections to Event Streams are secured by using TLS and user and password authentication, so you need these properties at a minimum. Replace BOOTSTRAP_ENDPOINTS, USER, and PASSWORD with your own service credentials:

Properties props = new Properties();
props.put("bootstrap.servers", BOOTSTRAP_ENDPOINTS);
props.put("sasl.jaas.config", "org.apache.kafka.common.security.plain.PlainLoginModule required username="USER" password="PASSWORD";");