Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

The Trouble with Virtualization - Cranky IT Staffs

Posted by Zonk on Thu Jan 03, 2008 02:22 PM
from the p-e-b-k-a-c dept.
lgmac writes "A new survey on the results of Enterprise use of virtualization shows that the process is seeing wide and appreciative use. Technical hurdles are obviously the biggest problem facing corporate IT shops. Just the same, political squabbles among IT staffers fighting for turf after being forced to work together in new ways seems to be a going concern as well. 'Technical woes rank higher--to be expected when CIOs deploy a new technology such as virtualization. However, the politics pain many of you. Remember, virtualization not only asks people to cede some control over their physical server kingdoms, but also asks IT experts from different realms to work more closely together.'"
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • 34% on desktops? (Score:4, Informative)

    by Otter (3800) on Thursday January 03 2008, @02:26PM (#21899036) Journal
    34% of surveyed companies have been running virtualized desktops? Putting aside that that number doesn't seem to square with the "Virtual Desktops a Hard Sell" table below, does that seem likely?!?
    • As with many articles in that rag...the points it seems to make are all on the boss's hair. I am sure my lack of understanding comes from my lack of righ-sized, value added, synergy.
      • by OnlineAlias (828288) on Thursday January 03 2008, @03:01PM (#21899618)
        On a go forward basis, you need step up to the plate and reach out to someone to get your thought processes in alignment. Perhaps a little thinking outside the box or brainstorming session would help to get someone to take ownership of this problem. Anyway, thanks for running this up the flagpole but lets take this conversation offline. I'll touch base with you later to discuss some of these basic action items.....
          • by syousef (465911) on Thursday January 03 2008, @05:23PM (#21901818) Journal
            Office Space, meet Slashdot.

            - They said I'm allowed to troll at a reasonable volume.

            - Now Milton, don't be greedy, let's pass along the karma and make sure everyone gets a piece.

            - Excuse me? Excuse me, senor? May I speak to you please? I asked for an overlords joke, and they brought me an in soviet russia joke.....and I said no trolling, NO trolling for the replies, but it lots of trolls, big stupid trolls

            - Oh, and remember: next Friday... is MS bashing shirt day. So, you know, if you want to, go ahead and wear an MS bashing shirt and jeans.

            - I can't believe what a bunch of nerds we are. We're looking up "social engineering" in a dictionary.

            - Just remember, if you hang in there long enough, good things can happen in this world. I mean, look at me.

            - Looks like you've been missing a lot of work lately.
  • Backup problems (Score:3, Interesting)

    by r0BOT (1211902) on Thursday January 03 2008, @02:29PM (#21899090)
    My companies biggest problem concerning virtualization at this point has been backing up running copies of virtual server without interruption, anyone have some insight on this?
    • Re: (Score:2, Informative)

      Depends on the virtualization solution. Vmware has a product called Vmware consolidated backup. You can also load agents on the vms just like a physical server and back them up. You could also use things like mirroring and snapshotting to back them up at the storage layer. We used a combination of all 3 at my previous employ. Really depended on the virtualized box, what needed backing up, how often, etc.
    • Don't overlook the low tech method of just running a backup client in the VM. Separately, make use SAN snapshots, and backup of those.
    • Re:Backup problems (Score:4, Informative)

      by TheRealFixer (552803) * on Thursday January 03 2008, @02:35PM (#21899196)
      On the VMware side, there's several options. VMware's Consolidated Backup [vmware.com] does exactly this. Also you can look at ESX Ranger [vizioncore.com].
    • If you can afford 5 minutes of downtime you can solve the problem by:
      • Use a host OS that has some type of shadow-copy mechanism.
      • Suspending the VM and spooling the memory out to a disk file. This should take a few minutes at most.
      • Shadow-copy all files that are normally used by the VM. This should take less than a minute.
      • Ressurrect your VM
      • Back up the image and all associated files including the associated memory spool file.

      It may be more practical to back up the system from within the VM, i.e. treat it as i

  • by truthsearch (249536) on Thursday January 03 2008, @02:30PM (#21899112) Homepage Journal
    Technology is continually changing. Those who adapt will be the most successful. Those who don't will eventually be pushed aside. Fighting over turf won't get you far in a corporate environment in the long term.
    • Fighting over turf won't get you far in a corporate environment in the long term.
      Nor will complacency and ceding to other's demands. Best to stick with social engineering and make people that want "your" turf to think it was their idea to move elsewhere :)
    • Re: (Score:2, Insightful)

      by Anonymous Coward
      Fighting over turf won't get you far in a corporate environment in the long term.

      Wrong. In most corporate environments, that is precisely how you get ahead. Playing "nice" ensures that you will always be the underling. Why? Because you are so easy to get along with, anyone can task and work with you. This can and does keep people from getting promoted.

      If you want it, you better fight for it. If you don't, it will be taken away by someone else who did. End of story.
    • Technology is continually changing. Those who adapt will be the most successful.

      And one of these days someone will teach this lesson to the RIAA right? Or is it that when things work a certain way and do so correctly (Like an AS400 Machine) they are reluctant to change and disrupt production.
    • This is nothing new. The same nonsense occurs in the "converged" world where VoIP and data mesh. You have the Cisco-tards who want to rip out and replace an entire PBX infrastructure because they think it will protect their turf if they move to Cisco's Call Mangler platform, even though it's an entirely different set of challenges. On the other side are old timer PBX folks who refuse to learn anything new.

      From my experience however, it's relatively easier for a voice person to get quickly up to speed regard
  • by sammy baby (14909) on Thursday January 03 2008, @02:31PM (#21899124) Journal
    In my experience as a systems engineer, the biggest problem we've had with virtualization is that too many people who don't understand it well view it as a magic wand that you can wave to make all your capacity & provisioning problems disappear.

    "Hey! We need a new server to run Blah version 3.0!"
    "No problem! Sammy can create a new virtual server!"
    "Oh wait - my bad. We actually need a whole farm."
    "That's okay, he can whip up a whole batch of them!"

    Ad nauseaum. About the worst I've heard was a clueless manager asking me if the resource requirements for Oracle 10g could be relaxed because we were running it on VMware. I actually found myself calling a "come to Jesus" meeting in which I explained, in as simple terms as I could, that "making the system virtual" doesn't mean that hardware requirements go away. Very, very few applications get faster when you put them on equivalent hardware, only virtualized.
    • by Cerberus7 (66071) on Thursday January 03 2008, @02:40PM (#21899292)
      *facepalm* I sometimes forget how stupid people can be.

      Personally, what I've found to work great with virtualization is consolidating all the dozens of little low-load servers. It helps with power consumption and heat output, as well as hardware costs. For a major company-wide high-load system, virtualization is absolutely not what I would be looking at. It's also fantastic for testing environments.
      • Are you crazy, man! Every DNS, NTP, and DHCP server out there needs it's own quad core with 8GB RAM! Our departmental wiki needs a whole load balanced cluster.
        • by cayenne8 (626475) on Thursday January 03 2008, @04:28PM (#21900908) Homepage Journal
          "Are you crazy, man! Every DNS, NTP, and DHCP server out there needs it's own quad core with 8GB RAM! Our departmental wiki needs a whole load balanced cluster."

          On the other hand, it often isn't a bad idea to ask for the moon when you can order hardware. Often, you get less....then I've seen SO many times, where a dev/testing box....turns INTO the production server.

          Not to mention other new projects that come in, with no budget for hardware....and you have to squeeze multiple things onto boxes that you do have.

          If you can get a quad core with 8G ram....often, I say go for it!!

      • Re: (Score:3, Insightful)

        For a major company-wide high-load system, virtualization is absolutely not what I would be looking at
        It can be, when the goal is not to run faster or cheaper, but when the goal is the ability to recover from a disaster quickly. Restarting a virtual server on a different VMWare host somewhere far away from the earthquake/fire/whatever-drama is a heck of a lot easier then having to rebuild the physical environment.
        • by gbjbaanb (229885) on Thursday January 03 2008, @04:59PM (#21901424)
          lol. Shows you don't have what it takes to work at a consultancy...

          "We want you to virtualize this system. How much will it cost?"
          "Okay... um, what are the hardware specifications?"
          no, no no nonononono.

          "We want you to virtualize this system. How much will it cost?"
          "Okay... um, quite a small amount that, amortised over the duration of the contract and combined with our leading edge technical capacity and skill-based best-of-breed approaches to migration technologies will end up saving you significant sums compared to your current total cost of ownership. Oh, and there will be a small, tiny, insignificant, additional cost based upon actual usage of capacity going forward, nothing to worry about that last bit. really. honest."

    • I owe you a beer. And you owe me a new keyboard =) It is now very Mountain Dewy.
  • I'd imagine... (Score:2, Interesting)

    by Anonymous Coward
    I'd imagine that one of the big problems with virtualization is clueless IT managers/staff who don't understand that you basically are dividing a server down into sub-servers. I've encountered a few people who seem to think that virtualization multiplies the server resources. That is, everyone using a VM basically gets the full specs of the host machine--all at once! Ugh! Maroons!
  • by Gybrwe666 (1007849) on Thursday January 03 2008, @02:36PM (#21899214)
    My company works with several shops that are working on large-scale virtualization and common platform projects. I would say the biggest single issue is simply politics, because much of the initial work is affecting older platforms that are the biggest win technically and financially to replace. For instance, one shop has a significant investment in Alpha systems, and still has production servers that are 15+ years old running a huge chunk of their revenue producing systems. The folks working directly on the Alpha servers have considerable clout, since they've been the golden children for many, many years. Their bosses know how to play politics, and, considering that Alpha/VMS experience is one of those IT areas where there is little new blood from younger IT staff members, they are quite adept at finding reasons why it won't work to serve their own ends.

    Not only that, but virtualization will result in lost jobs at some point. Many IT staffers are afraid, whether rightly or wrongly, of losing their jobs. In a sense, they are outsourcing a good chunk of their day-to-day duties. I remember when this particular company went to SAN's over the last half-decade, and you would have thought, from the way the Alpha guys were fighting it, that the world was ending. They created road-block after road-block about how they wouldn't be able to keep the systems running, how it wouldn't work in "their" environment, etc, etc.

    And, because of the compartmentalization that often occurs in large enterprise, many of these guys have very little idea about anything outside their own box. I know guys who have architected corporate platform migrations who are so narrow in their focus that they have *NO* experience outside their box, be it a particular OS, a server type, a network type, whatever. When the box becomes a cloud of equipment, they are lost and often have little or no ability to work with the other layers involved. Learning new troubleshooting skills in these environments is a painstaking process, and not one that many people are comfortable with.

    In the end, these various factors are creating far larger artificial roadblocks for implementing virtualization than any technical challenges. To top it off, much of this is being driven by financials. The CFO and CTO are desparately trying to find ways to cut costs. By the time this message percolates down to the workers, they feel threatened rather than empowered, and have little incentive (and generally no training, either) to be complicit in what they feel is a threat.

    Bill
  • [Virtualization] also asks IT experts from different realms to work more closely together.

    Oh yes, there will be blood.
  • Resource Scheduling (Score:3, Informative)

    by Detritus (11846) on Thursday January 03 2008, @02:40PM (#21899282) Homepage
    How do you ensure that the VM supervisor fairly and efficiently allocates resources to the VMs? The mainframe people put a great deal of work into this area. One badly behaved VM shouldn't be able to degrade the performance of the other VMs.
    • by TheRealFixer (552803) * on Thursday January 03 2008, @02:48PM (#21899402)
      VMware has multiple ways to balance and protect resources. You can set hard limits on VM resource utilization, ensuring that one machine can never take over a certain percentage of CPU, memory and even network bandwidth. VMs can also be given "shares", which determine priority over resources. In a contention for resources, the VM with the highest number shares is given immediate access to what it needs, with the lower share VMs splitting what's left over. This is the recommended way to handle it, as it gives you the best overall hardware utilization across your entire implementation.

      Starting in VI3, VMware also introduced the ability for VMs to migrate automatically across an entire farm of hosts, based on server load. In my experience, with very little tweaking, VMware does a very good job of fairly balancing resources.
  • by davidwr (791652) on Thursday January 03 2008, @02:40PM (#21899288) Homepage Journal
    This is a problem with management and/or the IT staff.

    Management should run the company in a way that cooperation is rewarded not punished. Consolidation to save money shouldn't result in harm to those who are making it happen or anyone else for that matter.

    The IT staff as well as all of the other employees and officers should have the attitude that if it's good for the company and not bad for anyone else it's the right thing to do.
  • At my job, we honestly don't have a valid reason to adopt virtualization right now. It'll actually cost us more money to accomplish the same job we're presently doing without it. But my boss wants to deploy it somehow only because it's one of the latest buzzwords. I guess it looks good to have some vm experience on my c.v. also ;-)
  • Well of course (Score:2, Insightful)

    by Anonymous Coward
    Yes, well, naturally the problem is us "peons" can't work together. It has nothing to do with the fact that our bosses don't have a fucking clue about how to use the technology.
  • Skirts the problem (Score:3, Insightful)

    by John Jamieson (890438) on Thursday January 03 2008, @02:54PM (#21899514)
    The problem is not that we don't want to work together. It is that you often cede control when you virtualize. And most of us don't love giving up control.

    With virtualization in some Corp's, you have to ask for another of the 32 processors, instead of just having the headroom all the time.(work that one through a buricratic organization, it can take months)
    Say you have a need to add another fax board(or whatever) to the virtualized x86 server, to find that they stuck some mission critical Virtual Environment on the Server and It CAN'T come down for another 2 weeks.

    Yep, it saves hardware, but multiplies headaches in some situations. It is no wonder some fear it.
    • by Cerberus7 (66071) on Thursday January 03 2008, @03:07PM (#21899698)
      Nobody should EVER virtualize a server that needs special hardware. EVER. Virtual servers should be reserved for the most generic of hardware requirements. Once you start bringing in fax boards you need a dedicated physical solution. If you want to test that kind of thing, go ahead and virtualize it, but the production box should be physical. I shudder to think of a virtualized firewall or router. Ouch.
      • Re: (Score:3, Interesting)

        I shudder to think of a virtualized firewall or router. Ouch.
        NetScreen firewalls have had virtualization capability for a long time. Cisco routers have virtualization via commands using the "vrf" parameter.
      • by blhack (921171) on Thursday January 03 2008, @03:32PM (#21900062)
        But the IBM commercial told me that i could replace my entire datacenter with a single server! Are you telling me that those two youngish looking racially diverse guys having a conversation at a coffee shop about sloshing hundreds of thousands of dollars worth of hardware around even though neither of them really seems to be sure what all of it does were LYING TO ME!?
    • Re: (Score:3, Interesting)

      That's just silly. Why would you put a physical fax card in your virtual server?

      Virtualize the fax card with iaxmodem, run it over a TCP connection to a serial port on a separate box, use t38modem with the other endpoint on a dedicated piece of Cisco hardware... there are plenty of other options.
    • Re: (Score:3, Informative)

      Say you have a need to add another fax board(or whatever) to the virtualized x86 server, to find that they stuck some mission critical Virtual Environment on the Server and It CAN'T come down for another 2 weeks.

      Aside from another poster's excellent point about not virtualizing servers that require specialized hardware, you're missing another point of the virtualized servers.

      In the case of VMWare ESX server, you'd use VMotion to solve this problem. Say you have a cluster of 3 or 4 physical servers running s
  • by Danathar (267989) on Thursday January 03 2008, @03:05PM (#21899672) Journal
    You want to watch a fight? Get the Windows Server sysadmins and the UNIX/LINUX sysadmins and ask each group which server OS should be the "Native" operating system under which the other runs....fun...
  • by lanner (107308) on Thursday January 03 2008, @03:13PM (#21899782) Homepage
    "when CIOs deploy a new technology"

    That could be your problem right there. When a specific technology or whoop-do-doo product is pushed from the top down, rather than the bottom up, it's a problem. That's not the same as management saying "Get this done", so much as it's "Use this fancy thingy I read about in the newspaper... who cares what it does or if there is something better, I'm the decider!"
  • by petes_PoV (912422) on Thursday January 03 2008, @03:22PM (#21899922)
    Just the same, political squabbles among IT staffers fighting for turf

    This is a classic sign of a broken IT department. One place I worked, if you (well, if I) needed to increase the size of a database table, I had to get sign-offs from

    • The database team - not unreasonable
    • the server team - it ran on their boxes
    • the storage team - they allocated the disk space
    • the network team - as the storage was NAS'd (bad idea!!!)
    • the backup/security team - or it wouldn't get backed up

    net result? nothing ever got agreed. The simplest changes took forever and cost a fortune. The operation is now outsourced.

    Who's to blame? Probably not the techies, they just pressed buttons. Quite likely the team-leaders for turning it political, definitely the IT managers who allowed the situation to continue.

    Who kept their jobs?
    yup, the managers! You've been warned: infighting only hurts the foot-soldiers, the generals aren't affected. Sort it out yourselves or you'll have to start learning chinese.

  • by Weaselmancer (533834) on Thursday January 03 2008, @04:07PM (#21900592)

    It's happened twice to me at two different companies.

    Whenever I need a machine scratch-pad, I boot up a VMWare machine. Test the software or do whatever I need to do and delete it. But while it's running, it broadcasts itself on the local net. Admins really freak out when a machine named //FAKEOUT or //BOGUS suddenly shows up on their net.

    I've given two different IT guys at two different companies cardiac events over it.

    Sorry, fellas.

    • I think that if you have the ability to reduce staff once you convert to virtual servers, you had too big of a staff to begin with. Whether you have 5 physical machines, or 1 physical with 5 virtuals, you still have 5 servers providing services, and you should have the appropriate number of staff members for that many servers.

      Companies are using virtualization as an excuse to do the kind of reorganization they should have done a couple of years ago. But, yes, make sure you're in charge of what pie remai
        • by blantonl (784786) on Thursday January 03 2008, @05:23PM (#21901812) Homepage

          With the physical machines, you have to worry about 5 sets of software failing and 5 sets of hardware failing. On the virtual setup, it's 5 sets of software and 1 set of hardware.
          On the contrary - I would argue that you have to worry about 5 sets of software failing, many sets of hardware failing, and one very important software component failing (virtualization software).

          Many large virtualized deployments include very advanced technologies such as shared SANs, shared infrastructure, and complex virtualization tools.

          Frankly, I would argue that you are probably just redeploying people resources into different roles and responsibilities, while probably saving on hardware and energy costs for the infrastructure through consolidation.
          • by toadlife (301863) on Thursday January 03 2008, @08:29PM (#21904096) Journal

            Many large virtualized deployments include very advanced technologies such as shared SANs, shared infrastructure, and complex virtualization tools.
            Correctomundo.

            We recently moved everything into virtua-land, complete with a hige SAN, fiberchannel switches, blade servers - the whole nine yards.

            While I do think the move was a net positive, the complication of 60 physical servers was more or less replaced by the complication of all the new SAN/Bladecenter components and their interdependency.

            One particular thing we've run into is "firmware hell", where you have several components in the chain that all require firmware updates and all depend on each other.
    • by Anonymous Coward on Thursday January 03 2008, @03:03PM (#21899650)
      An effect I've noticed many times is that when you ask IT staff to vote, the windows IT staff always outnumber the Unix and mac It staff. Thus one man one vote favors the windows firedrill fix-it jockeys over the more talented kernel of Unix and mac support gurus. Yes I realize that's ripe for flamebait, but it's actually true. By and large windows has so many problems to keep functioning it lakes a large staff of low paid trained monkies on hand. The revenge of the c-strudents is that they out number the A-students who run the linux servers.
    • Re: (Score:2, Informative)

      With HA and Clustering capabilities offered by many virtualization solutions you could end up taking a physical server and resources that weren't redundant and through consolidation efforts end up with more redundancy than before. It's all in how the solution is designed and knowing when to use virtualization and when not to use virtualization.
    • by TheRealFixer (552803) * on Thursday January 03 2008, @02:58PM (#21899576)
      Items that need to be redundant, should not be virtualized on shared hardware. I've heard people want to virtualize redundant instances of directory services, databases, proxy servers...etc. I call this the "putting all your eggs in one,central-point-of-failure, hardware basket".

      If you're doing something stupid like putting clusters or redundant servers on the same virtualization host, then I would agree. High availability loses it's meaning if all your nodes have a single point of failure.

      However, there's absolutely no reason you can't make your virtualization implementation highly available itself. Right now, I have clusters running in VMware VI3, that are running on separate hosts. Even with DRS, which balances all your VMs across an entire pool of servers, I can ensure that redundant servers and clusters don't end up running on the same piece of physical hardware. And when you add HA into the mix, you also provide a level of high availability to systems that you might not otherwise have been able to justify the expense on.