vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Using quotation marks with strings in IBM Cloud CLI 

Depending on the operating system that you're running IBM Cloud® Command Line Interface on, you use either single or double quotation marks in the command. Linux™, macOS, the Windows™ command prompt (cmd.exe), and Windows™ PowerShell have different quotation-escaping requirements when you run commands. This difference impacts how you pass strings on the IBM Cloud® command line, including JSON content.

For Linux, macOS, or PowerShell, use single quotation marks ('). For the Windows command prompt, use double quotation marks ("). A JSON string requires double quotation marks around each name and value in the JSON structure. For more information, see the following examples.



  Windows command prompt 

For a Windows command prompt, use double quotation marks to surround the JSON data structure. Additionally, you must escape each double quotation mark that is inside the JSON structure by using a backslash before each double quotation mark.

ibmcloud resource service-instance-create my-service-instance db-service lite us-south -p "{"units":1}"





  Linux or macOS 

For Linux or macOS, use single quotation marks to surround the JSON data structure.

ibmcloud resource service-instance-create my-service-instance db-service lite us-south -p '{"units":1}'





  Windows PowerShell 

For PowerShell, use single quotation marks to surround the JSON data structure. Additionally, you must escape each double quotation mark that is inside the JSON structure by using a backslash before each double quotation mark.

ibmcloud resource service-instance-create my-service-instance db-service lite us-south -p '{"units":1}'
: A [new method](https://cloud.ibm.com/apidocs/activity-trackerlist-usage-v2) is available to get aggregate data usage information for an account during a specified time period.





 10 January 2023 

Webhook alerts are enabled for Index Rate alerting.
: For more information, see [Activate the index rate alert feature](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-control_usage_index_rate&interface=uicontrol_usage_index_rate_activate).





 18 November 2022 

New documentation locations for Activity Tracker Event Routing and Activity Tracker hosted event search
: There are now two different locations for Activity Tracker documentation depending on your use case.



* For Activity Tracker Event Routing, see the [Activity Tracker Event Routing documentation.](https://cloud.ibm.com/docs/atracker)
* For Activity Tracker hosted event search, see the [Activity Tracker hosted event search documentation.](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started)







 24 March 2022 

Ability to limit access to private endpoints only
: You can limit access to an IBM Cloud® Activity Tracker instance to private endpoints only. [Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-private_endpoints_only).





 31 January 2022 

Index rate analysis to alert on unexpected data volume spikes
: You can configure index rates alerts in your Activity Tracker instance to monitor and be alerted of unexpected spikes in your data volumes. Use the index rate to analyze and predict costs associated with storage of searchable data. [Learn more about index rate analysis](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-control_usage_index_rate).

Managing and limiting data usage
: In your Activity Tracker instance, you can use the usage quota settings to control how much data is stored so you can manage your data cost while still being able to view and retain the data you need.
Make sure to then set resource quotas as part of the pod specifications. This setting is what Kubernetes uses to select (or schedule) a worker node that has enough capacity to support the request. Estimate how many pods will run on the worker node and the resource requirements for those pods. At a minimum, your worker node must be large enough to support one pod for the app.
7. When to increase the number of worker nodes? You can monitor the cluster usage and increase nodes when needed. See this tutorial to understand how to [analyze logs and monitor the health of Kubernetes applications](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-application-log-analysis).
8. Do you need redundant, reliable storage? If yes, create a persistent volume claim for NFS storage or bind an IBM Cloud database service to your pod.
9. Do you need to deploy a cluster on [Virtual Private Cloud infrastructure](https://cloud.ibm.com/docs/containers?topic=containers-plan_vpc_basics) or in [Classic infrastructure](https://cloud.ibm.com/docs/containers?topic=containers-plan_basics)? VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.



To make the above more specific, let's assume you want to run a production web application in the cloud and expect a medium to high load of traffic. Let's explore what resources you would need:



1. Setup three clusters, one for development, one for testing and one for production.
2. The development and testing clusters can start with minimum RAM and CPU option (for example 2 CPU's, 4GB of RAM and one worker node for each cluster).
3. For the production cluster, you might want to have more resources for performance, high availability, and resiliency. We might choose a dedicated or even a bare metal option and have at least 4 CPU's, 16GB of RAM, and two workers nodes.







 Decide what Database option to use 

With Kubernetes, you have two options for handling databases:



1.
Setting Kafka quotas 

Kafka quotas enforce limits on produce and fetch requests to control the broker resources used by clients. Kafka quotas enable an administrator to enforce limits on the network throughput that can be consumed by individual producer and consumer applications.



 About Kafka quotas 

If left unconstrained, it is possible for a small number of consumers or producers to monopolize the available network throughput for your service instance.

Kafka brokers support quotas that enforce rate limits to prevent clients saturating the network or monopolizing broker resources. For more information, see the [Apache Kafka documentation](https://kafka.apache.org/documentation/design_quotas).

Kafka quotas can be configured to limit network bandwidth usage, Kafka measures this throughput in bytes per second. If throughput over a 30 second window is found to exceed a configured quota, Kafka calculates a sufficient delay to bring throughput within the quota limit.

Kafka brokers then send the delay information to clients as part of standard Kafka protocol responses. A cooperative client, respecting the protocol contract, waits for this delay before making new requests; an uncooperative client may not respect the throttling request, but in such a case, the broker does not read that client's requests until the throttling delay has elapsed (which may cause timeouts on the uncooperative client).

The following information applies for quotas:



* Separate quotas may be defined for producers and consumers.
* By default, client quotas are unlimited.
* Quotas are applied per broker, rather than per cluster.
* A quota is applied to all clients that share a single user identity.
* A quota can be applied to the 'default' user, so it applies to any user, even for whom no user-specific quota was set.







 Client metrics 

The Java client also exposes throttling information with the following per-broker metrics:



* produce-throttle-time-max
* produce-throttle-time-avg
* fetch-throttle-time-max
* fetch-throttle-time-avg







 Setting client quotas
About Watson IoT Platform 

IBM Watson® IoT Platform is deprecated. As of 30 April 2023, only subscribers on paid plans will be able to deploy new instances. The service will be fully withdrawn on 1 December 2023. Any instances that still exist on 1 December 2023 will be deleted. For more information, see [the deprecation details](https://cloud.ibm.com/docs/IoT?topic=IoT-deprecation).

This IBM Cloud® documentation collection pertains to the IBM Watson® IoT Platform Lite pricing plan and includes basic getting started information, API references, and general troubleshooting information. For the full Watson IoT Platform feature documentation, see the [Watson IoT Platform product documentation ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/overview/overview.html) on IBM Knowledge Center. More information about the various plans can be found in [Watson IoT Platform service plans](https://cloud.ibm.com/docs/services/IoT?topic=IoT-plans_overviewplans_overview).

IBM Watson® IoT Platform is a fully managed, cloud-hosted service that makes it simple to derive value from Internet of Things (IoT) devices.

Simply register and connect your device, be it a sensor, a gateway, or something else, to Watson IoT Platform and start sending data securely up to the cloud using the open, lightweight MQTT messaging protocol. You can set up and manage your devices using your online dashboard or our secure APIs, so that your apps can access and use your live and historical data.

To find out more about the overall architecture of the Watson IoT Platform offering, see [Product architecture ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/overview/architecture.html) topic in the full Watson IoT Platform documentation.
"type": "ibm_resource_instance",
"name": "cos_instance",
"provider_config_key": "instance:ibm",
"expressions": {
"location": {
"constant_value": "global"
},
"name": {},
"plan": {
"constant_value": "lite"
},
"service": {
"constant_value": "cloud-object-storage"
}
},
"schema_version": 0
}
]
}
},
"instance_config": {
"source": "./instance_config_module",
"expressions": {
"cos_instance_id": {
"references": [
"module.instance.cos_instance_id",
"module.instance"
]
}
},
"module": {
"resources": [
{
"address": "ibm_cos_bucket.bad_resource_cos_bucket_missing_all_configuration",
"mode": "managed",
"type": "ibm_cos_bucket",
"name": "bad_resource_cos_bucket_missing_all_configuration",
"provider_config_key": "instance_config:ibm",
"expressions": {
"bucket_name": {},
"region_location": {
"constant_value": "us-south"
},
"resource_instance_id": {
"references":
"var.cos_instance_id"
]
},
"storage_class": {
"constant_value": "standard"
}
},
"schema_version": 0,
"count_expression": {
"constant_value": 2
}
}
],
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database node resides on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the nodes are spread over the region's availability zone locations.







 SOC 2 Type 2 Certification 

IBM provides a Service Organization Controls (SOC) 2 Type 2 report for Databases for EnterpriseDB. The reports evaluate IBM's operational controls according to the criteria set by the American Institute of Certified Public Accountants (AICPA) Trust Services Principles. The Trust Services Principles define adequate control systems and establish industry standards for service providers such as IBM Cloud to safeguard their customers' data and information.

You can request an SOC 2 Type 2 report from the customer portal or contact your sales representative. Alternatively, you can open a support ticket with [IBM Cloud support](https://cloud.ibm.com/unifiedsupport/supportcenter)





 ISO 27017, ISO 27018 

Databases for EnterpriseDB conforms to the guidelines for information security controls applicable to the provision and use of cloud services that are defined in [ISO 27017](https://www.iso.org/standard/43757.html) and [ISO 27018](https://www.iso.org/standard/76559.html).





 General Data Protection Regulation (GDPR) 

If you have an account with IBM Cloud, your personal data is held by IBM Cloud. The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client in order to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Databases for EnterpriseDB processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.
Terms and notices 

See [IBM Cloud Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms) for information about the terms of service.

US Health Insurance Portability and Accountability Act (HIPAA) support is available with Enterprise with Data Isolation plans that are hosted in the Washington, DC location created on or after 1 April 2019. For more information, see [Enabling HIPAA support for your account](https://cloud.ibm.com/docs/account?topic=account-enabling-hipaa).

To learn more about service terms and data security, read the following information:



*  [Service terms](https://www.ibm.com/support/customer/csol/terms/) (Search for the Watson Assistant offering)
*  [Data Processing and Protection Datasheet](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=DF7F84500FA711E69DCADF455C6AF151)
*  [IBM Cloud Data security and privacy](https://www.ibm.com/software/sla/sladb.nsf/sla/csdsp?OpenDocument)
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/edit-tagging.svg) in the summary panel to update an existing context.



1. Update the allowed endpoint types.



* Set the toggle to No to allow all service supported endpoint types.
* Set the toggle to Yes to allow only specific endpoint types.



2. Update the nework zones. You can select new network zones or deselect network zones to remove them.



6. Then, click Apply.
7. Click the Remove icon ![Remove icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/delete.svg) in the summary panel to remove a context.
8. Configure a new context by selecting all endpoints or a specific endpoint, and by selecting your network zones. Then, click Add.
9. Click Apply or Continue.
10. Provide a new description for your rule. Click Apply to update the description, or click Continue.
11. To update the enforcement of a rule, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/edit-tagging.svg). You can Enable, Disable, or set the rule to Report-only.
12. Click Apply to finish.







 Updating rules by using the CLI
A list of all IBM Cloud services that are configurable through a virtual private endpoint gateway is at [VPE Supported Services](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-supported-services).

To ensure basic CLI capability against the private endpoint, you must configure the gateway to include these services:



* Account Management: Endpoint URL (https://private.accounts.cloud.ibm.com)
* Global Catalog: [Endpoint URL](https://cloud.ibm.com/apidocs/resource-catalog/global-catalogendpoint-url)
* Global Search: [Endpoint URL](https://cloud.ibm.com/apidocs/searchendpoint-url)
* Global Tagging: [Endpoint URL](https://cloud.ibm.com/apidocs/taggingendpoint-url)
* Usage Metering: [Endpoint URL](https://cloud.ibm.com/apidocs/usage-meteringendpoint)
* Enterprise Management: [Endpoint URL](https://cloud.ibm.com/apidocs/enterprise-apis/enterpriseendpoint-urls)
* Resource Controller: [Endpoint URL](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerendpoint-urls)
* User Management: [Endpoint URL](https://cloud.ibm.com/apidocs/user-managementendpoint-urls)







 Determining which CLI plug-ins support private endpoints 

The [ibmcloud plugin list](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_settingsibmcloud_plugin_list) command reports whether an installed CLI plug-in supports private endpoints. If a plug-in that you use does not show private support, you must continue to use it with your API set to the public endpoint cloud.ibm.com.





 Determining which commands support private endpoints 

The following commands support private endpoints:



* api
Makes it possible to isolate the production and nonproduction networks and install rules that ensure production applications don't accidentally depend on nonproduction resources.
* Scale. Doubles the maximum number of accounts and applications that can be managed.
* Alignment with IBM use. IBM Cloud uses this pattern internally, so it is well tested.



There are some limitations to using multiple enterprises, for example subscription commitments and credits are separately calculated for each enterprise at this time.





 User Access 

In general, users should not be directly provisioned within this account structure. Instead, use [Federated identities](https://cloud.ibm.com/docs/account?topic=account-federated_id) in combination with [trusted profiles](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile) or [dynamic access groups](https://cloud.ibm.com/docs/account?topic=account-rules) to grant access permissions in accounts as required.





 Scaling down 

Not all enterprises will require maximum scale immediately. In this case there are some options to consider:



* Single enterprise account

Place both production and development in a single account. In this case, create a top-level development and production account group that contains the remaining accounts. This makes it easier to separate development and production resources for accounting, compliance, security policy, and so on. A single enterprise cuts maximum scalability of the overall solution in half and results in a single bill.
* Reduced number of business units

Deploy only as many business unit account groups as required. At a minimum, an enterprise can use a single business unit account. Some enterprises might want to consolidate multiple real-world business units into a single business unit account. The single BU approach should be avoided at scale as it does not provide individual business unit autonomy or separation of concerns.
* Reduced number of workload accounts

Deploy only as many workload accounts in each business unit as required. However, it is not recommended to consolidate development and production into a single account.
Initiating the conversion 

Existing IBM Cloud customers can [open an IBM Support case](https://cloud.ibm.com/unifiedsupport/cases/add) through the IBM Cloud console, requesting to be migrated to a VRF. Have the support case state: “Private Network Question” and include the following text:

"We are requesting that account your account number is moved to its own VRF. We understand the risks and approve the change. Reply with the scheduled window(s) of time where this change will be made so we can prepare for the migration."

Migration is completed by the IBM Cloud Network Engineering team. No other information is required from you, except an agreed-to schedule. Intermittent packet loss might last 15 - 30 minutes, depending on the complexity of your account. It might be longer if your account has legacy Direct Link connections. The process is highly automated, requiring minimal interaction by the IBM team.

When you're opening the case, it's recommended to select the Technical support type option, with a category of Networking > Direct Link.
Deployments contain a cluster with three nodes where all the nodes store data and maintain state with a quorum.
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database node resides on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the nodes are spread over the region's availability zone locations.







 SOC 2 Type 2 Certification 

IBM provides a Service Organization Controls (SOC) 2 Type 2 report for Databases for etcd. The reports evaluate IBM's operational controls according to the criteria set by the American Institute of Certified Public Accountants (AICPA) Trust Services Principles. The Trust Services Principles define adequate control systems and establish industry standards for service providers such as IBM Cloud to safeguard their customers' data and information.

You can request an SOC 2 Type 2 report from the customer portal or contact your sales representative. Alternatively, you can open a support ticket with [IBM Cloud support](https://cloud.ibm.com/unifiedsupport/supportcenter)





 ISO 27017, ISO 27018 

Databases for etcd conforms to the guidelines for information security controls applicable to the provision and use of cloud services that are defined in [ISO 27017](https://www.iso.org/standard/43757.html) and [ISO 27018](https://www.iso.org/standard/76559.html).





 General Data Protection Regulation (GDPR) 

If you have an account with IBM Cloud, your personal data is held by IBM Cloud. The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client in order to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Databases for etcd processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.
operator: 'stringEquals',
};
const policyResources = [
{
attributes: accountIdResourceAttribute, serviceTypeResourceAttribute]
},
];
const params = {
type: 'access',
subjects: policySubjects,
roles: policyRoles,
resources: policyResources,
};

iamPolicyManagementService.createPolicy(params)
.then(res => {
examplePolicyId = res.result.id;
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});





 Actions and roles for account management services 

The following tables outline the actions that users can take when they are assigned a specific role for each account management service. Review the information to ensure that you are assigning the correct level of access to your users.



 All Account Management services 

To quickly give users a wide range of account management access, you can assign a policy on all account management services. When a user is assigned a role on All Account Management services, they can complete all of the actions that are associated with that role for each individual service.

The group of All Account Management services includes the following services:



* IAM Access Groups
* IAM Identity service
* IAM Access Management



* Role management



* User Management
* Billing
* Catalog management
* Context-based restrictions
* Enterprise
* Global catalog
* IBM Cloud shell settings
* License and entitlement
* Partner Center
* Partner Center - Sell
* Projects
* Security and Compliance Center
* Software instance
* Support center





Table 2. Roles and example actions for a policy on all account management services

 Roles Actions role_ID value 

 Viewer All viewer role actions for the account management services crn:v1:bluemix:public:iam::::role:Viewer
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 Remote Gateway ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 Integration with HW VTEPs ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 VMware Aria Operations for Logs for NSX 







 vSAN edition comparison 

The following table lists the available features for the vSAN Advanced and Enterprise editions that the solution supports.



Table 5. vSAN edition comparison chart

 vSAN feature Advanced Enterprise 

 Storage policy-based management ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 Flash read/write caching ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) !