US Government Begins Largest IT Consolidation in History
miller60 writes "Saying 1,100 data centers is too many, the federal government has begun what looms as the largest IT consolidation in history. Federal CIO Vivek Kundra has directed federal agencies to inventory their assets by April 30 and prepare a plan to reduce the number of servers and data centers, with a focus on slashing energy costs (full memo). Kundra says some applications may be shifted to cloud computing platforms customized for government use."
I predict a rash of job openings that you can get hired for provided you can spell "Cloud Computing"
[signature]
Dinner is served! Please approach the money trough in an orderly line...
See, the last time we upgraded we put everything on eleven hundred windows 95 machines with 1 gig hard drives. That did pretty good for a spell, all things considered. Now we're thinking about one of them pointy computers... whaddya call em? Blade servers? Yeah, we hear good things about those.
This being a government IT project, I predict it will take 5 years longer than planned, cost 10x the initial budget, and still never really work quite right.
Finally, IT is on its way to being considered a commodity, as it should. There's no reason for every organization to maintain their own IT infrastructure any more than there's reason for every organization to maintain their own electricity generation and distribution. Of course, the hordes of IT people won't be happy, as the number of It jobs will continue to fall precipitously, but such is life. Because everybody has access to relatively significant computing power, society as a whole gets to reap the rewards, as opposed to 20 years ago, when only the largest organizations had the money and the manpower to maintain an IT network of any kind.
I don't respond to AC's.
If Virginia's IT overhaul is any indication, this is going to be a slow-motion cluster of a mess for the next 10-20 years
Every business I've ever worked for has had that one dusty 8086 off in a corner. It would run a single batch file every few hours. No one would touch it, because no one knew what it did-- just that whatever it did do was mission critical.
Thus, the US government should just consolidate everything down to a single batch program run by a 8086. I'm sure there's a spare closet in the White House or something they can use as a server room.
UTF-8: There and Back Again
Oh, Vivek, what brilliant thing will you think of next? How much energy will it take to replace all of these server farms? How much energy will be required for the taxpayers to earn the money necessary to pay for it? What about security concerns of consolidating all of this data?
I think Vivek wants to make himself look useful after being exposed as a fraud by John C. Dvorak. http://www.dvorak.org/blog/2009/08/12/special-report-is-us-chief-information-officer-cio-vivek-kundra-a-phony/
I work for a government project in a Federally funded building right now and all I can say is... it sound promising. Common sense, proper planning and innovation gets put on the back burner for under-estimated budgets, bad trade studies, botched planning and wrong decisions being made by the wrong people. In the end, everything will still be money driven and the stove-pipe approach to IT infrastructure will remain the same: everyone will take their OWN budgeted money and set up their OWN infrastructure that will be completely different than project-A over project-B, so you'd spend double that to consolidate it. If you want to use some of project-A's setup (e.g. authentication, storage, ect.) because mis-managed budgets being a huge concern, project-B will get quoted a ridiculous amount of money to jump aboard to do it; much more, in-fact, than it would take to do a trade study, setup of a proof-of-concept test, purchase what you need and implement it. Thus that's how stove-piped approaches become what they are: a mess.
Didn't read the article, but my experience with government entities is that they receive a specific value of funding each year to spend on gear, training, energy costs, etc.
The nature of the funding goes that if you don't use all of it this year, you get a reduced amount next year. Now this may seem logical -- it may seem like a policy that governs spending. Instead what it is is a policy that drives UNNECESSARY SPENDING.
The places I have been were frugal but appropriate in their spending throughout the year. As the funding for the year would approach a close (in October), all-of-a-sudden the leadership would start spending money like crazy because they had a large surplus. Money would be spent on things that were not actually necessary; if they were necessary, why not get them at any other time during the year?
In several cases, seeing this strange frenzy of spending I would ask the leadership what was going on. They explained the 'use it or lose it' policy and that in order to maintain the funding they got this year, for next year, they *must* spend it all. I was in conflict because I was taught integrity/honesty and there is no integrity in spending up dads helpful money on worthless junk so as to appear that you still have 'need'.
------
The reason I bring this up is because I am curious if the units that will save money via IT consolidation will actually save us money or if they will be (by obvious standing procedure) driven to spend it in pointless/needless ways.
Discuss? Anyone else experience this?
Now just wait for a data center to be scheduled to close in some Congressman's home district and see how big of a block is put into place.
III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIII
I have no problem with the CONCEPT of consolidation, but Virginia's IT outsourcing/consolidation project to Northrup Grumman happened on Kundra's watch. It is an unmitigated disaster.
Years into it, there's not even a complete inventory of the systems that NG is supposed to be managing for the Commonwealth, and at least as of a few months ago, NG couldn't even produce an invoice for the Commonwealth to pay that had more than six or eight line items on it.
I sat through a special meeting of the House Committee on Science and Technology on the issue a few months ago, and the legislature is NOT happy about the situation. Privately, you will hear from them words like "gross negligence" to "I'm convinced it's corruption". The Delegates who engineered the legislation enabling the IT outsourcing are especially pissed.
No disrespect to Kundra, but I don't think he's the right guy to oversee it.
To run a sovereign state, it is necessary for all systems to be based on free software and to be run on public infrastructure. That means no privately hosted cloud computing and no proprietary software. How else are we to ever find out how our government is run?
This is no joke. I work at one of the biggest government data centers, and we consider Google to be alternately either our best friend or the people who will put us out of business. Google is our biggest domestic consumer -- I think they've already sucked down all the data we have here on site. I could easily see them positioning themselves to take over the ingesting and archiving responsibilities.
Google likely already has a copy of all the nonclassified data that the government is holding. The only people with more appetite for data are the Chinese. If the government decides to outsource data centers, that's where they'll be going.
Genocide Man -- Life is funny. Death is funnier. Mass murder can be hilarious.
4 8 15 16 23 42
Wow. I definitely can't think of any potential downsides to putting a military entity, with a strong history of not always sticking to its legal role of foreign intelligence gathering, in charge of all IT for our ostensibly civilian government...
Because IT is a pretty damn banal subject, your proposal doesn't elicit the visceral distaste that "Hey, we should let the army take over policing. The army has 1) mad combat skillz 2) massive firepower and 3) the security chops to actually keep the streets safe."; but it is basically in the same class.
I've actually done a lot of smaller server consolidation projects. In most cases, the results are great...those lonely database and file servers that get hits 5 or 6 times a day are all combined into one big box that actually uses all the hardware capacity.
The biggest problems I've seen with VMs are the project managers who treat it as magic, never-ending capacity. The new favorite phrase in IT project management circles seems to be, "Oh, we'll just build a VM for it." Problem is, unless someone else is hosting your data center, you can't just call up and order more capacity without paying for more hardware.
Second-biggest with a consolidation like this is incomplete requirements. Lowest-bidder contractors are not going to do a good job of gathering every single requirement...even high-bidder contractors have problems with this. And the problem is that the more they miss, the worse the fallout. A certain large company I used to work for found this out the hard way moving their inhouse data center to one of the big IT services companies. I'm a systems guy, and had all my stuff well documented. Others were pissed off they were losing their jobs and intentionally withheld information...the contractors didn't follow up, and a lot of last minute scrambling had to be done to complete the migration.
Third problem for a government IT consolidation? Some huge services company like Accenture or IBM is going to win the bid and staff the project with dumbasses they pulled off the street in order to maximize profits. (Yes, this happened in my case in point #2 above...the sales staff presented the A Squad and swapped them out as soon as the contract was signed.) Not that government employees are rockstars, but they at least have a vested interest in keeping the data safe. IBM will probably win the contract too, given their involvement with government systems already. IBM has been so India-happy over the last ten years that I wouldn't be surprised if a lot of the (non security critical) work ends up there.
Just like PMs treat VMs as magic hardware, CIOs treat outsourcers as magic black boxes that flawlessly run their IT operations. Unfortunately, the reality is not as sunny beneath the surface!
We've been consolidating for the last few years in the Air Force. Needless to say the whole experience has been on par with getting punched in the face everyday. The concept of cloud computing works great until you realize that you have to pay for all that bandwidth when people actually want to use there computers for something other than email and a few web based portals.
Their solution has been to disable just about every usefull function since data transfer is no longer hopping a free ride across the base network. That combined with the fact that when the network at our primary factility goes down so does everyone else's since those oh so lovely portals that link us to everything else are only served up there.
The concept of cloud computing looks great on paper and actually does work for really light applications such as email, but who ever thought that converting everything including locally shared data over to the cloud (cloud served but still restricted to local access??!!) should be forced to lick the toilets in every office, just after lunch time while they are still warmed, in every office they've inflicted this crap upon.
Nixon took us off the gold standard during the Civil War? http://en.wikipedia.org/wiki/Gold_standard#Suspension_of_the_gold_standard
THAT BASTARD!
Don't you know yourself no history? He did it during the Great Depression!
family farms dying
Please. Family farms started dying around the end of the 19th century, when mechanization started to make operating a farm a business rather than a family pastime. Various forms of farm subsidies managed to stave off the inevitable decline of "pa and his sons working the farm" for quite some time, but by the 70's, the ride was just plain fucking over. Seriously, in this day of GPS guided multi-hundred-thousand dollar combine harvesters, there simply ain't no efficient way to operate a "family farm". The reason we have all the agri-business corps running giant farms is that technology has allowed tremendous economies of scale. There are a number of families that still manage to run small businesses based on farming, but that's because they run them as businesses. Most of them don't even live on the land they farm anymore, because there's no advantage to living on site when all you are is a manager and your kids don't work on the farm. The quaint notion of a man making a living hitching a plow to an ox while his wife sows behind him is ancient history.
If a job's not worth doing, it's not worth doing right.