Re: [DISCUSS] CloudStack Website build and modernisation
All, Update - the first iteration of the website+blog PoC is ready for review for the community: https://beautiful-pastelito-4eb422.netlify.app/ Except for a few new pages and blogs, I've ported most of the content from the old website and blog to this PoC. Thanks. Regards. From: Rohit Yadav Sent: Monday, May 1, 2023 11:24 To: dev@cloudstack.apache.org Cc: priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation All, The ASF infra has advised deprecating and removing Roller support by 31st May 2023, our project blog is based on Roller. Since my previous mail, I have been reviewing alternatives and options that are compliant with ASF policies and have looked at several other top-level Apache projects on how they manage, maintain, and publish their websites and blogs. For reference, some of that progress and options have been discussed at https://issues.apache.org/jira/browse/INFRA-24170 In order to have an ASF-compliant website and blog setup that would be more inclusive for our non-technical contributors, I've set up a proof-of-concept blog+website [1] using Docusauras (and configs from one of the ASF project websites, treat all the content outside of the blog as placeholder pages or lorem-ipsum) which is a static-site generator used by a dozen other Apache TLP websites [0] such as Apisix, Pulsar etc. This PoC has all most of our blog migrated (except the most 4-6 new ones), but pending migration of website content; and is currently integrated with a Netlify CMS which isn't as rich as WP but allows a committer/PMC to login via Github and manage the website+blog using a rich-text markdown editor [1][2] where editing/saving content created git commits pushed to Github. I'm also looking at other headless git-based CMSs that we can use. We may revisit any design/theme changes in the future, if there are no objections as the first iteration I propose to migrate all our project website content along with the Roller blog to this PoC and ask interested contributors to review and collaborate in an on-going basis as we need to migrate the blog by 31st May '23. I hope to update again regularly. [0] https://github.com/search?q=org%3Aapache+docusaurus.config.js=code [1] https://beautiful-pastelito-4eb422.netlify.app/blog/ [2] https://beautiful-pastelito-4eb422.netlify.app/admin/ Thanks and regards. From: Rohit Yadav Sent: Wednesday, February 8, 2023 15:07 To: dev@cloudstack.apache.org Cc: priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation All, The ASF infra has advised recently that they're deprecating and removing Roller support, our project blog is based on Roller. Given this hasn't received any objections on this thread, I've spent some time in the last two months exploring options that solve most of our website and blog requirements. I explored several other top-level ASF project websites and found they had built their website/blog/article using something like Pelican, Hugo, Jekyll and recently Docusaurus. Among these Jekyll is the oldest and most stable platform that Github supports out of the box. Most of these TLP websites use a CI/CD based staging->publishing pipeline, using Github Actions, Gitpod, Netlify etc. Among these various options, Docusaurus seems to satisfy many of the requirements and integrates with Netlify CMS (to support our marketing contributors who aren't necessarily git-experts; https://www.netlifycms.org/docs/docusaurus/). If there aren't any objections I would like to set up a staging/beta website (as per https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories this can be configured, using default it would be on cloudstack.staged.apach.org). Example TLP website source repos: Docusaurus: https://github.com/apache/apisix-website https://github.com/apache/shenyu-website https://github.com/apache/incubator-kvrocks-website Jekyll: https://github.com/apache/openwhisk-website https://github.com/apache/nuttx-website Hugo: https://github.com/apache/kyuubi-website https://github.com/apache/hop-website https://github.com/apache/dubbo-website Regards. From: Rohit Yadav Sent: Monday, December 19, 2022 14:57 To: dev@cloudstack.apache.org Subject: [DISCUSS] CloudStack Website build and modernisation All, For 4.17.2.0 release publication on the website, I had to manually edit the website [0] build as I couldn't get middleman to work on either Ubuntu 20.04, 22.04 (after spending a good hour to fix the ruby/gems build system). Any pointers on getting middleman/gems to work? As our website is dated, and in the past ASF infra has advised against setting up a dynamic CMS such as Wordpres for us I'm looking into alternatives that are ASF infra approved [1] and looking into
Re: [PROPOSE] RM for 4.19.0
+1, thanks Abhishek. I know we’re in safe hands with you! Bobby. From: Harikrishna Patnala Date: Monday, 1 May 2023, 9:21 To: us...@cloudstack.apache.org , dev@cloudstack.apache.org Subject: Re: [PROPOSE] RM for 4.19.0 +1, thanks for volunteering and good luck Abhishek. Regards, Harikrishna From: Abhishek Kumar Date: Sunday, 30 April 2023 at 10:23 PM To: dev@cloudstack.apache.org , us...@cloudstack.apache.org Subject: [PROPOSE] RM for 4.19.0 Dear All, I would like to propose and put myself forward as the release manager for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of releases before that. I would like to take experiences from those to work on a successful release. I propose we start early, sometime in Q3 2023, with the planning, triaging, bug-fixing, etc to get back on the traditional two-release per year cycle. With this we can aim to cut the RC sometime in October. I will propose a detailed timeline soon. I hope to have your support. Please let me know if you have any thoughts/comments. Regards, Abhishek
[VOTE] Release Apache CloudStack CloudMonkey 6.3.0 - RC1
Hi All, I've created a v6.3.0 release of CloudMonkey, with the following artifacts up for a vote: Git Branch and commit SHA: https://github.com/apache/cloudstack-cloudmonkey/commit/860771ad1e2a759a8099a4dbeb264c342e3b9577 Commit: 860771ad1e2a759a8099a4dbeb264c342e3b9577 GitHub pre-release (for RC1 testing, contains changelog, artifacts/binaries to test, checksums/usage details): https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.3.0 Source release (checksums and signatures are available at the same location): https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.3.0/ PGP release keys (signed using 4A64E2F46BBC136DD92D71FB5B7DEFE0508A4AD8) https://dist.apache.org/repos/dist/release/cloudstack/KEYS The vote will be open until 5th May, 2023. 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 the reason why)
Re: ACS upgrade to Log4J2 version 2.19
Abhishek, I do not see why it would be a 5.0 change. Also, ACS 5.0 is a discussion the community has been having for a long time from now and is something we are too far away to achieve consensus. The patch is important to enable further development for the log management on ACS and facilitate everyone's life while coding and troubleshooting. If you think it is too much work for the RM, I reiterate that I am willing to be the 4.19 RM and conduct/execute all of the work. Best regards, Daniel Salvador (gutoveronezi) On Mon, May 1, 2023 at 4:10 AM Abhishek Kumar wrote: > Great work. > Though I feel this is a 5.0 change. I agree with Wei that this would create > too much overhead for upcoming releases. 4.18 was pushed ahead a few months > and we may end up on a similar path. > Also, reload4j is still actively maintained so I don't think this is > urgent. > > Regards, > Abhishek > > On Fri, 28 Apr 2023 at 18:28, João Jandre Paraquetti > > wrote: > > > In PR #7131 (https://github.com/apache/cloudstack/pull/7131) I have > > proposed to normalize ACS's loggers, and more importantly, upgrade the > > library log4j to log4j2 version 2.19. > > > > Log4j2 has a lot of features that could offer benefits to ACS: > > > > * 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 is separated from the Log4j 2 implementation. > > * 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. > > > > In my personal experience using it in some other projects, log4j2 is > > easier to work with in general, has better performance, and is an active > > project with constant development, innovation, and security patches. > > Moreover, it is under a well known and trusted open source organization. > > > > The change proposed in PR #7131 > > (https://github.com/apache/cloudstack/pull/7131) has been tested and > > validated in a lot of different scenarios by different people. We have > > already tested the logging in the management server, usage, agents, and > > system VMs; all of that using KVM and Vmware + Veeam. Most feature sets > > were tested, create/delete/update VMs, disks, cresate snapshots, user > > management and so on. > > > > The proposal has been discussed since January, 2023 in the PR > > (https://github.com/apache/cloudstack/pull/7131), but I have been > > requested to bring it to the mailing list. I would love to hear your > > opinions on it, also, any reviews to the PR would be welcome. >
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #313: Add docs for scheduling operations on a VM
blueorangutan commented on PR #313: URL: https://github.com/apache/cloudstack-documentation/pull/313#issuecomment-1529507294 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/313. (QA-JID 73) -- 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
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #313: Add docs for scheduling operations on a VM
blueorangutan commented on PR #313: URL: https://github.com/apache/cloudstack-documentation/pull/313#issuecomment-1529506467 @rohityadavcloud 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
[GitHub] [cloudstack-documentation] rohityadavcloud commented on pull request #313: Add docs for scheduling operations on a VM
rohityadavcloud commented on PR #313: URL: https://github.com/apache/cloudstack-documentation/pull/313#issuecomment-1529505720 @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
[GitHub] [cloudstack-documentation] rohityadavcloud commented on pull request #313: Add docs for scheduling operations on a VM
rohityadavcloud commented on PR #313: URL: https://github.com/apache/cloudstack-documentation/pull/313#issuecomment-1529505075 @blueorangutan docbuild (@vishesh92 you can kick this yourself in future) -- 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: ACS upgrade to Log4J2 version 2.19
Great work. Though I feel this is a 5.0 change. I agree with Wei that this would create too much overhead for upcoming releases. 4.18 was pushed ahead a few months and we may end up on a similar path. Also, reload4j is still actively maintained so I don't think this is urgent. Regards, Abhishek On Fri, 28 Apr 2023 at 18:28, João Jandre Paraquetti wrote: > In PR #7131 (https://github.com/apache/cloudstack/pull/7131) I have > proposed to normalize ACS's loggers, and more importantly, upgrade the > library log4j to log4j2 version 2.19. > > Log4j2 has a lot of features that could offer benefits to ACS: > > * 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 is separated from the Log4j 2 implementation. > * 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. > > In my personal experience using it in some other projects, log4j2 is > easier to work with in general, has better performance, and is an active > project with constant development, innovation, and security patches. > Moreover, it is under a well known and trusted open source organization. > > The change proposed in PR #7131 > (https://github.com/apache/cloudstack/pull/7131) has been tested and > validated in a lot of different scenarios by different people. We have > already tested the logging in the management server, usage, agents, and > system VMs; all of that using KVM and Vmware + Veeam. Most feature sets > were tested, create/delete/update VMs, disks, cresate snapshots, user > management and so on. > > The proposal has been discussed since January, 2023 in the PR > (https://github.com/apache/cloudstack/pull/7131), but I have been > requested to bring it to the mailing list. I would love to hear your > opinions on it, also, any reviews to the PR would be welcome.
[GitHub] [cloudstack-cloudmonkey] rohityadavcloud commented on pull request #129: Optimizing network.go
rohityadavcloud commented on PR #129: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/129#issuecomment-1529405561 Agree, we can merge this after 6.3 is out @borisstoyanov -- 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: [PROPOSE] RM for 4.19.0
+1, thanks for volunteering and good luck Abhishek. Regards, Harikrishna From: Abhishek Kumar Date: Sunday, 30 April 2023 at 10:23 PM To: dev@cloudstack.apache.org , us...@cloudstack.apache.org Subject: [PROPOSE] RM for 4.19.0 Dear All, I would like to propose and put myself forward as the release manager for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of releases before that. I would like to take experiences from those to work on a successful release. I propose we start early, sometime in Q3 2023, with the planning, triaging, bug-fixing, etc to get back on the traditional two-release per year cycle. With this we can aim to cut the RC sometime in October. I will propose a detailed timeline soon. I hope to have your support. Please let me know if you have any thoughts/comments. Regards, Abhishek
