Xen API Project Meeting #2 Minutes - July 2, 2008 * Portions of API not complete yet - (storage manager, physical device manager,statistics) * libvrt - more general purpose API and not a complete API set for Xen * People want to write applications that run against XenServer and Open Source Xen * Specification Documents * 4.1 for XenServer (docs.xensource.com) * 1.0 for Xen API (open source) - fairly complete, certain functions need to be updated ** Have open source API updated to the Citrix definition API (e.g. Bond Class, VLAN Class) * VDI uuid is always recreated when creating. (XendLocalStorageRepo.py, XendQCoWStorageRepo.py). Is it designed like that or a bug? - VDI - uuid is always recreating; designed like that - location field is the storage backend to identify the disk to it * the xm command line interface has too much history burden. can we just leave it for the legacyXMLRPC interface and rewrite a small XenAPI only client? Does citrix has the plan to rewrite and open the xe tool for open source XenAPI? - have a Xen API only client without a large client installation; run in RAM disk (python) * Next Steps * Determine which functions needed completion or work in Xen API 1.0 and have volunteers agree to do the development and testing * Create a list of API requirements that people want in the final Xen API - list will exist on Wiki for people to update or send email to stephen.spector@xen.org for tracking