vFrank

Essense of virtualization

FrankBrix

Join The Public VMware Workstation Technology Preview 2013

by Leave a Comment

I just received an e-mail from VMware about the public technology preview of the next version of VMware Workstation. Everybody can participate so I wanted to share it with you. Find the e-mail below.

 

The VMware® Workstation™ Team is excited to invite you to participate in the VMware Workstation Technology Preview 2013. With the upcoming Windows 8.1 release, and the recent releases of Ubuntu 13.04, and Fedora 18 we thought it was the perfect time to release a technology preview. We would like to get your feedback on new capabilities that may appear in future releases of VMware Workstation.

In this preview, we would appreciate your help in evaluating the following areas:
• Creating and running Virtual Machines using the latest operating systems
• Running Restricted virtual machines with an expiration date
• Converting physical machines running Windows 8 into virtual machines
• Performance of Virtual Machines running up to 16 vCPUs
• General stability, application compatibility and usability
This is a public technology preview. You may share this email with your peers so they can download and try the technology preview.

Get Started Now
1. Download the VMware Workstation Technology Preview here: http://communities.vmware.com/community/vmtn/beta/workstation_2013
2. When prompted, enter this expiring license key to enable the software: M109C-N0J5L-08J8A-02ARP-CE64F (expires 10/15/2013)

Your participation in the technology preview is an important part of the product development process. Your feedback helps the VMware Workstation Team:

– Improve the implementation of new features
– Guarantee a reliable installation experience
– Increase product performance and stability
– Test a broader number of operating systems and devices
– Refine general usability

Provide feedback
To provide your feedback to VMware, please visit the technology preview community site:
http://communities.vmware.com/community/vmtn/beta/workstation_2013

Please contribute to an existing discussion or start a new one. Our Developers, Quality Assurance Engineers, Support Teams, Technical Writers and Product Managers are all actively involved in the forums to ensure that your suggestions and comments get our attention.

Thank you very much for participating in the VMware Workstation Technology Preview 2013 program.

We look forward to your feedback!

The VMware Workstation Team

vExpert 2013 – an honor

by 1 Comment

I have been awarded vExpert 2013. This is the fourth year in a row for me. It is a great honor for me but it also sets the bar high for things to do for the community in the following year. Hopefully in the next year I will have at least one VMUG presentation and if lucky one of my VMworld sessions will get approved.

If you want to see who else made it you can see the list here 575 people made it this year.

This is the Danish #vExpert group of this year. (sorry if I missed ayone)

 

Mikael Korsgaard Jensen @jekomi – VMUG DK leader 

Liselotte Foverskov @LFoverskov – VMUG DK leader

Rasmus Haslund @haslund – Blogger

Kenneth Hansen – VMUG DK leader

Nicolai Sandager – @nsa42 VMUG DK leader

 Gert Kjerslev @gertkjerslev – Blogger

 

 

 

High Availability in a vCloud Director Environment

by 2 Comments

High Availability in a vCloud Director Environment

 

Making sure your cloud is accessible, at all time,  to end users and administrators is an important task. When looking into a cloud based on VMware vCloud Director there are several things to take into consideration. A VMware vCloud can consist of a lot of components. The mandatory components are the following

  • VMware vCenter Server (Typically Windows 2008/2012 or Linux Appliance)
  • VMware ESXi hosts
  • VMware vShield Manager (Linux Appliance)
  • VMware Director cell (Red Hat Enterprise Linux)
  • Database Server for vCenter and vCloud Director

Optional Components

  • vCenter Chargeback
  • vCenter Operations Manager
  • vCloud Automation Center
  • VMware Orchestrator
  • …

You have to think about how you want to protect the mandatory and optional components. I will focus on the mandatory now.

VMware vCenter Server

There are different ways to protect the vCenter Server. But before you think about protection you need to think about how you are going to deploy it. Your first option is am I going with the Windows version or going with the Linux appliance. In most cases people go for the Windows version, and that is definitely the safe bet. One of the things the Linux appliance has against it is only support for external Oracle databases. No MS SQL support.

If you choose the Windows version you have to consider if you are a splitting the vCenter roles up on multiple virtual machines. The roles you are considering are the following: SSO, Inventory Service, vCenter Service and Update Manager. For best performance and scalability you would split it up. But that also means you have to consider how to protect each server.

