vania-janet/multiturn-rag-retrieval-data huggingface dataset:
CRN crn:v1:bluemix:public:is:eu-de:a/a10d63fa66daffc9b9b5286ce1533080::backup-policy:r138-5c719085-cf26-456e-9216-984866659e29
Status pending
Plans ID Name Resource type
r138-07200396-ba41-4d8b-a094-89ab5fadc879 my-plan-b backup_policy_plan

Backup tags dev:test
Backup resource type volume
Resource group defaults
Created at 2023-02-21T22:12:51+00:00

For more information about available command options, see [ibmcloud is backup-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-create).





 Creating a backup policy with multiple plans from the CLI 

Run the ibmcloud is backup-policy-create command and define multiple plans in a JSON format. This example creates two plans, my-policy-plan-a and my-policy-plan-b.

cloudshell:$ ibmcloud is backup-policy-create --match-tags dev:test --name backup-policy-v1 --plans '[{
> "active": true,
> "attach_user_tags":
> "daily-backup-plan"
> ],
> "copy_user_tags": true,
> "cron_spec": "05 15 * * ",
> "clone_policy": {
> "max_snapshots": 4,
> "zones":
> {
> "name": "eu-de-1"
> },
> {
> "name": "eu-de-2"
> }
> ]
> },
> "deletion_trigger": {
> "delete_after": 20,
> "delete_over_count": 20
}
]

For more information about available command options, see [ibmcloud is backup-policy-plans](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencebackup-policy-plans).





 Viewing backup plan details from the CLI 

Run the ibmcloud is backup-policy-plan command and specify the policy ID or policy name, and plan ID or plan name.

ibmcloud is backup-policy-plan POLICY PLAN [--output JSON] [-q, --quiet]

The following example specifies the policy and the plan name.

cloudshell:$ ibmcloud is backup-policy-plan backup-policy-v1 my-policy-plan-a
Getting plan my-policy-plan-a under account Test Account as user test.user@ibm.com...

ID r138-2129a79a-5629-4069-bf79-7bb0af3b0bd3
Name my-policy-plan-a
Active true
Lifecycle state stable
Clone policy Max snapshots Zones
4 eu-de-1,eu-de-2

Deletion trigger Delete after Delete over count
20 20

Remote Region Policies Region Encryption Key Delete over count
us-east - 99

Attached tags daily-backup-plan
Copy tags true
Cron specification 05 15 * * 
Created at 2023-02-21T22:42:31+00:00
Resource type backup_policy_plan

For more information about available command options, see [ibmcloud is backup-policy-plan](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-plan).







 Viewing backup policies and plans with the API 

You can view backup policies and plans by using the API.



 Showing details of a backup policy with the API 

Make a GET /backup_policies/{backup_policy_id} request to show details of a backup policy that is identified by ID.
As part of the IaaS, it is not uncommon to deploy other types of network services for security or remote access. While these services do not help improve the overall availability of the application, they can be a SPOF as the traffic might transit through them. The document does not go into the design but addresses salient points in the context of high availability.



 Direct Link 

