Re: [PR] service and disk offerings [cloudstack-terraform-provider]
adidiborg commented on PR #77: URL: https://github.com/apache/cloudstack-terraform-provider/pull/77#issuecomment-1940493371 > Hi @adidiborg welcome to the opensource project, I hear you and I hope the community can work towards a release soon. I hope the next TF release will be sometime in coming months. > > Anybody in the community can work to become a committer and PMC member, and lead release work who work in their "free" time, and it's highly encouraged that users and organisations participate and sponsor their team to work in the community. It's often seen many interested individuals and organisations come together to work on their features and sometimes releases, and often some organisations sponsor feature and maintenance work, and collaborate for testing and release work but not just limited to coding but also documentation, website, marketing and events. > > Everyone is welcome to start discussions on our dev@ and users@ mailing lists, in fact your comment would be more visible on the lists unless it was only specifically for me. thanks for responding, I will also try to contribute whereever I can -- 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
DeployDB failing on main
Hi, On main (I think on 4.19 also) there is an issue seen when deploying database using the command “mvn -Pdeveloper -pl developer -Ddeploydb” > Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker [WARNING] java.lang.reflect.InvocationTargetException at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:297) at java.lang.Thread.run (Thread.java:834) Caused by: java.lang.NullPointerException at java.io.Reader. (Reader.java:167) at java.io.InputStreamReader. (InputStreamReader.java:72) at com.cloud.upgrade.DatabaseUpgradeChecker.runScript (DatabaseUpgradeChecker.java:234) at com.cloud.upgrade.DatabaseUpgradeChecker.executeViewScripts (DatabaseUpgradeChecker.java:388) When I checked the code with debugger, I see NPE here https://github.com/apache/cloudstack/blob/d353fcc599d1c1e2ca4b58c6b793bcaf515a3f34/engine/schema/src/main/java/com/cloud/upgrade/DatabaseUpgradeChecker.java#L387-L388 here viewScript is null. This is happening when filePath is “/META-INF/db/views/cloud.service_offering_view.sql”. When I remove the initial back slash using the debugger “META-INF/db/views/cloud.service_offering_view.sql”, it has continued and deployDB has passed. Guto or anybody here, any idea why this is happening or am I missing anything ? Thanks, Harikrishna
Re: [PR] Document advance DRS settings [cloudstack-documentation]
rohityadavcloud merged PR #374: URL: https://github.com/apache/cloudstack-documentation/pull/374 -- 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] service and disk offerings [cloudstack-terraform-provider]
rohityadavcloud commented on PR #77: URL: https://github.com/apache/cloudstack-terraform-provider/pull/77#issuecomment-1940435831 Hi @adidiborg welcome to the opensource project, I hear you and I hope the community can work towards a release soon. I hope the next TF release will be sometime in coming months. Anybody in the community can work to become a committer and PMC member, and lead release work who work in their "free" time, and it's highly encouraged that users and organisations participate and sponsor their team to work in the community. It's often seen many interested individuals and organisations come together to work on their features and sometimes releases, and often some organisations sponsor feature and maintenance work, and collaborate for testing and release work but not just limited to coding but also documentation, website, marketing and events. Everyone is welcome to start discussions on our dev@ and users@ mailing lists, in fact your comment would be more visible on the lists unless it was only specifically for me. -- 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] service and disk offerings [cloudstack-terraform-provider]
adidiborg commented on PR #77: URL: https://github.com/apache/cloudstack-terraform-provider/pull/77#issuecomment-1939069300 Hi @rohityadavcloud, any tentative timelines when v0.5.0 would release? Already merged features could be of a lot of use -- 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: [PROPOSAL] version naming : drop the 4.
bump, @Daniel Salvador is there any technical reason to keep the 4? any reason why there must be a 5 instead of a 21, 22 or 23? We are maintaining 4 number semantic versioning for no reason, as I see it. On Tue, Jan 30, 2024 at 12:02 PM Daan Hoogland wrote: > > Daniel, "technical" reasons for dropping the 4 are all in the field of > social engineering. In practice (as I think Wei also described) we are > already treating the "minor" version number as major version. Since > 4.0 or 4.1 (don´t remember) there has been renewed talk of a 5 , but > never enough reason and or commitment to make it real. We could argue > about it a lot. > > so > ¨¨¨ > The main point is: *we have to understand the technical reasons for > the proposal and what we expect from it before deciding anything. > ¨¨¨ > The most important point is that we expect that people understand that > we treat the number that now seems to be "minor" as major release > numbers. > > > On Fri, Jan 26, 2024 at 7:42 PM Wei ZHOU wrote: > > > > Hi Daniel, > > > > If we are discussing 5.0, I would have the same concern as you. > > What we are discussing is dropping 4.x. The fact is, we will never release > > 5.0 (anyone disagree ?) > > In this case, the major version 4.x becomes useless. > > If we compare 4.20.0/4.21.0 with 20.0/21.0, it is obvious which is better. > > IMHO due to the similar reason, the Java version has been changed from 1.x > > to java 1.7/1.8 (=java 7/8) then to java 11/14/17. > > of course there will be some issues if semantic changes, I think it is > > under control. > > > > > > > > Regarding the compatibility, I think we can change the APIs gradually. > > I noticed the following recently when I tested VR upgrade to > > debian12/python3 > > > > root@r-431-VM:~# python > > Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux > > Type "help", "copyright", "credits" or "license" for more information. > > >>> import cgi > > :1: DeprecationWarning: 'cgi' is deprecated and slated for removal > > in Python 3.13 > > > > For the API changes you mentioned, we could try the similar > > - in version X, add new APIs, mark the old APIs as deprecated > > - tell users the old APIs will be removed in version Y, please use new APIs > > instead. > > - in version Y, remove the old APIs. > > > > This can be done in each major/minor release. No need to wait for 5.0. > > > > > > -Wei > > > > On Fri, 26 Jan 2024 at 18:51, Guto Veronezi wrote: > > > > > Exactly, so you understand now why we must discuss what we intend. > > > Although, incompatibilities are needed sometimes so we can evolve, > > > leaving old ways and deprecated technologies and techniques in the past. > > > > > > *The main point is: *we have to understand the technical reasons for the > > > proposal and what we expect from it before deciding anything. > > > > > > Best regards, > > > Daniel Salvador (gutoveronezi) > > > > > > > > > > > > > -- > Daan -- Daan
Re: [PROPOSE] RM for 4.19.1.0
Thanks for volunteering Suresh. Agree as Daan has mentioned, community would benefit to have the 4.18.2.0 first with some gap to then have 4.19.1.0. The 4.19.1 RC by May end or early June LGTM. Regards. From: Daan Hoogland Sent: Monday, February 12, 2024 5:25:44 PM To: dev@cloudstack.apache.org Cc: us...@cloudstack.apache.org Subject: Re: [PROPOSE] RM for 4.19.1.0 no worries as João proposed to release 4.18.2 in march, but let's make sure we have a good period between the two. On Mon, Feb 12, 2024 at 12:50 PM Suresh Anaparti wrote: > > Hi All, > > CloudStack 4.19.0.0 is the latest LTS release. There are already some open > issues [1] and pull requests [2] targeted for 4.19.1.0 [3] release. > > I'd like to propose and put myself forward as the release manager for > 4.19.1.0 if no objections there. Please ping me (@sureshanaparti) on GitHub, > in case you want to include any Issue/PR in 4.19.1.0. > > I propose to have a window of at least 8 weeks (2 months), which allows the > community / users to test, use 4.19.0.0 and report any issues. We can aim to > cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline > details soon. I hope to have your support. > > Please let me know if you have any thoughts/comments. > > [1] > https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0 > [2] > https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen > [3] https://github.com/apache/cloudstack/milestone/31 > > > Regards, > Suresh > > > -- Daan
Re: [PROPOSE] RM for 4.19.1.0
no worries as João proposed to release 4.18.2 in march, but let's make sure we have a good period between the two. On Mon, Feb 12, 2024 at 12:50 PM Suresh Anaparti wrote: > > Hi All, > > CloudStack 4.19.0.0 is the latest LTS release. There are already some open > issues [1] and pull requests [2] targeted for 4.19.1.0 [3] release. > > I'd like to propose and put myself forward as the release manager for > 4.19.1.0 if no objections there. Please ping me (@sureshanaparti) on GitHub, > in case you want to include any Issue/PR in 4.19.1.0. > > I propose to have a window of at least 8 weeks (2 months), which allows the > community / users to test, use 4.19.0.0 and report any issues. We can aim to > cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline > details soon. I hope to have your support. > > Please let me know if you have any thoughts/comments. > > [1] > https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0 > [2] > https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen > [3] https://github.com/apache/cloudstack/milestone/31 > > > Regards, > Suresh > > > -- Daan
[PROPOSE] RM for 4.19.1.0
Hi All, CloudStack 4.19.0.0 is the latest LTS release. There are already some open issues [1] and pull requests [2] targeted for 4.19.1.0 [3] release. I'd like to propose and put myself forward as the release manager for 4.19.1.0 if no objections there. Please ping me (@sureshanaparti) on GitHub, in case you want to include any Issue/PR in 4.19.1.0. I propose to have a window of at least 8 weeks (2 months), which allows the community / users to test, use 4.19.0.0 and report any issues. We can aim to cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline details soon. I hope to have your support. Please let me know if you have any thoughts/comments. [1] https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0 [2] https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen [3] https://github.com/apache/cloudstack/milestone/31 Regards, Suresh
Re: [PR] systemvm: Update patch systemvm support matrix [cloudstack-documentation]
blueorangutan commented on PR #382: URL: https://github.com/apache/cloudstack-documentation/pull/382#issuecomment-1938243169 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/382. (QA-JID 212) -- 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] systemvm: Update patch systemvm support matrix [cloudstack-documentation]
blueorangutan commented on PR #382: URL: https://github.com/apache/cloudstack-documentation/pull/382#issuecomment-1938241764 @weizhouapache 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] systemvm: Update patch systemvm support matrix [cloudstack-documentation]
weizhouapache commented on PR #382: URL: https://github.com/apache/cloudstack-documentation/pull/382#issuecomment-1938241099 @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] systemvm: Update patch systemvm support matrix [cloudstack-documentation]
weizhouapache opened a new pull request, #382: URL: https://github.com/apache/cloudstack-documentation/pull/382 (no comment) -- 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
