You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2013/12/18 20:45:07 UTC

[jira] [Created] (CLOUDSTACK-5547) Capacity reservation should be customizable at the vm level

Nitin Mehta created CLOUDSTACK-5547:
---------------------------------------

             Summary: Capacity reservation should be customizable at the vm level
                 Key: CLOUDSTACK-5547
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5547
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.3.0
            Reporter: Nitin Mehta


Capacity reservation should be customizable at the vm level. Say with a flag in the service offering. Currently its cloud-wide through skip.counting.hours.

Also in CS, reserved capacity is tracked per host instead of per vm level and this creates issues say when a stopped vm is upgraded. We should move to a model of tracking it per vm level.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)