AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Dave.Limato@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	D7A889C980962746B30DE07864593C02C7AAA67D@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 24 Aug 2009 15:12:19 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Limato, Dave" <Dave.Limato@lsi.com>
Subject: Re: lab management related emails
Message-ID: <20090824151219.2ff4805f@ripper.onstor.net>
In-Reply-To: <D7A889C980962746B30DE07864593C02C7AAA67D@cosmail02.lsi.com>
References: <20090824124926.28f315ea@ripper.onstor.net>
	<D7A889C980962746B30DE07864593C02C7AAA67D@cosmail02.lsi.com>
Organization: LSI
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

OK, thanks.

On Mon, 24 Aug 2009 15:59:30 -0600 "Limato, Dave" <Dave.Limato@lsi.com>
wrote:

> Here it is...This was the conversation between Karen and Sandrine. It
> looks like a bunch of noise to me. Lets just go into the call
> tomorrow with an open mind, and see where she goes with this. She may
> hear that we have a req to be filled and all this is out the window. 
> 
> 
> ============================================================
> 
> From: Boulanger, Sandrine 
> To: Nahum, Nelson; Crane, Karen 
> Cc: Stark, Brian 
> Sent: Fri Aug 07 17:22:28 2009
> Subject: RE: Thnings to consider for lab management 
> 
> 
> Thanks Nelson. Karen, could you send me your phone number and some
> time I could give you a call to discuss all this? Our lab goes
> through a lot of configuration cahnages, and not only for test
> engineers but also for software developers, support and SEs. So
> evrywhere you mention taht a test engineer would do it is incorrect;
> first it would be chaos in the lab, nobody would know how things are
> configured; second, only an IT person would have some of the
> knowledge to configure some of the things we need; that same person
> could also handle the upgrade of the firmwares and OS, handle the
> purchase requests, perform a detailed lab inventory, and also handle
> the configuration requests from engineering and support
> organizations, which as I said earlier come in pretty much every day,
> so that's a lot to cover. We already have somebody here under
> contract who is doing all those things (more or less since there's
> more to do than one person can do!), we are looking into making him a
> full time offer, Brian Stark is taking care of this. I would need to
> discuss further with you what the outsourcing od the cooling, power,
> capacity means. I believe IT in Miliptas (Trinh Tranh) is already
> looking into the corporate cluster (a.k.a "Mightydog") that hosts all
> our comapny data. By lab resource management tool I mean something
> that allows engineering and support to reserve the equipment in the
> lab that they need (gateways, clients...). Right now we are using
> something called Resource Scheduler which does not work very well for
> us, I wonder if LSI already has a tool of choice for such a thing.
> 
> I'll also contact David Stein for automation standards already used
> ly LSI teams.
> 
> Thanks,
> Sandrine
> 408 963 2453
> 
> 
> --------------------------------------------------------------------------------
> From: Nahum, Nelson
> Sent: Tuesday, August 04, 2009 12:46 PM
> To: Boulanger, Sandrine; Crane, Karen
> Cc: Stark, Brian
> Subject: FW: Thnings to consider for lab management
> 
> 
> Hi Sandrine,
> 
> I wanted to introduce you to Karen Crane, among all her jobs, Karen
> is the responsible for the lab. in Wichita and she graciously
> volunteer to guide you and help you with your lab.
> 
> Karen, answered you email below.
> 
> 
> 
> I suggest you call Karen and discuss the best way to accomplish the
> lab. management, like we do in other small offices that doesn't have
> lab. manager.
> 
> 
> 
> Nelson
> 
> 
> 
> 
> --------------------------------------------------------------------------------
> 
> From: Sandrine Boulanger [mailto:sandrine.boulanger@onstor.com] 
> Sent: Wednesday, July 29, 2009 13:34
> To: Nahum, Nelson
> Cc: Brian Stark
> Subject: Thnings to consider for lab management
> 
> 
> 
> Here's a follow-up email with the least of things to consider for our
> labs.
> 
> We'll need 1 to 2 people to be responsible for the lab management in
> Campbell and Pleasanton, this is key to engineering and support to
> work smoothly.
> 
> 
> 
> Lab management includes:
> 
> - Keep track of cooling, power consumption, capacity (power, terminal
> server, switches, patch panels ports...)
> 
> (Karen Crane):  As of July 23, we outsourced this function to a
> combination of IT and WPS.   I have already brought up the potential
> of supporting OnStor labs with Colleen Polek and Rich Miller.  What
> is covered:  Power, Cooling, Core network switch support, KVM
> support.  What ISN'T supported - switches IN a test configuration.
> 
> - Maintenance (firmware for arrays, switches, licenses for
> applications, client OS support)
> 
> (Karen Crane)  This is handled by test engineers
> 
> - Repair and replacement (disk, switch, port, cable...)
> 
> (Karen Crane):  This is handled by test engineers
> 
> - Buying new equipment for qualifications, setting up new system
> testbeds, power manager/APCON systems for automation of power on/off,
> simulate cable pulls...)
> 
> (Karen Crane):  We have a group to handle purchases and a defined
> processes.  Things such as simulated cable pulls, etc (automation
> tools) we will need to connect you with David Stein - he manages the
> test automation group.  
> 
> - Monitoring (Nagios...)
> 
> - Lab inventory and client OS update (many clients not reachable, OS
> too old, some gateways without storage, or no FP or FC ports
> connected...)
> 
> (Karen Crane):  If there is an inventory system that contains all
> serial numbers and equipment we need to get to that and extract the
> data.
> 
> - Lab resources management tool (Arnaldo was investigating a new one)
> 
> (Karen Crane)  Not sure what they are talking about?  What type of
> tool?
> 
> - Handle elab requests (add more luns to a gateway, create multiple
> paths to luns, setup lport aggregation, vlan tagging, jumbo frames,
> create private network, simulate WAN, create backup domain
> controller, create NTLM, Kerberos, LDAP server, Windows domain
> trusts, DFS root, restore ssh or telnet access, fix console port
> access...)  
> 
> (Karen Crane)  These items are handled by engineers typically.  Some
> of these would be handled by IT.
> 
> 
> 
> We also need to have someone take over the management of the
> corporate cougar cluster Mightydog, where we have all our home
> directories (NFS and CIFS accessible), project data, etc...  
> 
> (Karen Crane)  Talk with Colleen Polek - this is an IT function.
> 
>  
> 
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@lsi.com] 
> Sent: Monday, August 24, 2009 12:49 PM
> To: Limato, Dave
> Subject: Re: lab management related emails
> 
> On Mon, 24 Aug 2009 10:54:03 -0600 "Limato, Dave"
> <Dave.Limato@lsi.com> wrote:
> 
> > 
> > 
> > _____________________________________________
> > From:   Boulanger, Sandrine
> > Sent:   Wednesday, August 19, 2009 4:12 PM
> > To:     Currin, Shawn
> > Cc:     Limato, Dave
> > Subject:        lab management related emails
> > 
> >  << Message: Re: Thnings to consider for lab management >>  <<
> > Message: RE: OnStor Labs >>
> > 
> 
> Hi Dave, this is all I got.  No actual attachment.  This is probably
> a form of a "link" for exchange/outlick, so if I was using Outlick, I
> would get those messages or whatever.  Perhaps just forward the
> latest email from that thread inline?
> 
> Thanks,
> 
> a
