VMware Cloud Director 10.2.2

Good news, VMware Cloud Director 10.2.2 has been released introducing several new features.

VMware Cloud Director version 10.2.2 includes the following:

  • Tanzu Kubernetes Cluster Tenant Network Isolation – Tanzu Kubernetes clusters are now only reachable from workloads within the same organization virtual data center in which a cluster is created.
  • Tanzu Kubernetes Cluster Pod and Services CIDR selection – During the creation of a Tanzu Kubernetes cluster, you can specify ranges of IP addresses for Kubernetes services and Kubernetes pods.
  • VMware Cloud Director uses its management network for communication with Tanzu Kubernetes Clusters – The VMware Cloud Director management network is a private network that serves the cloud infrastructure and provides access for client systems to perform administrative tasks on VMware Cloud Director. Earlier releases use the Kubernetes service network. 
  • VMware Cloud Director appliance SNMP agent – You can configure the agent to listen for polling requests. If there is a preexisting Net-SNMP agent, during the upgrade, the VMware Cloud Director appliance replaces the Net-SNMP installation with VMware-SNMP. During VMware-SNMP set-up, the VMware Cloud Director appliance configures dynamically the firewall rules required for SNMP operation.  You must remove any existing firewall rules that work with Net-SNMP before the upgrade.
  • Global Placement Policy – Service providers can define placement policies that work effectively across all vCenter Server instances and clusters in a VMware Cloud Director environment. A single placement policy can point to hosts that span multiple clusters in one or more vCenter Server instances. Boundaries in underlying infrastructure are abstracted away behind the global logical construct of a placement policy making for a more logical experience for both service providers and tenants. This change enables capturing the placement policy when a vApp Template is created from a VM; the resulting vApp Template will inherit any placement policy from the original VM even if the VM and vApp Template are in different Provider VDCs. 
  • Guest Customization for Encrypted VMs – VMware Cloud Director 10.2.2 fully supports guest customization of VMs that run on encrypted storage. 
  • Organization Virtual Data Center Templates – You can create and share virtual data center (VDC) templates with tenant organizations so that organization administrators can use the templates to create VDCs. VMware Cloud Director 10.2.2 supports the use of NSX-T based networking with the organization VDC templates.
  • Storage Policy Update – Service providers can use storage policies in VMware Cloud Director to create a tiered storage offering, for example,  Gold, Silver, and Bronze, or even offer dedicated storage to tenants. With the enhancement of storage policies to support VMware Cloud Director entities, you have the flexibility to control how you use the storage policies. You can have not only tiered storage, but isolated storage for running VMs, containers, edge gateways, and so on.
  • FIPS Support  – This release of VMware Cloud Director includes support for the Federal Information Processing StandardsBoth the VMware Cloud Director appliance and Linux binary can run in FIPS-compliant mode. FIPS mode is disabled by default. Enabling FIPS mode might affect the performance of VMware Cloud Director. If metrics collection is configured, verify the configuration of the server and client communication with Cassandra over SSL.
  • Direct VDC Networks Support in Organization VDCs backed by NSX-T Data Center –  Service providers can create direct organization VDC networks in VDCs backed by NSX-T Data Center.
     
  • Autoscaling – Scaling groups are a new top-level object that tenants can use to implement automated horizontal scale-in and scale-out events on a group of workloads. You can configure autoscale groups with a source vApp template, a load balancer network, and a set of rules for growing or shrinking the group based on CPU and memory use. VMware Cloud Director automatically spins up or shuts down VMs in a scaling group.
  • Guided Tours Update – Service providers can publish custom-built guided tours and scope the tours to system administrators or tenants. Starting with VMware Cloud Director 10.2.2 you can download guided tours from a VMware Github repository or a custom Github repository. 
  • Removing Static T-shirt Size – VMware Cloud Director 10.2.2 no longer supports the use of the predefined virtual machine sizes available since vCloud Director for Service Providers 9.0.  You can use the VM sizing policy functionality to provide predefined VM sizing.

