vania-janet/multiturn-rag-retrieval-data huggingface dataset:
System requirements 

The analytics cluster consists of one primary node, one primary replica node, and two data nodes to enable scaling out and high availability. More data nodes are added to scale up. The analytics cluster can scale to a maximum of eight medium-sized nodes.

Primary/replica node system settings

Data node system settings



Table 1. Operations Manager primary/replica node system settings

 Attribute Specification 

 vCPU 8 
 Memory 32 GB 
 Disk (thick provisioned) 254 GB 



When the compute VM monitoring is required, the client installs two remote collector nodes on a VXLAN. The size of a Standard Remote Collector Virtual Appliance is 2 vCPU with 4 GB of RAM and the default appliance VMDK size is sufficient. The remote collector nodes are deployed with thin-provisioned disks as the remote collectors do not run analytics operations or store data.



Table 2. Operations Manager Load Balancer settings

 Setting Load balancer 1 Load balancer 2 

 Name vrops-ui vrops-data 
 Interval 30 5 
 Timeout 5 15 
 Max Retries 3 
 Type HTTPS TCP 
 Method Get 
 URL /suite-api/api/deployment/node/status 
 Receive Online 
 Algorithm ROUND-ROBIN LEASTCONN 
 Pool Four nodes of VMware Aria Operations Four nodes of VMware Aria Operations 







 Networking 

Deployment of the VMware Aria Operations appliance requires six IP addresses from the Tooling private portable subnet. Network connectivity VMware Aria Operations requires access to the following items.



* vCenter Appliance
* VMware Aria Operations for Logs Appliance
* VMware NSX-T™ or NSX-V Appliances
* Tools Expansion VXLAN
* Customer Networks
* NTP server (time.services.softlayer.com)
* IBM Cloud for VMware Solutions Active Directory, DNS
* The Remote Collectors require NAT rules on the NSX ESG to enable connectivity to the primary node, primary node replica, and data nodes







 Ports 



Table 3. Operation Manager ports

 Component Protocol Port 

 vCenter Server TCP 443 
 DNS TCP/UDP 53
