vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Appliance installation size Medium (up to 400 hosts or 4,000 VMs) 
 Platform Services Controller Integrated 
 Number of vCPUs 8 
 Memory 28 GB 
 Disk 700 GB on local datastore (Large disk deployment) 
 Disk type Thin provisioned 





 vCenter Server database 

The vCenter Server configuration uses a local, embedded PostgreSQL database that is included with the appliance. The embedded database is used to remove any dependencies on external databases and licensing.





 vCenter Server cluster specification 

With this design, you can cluster the vSphere ESXi® hosts that are provisioned through the solution. However, before clusters can be created a data center object is created that signifies the location of the vSphere ESXi hosts and the pod within the data center. A cluster is created after the data center object is created. The cluster is deployed with VMware vSphere High Availability (HA) and VMware vSphere Distributed Resource Scheduler (DRS) enabled.





 vSphere Distributed Resource Scheduler 

This design uses vSphere Distributed Resource Scheduling (DRS) in the initial cluster to place VMs and uses DRS in additional clusters to dynamically migrate VMs to achieve balanced clusters. The automation level is set to fully automated so that initial placement and migration recommendations are run automatically by vSphere. Additionally, the migration threshold is set to moderate so that vCenter applies priority 1, 2, 3 recommendations to achieve at least a decent improvement in the load balance of the cluster.

Power management through the Distributed Power Management feature is not used in this design.





 vSphere High Availability 

This design uses vSphere High Availability (HA) in the initial cluster and in the additional clusters to detect compute failures and recover VMs that run in a cluster. The vSphere HA feature in this design is configured with both the Host Monitoring and Admission Control options that are enabled in the cluster. Additionally, the initial cluster reserves one node’s resources as spare capacity for the admission control policy.

You are responsible to adjust the admission control policy when the cluster is later expanded or contracted.

By default, the VM restart priority option is set to medium and the Host isolation response option is disabled.
ClientAsn Client AS number int 
 ClientBytes The number of bytes read from the client by the Spectrum service int 
 ClientCountry Country of the client IP address string 
 ClientIP Client IP address string 
 ClientMatchedIpFirewall Whether the connection matched any IP Firewall rules; UNKNOWNALLOWBLOCK_ERRORBLOCK_IPBLOCK_COUNTRYBLOCK_ASNWHITELIST_IPWHITELIST_COUNTRYWHITELIST_ASN string 
 ClientPort Client port int 
 ClientProto Transport protocol used by client; tcpudpunix string 
 ClientTcpRtt The TCP round-trip time in nanoseconds between the client and Spectrum int 
 ClientTlsCipher The cipher negotiated between the client and Spectrum string 
 ClientTlsClientHelloServerName The server name in the Client Hello message from client to Spectrum string 
 ClientTlsProtocol The TLS version negotiated between the client and Spectrum; unknownnoneSSLv3TLSv1TLSv1.1TLSv1.2TLSv1.3 string 
 ClientTlsStatus Indicates state of TLS session from the client to Spectrum; UNKNOWNOKINTERNAL_ERRORINVALID_CONFIGINVALID_SNIHANDSHAKE_FAILEDKEYLESS_RPC string 
 ColoCode IATA airport code of data center that received the request string 
 ConnectTimestamp Timestamp at which both legs of the connection (client/edge, edge/origin or nexthop) were established int or string 
 DisconnectTimestamp Timestamp at which the connection was closed int or string 
 Event connectdisconnectclientFilteredtlsErrorresolveOriginoriginError string 
 IpFirewall Whether IP Firewall was enabled at time of connection bool 
 OriginBytes The number of bytes read from the origin by Spectrum int 
 OriginIP Origin IP address string 
 OriginPort Origin port int 
 OriginProto Transport protocol used by origin; tcpudpunix string 
 OriginTcpRtt The TCP round-trip time in nanoseconds between Spectrum and the origin int 
 OriginTlsCipher The cipher negotiated between Spectrum and the origin string 
 OriginTlsFingerprint SHA256 hash of origin certificate string
Client Version: 4.10.23

 zip
Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license.
This is Zip 3.0 (July 5th 2008), by Info-ZIP.

 unzip
UnZip 6.00 of 20 April 2009, by Debian. Original by Info-ZIP.

 git --version
git version 2.37.1

 curl
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3

 wget
GNU Wget 1.19.4 built on linux-gnu.

 openssl version
OpenSSL 1.1.1 11 Sep 2018

 make
GNU Make 4.1

 docker
