US Gov't Data Centers to focus on being Efficient after closing down the excess capacity

NextGov has a post on the next move by the US Federal Gov't to create new metrics to asses the efficiency of remaining data centers after closing many.

The Office of Management and Budget wants to focus less on simply closing federal data centers and more on making sure the government’s existing data center stock is operating as efficiently as possible, an OMB official said Thursday.

That’s why federal Chief Information Officer Steven VanRoekel’s office plans to roll its three-year-old data center consolidation initiative into a separate program called PortfolioStat, which audits agencies’ commodity information technology budgets to root out waste and inefficiencies, said OMB Portfolio Manager Scott Renda, who works in VanRoekel’s office.

The strategy is to focus on metrics.

“You’re going to see more focus on the right kind of metrics, efficiency metrics” Renda said. “[We’ll be] thinking about PUE [an energy measurement], thinking about storage, thinking about density measures that really talk to how efficient your infrastructure is. The goal with PortfolioStat is an efficient infrastructure that’s serving the mission of the agency. Consolidation is done to support that program and mission.”

This is a strategy that probably got the consensus of many of the IT decision makers and the vendors who do a lot of consulting for these people.  Don't ever think a big move like this is not done without a vendor helping to say "yeh this is a great way to make you more efficient."  Meanwhile they are figuring out the initiatives that will replace the legacy systems and upgrade them to the latest technology.

Notice the idea is focused on metrics to make a more efficient infrastructure. 

If it was up to me, I would focus on the supply chain of who are the best performing vendors and where are the quality issues that cause huge wastes.  Then determine the metrics that support the monitoring of quality of the system including the quality of the vendors.

But, I don't do any federal gov't work and my partners have no desire to slow ourselves down by adding federal as a market segment.

The problem with metrics is it can take you down the wrong path.  

Much like the work that John Boyd to fight the bureaucracy in Washington that was building faster fighter jets and he was telling people no, you want jets that are more maneuverable.  The ability to change direction, add speed, dump speed is what wins.  The trouble is there were no metrics for that.  And the vendors liked a nice easy if it goes faster with less fuel then it is better approach.

Doesn't it kind of make sense that you want a more maneuverable infrastructure vs. an efficient metric driven machine?

Two different ways to attend SXSW

Last year a group of data center guys and I went to SXSW for the first time.  CNET News has a post on their recommendation which I'll highlight and then give you a different way.

How to win at SXSW -- and live to brag about it

CNET reporter Daniel Terdiman has been going to South by Southwest for years. When a friend asked for advice on how to get the most out of SXSW, he had plenty of suggestions.

...

So where to begin? A lot of people will tell you to RSVP for everything you get invited to. That's sound advice, because there's a million things going on during SXSW -- parties, panels, special events, bar-b-ques, meetups, and so forth -- and you don't even stand a chance at getting into many of them if you don't RSVP.

...

If you do decide to go to big parties, be prepared to wait in line for an hour, often even if you have a VIP wristband. Once in, you're going to be crammed into a bar, or a club, or a restaurant, it's going to be too loud to talk, and you'll have to wait in line again for a drink. That's fun?

...

People think SXSW is mostly about the parties, but a lot of folks have forgotten that there's amazing panels, keynotes, and discussions on the schedule. Bre Pettis, the CEO of MakerBot is keynoting, and so is Elon Musk, CEO of both SpaceX and Tesla. Al Gore's talking, and so is Neil Gaiman. How great is that?

...

People will tell you to take a night off, since SXSW is so intense. My approach is a little different: Dive in full-force every day and night you're there. But let yourself sleep in if you need to. Do not -- and I mean this with all my heart -- make plans for earlier than 10 a.m. You'll just be too tired. Because if you go to bed early at SXSW, you're definitely doing it wrong.

We did things a different way, and had a blast going to great parties, meeting great people, seeing some good bands.  Oh yeh, and had some great data center discussions.

First we rented a house 3 miles out of town.  We didn't register for the conference.  We contacted people and said hey were in town for SXSW want to come over to our house to chat.  People came over, relaxed in the backyard. They told us parties we should go to and they'll get us in. Invited a few other people who had been at the conference, let them give us an update of what was interesting.  Heard about more parties.  Went out for the evening.  Stayed out late.  Slept in, then did the same thing the next day.

