Has anyone had a chance to review this patch? -- Hutson Betts Computer Science and Engineering Texas A&M University
On Sat, 2011-11-19 at 19:00 +0000, Hutson Betts (Updated) (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/LIBCLOUD-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Hutson Betts updated LIBCLOUD-121: > ---------------------------------- > > Attachment: opennebula.patch > > This patch is an update to the OpenNebula compute driver and compute tests as > compared to the latest Libcloud trunk. > > Changes include: > > Overall: > * Change the name of the OpenNebula v3.0 Compute Driver to > OpenNebula_2_0_NodeDriver to reflect that every API after v2.0 has remained > the same. Therefore, 2.0 should remain the defacto standard API version until > an API change is made. > * Added API v3.2 to supported API versions of the OpenNebula v2.0 Compute > Driver. OpenNebula 3.2 will be published later this year, but the OCCI API, > OpenNebula uses OCCI v1.0, will remain the same. > > OpenNebula v1.4 Compute Driver > * Changes to the create_node function: > * Added support for specifying a disk image for disk images available > in the storage pool. > * Added support for specifying a network for networks available in the > network pool. > * Replaced HTTP Response codes, such a integer values that were used for > checking HTTP responses, with codes in the httplib library. > * Updated network retrieval support to get the 'SIZE' attribute for each > network in the network pool. > * Added support to get extract the image information for each compute node. > * Corrected code associated with adding an image to a compute node or reading > a compute node description with an image. > * Documentation update. > > OpenNebula v2.0 Compute Driver > * Added context variable for allowing user-defined context values in > create_node. > * Added support to extract context information from a compute node > description. > * Added support to extract NodeSize information from a compute node > description. > * Added support to extract NodeImage information from a compute node > description. > * Documentation updates. > > OpenNebula Tests > * New test cases for OpenNebula computer driver v2.0+. > * Updated MockHTTP handlers. > * Updated XML files to include network files, and corrections to the files > relating to OpenNebula v2.0+. > > I hope this will finish out the requirements for this ticket. If not, please > let me know. > > > OpenNebula Driver Improvements and Additional Driver Updates > > ------------------------------------------------------------ > > > > Key: LIBCLOUD-121 > > URL: https://issues.apache.org/jira/browse/LIBCLOUD-121 > > Project: Libcloud > > Issue Type: Improvement > > Components: Core > > Affects Versions: 0.6.1 > > Environment: Latest Libcloud trunk with contents of diff operating > > on Debian 6.0 (Stable). > > Reporter: Hutson Betts > > Priority: Minor > > Labels: api-change, patch > > Attachments: base-update.diff, opennebula.diff, opennebula.patch, > > update.diff > > > > > > I'm attaching a diff/patch that contains modifications to several compute > > drivers; OpenNebula in particular. > > With regard to OpenNebula, these changes include the ability to request a > > list of virtual networks provided by the OpenNebula infrastructure > > provider. Furthermore, the OpenNebula NodeDriver has been extended to > > extract the disk and network descriptions from the compute XML description. > > Disks and networks are instantiated as NodeImage and NodeNetwork objects > > and then attached to a newly instantiated Node. To support this capability, > > I added a NodeNetwork class to the base compute class. > > Furthermore, I modified the Opsource and OpenStack drivers to match in > > consistency with the OpenNebula driver. This also included changes to > > include httplib. I hope to extend that work later to other drivers, if the > > work is desired. > > This patch really requires additional, more in-depth testing, during this > > following week, but I wanted to present that patch for consideration, and > > comments. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
signature.asc
Description: This is a digitally signed message part