SSO has its own “clustering” functionality. But Inventory Service and vCenter does not. In most situations the software is installed inside a virtual machine running on a ESXi host with VMware HA enabled. This means you don’t need to worry about physical server failure. But it does not protect you against a failure on the software side that could be related to the Operating System or vCenter itself. If you figure out you want to go beyond hardware failure your only option is to deploy VMware vCenter Heartbeat. Heartbeat is able to protect all servers running SSO, Inventory Service and vCenter Service. It does it by replicating the server to another virtual or physical machine. Heartbeat is the tool if you have very strict SLA agreements. It will make your system more secure, but it will be on the cost of losing simplicity.

ESXi hosts

The ESXi hosts are the easiest to protect, and you don’t have to do a lot of planning in this area. Just make sure you have multiple ESXi hosts. All connected to the same network and access to the same shared storage. This way the virtual machines can gets it compute resources from any host in the cluster. On that cluster you will enable the DRS and HA functionality. I would not even worry about backing up the ESXi hosts. If you lose a host just reinstall it.

VMware vShield Manager

The vShield Manager comes as a virtual appliance from VMware. You simply download it and import into your management cluster. There is no native clustering functionality so you have to rely on VMware HA or VMware Fault Tolerance.

VMware Director Cell

The vCloud Director software has to be installed on a Linux machine running Red Hat Enterprise. Luckily for us the software has its own clustering functionality. What you basically do is install multiple Red Hat machines. All of these machine will share the same database on MS SQL or Oracle and the will also have access to the same NFS share. When implementing multiple vCloud Director Cells you would deploy the behind a load balancer. That load balancer could be VMware vShield Edge or you could use something else like Netscaler, F5 etc.

Database Server

The database server is extremely critical in the vCloud Environments. If we are only looking at the mandatory components you will have created three databases on your server. One for the SSO service, One for the vCenter Service and One for the vCloud Director Cell.

What you would normally do with your database is to look into clustering the MS SQL or Oracle with its own tools. If you don’t want to cluster the database. At least make sure that it is running as a virtual machine so you get the benefit of VMware HA. And of course remember to backup all databases at a regular interval.

If you are using a MS SQL cluster you have to know that it is not “officially” supported by VMware for the SSO service. Although they will do their best to help you if you have problems. I have installed all of the components against a MS SQL Cluster and haven’t experienced any problems yet. But we aware of this and set it as a risk.

VMworld 2013 – My session submissions

by 2 Comments

VMworld US 2013 is in San Francisco from August 26th to 29th and VMworld Europe is from October 15th to 17th. This year I have submitted two sessions to VMworld. VMworld Call for papers ended April 12.

The title of the first session is: “vCenter Operations Manager – Troubleshooting Best Practises” #4555. I did a session at the danish VMUG March 7th and it was very well received by the audience. This gave me the confidence that it was ready for a bigger audience and I have submitted it for VMworld US and VMworld Europe. 

The second session is: “From vSphere to Hybrid Cloud – Best Practises” #4799. This is a session I have submitted with Michael Munk Larsen from Zitcom. In this session we are going to be talking about the move from vSphere to the hybrid cloud, and discuss the challenges and how to build the hybrid cloud.

Hopefully one or both of the sessions will be accepted. I know it is extremely hard to get sessions approved, but I keep my fingers crossed. In a few weeks I expect the public voting to start, and during the public voting I need your help to get attention to the sessions.

 

Mark a disk as SSD and Local in ESXi 5.x

by Leave a Comment

I was just working in my lab and wanted to play around with a vSphere 5.x feature. The feature I wanted to use required that the disk is SSD and the disk is Local. My lab environment is entirely virtual and I have no SSD. Here is what I did to accomplish it.

The first thing you need to do is list your devices. Everything is done from the local ESXi shell:

esxcli storage nmp device list

This gave me the following output. The information you need to look for is the “device id” and the “satp”

Fake_ssd_1

 

The next thing we can do is to mark the device as “Local” and “SSD”. I used the following command:

esxcli storage nmp satp rule add –satp VMW_SATP_LOCAL –device mpx.vmhba2:C0:T0:L0 –option “enable_local enable_ssd”

Then we have to claim the new rule:

esxcli storage core claiming reclaim -d mpx.vmhba2:C0:T0:L0

