vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Viewing a private network endpoint for a virtual data center 

You can view the details of a private network endpoint for a virtual data center.



 Procedure to view a private network endpoint for a virtual data center 



1. From the IBM Cloud® for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2. In the VMware Shared table, expand the site and click a virtual data center name.
3. View the Private network endpoint details. Expand Allow listed IPs and subnets to view the list of IP addresses and subnets that you added when you ordered the private network endpoint.





Table 1. Private network endpoint items

 Item Description 

 Device type The multitenant or dedicated device and size. 
 Service network IP The IP address for the service network. 
 Private network IP The IP address for the private network. 
 Service address The IP address that your virtual data center is allocated for IBM Cloud access. 
 Allow listed IPs and subnets The list of all allow listed IP addresses and subnets for the virtual data center. 



The Service address is available only when you select the Dedicated 1 Gbps uplinks or Dedicated 10 Gbps uplinksDevice type when you order the private network endpoint.

The private network endpoint can have different statuses.



Table 2. Status descriptions for a private network endpoint

 Status Description 

 Creating The private network endpoint is being created. 
 Ready to use The private network endpoint is operating. 
 Modifying The allow listed IPs and subnets are being modified. 
 Deleting The private network endpoint is being deleted. 
 Deleted The private network endpoint is deleted. 







 Related links 



* [Operating VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guide)
* [VMware Shared pricing](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_pricing)
These instructions help you locate and copy the IBM Cloud infrastructure username and API key from the IBM Cloud infrastructure customer portal. 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 day two of operation, it is your responsibility to monitor and manage the vCenter and NSX-T, including backups, patching, configuration, and monitoring of the VMware software and the underlying vSphere hypervisor.





 Key benefits 

The architecture provides fundamental building blocks, which include VMware vSphere, vCenter Server, VMware NSX-T, and shared storage options, such as VMware vSAN or IBM Cloud VPC file share. These building blocks are needed to flexibly design a VMware software-defined data center solution that best fits your workloads.

VMware Solutions in IBM Cloud VPC have the following key benefits over IBM Cloud classic deployments:



* IBM Cloud VPC gives you the ability to easily and rapidly define and control a virtual network, which is logically isolated from all other tenants. The logical isolation is implemented by using virtual network functions and security that is built into the platform.
* Provisioning the IBM Cloud bare metal server on IBM Cloud VPC takes minutes instead of hours when compared to the IBM Cloud bare metal server on IBM Cloud classic.
* VMware workloads by running in IBM Cloud VPC can take advantage of all original functions for VPC networking capabilities and other IBM Cloud interconnectivity services.



With this single-tenant IBM Cloud bare metal server infrastructure that is provided in IBM Cloud VPC, you can quickly deploy network, compute, and storage capacity for your VMware environment to the IBM Cloud in minutes.

Unlike the managed service offerings, this architecture gives you flexibility to design a solution for your needs, and provides you full and complete access to all components.





 Related links 



