vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing provisioning scripts 

You can use provisioning scripts to specify a URL to a script that runs on a newly provisioned device. Provisioning scripts can be any file that the operating system can run, including combined binary files or any OS-supported language. You have no restrictions for the script name; however, using a similar naming convention for each script makes it easier to identify. Provisioning scripts must be associated with a fully qualified domain name and accessible using the HTTP or HTTPS protocols. The type of protocol that is used impacts the system's automated response when the provisioning script is downloaded to the device.



* Using HTTP protocol requires an administrator to run the script manually after it is downloaded.
* Using HTTPS protocol downloads and runs the script automatically, if possible. If the URL is not associated to a valid script, the script is downloaded and no further action must be taken.





 Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices).
* Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Adding a provisioning script 



1. From the Devices menu, select Manage > Provisioning Scripts.
2. Select Add Provisioning Script.
3. Enter an identifying name for the provisioning script in the Name field.
4. Enter the fully qualified domain name that is associated with the script in the URL field.
5. Click Add to add the provisioning script to the account.







 Editing provisioning script details 



1.
You save quota for other images and save money.
* Sometimes, the build run needs less time to complete because a smaller image can be transferred faster to the container registry than a much larger one. You again save money.
* The application or job that uses the image starts faster because the time that is needed to pull the image is shorter. As the resources that are needed to run your application or job are reserved while the image is pulled, you again save money. A fast startup time is especially relevant for applications in Code Engine because it guarantees an acceptable response time for the requests of your users, even if the application is scaled down to zero.



Let's look at some best practices to reduce the size of your build.



 Combine several commands in a single RUN statement to reduce image size 

In this example, you must install software in the container image, for example, Node.js. Use the base images for Node.js to build a Node.js application.

To manually install Node.js, you can use the following Dockerfile example,

FROM ubuntu

