WoodITWork.com

VMware has announced its latest update to version 5.5 of its global virtualisation powerhouse, vCloud Suite.

To read the updates for all the suite components, see my post: What’s New in vCloud Suite 5.5: Introduction

vCloud Networking and Security has been updated with two networking enhancements, LACP and flow based marking & filtering.

Link Aggregation Control Protocol (LACP) is used to bond your physical network uplinks together to increase bandwidth, have better load balancing and improve link level redundancy. vSphere5.1 supported a simplified version of LACP with support for only a single Link Aggregation Group (LAG) per host and not much choice of load balancing algorithms.

LACP in 5.5 gives you over 22 load balancing algorithms and you are now able to create 32 LAGs per host so you can bond together all those physical Nics.

Flow based marking and filtering provides granular traffic marking and filtering capabilities from a simple UI integrated with VDS UI. You can provide stateless filtering to secure or control VM or Hypervisor traffic. Any traffic that requires specific QoS treatment on physical networks can now be granularly marked with COS and DSCP marking at the vNIC or Port group level.

Manageability has been enhanced in the vSphere Web Client with an object-policy based model.

Firewall Rule management has been made easier. You can now reuse vCenter objects in firewall rule creation and there is an option to create VM vNIC level rules with full visibility into the virtual network traffic via Flow Monitoring.

Upgrades

To upgrade vShield, you must first upgrade vShield Manager and then upgrade the other components in this order:

1. vShield Manager
2. vCenter Server
3. Other vShield components managed by vShield Manager
4. ESXi hosts

You can upgrade just vShield to 5.5 if you want and still run vCenter Server 5.1 and ESXi 5.0/5.1 hosts.

VMware has announced its latest update to version 5.5 of its global virtualisation powerhouse, vCloud Suite.

To read the updates for all the suite components, see my post: What’s New in vCloud Suite 5.5: Introduction

vCloud Director 5.5 has been updated with changes to the Content Catalog, vApp provisioning and lifecycle management process, an improved OVF import/export function and new browser support including Mac OS.

vCloud Director Virtual Appliance

The vCloud Director Virtual Appliance is still only to be used for PoC and Eval use for simple deployment and setup. With the appliance you can choose to use an internal/embedded database or an external MS SQL or Oracle database. Hopefully the appliance is extended in the future to be the default deployment solution in some highly available way or maybe even merged with vCenter.

vCD is still a standalone web client, not integrated as an extension to the vSphere Web Client. There are contextual shortcuts to help you navigate between the two. I don’t actually think that vCD in the future will become an extension to the vSphere Web Client but the admin functionalities of vCenter and vCloud Director will merge into a single appliance but this is just speculation.

Read more…

VMware has announced its latest update to version 5.5 of its global virtualisation powerhouse, vCloud Suite.

To read the updates for all the suite components, see my post: What’s New in vCloud Suite 5.5: Introduction

vCenter SSO gets one of the major updates. This is welcome news to anyone who installed SSO in vSphere 5.1 which was plagued with an overly complex and restrictive design. SSO in 5.1 was apparently an OEM component which VMware customised. SSO in 5.5 has been completely rewritten from the ground up internally.

Evolving vCenter is a major undertaking as it was originally built as a monolithic platform with everything included in one place. VMware’s strategy is to pull out all the core central services from vCenter and have them run stand-alone.

In the future, vCenter may not in fact be the only management option. I can think of other future management options such as OpenStack or even Microsoft System Center or some other partner management ecosystem, all obviously at cloud scale. Today SSO has been re-built to scale serving vCloud Director, vCenter Orchestrator and Horizon View.

What’s New:
The whole architecture has been redesigned with a multi-master model with built-in replication both between and within sites. There are no longer primary and secondary SSO servers. Site awareness is part of the design, you can add new sites and SSO can be aware of the original site.

Read more…

VMware has announced its latest update to version 5.5 of its global virtualisation powerhouse, vCloud Suite.

I would say that this is an evolutionary rather than revolutionary update being the third major release in the vSphere 5 family (5.0,5.1,5.5).

There are however some significant storage additions such as Virtual SAN (VSAN) and VMware Virtual Flash (vFlash) as well as a new vSphere App HA to provide application software high availability which is in addition to vSphere HA.

VMware has also responded to the customer frustration over Single-Sign on (SSO) which is an authentication proxy for vCenter and made some changes to SSO to hopefully make it easier to deploy. Every component of the suite has been updated in some way which is an impressive undertaking to get everything in sync.

Here are all the details:

