The up.time IT Systems Management Blog

Posts Tagged ‘VMware’

Do more with less. Virtualize and save – but plan carefully!

Wednesday, June 10th, 2009

Here’s some more work for you. Here’s some more responsibility. Here’s a shorter deadline. Now do it all with less money, less time, less resources, less, less, less!

It seems as though the more efficient we become, the more constrained we are. The current economic climate doesn’t help either.   Yes, this is the new norm.  So what can you do?

If you’re reading this you’ve probably invested time and money into a virtual infrastructure, or are considering it.  Great!  Virtualized computing environments squeeze every last drop of performance from hardware and, when properly budgeted, can save you thousands in the long run. But don’t expect a free lunch.

Physical to Virtual Consolidation

Consolidation of physical servers to virtual hosts allows you to break the 1 application to 1 server mold.  However the increased density in your server room might create hot spots, especially if you’ve decided on using a blade chassis.

That increased density means you’ll also be pushing your hardware harder. This will likely increase your power requirements, slightly.  Newer hardware is indeed more efficient, and technologies like VMware’s DRS Distributed Power Management allow you to move workloads around to less stressed hosts and power off unused resources. The net effect is a possible overall reduction in power usage, but peak times could actually require more.

An Up Front Expense?

Virtualization is a net new expense. Unless you are starting from scratch, you will need to invest in hardware, and software licensing.  I was recently asked to vet the cost of a 24 host, enterprise level virtual environment.  Assuming a requirement of 10 Terabytes of storage, and going with mid tier hardware I came up with an up-front ballpark cost of USD $225,000.  No small change.  Amortize your projected savings carefully. Is it worth the up-front investment? Luckily you can grow your virtual environment easily as required with little to no negative impact on the existing services.

Implement Standards

Virtualization has made provisioning services a snap. You’ve heard all the marketing buzz — reduced time to market, provision servers in seconds!, etc.  Suddenly that 10T of storage is GONE.  But how?

Sprawl. (Yes, up.time can help you with this!)

Back in the days before virtualization, if you needed more resources you had to justify the expense nine ways from Sunday.  When it finally arrived you’d spend a week staging it.  Then testing and finally implementing it, only to have it completely consumed a few months later!  When you planned your virtual infrastructure you WAY over provisioned it, didn’t you?  You thought ahead 3 years like you  did when you bought a single server for that one application.  However now you’re planning for possibly hundreds of workloads.  Need another machine?  No problem, just clone it and wait a few minutes.   Ever have cash burn a hole in your pocket?  Budgets prevent us from blowing that spare cash.  It’s exactly the same in a virtual environment, except the spare cash is extra CPU cycles, storage and memory.  From simply devising a set of rules for managing the virtual machine life cycle, or implementing tools to manage it, the only way you will realize long-term savings is to ensure you’re only using what you need.  Don’t run your VM environment like that TV salesperson’s famous oven — “Set it, and forget it!”.

If you keep these things in mind when building and managing your VMware vSphere environment, or any other virtual infrastructure, you will absolutely be able to do more, with less. Of course <shamesless plug>, up.time can solve you VMware monitoring needs with it’s deep VMware monitor and reports.

VMware vSphere – Are you ready? We are!

Wednesday, June 3rd, 2009

Unless you live under a rock, you know that VMware recently released vSphere 4.  The highly anticipated upgrade to its virtual infrastructure suite.  The number of feature upgrades and enhancements makes the new version somewhat hard to ignore.  But if you’re like me you tend to shy away from .0 releases.  I usually wait for the real world installations to sort out the bugs and let the developer issue a patch or point release. Let someone else be my guinea pig.  The last thing you want is for an upgrade to nuke your production system.

I am, however, happy to report that our experience with vSphere 4 has been relatively smooth so far.  While I’ve not taken the plunge and upgraded our production environment yet, our lab upgrade from 3.5 to the 4.0 beta, and subsequently the general release went off without a hitch.  This gives me the confidence to at least begin the planning stages of the production system upgrade.

