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

In second post of this series we looked at the components which are needed to form a VCAV solution stack and we saw cassandra is an integral part of this solution.

To know about cassandra in detail, you can refer an old blogpost written by me.

If you are not following along 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

4: Install Cloud Proxy for vCD

In this post we will deploy a Cassandra Cluster. Before installing cassandra software we need to meet following requirements:

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

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

I have disabled SELinux and firewall service in my lab. 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 last post of this series we discussed about logical architecture of VCAV and we discussed about the various components involved which makes the VCAV stack.

In this post we will be deploying VCAV appliance. Current version of VCAV is 2.0.1 and it can be downloaded from here. vCloud Availability appliance deployment is straight forward 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 location where VCAV ova file is stored on your system.

vcavd-1

Review the ova details and hit next to continue.

vcavd-2

Accept EULA and hit Next.

vcavd-3

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

vcavd-4

Select the cluster where vm will be deployed and hit Next.

vcavd-5

For prod deployment, thick provisioned disk is recommended. For lab deployment thin provisioned disk works just fine.

vcavd-6

Select appropriate portgroup to which VCAV vm will connect and hit Next.Read More

vCloud Availability for vCloud Director-Part-2-Architecture & Components

In first post of this series we discussed about what is vCloud Availability solution and what problem are we solving by using this product. In this post we will discuss about the architecture of VCAV and what are the components needed to create a full-fledged DRaaS solution using VCAV.

vCloud Availability Logical Architecture

Basically the architecture relies solely on service provider environment. There can be a slight differences in components that different service provider uses. Typical components can include what is visible in below diagram.

Components shown in gray color are the components which tenant and service provider have already deployed in their side. Colored components are the one which we will be deploying later in this series.

vCloud Availability Components

Below table taken fro m VMware docs explains high level overview of components needed for setting up a VCAV environment.

vcav-components-2

And that’s it for this post.

In the upcoming posts of this series, we will deploy these components one by one.Read More

vCloud Availability for vCloud Director-Part-1-Introduction

What is vCloud Availability for vCloud Director (VCAV) ?

vCloud Availability for vCloud Director is a Disaster Recovery-as-a-Service (DRaaS) solution that provides simple and secure asynchronous replication and failover for vSphere managed workloads.

VMware released vCloud Availability for vCloud Director keeping in mind to provide cloud innovations to vCloud Air Network partners so that they can implement this software solution to provide Disaster Recovery as a Service (DRaaS) to customers.

Customer’s who are using vCloud Air, knows that vCloud Air uses vSphere Replication to provide the DRaaS service to their customers. This is a very similar solution which vCAN partners will now be using for DRaaS. 

Since vCloud Air is not present in all regions,  vCloud Availability will be a blessing for vSphere customers because they can now buy and use DRaaS service from a local partner.

In last 3-4 years there is a shift in technology as more and more customer are now adopting to cloud solutions.Read More

Learning NSX-T-Part 10: Logical Routing

In last post of this series we created logical switches and established communication between the App and Web VM which were on same subnet and connected to same logical switch. In this post we will learn about logical routing.

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

1: Introduction to NSX-T

2: NSX-T Architecture

3: NSX Manager Deployment

4: NSX Controllers Automated Deployment

5: NSX Controllers Manual Deployment

6: Prepare Esxi host to form NSX-T Fabric

7: Configuring Uplink Profile

8: Configuring Transport Zone and Transport Nodes

9: Creating Logical Switches and Testing Connectivity

Optimal routing is one of the biggest challenges in any datacenter and NSX revolutionized the way how networking was used in infrastructure. 

NSX-v offered distributed routing to SDDC and because of this routing between different subnets on a Esxi hypervisor can be done in kernel and traffic never has to leave the hypervisor and thus eliminating the traffic hairpinning problems.Read More

Learning NSX-T-Part 9:Creating Logical Switches and Testing Connectivity

In last post of this series we configured transport zones and transport nodes. We discussed about the modes of transport zone and also touch based on N-VDS. In this post we will learn how to create logical switches in NSX-T and we will test connectivity between vm’s attached to same logical switch.

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

1: Introduction to NSX-T

2: NSX-T Architecture

3: NSX Manager Deployment

4: NSX Controllers Automated Deployment

5: NSX Controllers Manual Deployment

6: Prepare Esxi host to form NSX-T Fabric

7: Configuring Uplink Profile

8: Configuring Transport Zone and Transport Nodes

Logical switch provides layer 2 connectivity for the virtual machines that are attached to the it. In last post we discussed that transport zones are of two types (Overlay and VLAN) and the type of logical switch is based on to which type of transport zone it connects to. Read More

Learning NSX-T-Part 8:Configuring Transport Zone and Transport Nodes

In last post of this series we discussed about Uplink profiles. In this post we will learning about transport zones and its types.

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

1: Introduction to NSX-T

2: NSX-T Architecture

3: NSX Manager Deployment

4: NSX Controllers Automated Deployment

5: NSX Controllers Manual Deployment

6: Prepare Esxi host to form NSX-T Fabric

7: Configuring Uplink Profile

What is transport zone in NSX-T?

As per vmware documentation

A transport zone is a container that defines the potential reach of transport nodes. Transport nodes are hypervisor hosts and NSX Edges that will participate in an NSX-T overlay.

What is meant by above is that if two or more Esxi hosts that are configured as transport nodes participate in the same transport zone, then VMs on these different hosts using the overlay network can communicate with each other.Read More

Learning NSX-T-Part 7:Configuring Uplink Profile

In last post of this series we prepared the Esxi host for NSX-T and we ensured that host connection to NSX manager was up and all necessary vib’s have been pushed on hosts. In this post we will learn about uplink profile.

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

1: Introduction to NSX-T

2: NSX-T Architecture

3: NSX Manager Deployment

4: NSX Controllers Automated Deployment

5: NSX Controllers Manual Deployment

6: Prepare Esxi host to form NSX-T Fabric

What is Uplink profile in NSX-T?

From VMware documentation:

An uplink profile defines policies for the links from hypervisor hosts to NSX-T logical switches or from NSX Edge nodes to top-of-rack switches.

Confused? All right lets simplify it a bit.

Uplink profile is pretty much similar to specifying the teaming policy when you enable VXLAN on Esxi host in NSX-v.… Read More

Learning NSX-T-Part 6: Host Preparation and forming NSX-T Fabric

In last 2 post of this series, we discussed the automated and manual deployment of NSX controllers and how to form controller cluster. In this post we will learn how to do host preparation for NSX-T.

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

1: Introduction to NSX-T

2: NSX-T Architecture

3: NSX Manager Deployment

4: NSX Controllers Automated Deployment

5: NSX Controllers Manual Deployment

When we do host preparation, NSX-T pushes few vibs on the Esxi host (just like NSX-v) and once the hosts are prepared they are known as fabric nodes. All Esxi host that are fabric nodes have NSX-T modules installed and are registered with the NSX-T management plane.

Before jumping into host preparation task, ensure that  install-upgrade service status on NSX-T manager is reporting as running. If this service is down, NSX manager won’t be able to push the vibs onto the ESXi hosts when we add them in the fabric.Read More