vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Installing the CLI 

You can use the following tools to manage your Satellite locations and clusters. While you can install a subset of the tools, all of the following tools are recommended.



 Understanding the CLI tools 



Table 1: CLI tools

 CLI Description 

 ibmcloud You can use the ibmcloud CLI to login to your account, add users, manage your catalogs and more. 
 ks plug-in You can use the ks plug-in to create and manage clusters and to manage your Satellite resources. 







 Step 1: Run the installation command 

The latest version of the IBM Cloud CLI is installed when you run the command. As the CLI installs, keep an eye on the command line to authenticate as needed.



* For MacOS, run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/osx | sh
* For Linux™, run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/linux | sh
* For Windows™, run the following command in PowerShell as an administrator:

iex (New-Object Net.WebClient).DownloadString('https://clis.cloud.ibm.com/install/powershell')

To open PowerShell, right-click the Windows™ PowerShell icon, and select Run as administrator.
* For WSL2 on Windows™, run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/linux | sh



For more information about installing the Mac OS X M1/ARM or Linux 64-bit ARM versions of the CLI, see the IBM Cloud CLI [release notes](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/). These versions are provided as-is and are not fully supported.

For more installation methods, see [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).





 Step 2: Verify the installation 

To verify that the CLI was installed successfully, run the help command:
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.