Step one is to make sure our existing systems are at the latest version of Infrastructure 3.5 and fully patched. We start that in a a week or so and I’ll keep you all abreast of the progress.  One thing I don’t have to worry about as we ready our production environment for vSphere is that the up.time monitoring station is waiting for us on the other side.  It’s just waiting for me to play catch up!

So, have you upgraded to vSphere yet?  Tell us about your experience with the process and about vSphere in general. Or even better, if you are monitoring your vSphere infrastructure with up.time we’d love to hear about your experience. You can visit the up.time website for more on vSphere Monitoring or VMware monitors.

VMware VMotion & DRS… Problem Solved

Wednesday, May 27th, 2009

I have been working with a large financial institution for the past few months and on Monday, they used one of the many Virtualization reports available in up.time 5 to help solve an issue they were having with one of their VMware ESX clusters. I have been using this report quite a bit but wanted to highlight it on the blog. It’s called the VMware Instance Motion Report and tracks instances (Virtual Machines) and when they VMotion (move) around an ESX cluster. Either manually or by such methods as DRS (Distributed Resource Scheduler).

For the financial customer I was referring to, they had recently setup DRS on a new cluster. For those of you not familiar with DRS, it basically dynamically allocates resources to enforce resource management policies while harmonizing resource usage across multiple ESX hosts. One of the options when setting up DRS is how aggressive you want to be (this is set across the entire cluster) and has five different options which range from Level 1 (Conservative) to level 5 (Aggressive). The person who had setup DRS on this new cluster had it set to level 5 which was causing constant VMotioning between hosts. We were able to immediately see this in the instance motion report, which tracks individual Virtual Machines across multiple ESX hosts.

Problem Solved.

VMware Instance Motion Report

[/caption]

VMware Lifecycle Management Question…

Tuesday, May 5th, 2009

I was recently over at the “Offical VMware Virtualization Group” at Linkedin and a person was asking about VM Lifecycle Management and how they could prevent VMsprawl in their datacenter.

I have been working with VMware Virtualization for the past few years and the topic of VM Lifecycle Management has become much more prevalent over the last 6 months. One of the most confusing things is that VMware named their provisioning system “VMware Lifecycle Manager” when it is really all about getting VM’s into the infrastructure. It’s not so much about managing those VM’s, preventing VM sprawl, performance monitoring of ESX/individual VMs, visibility, control and audibility.

VMware did acquire a company called Dunes Technologies which played in the Lifecycle Management game. VMware is now releasing the Dunes product as VMware vCenter Orchestrator. It really concentrates on drag and drop automation and orchestration. This in combination with vSphere will help solve some of the lifecycle management issues; however, there is still the need for a 3rd party to get total control.

Check out the VMware Monitoring page at uptime software and you will see how up.time 5 can greatly assist in getting control back in your virtual infrastructure. Better virtual management and performance, deep workload profiling, VM density optimization reporting, tracking of vMotion, VMsprawl prevention and consolidation planning tools.  All in one easy to install application that not only will help with your virtual machines but your physical boxes as well.

Adapting to the Integrated Technology Stack: Next Generation IT Systems Management

Saturday, May 2nd, 2009

I read  The race for the integrated technology stack, from Enterprise Strategy Group this week. Some completely valid points are made about the transition that IT departments and tool vendors in the ITSM space are going to have to go through to add value to the ‘new’ integrated data center. Virtualization has already challenged many deeply entrenched paradigms that many IT staff, and software vendors, have struggled to adapt to.

Agility from a training and tooling point of view are going to be essential for companies to see success in their rapidly changing environments and ensure that they are able to maintain their IT SLA with their users through this transition. As the integrated stack and adaptive infrastructure continue to gain share in large environments I have to wonder how software vendors, who are already unable to adapt to the rate of change in the data center, will stay relevant.

I see more agile companies like uptime, who already have mature solutions in the virtual systems management & physical server monitoring space, being able to adapt faster and offer solutions that directly address challenges in the new data center well before the big 4 framework vendors are able to align their solutions with the modern day problem set.

