VMware Cloud Director 10.1 now available!

VMware Cloud Director™ 10.1 is now Available, with a few core updates in this release.

So, what’s new?

  • App Launchpad
  • Container Service Extension (CSE) 2.6
  • Object Storage Extension (OSE) 1.5
  • Terraform VMware Cloud Director Provider 2.7
  • Tenant App 2.4
  • NSX-T Migration Tool
  • NSX-T Enhancements
  • Encryption as a service

Highlights:

  • NSX-T migration tool script is part of Cloud Director, as NSX-T features are getting parity with NSX-V
  • Network downtime is minimized using bridged networks during migration.
  • vSphere Encryption from VMware Cloud Director. Encryption requires certificate keys that require a key management server (KMS) and Cloud Providers can choose from partners such as Fortanix or Dell Cloudlink.
  • New monitoring and metering capability with closer integration with NSX data collection, more network metrics and sizing profile-based metering.
  • K8 Kubernetes Clusters or PKS Kubernetes Clusters for VMware Cloud Director.
  • App Launchpad is a free component for VMware Cloud Director

Multitenant Use of VMware vRealize Operations as a Service

Service Providers Use cases:

  • Shared multitenant environment with tenant and service provider access 
  • Dedicated environment with tenant access 
  • Shared and/or dedicated environment with no tenant access

Shared Multitenant Environment with Tenant and Service Provider Access 

In this scenario, the service provider operates a centralized vRealize Operations Manager instance to collect all data generated by the resource cluster. Both service provider personnel and tenants will access the same instance of vRealize Operations, and data access will be controlled with RBAC. This scenario allows for easy management and deployment. This approach is especially attractive for service providers who can operate their complete environment within one vRealize Operations Manager environment.

Advantages include the following: 
• Easy to deploy and manage
• No additional data/configuration distribution for dashboards, policies, and so on is needed
• Only one instance to maintain (software updates, management packs, and so on) 

Disadvantages involve the following: 
• Role-based access control requires careful maintenance 
• Objects can only be operated under one policy, removing the ability to limit alert visibility for a customer/tenant
• Sizing can become complex and larger environments could be limited by sizing parameters. A possible workaround is to build instances per larger resource group.

Dedicated Environment with Tenant Access 

This scenario is unrelated to the vRealize Operations Manager multitenant use case that this document is focused on. This scenario is included for comparison reasons. In this scenario, the service provider operates a vRealize Operations Manager instance per dedicated customer. This is usually done when the customer operates its own cluster and vCenter Server within the service provider environment. Access to this environment is primarily focused on the tenant, but might be open for the service provider as well. An extended scenario might be that the service provider also collects data from the customer operated vCenter Server. This approach is commonly used in managed service environments or dedicated public cloud offerings where the customer rents a dedicated hardware stack. 

The advantages are as follows: 
• Easy to deploy and manage 
• Sizing is easy because it can be done per tenant/customer 
• Object policies can be customized to be tenant specific 

Disadvantages include the following: 
• Difficult to get a “big picture” when each customer operates on its own 
• Currently no data federation available for vRealize Operations 
• Service provider must monitor a high number of instances 
• Maintenance (upgrades and so on) requires more resources

Shared and/or Dedicated Environment with No Tenant Access 

In this scenario, the service provider operates a centralized vRealize Operations Manager instance to collect all data generated by the resource cluster. The primary difference from the, Shared Multitenant Environment with Tenant and Service Provider Access is that access is only provided for the service provider. This scenario allows for easy management and deployment. This approach is often used in managed services environments where the service provider focuses on resource optimization. 

The following advantages apply: 
• Easy to deploy and manage 
• No additional data/configuration distribution for dashboards, policies, and so on necessary 
• Only one instance to maintain (software updates, management packs and so on) 
• No complex RBAC necessary 

Disadvantages include the following: 

