vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Review the execution plan to verify the type of resource that is planned to be provisioned by Terraform on IBM Cloud.





 Step 5: Executing Terraform apply 

Create your classic infrastructure virtual server. Confirm the creation by entering yes when prompted.

terraform apply

Example output

Creating...

ibm_compute_vm_instance.vm1: Still creating... (40s elapsed)
ibm_compute_vm_instance.vm1: Still creating... (50s elapsed)
ibm_compute_vm_instance.vm1: Still creating... (1m0s elapsed)
ibm_compute_vm_instance.vm1: Creation complete after 1m04s (ID: 62364997)

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.





 Step 6: Running Terraform show 

List the classic infrastructure virtual server that is provisioned.

terraform show

Example output

ibm_compute_vm_instance.vm1:
id = 62364997
block_storage_ids. = 0
cores = 1
datacenter = dal10
...
wait_time_minutes = 90

Optional: Review your classic virtual server instance in the [IBM Cloud](https://cloud.ibm.com/classic/devices) is created.





 Step 7: Executing Terraform destroy 

Optional: Remove your classic infrastructure virtual server.

terraform destroy





 What's next? 



* Explore [Classic infrastructure services](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templateclassic-infra-templates) related templates that you can provision by using Terraform on IBM Cloud.
* Explore [IBM Cloud VPC resources](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc) that you can provision by using Terraform on IBM Cloud.
* [Change log for version 2.1.20, released 17 August 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02120_object_plugin)
* [Change log for version 2.1.19, released 27 July 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02119_object_plugin)
* [Change log for version 2.1.18, released 14 July 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02118_object_plugin)
* [Change log for version 2.1.17, released 28 June 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02117_object_plugin)
* [Change log for version 2.1.16, released 25 May 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02116_object_plugin)
* [Change log for version 2.1.15, released 6 May 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02115_object_plugin)
* [Change log for version 2.1.14, released 13 April 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02114_object_plugin)
* [Change log for version 2.1.13, released 24 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog02113_object_plugin)
* [Change log for version 2.1.19, released 27 July 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02119_object_plugin)
* [Change log for version 2.1.18, released 14 July 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02118_object_plugin)
* [Change log for version 2.1.17, released 28 June 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02117_object_plugin)
* [Change log for version 2.1.16, released 25 May 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02116_object_plugin)
* [Change log for version 2.1.15, released 6 May 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02115_object_plugin)
* [Change log for version 2.1.14, released 13 April 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02114_object_plugin)
* [Change log for version 2.1.13, released 24 March 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02113_object_plugin)
* [Change log for version 2.1.12, released 11 March 2022](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog02112_object_plugin)
The playlist then informs the video player about the video fragments it should fetch, and it provides other data on how to play the streamed content successfully. The .ts files are the video "fragments." These fragments are fetched and played by the video player according to details given in the "playlist."

Now, check and see the format, bit rate, and other information, for the video and audio streams of our source .mp4 video.

ffprobe test-video.mp4

In this example, consider the following stream information for test-video.mp4:



* Video stream 0



* Format - h264
* Format profile - High
* Resolution - 1920x1080
* Bit rate - 438 kb/s
* Frame rate - 30.30 fps



* Audio stream 0



* Format - aac
* Sample rate - 48000
* Bit rate - 128k





Now, convert our test-video.mp4 file into the formats for HLS.

ffmpeg -i test-video.mp4 -c:a aac -ar 48000 -b:a 128k -c:v h264 -profile:v main -crf 23 -g 61 -keyint_min 61 -sc_threshold 0 -b:v 5300k -maxrate 5300k -bufsize 10600k -hls_time 6 -hls_playlist_type vod test-video.m3u8

The following shows the breakdown of what this command did:



Table 1: ffmpeg arguments and descriptions

 Arguments Effect 

 ffmpeg Use the ffmpeg tool. 
 -i test-video.mp4 The source video is at test-video.mp4. 
 -c:a acc Use the acc audio codec for the output. 
 -ar 48000 Set the audio sample rate to 48000 Hz for the output. 
 -b:a 128k Set the audio bit rate to 128000 bits/second for the output. 
 -c:v h264 Use the h.264 video codec for the output. 
 -profile:v main Use the "main" format profile of the selected codec for widest device support.
* [18 November 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-nov1820)



* Review the release notes for 18 November 2020.
* Internal registry
* Service overview





* [October 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-oct20)



* Review the release notes for October 2020.
* [8 October 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-oct0820)



* Review the release notes for 8 October 2020.
* Host network requirements



* [6 October 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-oct0620)



* Review the release notes for 6 October 2020.
* CLI change log
* Location subdomain troubleshooting





* [September 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-sep20)



* Review the release notes for September 2020.
* [14 September 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-sep1420)



* Review the release notes for 14 September 2020.
* Host requirements
* IAM
* Provider documentation
* Service requirements





* [August 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-aug20)



* Review the release notes for August 2020.
* [21 August 2020](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-aug2120)



* Review the release notes for 21 August 2020.
* New! IBM Cloud Satellite is now available as a closed beta.











 Tutorial library for Satellite
[Figure 3 - vSRX HA chassis cluster on vCenter Server interconnections](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vcsvsrx-vsrx-vcs-connections.svg)

Figure 3. vSRX HA chassis cluster on vCenter Server interconnections

Each network adapter that is defined on the vSRX is mapped to a specific interface, depending on whether the vSRX instance is a stand-alone VM or one of a cluster pair for high availability.

Note the following information for the stand-alone mode.



* The fxp0 interface is the out-of-band management interface.
* The ge-0/0/0 interface is the first traffic (revenue) interface.



Note the following information for the cluster mode.



* The fxp0 interface is the out-of-band management interface.
* The em0 interface is the cluster control link for both nodes.
* Any of the traffic interfaces can be specified as the fabric links, such as ge-0/0/0 for fab0 on node 0 and ge-7/0/0 for fab1 on node 1.



The following table shows information for a stand-alone vSRX VM.



Table 1. Interface names and mappings for a standalone vSRX VM

 Network adapter Interface name in Junos OS 

 1 fxp0 
 2 ge-0/0/0 
 3 ge-0/0/1 
 4 ge-0/0/2 
 5 ge-0/0/3 
 6 ge-0/0/4 
 7 ge-0/0/5 
 8 ge-0/0/6 



The following table shows information for a pair of vSRX VMs in a cluster (node 0 and node 1).



Table 2. Interface names and mappings for a pair of vSRX VMs in a cluster (node 0 and node 1)

 Network adapter Interface name in Junos OS
* Trying 169.xx.xxx.xxx...
* TCP_NODELAY set
* Connected to 169.xx.xxx.xxx (169.xx.xxx.xxx) port 30000 (0)
> GET / HTTP/1.1
> Host: 169.xx.xxx.xxx:30000
> User-Agent: curl/7.54.0
> Accept: /
>
< HTTP/1.1 200 OK
< content-length: 58
< cache-control: no-cache
< content-type: text/html
< connection: close
<
<html><body><h1>200 OK</h1>
Service ready.
</body></html>
* Closing connection 0
4. Find the ID of the host that did not return a 200 response. You can compare the Host: 169.xx.xxx.xxx from the previous step with the Worker IP in the output of the following command.

ibmcloud sat host ls --location <location_ID> | grep infrastructure

Example output

Name ID State Status Cluster Worker ID Worker IP
host1 aaaaa1a11aaaaaa111aa assigned Ready infrastructure sat-virtualser-1234... 169.xx.xxx.xxx
host2 bbbbbbb22bb2bbb222b2 assigned Ready infrastructure sat-virtualser-1234... 169.xx.xxx.xxx
host3 ccccc3c33ccccc3333cc assigned Ready infrastructure sat-virtualser-1234... 169.xx.xxx.xxx
5. [Add a host to the control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane) in the same zone so that the location control plane has enough compute resources to continue running when you remove the unhealthy host.
6.
6 Paris
7 Milano
9 Amsterdam
13 Hamburg
14 München
15 Kista
17 Calgary
18 Toronto
19 Boston
20 Seattle
21 Los Angeles
22 Miami
23 Lyon
24 Distrito Federal
25 Tokyo
26 Osaka City
28 Melbourne
29 Bilbao
30 Sao Paulo
31 Kuopio
32 Seoul
33 Singapore

BRANCH_CODE CITY
----------- --------------------------------------------------
34 Shanghai
35 London
36 Birmingham
37 Zürich
38 Heverlee
39 Wien
40 Geneve

29 rows were retrieved.
Show more











 Data visualization & BI 



 Cognos Analytics 

You can run your IBM Cognos® reports against data in the cloud rather than the data in an on-premises database. After you load your data to a Db2 Warehouse on Cloud database, you set up the JDBC driver, and then use the Cognos administration tools to create the database connection.

Watch this video to see how to create a connection.

For more information, see [Connecting Cognos Analytics](https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.ug_cra.doc/c_create_ds.htmlcreate_ds)







 Data science 



 Watson Studio 

After you create a project in IBM Watson Studio (formerly Data Science Experience), you add data assets to it so that you can work with data. All the collaborators in the project are automatically authorized to access the data in the project.

How you add data and from where you can add data differs between legacy and IBM Watson projects. IBM Watson projects use IBM Cloud Object Storage. The project is a legacy project if it uses Object Storage OpenStack Swift.



 To create a new connection in an IBM Watson project: 



1.
* [Change log for worker node fix pack 1.17.17_1555, released 1 March 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1555_worker)
* [Change log for master fix pack 1.17.17_1555, released 22 February 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1555)
* [Change log for worker node fix pack 1.17.17_1553, released 15 February 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1553)
* [Change log for worker node fix pack 1.17.17_1552, released 1 February 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1552)
* [Change log for master fix pack 1.17.17_1551, released 19 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1551_master)
* [Change log for worker node fix pack 1.17.17_1551, released 18 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1551)
* [Change log for master fix pack 1.17.16_1550, released 6 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11716_1550)
* [Change log for worker node fix pack 1.17.15_1549, released 21 December 2020](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11715_1549)
* [Change log for master fix pack 1.17.15_1548, released 14 December 2020](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11715_1548)
* [Revision 14, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-14-change-log)



* [Version 21.04](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-san21.04-change-log)



* [Revision 22, released 19 June 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-21.04-rev-22-change-log)
* [Revision 21, released 21 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-21.04-rev-21-change-log)
* [Revision 20, released 4 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-21.04-rev-20-change-log)
* [Revision 19, released 21 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-21.04-rev-19-change-log)
* [Revision 18, released 6 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-21.04-rev-18-change-log)
* [Revision 17, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-21.04-rev-17-change-log)
cos.Bucket(bucket_name).delete()
print("Bucket: {0} deleted!".format(bucket_name))
except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to delete bucket: {0}".format(e))

SDK References



* Classes



* [Bucket](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlbucket)



* Methods



* [delete](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.Bucket.delete)









 Run a multi-part upload 



 Upload binary file (preferred method) 

The [upload_fileobj](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.Object.upload_fileobj) method of the [S3.Object](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlobject) class automatically runs a multi-part upload when necessary. The [TransferConfig](https://ibm.github.io/ibm-cos-sdk-python/reference/customizations/s3.htmls3-transfers) class is used to determine the threshold for using the multi-part upload.

def multi_part_upload(bucket_name, item_name, file_path):
try:
print("Starting file transfer for {0} to bucket: {1}n".format(item_name, bucket_name))
 set 5 MB chunks
part_size = 1024 * 1024 * 5

 set threadhold to 15 MB
file_threshold = 1024 * 1024 * 15

 set the transfer threshold and chunk size
'num_clbits': 4, 'input_qubit_map': 3, 3], 2, 2], 1, 1], 0, 0]], 'num_qubits': 4,
'method': 'statevector', 'fusion': {'applied': False, 'max_fused_qubits': 5,
'threshold': 14, 'enabled': True}}}])
quasi_dists: [{1: 0.2802734375, 2: 0.2412109375, 0: 0.2392578125, 3: 0.2392578125}]

