vCloud Availability for Cloud-to-Cloud DR-Part 2: POC Deployment

As discussed in the last post, we can configure all roles present in vCAV-C2C in a single appliance for Lab/POC deployment. In my lab, I am starting with a small deployment to have a general understanding of this product before doing a distributed deployment.

In my lab, I have 2 sites, and each site is configured with the following components:

  1. vSphere/vCenter Server 6.5 U2
  2. vCloud Director 9.0
  3. VMware NSX 6.3.6

vSphere and vCD are fully configured, and Org/Org vDCs are in place at both sites with external networks, etc., configured.

Let’s start the deployment with Site-A.

Deployment of the VCAV-C2C appliance is straightforward, and the steps are shown below.

Once appliance deployment is complete and it boots up, it will give you information on how to connect to the appliance for further configuration.

Configure vCloud Availability Replicator

To configure the vCloud Availability Replicator role, connect to https://VCAV-FQDN:8043 and click on the link under Additional Resources

Login with root credentials set during deployment.Read More

vCloud Availability for Cloud-to-Cloud DR-Part 1:Introduction

VMware vCloud Availability for Cloud-to-Cloud DR is the most recent addition to the VMware Cloud Provider Platform portfolio. It was originally introduced in May 2018, and it delighted service providers who have long desired a VMware native cloud-to-cloud DR solution for vCloud Director-based clouds.

What is vCloud Availability for Cloud-to-Cloud DR (vCAV-C2C)?

VMware vCloud Availability for Cloud-to-Cloud is a solution for disaster recovery between two instances of vCloud Director. The concept of cloud-to-cloud DR is not new; however, VMware did not have any solutions for vCloud-based clouds. vCAV-C2C bridges this gap and enables VMware Cloud Providers to use their current vCloud Director installations to deliver disaster recovery services, such as replication and failover capabilities for workloads at both the VM and vApp levels.

The following are the main capabilities of the vCAV-C2C solution:

1: Replicate and recover vApps/VMs between two vCD instances for migration, DR, and planned migration use cases.

2: A unified HTML5 portal that tenants can use for managing replication, migration, and failover for vApps and VMs.Read More

vCloud Availability for vCloud Director: Part 10: Integrating VCAV With Deployed Components

Now we have deployed all components needed to form the VCAV stack. It’s time to integrate all of them with VCAV. Let’s start.

At this point of time, I am assuming that you have already declared the following variables as per your environment

Read More

vCloud Availability for vCloud Director: Part 9-Create vCloud Availability Portal Host

In the last post of this series, we deployed the VRCS and VR appliances. In this post, we will deploy the VCAV Portal.

If you are not following along with this series, then I recommend reading earlier posts of this series from links below:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

4: Install Cloud Proxy for vCD

5: Deploy Cassandra Cluster

6: RabbitMQ Cluster Deployment and vCD Integration

7: Deploy VRMS Appliance

8: Deploy vRCS and VR Server

What is vCloud Availability Portal?

The vCloud Availability Portal provides a graphic user interface for the management of vCloud Availability operations. The vCloud Availability Portal back end scales horizontally, and we can deploy more than one portal host for HA and load balancing.

VCAV portal host size varies from small to medium to large, depending on the number of concurrent sessions that the portal host will be handling.Read More

vCloud Availability for vCloud Director: Part 8-Deploy vSphere Replication Cloud Service & vSphere Replication Server

In the last post of this series, we deployed the VRMS appliance. In this post, we will deploy the vSphere Replication Cloud Service and the vSphere Replication Server appliance.

If you are not following along this series, then I recommend reading earlier posts of this series from the links below:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

4: Install Cloud Proxy for vCD

5: Deploy Cassandra Cluster

6: RabbitMQ Cluster Deployment and vCD Integration

7: Deploy VRMS Appliance

Before we kick off the deployment, let’s recap the role of appliances in the VCAV stack.

What is vSphere Replication Cloud Service (VRCS)?

The vSphere Replication Cloud Service is a tenant-aware replication manager that provides the required API for managing the service and all its components. vSphere Replication Cloud Service registers as a vCloud Director extension and is accessible through the vCloud Director interface.

