vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Today, "Vyatta" and "Vyatta OS" describe commercial software adaptations that are derived from that closed source project. IBM VRA incorporates elements of Vyatta OS, along with substantial feature and service enhancements available exclusively through IBM Cloud.

"vRouter" was a short-lived rebranding of Vyatta by its then-owner. When seen in documentation, it can be considered synonymous with Vyatta.
* Is Vyatta 5400 still supported?

IBM no longer supports Vyatta 5400 as of 31 March 2019.
* What about the AT&T vRouter 5600 offering?

AT&T (formerly Brocade) announced the End-of-Life and End-of-Support of their Brocade vRouter 5600 offering. While the Brocade vRouter 5600 provides the underlying technology capability for the IBM Cloud® Virtual Router Appliance, this announcement does not apply to IBM customers. IBM customers continue to have support by using this new offering.
* How is VRA delivered?

You obtain a VRA by ordering a network gateway. This streamlined process allows you to choose a data center and a suitable VRA server, as well specify whether you want to deploy an HA pair of VRAs. Servers, operating systems, and the gateway appliance fixture are all provisioned automatically. When the provisioning is complete, you can use the gateway appliance interface to route VLANs through the VRA. You can configure your VRA server directly by using SSH (Secure Shell) with the passwords that are provided in the Hardware Details section of the IBM Cloud console.
* Is my password safe?

Yes. All VRAs are assigned random passwords visible only to the account holder. Passwords are easily changed, as are SSH public keys and admin IP access restrictions.
* Can I get VRA without a gateway appliance?

Yes, but it can only manage traffic between the VRA's public and private interfaces. VLANs and HA require the gateway appliance fixture.
* Is all network traffic sent through the VRA?
* See [Setting up authorities for image registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registryauthorities-registry).







 12 May 2022 

CLI version 1.31.1 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 05 May 2022 

CLI version 1.31.0 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Added new FAQ topics to Migrating Cloud Foundry information
: 

* [Can I use a custom URL with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faqcustomurl)?
* [Why are my apps slow to respond](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faqapp_response)?



Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).







 April 2022 

Review the release notes for April 2022.



 29 April 2022 

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 27 April 2022 

New! Deploying apps and running jobs with Code Engine is even easier!
: With Code Engine, you can now go from source code to a running app or a configured job with a single command. The app create command automatically runs the container build and deploys your app in a single step. You don't even need to know about building container images or working with registries. Just let Code Engine handle all these processes for you.
Code Engine 

IBM Cloud® Code Engine is a fully managed, serverless platform that runs your containerized workloads, including web apps, micro-services, event-driven functions, or batch jobs. Code Engine represents a service destination, where an incoming notification can be consumed programmatically. For example, an incoming notification about an event can trigger a Code Engine destination to a backend microservice to act based on the content of the incoming notification.



  Configuring a Code Engine destination 

You can configure a IBM Cloud Code Engine destination in the Destinations tab. As part of the configuration, enter the secured URL (only HTTPS), and select the Verb to be called (GET or POST). You can also enter authorization headers to the destination Code Engine. Create a subscription to associate the Code Engine destination to a topic.





  Code Engine retry policy 

When calling Code Engine, issues such as network errors and application glitches can cause the requests to fail. A retry is used to provide resiliency to external requests. Attempt to retry the requests in such situations by using the following values:



*  Limit = 60 seconds: total time that the service retries.
*  Step = 5 seconds: after each failure, the service waits 5 seconds before retrying. This delay prevents bombarding of the external services (Code Engine).



In addition, the following timeout conditions cause the Code Engine call to fail:



*  A connection timeout of 10 seconds
*  A response timeout of 60 seconds



If a call to the URL fails even after retry attempts, the notification is lost.
Complete the following steps to create and update an IBM Cloud Object Storage event subscription for a job from the console.



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions.
3. From the Event subscriptions page, click Create to create your subscription.
4. From the Create an event subscription page, complete the following steps.



1. For Event type, select the Cloud Object Storage tile. Click Next.
2. For General, provide a name for the Object Storage subscription, for example, mycos-job. You can optionally provide event attributes. When the event consumer is a job, event attributes are available as environment variables. Click Next to proceed.
3. For Bucket event details, select or type the name of an existing Object Storage bucket. Specify the types of changes for your object and optionally provide an object name prefix or suffix to filter objects in the bucket to trigger events for the subscription. Click Next to proceed.
4. For Event consumer, specify the job to receive events. Notice that you can choose from a list of defined jobs. For this example, use the myjob job that references the icr.io/codeengine/codeengine image. If your job does not exist, you can specify the name of your job and [create your job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-jobcreate-job-ui) after you create the Object Storage subscription. Click Next to proceed.
5. For Summary, review the settings for your Object Storage event subscription and make changes if needed. When ready, click Create to create the Object Storage subscription.