* [IBM Cloud VPC getting started](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [IBM Cloud VPC Bare Metal Servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers)
* [IBM Cloud VPC RYO VMware reference architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-arch-overview)
Deleting services from vCenter Server instances 

You can delete the services that were provisioned for your VMware vCenter Server® instances when you no longer need these services.



 Before you delete services from vCenter Server instances 



* Deleting services from vCenter Server instances with VMware vSphere® 6.5 is not supported.
* You are billed until the end of the IBM Cloud® infrastructure billing cycle for the deleted services.







 Procedure to delete services from vCenter Server instances 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance for which you want to delete services.
3. Click the Services tab.
4. On the Services page, locate the service instance that you want to delete, click the vertical overflow menu next to the Status column, and then click Delete service.
5. In the Remove service window, review the considerations or warnings if there are any and select I Understand. Click Delete.







 Results after you delete services from vCenter Server instances 

After your request to delete a service is accepted, the service status is changed to Removing.

When the service deletion is completed successfully, you are notified by email, and the service is deleted from the Services page of the instance.

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





 Manually removing the DNS entries for specific services 

For specific services, if you installed the service in a VMware Solutions release earlier than V4.0 and you delete that service, you must manually remove the DNS entries.

After you delete the service, unused DNS entries remain in Active Directory™. These entries do not cause any problems. However, in the future, they might create conflicts with reverse lookups. It is recommended that you remove the entries as soon as possible.

The following table shows the services that are affected. The table also shows the pattern for hostnames for various service offerings. The actual hostname might differ from the pattern in various ways.
KMIP for VMware overview 

This solution architecture describes the KMIP™ on VMware architecture for protecting your VMware® instances. Many storage encryption options are available to protect your VMware workload. KMIP for VMware works together with VMware native vSphere encryption and vSAN™ encryption. The vSphere and vSAN encryption provides simplified storage encryption management together with the security and flexibility of IBM Cloud® Key Protect or IBM Cloud Hyper Protect Crypto Services customer-managed keys.

This solution is considered to be an extra component and extension of the vCenter Server offering on IBM Cloud. As a result, this document doesn't cover the existing configuration of these foundation solutions on IBM Cloud. To understand more about the foundation solution architecture, see [Overview of VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_overview).



  Key benefits 

While many storage encryption solutions are available for your VMware workload, KMIP for VMware offers the following benefits:



*  Integration with VMware vSAN encryption and vSphere encryption, both of which are implemented in the hypervisor layer rather than the storage or virtual machine layer. This approach allows easy management and transparency to your storage solution and application.
*  Fully managed key management server available in many IBM Cloud multizone regions (MZRs).
*  Integrating your VMware cluster with IBM Cloud Key Protect or IBM Cloud Hyper Protect Crypto Services provides you with fully customer-managed keys that you can revoke at any time.







  Related links 



*  [Solution design](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip-design)
*  [Implementation and management](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip-implementation)
*  [High availability and disaster recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip-hadr)
* Use of common protocols and format such as Web Services, HTTP, JMS, REST, OSLC, XML, JSON, XML and .csv files, DB tables
* Support of Create, Replace, Update, Delete and Query operation
* Support for customizing integration processing using Processing Rules and Scripting



For the MS-Manage Application:



* Maximo integration message generation and delivery based on application object events
* Support for implementation (batch) data loading
* Pre-defined (75+) interface components provided along with applications to configure new interfaces
* Support for customizing integration processing using Processing Rules and Scripting



For file based integrations, an IBM Cloud Object Storage location will be allocated for each order. 5 API Keys will be generated for the client to use to move files in and out of the location. Additional keys can be ordered. To initiate this process, customers must submit a support case.

One Site-to-Site VPN is included in the order. To initiate the creation of this VPN, customers must submit a support case. At this time, the VPN is only available for LDAP integrations.

For clients wanting to use App Connect or File integration for other applications within the suite:



* AppConnect is included as an entitlement with the Maximo Application Suite, but the Dedicated Service does not implement or support this within the MAS-Dedicated environment. The client is responsible for implementing AppConnect or beginning with version MAS v8.7, AppConnect SaaS will be supported.
* For clients wanting file integrations with applications other than Manage, this needs to be discussed with the Sales team and an appropriate solution implemented. COS is only included for the Manage application in the Dedicated Service.







 MAS-Dedicated Bundles 

The following table shows the distribution of workload across worker nodes. This is based on the T-Shirt sizes on the [Maximo Application Suite Dedicated T-Shirt Calculator v6](https://ibm.box.com/shared/static/aydqzy5in7coc0995vfcctyhg55ic4ar.xlsm) and will be the setup based on the selected size of the sites.
Asia-Pacific TOK02 02 
 Asia-Pacific TOK04 01 
 Asia-Pacific TOK05 01 







 Networking type 

Select either Public and private network or Private network only.







 Related links 



* [Network interface](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-network-interface-settings)
* [Procedure to order vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure)
<br><br> * Provide infrastructure and administration access<br> * Limit the number of infrastructure administration entry points to ensure security audit<br><br><br> Management VPC service Create a separate VPC service for management and maintenance of workload resources and access through a site-to-site VPN 
 <br><br> * Provide infrastructure for service management components like backup, monitoring, IT service management, shared storage<br> * Ensure you can reach all IBM Cloud and on-premises services<br><br><br> Workload VPC service Create a separate VPC service as an isolated environment to support hosted applications 
 Create virtual server instances to support management Management virtual server instances Create a VPC virtual server instance that can be used for management and maintenance of your hosted application. Configure ACL and security group rules to allow access to IBM Cloud services, and workload and management VPCs. 
 Create virtual server instances to support hosted applications Workload virtual server instances Create a VPC virtual server instance that can act as a workload server to support hosted applications. Configure ACL and security group rules to allow access to IBM Cloud services, workload and management VPCs. 
 <br><br> * Demonstrate compliance with control requirements of the IBM Cloud Framework for Financial Services<br> * Set up network for all created services<br> * Isolate network for all created services<br> * Ensure all created services are interconnected<br><br><br> Secure landing zone components Create a minimum set of required components for a secure landing zone Create a modified set of required components for a secure landing zone in preset 







 Network security architecture decisions 



Table 2. Network security architecture decisions

 Requirement Component Reasons for choice Alternative choice 

 <br><br> * Isolate management VPC and allow only a limited number of network connections<br> * All other connections from or to management VPC are forbidden<br><br><br> ACL and security group rules in management VPC Isolate environment for access through site-to-site VPN<br><br><br><br> * All ports to other VPCs are open<br><br><br> More ports might be opened in preset or added manually after deployment
IBM Cloud VPN overview 

IBM Cloud® Virtual Private Network (VPN) for VPC service offers two types of VPNs:



* Site-to-site gateways - This VPN type connects your on-premises network to the IBM Cloud VPC network.
* Client-to-site servers - This VPN type allows clients on the internet to connect to VPN servers, while still maintaining secure connectivity.



IBM Cloud VPN Gateway for VPC provides a simple yet powerful solution for highly scalable and robust site-to-site VPN gateways. With this service, you can create site-to-site VPN tunnels for secure, encrypted connectivity. Also, you connect from on-premises sites to IBM Cloud through a VPN gateway on an IBM Cloud VPC, and a peer gateway on-premises. For more information, see [About site-to-site VPN gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn).

IBM Cloud Client VPN for VPC provides an open source compatible client-to-site VPN solution that allows users to connect to IBM Cloud resources through secure, encrypted connections. Whether you want to connect to access or manage your workloads that are running in VPC Virtual Servers or VMware® workloads, you can use the OpenVPN-based client-to-site VPN solution for remote access. For more information, see [About client-to-site VPN servers](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview).



 Considerations with roll-your-own VMware solution in VPC 

When you use the VMware virtual machines (VMs) on VPC subnets architecture, your VMs are attached to VPC subnets and the routing behaves in the same way as with VPC Virtual Servers. The VPC subnets are provisioned from the zone prefix, and the routing works between the VPC without any required changes. You can use both IBM Cloud VPN Gateway for VPC and IBM Cloud Client VPN for VPC with this solution as described in the documentation previously listed.

Zoom

!
Networking services 

You automatically get connected to the Virtual Private Network (VPN) for VPC when your IBM Cloud account is set up. By default, your server has a public IP address and a private IP address. If you want your server to be private, you can either turn off the public interface after your server is provisioned or order your server as private. For more information, see [Getting started with Virtual Private Networking](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-started) for more information.

Check out the following tables for a summary of networking options.



 VPC infrastructure 

Within the infrastructure layer, you can build a virtual private cloud, which is a virtual network that is tied to your IBM Cloud account.



Table 1. Networking options - VPC

 Option Description 

 [Getting started with IBM Cloud® Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started) Provides cloud security and the ability to dynamically scale your virtual server instances. 
 [Load balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers) Distributes traffic among multiple server instances within the same region of your VPC. 
 [VPN for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn) Securely connect your VPC to another private network. You can use VPN to set up an IPsec site-to-site tunnel between your VPC and your on-premises private network or another VPC. 
 [DNS Services](https://cloud.ibm.com/docs/dns-svcs/getting-started) Provides private DNS to Virtual Private Cloud (VPC) users. 
 [Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started) Interconnect IBM Cloud Classic and Virtual Private Cloud (VPC) infrastructures worldwide, keeping traffic within the IBM Cloud network.
Running a query 

Watch the following video to learn more about Data Engine and how you can get started to run a basic query.

In SQL, the term query is just another way of saying SELECT statement. To run a query:



1. In the SQL editor field of the Data Engine UI, enter a SELECT statement.



* After the FROM keyword, specify one or more [unique resource identifiers](https://cloud.ibm.com/docs/sql-query?topic=sql-query-runningunique) (URIs). Each URI can be thought of as a table. It specifies one or more input objects; each input object can be thought of as a table partition. You must have at least 'Reader' access to the buckets that contain the input objects.
* If the format of the input objects is CSV, and no special options are required, it is not necessary to specify a STORED AS clause. However, if the format is JSON, ORC, Parquet, or AVRO, after the FROM clause, specify STORED AS JSON, STORED AS ORC, STORED AS PARQUET, or STORED AS AVRO.
* If text formats, such as JSON and CSV, are compressed with either gzip or bzip2 and have the extensions .gz and .bz, they automatically get recognized as compressed files. However, do not use these kinds of compressed files due to performance reasons.
* If the format of the input objects is CSV and a delimiter other than the default , (comma) is used, you must specify the delimiter by using the FIELDS TERMINATED BY option of the [STORED AS](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referenceexternalTableSpec) clause. All single Unicode characters are allowed as delimiters.
* By default, it is assumed that CSV input objects have a header line that specifies the names of the input columns.
* Run the query.
* Observe the results when it is complete in the Result tab.
* Now lets do some investigation by modifying this basic query.



2. In the Data Engine UI, edit the SQL in the text area to look more like this, keep the FROM statement as is.

-- What are the top 10 web pages on NASA from July 1995?
-- Which mission might be significant?
SELECT REQUEST, COUNT(REQUEST)
FROM cos://<REGION>/<BUCKET-NAME>/log-stream-landing/topic=webserver/jobid=<JOBID> STORED AS PARQUET
WHERE REQUEST LIKE '%.htm%'
GROUP BY REQUEST
ORDER BY 2 DESC
LIMIT 10
3. Update the FROM clause with your Object SQL URL and click Run.
4. Click on the latest Completed job to see the result under the Result tab.
5. Select the Details tab to view additional information such as the location where the result was stored on Object Storage.
6. Try the following question and answer pairs by adding them individually to the Type SQL here ... text area.

-- Who are the top 5 viewers?
SELECT HOST, COUNT()
FROM cos://<REGION>/<BUCKET-NAME>/log-stream-landing/topic=webserver/jobid=<JOBID> STORED AS PARQUET
GROUP BY HOST
ORDER BY 2 DESC
LIMIT 5

-- Which viewer has suspicious activity based on application failures?
SELECT HOST, COUNT()
FROM cos://<REGION>/<BUCKET-NAME>/log-stream-landing/topic=webserver/jobid=<JOBID> STORED AS PARQUET
WHERE responseCode == 500
GROUP BY HOST
ORDER BY 2 DESC

-- Which requests showed a page not found error to the user?
SELECT DISTINCT REQUEST
FROM cos://<REGION>/<BUCKET-NAME>/log-stream-landing/topic=webserver/jobid=<JOBID> STORED AS PARQUET
WHERE responseCode == 404

-- What are the top 10 largest files?
Each select expression must be in one of the following forms:

select
<viewname>.<colname> as <alias> 
<viewname>.* 
<expr> as <alias> 
case
when <predfunction1()> then <expr1>
when <predfunction2()> then <expr2>...
when <predfunctionn()>
then <exprn>
[else <expr_default>]
as <name>





 Description 



* <viewname>.<colname> as <alias>



* <viewname>

Specifies the view from which to select columns.
* <colname>

Specifies the column in that view.
* <alias>

Specifies the name by which the selected field is known. This field is an optional field. It is selected to be a part of each output tuple. If <alias> is not specified, the name of the column is by default the <colname>. Can be a simple identifier or a double-quoted identifier.



* <viewname>.

Specifies the name of a view. This syntax indicates that all columns of the specified view must be carried forward to the enclosing select or extract statement.

Like SQL, AQL allows the shorthand select * statement. The effect of this statement is to select all columns from all inputs that are specified in the from clause of the select statement. However, the shorthand extract * statement is not supported.
* <expr> as <alias>

Represents the assignment of an expression to an attribute of the encompassing view.



* <expr>

Specifies an expression that is composed of scalar function calls, aggregate function calls, or a constant.
* <name>

Represents the name of the column that holds the result of the expression that is specified by <expr> as <alias>. If <alias> is not specified, the name of the column is by default the <name>. Can be a simple identifier or a double-quoted identifier.