RUN apt update
RUN apt upgrade -y
RUN apt install -y nodejs
RUN apt clean
RUN rm -rf /var/lib/apt/lists/*

In this example, several RUN statements are used to update, upgrade, install Node.js, clean, and remove the cache of files. While this sequence of statements is correct, the use of multiple RUN statements is not the best way to implement it. When a Dockerfile is processed, each statement in the Dockerfile creates a layer. Each layer contains the files that were created or updated and also information about what was deleted. A container image is the collection of all the layers. If a file is added in one statement and deleted in a second one, then the resulting image still contains the file in the layer for the first statement and then marks it as deleted in the second layer.

To save disk space, specify a single RUN statement to create a single layer for this set of commands,

FROM ubuntu

RUN apt update && apt upgrade -y && apt install -y nodejs && apt clean && rm -rf /var/lib/apt/lists/*
Ordering Hyper-V 

If you have an existing server, you can install Hyper-V on a server by initiating an OS reload and by changing the operating system to Windows Server Datacenter Edition with Hyper-V.

If you want to provision a server by using Hyper-V, place an order for the new server and select Windows Server Datacenter Edition with Hyper-V” as the operating system.
Initial Provisioning 

The initial provisioning covers several key aspects of the Maximo Application Suite deployment.

The base architecture is finalized regarding the size and number of OpenShift clusters needed. The provisioning of all based components and configuration is performed and the initial DNS registration for the Maximo Application Suite done. A temporary license file is installed. The client will need to supply the final license file (described below).





 Provisioning of the Individual Products 

At this point, the products the client has selected is provisioned based on the sizing parameters that were specified. This includes deploying the appropriate containers within OpenShift and configuring the products to be available to the client. This includes the application, database, any network configuration required, DNS registrations and set up of client administration users.

At this stage, all operational configuration is finalized including ensuring backups are configured properly, monitoring in place and security scans completed. Alerting is configured and the sites added to the MAS-Dedicated escalation process.





 Final Verification of the Provisioning 

A final review of the install is done to ensure what has been deployed meets the order and the additional information gathered. At this point, the order is marked complete and a [welcome letter](https://cloud.ibm.com/docs/mas-ms?topic=mas-dedicated-getting-started-with-ibm-maximo-application-suite-dedicated-servicewelcome-letter) is sent to the client.
The AIX stock images have a local repository that contains all available packages for the current level of the operating system. Any software that is not automatically installed is considered as optional and is included with the operating system in a separate file system starting with the 7100-05-05 or newer images /usr/sys/inst.images. By creating a separate file system, the local repository prevents the expansion of /usr file system. In addition, the separate file system can be safely removed if you want to reclaim the additional space used by the local repository.

The optional software products found under the /usr/sys/inst.images file system can be installed by using either command-line or SMIT menu options. For more information on installation options, visit the [installp](https://www.ibm.com/support/knowledgecenter/ssw_aix_72/i_commands/installp.html) command guide.



 Examples: 



* To list all the software products and installable filesets in the /usr/sys/inst.images file system, enter the following command:



installp -L -d /usr/sys/inst.images



* To install and commit all software within the Geographic Logical Volume Manager software package (located in the /usr/sys/inst.images directory) and expand the file systems if necessary, enter the following command:



installp -acXd /usr/sys/inst.images glvm.



* To preview the installation of the bos.sysmgt.nim.master fileset (located in the /usr/sys/inst.images directory) and all requisite software, enter the following command:



installp -pagXd /usr/sys/inst.images bos.sysmgt.nim.master



* To install software by using the SMIT interface, enter the following command:



smit install
You must then specify the individual enhanced neural voices that are to be installed. By default, only en-US_AllisonV3Voice, en-US_LisaV3Voice, and en-US_MichaelV3Voice are installed. You can choose to install these default voices, these and other voices, or just other voices. Only the voices that you install are available.
* Specify neuralVoices to install the neural voices. All of the neural voices are installed and available. You cannot refine the list of installed voices.



For more information about using the custom resource to install voices, see [Installing Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-installing-watson-text).

Specifying a voice for speech synthesis
: Both the HTTP POST and GET /v1/synthesize methods, as well as the WebSocket /v1/synthesize method, accept an optional voice query parameter that you use to specify the voice that is to be used for speech synthesis. If you omit the voice parameter, the service uses a default voice. The default voice depends on the voices that you installed:



* If you installed the enhanced neural voices, the service uses the US English en-US_MichaelV3Voice by default. If that voice is not installed, you must specify a voice.
* If you installed the neural voices, the service always uses the Australian English en-AU_MadisonVoice by default.



For more information, see [Using a voice for speech synthesis](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices-use).

Specifying a language for a custom model
: You use the POST /v1/customizations method to create a custom model. The method includes a language parameter that you use to identify the language of the new custom model.



* If you installed the enhanced neural voices, the language parameter is optional. By default, the service uses the en-US identifier for the language.
* If you installed the neural voices, the language parameter is required.
export PATH=$PATH:$HOME/app/.java/jre/bin

$HOME/app/.liberty/bin/installUtility install audit-1.0 --acceptLicense

You can install multiple features by specifying additional features names separated by spaces.
3. Push your app to IBM Cloud, using the -p option to specify the app's root directory.

For example, run the following command to push your app:

ibmcloud cf push myApp -p /<path-to-app>
4. Verify that the feature installed successfully by viewing the app's recent log.

For example, run the following command to display the log:

ibmcloud cf logs myApp --recent

If the feature was installed, the output shows the following messages:

2018-09-18T13:01:17.61-0400 [APP/PROC/WEB/0] OUT Installing audit-1.0
2018-09-18T13:01:19.13-0400 [APP/PROC/WEB/0] OUT Establishing a connection to the configured repositories ...
2018-09-18T13:01:19.13-0400 [APP/PROC/WEB/0] OUT This process might take several minutes to complete.
2018-09-18T13:01:21.28-0400 [APP/PROC/WEB/0] OUT Successfully connected to all configured repositories.
2018-09-18T13:01:21.28-0400 [APP/PROC/WEB/0] OUT Preparing assets for installation. This process might take several minutes to complete.
2018-09-18T13:01:25.87-0400 [APP/PROC/WEB/0] OUT The --acceptLicense argument was found. This indicates that you have
2018-09-18T13:01:25.87-0400 [APP/PROC/WEB/0] OUT accepted the terms of the license agreement.
(https://cloud.ibm.com/docs-content/v1/content/b6066ebcc4ff31f2a8b558531f2ee791d108a7e1/cloud-pak-multicloud-management/images/setup_appliance.png)

Figure 17. Welcome to the Appliance Console
3. Press Enter to manually configure settings.

Note: Networking is already configured. You can skip this step.
4. Select 5) Configure database from the menu.



* You are prompted to create or fetch an encryption key. If this instance is the first Infrastructure management appliance, select 1) Create key.
* If this is not the first Infrastructure management appliance, select 2) Fetch key from remote system to fetch the key from the first appliance. For worker and multi-region setups, use this option to copy key from another appliance.



Note: All Infrastructure management appliances in a multi-region deployment must use the same key.
5. Select 1) Create Internal Database for the database location.
6. Choose a disk for the database. The disk can be either a disk you attached previously, or a partition on the current disk.

Important: Best practice is using a separate disk for the database.

If an unpartitioned disk is attached to the virtual machine, the dialog shows the options. For example,

1) /dev/vdb: 20480
2) Don't partition the disk



* Enter 1 to choose /dev/vdb for the database location. This option creates a logical volume by using this device and mounts the volume to the appliance in a location appropriate for storing the database. The default location is /var/lib/pgsql, which can be found in the environment variable $APPLIANCE_PG_MOUNT_POINT.
* Enter 2 to continue without partitioning the disk. A second prompt confirms this choice. Selecting this option results in using the root file system for the data directory (not advised in most cases).



7.
But you can install read-only software such as OpenSCAP on the hosts before attaching them to your location.

The reasons that you cannot install extra software on the hosts relate to [IBM 's responsibilities](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilities) to manage multiple aspects of the Satellite hosts for you, such as installation, access, and maintenance.

Installation: The Satellite team tries to keep the host requirements to a minimal level so that many servers across infrastructure providers can meet the requirements to become Satellite hosts. By limiting the number of possible software packages, Satellite reduces instability and conflicts during installation tasks such as [bootstrapping](https://cloud.ibm.com/docs/satellite?topic=satellite-location-host) each host so that all hosts across Satellite locations have a consistent set of images and container platform software. This consistency also helps you develop applications and deploy Satellite-enabled IBM Cloud services that work across your environments.

Access: For security purposes, Satellite restricts external access to hosts, including SSH. Many extra software packages require access to or from the host, so extra software packages are not allowed to be installed.

Maintenance: IBM provides software updates that you choose when to apply to the host. Because IBM is responsible for providing these updates, you cannot install extra software that is not managed by IBM. Extra software also uses mores CPU, memory, and disk storage resources on the host, which impacts the amount available to your Satellite-enabled IBM Cloud services and applications that run on the hosts.
* What am I charged for when I use IBM Cloud Satellite?

IBM Cloud Satellite provides a convenient way for you to consume IBM Cloud services in any location that you want, with visibility across your locations. For more information, see [Pricing](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-pricing).
* Can I estimate my costs?

When you create a resource such as a location or cluster, you can review a cost estimate in the Summary pane of the console. For other types of estimates, see [Estimating your costs](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-costcost).
These scripts can contain custom actions to be completed before or after applying the fix.
* Check fix packages, without installing them. This preliminary check determines whether your existing cluster is compatible with the fix you want to install, verifies that the user account has appropriate permissions, and lists files that are overwritten by and added by the fix.
* Roll back the most recent fix (either by fix package name or by build number) so that your host returns to its original state before installing the fix.



Use the egoinstallfixes command only on Linux hosts; to manage fixes on Windows, refer to the readme file that is bundled with the fix you want to install.



 Installing interim fixes 



1. Use the egoinstallfixes command to install or roll back interim fixes for your IBM Spectrum Symphony installation on a Linux host. For command syntax and option details, see [egoinstallfixes](https://www.ibm.com/docs/en/spectrum-symphony/7.3.1?topic=commands-egoinstallfixesreference_p3w_4dm_bdb).

a. To run the egoinstallfixes command, your Linux host must include the ed Linux line-oriented text editor.

b. To run the egoinstallfixes command remotely, note the following considerations:



* Set the full path and file name to the environment file that properly defines your EGO_TOP and EGO_CONFDIR parameters by running the command with the -f env_file option.
* Force pseudo-tty allocation to that remote host by prefacing the egoinstallfixes command with the ssh -t remote_hostname command.
* Surround the command syntax with quotation marks ().

Here is an example of using the egoinstallfixes command from your local host to apply the sym-version_x86_64_build123456.tar.gz package to a remote host called abc123, and specifying the /home/egoadmin/cluster.env location for the -f option:
Summary of an SAP landscape installation onto Cloud IaaS 

This table summarizes the SAP landscape installation steps for you and your team:



Table 1. Overview of your SAP landscape installation steps

 Task Details 

 Read the [Overview of IBM Cloud® for SAP](https://cloud.ibm.com/docs/sap?topic=sap-overview) Identify the various offerings that are available for your SAP landscape. Provides a high-level comparison of your options. 
 Read the relevant documents in the following topic groups: <br><br> * Infrastructure environments section for your specific environment, such as [IBM Power Systems Infrastructure environment introduction](https://cloud.ibm.com/docs/sap?topic=sap-power-env-introduction)<br> * [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings)<br> * [Sizing process for SAP Systems](https://cloud.ibm.com/docs/sap?topic=sap-sizing) <br> Read these documents to identify the detailed infrastructure options and design considerations that apply to your SAP landscape.<br><br><br> 
 Read the relevant SAP software documentation. Short lists of planning considerations are available to assist under topic groups:<br><br><br><br> * SAP Business Applications<br> * SAP Technical Applications<br> * SAP AnyDB databases <br> Lists of usage, network, storage, database, and OS considerations are available for SAP Business Applications, SAP Technical Applications, SAP AnyDB databases, SAP Development Applications. References to SAP installation documents are also included.<br><br><br> 
 Optional: Read the relevant SAP Business Partner certified solutions documents Various SAP Open Ecosystem Partners are available from IBM Cloud, with documents on how to best use these solutions for your SAP deployment. 
 Optional: Read the relevant IBM-SAP innovation solutions documents IBM Cloud® for SAP 
 Read and follow the documents in the Pre-Requisites for SAP Workloads topic group Prepare the credentials, account structure, connectivity, software downloads, support procedures, and licensing that is needed before you begin your deployment.
FAQs 

Review frequently asked questions for IBM® WebSphere® Application Server in IBM Cloud®. To find all FAQs for IBM Cloud, see the [FAQ library](https://cloud.ibm.com/docs/faqs).



  What products can I install with WebSphere Application Server? 

You can install a WebSphere Application Server traditional environment on a virtual server instance (VSI) on IBM Cloud. For a description of the topologies that you can install with WebSphere Application Server, see [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies).





  What permissions do I need to use this tile? 

You need Manager role on the Schematics service in at least one resource group. You also need Administrator role for VPC Infrastructure Services in the resource group for the Schematics workspace, VPC, and VSIs.





  Where can I see the installation logs? 

To see the Installation logs, look under the [Schematics workspace](https://cloud.ibm.com/schematics/workspaces).





  Where can I see my installation history? 

To see the installation history, look under the [Schematics workspace](https://cloud.ibm.com/schematics/workspaces).





  How do I uninstall? 

Follow the instructions in [Uninstalling your workspace or resources](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-uninstalling).





  Do I get charged for using the tile? 

No, but you get charged for the infrastructure. Refer to [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies) for infrastructure resources provisioned and to [Pricing](https://www.ibm.com/cloud/vpc/pricing) for the associated cost.





  Can I use the tile to upgrade WebSphere Application Server after initial installation? 

No, you can use the tile only for one installation. After the initial installation, it is your responsibility to manage and upgrade the installation.
Considerations for on-premises VMware HCX instances 

Review the following considerations before you install or delete the VMware HCX® instances that you ordered for on-premises use.

A VMware vCenter Server® instance with HCX is limited to three simultaneous connections from on-premises sites.



 Considerations before you install on-premises HCX instances 

The HCX components must be installed both on IBM Cloud® and in your on-premises VMware vSphere® environment. It is recommended that you install the HCX service into your vCenter Server instance before you install the on-premises HCX instance.

For more information, see [Considerations when you install HCX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_considerationshcx_considerations-install).



 Notes for HCX installations 



* Before the service is installed in your environment, a check is performed against the available capacity of the default cluster in the environment to ensure that the service components can fit.
* If the capacity check fails, the service is not installed and the service status is set to Capacity Validation Failed on the console. In addition, a console message with more details is displayed and you are notified by email.
* To install the service, you must increase the capacity in your default cluster. Either add more hosts or by free up RAM, CPU, or disk space, and then add the service again in the console. Then, you can delete the existing service in the Capacity Validation Failed state by clicking the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) next to it.







 IP address requirements 

For full HCX functions, you need at least five private IP addresses that have internet access.





 Deployment process for on-premises HCX instances 

You must complete the following tasks for a successful installation of the on-premises HCX instance:



1. In the IBM Cloud for VMware Solutions console, order the on-premises HCX instance.