cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [cloudstack] div8cn opened a new issue #3482: Compute resources are not automatically released after vm stop
Date Wed, 10 Jul 2019 13:50:18 GMT
div8cn opened a new issue #3482: Compute resources are not automatically released after vm
stop
URL: https://github.com/apache/cloudstack/issues/3482
 
 
   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
   
    * Improvement Request
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Management Server
   Usage Server
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.9/4.11/4.11.2/4.11.3
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking,
etc.  N/A otherwise
   -->
   N/A
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   N/A
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   The computing resource cannot be released after the VM is stopped. You must execute delete
to release the computing resource.
   
   After the VM is stopped, it does not consume any computing resources. We should not think
that it still occupies computing resource quota (aws azure google cloud is designed in this
way).
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots
if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   1. Create an account and update the following resource quotas
       Instance Limits=5
       CPU limits=8
       Memory limits (MiB)=32G
   2. Create and run two VMs under the new account:
       Name=vm1,vcpu=4,ram=16
       Name=vm2,vcpu-4,ram=16
   
   3. Stoped vm1, vm2
   
   4. Create a third VM under account (test1)
       Name=vm3,vcpu=4,ram=16 
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   vm3 can be successfully created and run
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Error:
   Maximum amount of resources of Type = 'cpu' for Account Name = test1 in Domain Id = 4 is
exceeded: Account Resource Limit = 8, Current Account Resource Amount = 8 Requested Resource
Amount = 4.
   ~~~
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message