Client:
Version: 20.10.16
API version: 1.41
Go version: go1.17.10
Git commit: aa7e414
Built: Thu May 12 09:14:28 2022
OS/Arch: linux/amd64
Context: default

 dc --version
dc (GNU bc 1.07.1) 1.4.1

 ed --version
GNU Ed 1.10
Show more





 Version 2.20 

To view the contents of version 2.20, from the running image, type default_versions.sh.

The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).
* The <vcsa_user> is the username of the account in vCenter appliance that has necessary privileges to add roles.
* The <vcsa_user_password> is the password for the <vcsa_user>.
* The <sub_domain> is the subdomain of the root domain, that is, for example.test.local, <sub_domain> is example and <root_domain> is test.local.



4. Use the following commands to create the role and assign permissions:



Add-PSSnapin VMware.VimAutomation.Core -ea "SilentlyContinue"
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Confirm:$false | Out-Null
$vcsa = "<vcsa_fqdn>"
$vcsauser = "<vcsa_user>"
$vcsapassword = '<vcsa_user_password>'
$securevcsapassword = ConvertTo-SecureString -String $vcsapassword -AsPlainText -Force
$sn = "sa-veeam-cyber-admin"
$id = "<sub_domain>"
$role = "veeambur"
$principal = "$id$sn"
$creds = New-Object System.Management.Automation.PSCredential -ArgumentList $vcsauser,$securevcsapassword
$privileges = @(
'System.Anonymous',
'System.View',
'System.Read',
'Global.ManageCustomFields',
'Global.SetCustomField',
'Global.LogEvent',
'Global.Licenses',
'Global.Settings',
'Global.DisableMethods',
'Global.EnableMethods',
'Folder.Create',
'Folder.Delete',
'Datastore.Browse',
'Datastore.DeleteFile',
'Datastore.FileManagement',
'Datastore.AllocateSpace',
When you choose the locations where you plan to provision IBM Cloud Activity Tracker instances, check the regulatory and high availability (HA) specifications of each location.

For example, in Europe, only the Frankfurt region is EU-supported.

You can also check [ensure zero downtime](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the high availability and disaster recovery standards in IBM Cloud.





 Resource groups 

Resource groups are a logical container for organizing your IAM-enabled resources.



* IAM-enabled services belong to a resource group. The IBM Cloud Activity Tracker service is an IAM-enabled service.
* You assign a resource to its resource group when you create it from the catalog.
* You can't change the resource group assignment after you set it, which is why it's important to plan your resource groups.
* If you add PII information in the resource group name, you might be disclosing sensitive data to others in the same account.



Use a resource group, that only includes Activity Tracker instances, to organize your IBM Cloud Activity Tracker instances for access control and billing purposes.

Account owners can add resources to any resource group. Other users must be granted access by using an IAM access policy to add resources to resource groups. For more information, see [Best practices for organizing resources and assigning access](https://cloud.ibm.com/docs/account?topic=account-account_setup).

When you define your resource groups, do not add sensitive information in the name.





 Naming 

If you add PII or other sensitive information in the name or the description of a service instance, you might be disclosing sensitive data to others in the same account.

When you define your auditing instances names, do not add sensitive information in the name or in the description.





 Service plan 

The service plan that you choose determines the number of days that data is available for search. For more information, see [Service plans](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_plan).
An execution plan has been generated and is shown here.
Resource actions are indicated with the following symbols:
+ create

Terraform on IBM Cloud perform the following actions:

+ ibm_compute_vm_instance.vm1
id: <computed>
block_storage_ids.: <computed>
cores: "1"
datacenter: "dal09"
disks.: "1"
disks.0: "25"
domain: "example.com"
file_storage_ids.: <computed>
hostname: "vm1"
hourly_billing: "true"
ip_address_id: <computed>
ip_address_id_private: <computed>
ipv4_address: <computed>
ipv4_address_private: <computed>
ipv6_address: <computed>
ipv6_address_id: <computed>
ipv6_enabled: "false"
ipv6_static_enabled: "false"
local_disk: "false"
memory: "1024"
network_speed: "10"
os_reference_code: "DEBIAN_8_64"
private_interface_id: <computed>
private_network_only: "false"
private_security_group_ids.: <computed>
private_subnet: <computed>
private_subnet_id: <computed>
private_vlan_id: <computed>
public_bandwidth_limited: <computed>
public_bandwidth_unlimited: "false"
public_interface_id: <computed>
public_ipv6_subnet: <computed>
public_ipv6_subnet_id: <computed>
public_security_group_ids.: <computed>
public_subnet: <computed>
public_subnet_id: <computed>
public_vlan_id: <computed>
secondary_ip_addresses.: <computed>
wait_time_minutes: "90"

Plan: 1 to add, 0 to change, 0 to destroy.
The ESXi servers are fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted ESXi servers.







 Related links 



* [Planning for VMware vSphere](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_planning)
* [Procedure to order VMware vSphere instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_orderinginstances-procedure)
* [Place a host in maintenance mode](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.resmgmt.doc/GUID-8F705E83-6788-42D4-93DF-63A2B892367F.html)
* [Enhanced vMotion Compatibility (EVC) processor support](https://kb.vmware.com/s/article/1003212)
If your cluster includes multizone support, you need to bring your own storage solution. You can choose from several [persistent storage options](https://cloud.ibm.com/docs/containers?topic=containers-storage_planningpersistent_storage_overview).

If you are setting up an IBM Blockchain Platform network in an MZR cluster and want your components to eventually fail over between data centers, you should select Portworx as your storage type. Otherwise, if you use File Storage for your node in your MZR cluster and the zone fails, you will need to provision that component again later. Currently, if a data center (or zone) goes down, the node will not automatically come up in another zone, regardless of the storage type that is used for the node. However, if one of the nodes fails in a single zone, it will automatically failover to another node in the same zone regardless of the storage type that is being used for that node.

After you create the storage class, run the kubectl patch storageclass command above to set the storage class of the multizone region to be the default storage class.





 Pricing and Billing information 



* See [Pricing](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricing) if you need to revisit the IBM Blockchain Platform pricing information.
* Your current IBM Cloud usage information is available on your [usage tile](https://cloud.ibm.com/billing/) of the IBM Cloud dashboard and your bill is visible under [billing information](https://cloud.ibm.com/billing/billing-items). See this topic on [Billing](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-billing) for more details about how IBM Blockchain Platform billing works.







 Choose your deployment process 

From your IBM Cloud account, you can deploy the IBM Blockchain Platform service from either the IBM Cloud Catalog or the Red Hat Marketplace.



* IBM Cloud Catalog Use the IBM Cloud Catalog to deploy blockchain to an IBM Kubernetes service or OpenShift cluster in IBM Cloud.
You can always submit new request through “Help” on Applications Lab main page.



Once we gather all the information, our engineer will setup and configuration your instance env and once it is completed, the instance status will be set to "Active", and billing will start for that month based on the plan you ordered.





 What information is required from client to setup Federated Single Sign-On? 

If clients choose to use federated ID authentication, clients need to provide following information:



1. Download Cloud for Education metadata from [https://fed.education.cloud.ibm.com/simplesaml/module.php/saml/sp/metadata.php/default-sp](https://fed.education.cloud.ibm.com/simplesaml/module.php/saml/sp/metadata.php/default-sp)
2. Import the downloaded metadata to clients' federated server
3. Export and email clients' federated server metadata to [eduhelp@ibm.com](mailto:eduhelp@ibm.com)
4. Configure clinets' federated server to share the necessary attributes includes: email, first name, last name and user groups.







 What information is required from client to setup VPN? 

If clients' VMs running on IBM Cloud for Education need to access resources on clients' internal network, such as clients' license servers, data etc, we can setup VPN to access clients' internal network, In order to setup VPN, clients need to provide following information to IBM:



* VPN account
* VPN connection information (e.g endpoint URL)
* The name of the image requiring VPN access







 When I order "Base Flex Plan", it says each authorized user entitled for one VM, what if user needs to provision more than one VM? 

Applications Lab Base Flex Plan (a.k.a. per authorized user plan) allows maximum one reservation at a time. If you want to have multiple reservations at the same time, please use other plans or use mutiple accounts.





 What happens when I delete my service instance? 

The service instance will not appear on Resource List and billing of the instance stops from next month.
Added Code Engine billing.
: See [Pricing for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).

Updated CPU and memory limits for jobs and apps.
: See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).





 25 March 2021 

Review the release notes for 25 March 2021.

Added Code Engine monitoring information.
: See [Monitoring for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-monitor).

Added information for determining CPU and memory combinations.
: See [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo).

Code Engine Tutorial
: See [Code Engine Tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-github-traffic-analytics).





 23 March 2021 

Review the release notes for 23 March 2021.

Code Engine is supported in a new region: Asia Pacific (jp-tok).
: See [Regions for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regions).

Added Code Engine high availability and disaster recovery documentation.
: See [Understanding high availability and disaster recovery for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ha-dr).





 22 March 2021 

Review the release notes for 22 March 2021.

CLI version 0.6.1 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 18 March 2021 

Review the release notes for 18 March 2021.

CLI versions 0.6.0 and 0.5.25 released.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 IBM Cloud Monitoring ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 Platform services 



Table 6. Integrated security services integration in America locations

 Global service Location 

 Billing Events are available through the Activity Tracker Frankfurt (eu-de) instance 
 User management Events are available through the Activity Tracker Frankfurt (eu-de) instance
* If your original volume is 2, 4, or 10 IOPS Endurance tier, you can move anywhere between those tiers for the new volume.



11. Check the box if you read and agreed to the terms and conditions.
12. Click Create to continue.







 Creating a duplicate from the Volume detail page the UI 



1. Go to your list of Block Storage for Classic.
2. Click a LUN from the list to view the details page. (It can either be a replica or a primary volume.)
3. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg)> Duplicate Volume.
4. Select whether the duplicate is to be dependent or independent.
5. Select the snapshot option to be used to create the duplicate. You can choose an existing Snapshot or take a new one.
6. The location entries remain the same as the original volume.
7. Hourly or Monthly Billing – you can choose to provision the duplicate LUN with hourly or monthly billing. The billing type for the original volume is automatically selected. If you want to choose a different billing type for your duplicate storage, you can make that selection here.
8. You can update the size of the new volume so that it's larger than the original. The size of the original volume is set by default.

Block Storage for Classic can be resized to 10 times the original size of the volume.
9. You can update the snapshot space for the new volume to add more, less, or no snapshot space.
10. You can select the OS Type to be different than the original volume or to stay the same.
11. You can specify IOPS or IOPS Tier for the new volume if you want to. The IOPS designation of the original volume is set by default. Available Performance and size combinations are displayed.
2. You are notified by email that your request to remove NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3. The NFS storage is fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the removed NFS storage.







 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
* [Planning for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning)
* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Deleting clusters from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingclusters)
* [Place a host in maintenance mode](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.resmgmt.doc/GUID-8F705E83-6788-42D4-93DF-63A2B892367F.html)
* [Enhanced vMotion Compatibility (EVC) processor support](https://kb.vmware.com/s/article/1003212)
* [Consider the availability that you want for your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clusters). For example, a basic high availability setup is one multizone cluster with two worker nodes in each of three zones, for a minimum total of 6 worker nodes.



3. Check out other IBM Cloud services, add-ons, operators, and other third-party software that you might use that can increase your cost. To get an idea of what other costs clusters typically incur, review [Understanding costs for your clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-costscosts-for-clusters).
4. [Estimate your costs](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-costcost) and review detailed pricing information for the service, see [IBM Cloud Kubernetes Service: Pricing](https://www.ibm.com/products/openshift).
5. Manage the lifecycle of your cluster to control costs.



* Consider [enabling the cluster autoscaler](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-classic-vpc) to automatically add or remove worker nodes in response to your cluster workload resource requests.
* Manually [resize your worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workers) to remove worker nodes that you don't need. Keep in mind that you can't scale a worker pool down to zero worker nodes.
* To save the updates to a new saved configuration, click Save configuration, select Create new configuration, enter a new name for the configuration, and click Continue.



13. To place the order, ensure that the account to be charged is correct, review and accept the terms, and then click Create.





 Related links 



* [Adding clusters to Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingclusters)
* [Expanding and contracting capacity](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingservers)
List the PVCs in your cluster and note the NAME of the PVC, the STORAGECLASS, and the name of the PV that is bound to the PVC and shown as VOLUME.

oc get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
claim1-block-bronze Bound pvc-06886b77-102b-11e8-968a-f6612bb731fb 20Gi RWO ibmc-block-bronze 78d
claim-file-bronze Bound pvc-457a2b96-fafc-11e7-8ff9-b6c8f770356c 4Gi RWX ibmc-file-bronze-retain 105d
claim-file-silve Bound pvc-1efef0ba-0c48-11e8-968a-f6612bb731fb 24Gi RWX ibmc-file-silver 83d
2. Review the ReclaimPolicy and billingType for the storage class.

oc describe storageclass <storageclass_name>

If the reclaim policy says Delete, your PV and the physical storage are removed when you remove the PVC. If the reclaim policy says Retain, or if you provisioned your storage without a storage class, then your PV and physical storage are not removed when you remove the PVC. You must remove the PVC, PV, and the physical storage separately.

If your storage is charged monthly, you still get charged for the entire month, even if you remove the storage before the end of the billing cycle.
3. Remove any pods that mount the PVC. List the pods that mount the PVC. If no pod is returned in your CLI output, you don't have a pod that uses the PVC.

oc get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"

Example output