[
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