What is vSphere Replication Server?Read More

vCloud Availability for vCloud Director: Part 7-Deploy vSphere Replication Manager

In the last post of this series, we deployed RabbitMQ and integrated it with vCD.

In this post, we will deploy and configure vSphere Replication Manager (VRMS). Before deploying VRMS, let’s discuss what the role of VRMS is in a VCAV stack.

If you are not following along with this series, then I recommend reading earlier posts of this series from the links below:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

4: Install Cloud Proxy for vCD

5: Deploy Cassandra Cluster

6: RabbitMQ Cluster Deployment and vCD Integration

vSphere Replication Manager manages and monitors the replication process from tenant VMs to the cloud provider environment. A vSphere Replication management service runs for each vCenter Server and tracks changes to VMs and infrastructure related to replication.

VRMS, when deployed, is integrated with the resource vCenter Server, which is registered to vCloud Director, and made available to tenants.Read More

vCloud Availability for vCloud Director: Part 6: Install and Configure RabbitMQ Cluster

In the last post of this series, we deployed a Cassandra node and configured ssl security for Cassandra. In this post, we will be installing RabbitMQ for vCD.

If you are not following along this series, then I recommend reading earlier posts of this series from the links below:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

4: Install Cloud Proxy for vCD

5: Deploy Cassandra Cluster

What is RabbitMQ (RMQ)?

RabbitMQ is an open source message-queuing software that helps facilitate message exchange between two or more applications. The exchange of messages is done via a queue, defined by the administrator. An application can publish a message to the queue, which can be retrieved or consumed by a different application.

A message can include any kind of information, for example, it could have information about a process/task that should start on another application may be on another server, or it could be just a simple text message.Read More

vCloud Availability for vCloud Director: Part 5: Deploy and Configure Cassandra Cluster

In the second post of this series, we discussed the components needed to form a VCAV solution stack, and we saw that Cassandra is an integral part of this solution. In this post, we will learn how to deploy a Cassandra Cluster.

If you are not following along with this series, then I recommend reading earlier posts of this series from the links below:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

4: Install Cloud Proxy for vCD

 Before installing Cassandra software, we need to meet the following requirements:

1: Verify that routing, NTP, forward, and reverse DNS resolutions are working correctly.

2: Make sure that SELinux and your firewall are disabled. If they are enabled, then open appropriate ports in the firewall.

I have disabled SELinux and the firewall service in my lab.

3: Install Python: Make sure Python 2.7 is installed in your CentOS 7 system.Read More

vCloud Availability for vCloud Director: Part 4: Installing Cloud Proxy for vCD

In the last post of this series, we deployed the VCAV appliance and discussed that it will be configured later once we are done with the deployment of all the other needed components.

In this post, we will add a vCloud proxy cell to an existing vCloud Director environment.

If you are not following along with this series, then I recommend reading earlier posts of this series from below links:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

What is a Cloud Proxy?

As per VMware documentation:

The Cloud Proxy is a standalone, optional component of vCloud Director that can act as a generic Transmission Control Protocol (TCP) connection proxy. It supports forwarding incoming TCP connections and listening incoming connections.

The Cloud Proxy creates virtual connections for data to travel from the on-premise to the service provider (cloud) site and reverse.

For installing Cloud Proxy, you should have your vCD environment already deployed and fully configured.Read More

vCloud Availability for vCloud Director: Part 3-VCAV Deployment

In the last post of this series, we discussed the logical architecture of VCAV and the components that constitute the VCAV stack.

In this post, we will be deploying the VCAV appliance. The current version of VCAV is 2.0.1, and it can be downloaded from here. vCloud Availability appliance deployment is a straightforward task and is pretty much like any other standard OVA deployment.

Connect to your management vCenter Web Client and choose to Deploy OVF Template and browse to the location where the VCAV OVA file is stored on your system.

Review the OVA details and hit next to continue.

Accept the EULA and hit Next.

Provide a name for the VCAV VM and select the data center where it will be deployed.

Select the cluster where the VM will be deployed and click Next.

For prod deployment, a thick-provisioned disk is recommended. For lab deployment, a thin-provisioned disk works fine.Read More