5. Now that your Object Storage subscription is created, go to the Event subscriptions page to [view a listing of defined subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producerview-eventing-cos-job-ui).
set security firewall name [firewall name] rule [rule number] disable
commit
2. Unhook the entire named rule set from the necessary interface by running:

delete interfaces dataplane [interface] firewall [type] [firewall name]
commit



Incorrect use of these commands can wipe out your interface configuration.
* Why would I want to run two Vyatta devices in a High Availability (HA) pair?

Most cloud customers want HA services. This is so that your workload is hosted on at least two separate (hardware) machines, or even better, in two separate availability zones (think data centers), so that if one fails, the other is able to continue the service. If one machine fails, there is a failover to the other machine, which means that the service can keep running. This is what is referred to as an HA service — it’s almost always available.
* How can I enable root logins to the VRA?

To enable root access through SSH, run the following command:

set service ssh allow-root

Allowing root access that uses SSH is considered unsafe.

An alternative to accessing a root shell is to either log in as another user and elevate to root locally with su -, or allow sudo commands to superusers. For example, to configure the Vyatta as a superuser:

set system login vyatta level superuser
* Why is the Vyatta 5400’s “End of Support” (EoS) on March 31, 2019?

In September 2017, the legacy Vyatta 5400 announced its EoS to be on February 20, 2018. Based on IBM’s lifecycle policy for support, EoS was six months after the General Availability (GA) date of IBM Cloud® Virtual Router Appliance (VRA).

To honor customer migration timelines, the Vyatta 5400 EoS date was extended to March 31, 2019. Because the Debian 7 software is now no longer supported by the Debian Open Source community, there are no future plans to extend vendor support from AT&T.
Why can't I complete an API request to a Watson service? 

You send a request to a Watson API but receive an error message that you don't have permission.

 What’s happening 

When you send a request through a Watson API, you receive a 403 HTTP status code.

For example,

{
"trace":"b0615b07-3a0f-4eb0-8df4-263d64be6b03",
"error":"Forbidden",
"more_info":"https://cloud.ibm.com/docs/watson?topic=watson-forbidden-error",
"code":403
}

 Why it’s happening 