[External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://youtu.be/kp8dcM9AKrA?cm_sp=Developer-_-extend-watson-text-classification-_-Watch-the-video)







 Fingerprinting personal data from unstructured text 

Build a custom model using Watson Natural Language Understanding and Watson Knowledge Studio.



* [Learn more ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/patterns/fingerprinting-personal-data-from-unstructured-text/)
* [Get the Code ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://github.com/IBM/gdpr-fingerprint-pii)
* [Blog Post ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://youtu.be/NiBCa3EtCr0)







 Use Swift to interpret unstructured data from Hacker News 

Use cognitive APIs to gain insight into tech trends on Hacker News with a twist.



* [Learn more ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/patterns/use-swift-interpret-unstructured-data-hacker-news/)
* [Get the Code !
VRF is enabled at the account level, so all resources are affected by this networking change. For more information about VRF technology and how it affects your account's network routing, see [Virtual routing and forwarding on IBM Cloud](https://cloud.ibm.com/docs/dl?topic=dl-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud).

Enabling VRF permanently alters networking for your account. Be sure that you understand the impact to your account and resources. After you enable VRF, it cannot be disabled.

To enable VRF, create a support case with your request. This option applies only to billable accounts.



1. In the console, go to Manage > Account, then click Account settings.
2. In the Virtual routing and forwarding section, click Create case.
3. In the case description, enter your classic infrastructure account number, and click Submit.

Don't change the rest of the prefilled support case information. The information is tailored to make sure that your request is handled as quickly as possible.



The IBM Cloud network engineering team will contact the case owner to schedule a time for your account's networking to be converted to VRF. During the conversion process, connections to resources in your account might be unstable due to packet loss. The conversion takes roughly 15 - 30 minutes, depending on the complexity of your account. If your account has legacy IBM Cloud® Direct Link connections, it might take more time.

Changing an empty account to VRF modifies the behavior of the future resources with no interruption. A short intermittent connectivity loss can occur between your existing servers on the private network during the migration process, which is scheduled at a convenient time for you.

The migration does not make any changes to the public network configuration of your VLANs or subnetworks. However, if you have any web or application servers that provide a public-facing service that relies on a private network connection to reach a database, application, or other type of server, be aware that the public-facing service might be disrupted.

VRF is not compatible with IPSec VPN services and limits SSL VPN connections to the resources in the data center of the connection.
The migration does not make any changes to the public network configuration of your VLANs or subnetworks. However, if you have any web or application servers that provide a public-facing service that relies on a private network connection to reach a database, application, or other type of server, be aware that the public-facing service might be disrupted.

VRF is not compatible with IPSec VPN services and limits SSL VPN connections to the resources in the data center of the connection. Alternatively, you can purchase IBM Cloud® Direct Link products for management of your servers, or run your own VPN solution that can be configured with different types of VPNs.





 Enabling service endpoints 

When IBM Cloud service endpoints are enabled in your account, you can choose to expose a private network endpoint when you create a resource. You can then connect directly to this endpoint over the IBM Cloud private network rather than the public network. Because resources that use private network endpoints don't have an internet-routable IP address, connections to these resources are more secure. For more information, see [Secure access to services using service endpoints](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview).

Before you can enable service endpoints, VRF must be enabled for your account. Virtual Private Clouds (VPCs) are automatically enabled for VRF.



 Enabling service endpoints in the console 



1. In the console, go to Manage > Account, then click Account settings.
2. In the Service endpoints section, click On.

If you can't click the button, VRF might not be enabled for your account. Verify that it's enabled by checking the virtual routing and forwarding section, which is the preceding section in your account settings.
3. Review the impacts to your account, and click On.



It might take a few minutes for this change to take effect.





 Enabling service endpoints in the CLI 

To enable service endpoints from the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started), you need version 0.13 or later.



1.
For more information, see:



* [vCenter Server overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview)
* [Expanding and contracting capacity for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)



If you change your credentials, for example passwords, IBM Support might no longer be able to help you recover lost or forgotten credentials, or to troubleshoot any problems in your environment. For more information, see [Client responsibilities](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_compl_infovc_compl_info-client-responsibilities).

Changes to VMware ESXi server names or configurations might have a negative impact on managing your instance. For more information, see:



* [Can I change the ESXi server names and IP addresses?](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq_esxifaq_esxi-change-name-ip)
* [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impact)



In IBM Cloud for VMware Solutions, every primary instance deploys an Active Directory domain controller. Review the following to understand limitations on changes that you can make and recommendations on integration in your environment.



* [VMware Solutions infrastructure domain](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-adds-infra-domain)
* [VMware Solutions workload domain](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-adds-wkld-domain)







 Related links
You can change one component, for example, config.HostAgent.level[Vimsvc].logLevel that defines the level of logging for Virtual infrastructure management services in that host.

You can change the log level of the host that is applied across all components by checking Config.HostAgent.log.level. This value is set by default ot info.
4. For each component that you plan to modify, enter the value that you want. Then, click OK.

For each component that you plan to modify, enter the value that you want. Valid values are none, quiet, error, warning, info, verbose, and trivia.

For the host log level setting, , enter the value that you want. Valid values are debug, error, warning, and info.
5. Restart the ESXi host to reload the syslog daemon and enable the new log level.



When you set the log level to verbose or to trivia, you add SOAP message content to the log record that you can use when you are debugging a problem.





 Set the Log Level on NSX ESXi hosts 

Complete the following steps to change the log level that is configured for NSX ESXi hosts:



1. Launch the vSphere Client.
2. Select the vCenter or NSX host host that you want to modify. Then, select Actions > Edit Settings.
3. Click VM Options.
4. In the Advanced section, check the option in Settings for Enable logging is selected. Then, select for Debugging and statistics the level of logging. Valid values are Run normally, Record debugging information, and Record Statistics.
5. Click OK.
Authorization considerations for cross-account virtual connections 

The following table shows the authorization changes for cross-account virtual connections.

A cross-account virtual connection means that the gateway exists in an IBM Cloud account and a virtual connection in that gateway connects to a VPC in a different IBM Cloud account. This setup requires special authorization considerations because the objects (the directlink gateway and the VPC) and their resource groups do not exist in both accounts.



Table 2. Authorization changes for cross-account virtual connections

 Related account Capability Required authorization 

 Gateway account Any capabilities not mentioned in this table. No authorization changes. 
 Gateway account Create and delete a cross-account virtual connection. directlink.dedicated.edit or directlink.connect.edit <br>No VPC authorization required at create or delete time. 
 Network account View read-only gateways and virtual connections. Service-level directlink.dedicated.view or directlink.connect.view 
 Network account Accept and reject pending connections. Service-level directlink.dedicated.view or directlink.connect.view <br>Update authorization on the connected VPC. 
 Network account DELETE attached virtual connection. Service-level directlink.dedicated.view or directlink.connect.view <br>Update authorization on the connected VPC. 







 Assigning access to Direct Link in the CLI 

For step-by-step instructions for assigning, removing, and reviewing access, see [Assigning access resources by using the CLI](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources&interface=cliaccess-resources-cli). The following example shows a command for assigning the Editor role to a user:

Use directlink for the service name. Also, use quotations around role names that are more than one word like the example here.

ibmcloud iam user-policy-create USER@EXAMPLE.COM --service-name directlink --roles Editor





 Assigning access to Direct Link by using the API
A message displays if you must power off the VM before you modify a disk setting. For more information, see [Power off a virtual machine](https://docs.vmware.com/en/VMware-Cloud-Director/10.0/com.vmware.vcloud.tenantportal.doc/GUID-2323B049-4E36-4510-999E-F2D4A77AC0F9.html).

For more information about changing a storage policy, see [Change the general properties of a virtual machine](https://docs.vmware.com/en/VMware-Cloud-Director/10.0/com.vmware.vcloud.tenantportal.doc/GUID-8301D672-8333-4FD2-B132-2D4A42E11216.html).

If you must power off the VM before you change a storage policy, power the VM back on after the VM is moved to the new storage policy. For more information, see [Power on a virtual machine](https://docs.vmware.com/en/VMware-Cloud-Director/10.0/com.vmware.vcloud.tenantportal.doc/GUID-33C22124-A610-4C3E-8F40-26CAC570F958.html).







 Enabling a compute policy 

Compute policies are applied for VMware stretched vSAN virtual data centers. When you create a new VM in a stretched location, it uses the compute_policies available for that virtual data center. Additionally, you can change from one compute policy to another by editing your VM hardware properties.

During a failover, a VM moves to a secondary site. When the preferred site is recovered, the VM automatically returns back to the preferred site with the compute policies restored.

You can select the compute policy that you prefer for each VM and VMware Solutions attempts to keep the VM on the preferred data center if it is up and running.



1. From the tenant portal, click Virtual Machines from the left panel.
2.
Reconfiguring an existing virtual server 

After you provision IBM Cloud® Virtual Servers, you can upgrade or downgrade your server configurations at any time.

Various public virtual servers are available in pre-set profiles. For a limited time, you can modify any virtual servers that were available before pre-set profiles. Then, you are required to migrate or cancel the existing instances and reorder.

You cannot modify the individual core, RAM, or disk size of a virtual server that uses profiles. You must pick a different profile that has the pre-set cores, RAM, and disk size you need. The virtual server profile that you select determines the valid cores, RAM, and disk sizes.

Dedicated virtual servers are more customizable than public virtual servers. Therefore, you can modify the individual cores, RAM, and disk sizes.



 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 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).





 Resizing an existing virtual server 

Complete the following steps to resize an existing virtual server that uses pre-set profiles.



1. From the Devices menu, select Device List.
2. From the Device List, click the name of the virtual server that you want to resize.
3. Select Resize.
4. In the Resize window section, specify the window of time your system is down to perform the update.
The following table lists the operations that might be impacted if the SSO administrator changes VMware vCenter Server resources outside of the IBM Cloud for VMware Solutions console. If a solution to recover is available, it is provided as well.

The following table is applicable to instances deployed in V1.8 and earlier, including the ones that were initially deployed in V1.8 and earlier and then upgraded to V1.9 or later.



Table 1. Operations that are impacted by changing VMware resources

 Attempted change Impacted operations Severity Recovery method 

 Change the VMware virtual data center name. Adding a VMware virtual data center might fail because the new ESXi server cannot join the changed virtual data center. Important Change the VMware virtual data center name back to the original name. 
 Change any port group names. Adding an ESXi server might fail. Important Change the port group name back to the original name. 
 Change the cluster name. Adding an ESXi server might fail. Important Change the cluster name back to the original name. 
 Change the public or private Distributed Virtual Switch (DVS) name. Adding an ESXi server might fail. Important Change the public or private Distributed Virtual Switch (DVS) name to the original name. 
 Change the vSAN datastore name in the instance that uses vSAN. Adding an ESXi server might fail.<br><br>Upgrading the instance might fail. Important Change the vSAN datastore name back to the original name, vsanDatastore. 
 Change the management NFS datastore name in the instance that uses NFS. Adding an ESXi server might fail.<br><br>Upgrading the instance might fail. Important Change the NFS management datastore name back to the original name, management-share, and remount the NFS datastore as read-only on the ESXi server. 



The following table lists the operations that might be impacted if SSH or shell access is disabled for various resources.



Table 2. Operations that are impacted by SSH and shell access (local)

 Attempted change Impacted operations Severity Recovery method 

 Disable SSH or shell access for vCenter Server or PSC. Pairing a primary and secondary instance might fail.
For more information, see [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices).







 Considerations when you delete FortiGate Security Appliance 

Review the following considerations before you delete the FortiGate Security Appliance service:



* Deleting the FortiGate Security Appliance service deletes the public VLAN that was added.
* During the service deletion, your instance might not be able to access the internet temporarily.
* All FortiGate rules to permit, inspect, block, and route NAT traffic are deleted together with the Fortinet service. If you have any NAT rules, you must reconfigure them.
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click the name of a virtual server instance that includes the network interface that you want to edit. Or you can add a network interface to the virtual server instance.
3. On the Instance details page, find the Network interfaces section.
4. For specific steps for adding a floating IP address or adding a network interface, see the following sections.





 Adding a network interface 

You can add up to 15 network interfaces to your virtual server instance, depending on the vCPU count that is included in the instance profile. A network interface establishes a unique IP address, giving the option of multiple IP address for your virtual server instance. Before you begin adding an interface, make sure that you created a unique subnet to associate with the new network interface. Each network interface must be on a different subnet within the same zone.

To add a network interface to your virtual server instance, complete the following steps.



1. In the Network interfaces section of the Instance details page, click New interface.
2. On the New network interface page, the interface name defaults to an incremented number. If this instance is the first new interface after your primary interface, the default name is eth1. You can change the name if you want.
3. Select a unique subnet from the subnets that are assigned to your existing network interfaces.
4. Select the security group that you want to associate with the network interface.
5. Click Create.
6. If your virtual server instance was running when you added the network interface, you must configure the network interface for the instance. You can either stop and then restart the instance, or you can manually configure the interface in the guest operating system. For example, on a Linux-based operating system, you can use the ip link set dev <interface> up to retrieve the IP address configuration for the interface.
"Authorized" hosts are hosts that were given access to a particular LUN. Without host authorization, you can't access or use the storage from your system. Authorizing a host to access your LUN generates the username, password, and iSCSI qualified name (IQN), which are needed to mount the multipath I/O (MPIO) iSCSI connection.

You can authorize and connect hosts that are located in the same data center as your storage. You can have multiple accounts, but you can't authorize a host from one account to access your storage on another account.



1. Click Storage > Block Storage for Classic.
2. Locate the volume and click the ellipsis ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg).
3. Click Authorize Host.
4. To see the list of available devices or IP addresses, first, select whether you want to authorize access based on device type or subnets.



* If you choose Devices, you can select from Bare Metal Server or Virtual Server instances.
* If you choose IP address, select the subnet where your host resides.



5. From the filtered list, select one or more hosts that can access the volume and click Save.



The default limit for the number of authorizations per block volume is eight. That means that up to eight hosts can be authorized to access the Block Storage for Classic LUN. Customers who use Block Storage for Classic in their VMware deployment can request the authorization limit to be increased to 64. To request a limit increase, contact your sales representative or raise a [Support case](https://cloud.ibm.com/unifiedsupport/cases/add).





 Authorizing hosts to access Block Storage for Classic from the SLCLI 

"Authorized" hosts are hosts that were given access to a particular LUN. Without host authorization, you can't access or use the storage from your system.