For information about system requirements and installation instructions, see VMware Cloud Director 10.2 Release Notes.

For information on appliance configuration and sizing, see the guidelines in VMware Cloud Provider Pod Designer – VMware Validated Designs for Cloud Providers.

Enjoy!

Cloud and App Virtual Event!

Join VMware executives for a 35-minute live event to learn how to unlock the power of any cloud for a new generation of modern apps. Then dive deeper with labs, Cloud City demos and technical experts to turn your digital business vision into reality.
Latest Vision and Technology Preview: join VMware, top cloud providers, press, analysts, customers and fellow prospects as we launch our unique solution built specifically for multi-cloud

Expert-led technical deep dives into key topics from App Modernisation to Cloud Migration to Cloud Operations

Hands on Labs/Trials

Latest solutions overview demos

Technical resources, architectural guides

Get the answers you need—for your unique scenario ranging from getting started to accelerating even faster the future.



Workload Migration for Cloud Providers- Part 2

Last time we were talking about the most common Migration strategies for Cloud Providers (RepurchasingRehosting and Relocating), and migration types (Hot, Warm and Cold). Take a look here:

https://via.vmw.com/EQjT

Today I would like to focus on migration phases, at VMware professional Services we divided it into four:

Plan

Planning is the most important phase for any migration, it’s critical before starting your migration. We need to understand the type of workloads that are going to be migrated. Type of application, how these workloads interact with each other. 
A proper application discovery and dependencies mapping is a Key. vRealize Network Insight is a great tool for this task, but also understanding applications by having several meetings with applications owners.
I believe this is the most important phase, it’s the foundation. 

Build

It’s time to build the new Cloud environment, based on the planning stage. SDDC should be designed, deploy and configure. Also, we need to take care of future decisions and design accordingly. 
For example, It’s TANZU part of your roadmap?, are you planning to add K8’s as a service?, etc

Migrate

We already plan the migration and deployed the new Cloud Environment, so It’s time to start. HCX is VMware recommended tool. Ideally, the migration will be performed in waves (not more than 100 workloads each). It’s a good practice to start with the test or non-production VM’s. Test results should be part of this stage as well.

Operate

Workloads were already migrated into the new Cloud Environment. As usual, it’s time to start with the daily tasks, such as monitoring, licensing, security, logging, backups, disaster recovery, performance, etc.
VMware vRealize® Suite can help at this stage. 

Next time, I will be writing about Migration tools (HCX, vMotion, Advanced Cross vMotion, SRM, Etc)

Workload Migration for Cloud Providers- Part 1

Cloud migration and cloud operations | Dynatrace

In the last few days I have worked with Cloud Providers looking to migrate their workloads to new environments (Greenfield). That is why I have decided to write about the different options and their benefits..

As we have already discussed in previous posts, there are different migration strategies. But today, I want to focus on what I consider to be the most common ones in Cloud Providers.

The first one is Repurchasing; Moving away from a perpetual license model to a SaaS model (VCPP one in VMware case)


Rehosting is an important strategy, involves a change in the hypervisor. In most of the cases Hyper-V.

Last but not least, Relocating migrating VMs from one virtualized environment to another without requiring changes. Legacy to Greenfield.

Regarding the type of migration, the goal is to migrate as many workloads as possible with the least downtime. So we will try to add the greatest amount of VM’s in Hot or Warm waves.

Hot
Known as live migration. The virtual machine stays powered on during the initial full synchronization and the subsequent delta sync, using the VMware vSphere® vMotion® feature.

Warm
Migration is a virtual machine that is actively running while it is being replicated to ensure minimal downtime.

There is a third option, but it is the one we will try to avoid, although not in all possible cases and it is known as Cold.

Cold
A Cold Migration is a virtual machine that is powered off before starting the migration. It is advisable to divide the migration into phases: Plan, Build, Migrate and Operate.

I will be talking about these 4 phases in my next Post.

EMEA Cloud Briefing Review

