|
|
|
|
|
|
|
|
|
|
xen-cim
Re: [Xen-cim] Summary of 3/31 Weekly Call
Thanks Jim!
By next week the USA will be on daylight savings so things should be back to normal, but if Fri 7am PST is still bad then I'm OK with moving the meeting time, though many of my mornings are heavily 'booked' due to the lack of good timeslots to share with my IBM colleagues in Germany. Could everyone perhaps every post or send me what times they absolutely *cannot* make (please include your timezone) and I'll figure out blackout times and post some options.
I'm fine with postponing the LTC Xen CIM code walkthrough till the following week (April 10-14). I'll still post the background materials shortly, so you'll just have longer to read them :-)
- Gareth
Dr. Gareth S. Bestor
IBM Linux Technology Center
M/S DES2-01
15300 SW Koll Parkway, Beaverton, OR 97006
503-578-3186, T/L 775-3186, Fax 503-578-3186
"Jim Fehlig" <jfehlig@xxxxxxxxxx>
Agreed that Gareth and Jim will be co-maintainers. Jim will handle 3rd
party submissions. (Simon - I saw your post containing URL for provider
repository in my backlog of email. Sent my public key to
james@xxxxxxxxxxxxx and cc'd you.)
Seems like we still need to agree on a day and time for the weekly
call. Thursday is really the only bad day for me as there is a weekly
XenSource/Novell call at 7am PST/PDT and SVPC call at 9am PST/PDT. We
could squeeze the call in between these two at 8am. I also have a
weekly meeting at 8:30am PST/PDT on Wednesday but flexible otherwise.
Raj and Aravindh have requested postponing the code walk through until
the week of April 10 due to Linuxworld commitments next week. Do we
want to have separate call for the walk through or use the agreed upon
weekly call?
I have completed a first cut of a (temporary) shim between the LTC xm
interface and libvirt. I hope we still agree to this until such time
that libvirt exposes C structures :-). There are several routines that
have not been implemented (xm_set_domain, xm_delete, xm_mem_set,
xm_reboot, xm_migrate) due to no counterpart in libvirt. I will open a
discussion on libvirt mailing list to request entry points for this
functionality.
Regards,
Jim
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|
|
|
|
|