vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Ordering a Zerto Cloud Connector 

Optionally order Zerto Cloud Connector (ZCC) as an enhanced Zerto option to link on-premises workloads to IBM Cloud® and replicate on-premises virtual machines (VMs) to IBM Cloud. The Zerto and ZCC services seamlessly integrate as a managed solution to help your enterprise achieve VM replication and disaster recovery. You can order one ZCC per virtual data center.



 Before you begin 

Review the following limitations that currently exist for ZCC:



* You can create a ZCC only if you have a network that is created in VMware® Cloud Director. Ensure that you do not delete that network, either while the ZCC order is in progress or later.
* If you are ordering a Zerto Cloud Connector, you cannot use the following IP subnets for your on-premises Virtual Replication Appliance or Zerto Virtual Manager deployments:



* For the Dallas locations:



* 172.16.3.0/24 - Management
* 10.37.7.0/24 - DAL13
* 10.5.30.0/24 - DAL10
* 10.184.193.0/24 - DAL12



* For the Frankfurt locations:



* 172.16.7.0/24 - Management
* 10.215.201.0/24 - FRA02
* 10.240.220.0/24 - FRA04
* 10.13.28.0/24 - FRA05





* You must create Organization networks before you order a ZCC. For more information, see [Creating a network](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guideshared_vcd-ops-guide-create-network).







 Procedure to order a Zerto Cloud Connector from the virtual data center 



1. Under Enabled services on the virtual data center details page, click Order a Zerto Cloud Connector.
2. Select an organization network and enter the IP address for the new VM to deploy to that network.
3. Review the hourly price and click Order.
To support more user workloads, you can scale the environment by taking the following actions:



* Deploying more compute hosts in existing clusters.
* Deploying more clusters that are managed by the same vCenter Server appliance.
* Deploying new vCenter Server instances with their own vCenter Server appliance.







 VMware vSAN design 

In this design, VMware vSAN storage is employed in vCenter Server instances to provide shared storage for the vSphere hosts.

As shown in the following figure, vSAN aggregates the local storage across multiple ESXi hosts within a vSphere cluster and manages the aggregated storage as a single VM datastore. Within this design, the compute nodes contain local disk drives for the ESXi operating system (OS) and the vSAN datastore. An M.2 SSD drive is included in each node to house the ESXi installation regardless of which cluster a node belongs to.

Zoom

![vSAN concept](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vcsv4radiagrams-ra-vsan.svg)

Figure 2. vSAN concept

vSAN employs the following components:



* Two-disk group vSAN design; each disk group with two or more disks. One SSD or NVMe drive of the smallest size in the group serves as the cache tier and the remaining SSDs serve as the capacity tier.
* The onboard RAID controller is configured in a RAID 0 array for each individual drive that is used for vSAN cache or capacity.
* A single vSAN datastore is created from all storage.



The available vSAN features depend on the license edition that you select when you order the instance. For more information, see [VMware vSAN edition comparison](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution-appendixsolution-appendix-vsan-editions).



 Virtual network setup for vSAN
This example illustrates editing the name of a transit gateway connection:

PATCH
/transit_gateways/{transit_gateway_id}/connections/{id}
{
"name": "Transit_Service_BWTN_SJ_DL",
"prefix_filters_default": "permit"
}







 Response 

The following response shows after you initiate the request:



Table 3. Initiation request

 Response body Details 

 name <br>Always included <br>Name The user-defined name for this transit gateway connection. <br>Possible values: 1 ≤ length ≤ 63, Value must match regular expression `^([a-zA-Z] 
 network_type <br>Always included <br>string Defines what type of network is connected via this connection. The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. <br>Possible values: [classic,directlink,gre_tunnel,unbound_gre_tunnel,vpc] <br>Example:vpc 
 id <br>Always included <br>string The unique identifier for this Transit Gateway Connection <br>Example:1a15dca5-7e33-45e1-b7c5-bc690e569531 
 created_at <br>Always included <br>date-time The date and time that this connection was created 
 base_network_type <br>string Defines the type of network the GRE tunnel targets. This field only applies to unbound_gre_tunnel type connections. The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. 
 network_id <br>string The ID of the network being connected to using this connection. This field is required for some types, such as vpc and directlink For network types vpc and directlink it should be the CRN of the target vpc / gateway respectively.
Virtual Private Cloud

List all VPCs in the targeted resource group. If no resource group is targeted, then all VPCs in the account are listed.

ibmcloud oc vpcs [--provider vpc-gen2] [--output json] [-q]

Minimum required permissions:



* Viewer platform access role for IBM Cloud Kubernetes Service



Command options:

--provider vpc-gen2
: The infrastructure provider type ID for the VPC worker node machine. vpc-gen2 for VPC Generation 2 compute is supported.

--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 vpcs





 flavor command 

Each flavor includes the amount of virtual CPU, memory, and disk space for each worker node in the cluster.

By default, the secondary storage disk directory where all container data is stored, is encrypted with LUKS encryption. If the disable-disk-encrypt option is included during cluster creation, then the host's container runtime data is not encrypted. [Learn more about the encryption](https://cloud.ibm.com/docs/openshift?topic=openshift-securityencrypted_disk).

You can provision your worker node as a virtual machine on shared or dedicated hardware, or for classic clusters only, as a physical machine on bare metal. [Learn more about your flavor options](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes).



 flavor get command 

Virtual Private Cloud

Classic infrastructure

Get the information of a flavor for a zone and provider.

ibmcloud oc flavor get --flavor FLAVOR --provider PROVIDER --zone ZONE [--output OUTPUT] [-q]

Minimum required permissions
: None

Command options:

--flavor FLAVOR
: The flavor you want to get information for.
Create a configuration file for your stateful set and the service that you use to expose the stateful set.

Example stateful set that specifies a zone. The following example shows how to deploy NGINX as a stateful set with 3 replicas. For each replica, a 20 gigabyte File Storage for Classic device is provisioned based on the specifications in the ibmc-file-retain-bronze storage class. All storage devices are provisioned in the dal10 zone. Because File Storage for Classic can't be accessed from other zones, all replicas of the stateful set are also deployed onto worker nodes that are located in dal10.

apiVersion: v1
kind: Service
metadata:
name: nginx
labels:
app: nginx
spec:
ports:
- port: 80
name: web
clusterIP: None
selector:
app: nginx
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: nginx
spec:
serviceName: "nginx"
replicas: 3
podManagementPolicy: Parallel
selector:
matchLabels:
app: nginx
billingType: "hourly"
region: "us-south"
zone: "dal10"
template:
metadata:
labels:
app: nginx
billingType: "hourly"
region: "us-south"
zone: "dal10"
spec:
containers:
- name: nginx
image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
volumeMounts:
- name: myvol
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: myvol
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
iops: "300" required only for performance storage
Adding NFS storage to vCenter Server multizone instances 

New deployments of vCenter Server multizone instances are no longer supported. You can still add and delete clusters, add and remove ESXi servers, and add and delete storage for existing multizone instances.

You can expand the capacity of your VMware vCenter Server® multizone instances by adding NFS storage to the witness and management clusters.



  Before you add NFS storage to vCenter Server multizone instances 



*  Do not add NFS storage from the VMware vSphere® Web Client. The changes that you make on the vSphere Web Client are not synchronized with the IBM Cloud for VMware Solutions console.
*  IBM does not manage NFS file shares that you manually add to an instance.







  Procedure to add NFS storage to vCenter Server multizone instances 



1.  From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2.  In the vCenter Server table, click the instance for which you want to expand capacity.
3.  Click the Infrastructure tab.
4.  In the applicable cluster table, click the cluster to which you want to add NFS storage.
5.  In the Storage section, click Add.
6.  In the Add NFS storage side panel, complete the storage configuration.



*  To add and configure the same settings to all file shares, specify the Number of shares, Size (GB), and Performance.
*  To add and configure file shares individually, toggle the Configure shares individually switch on. Then, click Add shared storage and select the Size (GB) and Performance for each individual file share. You must select at least one file share.



7.  Review the estimated price and click Add.







  Results after you add NFS storage to vCenter Server multizone instances 



1.  You might experience a slight delay on the console while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2.  You are notified by email that your request to add NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3.  If you do not see that the new NFS storage is added to the list in the cluster, check your email or console notifications for more details.
Data included in change requests 

The reference implementation standardizes how a change request is populated in the following sections:



* Description & Plan
* Change Tasks
* Rollback



The change request is populated with content to simplify a compliance audit. It points to the key evidence that is generated by the continuous integration and continuous deployment process. It discloses the minimum set of information that is required; more details can be retrieved from durable storage when needed. For example, the change request contains references to scan logs, but not the actual logs. It also contains the reference to the build BOM, but not the build BOM itself.



 Description and plan section 

The content of the Description and Plan section is organized in the following way:



* CI INVENTORY COMMIT URL The pointer to the Git commit ID that represents your continuous integration inventory. The continuous integration inventory contains information about the code level to be deployed and the artifacts with their signature and checksums to be deployed with this change request.
* CHANGE LOG The list of all of the commit IDs and the description that is included in the code level to be deployed.



Git changelog for mymicroservice:

Git changelog of artifact '"uk.icr.io/mycontainerregistrynamespace/ mymicroservice:devsecops-pipeline4@sha256:733e74a13ad26d77a741204bcdc9c5f8f77023b26620ddaa7842d29b600014a0"'

COMMITS:
94de4256c346c00fee9fd5f7bbfb114ed4da7c81 - implemented myfunction



* PULL REQUESTS



mymicroservicerepo: <PR > - (Merge pull request 15 implemented myfunction)



* TEST AND SCANS RESULTS No issues are found if no failures are reported in the evidence summary or the list of failed IDs. For example, com.ibm.cloud.image_vulnerability_scan: failed; com.ibm.unit_tests: failed), with the abstract of the issues opened so that the approver can view details about what is failing.







 Additional attachments
UID: aa11a1a1-111f-aace-afac-1fa1afe1111a
Spec:
Billing Type: hourly
Mon Size: 20Gi
Mon Storage Class Name: ibmc-vpc-block-10iops-tier
Num Of Osd: 1
Ocs Upgrade: false
Osd Size: 100Gi
Osd Storage Class Name: ibmc-vpc-block-10iops-tier
Status:
Storage Cluster Status:
Events: <none>
4. [Deploy an app that uses ODF](https://cloud.ibm.com/docs/openshift?topic=openshift-odf-deploy-app).





 Scaling ODF 

You can scale your ODF configuration by increasing the numOfOsd setting. When you increase the number of OSDs, ODF provisions that number of disks of the same osdSize capacity in GB in each of the worker nodes in your ODF cluster. However, the total storage that is available to your applications is equal to the osdSize multiplied by the numOfOsd.



Table 1. OpenShift Data Foundation scaling.

 Number of worker nodes Initial osdSize numOfOsd Storage capacity available to applications Total storage of provisioned disks 

 3 150Gi 1 150Gi 450Gi 
 3 150Gi 2 300Gi 900Gi 
 3 150Gi 3 450Gi 1350Gi 
 3 150Gi 4 600Gi 1800Gi 







 Scaling by increasing the numOfOsd 

[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. Get the name of your OcsCluster custom resource.

oc get ocscluster
2. Save your OcsCluster custom resource YAML file to your local machine as ocscluster.yaml.

oc get ocscluster ocscluster-vpc -o yaml
3. Increase the numOfOsd parameter and reapply the ocscluster CRD to your cluster.
A resource reference MUST be a [graph fragment](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-schemasgraph-fragment-pattern) variant of the canonical schema (and, if it exists, the summary schema) for the resource type except for properties that indicate a resource no longer exists.

The resource's unique, immutable handle (usually its id) as represented in the final path parameter of its canonical URI MUST be included in its reference. A human-friendly handle for the resource, such as a user-defined name SHOULD also be included in the reference. If the referenced resource is native to the service in which the reference is returned, its href SHOULD be included. Finally, if the resource has a CRN, its crn property SHOULD also be included. Other properties SHOULD NOT be included in a resource reference.





 Resource identity schemas 

When a related resource is referenced within a request schema (such as a resource prototype), a schema with the name of the related resource's canonical schema, suffixed with Identity, should be used for the same property name used to reference the resource in the response.

For resources native to the service in which the identity is needed, the identifying property MUST be the unique, immutable handle (usually its id) as represented in the final path parameter of the resource's canonical URI and within the canonical schema. For resources external to the service, the crn property SHOULD be used.





 Resource patch schemas 

The request schema used in an operation to update a resource with a [JSON merge patch](https://datatracker.ietf.org/doc/html/rfc7396) SHOULD be the name of the canonical schema for the resource type, suffixed with Patch. In accordance with the JSON merge patch format, this schema MUST be a [graph fragment](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-schemasgraph-fragment-pattern) of the canonical schema, and MUST NOT have any required properties.







 Descriptions 

Every schema and property SHOULD have a description.
If you don't have an Ubuntu Linux virtual server instance, [create an Umbuntu Linux virtual server instance by using the UI and selecting Ubuntu Linux as the Operating System](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).







 Step 2: Provision an IBM Cloud Monitoring instance 

To provision an instance of IBM Cloud Monitoring through the IBM Cloud UI, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud UI opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. To filter the list of services that is displayed, select the Logging and Monitoring category.
4. Click the IBM Cloud Monitoring tile. The Observability dashboard opens.
5. Select the Create tab.
6. Select a region for the service instance.
7. Select the Lite service plan.

By default, the Lite plan is set.

For more information about other service plans, see [Pricing](https://cloud.ibm.com/docs/monitoring?topic=monitoring-pricing_plans).
8. Enter a Service name for the service instance.
9. Select the default resource group.

By default, the default resource group is set.
10. (Optional) Specify any [tags](https://cloud.ibm.com/docs/account?topic=account-tag) you want to use.
11. Select whether of not the service instance receives platform metrics for all service instances in the region.
12. To provision the IBM Cloud Monitoring service in the IBM Cloud resource group where you are logged in, click Create.



After you provision an instance, the Monitoring dashboard opens.
General Availability release, 15 December 2016 

A GA release is now available : The following notes apply to the General Availability (GA) release of IBM Watson™ Discovery.



 General notes 

General notes : Adding content [Update: Adding content](https://cloud.ibm.com/docs/discovery?topic=discovery-addcontent) : [API reference](https://cloud.ibm.com/apidocs/discovery) for current API version. : Integration [Update: Integrating with IBM Watson™ Knowledge Studio](https://cloud.ibm.com/docs/discovery?topic=discovery-integrating-with-wks). : You cannot currently specify the data type of fields. All fields are indexed as text (data type string). : If you use the API to work with the service, you must specify the API version with each call. The current API version is 2016-12-01. The specific version is not enforced in the GA release, but it still must be listed to enable compatibility with future releases. : You can use the service with a custom model created with IBM Watson™ Knowledge Studio. The custom model can be used to enrich ingested documents. You must use the API to integrate the custom model with Discovery; you cannot perform the integration by using the tooling.





 Data management 

Update : Pricing plans [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans)

Data management : Search indexes are not encrypted. : Backup and restore functions are not user controllable.





 Environments 

Update : Pricing plans [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans)

Environments : You can create only one environment per service instance to upload your own data. : Discovery is located in a single availability zone (US South). : Dedicated and Premium plans are not available at the current time.





 Environment sizing 

Update : Pricing plans [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans)
Step 1: Provision an Ubuntu Linux VPC server instance 

If you have an existing Ubuntu Linux virtual server instance you want to monitor, you can skip this step.



1. If you don't have a virtual private cloud, [use the IBM Cloud console to create VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console).
2. If you don't have an Ubuntu Linux virtual server instance, [create an Ubuntu Linux virtual server instance by using the UI and selecting Ubuntu Linux as the Operating System](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).







 Step 2: Provision an IBM Log Analysis instance 

To provision an instance of IBM Log Analysis through the IBM Cloud UI, complete the following steps:



1. Log in to your IBM Cloud account.

Click [Log in to IBM Cloud](https://cloud.ibm.com/login) to sign in to the IBM Cloud.

After you log in with your user ID and password, the IBM Cloud console opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. Select the Logging and Monitoring category.
4. Click the IBM Log Analysis tile.
5. Select a region for the service instance.
6. Select the Lite service plan.

By default, the Lite plan is set.

For more information about other service plans, see [Pricing plans](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).
7. Specify a Service name for your IBM Log Analysis service instance.
8. Select the Default resource group.

By default, the Default resource group is set.
9. To provision the IBM Log Analysis service in the IBM Cloud selected resource group, click Create.



After you provision an instance, the IBM Log Analysis dashboard opens.
IBM Cloud and the 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).

The IBM Watson® IoT Platform is a service that is available in IBM Cloud. You can access your Watson IoT Platform organization dashboard by using your IBM Cloud dashboard. As an IBM Cloud service, Watson IoT Platform can be integrated with other services that are hosted on IBM Cloud. Details of specific third-party service integrations can be found in the [External Service Integrations](https://cloud.ibm.com/docs/services/IoT?topic=IoT-ref-indexref-index) topic.



 How the Watson IoT Platform works with IBM Cloud 

Instances of the Watson IoT Platform can be created in the IBM Cloud dashboard. The Watson IoT Platform can be integrated with other IBM Cloud services and accessed by using the IBM Cloud dashboard, however, Watson IoT Platform does not run on IBM Cloud hardware, which allows for continual data collection by your Watson IoT Platform service.