The EMEA Cloud Briefing took place last Thursday, it has been a pleasure to be part of it. If you have not been able to connect, here is a brief summary

Andy Christmas, opened the event by reviewing the agenda: After showing the new VMware Cloud Interface for HD events he thanked the participants (more than 400 Service Providers from all over EMEA) and led to Herve Basso, EMEA Director for Cloud Providers.

Herve reviewed what happened over the past year, sharing VMware’s growth in the Service Provider market. Despite the difficult situation we have faced due to the pandemic, VMware has had an excellent year.

Later, it was the turn of Service Providers who shared their experiences working with VMware and how their operations and offerings have grown.

Finally, two Breakout Sessions were held:

Breakout Session 1: Patrick Verhoeven, Eiad Al-Aqqad and I talked about the Cloud Provider Platform evolution

Breakout Session 2: The “Leveraging SaaS Service” was conducted by Ramona Pilotto, Gerrit Lehr and Jerome Klodzinski.

Agenda:

Cloud Providers Briefing – Agenda

If you are a Service Provider looking to grow your business, please join the EMEA Briefing next Thursday 21 at 3:00 PM CET.



I will be presenting the “Cloud Provider Platform Evolution” breakout session with my colleagues Eiad AL-Aqqad and Patrick Verhoeven.

Also, Owen Rogers from 451 Research as a guest speaker during our keynote, following which we’ll break into two specific workstreams to assist in the development of your strategy.

Full agenda:

Register now

See you there!

EMEA Cloud Briefing for Cloud Providers

Im glad to be part of a new Cloud Briefing for cloud Providers on Thursday 21, January 2021. We’ll explain the latest VMware technologies and innovations that empower your own offerings, enabling you to provide flexibility and choice to your customers and yourselves.

We’re delighted to welcome Owen Rogers from 451 Research as a guest speaker during our keynote, following which we’ll break into two specific workstreams to assist in the development of your strategy.

Mark the date now!

Registration: https://via.vmw.com/EPY0

I will share a detailed agenda soon!

vCloud Usage Meter version 4.3 Upgrade

vCloud Usage Meter version 4.3 has been released couple of weeks ago, as version 3.6.x goes End of support on March 2021 it’s a good time to upgrade.

With Usage Meter Version 4.3 partners no longer need to update Usage Meter if program changes happen and also don’t need anymore to perform data retention for compliance purposes, because all usage data is stored in the SaaS service.

Products Support:

  • NSX-T
  • vRealize Network Insight
  • vSphere with Kubernetes
  • SDDC Manager


Download

In- Place Upgrade:

 vCloud Usage Meter 4.3 can be installed as an in-place upgrade on top of vCloud Usage Meter 4.1.x or vCloud Usage Meter 4.2. 

Prerequisites
  • Back up or take a snapshot of the source vCloud Usage Meter appliance that you want to upgrade.
  • You must enable SSH on the source vCloud Usage Meter appliance.
  • You must have a password to log in to the vCloud Usage Meter console as root.
Procedure
  1. Locally on you computer, download the ums-system-upgrade.shar file.
  2. Copy the upgrade ums-system-upgrade.shar file to a folder in the source vCloud Usage Meter console.You can use a SCP software like WinSCP on Windows.
  3. Log in to the source vCloud Usage Meter console as root.
  4. To install the shar file, run the command.
  5. To complete the in-place upgrade, you must reboot the appliance.After rebooting the appliance, the system generates a cloudusagemetering-old folder for the source vCloud Usage Meter installation backup. A newly created cloudusagemetering folder points to the upgraded vCloud Usage Meter installation.
  6. Verify that the vCloud Usage Meter services are up and running.
    1. Enter the /opt/vmware/cloudusagemetering directory.
    2. Verify the status of the vCloud Usage Meter services.
  7. Stop SSH by running the command

Migrate product configuration:

Product configuration data can be migrated from your source vCloud Usage Meter 3.6.x appliance to your vCloud Usage Meter 4.3 appliance.

