vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Provision script Provisioning scripts are commonly used to apply a customer-specific configuration to a server and to aid in automation of your scaling strategy. Provisioning scripts can be any file that the operating system (OS) can run, including combined binary files or any OS-supported language. Provisioning scripts can't be used on cloud-init images. For more information, see [Provisioning scripts](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-provisioning-scripts). 
 User data You can add user data that automatically performs common configuration tasks or runs scripts. User data can be used on cloud-init and non-cloud-init images. 







 Attached storage disks 

If you need extra storage, you can attach storage disks to your instance. The type of storage disks that are available to you depend on the profile that you select. For example, balanced local profiles and a few of the GPU profiles use local storage disks. If you select monthly billing, you can add IBM Cloud Backup for Classic and choose the option that best fits your needs. For more information, see [IBM Cloud Backup for Classic services](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-started).





 Network interface 



Table 3. Network interface options

 Field Details 

 Uplink port speeds You can select the uplink speed for your instance, up to 1 Gbps. These virtual uplinks are backed by redundant physical uplinks to the IBM public and dedicated networks. The public and dedicated speed is always the same at the time of order, with the option to upgrade or downgrade a link if needed. If you select the 100 Mbps rate-limited option, the maximum instance throughput is limited only by the physical bandwidth available to the virtual server host. If you select the 1 Gbps non rate-limited option, you can achieve higher network performance through extra configuration. For more information, see [Configuring virtual server settings for improved network performance](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-configuring-network-performance).
[Ensure that all deployed software meets all control requirements](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-self-installed-software) <br><br> * Consider the software that you plan to install into your workload clusters in your Satellite location. Ensure that software is developed, deployed, configured, and managed in a way that is consistent with the control requirements.<br><br><br> <br><br> * Consider the pieces of software that you plan to install into any part of your underlying infrastructure in your Satellite location or your supporting on-premises environment outside of Satellite. Ensure that software is developed, deployed, configured, and managed in a way that is consistent with the control requirements.<br><br><br> 
 [Implement a system of account, identity, and access management to enable a zero trust environment](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-zero-trust) <br><br> * For accounts and resources in IBM Cloud, use IBM Cloud IAM for account, identity, and access management for IBM Cloud.
