vSpecialist Labs: Roadmap

Part Two – Roadmap

In the hardware post for the vSpecialist Labs, we listed the hardware we have to play with to construct the Lab. Now is the challenge of what to do with it. Here is a scratch list of the projects we will be running in the Labs over the coming months.

Status: Testing (T), Research (R), Proof-of-Concept (POC), Evaluation (E).

Infrastructure / vSphere:

- ghettoVCB VM backups (T)

- ESXi Hardening using host profiles (T)

- Cisco UCS Platform Emulator v2.0 deployment and configuration (T) (E)

- vCenter Orchestrator appliance (T)

- Integrating vCenter Orchestrator appliance with Cisco UCS platform emulator (T) (E)

- vCenter Operations (E)

vCloud Director:

- Multi-site vCloud Director configuration with v1.5 (R) (POC)

- vCloud Director appliance (T)

- Multi-site PvDCs per Organisation (R)

- vCloud Connector 1.5 within an Organisation as an endpoint (T)

Site Recovery Manager 5

- SRM within a vCD Organisation as an endpoint (T)

- vSphere Replication (T)

VMware View 5

- View deployment with Cisco UCS (T) (POC)

Over time, we will link to these roadmap items with posts and more information. Please also see the vSpecialist Labs Overview page for lab configuration information.

vCenter Orchestrator Silent Install

Article by Michael Poore (@mpoore)

Is it possible to install vCO on a Windows server silently? Yes.

If you have the EXE file (DVDDrive:\vCenter-Server\vCO\vCenterOrchestrator.exe) available on the server then installing is as simple as:

D:\vCenter-Server\vCO>vCenterOrchestrator.exe -i silent

It takes a few seconds to complete but at the end of it the vCO Configuration service is present and running:

Of course that’s just installing vCO, it’s not configured – that’s still to be done (see my earlier article on configuring vCO).

So, what’s the point of doing such an install then? Where’s the benefit? If you look at vCO’s Configuration Maximums it’s not entirely obvious is it?

Item Maximum
Connected vCenter Server systems 10
Connected ESX/ESXi servers 300
Connected virtual machines spread over vCenter Server systems 15000
Concurrent running workflows 150

You’d need a very large environment to *need* more than one vCO server let alone to need a method of automatically deploying them. Either that or a very particular use case.

Install vCenter Orchestrator on a Dedicated Server

Article by Michael Poore (@mpoore)

The binaries for vCenter Orchestrator (vCO) come bundled alongside vCenter Server and are installed by default when vCenter is installed. But what if, and it’s probably a better practice, you want to install vCO on a separate server to vCenter. How’s that done?

Before running through that, first let’s cover requirements. vCO server components must be installed on a 64-bit Windows OS. The client component can happily sit on 32-bit. The minimum recommended RAM is 4GB but in a lab or non-production environment you can get away with less depending on if the database is co-located or not. [Read more...]

Configuring vCenter Orchestrator

Article by Michael Poore (@mpoore)

vCenter Orchestrator (vCO) is a no charge extra for vCenter Server owners. In fact the binaries are installed alongside vCenter Server itself.

This post covers what you need to configure vCO and start to use it. It’s based on the GA release of vCenter 5.0. (Of course I should point out that other orchestration products are available.) [Read more...]