vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Watson Query](https://cloud.ibm.com/docs/data-virtualization?topic=data-virtualization-getting-started) data-virtualization [Location-based events](https://cloud.ibm.com/docs/data-virtualization?topic=data-virtualization-activity-tracker) 







 Compute serverless services 

The following table lists serverless compute services that send auditing events:



Table 2. List of serverless compute services

 Service CRN service name Events 

 [IBM Cloud® Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-started) functions [Location-based events](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-at_events) 







 Database services 

The following table lists database services that send auditing events:



Table 3. List of database services

 Service CRN service name Events 

 [IBM Cloud® Databases for EnterpriseDB](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-getting-started) databases-for-enterprisedb-group [Location-based events](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-activity-tracker) 
 [IBM Cloud® Databases for DataStax](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-getting-started) databases-for-cassandra-group [Location-based events](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-activity-tracker)
This comparison equates to 10 continuously running and billable processes in a single availability zone, 20 when run across 2 availability zones, and 40 when run across two regions with two zones each. To achieve the same goal with Cloud Functions, you can run them across as many availability zones or regions as you like, without having to pay a penny of incremental costs.





 Web apps 

Given Cloud Functions’s event-driven nature, it offers several benefits for user-facing applications, whereas the HTTP requests coming from the user’s browser serve as the events. Cloud Functions applications use compute capacity and billed only when they are serving user requests. Idle standby or waiting mode is nonexistent. This feature makes Cloud Functions considerably less expensive when compared to traditional containers or Cloud Foundry applications. Both of those tools have idle time, waiting for inbound user requests, and you are billed for all that “sleeping” time.

Full web application can be built and run with Cloud Functions. Combining serverless APIs with static file hosting for site resources such as HTML, JavaScript, and CSS, means that you can build entirely serverless web applications. The simplicity of operating a hosted Cloud Functions environment is not having to operate anything at all. Since Cloud Functions is hosted on IBM Cloud, it is a great benefit when compared to standing up, and operating a Node.js Express or other traditional server runtime.





 IoT 

Internet of Things scenarios are often inherently sensor-driven. For example, an action in Cloud Functions might be triggered if a need to react to a sensor that exceeds a specific temperature. IoT interactions are usually stateless with the potential of high load in major spontaneous events such as natural disasters, significant weather storms, or traffic jams. A need is created for an elastic system where normal workload might be small, but needs to scale quickly with predictable response time. So the ability to handle many simultaneous events with no prior warning to the system is desirable. It is difficult to build a system to meet these requirements that use traditional server architectures. As they tend to either be underpowered, and unable to handle peak load in traffic, or be over-provisioned and highly expensive.

It is possible to implement IoT applications that use traditional server architectures.
For more information, see [Viewing and managing virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-summary).





 Related links 



* [Operating VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guide)
* [VMware Cloud Director](https://www.vmware.com/ca/products/cloud-director.html)
This option is suitable for saving resources and costs with independent networking control per VDC. 
 Performance - M This option is suitable when only L2 through L4 features such as NAT, routing, L4 firewall, L4 load balancer are required and the total throughput requirement is less than 2 Gbps. 
 Performance - L This option is suitable when only L2 through L4 features such as NAT, routing, L4 firewall, L4 load balancer are required and the total throughput is in the range 2 - 10 Gbps. 
 Performance - XL This option is suitable when the total throughput required is multiple Gbps for L7 and VPN. 



Alternatively, toggle Create without network edge on. This option is suitable for centralized networking administration and control over multiple VDCs.
8. Review the cost, accept the terms, and click Create to submit the VDC order.







 Results after you add virtual data centers 



* The deployment of the resources starts automatically and you receive confirmation that the order is being processed. You can check the deployment status, including any issues that might require your attention, by viewing the VDC status.
* When all resources are successfully deployed, the ordered components are installed on your virtual platform.
* When the resources are ready to use, the status of the VDC is changed to Available.







 What to do next 



1. [View the virtual data center](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-view-deletevdc-view-delete-details) that you ordered.
2. [Set the admin password](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-accessing-vcd-consoleaccessing-vcd-console-reset-proc) for the VMware Cloud Director console.







 Related links 



* [Viewing and deleting virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-view-delete)
Ordering services for vCenter Server instances 

You can order services for your VMware vCenter Server® instances, such as a disaster recovery solution. Add-on services support varies between vCenter Server with NSX-T™ and existing vCenter Server with NSX-V instances V4.7 and earlier.

If you want to migrate your F5 BIG-IP or Veeam services from VMware NSX-V to VMware NSX-T, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).



 Before you add services to vCenter Server instances 



* Adding services to vCenter Server instances with VMware vSphere® 6.5 is not supported.
* For existing vCenter Server multizone instances, adding services is not supported. However, you can view or delete existing add-on services. After a service is deleted, it cannot be reinstalled.
* By default, the service assumes that NSX-T is installed. For existing vCenter Server instances V4.7 and earlier, if NSX-T is not supported for a service, then NSX-V is used.







 Available services for vCenter Server instances 

The following table shows the services that are available to vCenter Server instances, together with the service versions.



Table 1. Available services for vCenter Server instances

 Service name Current version Notes 

 [Caveonix RiskForesight](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_considerations) 4.1 
 [Entrust CloudControl](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-entrust-cc_considerations) 6.6 NSX-T only 
 [F5 BIG-IP](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-f5_considerations) BIG-IP VE 17.1
"value": "2017-07-20T13:48:31-05:00"
}
],
"virtualGuests":
{
"id": 36189167
}
]
}
]
}
Show more







 Provisioning a transient virtual server with Create Object 