For more information about the process of collecting the required diagnostic information for VMware NSX® Edge™ devices, see [Collecting diagnostic information for VMware NSX Edge (2079380)](https://kb.vmware.com/s/article/2079380?lang=en_USq=Collecting%20diagnostic%20information%20for%20VMware%20NSX%20Edge%20). 







 VM procedures 



Table 2. VM procedures

 Title Description 

 Creating a VM For more information about creating a new VM, see [Create a virtual machine with the New virtual machine wizard](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE8AFBF1-75D1-4172-988C-378C35C9FAF2.html). 
 Configuring a VM For more information about configuring the VM hardware, see [Configuring virtual machine hardware](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html). 
 Installing a guest OS on a VM For more information about the process of installing a guest OS on to a VM, see [Installing a guest operating system](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html). 
 Creating a snapshot Snapshots capture the entire state of the VM at the time that you take the snapshot. You can take a snapshot when a VM is powered on, powered off, or suspended.
: Add the contents of a configmap to the file system of runs of the job by providing a mount directory and the name of a configmap, with the format MOUNT_DIRECTORY=CONFIGMAP_NAME. Each mounted configmap must use a unique mount directory. For each key-value pair in the configmap, a file is added to the specified mount directory where the filename is the key and the contents of the file is the value of the key-value pair. Specify one mount configuration per --mount-configmap option; for example, --mount-configmap /etc/config-a=config-a --mount-configmap /etc/config-b=config-b. This value is optional.

--mount-rm
: Remove the contents of a configmap or secret from the file system of runs of the job by specifying the directory where the configmap or secret is mounted. Specify one mount directory per --mount-rm option; for example, --mount-rm /etc/configmap-a --mount-rm /etc/secret-b. This value is optional.

--mount-secret, --mount-sec
: Add the contents of a secret to the file system of runs of the job by providing a mount directory and the name of a secret, with the format MOUNT_DIRECTORY=SECRET_NAME. Each mounted secret must use a unique mount directory. For each key-value pair in the secret, a file is added to the specified mount directory where the filename is the key and the contents of the file is the value of the key-value pair. Specify one mount configuration per --mount-secret option; for example, --mount-secret /etc/secret-a=secret--a --mount-secret /etc/secret-b=secret-b. This value is optional.

--no-wait, --nw
: Do not wait for the build run to complete. If you specify the --no-wait option, the build run begins and does not wait. Use the buildrun get command to check the build run status.
Specify one mount configuration per --mount-configmap option; for example, --mount-configmap /etc/config-a=config-a --mount-configmap /etc/config-b=config-b. This value is optional.

--mount-rm
: Remove the contents of a configmap or secret from the file system of your application container by specifying the directory where the configmap or secret is mounted. Specify one mount directory per --mount-rm option; for example, --mount-rm /etc/configmap-a --mount-rm /etc/secret-b. This value is optional.

--mount-secret, --mount-sec
: Add the contents of a secret to the file system of your application container by providing a mount directory and the name of a secret, with the format MOUNT_DIRECTORY=SECRET_NAME. Each mounted secret must use a unique mount directory. For each key-value pair in the secret, a file is added to the specified mount directory where the filename is the key and the contents of the file is the value of the key-value pair. Specify one mount configuration per --mount-secret option; for example, --mount-secret /etc/secret-a=secret--a --mount-secret /etc/secret-b=secret-b. This value is optional.

--no-cluster-local, --ncl
: Deploy the application with a public endpoint. The application deploys such that it can receive requests from the public internet or from components within the Code Engine project. This value is optional. The default value is true.

--no-wait, --nw
: Update the application and do not wait for the application to be ready. If you specify the no-wait option, the application update begins and does not wait. Use the app get command to check the application status. This value is optional. The default value is false.

--output, -o
: Specifies the format of the command output.
Because using a Docker image completely bypasses the need for the prerequisite setup (the prereqs are part of the Docker image), this approach is by far the simplest option and is the process that we use throughout these tutorials. This option does require that you install Docker before proceeding. To determine whether Docker is installed, run the command docker --version. If it is installed, you'll see something similar to:


Docker version 18.09.2, build 6247962


If you do not have Docker installed, see [install Docker](https://docs.docker.com/get-docker/) to download and install it. You can also check out the [Docker site](https://www.docker.com/) for more education and documentation.

Advanced users can review the [Ansible collection documentation](https://ibm-blockchain.github.io/ansible-collection/installation.html) for other installation options.





 Next steps 

After the image is successfully built, it can be used to run a playbook. To get started with the playbooks see [Building an IBM Blockchain Platform network using Ansible playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-build) if you already have an existing instance of the IBM Blockchain Platform deployed and want to use the Ansible playbooks to deploy your network components.





 Where to find support 

Ansible is an open source technology, therefore the Ansible playbooks are not officially supported by IBM. For support related to the usage of the IBM Blockchain Platform and Ansible playbooks open an issue in the [GitHub repository](https://github.com/IBM-Blockchain/ansible-collection/issues)
Field Name Index Description 

 Bin The recommended binary to create a connection; in this case it is curl. 
 Composed A formatted command to establish a connection to your deployment. The command combines the Bin executable, Environment variable settings, and uses Arguments as command-line parameters. 
 Environment A list of key/values you set as environment variables. 
 Arguments 0... The information that is passed as arguments to the command shown in the Bin field. 
 Certificate Base64 A self-signed certificate that is used to confirm that an application is connecting to the appropriate server. It is base64 encoded. 
 Certificate Name The allocated name for the self-signed certificate. 
 Type The type of package that uses this connection information; in this case cli. 





* 0... indicates that there may be one or more of these entries in an array.
Setting up continuous integration and delivery 

With IBM Cloud and other open source tools, you can set up continuous integration and delivery (CI/CD), version control, tool chains, and more to help automate app development and deployment.

Continuous integration (CI) can help you detect errors early, ensure early system integration, and improve collaboration in your development process. Continuous delivery (CD) is a practice by which you build and deploy your software so that it can be released into production at any time. By automating your continuous integration and delivery processes through setting up CI/CD pipelines, you can achieve repeatability in code releases and greater predictability in delivery schedules.

For a deep dive into the benefits and specifics of automating continuous integration and delivery, check out [Automate continuous integration](https://www.ibm.com/garage/method/practices/code/practice_continuous_integration) and [Build and deploy by using continuous delivery](https://www.ibm.com/garage/method/practices/deliver/practice_continuous_delivery) in the IBM Garage Methodology documentation.



 Supported automation tools 

To automate your CI/CD pipeline, check out the following supported integrations and tools.

Codeship
: You can use [Codeship](https://www.cloudbees.com/products/codeship) for the continuous integration and delivery of containers. For more information, see [Using Codeship Pro To Deploy Workloads to IBM Cloud Kubernetes Service](https://www.ibm.com/cloud/blog/using-codeship-pro-deploy-workloads-ibm-container-service).

Grafeas
: [Grafeas](https://grafeas.io) is an open source CI/CD service that provides a common way for how to retrieve, store, and exchange metadata during the software supply chain process. For example, if you integrate Grafeas into your app build process, Grafeas can store information about the initiator of the build request, vulnerability scan results, and quality assurance sign-off so that you can make an informed decision if an app can be deployed to production. You can use this metadata in audits or to prove compliance for your software supply chain.
Download and install SAP software and applications 

SAP software installation media must be obtained from SAP directly, and requires valid license agreements with SAP in order to access these files.

All downloads of SAP software installation media are handled through the [SAP Support Portal](https://support.sap.com/en/index.html) and the [SAP ONE Support Launchpad](https://launchpad.support.sap.com/). This was formerly called the SAP Marketplace (SMP) and may still be referred as this in some SAP documentation.

Downloads can be performed directly to a target server (when outbound internet connectivity is permitted), or could be downloaded to an administrator laptop and uploaded to an IBM Cloud storage option (such as IBM Cloud® Object Storage).

To perform a specific SAP installation, there are many different SAP software components and different installation media compressed archive files. The software might potentially use:



* SAP's own compression format called "SAP Archive (SAR)" which can only be decompressed with the SAPCAR program
* SAP's own compression format for Java called "Software Component Archive (SCA)"
* Provided in ZIP or RAR (self-extracting EXE) compression formats



The many various SAP software components to download can be downloaded individually by using a web browser, or these download items can be added to the [SAP Download Basket](https://launchpad.support.sap.com//downloadbasket) to make it easier for downloading all files by using the [SAP Download Manager](https://support.sap.com/en/my-support/software-downloads.html) (a Java GUI application).

After the SAP software installation media downloads, follow the standard SAP installation procedure that is documented in the applicable [SAP installation guide](https://service.sap.com/instguides) for your SAP version and components and the corresponding [SAP Notes](https://support.sap.com/en/my-support/knowledge-base.html). The installation guide and SAP Notes require an SAP S-user ID to view.
For more information, see [ibmcloud catalog offering get](https://cloud.ibm.com/docs/account?topic=account-manage-catalogs-pluginget-offering).

ibmcloud catalog offering get -c <CATALOGID> -o <OFFERINGID> --output json

Run the offering update command.

ibmcloud catalog offering update -c <CATALOGID> -o <OFFERINGID> --updated-offering <UPDATED_OFFERING.json>





 ibmcloud catalog offering version preinstall 

Run the following command to run the preinstallation script for a particular product.

ibmcloud catalog offering version preinstall --version-locator VERSION_NUMBER --cluster CLUSTER_ID --namespace NAME



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for this product, run the ibmcloud catalog offering list command and locate the specified product and version that you'd like to use.

--cluster CLUSTER_ID
: Provide the cluster ID of the cluster where you want to install the product.

--namespace NAME
: Provide the namespace that you'd like to use. You can specify a new one and it is automatically created as part of the preinstallation.





 Example 

Run the preinstallation script for a product with a version locator number of b636d651-8489-4425-bd6a-f30af1603577.18aad484-c78b-4269-808b-52027621abd4 in cluster with ID bn5ebho206o7fg45f2e0 in the namespace called test-namespace.

ibmcloud catalog offering version preinstall --version-locator b636d651-8489-4425-bd6a-f30af1603577.18aad484-c78b-4269-808b-52027621abd4 --cluster bn5ebho206o7fg45f2e0 --namespace test-namespace
After you configure your deployment values, you can add the service access and platform access roles that are required to install your product.

Use the following steps to define your product's access:



1. Click Configure version > Next > Next.
2. Click Add.
3. Select the service and the required service and platform access.



* The service access role allows access for using the service and performing service API calls.
* The platform access role enables actions to be performed on platform resources, such as creating an instance, connecting instances to apps, and assigning user access.



4. Click Save.



The following table lists the string comparison operators that you can use to build access policies with /v2/policies syntax. For more information about each version, see [Comparing /v1/policies and /v2/policies syntax](https://cloud.ibm.com/docs/account?topic=account-known-issuescompare-syntax).



Table 3. The string comparison operators available for conditions in access policies.

 Operator Description 

 stringEquals Case-sensitive string comparison. Boolean or number values are converted into a string before comparison. 
 stringMatch Case-sensitive string match is performed between the pattern and the target string by using either an asterisk (), question mark (?), or both. An asterisk () represents any sequence of zero or more characters in the string, and a question mark (?) represents any single character. You can also express an asterisk * and question mark ? as a literal value by enclosing each within two sets of curly brackets {{}}. 
 stringExists String must be present but can have any none zero value. 
 stringEqualsAnyOf Case-sensitive exact string matching any of the strings in an array of strings. 
 stringMatchAnyOf Case-sensitive string matching any of the strings in an array of strings. The values can include a multi-character wildcard (), which matches any sequence of zero or more characters, a single-character wildcard (?), matching any single character, or both. You can also express an asterisk * and question mark ?
The following parameters were added or modified in the ConfigurationFile.ini:



* Change QUIET=”False” to QUIET=”True”.
* Change UIMODE=”Normal” to ;UIMODE=”Normal”.
* Change UpdateEnabled=”True” to UpdateEnabled=”False”.
* Add the line; IACCEPTSQLSERVERLICENSETERMS=”True”.





 SQL Server configuration file example 

The ConfigurationFile.ini file used in the deployment patterns is shown. The following commands can be pasted into the ConfigurationFile.ini file on the SQL server and used for the quiet install of SQL Server. The following commands should be reviewed for applicability in your environment.

;SQL Server 2019 Configuration File
[OPTIONS]

; By specifying this parameter and accepting Microsoft Python Open and Microsoft Python Server terms, you acknowledge that you have read and understood the terms of use.

IACCEPTPYTHONLICENSETERMS="False"

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.

ACTION="Install"

; By specifying this parameter and accepting Microsoft R Open and Microsoft R Server terms, you acknowledge that you have read and understood the terms of use.

IACCEPTROPENLICENSETERMS="False"

; Specifies that SQL Server Setup should not display the privacy statement when ran from the command line.

SUPPRESSPRIVACYSTATEMENTNOTICE="False"

; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system.

ENU="True"

; Setup will not display any user interface.

QUIET="True"

; Setup will display progress only, without any user interaction.

QUIETSIMPLE="False"

; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.

;UIMODE="Normal"

; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0.
2. You are required to select your organization and the associated peer admin identity that you want to use to commit the definition.



When the smart contract definition is successfully committed to the channel, the status on the tile changes to Committed.





 How do I? 

Based on the preceding steps, the following table provides a summary of the lifecycle actions that are required depending on your goal:



Table 2. Frequent smart contract tasks

 Task Instructions 

 Deploy and run a smart contract on a channel You need to [package the smart contract](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-pkg) into .tgz or .tar.gz format and then [propose](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-install-propose) it to the channel. As part of the proposal process you must install the package on at least one peer. Organizations who are members of the lifecycle endorsement policy (specified when the channel is created or updated), must [approve](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-approve) the definition. After the channel members specified in the lifecycle endorsement policy approve the definition, any of them can [commit](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-commit) the definition, at which point the smart contract can start to process transactions on the peers. 
 Install a smart contract on my peers If the smart contract has not yet been proposed to the channel, navigate to the Channels tab and click Propose smart contract definition.
Planning your deployment 

Make sure that you are already familiar with the fundamental components and options that are provided by IBM Cloud Classic Infrastructure for SAP. Before you start with the deployment of servers, make sure that you also read the Get Started section.



  Content to review before you start deploying 

To ensure that your first deployment is a success, review the following information:



*  [Classic Infrastructure environment introduction](https://cloud.ibm.com/docs/sap?topic=sap-classic-env-introduction)
*  The Plan your SAP workloads topic group
*  The Infrastructure for SAP design considerations topic group



An exhaustive overview about IBM Cloud for VMware on Classic Infrastructure you find here: [IBM Cloud for VMware](https://www.ibm.com/cloud/vmware). Additional information is available on:



*  [IBM Cloud Intel Bare Metal and VMware vSphere (ESXi OS)](https://cloud.ibm.com/docs/vmware?topic=vmware-about-vmware) for the manual VMware setup and configuration
*  [IBM Cloud for VMware Solutions Dedicated](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-inst_comp_chart) for fully automated VMware SDDC setup and configuration





  Other useful documents 

See the respective topics in the Get Started section for the following information:



*  [SAP HANA design considerations for High Availability and Disaster Recovery (HA/DR)](https://cloud.ibm.com/docs/sap?topic=sap-hana-design-considerationshana-ha)
*  [SAP HANA backups - Storage impacts on Recovery Time Objective (RTO)](https://cloud.ibm.com/docs/sap?topic=sap-storage-design-considerationsstorage-performance-backup-rto)
*  [SAP NetWeaver design considerations for High Availability configuration](https://cloud.ibm.com/docs/sap?topic=sap-netweaver-design-considerationsnetweaver-ha)