>> Convert the output to bitstrings
>>binary_quasi_dist = quasi_dists[0].binary_probabilities()
>>> print("binary_quasi_dist: ", binary_quasi_dist)
binary_quasi_dist: {'0001': 0.2802734375, '0010': 0.2412109375, '0000': 0.2392578125, '0011': 0.2392578125}

For information about running noisy simulations with the Runtime primitives, see [this topic](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/how_to/noisy_simulators.html).
* [19 February 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1920)



* CLI change log
* Developing and deploying apps
* Learning paths
* Setting up image build pipelines
* Firewall subnets



* [17 February 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1720)



* Kubernetes version 1.17
* Version change logs



* [14 February 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1420)



* Istio add-on



* [10 February 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1020)



* New! Kubernetes version 1.17
* Deprecated: Kubernetes version 1.14
* VPC cluster creation troubleshooting
* Knative change logs



* [6 February 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb0620)



* Cluster autoscaler
* Tags
* VPC security groups



* [3 February 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb0320)



* Version change log
* Expanded troubleshooting





* [January 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan20)



* [30 January 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan3020)



* Ingress ALB change log
Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce project get --name myproject





 Example output 

Getting project 'myproject'...
OK

Name: myproject
ID: abcdabcd-abcd-abcd-abcd-f1de4aab5d5d
Status: active
Selected: true
Tags: tag1, tag2
Region: us-south
Resource Group: default
Service Binding Service ID: ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
Age: 52d
Created: Fri, 15 Jan 2021 13:32:30 -0500
Updated: Fri, 15 Jan 2021 13:32:45 -0500

