vania-janet/multiturn-rag-retrieval-data huggingface dataset:
owner=kgurudut@in.ibm.com, requestID=20c30a3b-fbb1-4f41-
aa71-5ed337047ec2
2022/08/03 15:51:17 Related Job: jobID=useast.JOB.Blueprint_Basic.e4081308
2022/08/03 15:51:32 --- Ready to execute the environment flow install
command ---
2022/08/03 15:51:32 Processing Module Entry us-east.workspace.basicresource-group.9ea437b2
2022/08/03 15:51:33 Module Status for ModuleID=us-east.workspace.basicresource-group.9ea437b2 is INACTIVE
2022/08/03 15:52:31 Install activity completed for module ModuleID=useast.workspace.basic-resource-group.9ea437b2
2022/08/03 15:52:33 Status for module ModuleID=us-east.workspace.basicresource-group.9ea437b2 is ACTIVE
2022/08/03 15:52:35 Processing Module Entry us-east.workspace.basic-cosstorage.adb78a38
2022/08/03 15:52:37 Module Status for ModuleID=us-east.workspace.basiccos-storage.adb78a38 is INACTIVE
2022/08/03 15:54:06 Install activity completed for module ModuleID=useast.workspace.basic-cos-storage.adb78a38
2022/08/03 15:54:08 Status for module ModuleID=us-east.workspace.basiccos-storage.adb78a38 is ACTIVE
2022/08/03 15:54:10 ENVIRONMENT_INSTALL -
ENVIRONMENT_SYSTEM_STATEENUM_FULFILMENT_SUCCESS
2022/08/03 15:54:11 Done with the environment install flow job
OK







 Step 5: Access and test the blueprint environment resources
Installing 

Learn how to install Watson Assistant for IBM Cloud Pak® for Data.

The IBM Cloud Pak for Data environment is a Kubernetes-based container platform that can help you quickly modernize and automate workloads that are associated with the applications and services you use. You can develop and deploy on your own infrastructure and in your data center which helps to mitigate risk and minimize vulnerabilities.

The installation process differs depending on the version you are installing. The following table shows the available versions.



