vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQ about Bring Your Own License for VMware 



 What is BYOL and is it supported for VMware perpetual licenses? 

BYOL was a feature available to vCenter Server and VMware vSphere® instances in version 2.0 and later. IBM Cloud previously allowed clients to bring their own licenses (BYOL) when moving their existing on-premises VMware workloads to IBM Cloud. BYOL is no longer allowed by VMware. You can no longer bring your own licenses for any new hosts. This applies to all VMware products that are available through IBM Cloud.

Existing BYOL servers will be able to perform upgrades and migrations to refresh software and hardware.





 Can you use the BYOL feature for some VMware components and purchase monthly licenses for others? 

Yes. You can continue to use the BYOL feature for clusters that already have BYOL. You must purchase licenses from IBM for any new combination of the four VMware components. The IBM Cloud for VMware Solutions console makes it straightforward for you to select the licensing option when you order your instance. Select I will provide, and enter your own license key only if you are performing an upgrade or migration of an existing BYOL cluster.





 For a specific VMware component, can you use BYOL for some licenses and buy the rest of licenses from IBM? 

Yes. If you selected BYOL for a specific VMware component when you created a cluster, you have the following options:



* Continue to use an existing BYOL key.
* Purchase IBM-provided licensing for any new clusters.



Currently, only VMware vSphere Enterprise and VMware vSAN can be licensed per cluster.

You cannot mix and match BYOL and IBM-provided licensing for any VMware component within a cluster.





 Can you use BYOL when you create a cluster? 

No. BYOL is no longer supported except for migrations or upgrades of existing BYOL clusters. Select I will provide, and enter your own license key only if you are performing an upgrade or migration of an existing BYOL cluster.





 How do you manage BYOL licenses? 

You can manage your BYOL licenses by using the VMware vSphere Web Client.
Configuring the V2 Logging agent for Windows 

The logging agent is responsible for collecting and forwarding logs to your IBM Log Analysis instance. After you provision an instance of IBM® Log Analysis, you must configure a logging agent for each log source that you want to monitor.

To configure your Windows server to send logs to your IBM Log Analysis instance, you must install the logdna-agent. The logging agent reads log files from a directory defined in your Windows system and forwards the log data to your logging instance.



 Install the Chocolately package manager 

You need to install the Chocolately package manager to install the Windows agent.

From a command prompt run:

powershell -command "Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))"

or from PowerShell run:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))





 Installing the V2 Logging agent 

To configure your Windows server to forward logs to your logging instance, run the following from a Windows command prompt as an admin user:

choco install logdna-agent -y
logdna-agent -k <INJESTION_KEY> this is your unique Ingestion Key
logdna-agent -s LOGDNA_APIHOST=api.us-south.logging.cloud.ibm.com this is your API server host
logdna-agent -s LOGDNA_LOGHOST=logs.us-south.logging.cloud.ibm.com this is your Log server host
For GitHub, you must also specify where the GitHub instance is located, by using the GH_URL environment variable or --git-api-url field, but it defaults to https://github.ibm.com.

The name of the evidence locker repository can be set by using --org and --repo, or by using the EVIDENCE_LOCKER_REPO_OWNER and EVIDENCE_LOCKER_REPO_NAME environment variables.

By default, the CLI on each invocation ensures that you work with an up-to-date version of a Git locker. This behavior can be disabled by setting COCOA_USE_CACHE to any value except 0, false, no, or n. In this case, the CLI uses its internal cache to look up evidence (much faster), but results might be stale.

