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

Daemian Mack edited comment on LIBCLOUD-196 at 5/17/12 5:17 PM:
----------------------------------------------------------------

Makes sense to leave that out of the libcloud driver.

In a perfect world, CloudStack would handle this itself -- I think that's in 
line with the general expectation of URL-handling. 

Since CloudStack leaves this wrinkle as a surprise to the developer, might we 
want to document this responsibility on the part of the developer? I'm just not 
sure where the best place for that might be.
                
      was (Author: daemianmack):
    Makes sense to leave that out of the libcloud driver.

In a perfect world, CloudStack would handle this itself -- I think that's in 
line with the general expectation of URL-handling. 

Since CloudStack leaves this wrinkle as a surprise to the developer, might we 
want to document this responsibility on the part of the user? I'm just not sure 
where the best place for that might be.
                  
> Support RegisterIso call in CloudStack compute driver
> -----------------------------------------------------
>
>                 Key: LIBCLOUD-196
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-196
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Compute
>    Affects Versions: 0.9.1
>            Reporter: Daemian Mack
>            Priority: Minor
>              Labels: newbie, patch
>             Fix For: 0.9.1
>
>         Attachments: add_support_for_cloudstack_registeriso.diff
>
>
> Patch adds support for RegisterIso call to pass a downloadable URL to 
> CloudStack.
> Known concerns:
> - Inner 'exhaust_redirects' method may merit inclusion as utility method 
> elsewhere.
> - Defaulting to bootable=False may not accurately represent typical use case.

--
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

        

Reply via email to