Missouri passes Bill creating Tax Exemptions for Data Centers

KY3 reports on Missouri passing a job creation bill that benefits data centers.

The bill also creates state and local sales and use tax exemptions for new and expanding data centers and permits donation lease agreements between municipalities and data center projects

The government document is here.

DATA CENTERS

The act authorizes state and local sales and use tax exemptions for new and expanding data centers and permits donation lease agreements between municipalities and data center projects.

This is good news for the Grass Fed Data Center folks in Missouri who are championing a biomass Green Data Center effort.

Blogging vs. Editorial Process, speed & quantity vs. quality

i have spent a bunch of time in the Publishing Industry, and remember in 1986 using Aldus Pagemaker 1.0 on a Mac.  Companies that were in my regular discussions were Altsys, Macromedia, Quark, Adobe, and a bunch of other high end publishing & printing technologies.  In 1994 I was a renegade and developed Verdana as the first TrueType font where screen readability was the priority, not print.  Leaving behind print changes what you can do.  Being a blogger is different than print as you focus on speed & quantity vs. quality.

What happens when you leave behind the Print Editorial Process?  Businessweek has a good post on Blogs vs. Magazine processes.

We're proud here of the work we do as a team to lift the level of each story. But what a slog. It's unthinkable for the blog world. Consider the path of a story as it winds its way through our system.

I looked at a draft of the story over the weekend, suggested changes, and spent nine hours editing it yesterday. (Usually two people share this job, but this week we're short-handed.) Then I sent it to the copy desk. There, people who are new to the story read it to see if it makes sense, if the thinking is logical, the context clear, the grammar and spelling ok, the names and titles correct. Meantime, some facts, such as names and Web addresses, are checked by a researcher. The copy desk sends the story, with questions, back to the writer and me. At the same time, the top editors of the magazine have a chance to read the story and suggest changes of their own. Potentially contentious or delicate stories are often sent upstairs to a McGraw-Hill lawyer, who might suggest further adjustments.

Today we work answering the questions, clearing up doubts, filling in holes, and cutting the story to fit on the page.

Then, wouldn't you know, the story goes back to the desk. They edit again--mostly proofreading, making sure questions have been answered, and writing display language this time around--and put it on a literal sheet of paper. Then that paper is circulated back to us. We read it and make fixes, and then carry it to the close desk, where editors make the final changes and push the button to send it to the printing press.

Much of this process is a good idea when you are thinking sending content to a printer.  But, what about a blog post?  Note this post was written in 2005, and describes a blog process.

The editorial process of blogging is far simpler. We write, we publish. This takes our journalism into a new sphere, but carries inherent risks. How do we handle them? First, we reduce risk by avoiding the sorts of stories that require heavy editing. We don't blog investigative pieces, for example, or heavy financial analysis. Second, we consult our gut. If it looks risky, we'll push it toward the more edited BW Online or the magazine. Finally, when we make mistakes--which we do--we aim to correct them quickly and ask for your understanding. We're into something new, and all of us, you and I, are only coming to understand it as we create it.

Much of the editorial process was constrained by the print process.  Blogging is constrained by speed of internet and data center software.  Quality is important, but do end users care about the intangible qualities.

Much of what gets the traffic is the fastest most relevant, and it is hard to beat that with better quality that is later, and shows up days later.

 

Facebook partners with Open Data Center Alliance to contribute Server and Data Center Designs

Facebook Open Computer Project and Open Data Center Alliance announced a partnership at Intel Developer Forum.

INTEL DEVELOPER FORUM, San Francisco, Sept. 13, 2011 – The Open Data Center Alliance (ODCA) today announced a collaboration with the Open Compute Project (OCP) on system and data center specifications to drive adoption of efficient data center and infrastructure design; spur rapid hardware innovation; and encourage greater openness and industry collaboration.

When I received the press release I let the PR firm know I was at Intel Developer Forum (IDF), and I could talk to the ODCA executive.  I received a call in 3 minutes and said they had a slot in 25 minutes.  I went upstairs and there was ODCA Board of Director’s Chairman, Marvin Wheeler, and Frank Frankovsky, a founding member of the Open Compute Project and director of technical operations at Facebook.

image

It feels like I have a reoccurring meeting to run into Frank – OCP summit in Palo Alto, GigaOm Structure in SF, IDF in SF, and OCP in NYC.  So, it was easy to quickly get down to what the partnership  is delivering.  If you look at ODCA models.

image

You may notice there is no server or data center models.  As ODCA is focused on the cloud.

We envision an IT industry that gives both users and suppliers a simpler, more secure, more efficient path to cloud computing.

With many people thinking of private clouds as well as public clouds, it would make sense for there to be a reference point to compare public clouds vs. private clouds.  Whose hardware would you use to build a private cloud that is willing to open source its designs?  This is where Facebook’s Open Compute Project fills a need, grounding the cloud to the reality of implementation on server hardware in a real data center.

Everyone has full access to these specifications. We want you to tell us where we didn’t get it right and suggest how we could improve. And opening the technology means the community will make advances that we wouldn’t have discovered if we had kept it secret.

Server Technology

Open Compute servers are designed to be efficient, inexpensive and easy to service. They’re also vanity free, with no extra plastic and significantly fewer parts than traditional servers.

Data Center Technology

Designed in tandem with our servers, the data center maximizes mechanical performance and thermal and electrical efficiency. It accepts 277 volts of AC, so more energy makes it from the grid to the data center to server components.

Both OCP and ODCA have  an end user focused leadership and take an open source approach which makes for a natural partnership between the organizations.  ODCA will present at the OCP event in NYC.

Members of both organizations are engaging in joint projects initially focused on rack-scale infrastructure; ultra-efficient server and storage designs; and scalable, open systems management. Additional details on these projects will be announced at the OCP Summit on October 27.

Facebook Open Compute Summit NYC registration is open

If you are interested in Facebook’s Open Compute Summit in NYC registration is now open.

Open Compute Summit: October 27, Skylight West, New York City

Thanks for your interest in the second Open Compute Summit. The nascent Open Compute community is actively seeking participants who are passionate about making strong technical contributions to defining and delivering the most efficient server, storage and data center designs. We will have executives share the latest and greatest thoughts and innovations, and a number of community-participation sessions. We will be providing more details of the event schedule in the coming weeks.

Location

Map

Skylight West

500 West 36th Street
New York, NY 10018