Second guest post written by my partner in crime, Dicky Donaldson. Running with team always makes a Spartan race more fun. When that team is your family, it is something even more special and memo…
I am so excited to introduce my first guest blogger, Doug, a newbie who’s Spartan cherry (along with our two other eBay teammates, Kevin and Sourya) Richard and I had the honor of popping (so…
eBay is busy building some of the world’s most-efficient data centers, and its efforts aren’t just show. The company has figured out a way to tie its computing infrastructure to specific business concerns and plans to continuously tweak its operations to meet top-level mandates. On Tuesday, eBay released a whitepaper describing how it accomplished this and laying out a framework for companies that want to do the same.
Dean Nelson, eBay’s vice president of Global Foundation Services, says the effort, called the Digital Service Efficiency report, “is the miles per gallon measure for technical infrastructure for eBay.” Essentially, the company has boiled its business down to a single currency — transactions (specifically URL requests) associated with users’ buying and selling on the site — and created a slew of metrics that measure how efficiently it delivers those transactions in terms of revenue, performance, cost and carbon footprint.
The project has…
View original post 798 more words
While not earth shattering, I suspect that many people who are in the business of managing internet infrastructure have long sought to holistically manage this infrastructure and searched for a set of common best practices. There is ITIL & ITSM which are really GREAT models to start from, yet seem a bit incomplete as per managing, specifically, interne infrastructure – built on the three pillars of Datacenters, Server (including storage), and Networks – as a “business”. Then there is traditional ERP best practices, yet again, ERP is not exactly a perfect fit either as it is too broad – so why pound the square peg thru the round hole then? Why not take the best of all of those three and call it Infrastructure Resource Planning (IRP)?
My own evolution has brought me to where I am in that very function – managing the business aspects of enterprise internet infrastructure – and as such, have begun to plan out the entire lifecycle of that infrastructure from procurement thru end of life/disposition and everything in between…including the very notion of shared services charge back models, which is why IRP is so analogous to ERP but not exactly the same thing.
ERP, as per wikipedia, is defined as the following:
“Enterprise resource planning (ERP) systems integrate internal and external management information across an entire organization—embracing finance/accounting, manufacturing, sales and service,customer relationship management, etc. ERP systems automate this activity with an integrated software application. The purpose of ERP is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders.” – overall, this sounds a lot like evolving infrastructure management best practices inside enterprises, yet the twist is that while ERP is generalized to suit all businesses, IRP would emphasize the underlying interent infrastructure that a business runs upon today and manage it accordingly.
ITIL is a GREAT framework to follow for infrastructure mgmt that is predicated upon 30yrs of evolution and primarily focused on IT services, which are traditionally centered around the “desktop”. “ITIL advocates that IT services must be aligned to the needs of the business and underpin the core business processes. It provides guidance to organizations on how to use IT as a tool to facilitate business change, transformation and growth.
The ITIL best practices are currently detailed within five core publications which provide a systematic and professional approach to the management of IT services, enabling organizations to deliver appropriate services and continually ensure they are meeting business goals and delivering benefits.”
However, ITIL doesn’t quite cover the infrastructure optimization of core datacenters, servers, and switches/routers specifically enough, as my own experience has yielded that a key component of IRP that differentiates itself from ITIL is that engineering research and development are requirements to optimize, holistically, the three pillars of internet infrastructure: Datacenters, Servers (including storage), and Networks.
Then, finally, there is ITSM. ITSM is itself a process based framework much like ITIL, however, ITSM is not attributed to any one person or organization (ITIL is trademarked by the UK Cabinet office). “ITSM is generally concerned with the “back office” or operational concerns of information technology management (sometimes known as operations architecture), and not with technology development.” This notion of a management framework, again, is a GREAT start, however, the fact that it is not interested in tech development is where it falls short and IRP picks it up.
The idea of infrastructure R&D is the KEY differentiator of IRP form ITIL, ITSM, and ERP. IRP is very much a large enterprise concept that does not disassociate itself from advancing the underlying technology; it embraces it as a way in which to drive ever more contribution to businesses’ bottom lines.
IRP is relevant today as businesses have scaled and evolved such that we are near a point where applications can be separated from direct relationships with internet infrastructure. From the moment virtualization commenced, we have been trying to allow apps to live anywhere, anytime on a cohesively managed infrastructure. When that infrastructure can be managed as a system onto itself is when IRP becomes relevant.
IRP is not a radical movement nor is it an earth shattering concept. It is a concept however, that is begging to be recognized as we further advance the separation of apps being directly tied to the underlying infrastructure. Then we can plan, manage, and tune that infrastructure as a system which is why technology advancement is a key component of IRP and where ITIL & ITSM fall just a bit short. Thus, IRP as a concept is timely and needed to truly get a hold of your internet infrastructure from supply chain to management and monitoring to refresh cycles to research and development all thru the lens of optimizing the underlying business value proposition.
PS – stay tuned as there is an emerging metric which will be able to tie IRP all together – it will be made public in the next month.
Ever since the Internet took off, those who have been managing the infrastructure have been laser focused on optimizing each and every part of the “stack” leading up to and stopping short of the application (another post on this one as that is about to change!!!). In so doing this, the largest of players have tuned their datacenter energy consumption thru quantification via Power Utilization Effectiveness/Efficiency (PUE), have sought to push the HW vendors to tune the servers we deploy in the datacenters via efforts like Open Compute Project (just attended recent event), and the industry has more robust contribution to the ever evolving set(s) of industry mgmt standards that are common across MOST infrastructure teams (see ITILv3.0).
What is not, however, all that common is an over-arching view (process map) to tie this universe from end to end – DCIM adoption has been slow due to not only this lack of cohesive visibility but also to advance our abilities to even further tune the “infrastructure engine”, we need to begin to holistically look at infrastructure the way in which manufactures have long done via Enterprise Resource Planning – I posit, we need to adopt Infrastructure Resource Planning (IRP) as a way in which to advance the concepts of ITIL + ITSM + DCIM + (soon to be published, new metric!!).
Spot on article – well written and good perspective!
When I founded my own startup, I thought I knew what I was getting into: after all, I had been a senior manager at eBay (s EBAY), managing director at Gumtree and chief operating officer at Zoopla. But since starting Adzuna in 2011, I’ve realized that being a founder can be very, very different. Here are some things I’ve learned in the past two years.
Learning to sell
As a finance guy who became a general manager, I’ve always been driven by strategy, product and marketing, and never valued sales. Sales was something I looked down on — a commodity role staffed by poorly qualified “liars for hire”, something you didn’t need if you had good product and marketing, or a necessary evil to get the word out.
As a founder, I sell every day, to investors, to staff, to the government, but also to customers, so that we can…
View original post 851 more words
I’d been holding out a bit on writing this as it really is a synthesis of ideas (aren’t they all) with special mention of dialogue with Jeffrey Papen of Peak Hosting (www.peakwebhosting.com)…
I’ve been collaborating and speaking extensively with Jeffrey on the next phase of “hosting” since we are now moving beyond the hype cycle of “Cloud Computing” (see previous post on “The end of the Cloud Era”). The community at large (and people in general) love the idea of simple, bite sized “solutions” with pithy and “sexy” naming conventions (think <30sec sound bites) and that was the promise/expectation around “the cloud” as it was popularized – a magic all in one solution whereby you just add applications and the “cloud” will do the rest. Yet, the promise never quite met expectations as the “cloud” really ended up being an open standards evolution of “virtualization” – nothing wrong with that, just not the “all in one” solution that people really wanted the cloud to be (ps – all in one refers to the aforementioned of applications just being pushed thru APIs to the “cloud” and the “cloud” manages all underlying resources).
So, as the Cloud Hype dissipates (love the metaphor), we are sorta back to the same basic elements that make up Infrastructure – Datacetners, Compute (IT), Communications (switches/routers), Software that manages it all (virtualization, cloud, etc), all accessible thru the to be built APIs. Put another way, we are coming full circle and back to centralized, on-demand computing that needs one more element to make it all work – Subject Matter Experts (SMEs).
I was inspired to write this today when I saw this post from Hitachi: http://www.computerworld.com/s/article/9226920/Hitachi_launches_all_in_one_data_center_service – “Japanese conglomerate Hitachi on Monday launched a new data center business that includes everything from planning to construction to IT support. Hitachi said its new “GNEXT Facility & IT Management Service” will cover consulting on environmental and security issues, procurement and installation of power, cooling and security systems, and ongoing hardware maintenance. It will expand to include outsourcing services for software engineers and support for clearing regulatory hurdles and certifications.” This is the comprehensive “build to suit” solutions the market has been seeking since the cloud – it includes everything to get your infrastructure building blocks right and is provided as a service – but what do we call this service????
How about “Operations-as-a-Service“!!
OaaS pulls together the elements in IaaS + PaaS + SMEs. It outsources the “plumbing” to those that can make it far more cost effective thru economies of scale. Sure, there are a select few companies who will do this all in house: Google, eBay, Microsoft, Amazon, Apple (trying), and of course, Zynga. Yet, these companies are at such massive scale that it makes sense – and yet, they even have excess (at least they should) capacity which is why AWS was born in the first place and we are now seeing Zynga open up to allow gamers to use their platform (see: http://www.pocketgamer.biz/r/PG.Biz/Zynga+news/news.asp?c=38455). Yet these are the exceptions and not the rule.
The rest of the world should and is seeking comprehensive, end-to-end Operations as a Service provided by single vendors. It doesn’t preclude the market place from buying discreet parts of OaaS individually, however, the dominant companies that will begin to emerge in this next decade will seek to add more and more of the OaaS solutions set to their product list thereby catalyzing a lot (I mean a lot) of consolidation.
I will be following up this blog with a more detailed look at how this concept is playing out, yet in the mean time would very much like to hear the feed back on this topic – is the world looking for OaaS?