It is important to remember that any SAP software installation will require some OS configuration; some of this information is available under the [Compute and OS Design Considerations](https://cloud.ibm.com/docs/sap?topic=sap-compute-os-design-considerations) section. This OS configuration can be done before or after the SAP software installation media downloads have completed.

For IBM Power, you may want to install AIX Toolbox for Linux Applications for easier handling of SAP software.

For more help with SAP Download Manager, see:



* [SAP Note 2272824 - How to Download SAP Solution Manager - SAP ONE Support Launchpad](https://launchpad.support.sap.com//notes/2272824)
* [SAP Note 1371839 - How to install SAP Download Manager - SAP ONE Support Launchpad](https://launchpad.support.sap.com//notes/1371839)
* [SAP Note 2624390 - What is the current version of SAP Download Manager?](https://launchpad.support.sap.com//notes/2624390)
sh ./evault_manual.sh
2. Enter your Cloud Backup Portal username and password.

For more information about viewing the username or changing the backup password, see [Managing username and password for the Cloud Backup service](https://cloud.ibm.com/docs/Backup?topic=Backup-changePassword).
3. After the username and password, no further input is required. The prompts that are written to the screen as the installation proceeds can be safely ignored.

They are being produced by a subscript, which is started by the evault_manual.sh script. The evault_manual.sh script provides the input for these prompts.
4. The installation is complete when the following messages appear.

Starting VVAgent: [ OK ]
Starting buagent: [ OK ]







 Verifying that the installation succeeded 



1. Verify that the message Registered to The Portal appears in the installation output. The verification can be done by looking for the message on screen or by inspecting the output of the following command.

grep 'Registered' /opt/BUAgent/Install.log
2. Run the following command and observe the output.

service vvagent status

The following messages are displayed.

VVAgent is running (PID xxxxx).
buagent is running (PID xxxxx).

The process IDs that are represented by xxxxx varies with each installation.







 Next steps 

Log in to Cloud Backup Portal to configure and manage your backup agents. For more information, see the [Getting Started Tutorial](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-startedgetting-started) and [Configuring simple file-level backup](https://cloud.ibm.com/docs/Backup?topic=Backup-configureFileBackup).
Provision the virtual server instance within the same data center as the AltaVault appliance and vSphere environment. The virtual server instance must have access to the AltaVault appliance and vCenter.







 Installing Veeam Backup & Replication 

Use the following steps to install Veeam Backup & Replication to the IBM Cloud virtual server instance after all of the prerequisites are met.



1. Double-click the program file and click Veeam Backup & Replication – Install. The setup wizard opens.



* Click Next and select I accept the terms in the license agreement .
* Click Next and specify the location of the license file that is obtained under Deploy Veeam Backup & Replication.
* Click Next and select which Veeam Backup & Replication components that you want installed and their installation location on the Program Features screen. Note:Veeam Backup & Replication and Veeam Backup Catalog are required components.
* Click Next.
The setup wizard runs a series of checks to make sure that all required program frameworks and supporting components are installed. If any components are missing, the setup wizard offers to install them.



2. Verify that all components Passed the systems check and click Next.
3. Select the Service (user) Account that you want the Veeam Backup Service to run. The default service account is the LOCAL SYSTEM account. Click Next.
4. Select the SQL Server Instance that you want to use to create and store Veeam Backup & Replication databases. For more information, contact your database administrator. Click Next.
5. Enter the Catalog service port (9393) and Veeam Backup service port (9392). Click Next.
6. Select the directories where you want to store the guest file system catalog (persistent data) and vPower NFS write cache (non-persistent data). Click Next.
7. Verify that all settings and values are correct and click Install. After the installation is done, click Finish.







 Configuring Veeam Backup & Replication 

After Veeam Backup & Replication installs, you are ready to connect with the AltaVault appliance.



1.
[root@sap-app2-vsi ] mkdir -p /usr/sap/trans
[root@sap-app2-vsi ] exportfs -a
5. Mount the NFS share on the application server by adding the following entry to its /etc/fstab and mount the application server from the command line by using the following command.

[root@sap-app-vsi ] vi /etc/fstab
...
sap-app2-vsi-priv:/sapmnt/C10 /sapmnt/C10 nfs defaults 0 0
sap-app2-vsi-priv:/usr/sap/trans /usr/sap/trans nfs defaults 0 0
6. Create and mount the target directory.

[root@sap-app-vsi ] mkdir /sapmnt/C10
[root@sap-app-vsi ] mkdir /usr/sap/trans
[root@sap-app-vsi ] mount /sapmnt/C10
[root@sap-app-vsi ] mount /usr/sap/trans



Your servers are now prepared to host the components of a distributed SAP installation. For more information about more installation preparations, see [Downloading and installing SAP software and applications](https://cloud.ibm.com/docs/sap?topic=sap-download-install-media).





 Step 8: Installing your SAP landscape 



 RPM package prerequisites 

An SAP installation requires that certain prerequisites are met regarding the packages that are installed on the OS and the OS daemons that are running. See the latest installation guides and support notes from SAP for an up-to-date list of these prerequisites. Currently, the following extra packages are required for an SAP NetWeaver installation: - compat-sap-c++-7: Achieves compatibility of the C++ runtime with the compilers that are used by SAP - uuidd: Maintains OS support for the creation of UUIDs - csh: C shell support for the OS



1.
Setting up cluster groups 

The cluster group specifies all clusters that you want to include in the deployment of your Kubernetes resources. The clusters can run in your Satellite location or in IBM Cloud.

If you want to use the console to create Satellite configurations, you can create cluster groups as part of the configuration creation process. If you want to use the CLI to create Satellite configurations, you must create a cluster group first. Follow these steps to create a cluster group with the CLI:



1.  List the clusters that are registered with the Satellite Config component and note their ID.

ibmcloud sat cluster ls
2.  Add the cluster to your cluster group.

ibmcloud sat group attach --cluster <cluster_ID> --group <cluster_group_name>
3.  Verify that your cluster is successfully added to your cluster group.

ibmcloud sat group get --group <cluster_group_name>
namespaces get, list, watch get, list, watch get, list, watch <br>cluster-admin only: create, delete 
 namespaces/status get, list, watch get, list, watch get, list, watch 
 networkpolicies get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 networkpolicies.extensions get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 node None None admin scoped to a namespace: None<br><br>cluster-admin for all namespaces: All verbs 
 persistentvolume None None create, delete, deletecollection, get, list, patch, update, watch 
 persistentvolumeclaims get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 poddisruptionbudgets.policy get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, top, patch, update, watch 
 pods/attach <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods/exec <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 pods/log get, list, watch get, list, watch get, list, watch
* [Key concepts for Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-cluster-configsatcon-terminology)





 Setting up clusters to use with Satellite Config 

[Granting Satellite Config access to your clusters](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigsetup-clusters-satconfig)



* [Automatically granting Satellite Config access to your clusters](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigauto-setup-clusters-satconfig)
* [Manually granting Satellite Config access to your clusters](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigmanual-setup-clusters-satconfig)



* [Cluster admin access](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigcluster-admin-access)
* [Custom access, cluster-wide](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigcustom-access-cluster-wide)
* [Custom access, scoped to a project](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigcustom-access-scoped-project)





[Setting up cluster groups](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig-groupssetup-clusters-satconfig-groups)

[Registering clusters with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-register-openshift-clustersregister-openshift-clusters)

[Verifying cluster status](https://cloud.ibm.com/docs/satellite?topic=satellite-satconfig-verify-cluster-statussatconfig-verify-cluster-status)
* [Creating a cluster, API key, and cluster roles](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-cluster-key-tenancy)



* [Creating a Satellite cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-cluster-tenancy)
* [Creating an API key](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-api-tenancy)
* [Setting up cluster admin and developer roles](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-roles-tenancy)





[Edge environments for AI, IoT, and machine learning](https://cloud.ibm.com/docs/satellite?topic=satellite-edge-usecaseedge-usecase)



* [Solving common edge workload challenges with IBM Cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-edge-usecaseedge-challenges)
* [Setting up your edge solution with Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-edge-usecaseedge-solution)



* [Step 1: Set up machine learning and model training for your data](https://cloud.ibm.com/docs/satellite?topic=satellite-edge-usecaseedge-example-ml)
* [Step 2: Deploy Satellite with a serverless component to your edge environment](https://cloud.ibm.com/docs/satellite?topic=satellite-edge-usecaseedge-example-serverless)
* [Step 3: Run model inferencing at the edge](https://cloud.ibm.com/docs/satellite?topic=satellite-edge-usecaseedge-example-inferencing)









 Understanding Satellite location and hosts 

[Understanding Satellite location and hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-location-hostlocation-host)
Cluster not found corresponding to the given cluster ID: CLUSTER-ID

Error type: Bad request

How to fix it: To list all the Satellite clusters that you have access to, run ibmcloud oc cluster ls --provider=satellite.

Response code: 404





 ST0031 error message 

The required input query parameter PARAMETER-NAME is missing.

Error type: Bad request

Response code: 404





 ST0032 error message 

The PARAMETER and PARAMETER parameters are exclusive. Provide only one of these parameters.

Error type: Bad request

Response code: 404





 ST0033 error message 

Updating an assignment, created for a cluster, to cluster group(s) is not supported. Run ibmcloud sat storage assignment rm to remove the assignment and create new assignment with cluster group(s).

Error type: Bad request

Response code: 400





 ST0034 error message 

Failed to remove old temporary storage configuration with name: OBJECT-NAME.

Error type: Services

How to fix it: To remove the storage configuration manually, run ibmcloud sat storage config rm --config=<config-name>.

Response code: 500





 ST0035 error message 

ERROR-MESSAGE. INCIDENT-ID

Error type: Services

Response code: 500





 ST0036 error message 

Parameter is an invalid UUID.

Error type: Bad request

Response code: 400





 ST0037 error message 

Failed to fetch OBJECT IDENTIFIER.

Error type: Services

Response code: 500





 ST0038 error message 

Satellite Location LOCATION not found. To list all the Satellite locations that you have access to, run ibmcloud sat locations.

Error type: Bad request

Response code: 404





 ST0039 error message 

IBM Cloud Satellite is not available in this region. Choose a supported IBM Cloud region with ibmcloud target -r REGION to manage your Satellite location from, and try again. For supported multizone regions, see http://ibm.biz/satloc-mzr.

Error type: Satellite

Response code: 404





 ST0040 error message 

Format error in template file.
* Geography: Select an area to create the cluster in, such as North America. The geography helps filter the Availability and Metro values that you can select in the console.



: 

* Availability: A cluster can be created with a Single zone or Multizone configuration. A multizone cluster provides high availability, with the Red Hat OpenShift master deployed in a multizone-capable zone and three replicas of the master spread across different zones.



* For multizone clusters, choose a Metro location. For the best performance, select the metro location that is physically closest to you. Your Worker zones are based on the metro location you choose. You can select which worker zones to apply, and your worker nodes are spread across your zones for high availability. Each worker zone has a public and private VLAN. If you do not have VLANs in that zone, they are created for you.
* For single zone clusters, choose a single Worker zone to host your cluster in. For the best performance, select a zone in the city that is physically closest to you. Each worker zone has a public and private VLAN. If you do not have a VLANs in that zone, they are created for you.





Kubernetes version
: By default, clusters are created with the default Kubernetes version. You can specify a different [supported version](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions&interface=uics_versions_available).

Worker pool
: The cluster worker pool defines the number and type of worker nodes that run you workload. You can change your worker pool details at anytime.
: 

* Flavor: The flavor defines the amount of virtual CPU, memory, and disk space that is set up in each worker node and made available to the containers. Available bare metal and virtual machines types vary by the zone in which you deploy the cluster. For more information, see [Planning your worker node setup](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodes).



: 

* Worker nodes per zone: For high availability, at least 3 worker nodes per zone are recommended.



:
List available zones and note which one you want to create the cluster in.

ibmcloud ks zones --provider vpc-gen2

Example output.

ID Name Metro Flavors
us-east-1 us-east-1 Washington D.C. -
us-east-2 us-east-2 Washington D.C. -
us-east-3 us-east-3 Washington D.C. -
us-south-1 us-south-1 Dallas -
us-south-2 us-south-2 Dallas -
us-south-3 us-south-3 Dallas -



7. Create the cluster. Specify the dedicated host pool, the subnet, vpc and zone you previously noted, and the cluster flavor. Note that it may take several minutes for the cluster to fully provision.

ibmcloud ks cluster create vpc-gen2 --name my_cluster --flavor bx2d.4x16 --dedicated-host-pool dh_a1aaa1111aaa1aaa1a11 --subnet-id 1111-a11aaaa1-1a11-1111-1a1a-aaaaa1111111 --vpc-id a111-11a111a1-11a1-1a11-11a1-a1a1111a11a1 --zone dal10 --workers 3
8. Verify that the cluster is created.

ibmcloud ks cluster ls

Example output.

Name ID State Created Workers Location Version Resource Group Name Provider
my_cluster a111a11a11aa1aa11a11 normal 1 hour ago 4 Dallas 1.26.6 default vpc-gen2
VMware vSphere 

For more information about [VMware vSphere](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphereclusteroverview) clusters, see the following topics:



*  [Planning for VMware vSphere](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_planning)
*  [Procedure to order vSphere clusters](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_orderinginstances-procedure)
*  [Scaling existing vSphere clusters](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_scalingexistingclusters)
*  [Deleting vSphere clusters](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_deletingclusters)
(https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 







 Cluster group platform access roles 



Actions that you can take with platform access roles.

 Action API CLI None Viewer Editor Operator Administrator 

 Add clusters to a cluster group. groupClusters [cluster-group attach](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-attach) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 Remove clusters from a cluster group. unGroupClusters [cluster-group detach](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-detach) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 Create a cluster group. addGroup [cluster-group create](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-create) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 View cluster groups that are attached to Satellite Config.
The geography helps filter the Availability and Metro values that you can select in the console.



: 

* Availability: A cluster can be created with a Single zone or Multizone configuration. A multizone cluster provides high availability, with the Kubernetes master deployed in a multizone-capable zone and three replicas of the master spread across different zones.



* For multizone clusters, choose a Metro location. For the best performance, select the metro location that is physically closest to you. Your Worker zones are based on the metro location you choose. You can select which worker zones to apply, and your worker nodes are spread across your zones for high availability. Each worker zone has a public and private VLAN. If you do not have VLANs in that zone, they are created for you.
* For single zone clusters, choose a single Worker zone to host your cluster in. For the best performance, select a zone in the city that is physically closest to you. Each worker zone has a public and private VLAN. If you do not have a VLANs in that zone, they are created for you.





Kubernetes version
: By default, clusters are created with the default Kubernetes version. You can specify a different [supported version](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions&interface=uics_versions_available).

Worker pool
: The cluster worker pool defines the number and type of worker nodes that run you workload. You can change your worker pool details at anytime.
: 

* Flavor: The flavor defines the amount of virtual CPU, memory, and disk space that is set up in each worker node and made available to the containers. Available bare metal and virtual machines types vary by the zone in which you deploy the cluster. For more information, see [Planning your worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes).



: 

* Worker nodes per zone: For high availability, at least 3 worker nodes per zone are recommended.



: