[ 
https://issues.apache.org/jira/browse/LIBCLOUD-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509224#comment-14509224
 ] 

Steven Gregory commented on LIBCLOUD-695:
-----------------------------------------

I have a forked repo of libcloud that includes all of the above functions 
except:

ex_boot_volume - I found out that the 'ex_block_device_mapping' kwarg will take 
care of that, so I'm going to refactor our internal codebase to use that and 
maybe look into a method that will make booting volumes less mysterious, whose 
output would be the 'ex_block_device_mapping' kwarg required for launch.

Also I have yet to add:
{code}
#2. Hypervisor support
def ex_list_hypervisor_nodes(self):
def ex_detail_hypervisor(self):
def ex_detail_hypervisor_node(self, hypervisor_id):
def ex_hypervisor_statistics(self):
{code}

I'm wondering if a 'Hypervisor' object would be required/beneficial here, or if 
I should just deal with the API as it stands and return back the python dict...

Looking for input

> Adding additional 'ex_' functionality to OpenStack Compute NodeDriver
> ---------------------------------------------------------------------
>
>                 Key: LIBCLOUD-695
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-695
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Compute
>            Reporter: Steven Gregory
>            Priority: Minor
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Using this as the umbrella and start point for discussion of the Listserv 
> post of the same name.
> Here is the list of functions i would like to contribute:
> {code}
> #1. Instance Shelving support
> def ex_shelve_instance(self, node):
> def ex_unshelve_instance(self, node):
> def ex_shelve_offload_instance(self, node):
> #2. Hypervisor support
> def ex_list_hypervisor_nodes(self):
> def ex_detail_hypervisor(self):
> def ex_detail_hypervisor_node(self, hypervisor_id):
> def ex_hypervisor_statistics(self):
> #3. Fixed IP support
> def ex_add_fixed_ip(self, server, network_id):
> def ex_remove_fixed_ip(self, server, fixed_ip_address):
> #4. Additional support for volume attachments
> def ex_list_volume_attachments(self, node):
> #5. Quota-sets support
> def ex_get_quota(self):
> def ex_update_quota_for_user(self, tenant_id, user_id, values):
> #6. Bootable Volume support
> def ex_boot_volume(self, volume, volume_size, **kwargs):
> def create_volume(self, size, name,description=None, 
> metadata=None,location=None, snapshot=None, image=None): 
> # Add image=None to create_volume to make a bootable volume
> # Add description=None to update the 'display_description' for the volume.
> #7. Image metadata support
> def ex_get_image_metadata(self, image):
> def ex_set_image_metadata(self, image, metadata): #Leaves non-conflicting 
> keys in-place.
> def ex_replace_image_metadata(self, image, metadata): #Wholesale replacement
> def ex_delete_image_metadata(self, image, key):
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to