Direct link provides you with a way to connect your on-premises resources to IBM Cloud resources in classic infrastructure. There are different types of direct-link offerings that vary by pricing and capabilities. To read more about direct link, refer to the IBM Cloud on [Getting started with IBM Cloud Direct Link on Classic](https://cloud.ibm.com/docs/direct-link?topic=direct-link-get-started-with-ibm-cloud-direct-link).

Regardless of which offering is chosen, keep in mind that by design, direct link is a single link and presents as a SPOF. You can consider ordering two direct links for redundancy to protect against the SPOF. Direct links can provide diverse connections that enable you to achieve redundancy through BGP. More information see [Models for diversity and redundancy in Direct Link on Classic](https://cloud.ibm.com/docs/direct-link?topic=direct-link-models-for-diversity-and-redundancy-in-direct-link).





 Gateway Appliance 

Another network offering that is provided by IBM Cloud is IBM Cloud Gateway Appliance. Gateway Appliance is a specialized appliance that gives you control over network reachability and improves network security for both public and private networks. For more information, see [Getting started IBM Cloud with IBM Cloud Gateway Appliance](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-getting-started).

Gateway Appliance can be ordered alone or in pairs for high availability. The default order is for high availability. When using a gateway appliance for high availability, consider configuring Virtual Router Redundancy Protocol (VRRP) for redundant computer gateways and synchronizing configurations across the appliances.
The list of IBM Log Analysis instances that are available on IBM Cloud is displayed.
4. Select one instance. Then, click Open dashboard.

The logging web UI opens and displays your cluster logs.







 Step 5: View your logs 

From the logging web UI, you can view your logs as they pass through the system. You view logs by using log tailing.

With the Lite service plan, you can only tail your latest logs.





 Next steps 

If you want to [filter cluster logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step5), [search cluster logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step6), [define views](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step7), and [configure alerts](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-alerts), you must upgrade the IBM Log Analysis plan to a paid plan.
Models for diversity in Direct Link 

Customers have the responsibility for creating diversity through their border gateway protocol (BGP) schemas; IBM Cloud® Direct Link is not a redundant service at the cross-connect router (XCR). This document presents possible configurations which can help you find a model for creating the most successful Direct Link deployment to meet your needs. The configurations are arranged in increasing levels of complexity and also according to the Direct Link offering.

Key:



* BCR - Back-end customer router
* XCR - Cross-connect router
* NE - Network Edge





 Influencing route preference using AS prepends 

If the same route prefixes are being advertised to and from IBM Cloud through the BGP session for Direct Link, BGP determines the best path. If the local preference of both paths are equal, such as in the case for Direct Link, the BGP path follows the shortest AS path. Using AS prepends, you can control which path is longest, reducing the priority. The local Autonomous System Number (ASN) on the BGP session is prepended three or more times to the matched route's AS-PATH, artificially increasing that path's length.

The greater the repetition value, the greater the preference is affected. Using three or more AS prepends to your prefixes ensures a significant difference.

You can configure AS prepends when [ordering Direct Link Connect](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-connect), [ordering Direct Link Dedicated](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-dedicated), or [after your direct link is provisioned](https://cloud.ibm.com/docs/dl?topic=dl-prepend-as-paths). A prepend rule is set up with a policy to determine whether the rule will target exported routes (virtual connection routes advertised to on-premises network) or imported routes (on-premises routes being advertised into the IBM Cloud infrastructure), and a repetition value, which determines how many times the local BGP session ASN is applied to routes.
* Plus plans are multi-tenant solutions that provide logical separation of data by using common encryption keys.
* Premium plans are single-tenant solutions that provide physical separation of data. Premium plans provide dedicated data storage accounts that use unique encryption keys.



Users of Premium plans can also integrate with IBM® Key Protect for IBM Cloud® to create, import, and manage their encryption keys. This process is commonly referred to as Bring your own keys (BYOK). For more information about using IBM® Key Protect for IBM Cloud®, see [Protecting sensitive information in your Watson service](https://cloud.ibm.com/docs/speech-to-text?topic=watson-keyservice).





 Network endpoints 

IBM Cloud

IBM Cloud supports both public and private network endpoints with certain plans. Connections to private network endpoints do not require public internet access. Private network endpoints support routing services over the IBM Cloud private network instead of the public network. A private network endpoint provides a unique IP address that is accessible to you without a VPN connection.

Private network endpoints are supported only for paid plans. Check the plan information for your service to learn about the plans that support private network endpoints. For more information, see [Public and private network endpoints](https://cloud.ibm.com/docs/speech-to-text?topic=watson-public-private-endpoints).





 Virtual private endpoints 

IBM Cloud

IBM Cloud® Virtual Private Endpoints for Virtual Private Cloud (VPC) are available with certain plans. Virtual private endpoints enable you to connect to supported IBM Cloud services from your VPC network by using the IP addresses of your choosing, allocated from a subnet within your VPC. Virtual private endpoints are an evolution of the private connectivity to IBM Cloud services. They are virtual IP interfaces that are bound to an endpoint gateway created on a per service or service instance basis.

Virtual private endpoints are supported only for paid plans. Check the plan information for your service to learn about the plans that support virtual private endpoints.
Data backup 

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/dc2670e9228a1dbe562d3d2c7ee63f7a48ba27c3/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).

Use the following information to understand the data backup strategy for IBM Watson® IoT Platform.



 What type of data is backed up? 

The following types of client data are currently backed up as part of the Watson IoT Platform strategy:



* Organizational information
* Device information
* API keys and tokens
* User information
* All records of device management requests including the history of any initiated requests, for example: the current state of the request
* Definitions of custom device management request bundles



Note: All data for an organization is retained for 14 days after service deprovisioning. Contact support within the 14-day window to have an organization restored.





 What type of data is not backed up? 

The following types of data are not backed up in Watson IoT Platform:



* Device events
The following example uses the IBM Cloud CLI to order the bare metal server. However, the following commands are used to capture the required inputs for the bare metal server order:



* ibmcloud sl hardware create-options - lists the available options.
* ibmcloud sl order package-list - lists the packages available. To find packages that support 12 drives, use ibmcloud sl order package-list | grep "12 Drives". The Key Name for the required package is used in a subsequent command.
* ibmcloud sl order category-list BARE_METAL_SERVER - defines what is mandated to be ordered. The Category Code can be used in the subsequent commands.
* ibmcloud sl order item-list <Key Name> --category <Category Code> - lists the options available for each category. For the required bare metal specifications, the following Key Name was selected from the available options when the associated Command was run:





Table 1. Bare metal options

 Key Name Description Command 

 INTEL_INTEL_XEON_5120_2_20 Dual Intel Xeon Gold 5120 (28 Cores, 2.20 GHz) ibmcloud sl order item-list 2U_DUAL_INTEL_XEON_PROCESSOR_SCALABLE_FAMILY_12_DRIVES --category server 
 OS_RHEL_8_X_64_BIT_PER_PROCESSOR_LICENSING Red Hat Enterprise Linux 8.x (64-bit per-processor licensing) ibmcloud sl order item-list 2U_DUAL_INTEL_XEON_PROCESSOR_SCALABLE_FAMILY_12_DRIVES --category os grep RHEL 
 RAM_64_GB_DDR4_2133_ECC_NON_REG 64 GB RAM ibmcloud sl order item-list 2U_DUAL_INTEL_XEON_PROCESSOR_SCALABLE_FAMILY_12_DRIVES --category ram 
 DISK_CONTROLLER_RAID RAID ibmcloud sl order item-list 2U_DUAL_INTEL_XEON_PROCESSOR_SCALABLE_FAMILY_12_DRIVES --category disk_controller
Managing classic infrastructure orders and quotes (ibmcloud sl order) 

Use the following commands from the IBM Cloud® Command Line Interface to manage orders and quotes in your classic infrastructure.



 ibmcloud sl order category-list 

List the categories of a package:

ibmcloud sl order category-list [OPTIONS] PACKAGE_KEYNAME



 Command options 

--required<
: List only the required categories for the package.





 Examples 

This command lists the categories of Bare Metal servers.

ibmcloud sl order category-list BARE_METAL_SERVER







 ibmcloud sl order item-list 

List package items that are used for ordering:

ibmcloud sl order item-list [OPTIONS] PACKAGE_KEYNAME



 Command options 

--keyword
: A word (or string) that is used to filter item names.

--category
: Category code that is used to filter items.





 Examples 

This command lists all items in the VSI package.

ibmcloud sl order item-list CLOUD_SERVER







 ibmcloud sl order package-list 

List packages that can be ordered with the placeOrder API:

ibmcloud sl order package-list [OPTIONS]



 Command options 

--keyword
: A word (or string) that is used to filter package names.

--package-type
: The keyname for the type of package. For example, BARE_METAL_CPU.





 Examples 

This command list out all packages for ordering.

ibmcloud sl order package-list







 ibmcloud sl order package-locations 

List datacenters a package can be ordered in:

ibmcloud sl order package-locations PACKAGE_KEYNAME





 ibmcloud sl order place 

Place or verify an order:

ibmcloud sl order place PACKAGE_KEYNAME LOCATION ORDER_ITEM1,ORDER_ITEM2,ORDER_ITEM3,ORDER_ITEM4... [OPTIONS]



 Command options 

--preset
: The order preset (if required by the package).<

--verify
: Flag denoting whether to verify the order, or not place it.

--quantity
Generally, the SLA availability terms require that when you configure your infrastructure resources in an HA architecture, you must distribute them evenly across three different availability zones. For example, to receive full HA coverage under the SLA terms, you must [set up a multizone cluster](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmz-clusters) with a total of at least 6 worker nodes, two worker nodes per zone that are evenly spread across three zones.





 What compliance standards does the service meet? 

IBM Cloud is built by following many data, finance, health, insurance, privacy, security, technology, and other international compliance standards. For more information, see [IBM Cloud compliance](https://cloud.ibm.com/docs/overview?topic=overview-compliance).

To view detailed system requirements, you can run a [software product compatibility report for IBM Cloud Kubernetes Service](https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html). Note that compliance depends on the underlying [infrastructure provider](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providers) for the cluster worker nodes, networking, and storage resources.

Classic infrastructure: IBM Cloud Kubernetes Service implements controls commensurate with the following security standards:



* EU-US Privacy Shield and Swiss-US Privacy Shield Framework
* Health Insurance Portability and Accountability Act (HIPAA)
* Service Organization Control standards (SOC 1 Type 2, SOC 2 Type 2)
* International Standard on Assurance Engagements 3402 (ISAE 3402), Assurance Reports on Controls at a Service Organization
* International Organization for Standardization (ISO 27001, ISO 27017, ISO 27018)
* Payment Card Industry Data Security Standard (PCI DSS)



VPC infrastructure: IBM Cloud Kubernetes Service implements controls commensurate with the following security standards:



* EU-US Privacy Shield and Swiss-US Privacy Shield Framework
* Health Insurance Portability and Accountability Act (HIPAA)
* International Standard on Assurance Engagements 3402 (ISAE 3402), Assurance Reports on Controls at a Service Organization
[35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/home)

 Latest updates 

[View more](https://cloud.ibm.com/docs/overview?topic=overview-whatsnew)25 April 2023 | Customized compliance validation

In addition to using default controls, you can specify a Security and Compliance Center attachment to validate deployable architectures that you're configuring in a project.

25 April 2023 | Support for deployable architectures onboarded from private or public GitHub repositories

You can now deploy architectures that are onboarded to the catalog from either a private or public GitHub repository. Previously, only deployable architectures onboarded from a public GitHub repository were supported.

17 April 2023 | Check out the new deployable architectures in the catalog

IBM Cloud provides deployable architectures in the IBM Cloud Catalog, which are products that provide automation for the deployment of common architectural patterns that combine one or more cloud resources and are designed for scalability and modularity. Go to the catalog, and filter by Deployable architectures to review the growing catalog of options.
To specify multiple locations, use one option for each location, such as -l dal -l seo.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

Example:

ibmcloud oc subnets -l ams03 -l wdc -l ap





 vlan commands 

Classic infrastructure

List public and private VLANs for a zone and view the VLAN spanning status.



 ibmcloud oc vlan ls 

Classic infrastructure

List the public and private VLANs that are available for a zone in your classic IBM Cloud infrastructure account. To list available VLANs, you must have a paid account.

ibmcloud oc vlan ls --zone ZONE [--all] [--output json] [-q]

Minimum required permissions:



* To view the VLANs that the cluster is connected to in a zone: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service
* To list all available VLANs in a zone: Viewer platform access role for the region in IBM Cloud Kubernetes Service



Command options:

--zone ZONE
: Required: Enter the zone where you want to list your private and public VLANs. To see available zones, run ibmcloud oc zone ls.

--all
: Lists all available VLANs. By default VLANs are filtered to show only those VLANs that are valid. To be valid, a VLAN must be associated with infrastructure that can host a worker with local disk storage.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example vlan ls command 

ibmcloud oc vlan ls --zone dal10







 ibmcloud oc vlan spanning get 

Classic infrastructure

View the VLAN spanning status for an IBM Cloud infrastructure account. VLAN spanning enables all devices on an account to communicate with each other through the private network, regardless of its assigned VLAN.
* UI
* CLI
* API







 Generating a plan 

After you've created your workspace, you need to generate a plan to validate all of the configuration properties.



 Generating a plan using the UI 



1. In the IBM Cloud® console, after the workspace is created, you can review the properties and the variables that are associated with that workspace by using the Settings tab. Make sure to update the following required parameters: api_key, ssh_key_name, ibm_customer_number, and zone.
2. After you review all of the values and make any applicable changes, click Generate plan.
3. When you click Generate plan, a new log is generated that can be viewed in the Jobs tab by clicking Jobs.
4. Review the log file for any errors, fix the properties, and regenerate the plan by clicking Generate plan again.







 Next steps 

After you've successfully generated a plan, you can begin [Applying a plan](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-applying-plan&interface=uiapply-plan-ui) to deploy your IBM Cloud resources to build a IBM Spectrum Symphony cluster instance.





 Generating a plan using the CLI 

Run the following command to generate the plan for your workspace.

ibmcloud schematics plan --id <WORKSPACE_ID>

You can view the log file to look for errors or confirm that the action was completed successfully. You might need to run this command multiple times to track the outcome of the command until it's completed.

ibmcloud schematics logs --id <WORKSPACE_ID>





 Next steps 

After you've successfully generated a plan, you can begin [Applying a plan](https://cloud.ibm.com/docs/ibm-spectrum-symphony?topic=ibm-spectrum-symphony-applying-planapply-plan-cli) to deploy your IBM Cloud resources to build a IBM Spectrum Symphony cluster instance.





 Generating a plan using the API 



1.
New region support
: Osaka region support.





 January 2021 

Apache Kafka upgrade
: Upgrade to Apache Kafka version 2.6 for all plans.





 September 2020 

Scaling support for Enterprise Plan
: [Scale your Enterprise Plan clusters](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_chooseplan_enterprise) to allow for greater throughput and higher retention.





 August 2020 

Mirroring support for Enterprise Plan
: [Mirroring](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-mirroring) enables messages in one service instance to be copied continually to a second instance, allowing disaster recovery scenarios to be implemented easily.

Terraform support
: Create your Event Streams instances and subsequent configuration by using Terraform.





 June 2020 

Schema registry support for Enterprise plan
: Add structure to your messages by using the Event Streams [Schema registry](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-ES_schema_registry).





 March 2020 

Customer metrics support
: Get visibility of metrics for your Enterprise Event Streams instance through a new customer metrics dashboard.





 November 2019 

Apache Kafka upgrade
: Upgrade to Apache Kafka version 2.3.

Bring Your own key for Enterprise plan
: Allows users to secure their data at rest with their own encryption key.

IP Allowlisting support
: Allows users to stipulate source IPs from which users must connect to Event Streams.





 September 2019 

New Lite plan
: Release of the [Lite plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_chooseplan_lite) in US-South allowing users to provision a minimal Event Streams instance for free.





 1 July 2019 

Updates to Enterprise plan
: Apache Kafka version upgrade.
: Support for Cloud Service Endpoints.

Kafka version upgrade
: Event Streams Enterprise supports version 2.2 of Apache Kafka to align with our recently released and upgraded Standard plan.