vania-janet/multiturn-rag-retrieval-data huggingface dataset:
2022-05-27T10:15:38Z
{
"id": "3dab42dc-6941-4841-8d27-4dabcc5aa09e",
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"template": {
"id": "93777bca-baef-4070-b9b5-a2e6079df1b4",
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE"
},
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{
"method": "enc-zero",
"value": "DDFA4A"
}
],
"activation_date": "2027-04-18",
"expiration_date": "2028-06-29",
"tags": [
{
"name": "first-tag",
"value": "for-ibm"
}
],
"created_at": "2022-03-09T11:26:01Z",
"updated_at": "2022-03-09T11:26:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
Your Load Balancer for VPC will not conflict with your Cloud Load Balancer, because DNS domain names are different for these services, and the name of the Load Balancer for VPC is not included in the DNS name.





 load_balancer_insufficient_ips 

Message: The subnet with ID(s) <subnet_id> has insufficient available IPv4 addresses.

In your request, provide a valid subnet with available IPv4 addresses, in which you wish to create the load balancer.





 load_balancer_invalid_description 

Message: Load balancer description <load_balancer_description> is not valid.

A load balancer description cannot exceed 255 characters.





 load_balancer_invalid_is_public 

Message: Value of is_public <load_balancer_is_public> is not valid.

The value of the load balancer parameter is_public must be either true or false.





 load_balancer_invalid_name 

Message: Name <load_balancer_name> is invalid.

Names may not be empty. A valid load balancer name starts with a letter, followed by letters, digits, or underscores. The length of the name may not exceed 40 characters.





 load_balancer_invalid_subnet 

Message: The subnet with ID <subnet_id> is not valid. Make sure to use an existing subnet with 'available' status.

Provide valid subnets that are in available status when entering your request to create a load balancer.





 load_balancer_missing_is_public 

Message: 'is_public' field is missing.

The field is is_public is required. Provide a value for the is_public field.





 load_balancer_missing_name 

Message: Load balancer name is missing.

The load balancer name is a required field. Provide a name for the load balancer.





 load_balancer_missing_subnets 

Message: Load balancer subnets is missing.

The field subnets is required. In your request to create a load balancer, provide information about the subnets in which you wish to create the load balancer.
envWorkloadSignature: Icbm1D/CVpLNYkWRC9e .....







 Getting started with a simple Hyper Protect Virtual Servers for VPC contract 

The following command examples are run on an Ubuntu system.



 1. Get the details of your logging instance 

You can configure logging with IBM Log Analysis or a generic syslog backend. This example uses IBM Log Analysis. There are different plans that you can choose from. To understand how you get the required details including the hostname and the ingestion key, see [Logging for Hyper Protect Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-logging-for-hyper-protect-virtual-servers-for-vpc).





 2. Create the env section 

Ensure that you do not miss the pipe symbol '|' if you are using a plain text contract. It is not required if you are planning to encrypt the section.

env: 
type: env
logging:
logDNA:
hostname: syslog-a.au-syd.logging.cloud.ibm.com
ingestionKey: XXXXXXXXXX
port: 6514





 3. Prepare the docker-compose file 

Assuming that you have the logging details, find a simple docker compose file. The following example has a public NGINX container. Create a docker-compose.yaml by using the example.

services:
nginx:
image: docker.io/library/nginx@sha256:b1306efee704017b0e02efadc011d374063a4e9c47b86bdc57744fc3f0666383
ports:
- 80:80
- 443:443





 4. Get the base64-encoded version of the docker-compose file 

tar -czvf compose.tgz docker-compose.yaml

base64 -i compose.tgz > compose.b64





 5.
Creating and connecting the management and workload VPCs 

After completing the work for [account setup and management](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setup), you can now create the management and workload VPCs from the [VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsi) and connect them using [Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-about).



