You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Hutson Betts (Created) (JIRA)" <ji...@apache.org> on 2011/10/11 20:17:11 UTC
[dev] [jira] [Created] (LIBCLOUD-119) OpenNebula Node Types Updates
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
Fix For: 0.5.2, 0.6.0
Attachments: base.size.py.patch, opennebula.size.feature.py.patch
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
[dev] [jira] [Updated] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-119:
----------------------------------
Attachment: size.patch
An updated patch that takes into consideration the changes in LIBCLOUD-120.
> 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, size.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
[dev] [jira] [Updated] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-119:
----------------------------------
Attachment: (was: opennebula.size.feature.py.patch)
> 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
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133127#comment-13133127 ]
Hutson Betts commented on LIBCLOUD-119:
---------------------------------------
Tomaz,
Under further consideration, I decided to sub-class NodeSize to implement the CPU and VCPU properties.
Though I believe we'll continue to face duplication in this area. I believe drivers might have to handle peculiarities amongst their sizes until we derive a definition for CPU, and VCPU.
Such as, I don't believe we can specify a CPU frequency as a property of a node type/size, since it is not concrete. A unit of "CPU", or "Compute Unit" might stand for any number of possible processing metrics. For Amazon, a Compute Unit implies a range, such as "1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor" - Amazon. Whereas, on an OpenNebula infrastructure, CPU is associated with the number of cores reserved for the virtual instance. That CPU could represent any processor, frequency, etc.
> 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: size.diff
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Tomaz Muraus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131137#comment-13131137 ]
Tomaz Muraus commented on LIBCLOUD-119:
---------------------------------------
Can this ticket be closed now that LIBCLOUD-120 has been merged intro tunk?
> 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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Tomaz Muraus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133331#comment-13133331 ]
Tomaz Muraus commented on LIBCLOUD-119:
---------------------------------------
Merged with minor modifications in r1187687 (http://svn.apache.org/viewvc?rev=1187687&view=rev).
Thanks.
> 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.6.0
>
> Attachments: size.diff
>
> 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
[dev] [jira] [Closed] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Tomaz Muraus (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus closed LIBCLOUD-119.
---------------------------------
> 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.6.0
>
> Attachments: size.diff
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132038#comment-13132038 ]
Hutson Betts commented on LIBCLOUD-119:
---------------------------------------
Tomaz,
That would make more sense, but I decided to look into the matter a little further. Currently, Amazon Web Services (As supported by the EC2 driver), and OpenStack (As supported by the OpenStack driver) support instances which contain 2 or more vCPUs.
Amazon instances: http://aws.amazon.com/ec2/instance-types/
An obscure reference to instance types for OpenStack: http://ken.pepple.info/openstack/2011/03/03/Configurable-Instance-Types-For-OpenStack-Nova/
Furthermore, Amazon associates a metric called an EC2 Compute Unit, with the CPU capacity available to an instance.
Therefore, I was incorporating support for those instance type/size properties in the base NodeSize class.
Thoughts?
> 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, size.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
[dev] [jira] [Updated] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-119:
----------------------------------
Attachment: (was: base.size.py.patch)
> 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
>
> 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
[dev] [jira] [Updated] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-119:
----------------------------------
Attachment: size.diff
I've attached a simpler version which just sub-classes the NodeSize class, and adds properties for CPU and VCPU.
> 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: size.diff
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Tomaz Muraus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131921#comment-13131921 ]
Tomaz Muraus commented on LIBCLOUD-119:
---------------------------------------
I just checked the patch and "cpu" and "vcpu" attributes shouldn't be part of the base NodeSize class. You should create a separate NodeSize class for the OpenNebula driver which inherits from the base NodeSize class and add those two attributes to it.
Thanks,
Tomaz
> 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, size.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
[dev] [jira] [Commented] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Tomaz Muraus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132750#comment-13132750 ]
Tomaz Muraus commented on LIBCLOUD-119:
---------------------------------------
I would be OK with adding two new attributes to the base NodeSize class:
- cpu -> CPU frequency in MHz
- cpu_count -> number of CPUs / cores
In case we add those two attributes, this also means we also need to update all the affected compute drivers. Currently some drivers already have a custom "NodeSize" class which includes "cpu" attribute.
> 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, size.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
[dev] [jira] [Updated] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-119:
----------------------------------
Attachment: (was: size.patch)
> 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
>
> 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
[dev] [jira] [Updated] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-119:
----------------------------------
Attachment: base.size.py.patch
opennebula.size.feature.py.patch
> 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
[dev] [jira] [Resolved] (LIBCLOUD-119) OpenNebula Node Types Updates
Posted by "Tomaz Muraus (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus resolved LIBCLOUD-119.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.5.2)
> 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.6.0
>
> Attachments: size.diff
>
> 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