The Register® — Biting the hand that feeds IT

Feeds

Virtually developed

When you need it’s there and then it’s gone

  • print
  • alert

SaaS data loss: The problem you didn’t know you had

You know how these things happen. A representative from a customer is wheeled in by some major vendor to demonstrate the efficacy of their wondrous technology, while the assembled audience smile politely and pray for the coffee.

That’s what happened recently in Raleigh, North Carolina, where IBM was demonstrating the efficacy of its Blade servers, and Gregg Ferguson, Kilo Client manager at Network Appliance, had the job of showing it all in dynamic action.

Somnolence could then easily have come along in its allotted place, had it not been for the fact that a penny dropped with the realization that Kilo Client is actually rather clever and could have a direct interest for bigger applications development shops. There was also the point that Ferguson had recently rumbled this potential interest for himself.

Kilo Client has been developed over the last year by Network Appliances to fill a specific testing gap. The company makes large Storage Area Networks (SANs) amongst other things, and in order to run effective QA tests on such systems needs access to a lot of servers that can be reconfigured into target infrastructures as quickly as possible. The blade server solution was an obvious option to consider and, so long as there was a suitable management environment that could reconfigure servers quickly, an interesting twist on the test rig idea would be possible.

In essence, what the QA team ended up with was a 1,000 Blade system from which large SAN systems could be simulated for testing purposes – hence the Kilo Client name tag. Put simply, the team tells the sysadmin what they want – a stated number of servers running defined operating systems and applications, for two days starting next Tuesday – and admin configures the management environment to provide it. As the configured system is virtual, no new hardware needs to be bought, and once the job is completed it all slides back into the resource pool for subsequent re-use.

There are other factors here, such as the ability to save commonly used configurations for rapid re-use and the ability to boot the servers straight off the SAN, rather than from local disk drives. Groups of 252 servers – known, strangely, as `Poduals’ – share services and each is connected via 1 Gbit Ethernet to a single switch which has eight, 10 Gbit connections.

So you get the picture – very high bandwidth communications and very flexible infrastructure management, all designed for QA testing. The penny that dropped simply asked: “can this be used for applications development teams as well?” The answer – “hmmmm, well, yes. Nobody has asked yet, but yes it can,” spoke volumes.

Here is an infrastructural approach to the needs of applications developers that should be of great interest. Imagine: you realise the project you have been asked to complete (on time and under budget, naturally) needs several servers running processor A, running operating system B and with a list of hardware resources as long as your arm. These days that probably means you venture your neck taking a chit along to your boss – and a probable long wait as the star prize. Or you could email sysadmin with a resource provision request.

Gregg Ferguson would love to hear from development shops that could use a Podual or two as the bedrock of their development environments. It wouldn’t be cheap to start with, but it could give some shops a real edge in delivering the goods. ®

Steps to Take Before Choosing a Business Continuity Partner

Latest Comments

Virtual Development Setup

I suspect the takeup for this item will not be great.

Why? It's simple - developers are at the bottom of the food chain, especially as they are seen as an expense item, not an investment (by most shops).

Most places, and I've worked in a number, put their faith in more people and fewer systems. The potential productivity payoff for a big virtual development, and double that for a QA environment, is very hard to demonstrate on paper.

And therein lies the rub. In order to maximize productivity with a big virtual system, the system also needs to run some software that keeps the whole development process organized from inspiration to delivery.

It will require training, another expense, ongoing education, ditto, and run into the rock wall that is the mindset of most developers - resistance to change. Essentially "I already know how to program, so why do I have to learn this stuff?" attitude.

There will be exceptions, and those exceptions will slowly seed the mindset of developers with new ideas. Over time, say five years, the idea will gain strength *if* the first set of installs works well.

Yes, it could work. But I'd rather bet on the leading apprentice jockey to place than this revolution to succeed, because it really requires revoltionary changes in the developer environment and mindset.

BillN

0
0

More from The Register

SCO vs. IBM battle resumes over ownership of Unix
Zombie lawsuit back and wants to suck the brains out of Linux
 breaking news
You don't need phone lines or cable for ANYTHING, says Dish
The satellite-dish man can sort you out with phone and broadband over the air too
 breaking news
What's HP got under wraps? Looks awfully flash and tape shaped
What happens in Vegas won't stay there - we've got the details
Microsoft borks botnet takedown in Citadel snafu
Stupid Redmond kicked over our honeypots, wail white hats
IBM's $1bn layoffs latest: Now axe swings in US, Canada - reports
Union claims 121 storage bods canned after dismal sales
NetApp musters muscular cluster bluster for ONTAP busters
Storage array OS overhauled to juggle more nodes, go down on you, er, less
HP adds 'Haswell' Xeon E3s to entry ProLiant servers
Gussies up MicroServer for SMBs, adds baby switches