Quotas:
Category Used Limit
App revisions 1 100
Apps 1 100
Build runs 0 100
Builds 0 100
Configmaps 2 100
CPU 1.025 64
Ephemeral storage 902625Ki 256G
Instances (active) 1 250
Instances (total) 2 2500
Job runs 1 100
Jobs 1 100
Memory 4400M 256G
Secrets 5 100
Subscriptions (cron) 0 100
Subscriptions (IBM Cloud Object Storage) 0 100







 ibmcloud ce project list 

List all projects.

ibmcloud ce project list [--all-resource-groups] [--output OUTPUT] [--quiet] [--regions REGIONS] [--sort-by SORT_BY]



 Command Options 

--all-resource-groups, --all
: Display projects from all resource groups. By default, projects are only displayed from the current resource group. This value is optional.
New beta FAQ extraction : Released the beta version of [FAQ extraction](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesconnectwebcrawl). This beta feature is only available if you build a search skill in Watson Assistant and configure a web crawl. FAQ extraction automatically extracts question-and-answer pairs from your FAQ web pages so that Watson Assistant returns more precise answers.





 12 August 2020 

Deprecated anomaly detection : Anomaly detection is deprecated and no longer available, effective 12 September 2020. You can no longer apply anomaly detection to a timeslice aggregation.





 30 July 2020 

