vania-janet/multiturn-rag-retrieval-data huggingface dataset:
10,000 - 12,000 1,000 - 48,000 



8. In the side panel, review your order summary, and apply your Promo Code if you have one.

Discounts are applied when the order is processed.
9. Acknowledge that you reviewed the terms and conditions bycheck the appropriate box.
10. Click Create. Your new storage allocation is available in a few minutes.







 Ordering Block Storage for Classic through the SLCLI 

You can use the SLCLI to place orders for products that are normally ordered through the [IBM Cloud console](https://cloud.ibm.com/login).

Each order must have an associated location (data center). When you order Block Storage for Classic, make sure that it is provisioned in the same location as your compute instances.

For more information about how to install and use the SLCLI, see [Python CLI Client](https://softlayer-python.readthedocs.io/en/latest/cli/).

Use the slcli block volume-order command to provision the LUN.

 slcli block volume-order --help
Usage: slcli block volume-order [OPTIONS]

Order a block storage volume.

Options:
--storage-type [performance|endurance]
Type of block storage volume [required]
--size INTEGER Size of block storage volume in GB.
Permitted Sizes:
20, 40, 80, 100, 250, 500,
1000, 2000, 4000, 8000, 12000 [required]
--iops INTEGER Performance Storage IOPs, between 100 and
6000 in multiples of 100 [required for
storage-type performance]
--tier [0.25|2|4|10] Endurance Storage Tier (IOP per GB)
[required for storage-type endurance]
--os-type [HYPER_V|LINUX|VMWARE|WINDOWS_2008|WINDOWS_GPT|WINDOWS|XEN]
Operating System [required]
--location TEXT Datacenter short name (e.g.: dal09)
[required]
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. For more VRRP-specific information, see [Working with High Availability (HA) and VRRP](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-working-with-high-availability-and-vrrp) while synchronizing configuration information can be found at [Synchronizing High Availability (HA) configurations](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-synchronizing-high-availability-configurations).

Note: Gateway appliance is POD-specific. If your application server is spread across different PODs, you need to order more gateways for the PODs that the application server resides in. Configurations synch does not handle cross-POD synchronizing. You need to coordinate to ensure rules that are consistent across PODs.





 IBM Cloud Load Balancers 

When you have multiple servers such as web servers or databases, incoming requests need to be distributed. Load balancers provide this function by sitting in front of the servers, taking incoming requests, and distributing the network or application across a number of backend servers. This distribution allows for higher performance because it increases capacity by allowing more concurrent sessions. A load balancer also provides for a better user experience and availability by preventing a single server from getting overburdened.

IBM Cloud offers several load balancers, including IBM Cloud® Load Balancer and IBM Cloud® Internet Services for the classic infrastructure. For information on all load balancer options, see [IBM Cloud Load Balancers](https://www.ibm.com/cloud/load-balancer).
The portal ordering experience only provides for ordering a single VLAN configuration per order. A configuration consists of the desired network, location option, and quantity. While it is possible to order multiple VLAN configurations in a single order via the API, each configuration quantity is restricted to 1. This means that each VLAN configuration provided is fulfilled independently. Thus, if each configuration utilizes the data center location option, each VLAN can be assigned to different pods within that data center.





 A note about capacity 

An attempt to order a VLAN may be prevented due to capacity restrictions in the location selected. If encountered, it affects all users trying to order VLANs in that location; no recourse is available. If possible, we encourage you to establish a presence in another data center, and consider taking advantage of [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanning). If your location needs are flexible, it's best to use the least specific location option when ordering VLANs, because this allows for greater flexibility in allocating your VLANs. Additionally, VLAN capacity in a previously attempted location can become available at a later time.







 Canceling premium VLANs 

When you are ready to remove a premium VLAN, locate the VLAN in your account's VLAN listing and click Cancel VLAN from the VLAN's overflow menu ![overflow menu](https://cloud.ibm.com/docs-content/v1/content/3fa5994ae9adccdcd1e1af1de40af9e12f188fef/vlans//images/overflow.png).

Premium VLANs cannot be cancelled if they are being used by other products. The following uses prevent cancellation:



* Servers directly homed on the VLAN (as opposed to trunked).
* Firewall products which serve the entire VLAN. This excludes non-dedicated hardware firewalls, for instance.



Additionally, some products and features do not prevent cancellation of a VLAN, but are affected by its removal. This includes being protected by a Virtual Router Appliance.
Order a Citrix Netscaler VPX 

If you haven't already, order your Citrix Netscaler VPX. For instructions on ordering, visit [Getting started with Citrix Netscaler VPX Software Appliance](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-getting-startedgetting-started), and make sure to select 12.1 in step 5.

If 12.1 does not show, proceed with latest version available and upgrade your VPX using instructions in [Upgrade your Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-upgrading-your-citrix-netscaler-vpxupgrading-your-citrix-netscaler-vpx). You can also use the steps in this IBM Cloud® article to upgrade an existing device.

If the 12.1 version is not available in the Cloud repo, contact IBM Cloud Support for additional help.
For more information, see [Grouping keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-grouping-keys). 
 show_total Optional. If set to true, returns totalCount in the response metadata for use with pagination for all keys in an active state, unless allKeyStates is also set to true. The totalCount value returned specifies the total number of key versions that match the request, disregarding limit and offset. The default is set to false. 
 allKeyStates Optional. If not set to true, an HTTP 409 is returned for all non-active keys. 



A successful GET api/v2/keys/<keyID_or_alias>/versions response returns the list of versions that are associated with the root key. The following JSON object shows an example returned value.

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.key.version+json",
"collectionTotal": 2
},
"resources": [
{
"id": "02fd6835-6001-4482-a892-13bd2085f75d",
"creationDate": "2020-03-05T16:39:25Z"
},
{
"id": "12e8c9c2-a162-472d-b7d6-8b9a86b815a6",
"creationDate": "2020-03-02T16:28:38Z"
}
]
}

The resources object lists each key version, along with its ID and creation date, in reverse chronological order.
[Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) 





* The way in which options are presented varies depending on the channel integration. The preference field is supported when possible, but not all channels support drop-down lists or buttons.







 Fields 



 Name Type Description Required? 

 response_type string option Y 
 title string The title to show before the options. Y 
 description string The text of the description that accompanies the options. N 
 preference string The preferred type of control to display, if supported by the channel (dropdown or button). N 
 options list A list of key/value pairs specifying the options from which the user can choose. Y 
 options[].label string The user-facing label for the option. Y 
 options[].value object An object defining the response that will be sent to the Watson Assistant service if the user selects the option. Y 
 options[].value.input object An object that includes the message input corresponding to the option, including input text and any other field that is a valid part of a Watson Assistant message. For more information about the structure of message input, see the [API Reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2?curl=message). N 







 Example 

This example presents two options (Buy something and Exit).

{
"generic":[
{
"response_type": "option",
"title": "Choose from the following options:",
"preference": "button",
"options":
{
"label": "Buy something",
"value": {
"input": {
"text": "Place order"
}
}
},
{
"label": "Exit",
"value": {
"input": {
"text": "Exit"
}
To order a dependent duplicate for a Performance (custom IOPS) volume, make a POST /SoftLayer_Product_Order/placeOrder call like the following REST API example.



* URL - https://USERNAME:APIKEY@api.softlayer.com/rest/v3.1/SoftLayer_Product_Order/placeOrder
* Type - POST
* Request body -

{
"parameters":[{
"complexType": "SoftLayer_Container_Product_Order_Network_Storage_AsAService",
"packageId": 531,
"duplicateOriginVolumeId":<PrimaryId>,
"isDependentDuplicateFlag": 1,
"prices": {"id": 15751}, {"id": 19487}, {"id": 18983}, {"id": 15749}, {"id":14043}],
"quantity": 1,
"iops":456,
"location": 2,
"volumeSize":23
}]
}



For more information about the API and the options, see the [API Reference](https://sldn.softlayer.com/reference/softlayerapi/).





 Managing your duplicate volume 

All duplicate volumes can be accessed by a host for read and write operations as soon as the volume is provisioned.

However, snapshots and replication of independent duplicate volumes aren't allowed until the data copy from the original to the duplicate is complete and the duplicate volume is fully independent. Depending on the size of the data, the separation process can take several hours. When it's complete, the duplicate can be managed and used as an independent volume.

While data is being copied from the original volume to the independent duplicate, you can see that the status indicator on the details page shows the duplication is in progress. During this time, you can attach to a host, and read and write to the volume, but you can't create snapshot schedules or refresh data from the original file share.
oc adm policy add-scc-to-user anyuid system:serviceaccount:dl-reverse-proxy:default
oc apply -f nginx-app.yaml -n dl-reverse-proxy
15. Double check that the NGINX is running by listing pods.

oc get pods

NAME READY STATUS RESTARTS AGE
nginx-757fbc9f85-gv2p6 1/1 Running 0 53s
nginx-757fbc9f85-xvmrj 1/1 Running 0 53s
16. Check logs.

oc logs -f nginx-757fbc9f85-gv2p6

/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
17. Check Ingress.

oc get ingress

NAME CLASS HOSTS ADDRESS PORTS AGE
sendfile on;
keepalive_timeout 65;
server {
listen 80;

server_name <custom_ingress_domain>;

proxy_connect_timeout 180;
proxy_send_timeout 180;
proxy_read_timeout 180;

location / {
proxy_pass https://<tunnel_server_ep>;
proxy_ssl_server_name on;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
}
Show more
3. Create the ConfigMap in your IBM Cloud Kubernetes Service cluster.

kubectl apply -f confnginx.yaml -n dl-reverse-proxy
4. Create a deployment configuration for the NGINX reverse proxy and a service so that the deployment is included in the private Ingress load balancing. Save the file as nginx-app.yaml.

apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx
labels:
app: nginx
spec:
selector:
matchLabels:
app: nginx
replicas: 2
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:alpine
ports:
- containerPort: 80
volumeMounts:
- name: nginx-config
mountPath: /etc/nginx/nginx.conf
subPath: nginx.conf
volumes:
- name: nginx-config
configMap:
name: confnginx
---
apiVersion: v1
kind: Service
metadata:
name: nginxsvc
labels:
app: nginx
spec:
type: NodePort
ports:
- port: 80
For more information about how to set up your environment for your first order, see [Setting up your environment for your first order](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-completing_checklist).





 Step 3: Ordering an instance 

After you set up your environment properly, begin the ordering process.

For more information about how to order an instance, see the following topics based on your selected deployment:



* [Ordering virtual data center instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering)
* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Ordering VMware vSphere instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_orderinginstances-req)
* [Ordering VMware Regulated Workloads instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-req)







 Step 4: Viewing the instance 

After you place an instance order in Step 3, the deployment of the instance starts automatically. You can track the status of the deployment by viewing the instance details. When the instance deployment is completed, you can view the summary and detailed information of the instance and its services on the instance details page too.

For more information about how to view the instance you ordered, see the following topics based on your selected deployment:



* [Viewing and managing virtual data center instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-summary)
* [Viewing vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewinginstances)
Blueprint job us-east.JOB.Blueprint-Basic-Json.59bf17a8 started at 2022-11-21 12:47:26

Module job execution status
Waiting:0 In Progress:0 Success:2 Failed:0

Blueprint job us-east.JOB.Blueprint-Basic-Json.59bf17a8 completed at 2022-11-21 12:50:55

Module Type Name Status Job ID
Blueprint Blueprint Basic Json job_finished us-east.JOB.Blueprint-Basic-Json.59bf17a8
Workspace basic-resource-group INITIALISED
Workspace basic-cos-storage INITIALISED

Blueprint ID blueprint_Basic.eaB.435a job_finished at 2022-11-21 12:50:56
OK





 ibmcloud schematics blueprint delete 

Delete a blueprint. A blueprint can only be deleted once all resources have been destroyed using the destroy command and workspaces are in Inactive state. For more information about the difference between destroy and delete command, see [Deleting a workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-workspace-setup&interface=uidel-workspace).

Syntax

ibmcloud schematics blueprint delete --id BLUEPRINT_ID [—force-delete] [--no-prompt] [--output OUTPUT]

Command options



Schematics blueprint delete flags

 Flag Required / Optional Description 

 --id or -i Required The ID of the blueprint. 
 --force-delete or --fd Optional Force deletes the blueprint including the active module. This action cannot be reversed. 
 --no-prompt Optional Set this flag to stop interactive command-line session. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 



Example

ibmcloud schematics blueprint delete -id blueprint_Basic.eaB.5cd9

Output

Modules to be deleted
SNO Module Type Name Status
sudo systemctl restart nginx







 Apache Tomcat 



1. Order an origin certificate.
2. Copy the private key and origin certificate in PKCS #7 format (cert.p7b) into separate files to the directory on your server where you keep key and certificate files.

You must install the SSL Certificate file to the same keystore and under the same alias name (or, "server") that you used to generate your CSR. The installation in the next step does not work if the SSL Certificate file is installed to a different keystore.
3. Install the certificate. Run the following command to install the SSL Certificate file to your keystore.

keytool -import -trustcacerts -alias server -file cert.p7b -keystore your_site_name.jks

A confirmation message appears: Certificate reply was installed in keystore. Enter y or yes if asked to trust the certificate. Your keystore file (your_site_name.jks) is now ready to use on your Tomcat Server.
4. Configure your SSL connector. Configure an SSL connector for Tomcat to be able to accept secure connections.



1. Open the Tomcat server.xml file in a text editor. The server.xml file is typically located in the conf folder of your Tomcat's home directory.
2. Identify the connector to use to secure the new keystore. A connector with port 443 or 8443 is typically used.
3. Remove any comment tags (<!-- and -->) that might be surrounding the connector.
4. Update the correct keystore filename and password in your connector configuration.



The following example represents a configured SSL Connector block.

<Connector port="443" maxHttpHeaderSize="8192" maxThreads="150"
minSpareThreads="25" maxSpareThreads="75" enableLookups="false"
disableUploadTimeout="true" acceptCount="100" scheme="https"
subPath: nginx.conf
volumes:
- name: nginx-config
configMap:
name: confnginx
---
apiVersion: v1
kind: Service
metadata:
name: nginxsvc
labels:
app: nginx
spec:
type: NodePort
ports:
- port: 80
protocol: TCP
name: http
- port: 443
protocol: TCP
name: https
- port: 8080
protocol: TCP
name: tcp
selector:
app: nginx
Show more
5. Create the deployment and service in your IBM Cloud Kubernetes Service cluster.

kubectl apply -f nginx-app.yaml -n dl-reverse-proxy



The reverse proxy is now configured to terminate incoming connections to your custom Ingress subdomain, open a new connection to the Satellite Link tunnel server, and forward requests to the tunnel server.





 Step 4: Configure Link to use the reverse proxy 

Configure the Link connector in your Satellite location to send traffic over the Direct Link connection to the reverse proxy.



1. To ensure that the Satellite Link configuration change was successful, verify that the location's State is normal.

ibmcloud sat location get --location <location_name_or_ID>
2. Verify that traffic flows from your Satellite location to IBM Cloud by [creating a Link endpoint of type cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-link-cloud-createlink-cloud). For example, you might create a cloud endpoint for the private service endpoint of an IBM Cloud service, and then [test the connection to the service from a Red Hat OpenShift on IBM Cloud cluster that runs in your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-link-cloud-createlink-cloud-test).
3.
Blueprint job us-east.JOB.Blueprint-Basic-Json.59bf17a8 started at 2022-11-21 12:47:26

Module job execution status
Waiting:0 In Progress:0 Success:2 Failed:0

Blueprint job us-east.JOB.Blueprint-Basic-Json.59bf17a8 completed at 2022-11-21 12:50:55

Module Type Name Status Job ID
Blueprint Blueprint Basic Json job_finished us-east.JOB.Blueprint-Basic-Json.59bf17a8
Workspace basic-resource-group INITIALISED
Workspace basic-cos-storage INITIALISED

Blueprint ID blueprint_Basic.eaB.435a job_finished at 2022-11-21 12:50:56
OK





 ibmcloud schematics blueprint delete 

Delete a blueprint. A blueprint can only be deleted once all resources have been destroyed using the destroy command and workspaces are in Inactive state. For more information about the difference between destroy and delete command, see [Deleting a workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks&interface=ui).

Syntax

ibmcloud schematics blueprint delete --id BLUEPRINT_ID [—force-delete] [--no-prompt] [--output OUTPUT]

Command options



Schematics blueprint delete flags

 Flag Required / Optional Description 

 --id or -i Required The ID of the blueprint. 
 --force-delete or --fd Optional Force deletes the blueprint including the active module. This action cannot be reversed. 
 --no-prompt Optional Set this flag to stop interactive command-line session. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 



Example

ibmcloud schematics blueprint delete -id blueprint_Basic.eaB.5cd9

Output

Modules to be deleted
SNO Module Type Name Status
Static Group sg-private-networks net-application and net-db 



To create an IP Set:



1. In the top menu navigation, click on Networking.
2. Click on Edge Gateways and select your virtual data center's Edge Gateway.
3. Under Security, click IP Sets.
4. Click New to create a new IP Set.
5. In the new IP Set window, enter a name and the IP range for this IP Set. In this example, ipset-dnat-to-jump is used as the name and public-ip-0 (the first actual public IP obtained in the previous task) is used.
6. Click Add to add the IP Set then click Save to complete the window.



Repeat the process for the other required IP Sets, or more if needed in your solution.

To create a Static Group:



1. In the top menu navigation, click on Networking.
2. Click on Edge Gateways and select your virtual data center's edge gateway.
3. Under Security, click Static Groups.
4. Click New to create a new Static Group. Enter the name and Click Save.
5. Select the created Static Group and click Manage Members. Select the net-application and net-dbnetworks created in the previous step. Click Save.



Upon completion of these tasks, the new IP Sets and Static Groups will be added.





 Step 4: Create NAT rules to allow virtual machines to access the Internet 

The next step is to create NAT rules to allow your virtual machines to access the public Internet and you to access the virtual machines over the public Internet.

You will create the following NAT rules in this tutorial.



NAT rules

 Name Type External IP Internal IP Application 

 dnat-to-jump DNAT public-ip-0 192.168.100.10/32 N/A 
 snat-to-inet-app SNAT public-ip-1 192.168.100.0/24 N/A 
 snat-to-inet-db SNAT public-ip-1 192.168.101.0/24 N/A