Re: [RESULT][VOTE] Apache CloudStack 4.19.0.0
Nice news, thanks Abhishek! Regards, Nicolas Vazquez From: Rohit Yadav Date: Friday, 2 February 2024 at 10:41 To: dev@cloudstack.apache.org , users Subject: Re: [RESULT][VOTE] Apache CloudStack 4.19.0.0 Thanks Abhishek and everyone involved in the effort. And congratulations everyone ! Regards. From: Abhishek Kumar Sent: Friday, February 2, 2024 5:48:54 PM To: dev@cloudstack.apache.org ; users Subject: [RESULT][VOTE] Apache CloudStack 4.19.0.0 Hi all, After more than 72 hours, the vote for CloudStack 4.19.0.0 *passes* with 7 PMC + 3 non-PMC votes. +1 (PMC / binding) * Daan * Rohit * Nicolas * Nux * Harikrishna * Boris * Wei +1 (non binding) * Vladimir * Pearl * Suresh 0 none -1 none Thanks to everyone participating. I will now prepare the release announcement to go out after 24 hours to give the mirrors time to catch up. Regards, Abhishek
Regarding the Log4j upgrade
Hi all, As some of you might already be aware, ACS version 4.20 will bring our logging library, log4j, from version 1.2 to 2.19. This change will bring us a number of benefits, such as: * Async Loggers - performance similar to logging switched off * Custom log levels * Automatically reload its configuration upon modification without loosing log events during reconfigurations. * Java 8-style lambda support for lazy logging (which enables methods to be executed only when necessary, i.e.: the right log level) * Log4j 2 is garbage-free (or at least low-garbage) since version 2.6 * Plugin Architecture - easy to extend by building custom components * Log4j 2 API supports more than just logging Strings: CharSequences, Objects and custom Messages. Messages allow support for interesting and complex constructs to be passed through the logging system and be efficiently manipulated. Users are free to create their own Message types and write custom Layouts, Filters and Lookups to manipulate them. * Concurrency improvements: log4j2 uses java.util.concurrent libraries to perform locking at the lowest level possible. Log4j-1.x has known deadlock issues. * Configuration via XML, JSON, YAML, properties configuration files or programmatically. Regarding the upgrade: * To our devs: We are planning on merging #7131 as soon as 4.19 is released, this way, we will have plenty of time to fix any other PRs that might break with this change. If you have any issues regarding log4j2 in your PRs after the PR is merged, feel free to ping me (@JoaoJandre) on GitHub and I'll try my best to help you. Also, for any doubts, it might be a good idea to check the log4j documentation: https://logging.apache.org/log4j/2.x/manual/index.html. * To our users: For users that haven't tinkered with the default log configurations, this change should not bring any work to you, when installing ACS 4.20, your package manager should ask you if you want to upgrade your log4j configuration, please accept this, as the old configuration will not work anymore. For those who have made modifications to the default configuration, please take a look at this documentation: https://logging.apache.org/log4j/2.x/manual/migration.html#Log4j2ConfigurationFormat; it should help you migrate your custom configuration. In any case, if you have problems upgrading from 4.19 to 4.20, feel free to create a thread on the users list so that we can try to help you. I should remind you that 4.20 will only be launched in the end of Q2/start of Q3, so you'll have plenty of time to review what needs to be done regarding the log4j2 configuration. Best regards, João Jandre.
Re: [RESULT][VOTE] Apache CloudStack 4.19.0.0
Thanks Abhishek and everyone involved in the effort. And congratulations everyone ! Regards. From: Abhishek Kumar Sent: Friday, February 2, 2024 5:48:54 PM To: dev@cloudstack.apache.org ; users Subject: [RESULT][VOTE] Apache CloudStack 4.19.0.0 Hi all, After more than 72 hours, the vote for CloudStack 4.19.0.0 *passes* with 7 PMC + 3 non-PMC votes. +1 (PMC / binding) * Daan * Rohit * Nicolas * Nux * Harikrishna * Boris * Wei +1 (non binding) * Vladimir * Pearl * Suresh 0 none -1 none Thanks to everyone participating. I will now prepare the release announcement to go out after 24 hours to give the mirrors time to catch up. Regards, Abhishek
Re: [PR] feature: tagged resource limits [cloudstack-documentation]
vladimirpetrov commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923823587 I think we should also mention the new option for tagged template and the VM deployment wizard changes, @shwstppr. -- 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
[RESULT][VOTE] Apache CloudStack 4.19.0.0
Hi all, After more than 72 hours, the vote for CloudStack 4.19.0.0 *passes* with 7 PMC + 3 non-PMC votes. +1 (PMC / binding) * Daan * Rohit * Nicolas * Nux * Harikrishna * Boris * Wei +1 (non binding) * Vladimir * Pearl * Suresh 0 none -1 none Thanks to everyone participating. I will now prepare the release announcement to go out after 24 hours to give the mirrors time to catch up. Regards, Abhishek
Re: [VOTE] go life with new website(design)
+1 New website looks good. Thank you Daan and all involved, for your efforts! Regards, Suresh From: Daan Hoogland Date: Thursday, 1 February 2024 at 6:03 PM To: dev Subject: [VOTE] go life with new website(design) LS, I am not sure this is still needed after all the discussions before,but I would like to start a lazy consent vote threat anyway there are some non-blocking rest points mentioned and we can administer those in the repo for the site [1] so without further ado; Do we want to go life with the website as staged in cloudstack.staged.apache.org +1 yes 0 no opinion (no reaction suffices as well) -1 no (please state reasons [1] https://github.com/apache/cloudstack-www/issues/new/choose
Re: [PR] feature: tagged resource limits [cloudstack-documentation]
blueorangutan commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923452259 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/379. (QA-JID 204) -- 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] feature: tagged resource limits [cloudstack-documentation]
blueorangutan commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923450198 @shwstppr a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- 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] feature: tagged resource limits [cloudstack-documentation]
shwstppr commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923437033 @blueorangutan docbuild -- 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] feature: tagged resource limits [cloudstack-documentation]
blueorangutan commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923424058 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/379. (QA-JID 203) -- 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] feature: tagged resource limits [cloudstack-documentation]
blueorangutan commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923421181 @shwstppr a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- 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] feature: tagged resource limits [cloudstack-documentation]
shwstppr commented on PR #379: URL: https://github.com/apache/cloudstack-documentation/pull/379#issuecomment-1923418007 @blueorangutan docbuild -- 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
[PR] feature: tagged resource limits [cloudstack-documentation]
shwstppr opened a new pull request, #379: URL: https://github.com/apache/cloudstack-documentation/pull/379 https://github.com/apache/cloudstack/pull/8362 -- 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: [VOTE] go life with new website(design)
+1 (binding) Thanks, Harikrishna From: Daan Hoogland Date: Thursday, 1 February 2024 at 6:02 PM To: dev Subject: [VOTE] go life with new website(design) LS, I am not sure this is still needed after all the discussions before,but I would like to start a lazy consent vote threat anyway there are some non-blocking rest points mentioned and we can administer those in the repo for the site [1] so without further ado; Do we want to go life with the website as staged in cloudstack.staged.apache.org +1 yes 0 no opinion (no reaction suffices as well) -1 no (please state reasons [1] https://github.com/apache/cloudstack-www/issues/new/choose
