VMworld Europe Day Two
Today is pretty much the day the whole conference springs to life. All the remaining delegates join the party with the TAM and Partner delegates. The Solutions Exchange opened for business and there’s just a much bigger bustle about the place than there was yesterday.
The opening general session was hosted by Carl Eschenbach, and credit to him for getting straight in there and talking about the Dell deal. I think most are scratching their heads, wondering what this means in the broader scheme of things, but Carl reassured the delegates that it would still be ‘business as usual’ with VMware acting as an independent entity. That’s not strictly true, as they’re still part of the EMC Federation, who are being acquired by Dell, so not exactly the same.
Even Michael Dell was wheeled out to give a video address to the conference to try and soothe any nerves, giving one of those award ceremony ‘sorry I can’t be there’ speeches. Can’t say it changed my perspective much!
The event itself continues to grow. This year there are 10,000 delegates from 96 countries and a couple of thousand partners.
Into the guts of the content, first up were Telefonica and Novamedia. The former are a pretty well known European telco, and the latter are a multinational lottery company. The gist of the chat was that VMware solutions (vCloud, NSX etc) have allowed both companies to bring new services and solutions to market far quicker than previously. In Novamedia’s case, they built 4 new data centres and had them up and running in a year. I was most impressed by Jan from Novamedia’s comment ‘Be bold, be innovative, be aggressive’. A man after my own heart!
VMware’s reasonably new CTO Ray O’Farrell then came out and with Kit Colbert discussed the ideas behind cloud native applications and support for containers. I’ll be honest at this point and say that I don’t get the container hype, but that’s probably due in no small part to my lack of understanding of the fundamentals and the use cases. I will do more to learn more, but for now, it looks like a bunch of isolated processes on a Linux box to me. What an old cynic!
VMware have taken to approaches to support containers. The first is to extend vSphere to use vSphere Integrated Containers and the second is the Photon platform. The issue with containerised applications is that the vSphere administrator has no visibility into them. It just looks and acts like a VM. With VIC, there are additional plug-ins into the vSphere Web Client that allow the administrator to view which processes are in use, on which host and how it is performing. All of this management layer is invisible and non-intrusive to the developer.
The concept of ‘jeVM’ was discussed, which is ‘just enough VM’, a smaller footprint for container based environments. Where VIC is a Linux VM on vSphere, the Photon platform is essentially a microvisor on the physical host, serving up resource to containersa running Photon OS, which is a custom VMware Linux build. The Photon platform itself contains two objects – a controller and the platform itself. The former will be open sourced in the next few weeks (aka free!) But the platform itself will be subscription only from VMware. I’d like to understand how that breaks down a bit better.
VRealize Automation 7 was also announced, which I had no visibility of, so that was a nice surprise. There was a quick demo with Yangbing Li showing off a few drag and drop canvas for advanced service blueprints. I was hoping this release would do away with the need for the Windows IaaS VM(s), but I’m reliably informed this is not the case.
Finally, we were treated with a cross cloud vMotion, which was announced as an industry first. VMs were migrated from a local vSphere instance to a vCloud Air DC in the UK and vice versa. This is made possible by ‘stretching’ the Layer 21 network between the host site and the vCloud Air DC. This link also includes full encryption and bandwidth optimisation. The benefit here is that again, it’s all managed from a familiar place (vSphere Web Client) and the cross cloud vMotion is just the migration wizard with a couple of extra choices for source and destination.
I left the general session with overriding feeling that VMware really are light years ahead in the virtualisation market, not just on premises solutions but hybrid too. They’ve embraced all cloud providers, and the solutions are better for it. Light years ahead of Microsoft in my opinion, and VMware have really raised their game in the last couple of years.
My first breakout session of the day was Distributed Switch Best Practices. This was a pretty good session as I’ve really become an NSX fanboy in the last few months, and VDSes are the bedrock of moving packet between VMs. As such, I noted the following:-
- DV port group still has a one to one mapping to a VLAN
- There may be multiple VTEPS on a single host. A DV port group is created for all VTEPs
- DV port group is now called a logical switch when backed by VXLAN
- Avoid single point of failure
- Use separate network devices (i.e switches) wherever possible
- Up to 32 uplinks possible
- Recommend 2 x 10v Gbps links, rather than lots of 1 Gbps
- Don’t dedicate physical up links for management when connectivity is limited and enable NIOC
- VXLAN compatible NIC recommended, so hardware offload can be used
- Configure port fast and BPDU on switch ports, DVS does not have STP
- Always try to pin traffic to a single NIC to reduce risk of out of order traffic
- Traffic for VTEPs only using single up link in an active passive configuration
- Use source based hashing. Good spread of VM traffic and simple configuration
- Myth that VM traffic visibility is lost with NSX
- Net flow, port mirroring, VXLAN ping tests connections between VTEPs
- Trace flow introduced with NSX 6.2
- Packets are specially tagged for monitoring, reporting back to NSX controller
- Trace flow is in vSphere Web client
- Host level packet capture from the CLI
- VDS portgroup, vmknic or up link level, export as pcap for Wireshark analysis
- Use DFW
- Use jumbo frames
- Mark DSCP value on VXLAN encapsulation for Quality of Service
For my final session of the dayt, I attended The Practical Path to NSX and Network Virtualisation. At first I was a bit dubious about this session as the first 20 minutes or so just went over old ground of what NSX was, and what all the pieces were, but I’m glad I stayed with it, as I got a few pearls of wisdom from it.
- Customer used NSX for PCI compliance, move VM across data center and keep security. No modification to network design and must work with existing security products
- Defined security groups for VMs based on role or application
- Used NSX API for custom monitoring dashboards
- Use tagging to classify workloads into the right security groups
- Used distributed objects, vRealize for automation and integration into Palo Alto and Splunk
- Classic brownfield design
- Used NSX to secure Windows 2003 by isolating VMs, applying firewall rules and redirecting Windows 2003 traffic to Trend Micro IDS/IPS
- Extend DC across sites at layer 3 using encapsulation but shown as same logical switch to admin
- Customer used NSX for metro cluster
- Trace flow will show which firewall rule dropped the packet
- VROps shows NSX health and also logical and physical paths for troubleshooting
It was really cool to see how NSX could be used to secure Windows 2003 workloads that could not be upgraded but still needed to be controlled on the network. I must be honest, I hadn’t considered this use case, and better still, it could be done with a few clicks in a few minutes with no downtime!