vania-janet/multiturn-rag-retrieval-data huggingface dataset:
VMware SDDC on IBM Cloud 

The VMware SDDC on IBM Cloud® solution provides a configured VMware Software Defined Data Center (SDDC) that is built to a standardized format and architecture. This solution provides a private cloud that can be quickly scaled up (or down) and allows existing VMware virtualized data center clients to extend or move their workloads into the IBM Cloud. This scaling allows companies to address such issues as rapid capacity expansion (or contraction), migration of workloads to the cloud, establishing cloud-based backup and disaster scenarios, and the ability to set up development, test, training, or lab capacity. More servers can be added quickly to meet increased capacity of over 10,000 sized virtual guest servers per region.

This SDDC configuration includes a software-defined networking solution that is based on VMware NSX providing unlimited networking flexibility in defining new VLANs, assigning IP addresses, and establishing network services such as load balancing, firewalls, and routers.

Shared storage is included based on VMware Virtual Storage Area Networking (VSAN) software defined storage. VSAN provides highly available, high performance, single tenant storage that grows automatically as more capacity nodes are added.

The VMware SDDC on IBM Cloud – Advanced reference architecture is the first partner architecture to be certified under the VMware Validated Design program.

For more information about VMware SDDC on IBM Cloud, see [VMware SDDC on IBM Cloud](https://www.ibm.com/cloud/learn/software-defined-data-center), [NSX](https://www.vmware.com/products/nsx), and [VSAN](https://www.vmware.com/products/virtual-san).

Add additional security and compliance to your workloads with a [trusted secure cloud solution with IBM, VMware, and HyTrust](http://wpc.c320.edgecastcdn.net/00C320/DeploymentGuide_IBM_Intel_HyTrust_VMware_v1%200.pdf).
* For VMware Shared, the support date for the [V1 API](https://cloud.ibm.com/apidocs/vmware-solutions-shared/vmware-solutions-shared-v1.0.0) is being extended until 31 December 2022. To ensure smooth transition in the future, start using the [V2 API](https://cloud.ibm.com/apidocs/vmware-solutions-shared/vmware-solutions-shared-v2.0.0).
* For [VMware Solutions API](https://cloud.ibm.com/apidocs/vmware-solutions), support is provided for Caveonix RiskForesight, Veeam, Zerto, and VMware HCX stand-alone licenses. Also, support for the 2U chassis types is added by using the new large_chassis_only parameter.



User interface enhancements
: The left navigation pane on the VMware Solutions console now groups items as Resources and Licenses so that they are more aligned with the resource types and names.





 29 August 2022 

HKG02 and SEO01 data centers no longer available
: (Updated on 20 September 2022) The Hong Kong 02 and Seoul 01 IBM Cloud data centers are no longer available for deployment.

Price calculation updates for IBM Cloud for VMware Solutions Shared
: Price calculations are now automatically generated when you access the order pages for IBM Cloud for VMware Solutions Shared offerings. For more information about the specific default selections, see Requirements and planning for VMware Solutions Shared.

vRealize Operations Tenant App for VMware Cloud Director availability
: You can now access the vRealize Operations Tenant App for a VMware Cloud Director for new and existing organizations through the VMware Cloud Director tenant portal. For more information, see Enabling VMware Chargeback.

Standard - Catalog storage policy availability
: The Standard - Catalog storage policy is now available for storing vApp templates and media files in your VMware Cloud Director catalog. For more information, see VMware Solutions Shared overview.

Private network endpoints for multizone virtual data centers
* Enables scaling for compute for batch and other inventory workloads that run infrequently.
* Use IBM® Event Streams for IBM Cloud® to manage streaming data from IoT devices.







 Step 2: Ensure global availability 



* Built-in HA tools in IBM Cloud Kubernetes Service balance the workload within each geographic region, including self-healing and load balancing.
* Load-balancing, firewalls, and DNS are handled by IBM Cloud Internet Services.
* Using the toolchains and Helm deployment tools, the apps are also deployed to clusters across the globe, so workloads and data meet regional requirements.







 Step 3: Share data 



* IBM Cloud® Object Storage plus IBM® Event Streams for IBM Cloud® provides real-time and historically data storage.
* APIs allow the customers of the shipping company to share data into their apps.







 Step 4: Deliver continuously 



* IBM Cloud® Continuous Delivery helps Developers to quickly provision an integrated toolchain, by using customizable, shareable templates with tools from IBM, third parties, and open source. Automate builds and tests, controlling quality with analytics.
* After Developers build and test the apps in their Development and Test clusters, they use the IBM CI/CD toolchains to deploy apps into clusters across the globe.
* IBM Cloud Kubernetes Service provides easy rollout and roll-back of apps; tailored apps are deployed to meet regional requirements through the intelligent routing and load balancing of Istio.









 Results 



* With IBM Cloud Kubernetes Service and IBM CI/CD tools, regional versions of apps are hosted near to the physical devices that they gather data from.
* Microservices greatly reduce time to delivery for patches, bug fixes, and new features. Initial development is fast, and updates are frequent.
* Shipping customers have real-time access to shipments’ locations, delivery schedules, and even approved port records.
* Transit partners at various shipping terminals are aware of manifests and shipment details so that onsite logistics are improved, instead of delayed.









 Airline delivers innovative Human Resources (HR) benefits site in under 3 weeks 

An HR Exec (CHRO) needs a new HR benefits site with an innovative chatbot, but current Development tools and platform mean long lead times for apps to go live.
Choosing a deployment solution 

Discovery is available both as a service that is hosted by IBM Cloud and as a service that you install on IBM Cloud Pak for Data. Learn about these deployment solutions and how they differ.

The product user interface and APIs are mostly equivalent regardless of whether you use the managed or installed version of the service. The few differences between the two solutions include:



* How you deploy and set up the service
* The underlying technology that is used to crawl data sources
* Limits for things like the maximum number of documents and enrichments or file sizes
* Who to contact for support and how you share product feedback



Although the documentation that describes how to use the product is the same (what you're reading now), more documentation about how to install and administer the service in IBM Cloud Pak for Data is available from the [IBM Cloud Pak for Data product documentation](https://www.ibm.com/docs/cloud-paks/cp-data) that is hosted in IBM Documentation.

To keep up with product changes, check the following topics periodically:



IBM Cloud Pak for Data

[Release notes for IBM Cloud Pak for Data service instances](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-release-notes-data)
IBM Cloud

[Release notes for IBM Cloud service instances](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-release-notes)





 Comparing features 

The following table describes the feature support differences between the two deployment types.

The features that are listed in the IBM Cloud column apply to service instances that are deployed from IBM Cloud Pak for Data as a Service also.



Feature support details
This table has row and column headers. The row headers identify features. The column headers identify the different deployment types of the product. To understand which features are supported by a deployment type, go to the row that describes the feature, and then find the column for the deployment type that you are interested in.

 Feature IBM Cloud IBM Cloud Pak for Data 

 Crawl the local file system, Window file system, databases, LDAP directories, FileNet P8, and HCL Notes !
Video - IBM Cloud Direct Link for hybrid cloud 

IBM Cloud® Direct Link offerings provide connectivity from an external source into a customer's IBM Cloud private network. Direct Link can be viewed as an alternative to a traditional site-to-site VPN solution, designed for customers that need more consistent, higher-throughput connectivity between a remote network and their IBM Cloud environments.
High availability and disaster recovery for VMware Solutions 

Learn about high availability and disaster recovery for IBM Cloud® for VMware® Solutions.

Review the following sections for more information:



*  [Disaster recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-understand-responsibunderstand-responsib-disaster-recovery)
*  [Client responsibilities for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_compl_infovc_compl_info-client-responsibilities)
*  [High availability and disaster recovery for KMIP](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip-hadr)
*  [High availability and disaster recovery for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_datashared_data-ha-dr)
Active Directory Domain Services introduction 

IBM Cloud® for VMware Solutions is a deployment service that delivers the automated deployment of a VMware Software Defined Data Center (SDDC), along with optional third-party products, and with IBM Cloud bare metal servers and network. After deployment, the systems are managed by the customer, who is responsible for ongoing software patches and updates. The customer has full access to the systems. For more information, see [Customer versus IBM responsibility for vCenter Server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_compl_infovc_compl_info-responsibility). To enable the deployment lifecycle (additions, removals), IBM Cloud for VMware Solutions retains user IDs with administrator privileges to deploy and configure the SDDC software.

Active Directory™ (AD) is a foundation of the IT infrastructure for many large enterprises. This document covers best practices for integrating Active Directory Domain Services architecture in IBM Cloud for VMware Solutions. For the design of Active Directory Domain Services, see [Active Directory Domain Service](https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/active-directory-domain-services). AD serves as a distributed hierarchical data storage for information about corporate IT infrastructure; devices and users, user credentials, and access privileges based on group membership. It also includes the Domain Name System (DNS) zones and records.



 Terms used 

The following terms are used:



* IBM Cloud for VMware Solutions infrastructure domain - This domain is configured as part of the automation process when your VMware vCenter Server® instance is initially deployed. It is used for the user credentials and service accounts of your system administrators and the computer objects for the underlay-connected infrastructure components only. This document describes the components and configuration of this domain and how it can be incorporated in your AD design.
* IBM Cloud for VMware Solutions workload domain - This term is used for the domain that needs to be designed and implemented by you after the deployment of the vCenter Server instance.
IBM Cloud services and third-party integrations 

You can use IBM Cloud® platform and infrastructure services, and other third-party integrations to add extra capabilities to your cluster.



 IBM Cloud services 

Review the following information to see how IBM Cloud platform and infrastructure services are integrated with IBM Cloud Kubernetes Service and how you can use them in your cluster.



 IBM Cloud platform services 

All IBM Cloud platform services that support service keys can be integrated by using IBM Cloud Kubernetes Service [service binding](https://cloud.ibm.com/docs/containers?topic=containers-service-binding).

Service binding is a quick way to create service credentials for an IBM Cloud service and store these credentials in a Kubernetes secret in your cluster. The Kubernetes secret is automatically encrypted in etcd to protect your data. Your apps can use the credentials in the secret to access your IBM Cloud service instance.

Services that don't support service keys usually provide an API that you can directly use in your app.

To find an overview of popular IBM Cloud services, see [Popular integrations](https://cloud.ibm.com/docs/containers?topic=containers-supported_integrationspopular_services).





 IBM Cloud classic infrastructure services 

Because IBM Cloud Kubernetes Service lets you create a cluster on IBM Cloud classic infrastructure, some classic infrastructure services, such as Virtual Servers, Bare Metal Servers, or VLANs are fully integrated into IBM Cloud Kubernetes Service. You create and work with these service instances by using the IBM Cloud Kubernetes Service API, CLI, or console.

Supported persistent storage solutions, such as IBM Cloud File Storage for Classic, IBM Cloud Block Storage, or IBM Cloud® Object Storage are integrated as Kubernetes flex drivers and can be set up by using [Helm charts](https://cloud.ibm.com/docs/containers?topic=containers-helm). The Helm chart automatically sets up Kubernetes storage classes, the storage provider, and the storage driver in your cluster. You can use the storage classes to provision persistent storage by using persistent volume claims (PVCs).
Operations management introduction 

The following reference architecture guides and constrains the instantiations of IBM Cloud® for VMware Solutions architectures.

It also provides the following items.



* Provides a common language for the various stakeholders.
* Provides consistency of technology implementation to solve problems.
* Supports the validation of solutions against proven reference architecture.
* Encourages adherence to common standards, specifications, and patterns.



The primary objective of this reference architecture is to document the Operations Management capability to provide monitoring and alerting of the IBM Cloud for VMware Solutions environment that is deployed for the client. The tools are configured with best practice parameters and thresholds for use by the client’s operations team.

The design allows the client to complete the following tasks:



* Scale up or down as needed.
* Install their own enterprise monitoring tools as mandated by their operational policies.
* Integrate the tools into their own enterprise IT Service Management (ITSM) platform.





 Operations management 

IBM Cloud for VMware Solutions is based on the following architectural layers:

Zoom

![Architecture diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/opsmgmt-architecture.svg)

Figure 1. Architectural layers



* Physical Layer - The lowest layer of the architecture is the physical layer, which consists of the compute, network, and storage components used from IBM Cloud:



* IBM Cloud bare metal servers that run the management, edge, and compute workloads.
* IBM Cloud network that consist of VLANs, subnets, Frontend, and Backend Customer Routers (FCR/BCR).
* vSAN storage, which is a consolidated datastore from the SSDs in the IBM Cloud bare metal servers or Endurance storage.



* Virtual Infrastructure Layer - The virtual infrastructure layer runs on top of the physical layer components. The virtual infrastructure layer controls the access to the underlying physical infrastructure, and controls and allocates resources to the management and compute workloads.
Post-deployment considerations for your VMware instance 

IBM Cloud® for VMware Solutions offerings are not managed services. You are responsible for the configuration, security, management, and monitoring of all software components. With complete administrative access to the solution, you have great power and flexibility that requires significant technical, administrative, and operational expertise across various domains. Managing a VMware® instance in the IBM Cloud requires the same planning and expertise as planning for an on-premises instance. Software-defined technologies such as VMware NSX® and VMware vSAN™ greatly simplify some aspects of instance management, but might require new skills and tools to be properly managed and operated. Combining the power, speed, and reliability of IBM Cloud automated VMware deployment with the appropriate operational planning and testing ensures quick and successful navigation to hybrid cloud.

Review the following considerations to understand your responsibilities for managing and operating the instance before and after it is deployed.



 IBM Cloud account access 

To manage access to your IBM Cloud account, permit other members of your team to access your instance in the IBM Cloud for VMware Solutions console. For more information, see [Inviting users to access services and resources](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-useraccountuseraccount-iamuserinv).





 Limitations 

Familiarize yourself with the following limitations for your instance:



* [Impacts of changing vCenter artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impact)
* [Networking considerations and limitations](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_networkingonvcenterserver)
* [Frequently asked questions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)







 Network design and connectivity 

Complete the following steps to manage access to your IBM Cloud network and to your VMware management components and to plan your IBM Cloud network topology.
[Getting Started with IBM Cloud for VMware Solutions Shared](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-solutions-shared-getting-started)Getting Started with IBM Cloud for VMware Solutions Shared

On IBM Cloud there are a number of deployment offerings for VMware that you can choose from, with each providing a different level of abstraction. VMware Cloud Director (VCD) is offered under the banner of IBM Cloud for VMware Solutions Shared. It is a multi-tenant service with elasticity and two subscription types:

VMware Solutions Schematics



* 2 hours
* 2023-05-05



[Scale workloads in shared and dedicated VPC environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-scaling-dedicated-compute)Scale workloads in shared and dedicated VPC environments

Isolate workloads by provisioning a dedicated host, attaching an encrypted data volume to a VSI, expanding the attached data volume, and resizing the VSI after the fact.

Virtual Private Cloud (VPC) Databases For PostgreSQL

+2

Schematics,Object Storage



* 2 hours
* 2023-05-05



[Use a VPC/VPN gateway for secure and private on-premises access to cloud resources](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-site2site-vpn)Use a VPC/VPN gateway for secure and private on-premises access to cloud resources

This tutorial provides the automation to create resources that demonstrate Virtual Private Network (VPN) connectivity between on-premises servers and cloud resources like IBM Cloud® Virtual Private Cloud Virtual Service Instances (VSIs) and IBM Cloud data services. DNS resolution to cloud resources is also configured. The popular strongSwan VPN Gateway is used to represent the on-premises VPN gateway.

Schematics Virtual Private Cloud (VPC)

+3

Object Storage,Databases For PostgreSQL,DNS Services



* 2 hours
[IBM Cloud for VMware Solutions and Red Hat OpenShift](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/openshift-sddc.svg)

Figure 1. IBM Cloud for VMware Solutions and OpenShift



 Application modernization on IBM Cloud 

Application modernization is a term that describes the process of transitioning existing applications to use new approaches on the cloud. Customers today are seeking innovative, efficient approaches that help them make this transition based on business and application complexity.

Business pressures demand faster time to market. Your existing estate includes not only applications, but data, processes, business logic, and user interfaces, all of which need to adapt to keep up with new business demands.

Application modernization has the following benefits:



* Improved developer productivity
* Increased operational efficiency
* Reduced cost to build new capabilities
* Expanded capacity delivered in a short time



IBM understands that 70% of private cloud adoption is driven by the need to modernize application environments. However, most organizations are approaching application modernization in a staged approach, which requires a hybrid and multi cloud landscape, where:



* Complex and monolithic legacy applications that typically run on mainframes or UNIX systems remain on-premises.
* x86 environments used for Systems of Record (SoR), applications that are security sensitive, and regulated workloads are placed on a virtualized infrastructure or a private cloud.
* Applications such as SAP® or high-performance computing use bare metal resources.
* Security sensitive and some regulated workloads, which can move to the public cloud are moving to dedicated environments.
* Systems of engagement (SoE) such as web, mobile, IoT, AI, or Video are moving to public clouds.



For example, a common pattern is to have front-end SOE applications that are deployed as containers with databases and legacy middleware that are deployed on VMs on a private cloud.

Because your IT infrastructure and business needs are unique, you need an approach to modernization that helps accelerate business value delivery, reduces your risks, and preserves your existing investments.
Understanding IBM Cloud Kubernetes Service 

Learn more about [IBM Cloud® Kubernetes Service](https://www.ibm.com/cloud/kubernetes-service), its capabilities, and the options that are available to you to customize the cluster to your needs.

Review frequently asked questions and key technologies that IBM Cloud Kubernetes Service uses.



 What is IBM Cloud Kubernetes Service and how does it work? 

IBM Cloud Kubernetes Service is a managed offering to create your own Kubernetes cluster of compute hosts to deploy and manage containerized apps on IBM Cloud. As a certified Kubernetes provider, IBM Cloud Kubernetes Service provides intelligent scheduling, self-healing, horizontal scaling, service discovery and load balancing, automated rollouts and rollbacks, and secret and configuration management for your apps. Combined with an intuitive user experience, built-in security and isolation, and advanced tools to secure, manage, and monitor your cluster workloads, you can rapidly deliver highly available and secure containerized apps in the public cloud.





 What is Kubernetes? 

Kubernetes is an open source platform for managing containerized workloads and services across multiple hosts, and offers management tools for deploying, automating, monitoring, and scaling containerized apps with minimal to no manual intervention.

Zoom

![Kubernetes certification badge](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/certified-kubernetes-color.svg)

Figure 1. This badge indicates Kubernetes certification for IBM Cloud Container Service.

The open source project, Kubernetes, combines running a containerized infrastructure with production workloads, open source contributions, and Docker container management tools. The Kubernetes infrastructure provides an isolated and secure app platform for managing containers that is portable, extensible, and self-healing in case of a failover. For more information, see [What is Kubernetes?](https://www.ibm.com/topics/kubernetes).