Re: [VOTE] Apache CloudStack 4.19.1.0 (RC2)
+1 Tested with upgrade, VR patching & instance deployments. -Jithin From: Daan Hoogland Date: Monday, 15 July 2024 at 9:03 PM To: us...@cloudstack.apache.org Cc: dev Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC2) +1 (binding) a bit biased , i can't remember the times I tested 4.19 over the last couple of months so please test some more. I did check signatures and these look good. On Mon, Jul 15, 2024 at 5:02 PM Rohit Yadav wrote: > > +1 (binding) > > Repeated all of RC1 testing, the blockers are fixed now. Upgraded my homelab > from 4.19.1.1 RC1 to RC2, no issues. Tested VM, volume, systemvm, VR > lifecycles. > > > Regards. > > > > > > From: Suresh Kumar Anaparti > Sent: Monday, July 15, 2024 19:14 > To: dev ; users > Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC2) > > Hi All, > > I have created a 4.19.1.0 release (RC2), with the following artifacts up > for testing and a vote: > > Git Branch and Commit SHA: > https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240715T1719 > Commit: 9f4c8959743d2f53faae6fc5d68e88ddc20e21a3 > > Source release (checksums and signatures are available at the same > location): > https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/ > > PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA): > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > The vote will be open until 18th July 2024. > > For sanity in tallying the vote, can PMC members please be sure to indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > For users convenience, the packages from this release candidate (RC2) and > 4.19.1.0 systemvm templates are available here: > https://download.cloudstack.org/testing/4.19.1.0-RC2/ > https://download.cloudstack.org/systemvm/4.19/ > > Regards, > Suresh -- Daan
Re: [PR] vm,metrics: note about behaviour across hypervisors [cloudstack-documentation]
rohityadavcloud commented on code in PR #413: URL: https://github.com/apache/cloudstack-documentation/pull/413#discussion_r1679023357 ## source/adminguide/virtual_machines.rst: ## @@ -1505,6 +1505,16 @@ Instance disk statistics are shown in the Metrics tab in an individual volume vi |vm-disk-metrics-ui.png| + +.. note:: + The metrics or statistics for VMs and VM disks in CloudStack depend on the + hypervisor plugin used for each hypervisor. The behavior can vary across + different hypervisors. For instance, with KVM, metrics are real-time + statistics provided by libvirt. In contrast, with VMware, the metrics are + averaged data based on the global configuration parameter + `vmware.stats.time.window`. Review Comment: @shwstppr Is this about any/all types of stats or just disk/network related? -- 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. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] vm,metrics: note about behaviour across hypervisors [cloudstack-documentation]
shwstppr commented on code in PR #413: URL: https://github.com/apache/cloudstack-documentation/pull/413#discussion_r1679034687 ## source/adminguide/virtual_machines.rst: ## @@ -1505,6 +1505,16 @@ Instance disk statistics are shown in the Metrics tab in an individual volume vi |vm-disk-metrics-ui.png| + +.. note:: + The metrics or statistics for VMs and VM disks in CloudStack depend on the + hypervisor plugin used for each hypervisor. The behavior can vary across + different hypervisors. For instance, with KVM, metrics are real-time + statistics provided by libvirt. In contrast, with VMware, the metrics are + averaged data based on the global configuration parameter + `vmware.stats.time.window`. Review Comment: @rohityadavcloud in my understanding this is true for all VM and disk stats -- 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. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] feature/featch all pages from api request [cloudstack-cloudmonkey]
damonb123 opened a new issue, #153: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/153 It would be great to have a param or setting to tell cmk to fetch all pages from api. It does allow setting params, like page and pagesize, but requires calling cmk multiple times. -- 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. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] vm,metrics: note about behaviour across hypervisors [cloudstack-documentation]
nvazquez commented on code in PR #413: URL: https://github.com/apache/cloudstack-documentation/pull/413#discussion_r1680229835 ## source/adminguide/virtual_machines.rst: ## @@ -1505,6 +1505,16 @@ Instance disk statistics are shown in the Metrics tab in an individual volume vi |vm-disk-metrics-ui.png| + +.. note:: + The metrics or statistics for VMs and VM disks in CloudStack depend on the + hypervisor plugin used for each hypervisor. The behavior can vary across + different hypervisors. For instance, with KVM, metrics are real-time + statistics provided by libvirt. In contrast, with VMware, the metrics are + averaged data based on the global configuration parameter + `vmware.stats.time.window`. Review Comment: What about a second note for Vmware, advising that better results are observed by reducing the dynamic configuration value? -- 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. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