Didn't wait in lines.  Which means we missed talking to random people standing in line.  That was kind of fine for us given we had very low expectations of running into data center people randomly. 

How does this work?  You have to have the right people in the house that people want to come over and chat with.  Oh yeh, and two of the guys were Texan natives who now live on the coasts which means they know a lot of people in Texas that helped the networking.

We wanted to go again this year, but we're all too busy now.  People were disappointed we weren't going back this year.  We'll try to go next year.

 

Saving Server RAM power using Mobile DRAM

Wired has an article on being more energy efficient in the data center using mobile DRAM.  What few people know is RAM is a top energy consumer in servers after the processors.  More than HD for many servers that are meant for memory intensive applications.

Over the past decade, the very concept of the server has evolved. Once, servers were giant machines jam-packed with processors and memory that focused on processing speed above all else. But nowadays, most servers are smaller and cheaper, and they consume less power. Services like Google Search and Microsoft Bing run on thousands of commodity machines, not the big beefy database servers hawked by companies like Oracle. When you’re serving millions of people across the globe, you can’t afford those power-hungry machines.

Here is the paper referenced in the wired article.

NewImage

Why I write, why do you?

I write this blog to ingrain ideas into my memory.  In the process of writing over 3,000 posts, I've learned a lot.  If I forget I can run a search on this blog. :-)

I don't look at the comments for feedback which is why many say it is good to blog.  What I do find quite useful with my blog is it speeds up the conversations I have with my friends who regularly read what I post.  Olivier Sanche was a great example and others from his teams.  At first it would be confusing to me, but after awhile it was amazing what we could cover in 15 minutes as we bounced over 10 different topics.  Part of the problem is they would remember my posts better than I would as I would tend to write then flush the idea and move on.

What is interesting to observe is why people write.  So many people think writing are facts.  Writing is simply words in a language.  You need to know the context of the author to know how to interpret their writing. George Orwell has an essay on "Why I write."

In the beginning he tells his childhood story.

NewImage

I was the middle child of three, but there was a gap of five years on 
either side, and I barely saw my father before I was eight. For this and 
other reasons I was somewhat lonely, and I soon developed disagreeable 
mannerisms which made me unpopular throughout my schooldays. I had the 
lonely child's habit of making up stories and holding conversations with 
imaginary persons, and I think from the very start my literary ambitions 
were mixed up with the feeling of being isolated and undervalued.

...

Then Orwell makes his point.

I give all this background information because I do not think one can 
assess a writer's motives without knowing something of his early 
development.

and the great observation.

he will have acquired an emotional 
attitude from which he will never completely escape.

Which then flows into the 4 reasons to write besides money.  I am more of the 3rd category, historical impulse.

Putting aside the need to earn a living, I think there are four great motives for 
writing, at any rate for writing prose. They exist in different degrees 
in every writer, and in any one writer the proportions will vary from 
time to time, according to the atmosphere in which he is living. They 
are: 

(i) Sheer egoism. Desire to seem clever, to be talked about, to be 
remembered after death, to get your own back on the grown-ups who snubbed 
you in childhood, etc., etc. It is humbug to pretend this is not a 
motive, and a strong one. Writers share this characteristic with 
scientists, artists, politicians, lawyers, soldiers, successful 
businessmen--in short, with the whole top crust of humanity. The great 
mass of human beings are not acutely selfish. After the age of about 
thirty they almost abandon the sense of being individuals at all--and 
live chiefly for others, or are simply smothered under drudgery. But 
there is also the minority of gifted, willful people who are determined 
to live their own lives to the end, and writers belong in this class. 
Serious writers, I should say, are on the whole more vain and 
self-centered than journalists, though less interested in money. 