And at the end we can run the following command to verify our changes:

esxcli storage core device list –device=mpx.vmhba2:C0:T0:L0

Fake_ssd_2

 

After doing this ESXi detected the disk as a Local SSD and I could start working in my lab.

vCenter Performance Graph Versus vCenter Operations Manager Metric Chart

by Leave a Comment

Most people who works with vSphere already knows the vCenter Performance Graphs. What most people don’t know is the “Metric Chart” in vCenter Operations Manager. In this article I want to discuss pros and cons of vCenter Performance Graphs vs. vCenter Operations Manager Metric Charts.

The Performance Graphs in vCenter can show information about the following CPU, Datastore, Disk, Memory, Network, Power, System, Virtual disk. You can the select if you want the graph to show: Real-time, Past day, Past week, Past month, past year or Custom. 

 When looking at these graphs the following table sums up what you are seeing.

vcenter_data

So by looking at the Real-Time graph you actually looks at a graph that is updated by a frequency of 20 seconds. So 180 datapoints in just one hour. But when you look at Past Day your graph is updated every 5 minutes. This is where rollup occurs. Without rollup you vCenter database would grow a lot in size. Whatever data you look at in the Past Day the graph is updated in 5 minutes interval, but what happens if you look at the graph more than 24 hours ago? Well if it is in the past week your graph will be updated every 30 minutes, but if you are further back your graph is updated every 2 hours! This basicly tells us that vCenter Performance Charts is BEST in Real-Time, it is alright in Past Day but moving further back than 24 hour data is being rolled up and we loose valuable insight. Look at the following screenshots to see what happens:

realtime_cpu_ready

real_time_cpu_day

 

real_time_yesterday

 

You should have noticed how we lose information when we try to investigate performance back in time. The further back we go the more we lose. Not only does data points get rolled up. But try and go back to the first graph. On the first graph we had the counters “Ready” and “Used” but on the other two we only have “Ready”. No I did not remove it. This is another feature of vCenter. Not only does it roll up. But it also chooses to remove counters as soon as we are looking at data more than one hour ago.

 cpu_realcpu_pastday

 

Now you should know some of the limitation with vCenter. So what is the solution if you want to look at data that is 1) More than one hour ago or 2) more than one day ago. The answer is of course vCenter Operations Managers Metric Charts. vCenter Operations Manager collects every counter and does not remove them when looking back. And vCenter Operations Manager have data points every 5 minutes. So yes you can argue that the past hour graph in vCenter is better than vCenter Operations Manager! That is true. The only time you actually should use vCenter Performance Graphs is when looking at the “Real-Time” graph.

Lets take a look in vCenter Operations Manager:

cpu_last_hour_vcops

 

The graph is for the “Last Hour” but I can dive into any period and see all counters updated every 5 minutes. Maybe it is monday morning now and we have a reported performance problem that happened this saturday between 2am and 3am. Well just change the graph to that interval. Data is there, and you have EVERY counter. 

VMUG.DK Updates

by Leave a Comment

Yesterday the Danish VMware User Group held a meeting in The movie theater Palads in Copenhagen. The theme of the day was “Admin & monitor” and I did a presentation on vCenter Operations Manager. It was a great day. It is incredible how much of their own time the Danish VMUG team puts into these events.  It is really appreciated. The next VMUG.dk events are already beeing prepared and it looks to be a good year.

  • June 13th VMUG meeting at VMware in Nærum. This is an Annual event and after the meeting there is a tradition of home brewed beer and BBQ!
  • December 3rd. VMUG meeting in Copenhagen @ Bella Centeret. This is the same place as VMworld Europe took place in 2010 and 2011. This VMUG will be a full day conference with 25-30 sessions. They hope to get at least 300 delegates. And of course it is free! So save these two dates. I hope to see you there.

VMUG DK meeting in March “Admin and monitor”

by Leave a Comment

Just wanted to get this out there. The next VMUG DK meeting will be in Copenhagen at “Palads” on March 7th. 

You can register for the event here: http://www.eventbrite.com/event/5299404662#

The subject will be “Admin and Monitor”. I will be doing a 50 minutes presentation on “vCops Best Practises” (still working on the title)

After the event you will get tickets for the move “The Last Stand”. 

I can’t wait! Hope to see you all there!