The SoftLayer_Virtual_Guest/createObject API service is the simplest way to provision a transient virtual server.

To provision a transient virtual server by using REST, a POST request would be submitted to [https://softlayer.github.io/reference/services/SoftLayer_Virtual_Guest/createObject/](https://softlayer.github.io/reference/services/SoftLayer_Virtual_Guest/createObject/) with the following JSON in the request body.

The following JSON request body is a generic example.



 JSON Request Body 4 

{
"parameters":[
{
"hostname": "sample-transient-public",
"domain": "softlayer.local",
"datacenter": {
"name": "mex01"
},
"operatingSystemReferenceCode": "CENTOS_LATEST",
"networkComponents":
{
"maxSpeed": 100
}
],
"supplementalCreateObjectOptions": {
"flavorKeyName": "B1_1X2X25"
},
"transientGuestFlag": true
}
]
}
Show more
You can configure vApps and VMs running inside of the virtual data center to use the IBM Cloud private network to access IBM Cloud services. Accessing IBM Cloud services through a private network can save on outbound public networking costs and can provide a higher degree of reliability and security. Virtual data centers route to the IBM Cloud private network through a virtual data center service network that is configured as an available external network on virtual data centers edge.

VMware Shared fully enables access to IaaS endpoints for IBM Cloud Virtual Private Cloud (VPC). For more information, see [Endpoints available for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-service-endpoints-for-vpc).

The following services are available:



Table 2. Available services

 Service IP address (Endpoint) 

 Microsoft Windows Update Server 52.117.132.5 
 Microsoft Key Management Server 52.117.132.4 
 Red Hat Capsule Server 52.117.132.7 
 DNS 161.26.0.10 (rs1.adn.networklayer.com) and 161.26.0.11 (rs2.adn.networklayer.com) 
 Ubuntu and Debian APT Mirrors 161.26.0.6 (mirrors.adn.networklayer.com) 
 RHEL and CentOS YUM repo 161.26.0.6 (mirrors.adn.networklayer.com) 
 NTP 161.26.0.6 (time.adn.networklayer.com) 
 [IBM Cloud Object Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-connecting-vpc-cos) s3.direct.xxx.cloud-object-storage.appdomain.cloud 



Enabling access to the service network is done in two edge configuration steps.



 Adding the NAT rule for VMware Solutions Shared 

Add a NAT rule for translating internal network addresses into the service network IP address space.



1. Log in to the VMware Cloud Director tenant portal.
2. Click the virtual data center Edges tab and open the single preconfigured edge.
3.
Managed interfaces include, for example, gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational information systems includes, for example, restricting external web traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security controls associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers, and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions.
VM to Internet 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/network-flows/flow4.png)





 Internet to VM 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/network-flows/flow5.png)





 VM to Client Campus Network over VPN 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/network-flows/flow6.png)







 Next Steps 

The next step on the deployment journey is:



* [Prepare Your Cloud Account](https://cloud.ibm.com/docs/vmware-classic-journey?topic=vmware-classic-journey-vmware-onboarding-prepare-account)
[vCenter Server with Hybridity Bundle architecture](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/hybrid_architecture.svg)

Figure 1. vCenter Server with Hybridity Bundle high-level architecture



 Physical infrastructure 

This layer provides the physical infrastructure (compute, storage, and network resources) to be used by the virtual infrastructure.





 Virtualization infrastructure (Compute, Storage, and Network) 

This layer virtualizes the physical infrastructure through different VMware products:



* VMware vSphere virtualizes the physical compute resources.
* VMware Virtual SAN (vSAN) provides software-defined shared storage, based on the storage in the physical servers.
* VMware NSX is the network virtualization platform that provides logical networking components and virtual networks.







 Virtualization management 

This layer consists of vCenter Server Appliance with embedded Platform Services Controller (PSC), NSX Manager, two VMware NSX Edge™ Services Gateway (ESGs), three VMware NSX Controllers™, and the IBM CloudDriver virtual server instance (VSI). The CloudDriver VSI was deployed on demand as needed for certain operations such as adding hosts to the environment.

The base offering is deployed with a vCenter Server appliance that is sized to support an environment with up to 400 hosts and up to 4000 VMs. The same vSphere API-compatible tools and scripts can be used to manage the IBM-hosted VMware environment.

In total, the base offering requires 38 vCPU and 67 GB vRAM that are reserved for the virtualization management layer. The remaining host capacity for your VMs depends on several factors, such as oversubscription rate, VM sizing, and workload performance requirements.

For more management resource requirements when you deploy the HCX service, see [HCX overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_considerationshcx_considerations).





 Infrastructure hybridity
Virtual infrastructure design 

The virtual infrastructure layer includes the VMware® software components that virtualize the compute, storage, and network resources provided in the physical infrastructure layer, such as VMware vSphere® ESXi™, VMware NSX-T™, and optionally VMware vSAN™. As with the roll-your-own VMware solution in VPC, you are responsible for configuring the virtual layer based on your needs.

Zoom

![Virtual infrastructure](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vpc-ryo-diagrams-overview-virtual.svg)

Figure 1. Virtual infrastructure



 VMware vSphere design 

The vSphere ESXi configuration consists of the following aspects:



* Boot configuration
* Time synchronization
* Host access
* User access
* DNS configuration



The IBM Cloud® bare metal server for IBM Cloud VPC with ESXi includes a default configuration, for example, hostname, DNS, and NTP. With the IBM Cloud bare metal servers boot configuration ([user data](https://cloud.ibm.com/vpc?topic=vpc-user-data)), you can settle these configurations based on your preference. This design uses IBM Cloud DNS service, and the IP addresses are configured automatically. Also, time synchronization uses IBM Cloud NTP, which is automatically set. Although Secure Shell (SSH) and ESXi Shell are useful for provisioning and using various automation tools, they must be disabled after provisioning as a best practice.

With this design, you can manage the ESXi hosts through vSphere Web Client. The first thing to be done after the initial provisioning of your first IBM Cloud bare metal server for IBM Cloud VPC with ESXi is to deploy vCenter® Server.

Then, your vCenter Server is deployed and initially configured for the data center and cluster settings.
Configuring your network to use the customer-managed NSX ESG with your VMs 

Configure the network for your virtual machines (VMs) so you can take advantage of the VMware NSX Edge™ Services Gateway (ESG) that is deployed in your VMware vCenter Server® instances. For more information about the security measures that are in place to help minimize security risk, see [Does the management services NSX Edge pose a security risk?](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutionsfaq-mgmt-nsx)

VMware NSX® is a network virtualization platform that allows the virtualization of isolated networks and provides several networking services such as switches, routing, and firewalls. For more information about NSX, see [Overview of NSX for vSphere](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.3/com.vmware.nsx.install.doc/GUID-10944155-28FF-46AA-AF56-7357E2F20AF4.html).

As part of the ordering process for your vCenter Server instance, the following actions are completed on your behalf:



* A private customer subnet is ordered to be used by your VMs to access the IBM Cloud® infrastructure private network.
* A public customer subnet is ordered to allow your VMs to access the internet.
* NSX is deployed and configured in your vCenter Server instance.
* A sample NSX Logical Switch is deployed to be used by the customer workload VMs.
* A sample router is deployed for potential east-west communication between local workloads that are connected to layer 2 (L2) networks. This router is a NSX-T™ Tier 1 Router for NSX-T and an NSX Distributed Logical Router for NSX-V.
* An NSX Edge appliance is deployed and configured to perform network address translation (NAT).
The IBM Cloud infrastructure credentials are stored in the IBM Cloud for VMware Solutions console after the first order. Future orders automatically use the stored credentials.





 How are my VMware virtual platform consumptions billed? 

All costs for the physical and virtual infrastructure and the licenses that result from the instance are charged to your IBM Cloud account. When you order an instance, you must have an IBM Cloud account and provide the SoftLayer API key that is associated with the account.





 What is the difference between vCenter Server and VMware vSphere? 

All instance types provide deployment choices for VMware® virtual environments. However, the difference is the extent of customizability and automation.



* When you order a VMware vCenter Server® instance, you deploy a VMware® virtual environment with customized compute, storage, and network resources. For more information about the deployed components, see [Technical specifications for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverviewvc_vcenterserveroverview-specs).
* When you order a VMware vSphere® instance, you obtain the maximum of flexibility to design and build your hosted VMware environment while you incorporate VMware-compatible hardware. However, IBM Cloud does not automate the installation, configuration, and bring-up of the optional VMware components for the VMware vSphere instance.
* The functions that are supported by vCenter Server instances and VMware vSphere instances are different. For more information, see [Offering comparison chart](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-inst_comp_chart).







 What is included in a vCenter Server instance? 

For more information, see [Technical specifications for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverviewvc_vcenterserveroverview-specs).





 What is included in a VMware vSphere instance?
Release notes for Citrix Netscaler VPX 

You can see the latest updates and functionality enhancements for your Citrix Netscaler VPX and IBM Cloud here.



  13 November 2019 

Virtual servers with multiple IP addresses
:   You can now create a single load balancing virtual server with multiple non-consecutive/consecutive VIP IPv4 and IPv6 addresses. Each VIP address bound to a virtual server is treated as an individual virtual server.

For more information about this feature, see the Citrix article [Multiple IP virtual servers](https://docs.citrix.com/en-us/netscaler/12-1/load-balancing/load-balancing-customizing/multi-ip-virtual-servers.html).





  25 September 2018 

SSL
:   The following updates have been applied for SSL connections:



*  Removal of weak ciphers from the DEFAULT_BACKEND cipher group.
*  Support for ECDHE ciphers on the front end of Thales nShield® external HSM
*  Support for ECDHE ciphers on the front end of SafeNet network external HSM
*  Removal of SSLv2: The NetScaler VPX appliance does not support SSLv2 from release 12.1.





  23 January 2018 

Service group support for GSLB
:   You can now configure IP address-based service groups, domain-name-based service groups, or domain-name-based autoscale service groups for GSLB. You can also manage a group of services as easily as a single service, and bind a service group to a virtual server, as well as add services to the group.
:   For more information about GSLB service groups, see the Citrix article [Configuring a GSLB service group](https://docs.citrix.com/en-us/netscaler/12/global-server-load-balancing/configure/configuring-a-gslb-service-group.html).
* Private network: provides complete control of the secured networking traffic without performance degradation if significant public network traffic occurs at the same time; the private network has three functional areas:



* Host to and from Host: network traffic in the private VLANs assigned to you. Bandwidth is free and unmetered.
* Host to and from Backend Services: network traffic to and from the private VLAN to OS update servers, NTP, DNS resolvers, network storage and more. Bandwidth is free and unmetered.
* VPN and direct connections to and from VLAN: network traffic to and from an existing internal network over direct connection or VPN that uses a distinct stand-alone network to the secure private VLAN. Bandwidth is free and unmetered.
* Data center to Data center interconnectivity: provides secure connectivity between hosts across IBM Cloud data center locations. Bandwidth is free and unmetered.



* Management network: provides Out-Of-Band Management (OOBM) accessible through VPN (for example the built-in SSL VPN for administration) or direct connection (for example IBM Cloud Direct Link). Network management allows Remote Console access through the IPMI network interface for Bare Metals hosts on the private network. Bandwidth is free and unmetered.



This network-within-a-network topology design provides maximum accessibility, security, and control for your IT infrastructure. The topology provides the ease of a public network with the security of a private network by keeping systems accessible to administrators and safely off-limits to external users.



 Networking VLANs 

The Virtual LAN (VLAN) assigned to you on the Classic Infrastructure network, provides an enterprise-grade private network with full isolation and security. Each VLAN is either public or private, and each VLAN is assigned to a specific data center for a specific IBM Cloud Account.

The following information is a summary of [Getting started with VLANs on Classic Infrastructure](https://cloud.ibm.com/docs/vlans?topic=vlans-getting-started) and [About VLANs on Classic Infrastructure](https://cloud.ibm.com/docs/vlans?topic=vlans-about-vlans).