(ii) Aesthetic enthusiasm. Perception of beauty in the external world, 
or, on the other hand, in words and their right arrangement. Pleasure in 
the impact of one sound on another, in the firmness of good prose or the 
rhythm of a good story. Desire to share an experience which one feels is 
valuable and ought not to be missed. The aesthetic motive is very feeble 
in a lot of writers, but even a pamphleteer or writer of textbooks will 
have pet words and phrases which appeal to him for non-utilitarian 
reasons; or he may feel strongly about typography, width of margins, etc. 
Above the level of a railway guide, no book is quite free from aesthetic 
considerations. 

(iii) Historical impulse. Desire to see things as they are, to find out 
true facts and store them up for the use of posterity. 

(iv) Political purpose.--Using the word 'political' in the widest 
possible sense. Desire to push the world in a certain direction, to alter 
other peoples' idea of the kind of society that they should strive after. 
Once again, no book is genuinely free from political bias. The opinion 
that art should have nothing to do with politics is itself a political 
attitude. 

Many of you who live in a corporate environment spend your time writing in #4, Political Purpose.

One of the zingers is Orwell's comment on writers.

All writers are vain, selfish, and lazy, and at the very bottom of their motives there lies a 
mystery.

But, keep in mind all of us write to some degree.  Your e-mails, tweets, Facebook posts are all writing.  Can you even say your instagram posts are a kind of visual writing?

I think about why I write.  Why do you write?

Tip for IT to control the cloud, don't control it, get data

I was on a webinar yesterday to discuss the best route to the cloud.  One of the last questions was 

NewImage

The day before I had a conversation with Luke Kanies, CEO of Puppetlabs to catch up.  I was introduced by a mutual friend a couple of years ago, and we have had always had great discussions.

I told Luke I was participating in a webinar on the cloud and it would seem like a tool like Puppet Enterprise could be used to get the data on what clouds are being built and deployed.

Puppet Enterprise is IT automation software that gives system administrators the power to easily automate repetitive tasks, quickly deploy critical applications, and proactively manage infrastructure changes, on-premise or in the cloud. Learn more about Puppet Enterprise below, or download now and manage up to 10 nodes free.

Download Free

Puppet Enterprise automates tasks at any stage of the IT infrastructure lifecycle, including:

  • Provisioning
  • Discovery
  • OS & App Configuration Management
  • Build & Release Management
  • Patch Management
  • Infrastructure Audit & Compliance

I didn't specifically mention Puppetlabs, but I made the point that the biggest step taken to take control of the cloud is to get data. Data from the deployment tools.  If central IT bought a tool that helped all the users, then they could get the data.

If Puppet Enterprise logs were sent to a central IT function they would have the data to determine what the users are doing in the cloud.  With the data you can determine how best to serve the needs.

This recommendation flies in the face of what I think of what 80% of the people would do which is to just take control.  This makes sense as these same 80% of the people would have no idea what a puppet enterprise log means.

I constantly tell people the misperception of corporate IT is it is technical organization.  No, IT is not necessarily technical.  Take a look around how many of these people are CS degrees, let alone MS or PhD.  What is technical?  Google, Apple, Facebook, Microsoft product development teams are technical.  PuppetLabs is also technical, and they have a good method to manage the IT infrastructure.

How Puppet Works

Puppet uses a declarative, model-based approach to IT automation.

  1. Define the desired state of the infrastructure’s configuration using Puppet’s declarative configuration language.
  2. Simulate configuration changes before enforcing them.
  3. Enforce the deployed desired state automatically, correcting any configuration drift.
  4. Report on the differences between actual and desired states and any changes made enforcing the desired state.

Which reminds me one of the things I enjoy talking to Luke and why another Portland friend introduced us is we both like the use of Models.

Enforce Desired State

After you deploy your configuration modules, the Puppet Agent on each node communicates regularly with the Puppet Master server to automatically enforce the desired states of the nodes.

  1. The Puppet Agent on the node sends Facts, or data about its state, to the Puppet Master server.
  2. Using the Facts, the Puppet Master server compiles a Catalog, or detailed data about how the node should be configured, and sends this back to the Puppet Agent.
  3. After making any changes to return to the desired state (or, in “no-op mode,” simply simulating these changes), the Puppet Agent sends a complete Report back to the Puppet Master.
  4. The Reports are fully accessible via open APIs for integration with other IT systems.

Uh, BTW, this is the way I think a data center should work as well.