1. What’s New in vCloud Suite 5.5: Introduction
2. What’s New in vCloud Suite 5.5: vCenter Server and ESXi
3. What’s New in vCloud Suite 5.5: vCenter Server SSO fixes
4. What’s New in vCloud Suite 5.5: Virtual SAN (VSAN)
5. What’s New in vCloud Suite 5.5: VMware Virtual Flash (vFlash)
6. What’s New in vCloud Suite 5.5: vCloud Director
7. What’s New in vCloud Suite 5.5: vCenter Orchestrator
8. What’s New in vCloud Suite 5.5: vCloud Networking & Security
9. What’s New in vCloud Suite 5.5: vSphere App HA
10. What’s New in vCloud Suite 5.5: vSphere Replication and vCenter Site Recovery Manager

VMware is certainly evolving their strategy of the software defined data center, this release puts software defined storage (SDS) on the map at least from a VMware perspective, a multi-year project. VMware vVolumes hasn’t made it into this release which shows what a major undertaking it is, we will have to wait for vSphere 6!

SDS is going to have a huge push this year from VMware and of course all the other storage vendors, expect some exciting innovation.

Software defined networking is the next traditional IT infrastructure piece to “Defy convention” and is arguably by far the hardest one to change. Another multi-year project is just beginning.

VMware and HP have both released advisories which say you shouldn’t use HP Virtual Connect in tunnel mode if you are using vCloud Director Network Isolation (vCDNI) which is MAC-in-MAC encapsulation.

There are two network modes available with Virtual Connect, Tunnel Mode and Mapped Mode.

When using Tunnel Mode, Virtual Connect passes all tagged and untagged packets through the Virtual Connect switch down to select blades where the VLANs are split into port groups. The uplinks are therefore considered dedicated uplinks as control over which VLANs are trunked is done at the upstream switch and so you can’t have a different set of VLANs going to Blade 1 and Blade 2 while still utilising the same uplinks. You could obviously have separate sets of uplinks for Blade 1 and Blade 2 to achieve this. The advantage of tunneling mode is only having to specify your VLANs once at the upstream switch and being able to pass all VLANs down the same trunk to multiple blades and only having to manage VLANs at the upstream switch and port groups on the ESXi host or within the vSphere Distributed Switch.

In Mapped Mode  mode, the Virtual Connect switch examines all the VLANs and by defining Ethernet Networks for each VLAN on the Virtual Connect switch you can selectively pass down all or some of the VLANs down to the blades. The uplinks are considered shared as you can trunk all VLANs you will need for any blade and for example have some VLANs going to Blade 1 and other VLANs going to Blade 2 but sharing the same uplinks. In order to do this you  have to create separate Ethernet Networks for every VLAN (possibly two for redundancy) and manage VLANs at both the upstream and Virtual Connect switches as well as port groups on the ESXi host or within the vSphere Distributed Switch.

Read more…

Unless you are a photographic memory super VCDX you probably don’t have every single ESXi command line, PowerCLI Cmdlet or vCloud Networking construct available in memory.

Luckily for the rest of us normal people, VMware has released some fantastic posters detailing these topics in an easy to grab format which you can download for your pleasure.

They are large format .PDF posters so you can print them out and either impress your friends with your techy wall art or have them handy on your smart phone just when you need to troubleshoot a problem.

Don’t forget you can also get the amazing vReference cards made by Forbes Guthrie.

VMware ESXi 5.1 Reference

VMware Management with PowerCLI 5.1

VMware vCloud Networking

VMware’s US mega conference, VMworld kicks off in San Francisco in just over 2 weeks time. 19000 people attended in Las Vegas last year (we will have to see whether the choice of venue affects the numbers for this year!)

This will be my first time attending VMworld US as living in London I have attended VMworld Europe previously so am excited to see the differences, enjoy the bigger conference and meet some more fellow vExperts and other community members.

There’s obviously a huge amount that goes on at the conference from the keynote speaches, breakout sessions, panel discussions, labs, formal and informal meetings, and general networking so working out what to actually see with so much going on is harder than many people would assume.

Read more…

VMware has released what at first looks like a minor update to their PowerShell snapin, PowerCLI to version 5.01. Although just a .01 release which brings the usual changes and bug fixes which are listed here,  the big news is that VMware has added a whole bunch of cmdlets for managing vCloud Director.

A whole new snapin has been created called VMware.VimAutomation.Cloud and this initial release focuses more on the reporting side, so being able to retrieve information from vCD rather than setting things but also does have cmdlets for importing VMs, Templates and .OVFs from vSphere into your vCD environment. This is a great step forward as cloud computing relies so much on automation and having PowerCLI also available means you have so many more options to tie together your automation workflows.

Read more…