• Sizing can become complex and larger environments might be limited by sizing parameters. A possible workaround is to build instances per larger resource group.
• No customer/tenant access to vRealize Operations Manager possible.

Becoming a Service Provider? VMware Cloud Provider POD

Are you looking to easily deploy your full Cloud Provider stack?, accelerates the time to value?, reduces the scope for errors?, and lowers operational expenses?

Cloud Provider Pod automates deployment of the full Cloud Provider stack and can be easily extended to provide custom provisioning needs

This image has an empty alt attribute; its file name is screenshot-2020-03-11-at-15.36.24.png

Components

Cloud Provider Pod can deploy the following VMware products in adherence with VMware Validated Designs for Cloud Providers, accompanied by customized documentation with guidance on design and operations.vSphere

• vSphere
• vSAN
• NSX
• vCloud Director
• vCloud Director Extender
• vRealize Orchestrator
• vRealize Operations
• vRealize Log Insight
• vRealize Network Insight
• Usage Meter

Detailed Deployment and Operations Guidelines

Cloud Provider Pod generates custom documentation based on cloud
design inputs that help the Cloud Provider deploy an interoperable and
validated stack.

Certified Interoperability and Scale per VMware Validated Design

Cloud Provider Pod-generated documentation bears adherence to the
latest VMware Validated Designs and is additionally scale-tested for Cloud
Provider environments.

Multi-tenant, open, extensible Cloud

Deploys a multi-tenant, self-service Cloud environment that is open (REST
APIs, CLI and Py SDK), extensible (UI-extensible, compliant with Ansible
and Terraform), and has native integration with ecosystem partners (Data
Protection from EMC Avamar).

What are the use cases for Cloud Provider Pod?

VMware Cloud Provider Pod facilitates the deployment of a software-defined
cloud provider environment that can be used to deliver a multitude of turnkey
services, such as:
• Managed Private Cloud
• Multi-tenant Cloud
• Disaster Recovery-as-a-Service
• Backup and Availability Services
• Security and Compliance Services
• Cloud Management Services
• Cloud Migration Services
• Cloud Operations and Monitoring Services

For more information, please visit:
https://www.vmware.com/cloud-solutions.html

It’s time to upgrade: vSphere 6.0 Reaches End Of General Support (EOGS) Today!!

2020-03-12T23:59:00

  days

  hours  minutes  seconds

until

This includes the following releases:

  • vCenter Server 6.0
  • vCenter Update Manager 6.0
  • ESXi 6.0
  • Site Recovery Manager 6.0 and 6.1
  • vSAN 6.0, 6.1 and 6.2
  • vSphere Data Protection 6.0 and 6.1
  • vSphere Replication 6.0 and 6.1

Learn more about VMware’s Lifecycle Support dates at vmware.com/go/lifecycle.

VMware vSphere 7: Saying hello to modern applications

No doubts, vSphere 7 is the most significant innovation since ESXi, twenty years ago. Nowadays, it is all about modern applications; customers are looking to design, deploy and maintain all apps at the same place. 

vSphere 7 allows deploying Applications using any combination of virtual machines, containers, and Kubernetes.

The new generation of vSphere is available in two editions:

  • vSphere 7
  • vSphere 7 with Kubernetes (Available on VMware Cloud Foundation)

What is VMware Cloud Foundation Services?

VMware Cloud Foundation Services is a new, integrated Kubernetes and RESTful API surface that enables you to drive API access to all core services. VMware Cloud Foundation Services consists of two families of services—Tanzu Runtime Services and Hybrid Infrastructure Services.

  • Tanzu Runtime Services deliver core Kubernetes development services, including an up-to-date distribution of Tanzu Kubernetes Grid.
  • Hybrid Infrastructure Services include full Kubernetes and RESTful API access that spans creating and manipulating virtual machines, containers, storage, networking, and other core capabilities.
new-vmw-vmware-cloud-foundation-services-overview-diagram-965x545