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:<brian.stark@lsi.com>,<rendell.fong@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 30 Sep 2009 17:37:12 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: Brian Stark <brian.stark@lsi.com>
Cc: Rendell Fong <rendell.fong@lsi.com>
Subject: schedule mods for vsvr
Message-ID: <20090930173712.66ead7c8@ripper.onstor.net>
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

Hi Brian,

Here's the schedule mods for the vsvr part.  No net changes.

Develop SSC/TuxRx [note nomenclature-o] daemons ==>

	Implement vsd changes (5 days)
	Implement ipmd changes (5 days)
	Implement libipmd changes (5 days)
	Integrate daemon changes (5 days)

Test/debug SSC/TuxRx [nomenclature-o] daemons (20 days) ==>

	Test/debug vsd (10 days)
	Test/debug ipmd (5 days)
	Test/debug libipmd (5 days)

Integrate SSC/TuxRx [nomenclature-o] daemons (10 days) ==>

	Integrate vsd with tuxstor kernel threads (5 days)
	Integrate libipmd with other SSC daemons (5 days)

Rendell and I went over the vsvr API for a couple of hours -- there
seems to be very little work there as far as we can tell.  The API
should come over almost completely intact according to our best guess.
The only question marks are a couple of routines that deal with bind
connection blocks, and that would depend on what Bill decides to do
with those.

Cheers,

a