Additionally, you can upload evidence and attachments to [Cloud Object Storage](https://www.ibm.com/cloud/object-storage)as well for archiving purposes. It is done automatically when the following environment variables are present:



* COS_ENDPOINT: The [endpoint](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints)where the Cloud Object Storage bucket can be accessed.
* COS_BUCKET_NAME: The name of the Cloud Object Storage bucket.
* COS_API_KEY: An [IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeyuserapikey)or [Service ID API key](https://cloud.ibm.com/docs/account?topic=account-serviceidapikeys&interface=ui)that has write access to the Cloud Object Storage bucket.
* IBM_AUTH_ENDPOINT: The endpoint where the API key can be used to generate an [IAM token](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey&interface=api)(defaults to https://iam.cloud.ibm.com/identity/token){: external}.
* No further jobs can be submitted to the session.
* The session cannot be reopened.







 Sessions and reservations 

IBM Quantum Premium users can access both reservations and sessions on specific backends. Such users should plan ahead and decide whether to use a session or a reservation. You can use a session within a reservation. However, if you use a session within a reservation and some session jobs don't finish during the reservation window, the remaining pending jobs might fail. If you use session inside a reservation we recommend that you set a realistic max_time value.

Zoom

![Diagram showing which job runs next in the queue.](https://cloud.ibm.com/docs-content/v1/content/5f399fa794584e8a662591b494b9a99aa927c74c/quantum-computing/images/jobs-failing.png)

Figure 4. Job selection





 Next steps 

[Run a primitive in a session](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/how_to/run_session.html)
- chown <UID>:<GID> /mount; Replace UID and GID with values from the Dockerfile
volumeMounts:
- name: volume Or you can replace with any name
mountPath: /mount Must match the mount path in the args line

Review the following example Jenkins deployment.

apiVersion: apps/v1
kind: Deployment
metadata:
name: my-pod
spec:
replicas: 1
selector:
matchLabels:
app: jenkins
template:
metadata:
labels:
app: jenkins
spec:
containers:
- name: jenkins
image: jenkins
volumeMounts:
- mountPath: /var/jenkins_home
name: volume
volumes:
- name: volume
persistentVolumeClaim:
claimName: mypvc
initContainers:
- name: permissionsfix
image: alpine:latest
command: ["/bin/sh", "-c"]
args:
- chown 1000:1000 /mount;
volumeMounts:
- name: volume
mountPath: /mount
Show more
5. Create the pod and mount the PVC to your pod.

oc apply -f my-pod.yaml

Is the init container failing? Because Red Hat OpenShift sets restricted security context constraints, you might see an error such as chown: /opt/ibm-ucd/server/ext_lib: Operation not permitted. For your deployment, [use an SCC](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc) that allows chown operations and try again.
6. Verify that the volume is successfully mounted to your pod. Note the pod name and Containers/Mounts path.

oc describe pod <my-pod>

Example output

Name: mypod-123456789
Namespace: default
...
Init Containers:
...
Mounts:
kind: HorizontalPodAutoscaler
metadata:
name: patient-hpa
namespace: example-health
spec:
scaleTargetRef:
apiVersion: apps.openshift.io/v1
kind: DeploymentConfig
name: patient-health-frontend
minReplicas: 1
maxReplicas: 10
metrics:
- type: Resource
resource:
name: cpu
target:
averageUtilization: 1
type: Utilization
Show more
2. Click Create.







 Test Autoscaler 

If you're not running the script to simulate load, the number of pods should stay at 1.



1. Check by opening the Overview page of the deployment config. Click Workloads > DeploymentConfigs and click patient-health-frontend and make sure the Details panel is selected.
2. Start simulating load (see previous section to simulate load on the application).

Zoom

![Scaled to 4/10 pods](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution55-openshift-microservices/ocp48-hpa-after.png)

Scaled to 4/10 pods

It can take a few minutes for the autoscaler to make adjustments.



That's it! You now have a highly available and automatically scaled front-end Node.js application. Red Hat OpenShift is automatically scaling your application pods since the CPU usage of the pods greatly exceeded 1% of the resource limit, 30 millicores.





 Autoscaling from the command line 

You can also can delete and create resources like autoscalars with the command line.



1. Start by verifying the context is your project:

oc project example-health
2. Get the autoscaler that was created earlier:

oc get hpa
3.
Why can't administrators use the console to view all orgs? 

As an administrator, you can't display every organization to administer them when you use the IBM Cloud console. You can display and administer only those organizations to which you belong.

  What’s happening 

As an administrator, you can't view all the organizations from the console.

  Why it’s happening 

This behavior is a limitation of the console.

  How to fix it 

You can use commands such as ibmcloud account orgs and ibmcloud account org-create from the IBM Cloud command-line interface to manage all the organizations.

For a full list of commands, enter ibmcloud account help.
What types of subnets are available with global IP addresses? 

We currently offer global IP addresses as both IPv4 addresses and IPv6 addresses. Our global IPv4 addresses are available as single /32 addresses, while our global IPv6 addresses are available as single /64 addresses.





 Can IPv4 and IPv6 global IP addresses be used interchangeably? 

Because of incompatibility between IP address styles, you cannot use IPv4 and IPv6 global IP addresses interchangeably.





 Can I transfer portable subnet IP addresses between servers? 

Yes. When transferring an IP address from one server to another, make sure that a gratuitous ARP packet is sent. This action allows IBM Cloud's routers to update the ARP entry and forward traffic to the correct server. Not doing so might result in up to a 4-hour delay in the new server receiving traffic for the transferred address.
These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.
3. No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.
4. The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.
5. The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.



TERMINATION This license becomes null and void if any of the above conditions are not met.

DISCLAIMER THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.





 UNIQUE (SLC REQD) 

Debian, Alpine OS & Its Components







 IBM Cloud CLI 

View the [Notices file](https://cloud.ibm.com/media/docs/downloads/oss-licensing-info/IBMCloud-CLI-OSS-Licenses.txt) for the IBM Cloud CLI.

This section consists of the following:



* CC-BY-2.5
* CC-BY-3.0
* CC-BY-4.0
To configure a VM instance for Epic workloads, select the Configure for Epic workloads checkbox on the Boot image tile. You can verify whether the deployed VM supports Epic workloads by checking the corresponding VM details page. On the VM details page, the Deployment type field must be se to Epic.

In the VM details page, for the VMs on which Epic workloads are supported, you must not create or attach volumes from Tier 3 to avoid performance issues.

For the VMs on which Epic workloads are supported and are in shut-down state, you must not change the core type to any value other than dedicated to avoid performance issues.

The following table explains the difference in VM configuration that may or may not support Epic workloads:



Table 2. VM configuration difference that supports non-Epic and Epic workloads

 VM deployed for Storage volume Core type Machine type 

 Non-epic workloads Tier 1 or Tier 3 Shared uncapped, <br>shared capped, or <br>dedicated S922 or E980 
 Epic workloads Always Tier 1 Always dedicated Always E980 



The epic VMs are not pinned by default that you can use internally for non production usage. You must consider pinning the production epic VMs to avoid performance issues.

You can choose to configure a VM for Epic workloads only when you select AIX as your operating system. The other conditions that apply are as follows:



1. Epic workloads is supported on AIX 7.2, and later. You cannot choose AIX 7.1.
2. Supported storage volume is Tier 1. You can change or attach Tier 3 storage volume. This lead, to performance issues.
3. Supported machine type is E980. You cannot select S922.
4. Supported core type is dedicated. You can switch to other core type, but it might lead, to performance issues.
These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.
3. No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.
4. The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.
5. The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.



TERMINATION

This license becomes null and void if any of the above conditions are not met.

DISCLAIMER

THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.





 Unique (SLC REQD) 

Alpine Linux (main) Debian (matching Ubuntu main) UBUNTU (MAIN)







 IBM Cloud Shell 

This section consists of the following:



* CC-BY-1.0
* CC-BY-2.5
* CC-BY-3.0
* CC-BY-4.0
* CC-BY-SA-1.0
* CC-BY-SA-2.0
Displaying the list of agents using the CLI 

You can display the list of agents in your account by using the [agent list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-agent-list) CLI command.

Example

ibmcloud schematics agent list

Output

Retrieving agents...
OK
Name ID Version Description Resource Group Agent Location Schematics location Status Tags Agent health
Agent-UI-Final-Testing Agent-UI-Final-Testing.deA.3dfb cli-testing eu-de Active
Vishwa-CLI-Testing Vishwa-CLI-Testing.deA.ef99 cli-testing eu-de Active
agent-5-multipod agent-5-multipod.deA.3d58 Srikar testing multiple pods in agent-5 ... job-runner eu-de Active agent_register
agent-prod-testing-api-mar-24-2 agent-prod-testing-api-mar-24-2.deA.ca07 1.6.0 Create Agent Default us-south eu-de Active env:prod, mytest
agent-testing-prod-cli-mar-27-2 agent-testing-prod-cli-mar-27-2.deA.727f v1.0.0 Default us-south eu-de Active
agent-testing-prod-cli-mar-27-3 agent-testing-prod-cli-mar-27-3.deA.fd13 Default us-south eu-de Active
agent-testing-prod-cli-mar-27-4 agent-testing-prod-cli-mar-27-4.deA.acd4 Default us-south eu-de Active
agent-testing-prod-cli-mar-27 agent-testing-prod-cli-mar-27.deA.3f7e Default jp-tok eu-de Active
gsmmar27v1cli-agent-test gsmmar27v1cli-agent-test.deA.6288 Default eu-de eu-de Active
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))
2. Run the following command in PowerShell to install NXLog Community Edition.

choco install -y nxlog







 Configure NXLog 



1. Provision a syslog port for NXLog.

To get the required port value, do the following:



1. Access the [IBM Log Analysis UI.](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-launchlaunch_cloud_ui)
2. Click the ![question mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/question_mark.png) to access install instructions.
3. Click NXLog.
4. The syslog port you need to provision in Windows will be displayed. For example, syslog-a.us-south.logging.cloud.ibm.com:63980.



Then, in Windows, do the following:



1. From the Control Panel access System and Security > Windows Defender Firewall.
2. Click Advanced settings.
3. Click Inbound Rules.
4. Click New Rule.
5. Select Port.
6. Click Next.
7. For Specific local ports: enter 63980.
8. Click Next.
9. Select Allow the connection.
10. Click Next.
11. Select where the rule should apply.
12. Click Next.
13.
Another option is to create the directory by using an S3 bucketcompatible tool. Using such tool is not covered in this topic.





 Creating the service instance and credentials for accessing the bucket 



1. Follow the steps under [Service credentials](https://cloud.ibm.com/docs/services/cloud-object-storage/iam?topic=cloud-object-storage-service-credentials) to create the service credentials for accessing the bucket that is handed over to the SAP Data Intelligence installation script. Make sure that you select the Writer role and click Include HMAC Credential.

The credential name in this example is sdiOScred. Choose a name that fits your needs when creating your service credentials.
2. After the service credentials have been created, click View credentials and note the values of access_key_id and secret_access_key. You will need them during the SDI installation dialog later. See below for an example.

...
"cos_hmac_keys": {
"access_key_id": "383cf3",
"secret_access_key": "a240f9"
},
3. Use [Endpoints and storage locations](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints) to find the S3 Host that matches the location where your bucket's created. In the example, it's s3.eu-de.cloud-object-storage.appdomain.cloud.

In a production environment, you should use the private endpoint.











 Installing the Software Lifecycle Container Bridge (SLCB) 

Go directly to the [(RHA) 5.1 Install Software Lifecycle Container Bridge (SLCB)](https://access.redhat.com/articles/5100521sdi-slcb) instructions, and see the next section to learn the specific parameters for IBM Cloud.

You need to copy the downloaded SLCB exectuable (SLCB01_-70003322.EXE) to your working directory $HOME/sap/install and rename it to slcb.
In the Tool Integrations section, click Jenkins.
3. Type the name that you want to display for this tool integration on the Jenkins card in your toolchain.
4. Type the URL for the Jenkins server that you want to open when you click the Jenkins card from your toolchain.
5. Copy the generated toolchain webhook.
6. In your Jenkins server, complete these steps:

a. [Install the IBM Cloud DevOps plug-in](https://wiki.jenkins-ci.org/display/JENKINS/IBM+Cloud+DevOps+PluginIBMCloudDevOpsPlugin-Installingtheplugin).

b. [Configure Jenkins to notify toolchains](https://wiki.jenkins-ci.org/display/JENKINS/IBM+Cloud+DevOps+PluginIBMCloudDevOpsPlugin-Notifyingtoolchains).

c. Return to the Configure the Integration page for the Jenkins tool integration.
7. Click Create Integration.
8. On the Toolchain's Overview page, on the Third-Party tools card, click Jenkins to view the Jenkins server.





 Configuring Jenkins by using the API 

The Jenkins tool integration supports the following configuration parameters that you can use with the [Toolchain HTTP API and SDKs](https://cloud.ibm.com/apidocs/toolchain) when you [create](https://cloud.ibm.com/apidocs/toolchaincreate-tool), [read](https://cloud.ibm.com/apidocs/toolchainget-tool-by-id), and [update](https://cloud.ibm.com/apidocs/toolchainupdate-tool) tool integrations.

You must specify the tool_type_id property in the request body with the jenkins value.



Table 1. Jenkins tool integration parameters

 Parameter Usage Type Terraform argument Description 

 api_token optional, updatable Password api_token The API token to use for Jenkins REST API calls so that DevOps Insights can collect data from Jenkins.
Assembling and compiling a custom crawler plug-in 

After you write the source code for your crawler plug-in, you must assemble and compile it.

IBM Cloud Pak for Data

IBM Cloud Pak for Data only

This information applies only to installed deployments.



  Prerequisites 

You must have the following items to compile a crawler plug-in:



*  Java SE Development Kit 1.8 or higher
*  [Gradle](https://gradle.org/install/)
*  cURL
*  sed (stream editor)
*  Crawler plug-in SDK package, see [Obtaining the crawler plug-in SDK package](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-crawler-plugin-buildobtain-sdk)







  Assembling and compiling the crawler plug-in 



1.  Specify the class name of the crawler plug-in by opening the config/template.xml file and modifying the initial-value of the crawler_plugin_class element.
2.  Ensure that you are in the crawler plug-in SDK directory on your development server.
3.  Enter gradle packageCrawlerPlugin to use Gradle to compile your Java source code and to create a compressed file that includes all of the required components for the crawler plug-in.
4.  Confirm that you have access to the crawler plug-in package, which is in the build/distributions/wd-crawler-plugin-sample.zip file.