AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080815142611.4ef7481b@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.rogers@onstor.com>,<paul.hammer@onstor.com>,<douglas.gruehl@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E09C428A5@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 15 Aug 2008 14:26:33 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "John Rogers" <john.rogers@onstor.com>
Cc: "Paul Hammer" <paul.hammer@onstor.com>, Douglas Gruehl
 <douglas.gruehl@onstor.com>
Subject: Re: Mcdonaldized Site Survey and Statement of Work
Message-ID: <20080815142633.5031762d@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E09C428A5@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E09C428A5@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

John,

This really good stuff.  I'm going to send the 'Data Integritini' to
Douglas.  But I'm going to take credit for it.  Sorry about that.

Cheers,

a

On Fri, 15 Aug 2008 09:28:51 -0700 "John Rogers"
<john.rogers@onstor.com> wrote:

> Hi Paul,
> 
>  
> 
> I came across this concept while watching Community College TV, since
> I don't get any good channels. "McDonaldization": to create a business
> patterned after McDonald's, with efficient and standardized practices.
> It has been dawning on me that I have been doing this for the
> engineering team for some time now. When Jonathan gave his
> presentation at the all hands he mentioned it several times, "John
> Rogers sets everything up for us and we just get to use the systems".
> There are two sides to that, one is that the engineers can quickly
> get to what they need to work on, but at the same time, they don't
> get exposed to certain areas of the product. 
> 
>  
> 
> When I think about it this way and realize what has been happening I
> think more of it really needs to be done. Our product is very complex
> and the more complexity in configuration the elab team can provide up
> front the better the test coverage we get as a by-product. My email
> about things we need to improve in the lab based on cougar is part of
> that. We need more complexity in our default hamburger meal deal. At
> the same time we need to actively build the experiences of the
> engineering team by giving them a place to exercise on their own from
> scratch.
> 
>  
> 
> The real trick is to bring this Mcdonaldization to our customers'
> experience. From the customers point of view we may need to provide
> multiple site survey's based on their needs. If not multiple survey's,
> then perhaps a modular survey based on customer needs. We already
> have a menu, provided by the marketing guys, "Mix it up with ONStor!"
> drink menu. Here are some of the nuances that today's Site Survey
> doesn't pick up on for what a customer might need to be up and
> running. It really depends on why the customer chose ONStor in the
> first place. The first time install needs to ensure that the customer
> gets what the customer paid for.
> 
>  
> 
> Server Consolidator:
> 
> How many servers are we displacing?
> 
> This gets us into how many virtual servers the customer needs. A site
> survey based on server consolidation would need to know the specifics
> on the servers that it is displacing.
> 
> How much data are we going to migrate?
> 
> What are the characteristics of the data set we are going to migrate?
> 
> What kind of storage are we migrating from?
> 
> Do we have white papers and tools to assist in the analysis and
> execution of this? Does the FS TOC tool work on other file systems, or
> is it specific to our file system?
> 
>  
> 
> GoGreen!:
> 
>             More focused on power requirements may need to come with
> Server Consolidator, like French Fries. "Do you want to GoGreen with
> that?"
> 
>  
> 
> Data Center Scaler:
> 
>             More focused on Scalability. The growth requirements must
> be detailed and our scalability features need to be highlighted.
> 
>             Need a limits evaluation.
> 
> Each volume needs a plan for growth and autogrow setup appropriately.
> 
>             Quotas should be setup from the beginning.
> 
>             A timetable should be set for the next sale of storage and
> or additional gateways.
> 
>             If this is a returning customer, then we need to cover
> moving from a 2 node to a 4 node, etc.
> 
>  
> 
> GNS Hopper:
> 
>             Planning requirements for GNS out of the box.
> 
>  
> 
> Data Intregritini(Ok I made that one up):
> 
>             Planning requirements for data integrity. Snapshots,
> Mirroring, Backup and Restore with NDMP, DMIP. Probably should come
> with all install, like a super-sized soda.
> 
>  
> 
> Virtualizer:
> 
>             Need to plan out number of number of shares, share
> security, multi-protocol support
> 
>             Setting up shares is a huge part of the install. Our
> customer shares seem to be something that is unique from site to site.
> 
>             We need to understand how customers are going to implement
> shares on their volumes.
> 
>             Shares are kind of like the first impression that our
> customers' customers are going to see our system. It needs to be setup
> right from the beginning.
> 
>  
> 
>  
> 
> I am sure there is more to cover and when you get back we can start in
> filling in, but just wanted to throw this concept out there. The more
> I think about it, the more I like the idea of a modular site survey
> and we could charge per module.
> 
>  
> 
> John
> 
>  
> 
