[
https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131249#comment-13131249
]
Hutson Betts commented on LIBCLOUD-119:
---------------------------------------
Actually, this patch was to update the NodeSize options available. LIBCLOUD-120
does not include those changes. However, this patch needs to be re-created from
updated source given the changes in LIBCLOUD-120. I hope to have a new patch
uploaded within 24 hours.
> OpenNebula Node Types Updates
> -----------------------------
>
> Key: LIBCLOUD-119
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-119
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Affects Versions: 0.5.2, 0.6.0
> Environment: Debian Squeeze, using libcloud 0.5.2 extracted from an
> archive file.
> Reporter: Hutson Betts
> Priority: Minor
> Labels: patch
> Fix For: 0.5.2, 0.6.0
>
> Attachments: base.size.py.patch, opennebula.size.feature.py.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> I updated the list_sizes() function to return the correct definitions for
> each size as specified in the current release (3.0) of OpenNebula.
> Template directory where sizes are specified:
> http://dev.opennebula.org/projects/opennebula/repository/revisions/master/show/src/cloud/occi/etc/templates
> Furthermore, I added a CPU and Virtual CPU attribute to NodeSize. These
> attributes are part of the Node Sizes as used by OpenNebula. This changed
> required the addition of CPU and VCPU parameters to the NodeSize base class.
--
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