A 403 HTTP status code indicates that you are not allowed to make the request. 403 is similar to [401](https://cloud.ibm.com/docs/watson?topic=watson-authorization-error), but the credential is not authorized for the resource or service instance.

As of 26 May 2021, the watsonplatform.net endpoint URLs are blocked, and calls to that domain return a 403. You might have received email to your IBM Cloud email address with information about this endpoint change.

 How to fix it 

Access in Watson services can be affected by the endpoint URL and by keys, tokens, or service roles that are not authorized.



* Verify the endpoint URL in your call.



* Check that the URL in your call matches the URL in the service instance.
* Make sure that you're not pointing to watsonplatform.net. For more information about the actions to take, see [Updating endpoint URLs from watsonplatform.net](https://cloud.ibm.com/docs/watson?topic=watson-endpoint-change).



* Verify that the API key in your call matches the URL in the service instance.
* Validate the role that is associated with your credentials. The service access role that is associated with your API key determines which endpoints and methods you can access.
Migrating to IBM Support for Hyperledger Fabric 

Customers who are currently operating and using IBM® Blockchain Platform (IBP) network Software as a Service (SaaS) edition must migrate their environment to IBM Support for Hyperledger Fabric by July 31, 2023. This document, along with step-by-step guidance in your console interface, describe how to complete the migration, which will have no impact on your existing data or blockchain network functionality.

Target audience: This topic is designed for network and system administrators who are responsible for planning, configuring and migrating IBM Blockchain networks.



 What is changing? 

In September, 2021, IBM released the IBM Support for Hyperledger Fabric edition, which provides certified images of Hyperledger Fabric open source code, accelerators, and IBM support for Fabric-based blockchain solutions. Given the functional overlap with the IBM Blockchain Platform Software and SaaS editions, IBM will be withdrawing the IBM Blockchain Platform SaaS edition on July 31, 2023. The [IBM Cloud service withdrawal announcement](https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS922-101/index.html&lang=en&request_locale=en) was published on July 26, 2022.





 Why is it changing? 

To maintain a focused development, delivery, and support effort for IBM Blockchain Platform, IBM Support for Hyperledger Fabric best recognizes the opensource foundation of the core code and aligns IBM’s value with support, certification, and accelerators.





 How do I transition my license? 

IBM Blockchain Platform SaaS PayGo customers can transition their license to IBM Support for Hyperledger Fabric during any month, without any existing long-term customer commitment, through coordination with their IBM Blockchain Support team or IBM Account Representative.

IBM Blockchain Platform SaaS subscription customers will be able to transition their license to IBM Support for Hyperledger Fabric at the end of their current subscription commitment, or before July 31, 2023 (whichever comes first), with assistance from their IBM Blockchain Support team or IBM Account Representative.





 Planning and Considerations
A collection of artifacts that define and manage resources and Infrastructure as Code deployments.





 promo code 

A code used to apply limited time credits to Pay-As-You-Go and Subscription accounts.





 proxy 

An application programming interface that forwards requests to a user-defined backend resource and relays responses back to the calling application.





 public cloud 

A cloud computing environment in which access to standardized resources, such as infrastructure, multi-tenant hardware, and services, is available to subscribers on a pay-per-use basis. See also [private cloud](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx4585362), [borderless](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx8439189).





 public gateway 

The connection of a subnet, with all virtual server instances attached, to the internet. A public gateway uses a many-to-1 network address translation (NAT), which means that thousands of virtual server instances with private addresses can use one public IP address to talk to the public internet.





 public resource 

An entry that is visible to everyone in the IBM Cloud catalog. Public resources can be built by any provider (IBM or third party providers). See also [private resource](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9439035).





 publish 

The process of moving an application or product from staging so that the plans and APIs included within it are available for application developers to access and use.





 push 

To send information from a server to a client. When a server pushes content, it is the server that initiates the transaction, not a request from the client.





 push notification 

An alert indicating a change or update on a mobile app icon.







 Q 



 quota 

The number of resources that can be consumed at an account or service instance level.







 R 



 Raft 

A crash fault tolerant ordering service implementation based on the etcd library of the Raft protocol. Raft follows a leader-and-follower model, where a leader node is elected per channel, and its decisions are replicated by the followers.





 read-mostly
The Kafka event subscription defines the relationship between the Kafka producer (sender) and consumer (receiver) of events.

Before you begin



* Determine the Code Engine project that you want to use and make sure that this project is selected. See [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



Complete the following steps to create a Kafka event subscription for an application from the console.



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions.
3. From the Event subscriptions page, click Create to create your subscription.
4. From the Create an event subscription page, select the Event Streams / Kafka tile to specify the event type.
5. For General, provide a name for the Event Streams / Kafka subscription. Click Next to proceed.
6. For Message broker details,



1. Specify the Kafka message broker hosts for the message queues from which messages are received as events through this subscription. To obtain information about the broker hosts, topics, and access credentials, view the service credential details for your service instance in the Event Streams console. For example, specify "broker-0-abcdabcdabcdabcd.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093", "broker-1-abcdabcdabcdabcd.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093" for the message broker hosts for the myeventstream-key service instance.
2. Click Configure to configure access to the message broker. To authenticate from Code Engine to your Kafka or Event Streams instance, you need to provide a message broker access secret.



* You can create a new secret, choose an existing secret, or if credentials are not required to access the message brokers, then choose None.
You can also use the ibmcloud resource service-key myeventstream-key command to retrieve the service key information.
3. Initialize the Event Streams plug-in relative to your Event Streams service instance.

ibmcloud es init --instance-name myeventstream
4. Create an Event Streams topic.

ibmcloud es topic-create kafka-topic1







 Setting up a Code Engine sample app to produce Kafka messages 

For this scenario, let's use a Code Engine application to act as an event producer of Kafka messages. The purpose of this application is to connect to your Event Streams instance and to send Kafka messages. This application uses the [Code Engine Kafka sender sample app](https://github.com/IBM/CodeEngine/tree/main/kafka) to send Kafka messages. This sample sender image requires the BROKERS environment variable and a secret that includes the password credentials. You can create this application from the console or with the CLI.

Make sure that you specify the Content-Type header when you produce Kafka messages to Event Streams. Specify this header so that the consumer can receive messages with the expected content type; for example, application/json.



 Creating a secret with credentials required by the Kafka samples 

Before you create the Code Engine application to send Kafka messages, create a Code Engine secret that contains the required credentials.

Before you begin



* Determine the Code Engine project that you want to use and make sure that this project is selected. See [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



For simplicity in this scenario, create one secret, kafka-subscription-secret, to contain the credentials that are required for both the Kafka sender sample app and the Kafka event subscription, which uses the Kafka receiver sample. These credentials are required for the sample Kafka sender app and the Code Engine Kafka event subscription to communicate with the service instance for Event Streams.
IBM no longer supports Vyatta 5400 as of 31 March 2019.





 What improvements does the IBM Cloud® Virtual Router Appliance (Vyatta 5600) have over the Vyatta 5400? 

Vyatta 5600 offers the following enhancements over the Vyatta 5400:



* Faster throughput, at up to 10 Gbps per CPU core
* Over 3X increased throughput per IPsec VPN session (Advanced Encryption Standards)
* Increased capacity for routers, flows, and concurrent connections
* Updated standards support, including Layer 2 Tunneling Protocol, Version 3 (L2TPv3), Internet Key Exchange, Version 2 (IKEv2), Secure Hash Algorithm 2 (SHA-2), and 802.1Q tunneling (Q-in-Q) encapsulation







 What about the AT&T vRouter 5600 offering? 

AT&T (formerly Brocade) announced the End-of-Life and End-of-Support of their Brocade vRouter 5600 offering. While the Brocade vRouter 5600 provides the underlying technology capability for the IBM Cloud® Virtual Router Appliance, this announcement does not apply to IBM customers. IBM customers continue to have support by using this new offering.





 How is VRA delivered? 

You obtain a VRA by ordering a network gateway. This streamlined process allows you to choose a data center and a suitable VRA server, as well specify whether you want to deploy an HA pair of VRAs. Servers, operating systems, and the gateway appliance fixture are all provisioned automatically. When the provisioning is complete, you can use the gateway appliance interface to route VLANs through the VRA. You can configure your VRA server directly by using SSH (Secure Shell) with the passwords that are provided in the Hardware Details section of the IBM Cloud console.





 Is my password safe? 

Yes. All VRAs are assigned random passwords visible only to the account holder. Passwords are easily changed, as are SSH public keys and admin IP access restrictions.





 Can I get VRA without a gateway appliance? 

Yes, but it can only manage traffic between the VRA's public and private interfaces.
Parametrized circuits With primitives 

Parametrized circuits are a commonly used tool for quantum algorithm design. Because backend.run() did not accept parametrized circuits, the parameter binding step had to be integrated in the algorithm workflow. The primitives can perform the parameter binding step internally, which results in a simplification of the algorithm-side logic.

The following example summarizes the new workflow for managing parametrized circuits.



 Example 

Let's define a parametrized circuit:

from qiskit.circuit import QuantumCircuit, ParameterVector

n = 3
thetas = ParameterVector('θ',n)

qc = QuantumCircuit(n, 1)
qc.h(0)

for i in range(n-1):
qc.cx(i, i+1)

for i,t in enumerate(thetas):
qc.rz(t, i)

for i in reversed(range(n-1)):
qc.cx(i, i+1)

qc.h(0)
qc.measure(0, 0)

qc.draw()
Show more

We want to assign the following parameter values to the circuit:

import numpy as np
theta_values = [np.pi/2, np.pi/2, np.pi/2]





 Legacy 

Previously, the parameter values had to be bound to their respective circuit parameters prior to calling backend.run.

from qiskit import Aer

bound_circuit = qc.bind_parameters(theta_values)
bound_circuit.draw()

backend = Aer.get_backend('aer_simulator')
job = backend.run(bound_circuit)
counts = job.result().get_counts()
print(counts)





 Updated (primitives) 

Now, the primitives take in parametrized circuits directly, together with the parameter values, and the parameter assignment operation can be performed more efficiently on the server side of the primitive.
* [Endpoints to verify connectivity by IBM Cloud multizone metro](https://cloud.ibm.com/docs/satellite?topic=satellite-assign-failsendpoints-to-verify)



[Why does host assign fail with a CRI-O error?](https://cloud.ibm.com/docs/satellite?topic=satellite-host-assign-file-systemhost-assign-file-system)

[Why can't I reuse a host in a different Satellite location?](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-host-reattach-failsat-host-reattach-fail)

[Why can't my HTTP proxy connect to the Red Hat servers?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-http-proxyts-http-proxy)

[Why do my unassigned hosts have an Unresponsive status?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-host-unassigned-unknownts-host-unassigned-unknown)

[Why is my host attach script triggering a state change in Terraform?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-host-terraformts-host-terraform)





 Connectors 

[Debugging Connectors](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-connectordebug-connector)



* [Tunnel cannot be established - Agent does not show up on list of Active Agents](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-connectoragent-not-listed)
* [Tunnel is established - Agent container is listed in the Active Agents tab on the console](https://cloud.ibm.com/docs/satellite?topic=satellite-debug-connectoragent-listed)



[Why can't I reach my endpoint from IBM Cloud?]