Hi Michael,

Thanks for posting these notes. It would be good if you could publish the conference call coordinates to this list so that anyone interested in Tashi could call in as well.

Regards,

Craig

On Oct 30, 2008, at 9:03 AM, Ryan, Michael P wrote:

I recently was part of a phone conversation discussing Tashi and Poolboy (a project at Yahoo that has similar goals) on 10/20. I mentioned on the phone bridge that we should post notes here so that those who were unable to call in could get an overview. Here are some quick notes I took:

Yahoo Participants:
       Peter Meulbroek
       Dan Mercer
       Daniel Muino
       Robert Miller
       Jay Buffington
       Andrew Evans
       Suraj Belavalgidad
       Jud Dangall

Intel Participants:
       Michael Kozuch
       Dave O'Hallaron
       Michael Ryan

Yahoo (poolboy):
Open-source working group presentation was done recently, results look good
       Patent/IP lawyer meetings ongoing
       Expect to finish meetings with them on Wednesday (10/22)
Releasing first piece this month (yvm) (VMM management layer -- node manager equivalent)
       Management console next
               More site-specific code involved and harder to clean up
       Might or might not release UI piece because of GPLv3 licensing
       RESTful interfaces
Tomer Shiran joining Yahoo! as intern this Wednesday or next Monday
       Requirements specification soon to be released on [EMAIL PROTECTED]

Intel (tashi):
Current code is almost entirely Intel code, with a little bit of CMU student contribution
       Intel is kicking off a power-management thrust
Power-management is particularly interesting with the storage layer Preparing to propose Tashi as a research project (within Intel Research)
       OpenCirrus review with upper management is soon

Next meeting time and bridge number TBD

- Michael Ryan

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to