1. Create two VPCs in a multizone region, one for the management VPC and another for the workload VPC. See [Create a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-clicreate-a-vpc-cli) for more details. For now, you should not follow the instructions in any of the other sections in that reference.

Do not create default address prefixes when you create the VPCs. You can specify manual for the --address-prefix-management argument in the [ibmcloud is vpc-create command](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencevpc-create), such as in ibmcloud is vpc-create my-vpc --address-prefix-management manual.
2. Review [Designing an addressing plan for a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-addressing-plan-design) to get guidance how to plan for addressing within your VPC. VPC uses [Classless Inter-Domain Routing (CIDR) notation](https://cloud.ibm.com/docs/vpc?topic=vpc-choosing-ip-ranges-for-your-vpc) for specifying addresses.
3.
n3392fd orderer4node1-pvc Bound pvc-5fd2b807-2361-406b-802a-a18dbaabe23e 100Gi RWO ibmc-file-bronze 49d
n3392fd orderer5node1-pvc Bound pvc-01da603e-3d2b-4b77-a0ac-af3e70e2d2f5 100Gi RWO ibmc-file-bronze 49d
n3392fd ordererorgca-pvc Bound pvc-e582ef7f-04ae-4493-9bdb-426c784886c3 20Gi RWO ibmc-file-bronze 49d
n3392fd peera-pvc Bound pvc-def5a60c-25f3-4de0-b9cc-2cf8dcf88cc2 100Gi RWO ibmc-file-bronze 49d
n3392fd peera-statedb-pvc Bound pvc-494ba122-3501-4413-b719-cbb4b3a8f91b 100Gi RWO ibmc-file-bronze 49d
n3392fd peerc-pvc Bound pvc-ba9cee42-4d35-48d9-ad05-85afc7256633 100Gi RWO ibmc-file-bronze 48d
n3392fd peerc-statedb-pvc Bound pvc-e945df85-5a32-4d37-991d-b2be334bc09b 100Gi RWO ibmc-file-bronze 48d
n3392fd peerorg1ca-pvc Bound pvc-152be78e-202d-43a4-bcf7-81a6a9013c2d 20Gi RWO ibmc-file-bronze 49d
Show more

To get the details on a particular volume, issue:

kubectl describe pv <VOLUME>
Dealing with overlapping VPC prefixes and classic infrastructure subnets 

A common problem when trying to connect networks is that they may have overlapping VPC prefixes and classic infrastructure subnets. During VPC creation, you set up prefixes and subnets for your private network. You may have chosen the default value, Default address prefixes. This is fine when the VPCs exist in isolation. However, when a transit gateway is used to connect these formerly isolated networks and the networks have VPC prefixes and classic infrastructure subnets that overlap, this can cause networking issues. If traffic does not appear to be routing to the correct network, this could be the issue.

VPCs created this way do not communicate through a transit gateway because all the traffic stays within the local VPC network. Virtual Machines provisioned on different VPCs with the same IP may appear to ping through the transit gateway, but in reality are just pinging themselves.

When creating VPCs that are intended to be interconnected using a transit gateway, make sure to create the VPCs with non-overlapping VPC prefixes. When creating VPCs that are also intended to be interconnected with your IBM Cloud classic infrastructure, do not use prefixes in your VPCs that overlap with the 10.0.0.0/14, 10.200.0.0/14, 10.198.0.0/15, and 10.254.0.0/16 blocks. Also, don't use addresses from your classic infrastructure subnets. To view a list of your classic infrastructure subnets, see [View all subnets](https://cloud.ibm.com/docs/subnets?topic=subnets-view-all-subnets).
For enhanced security, VPN for VPC now supports SHA2-512 (a Secure Hash Algorithm) and DH group 19 (a 256-bit elliptic curve algorithm) to generate a symmetric key.

If you use these new algorithms, be aware that existing client applications will be exposed to those new values in the existing authentication_algorithm and dh_group properties. To avoid disruption, check that client applications are written to gracefully handle unexpected values for these properties before using these new algorithms.

The following VPN for VPC methods have been updated:



* In IKE policies, the authentication_algorithm property now includes a sha512 value, and the dh_group property includes a 19 value.
* In IPsec policies, the authentication_algorithm property now includes a sha512 value, and the pfs property includes a group_19 value.



New VPN gateway property. Each element of the existing VPN gateway members array now includes a private_ip property, which provides the IP address assigned to that VPN gateway member.







 23 February 2021 



 For all version dates 

Application load balancer security group integration. For enhanced security, application load balancers can now be associated with security groups. You can specify one or more security groups when you create the application load balancer, and associate security groups with your existing application load balancers. If you omit security groups during load balancer creation, the default security group for the VPC is used.

If you plan to use default security groups for new application load balancers, review your default security group rules. If necessary, edit the rules to accommodate your expected application load balancer traffic.

The following load balancer methods have been updated:



* [Create a load balancer](https://cloud.ibm.com/apidocs/vpccreate-load-balancer) (POST /load_balancers) can now accept a list of security groups
* [Get load balancer details](https://cloud.ibm.com/apidocs/vpcget-load-balancer) (GET /load_balancers/{id}) now returns references to the security groups to which a load balancer is attached



New security group methods have been added for managing security group targets:
* [Viewing file shares and mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view).
* [Encryption in transit - Securing mount connections between file share and host](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit).
* [Mounting file shares on Red Hat Linux](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-RHEL).
* [Mounting file shares in CentOS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-mount-centos).
* [Mounting file shares on Ubuntu](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-ubuntu).
* [Manage your file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing).
* [Create a file share with replication](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create-replication).
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-retries: "<value>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-idle-connection-timeout: "<value>"
spec:
type: LoadBalancer
selector:

<selector_key>: <selector_value>
ports:
- name: http
protocol: TCP
port: 8080
targetPort: 8080 Optional. By default, the targetPort is set to match the port value unless specified otherwise.
- name: https
protocol: TCP
port: 443
targetPort: 443 Optional. By default, the targetPort is set to match the port value unless specified otherwise.
externalTrafficPolicy: Local Specify Local or Cluster.
Show more

service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-lb-name: "my-load-balancer"
: Optional. Versions 4.11 and later: Include a unique name to make your VPC load balancer persistent. Persistent VPC load balancers are not deleted when the cluster they belong to is deleted. For more information, see [Persistent VPC load balancers](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-lbaasvpc_lb_persist).

service.kubernetes.io/ibm-load-balancer-cloud-provider-enable-features: "proxy-protocol"
: Enable the PROXY protocol. The load balancer passes client connection information, including the client IP address, the proxy server IP address, and both port numbers, in request headers to your back-end app. Note that your back-end app must be configured to accept the PROXY protocol.
Add the outbound rules below:



Outbound rules

 Protocol Source type Source Value 

 TCP Any 0.0.0.0/0 Ports 80-80 
 TCP Any 0.0.0.0/0 Ports 443-443 



5. Repeat the steps above in region 2.







 Configure load balancers 



1. Navigate to Load balancers and click Create.
2. Enter vpc-lb-region1 as the Name, select vpc-region1 as the Virtual Private Cloud, select the resource group, Application load balancer as the Load balancer and Load balancer Type: Public.
3. Select the Subnets of vpc-region1-zone1-subnet and vpc-region1-zone2-subnet..
4. Click Create pool to create a new back-end pool of VSIs that acts as equal peers to share the traffic routed to the pool. Set the parameters with the values below and click Create.



* Name: region1-pool
* Protocol: HTTP
* Session stickiness: None
* Proxy protocol: Disabled
* Method: Round robin
* Health check path: /
* Health protocol: HTTP
* Health port: Leave blank
* Interval(sec): 15
* Timeout(sec): 5
* Max retries: 2



5. Click Attach server to add server instances to the pool.



* From the Subnet dropdown, select vpc-region1-zone1-subnet, select the instance your created and set 80 as the port.
* Click on Attach.
* From the Subnet dropdown, select vpc-region1-zone2-subnet, select the instance your created and set 80 as the port.
* Click Save to complete the creation of a back-end pool.



6. Click Create listener to create a new front-end listener; A listener is a process that checks for connection requests.



* Protocol: HTTP
* Proxy protocol: not checked
* Port: 80
* Back-end pool: region1-pool
* Maximum connections: Leave it empty and click Create.



7.
: Adds a troubleshooting topic for [device set creation failure due to PVC names exceeding the Kubernetes character limit](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ocs-roks-debug).

VPC NLB
: Adds steps for [registering a VPC network load balancer with a DNS record and TLS certificate](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-lbaasvpc_nlb_dns).

Worker node versions
: Worker node fix pack update change log documentation is available for version [4.6.25_1541_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464625_1541), [4.5.37_1537_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4537_1537), [4.4.33_1540_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1540), and [3.11.420_1587_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311420_1587).





 22 April 2021 

HPCS Router
: Updated version change log for the [HPCS Router](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) add-on.





 20 April 2021 

New! Toronto multizone region for VPC
: You can now create clusters on VPC infrastructure in the Toronto, Canada (ca-tor) [location](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zones).





 19 April 2021 

add-on change logs
<prices SOAP-ENC:arrayType="ns1:SoftLayer_Product_Item_Price[3]" xsi:type="SOAP-ENC:Array">
<item xsi:type="ns1:SoftLayer_Product_Item_Price">
<id xsi:type="xsd:int">189433</id> 
</item>
<item xsi:type="ns1:SoftLayer_Product_Item_Price">
<id xsi:type="xsd:int">190233</id> <!-- 2000 - 2999 GBs storage price--><!-- 2000 - 2999 GBs storage price-->
</item>
<item xsi:type="ns1:SoftLayer_Product_Item_Price">
<id xsi:type="xsd:int">190293</id> <!-- 200 - 40000 IOPS price--><!-- 200 - 40000 IOPS price-->
</item>
</prices>
</orderData>
</ns1:placeOrder>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
* Increase capacity on an Endurance storage volume.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://api.service.softlayer.com/soap/v3.1/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<prices SOAP-ENC:arrayType="ns1:SoftLayer_Product_Item_Price[3]" xsi:type="SOAP-ENC:Array">
<item xsi:type="ns1:SoftLayer_Product_Item_Price">
<id xsi:type="xsd:int">189433</id> 
</item>
<item xsi:type="ns1:SoftLayer_Product_Item_Price">
<id xsi:type="xsd:int">190233</id> <!-- 2000 - 2999 GBs storage price--><!-- 2000 - 2999 GBs storage price-->
</item>
<item xsi:type="ns1:SoftLayer_Product_Item_Price">
<id xsi:type="xsd:int">190293</id> <!-- 200 - 40000 IOPS price--><!-- 200 - 40000 IOPS price-->
</item>
</prices>
</orderData>
</ns1:placeOrder>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
* Adjust IOPS on Endurance storage volume.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://api.service.softlayer.com/soap/v3.1/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
hourly_billing: "" => "true"
ip_address_id: "" => "<computed>"
ip_address_id_private: "" => "<computed>"
ipv4_address: "" => "<computed>"
ipv4_address_private: "" => "<computed>"
ipv6_address: "" => "<computed>"
ipv6_address_id: "" => "<computed>"
ipv6_enabled: "" => "false"
local_disk: "" => "false"
memory: "" => "1024"
network_speed: "" => "10"
os_reference_code: "" => "DEBIAN_8_64"
private_network_only: "" => "false"
private_subnet: "" => "<computed>"
private_vlan_id: "" => "<computed>"
public_bandwidth_limited: "" => "<computed>"
public_bandwidth_unlimited: "" => "false"
public_ipv6_subnet: "" => "<computed>"
public_subnet: "" => "<computed>"
public_vlan_id: "" => "<computed>"
secondary_ip_addresses.: "" => "<computed>"
wait_time_minutes: "" => "90"
ibm_compute_vm_instance.vm1: Still creating... (10s elapsed)
ibm_compute_vm_instance.vm1: Still creating... (20s elapsed)
ibm_compute_vm_instance.vm1: Still creating... (30s elapsed)
ibm_compute_vm_instance.vm1: Still creating... (40s elapsed)
ibm_compute_vm_instance.vm1: Still creating... (50s elapsed)
: The name of the storage class that you want to use to provision File Storage for Classic. You can choose to use one of the [IBM-provided storage classes](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_storageclass_reference) or [create your own storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_custom_storageclass). If you don't specify a storage class, the PV is created with the default storage class ibmc-file-bronze.

If you want to use a customized storage class, create your PVC with the corresponding storage class name, a valid IOPS and size.

2. Create the PVC.

oc apply -f mypvc.yaml
3. Verify that your PVC is created and bound to the PV. This process can take a few minutes.

oc describe pvc mypvc

Example output

Name: mypvc
Namespace: default
StorageClass: ""
Status: Bound
Volume: pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
Labels: <none>
Capacity: 20Gi
Access Modes: RWX
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
3m 3m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
26 February 2021 

Block Storage for VPC add-on
: Version 3.0.0 of the Block Storage for VPC add-on is released. Update your clusters to use the latest version. For more information, see the [Block Storage for VPC add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).





 25 February 2021 

CLI change log
: Updated the Red Hat OpenShift on IBM Cloud CLI plug-in change log page for the [release of version 1.0.231](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10).





 23 February 2021 

VPE
: Worker node communication to the Kubernetes master is now established over the [VPC virtual private endpoint (VPE)](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-subnetsvpc_basics_vpe).





 22 February 2021 

Master versions
Planning your file shares 

When you're planning to create File Storage for VPC, you might find this checklist helpful to set up and use the file service.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.



 Planning for creating file shares 

Consider the following prerequisites before you set up File Storage for VPC.



Table 1. Checklist for planning file shares

 Considerations 

 __ Check your [IAM access permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfile-storage-vpc-iam) to ensure you can create file shares. 
 __ Think about the location and resources where you're going to use the file share. The file share needs to be mounted to a compute resource within a VPC. Identify an existing VPC or create a [VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console). 
 __ To mount a file share on a virtual server instance, you must create at least one mount target. You can create a mount target along with the file share and add more mount targets separately later. 
 __ Decide whether you want to [restrict access](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-aboutfs-mount-access-mode) to the file share from one specific virtual server instance or allow mounting on all virtual server instances within a VPC. <br><br>New 
 __ Evaluate the capacity and performance that you need. The dp2 profile provides ample flexibility in this regard. The range of total IOPS that you can specify is based on the size of the file share. You can provision shares with IOPS performance from 100 IOPS (default minimum) to 96,000 IOPS.
You can choose to use one of the [IBM-provided storage classes](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_storageclass_reference) or [create your own storage class](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_custom_storageclass). If you don't specify a storage class, the PV is created with the default storage class ibmc-file-bronze.

If you want to use a customized storage class, create your PVC with the corresponding storage class name, a valid IOPS and size.

2. Create the PVC.

kubectl apply -f mypvc.yaml
3. Verify that your PVC is created and bound to the PV. This process can take a few minutes.

kubectl describe pvc mypvc

Example output

Name: mypvc
Namespace: default
StorageClass: ""
Status: Bound
Volume: pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
Labels: <none>
Capacity: 20Gi
Access Modes: RWX
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
3m 3m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibm.io/ibmc-file", expecting that a volume for the claim is provisioned either manually or via external software