In one of my last posts, I quickly explained I worked in the
SharePoint Engineering team for few months. The experience was amazing, though
pretty challenging. I found out a lot of things on a lot of topics, but I loved
meeting smart, dedicated and great people.
Some people wonder what I was doing there.
Here are some clues in
You may did read this post few months ago from Jeff Teper
(SharePoint Corp VP) http://blogs.msdn.com/b/sharepoint/archive/2009/10/11/engineering-sharepoint.aspx
. It was a pre-SharePoint conference post where some of the engineering
organization details where explained.
In this post, you may notice this section:
Team – In the last couple of posts I mentioned that SharePoint Online is big
part of our development cycle. […]. This release, we created a dedicated team
called “The Grid” team to analyze and optimize in great detail the total costs,
time, reliability and other factors of a SharePoint deployment we hope to reach
10s and eventually 100s of millions of users. Almost all of what we learn there
helps make the product more reliable for customers and partners hosting their
own servers from a small company to a 250,000 employee enterprise. There is a
bunch of great learning from things like virtualization with Hyper-V to best
practice analysis to operations monitoring we will share in the coming months.
The Grid team will be at the SharePoint Conference.”
For those of you who attended the SharePoint Conference, you
didn’t see a “Grid” session or a “Grid team” at asks the experts. In fact they
were here, but with their “classic” SharePoint titles.
In the excerpt, you read “we will share in the coming months”.....
Well, here you go: that’s partly what I was requested to do.
So, step by step, that’s how I
became internally the “Grid guy”. With my PFE colleague we led few webcasts and
technical internal sessions/events to start the messaging about SharePoint
Grid. Being passionate about those topics of Automation and Orchestration,
people came to me on these aspects.
We also presented these concepts
to various internal stakeholders, and few customers interested in hosting their
own “Private Clouds” with SharePoint being part of it.
To be clear, “Grid” is a
SharePoint Engineering set of concepts, tools and processes. They own this
thing, and are quite amazing on how they do that. But out of the Building 16, I
became the “Grid guy” – its “public face” like the Grid PM lead said once – of
this work. Just because I was asked to understand, and explain outside of the
building how it’s done.
To test my understanding, I
reproduced SharePoint Grid on servers in France. That was pretty good
experience to do that. I needed to check what it was and how it worked. That’s
the way I am, I like to know what I talk about, up to be able to do it myself
if needed J.
“SharePoint Grid” you can represent like this:
=> etc. =>
Nice, isn’t it? And that’s just for 6 Hyper-V hosts, hosting
each 6 VMs….. But it’s already 48 Windows Servers to operate and manage.
How can you do that? ….. Automation with new concepts is the
only way J …
and that’s my passion!
I’ll share few useful insights and background in the weeks
to come. First one to start:
< Emmanuel />