)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"c2565d3bae58bbc507d924f77454de840a687948","unresolved":true,"context_lines":[{"line_number":22,"context_line":"`os-simple-tenant-usage`) would only report the time the VM has been up"},{"line_number":23,"context_line":"and running. However, that is not what happens. The"},{"line_number":24,"context_line":"`os-simple-tenant-usage` reports the time that a virtual machine (VM)"},{"line_number":25,"context_line":"exists in the cloud environment. Therefore, actions such as pause,"},{"line_number":26,"context_line":"suspend, and stop do not affect the usage accounting."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"This might be a problem for people using this API for billing, or for"},{"line_number":29,"context_line":"people that use other systems (e.g. CloudKitty) for billing."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"4bdf848d_ad631bcd","line":26,"range":{"start_line":25,"start_character":33,"end_line":26,"end_character":53},"updated":"2020-12-08 12:42:25.000000000","message":"yes this is because the vms are still consuming resouce on the phsyical\nhost when they are in does states. if the vm is shelved it will not be counted towords\nthe usage of cpu and ram as those resouce are freed when it is shelve offloaded.","commit_id":"01f0424930213b86219d9f05a2bcd28c6f3e19f9"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"c2565d3bae58bbc507d924f77454de840a687948","unresolved":true,"context_lines":[{"line_number":25,"context_line":"exists in the cloud environment. Therefore, actions such as pause,"},{"line_number":26,"context_line":"suspend, and stop do not affect the usage accounting."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"This might be a problem for people using this API for billing, or for"},{"line_number":29,"context_line":"people that use other systems (e.g. CloudKitty) for billing."},{"line_number":30,"context_line":"End-users might try to cross-check the data from the billing from"},{"line_number":31,"context_line":"CloudKitty for instance, with the usage report found in Horizon that"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"158d9da7_cae0ac16","line":28,"range":{"start_line":28,"start_character":45,"end_line":28,"end_character":62},"updated":"2020-12-08 12:42:25.000000000","message":"this is not the intent of the api but yes you are correct","commit_id":"01f0424930213b86219d9f05a2bcd28c6f3e19f9"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"c2565d3bae58bbc507d924f77454de840a687948","unresolved":true,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Having said that, we would like to propose a documentation amendment."},{"line_number":46,"context_line":"The idea is to explicitly say for users/operators that the simple usage"},{"line_number":47,"context_line":"API only considers the time that the VM existed in the cloud for the"},{"line_number":48,"context_line":"accounting, and not the actual time it has been up and running."},{"line_number":49,"context_line":"This will save some misunderstanding and misuse of the API data."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"ab74a49d_f9c09ea2","line":47,"range":{"start_line":47,"start_character":36,"end_line":47,"end_character":61},"updated":"2020-12-08 12:42:25.000000000","message":"yes looking at the algorithim here\n\nhttps://github.com/openstack/nova/blob/80b807a4c590980b9e514042778bd8c277e89e40/nova/api/openstack/compute/simple_tenant_usage.py#L140-L222\n\nthis is what its doing within the specificed start and end time of the query.","commit_id":"01f0424930213b86219d9f05a2bcd28c6f3e19f9"}],"api-ref/source/os-simple-tenant-usage.inc":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"c2565d3bae58bbc507d924f77454de840a687948","unresolved":true,"context_lines":[{"line_number":11,"context_line":".. warning::"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"   The `os-simple-tenant-usage` will report usage statistics based on the latest"},{"line_number":14,"context_line":"   flavor that is configured in the virtual machine (VM), and ignoring stop,"},{"line_number":15,"context_line":"   pause, and other events that might have happened with the VM. Therefore, it"},{"line_number":16,"context_line":"   uses the time the VM existed in the cloud environment to execute the usage"},{"line_number":17,"context_line":"   accounting."},{"line_number":18,"context_line":""}],"source_content_type":"text/x-c++src","patch_set":4,"id":"b1bba519_a1c323ed","line":15,"range":{"start_line":14,"start_character":58,"end_line":15,"end_character":65},"updated":"2020-12-08 12:42:25.000000000","message":"the one state that one might resonable expect to be excluded is shelve since\nthat alther the actual resouce usage in the cloud since you are no longer consuming\ncpu and ram. for stopped and paused the instnace is consuming the same abount of resouces\nas active since no other instnace can use the reousce allcoated to the stopped instance.","commit_id":"01f0424930213b86219d9f05a2bcd28c6f3e19f9"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"3ed1c0b0e4f141839b5a3ce9b670f4085766364f","unresolved":true,"context_lines":[{"line_number":11,"context_line":".. warning::"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"   The `os-simple-tenant-usage` will report usage statistics based on the latest"},{"line_number":14,"context_line":"   flavor that is configured in the virtual machine (VM), and ignoring stop,"},{"line_number":15,"context_line":"   pause, and other events that might have happened with the VM. Therefore, it"},{"line_number":16,"context_line":"   uses the time the VM existed in the cloud environment to execute the usage"},{"line_number":17,"context_line":"   accounting."},{"line_number":18,"context_line":""}],"source_content_type":"text/x-c++src","patch_set":4,"id":"3ae6b8c9_62c22b65","line":15,"range":{"start_line":14,"start_character":58,"end_line":15,"end_character":65},"in_reply_to":"b1bba519_a1c323ed","updated":"2020-12-08 12:58:04.000000000","message":"Well, to us, stopped VMs do not exist in the hypervisor. Therefore, they are not consuming resources. The disks are totally different though, even for stopped VMs they are charged. \n\nIndeed, one can consider allocated resources as used ones, but they are not used in reality. In public cloud env. people normally use overprovisioning/overcommitment of resources, and they also do not charge for stopped VMs (only for disks/volumes allocated).","commit_id":"01f0424930213b86219d9f05a2bcd28c6f3e19f9"}]}