Available versions

 Version Cluster Installation instructions 

 4.7.0 IBM Cloud Pak for Data 4.7.x [Installing 4.7.0](https://www.ibm.com/docs/SSQNUZ_4.7.x/svc-assistant/assistant-svc-install.html) 
 4.6.5 IBM Cloud Pak for Data 4.6.x [Installing 4.6.5](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-assistant/assistant-svc-install.html) 
 4.6.3 IBM Cloud Pak for Data 4.6.x [Installing 4.6.3](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-assistant/assistant-svc-install.html) 
 4.6.2 IBM Cloud Pak for Data 4.6.x [Installing 4.6.2](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-assistant/assistant-svc-install.html) 
 4.6.0 IBM Cloud Pak for Data 4.6.x [Installing 4.6.0](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-assistant/assistant-svc-install.html) 
 4.5.3 IBM Cloud Pak for Data 4.5.x [Installing 4.5.3](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-assistant/assistant-svc-install.html)
Setting up an IBM i network install server 

Before you can install or upgrade an IBM i system through the network, you must set up a network installation server. The network installation server contains images of the IBM i operating system, its internal code as well as licensed programs and PTFs. To share virtual optical images through a network, the network installation server must meet the following requirements:



  Configuration 

To complete the configuration of an IBM i network installation server, see [Virtual optical storage using the Network File System](https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzam4/rzam4virtualopstoragenfs.htm) and [IBM i Network Install](http://www.redbooks.ibm.com/redpapers/pdfs/redp4937.pdf).

Cloud Optical Repository (COR) is a virtual image that can be deployed and used as a Network File Server (NFS) to perform various IBM i tasks that require media. This virtual optical image includes a collection of the media necessary for various IBM i tasks, for all supported IBM i releases. With the COR image deployed, a second Power Systems Virtual Server Instance can be deployed on the same VLAN that is set up as the client and pointed to the COR (target) NFS Server Instance. For more information on COR images, see [Cloud Optical Repository](https://cloud.ibm.com/media/docs/downloads/power-iaas/Cloud_Optical_Repository.pdf).
* [Installing the virtualization operator](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-locationvirt-operator-install)
* [Setting up the virtctl CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-locationvirt-tools)
* [Creating a data volume for your virtual machine](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-locationvirt-vm-storage)
* [Creating a virtual machine](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-locationvirt-vm-create)
* [Additional resources](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-locationsat-virt-additional)







 Installing the CLI 

[Installing the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-installcli-install)



* [Understanding the CLI tools](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-installcli-understand)
* [Run the installation command](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-installcli-install-include-step1-install-idt)



[Updating the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-updatecli-update)



* [Updating the IBM Cloud CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-updatecli-update-include-update-ibmcloud-cli)
* [Updating installed plug-ins](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-updatecli-update-include-cli-update-plugin)
If you decide to add an SSH key, provide a public key of your SSH key, which you can use to log in to your instance after it is provisioned. 
 Image An image is the deployed operating system for your instance. You can select a number of free options such as CentOS and Ubuntu. Paid options such as Windows Server and Red Hat Enterprise Linux (RHEL) are also available. It's important to note that Windows requires a 100 GB primary disk. 







 Transient instance add-ons 

If you choose any software add-ons, they must be compatible with your image to avoid an error when you are ordering your instance. For example, you can’t provision a Red Hat image with a Microsoft database.



Table 2. Transient instance add-ons

 Field Details 

 Database software You can select a database software to install. IBM Cloud supports any database software that is deployed during the provisioning process. You can also install your own database software after the server is deployed. 
 Services Some services are automatically selected for you, depending on image selection. You can choose from any of the remaining service add-ons for your instance. 
 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.





 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.
Setting up your environment for your first order 

The setup information applies only to the following offerings: VMware vSphere, VMware vCenter Server, VMware Regulated Workloads, and Cyber Recovery.

When you order an instance for the first time, you might be prompted to follow a set of instructions to ensure that your environment is ready for your order.



 Procedure to set up your environment for your first order 

Follow the instructions in the Before you begin section on the instance order page. The instructions vary depending on the instance type and whether your account meets the requirements.

The following table lists the possible instructions and additional information for you to complete the tasks.



Table 1. Information for completing before you begin tasks

 If you are asked to... See... 

 ...upgrade your account [Upgrading to a Pay-As-You-Go account](https://cloud.ibm.com/docs/account?topic=account-upgrading-accountupgrade-paygo). <br>Subscription accounts are not supported for VMware®. 
 ...create an API key [Creating a classic infrastructure API key](https://cloud.ibm.com/docs/account?topic=account-classic_keyscreate-classic-infrastructure-key). <br>Additional steps:<br><br><br><br>1. In the IBM Cloud® for VMware Solutions console, retrieve your API key and username.<br>2. Click Settings from the left navigation pane and click Retrieve credentials.<br>3. Review the username and API key that are automatically entered and click Save credentials.<br><br><br> 
 ...locate an account administrator because admin access is required [Locating an IAM account administrator](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iam_verify_permissions) 
 ...convert to a VRF account [Converting to virtual routing and forwarding](https://cloud.ibm.com/docs/direct-link?topic=direct-link-what-happens-during-the-account-conversion-process)
A temporary license file is installed. The client will need to supply the final license file.





 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-SaaS 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-ms-getting-started-with-ibm-maximo-application-suite-managed-servicewelcome-letter) is sent to the client.
Due to these variations, provisioning of a server, adding network storage, and configuring network connectivity and interfaces differ for each. The process to order a VMware setup for manual configuration is similar to [Provisioning your Bare Metal server](https://cloud.ibm.com/docs/sap?topic=sap-bm-set-up-infrastructurebm-provision-server). Therefore, the sections to follow will not cover this option. Rather, the focus is on IBM Cloud for VMware Solutions Dedicated to using the vCenter Server (VCS) solution type.



 Before you begin 

The IBM Cloud® console requires a unique log-in ID, which is an IBMid.

Because ordering IBM Cloud for VMware Solutions Dedicated creates an Overlay Network that is managed by VMware NSX, there are several prerequisites for a VMware SDDC.

Complete the following tasks before your initial provisioning. Additional information and detailed steps for these tasks can be found in [Setting up your environment for your first order of IBM Cloud for VMware](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-completing_checklist) and [Requirements for the IBM Cloud Classic Infrastructure account when you use IBM Cloud for VMware](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cloud-infra-acct-req).



1. [Create an IBM Cloud Classic Infrastructure API key](https://cloud.ibm.com/docs/account?topic=account-classic_keyscreate-classic-infrastructure-key). This task coordinates the infrastructure setup for the VMware SDDC (such as VLAN, Subnet, Bare Metal).
=============================================================================

Installing:

bind x86_64 30:9.3.4-6.0.2.P1.el5_2 rhel-x86_64-server-5 965 k

Transaction Summary

=============================================================================

Install 1 Package(s)

Update 0 Package(s)

Remove 0 Package(s)

Total download size: 965 k

Is this ok [y/N]: y

Downloading Packages:

(1/1): bind-9.3.4-6.0.2.P 100% |=========================| 965 kB 00:00

Running rpm_check_debug

Running Transaction Test

Finished Transaction Test

Transaction Test Succeeded

Running Transaction

Installing: bind [1/1]

Installed: bind.x86_64 30:9.3.4-6.0.2.P1.el5_2

Complete!

[root@virtuozzo ] cat > /etc/named.conf <_EOF_

options

{

directory "/var/named";

forwarders { 10.0.80.11; 10.0.80.12; };

listen-on { 10/8; };

};

_EOF_

[root@virtuozzo ] chkconfig named on

[root@virtuozzo ] chkconfig --list named
Provisioning scripts 

A provisioning script is a script that can either be downloaded to, or downloaded and run on, a device during the provisioning process. For existing accounts, provisioning scripts are managed within the IBM Cloud® console. During the ordering process, you can manually enter scripts for new accounts or scripts that are not yet tracked.

Alternatively, you can use a cloud-init enabled image and provide user data to automatically perform configuration tasks or run scripts. For more information, see [Provisioning with a cloud-init enabled image](https://cloud.ibm.com/docs/image-templates?topic=image-templates-provisioning-with-a-cloud-init-enabled-image).

During the provisioning process, scripts that are associated with an HTTP URL are downloaded to the device. After provisioning, an administrator must run the script manually on the device. Scripts that are associated with an HTTPS URL are downloaded and run automatically. Provisioning scripts are currently available on only Linux operating systems (CentOS, RHEL, Fedora, Debian, or Ubuntu), and Windows and FreeBSD. The provisioning script can be any type of file that is run by the operating system, including combined binary files or any OS supported language.

For more information, see [Managing a provisioning script](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-a-provisioning-scriptmanaging-a-provisioning-script).
* Check that you see your new file system listed.

df -h



5. Add the new file system to the system's /etc/fstab file to enable automatic mounting on boot.



* Append the following line to the end of /etc/fstab (with the partition name from Step 3).

/dev/mapper/XXXp1 /PerfDisk ext3 defaults,_netdev 0 1





For more information about available command options, see [fdisk - manipulate disk partition table](https://manpages.ubuntu.com/manpages/xenial/man8/fdisk.8.html).





 Creating a file system with parted 

On many Linux® distributions, parted comes preinstalled. If it isn't included in your distro, you can install it with:



* Debian and Ubuntu

sudo apt-get install parted
* RHEL and CentOS

yum install parted



To create a file system with parted, follow these steps.



1. Run parted.

parted
2. Create a partition on the disk.



1. Unless it is specified otherwise, parted uses your primary drive, which is /dev/sda in most cases. Switch to the disk that you want to partition by using the command select. Replace XXX with your new device name.

select /dev/mapper/XXX
2. Run print to confirm that you are on the right disk.

print
3. Create a GPT partition table.

mklabel gpt
4. Parted can be used to create primary and logical disk partitions, the steps that are involved are the same. To create a partition, parted uses mkpart. You can give it other parameters like primary or logical depending on the partition type that you want to create. The listed units default to megabytes (MB). To create a 10-GB partition, you start from 1 and end at 10000. You can also change the sizing units to terabytes by entering unit TB if you want to.

mkpart
* [Setting up virtualization on a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-location)



* How to



* Installing the CLI



* [Installing the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-install)
* [Updating the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-update)
* [Uninstalling the stand-alone IBM Cloud CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-uninstall-ibmcloud-cli)



* [Planning your environment for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plan)
* Preparing your host infrastructure



* [Host system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs)
* [Host storage and attached devices](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-storage)
* [Host network requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network)
* [Required outbound connectivity for hosts overview](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound)
* Host outbound connectivity for Dallas



* [RHCOS enabled locations in Dallas](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-rhcos-outbound-dal)
* [Non-RHCOS enabled locations in Dallas](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-dal)
* [RHCOS enabled locations with reduced firewall in Dallas](https://cloud.ibm.com/docs/satellite?topic=satellite-req-minimum-outbound-dal)
* Internal IBM verification of the provisioned environments
* Welcome letter sent to the client / designated contacts indicating provisioning is complete







 Order Validation 

Once an order has been placed, the initial step is to validate the order and the information submitted. This includes checking the part numbers, ensuring the provisioning form has been completed, performing IBM internal financial checks and setting up the order to be provisioned. In general this can take 1 to 2 days to complete.

Once this is complete, the order is sent to the IBM MAS Dedicated Provisioning Team to begin the provisioning of the order.





 Information Gathering 

Once the order has been placed into the provisioning queue, additional information needs to be validated and gathered. This includes preparing the final architecture for the order; specifying the infrastructure needed to meet the order requirements; ensuring requested URL(s) are valid and available; detailed review of the order to ensure completeness; meeting or clarifying specific items with the sales person or client as required and setting up the provisioning parameters.

This step can take a few hours to several days depending on the initial quality and completeness of the information. Critical information that is needed includes:



* products that to be deployed (not all products will be deployed by default).
* anticipated sizing information for each product - this can be based on users, I/O or other metrics specific to each product URL being requested
* Languages required
* Add On and/or Industry Solutions required
* location of the majority of users to determine optimal placement of the Suite in the proper IBM Cloud data center



If this information is missing or incorrect it can cause delays in the provisioning process while this information is being confirmed.

Please confirm accuracy of your requested URL as it is embedded in the MAS core once provisioned and cannot be changed.





 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
Installing and configuring Ansible 

The automation server is provisioned and the initial operating system configuration is completed in the previous step. In this step, the following tasks are implemented:



1. [Installing Ansible](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-ansibleveeam-cr-sag-ansible-install).
2. [Adding Ansible collections](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-ansibleveeam-cr-sag-ansible-collections).
3. [Creating an Ansible inventory file](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-ansibleveeam-cr-sag-ansible-inv).
4. [Using Ansible vault to encrypt files](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-ansibleveeam-cr-sag-ansible-vault).
5. [Testing connections](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-ansibleveeam-cr-sag-ansible-test).



An optional step is included to [install the Ansible NSX-T collections](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-ansibleveeam-cr-sag-ansible-nsxt). The optional step is needed only if Ansible® is used to create sandboxes.



 Installing Ansible 

At a command line on the automation server, run the following commands.

sudo apt update
Adding a hard disk drive to Citrix XenServer 

Adding new hard disk drive in XenServer is different from the traditional Linux process. For XenServer, you need to create a container that is called a "storage repository" to define a particular storage target (such as a hard disk). This container is where virtual disk images (VDIs) of VMs are stored. A VDI is an abstracted storage space that acts as the hard disk for VMs.

Xen storage repository supports IDE, SATA, SCSI, and SAS drives when locally connected, apart from iSCSI, NFS, SAS, and Fibre Channel for remote storage.



 Creating a storage repository in a XenServer 

Use the following steps to create a storage repository in a XenServer.



1. SSH to the XenServer as root.
2. Find the disk ID of the new device by using the following command:

 cat /proc/partitions

The command lists of all the HDDs and partitions. Find your new local disk, which is probably “sdx” (most probably sdb) or '/cciss/c0d1p0'. Use the following command to list the disk IDs for all the partitions and or HDDs that are in the server.

 ll /dev/disk/by-id

Find the disk ID of the “sdx” or 'cciss/c0d1'disk. The “scsi-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx” or “cciss-xxxxxxxxxxxxxxxxxxxxxxxxxx” format is what you need.
3. Find the host-uuid in a XenServer by using the following command:

xe host-list

The uuid (RO) is the 'host-uuid' that you need.
4. Create a Storage Repository (SR):

The [sr-create](http://support.citrix.com/article/CTX121313) command is for adding a new hard disk drive.