Prerequisites:

  • Back up or take a snapshot of the source vCloud Usage Meter appliance.
  • You must have the TCP host name or IP address and the usgmtr user password of the source vCloud Usage Meter appliance. 
  • Deploy vCloud Usage Meter 4.3 as a new appliance.

Procedure:

  1. Log in to the source vCloud Usage Meter console as root
  2. Start the SSHD service in the source vCloud Usage Meter appliance by running the following command. service sshd start
  3. Log in to the target vCloud Usage Meter console as usagemeter
  4. Start the SSHD service in the target vCloud Usage Meter appliance by running the following command. su root service sshd start
  5. To migrate the source product configuration data to the target vCloud Usage Meter 4.3 appliance, run the command. migrateum hostname

    Here, hostname is the TCP host name or IP address of the source vCloud Usage Meter appliance from which you are migrating the vCenter Server configuration data. 

    The migrateum command uses SSH and Secure copy protocol to export the database and keystore files from the source system and copy it to vCloud Usage Meter 4.3.

    Confirm that you want to migrate vCloud Usage Meter data. 
    You must enter the usgmtr password of the source vCloud Usage Meter appliance and confirm that you want to proceed with the data migration. 
  6. In the source vCloud Usage Meter console, stop the sshd service by running the following command. service sshd stop
  7. In the target vCloud Usage Meter console, disable the sshd service by running the following command.
Results

The login credentials for the vCloud Usage Meter 4.3 Web interface are the usagemeter ones, that you set during the deployment of vCloud Usage Meter 4.3.

Important:

You can run the migrateum command only once. 

To ensure that vCloud Usage Meter 4.3 is working correctly, run the new appliance in parallel with the source appliance for at least one full reporting cycle.

The vRealize Operations Manager product configuration data is not migrated from the source vCloud Usage Meter appliance to the target vCloud Usage Meter 4.3 appliance. If a vRealize Operations Manager server is associated with a vCenter Server instance that you added for metering in the source vCloud Usage Meter appliance, after you migrate the product confirguration data, vCloud Usage Meter 4.3 automatically detects the vRealize Operations Manager server.

To start metering the product consumption data of the migrated vRealize Automation instance, in the vCloud Usage Meter Web interface, you must manually update the vRealize Automation instance details and accept the server certificate.

See you next year, enjoy your Holidays

VMware Cloud Availability 4.1

VMware Cloud Availability brings a number of key improvements .

NSX-T integration

Increased options for geographic coverage and public API coverage is improved with guides and examples of more capabilities and now exposed to the customer

Email notification

Improved Controls with eMail notification to tenants, controllable by providers as well as available for providers (in addition to syslog and VCD events), new backup and restore controls and a new Initial config single pane of glass installation wizard as well as UI enhancements.

Other improvements

Improved Offerings are available in terms of addressing security concerns with Cloud to Cloud replication encryption of data at rest! Multi-site authentication improves user experience and now providers can control via SLA policy whether customer have access to migration or DRaaS or both.


CloudFlix Webinar series

CloudFlix Webinar series enable you to capture business opportunities in a Multi-Cloud World. During these webinars, you will gain information and context to better understand the rapidly evolving Cloud Services market and how VMware can help you be successful in delivering compelling new services to your end customers. 

 December 1st – 10:00am CET: Usage Meter 4.3 What´s New: We will present new feature and capabilities of Usage Meter 4.3 and what´s needed for Usage Meter 4.3.
 
 December 8th – 10:00am CET: What´s new in VCD10.2: We will present new features and capabilities of VMware Cloud Director 10.2 like but not limited to NSX-T integration, vSphere with Tanzu and CSE3.0.
 
 December 15th – 10:00am CET: VMware Cloud on AWS with Cloud Director Service: ‘We will present possible ways to build a Multi-Tenant VMware Cloud on AWs environment leveraging Cloud Director Service. Furthermore, we will present capabilities and limitations of Cloud Director Service.

Register HERE: https://via.vmw.com/EOdu