Improved training data limit : The maximum number of trained collections has been increased from 24 to 40. For more information, see [Training data requirements](https://cloud.ibm.com/docs/discovery?topic=discovery-improving-result-relevance-with-the-apireqs).





 6 May 2020 

Deprecated Element Classification : The Element Classification enrichment deprecation date announced [6 March 2020](https://cloud.ibm.com/docs/services/discovery?topic=discovery-release-notes6mar2020) has been changed. The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.





 6 March 2020 

Change to Element Classification deprecation date : The Element Classification enrichment is deprecated and no longer be available, effective 15 May 2020. Data already in Discovery collections enriched with Element Classification is not affected, nor are any other existing queries or operations affected. You can no longer apply the Element Classification enrichment to any new or existing collection.





 17 January 2020 

New French language support for Discovery News : Released [IBM Watson™ Discovery News](https://cloud.ibm.com/docs/discovery?topic=discovery-watson-discovery-news) in one additional language: French (collection_id: news-fr).





 12 December 2019 

Full support for IBM Cloud IAM : Discovery now supports the full implementation of IBM Cloud Identity and Access Management (IAM). API keys for Watson services are no longer limited to a single service instance.
* [26 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may2620)



* CLI change log
* Image pull secrets
* Ingress status
* NodeLocal DNS cache
* Version change logs



* [20 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may2020)



* New! Virtual Private Cloud Generation 2



* [19 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may1920)



* Istio add-on



* [18 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may1820)



* Ingress ALB change log



* [14 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may1420)



* Kubernetes version 1.18



* [11 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may1120)



* New! Kubernetes version 1.18
* Deprecated: Kubernetes version 1.15
* NodeLocal DNS cache
* Zone-aware DNS beta
* Version change logs



* [8 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may0820)



* CLI change log



* [6 May 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may0620)



* New! IBM Cloud Kubernetes Service observability plug-in
servicePassword = "680b037145f9dc8ef9e6a6d8b480783cbc1d1c12e71a0f4ced6b1eee30a243cd"
serviceURL = "serviceURL = "https://0c869093-c3ee-4a3f-bcec-00f01c8df8d8-bluemix.cloudantnosqldb.appdomain.cloud""
databaseName = "databasedemo"

 Define sample data.
sampleData = [
1, "one", "boiling", 100],
2, "two", "hot", 40],
3, "three", "hot", 75],
4, "four", "hot", 97],
5, "five", "warm", 20],
6, "six", "cold", 10],
7, "seven", "freezing", 0],
8, "eight", "freezing", -5]
]

def main():
 Establish a connection with the service instance.
client = Cloudant(serviceUsername, servicePassword, url=serviceURL)
client.connect()

 Create database and verify it was created.
myDatabaseDemo = client.create_database(databaseName)
if myDatabaseDemo.exists():
print("'{0}' successfully created.n".format(databaseName))

for document in sampleData:
 Retrieve the fields in each row.
number = document[0]
name = document[1]
description = document[2]
temperature = document[3]

 Create a JSON document that represents all the data in the row.
jsonDocument = {
"numberField": number,
"nameField": name,
"descriptionField": description,
"temperatureField": temperature
}

 Create a document by using the Database API.