Virtualized Virtualization. Is it art?

Wednesday, April 29th, 2009

I love elegant but useless hacks.  There’s something artful about hacks that provide no real value, other than to make a statement;

“Yes, this can be done”

It’s like scaling Everest, or BASE Jumping the Petronas Towers in Kuala Lumpur.  But why do it?  Take, for example, this hack:

Run VMware ESX 3 in a VMware Workstation 6 virtual machine.

Can someone please explain to me why this is useful?

I’m not trying to be being obtuse, or short sighted.  I see the benefit of running ESX within a desktop virtualization platform for, say, quick development purposes, or simply to familiarize one self with the product.  But surely you have a hunk of hardware lying around that would better host ESX and give you more of a real-world feel for it?  Besides, ESX isn’t free.  You have 60 days to evaluate it, and surely you’re not going to purchase a license to run it in a virtual machine.  ESXi is free and can apparently be coerced to run virtualized as well.

So, are hackers artists?  Running a virtualization platform inside a virtualization platform is interesting, but not particularly useful.  It’s a beer’s worth of discussion, but much more than that and you’re thinking too hard about it.  Move on to the next piece in the gallery.

vSphere Makes for Interesting Times

Friday, April 24th, 2009

With the announcement of vSphere on Tuesday by VMware and the associated products that are coming as part of the overall solution, it is a very exciting time for us IT folk.  There are several enabling technologies that are a part of their new ‘cloud operating system’ that will fundamentally change how we implement IT services within the datacenter, and bridge those services between the public and private cloud.  There are two technologies that are really interesting to me, the new version of Orchestrator and VMsafe.

With Orchestrator, truly automated application delivery based on SLA targets can be achieved, and not just for the components running on vmware, but across the service stack.  Orchestrator provides hundreds of out of the box workflows, with 3rd party vendors providing their own workflow packs for Orchestrator.  Creating fully automated stacks across multiple vendors is about to become much easier.  What used to take significant development effort can be accomplished with a drag and drop workflow builder.

The other technology that is very exciting is VMsafe.  Through VMsafe, software vendors will be able to provide technology solutions that are truly application aware.  Through the API they will be able to know exactly what the application workload is doing to the vSphere environment without having to instrument the guest.

Distributed Fault Tolerant workloads, and lifecycle/stage manager/orchestrator all come together to provide a complete solution that will allow commodity servers to provide the flexibility and availability that was once the realm of MVS, but without the expense.

Posted on behalf of Chris Knowles

 

VMware announces vSphere release…

Tuesday, April 21st, 2009

Today, VMware announced the release of vSphere. On the same day uptime announced support for vSphere in the current version of up.time. We have been working with VMware over the past few months to ensure we could support this release immediately. Watching the VMware vSphere webcast this afternoon, it was great to see all the new features (thin provisioning, Distributed Power Management, Fault Tolerance and the many enhancements created in partnership with Cisco) that are now available in this “Cloud Operating System”.

What’s even more exciting is the amount of new products coming out this year from VMware.  vCenter Chargeback, vCenter ConfigControl, vCenter CapacityIQ, vCenter AppSpeed and vCenter Orchestrator just to name a few. The one that I find really exciting is vCenter Orchestrator. Basically, it’s a GUI based workflow tool that interacts with the VMware API, CLI, SSH, 3rd party systems to name a few. For those of you who have been using VMware Lifecycle Manager… you have already seen bits of vCenter Orchestrator. With over 400 pre-built workflows there is a lot of potential automation that will be able to be put in place…stayed tuned.

uptime is committed to supporting the virtualization initiative, so I am truly excited for our coming software releases of up.time over the next 2 quarters. Just this past month, I have been working with customers to assist in implementing a real “Single Pane of Glass” management system for both physical and VIRTUAL servers. Beyond that, I’m busy helping to prevent VM sprawl and assisting in virtualization/consolidation planning using up.time 5.