| |
|
 |
|
 |
|
|
|
| |
|
|
xen-cim
[OK, I'll use and external account since we still some internal problems with posting to lists.xensource.com]
All,
I have finally gotten around to testing the xm to libvirt (temporary) shim. It is looking good with the exception of xm_set_domain(), xm_delete(), xm_create() and xm_migrate() - no corresponding libvirt entry points as discussed earlier. These routines are coded to proposed entry points posted on libvirt mailing list.
I opened a discussion on libvirt ml concerning additional entry points to support the idea of setting config, activating a domain based on previously set config, and deleting config. There seems to be some resistance to providing this functionality in libvirt. I don't have any compelling arguments supporting the idea
:-). Please join in the discussion if you think otherwise. Other tools will surely use libvirt and they don't know or care about defined vm's. The provider should probably implement this functionality IMHO. Question is whether config is written to xenstore, a file, the cimom's static instance repository?? If written to xenstore, then as Gareth pointed out why use a middleman ** jim sighs **. Perhaps we should just pull in some of the internal libvirt functionality and go from there.
I would like to get this resolved quickly so we can move the provider forward. Also would like to get the new code base running on SLES as I've abandoned the OpenWBEM-based provider.
BTW, are we having the weekly call at 7am PDT on Friday this week?
Regards,
Jim
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|
|
|
| |
|
Home