[GitHub] [cloudstack-documentation] sureshanaparti commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
sureshanaparti commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699043722 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. Review comment: ```suggestion Instead of those APIs, it can be performed directly using change offering for volume operation. ``` I think, no need to explicitly mention supported from UI (as the doc is primarily with respect to UI) -- 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] sureshanaparti commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
sureshanaparti commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699044798 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. +Upon changing the disk offering the volume will be resized and/or migrated to the suitable storage pool if required according to the new disk offering. + +Global setting "match.storage.pool.tags.with.disk.offering" gives flexibility or control to choose the new disk offering. Review comment: ```suggestion The zone level setting "match.storage.pool.tags.with.disk.offering", gives flexibility or control to choose the new disk offering. ``` -- 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] DaanHoogland commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
DaanHoogland commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699046278 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. Review comment: ```suggestion Instead of using these APIs directly, the operation can be performed in the UI using change offering in the details view for the volume. ``` -- 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: Console proxy creation failure
Hi At just a glance, It looks like there isn't sufficient memory for the Console proxy to come up (by default it needs 1024 MB) Try adding more memory or increasing the memory overprovisioning factor in the configuration / global settings tab From: technologyrss.mail Sent: Tuesday, August 31, 2021 12:31 PM To: us...@cloudstack.apache.org ; dev@cloudstack.apache.org Subject: Console proxy creation failure Hi, I am able to setup ACS using centos 7.9. all service are properly working fine. But when I create basic zone then I see error like below . ACS server : Centos 0s 7.9 NFS server : Centos 0s 7.8 KVM server : Centos 0s 7.8 [cid:part1.B6819867.0C83CE47@gmail.com] Secondary Storage VM working fine but can't start proxy vm. what is issue? [cid:part2.99CE7C85.B5717BC5@gmail.com] This is system capacity like as below. [cid:part3.389FB6FD.77D44A7C@gmail.com] Please give me any idea.. Thanks, Alamin
[GitHub] [cloudstack-go] psycofdj commented on pull request #7: Fix generator for map parameters that are lists of objects
psycofdj commented on pull request #7: URL: https://github.com/apache/cloudstack-go/pull/7#issuecomment-909104097 Everything works fine on my production environment, I removed the WIP status. -- 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] harikrishna-patnala commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699254953 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. Review comment: I've updated with Daan's version. -- 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] harikrishna-patnala commented on pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172197 @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] blueorangutan commented on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172731 @harikrishna-patnala 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] blueorangutan commented on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909173546 Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/238. (SL-JID 134) -- 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-go] pdion891 commented on pull request #7: Fix generator for map parameters that are lists of objects
pdion891 commented on pull request #7: URL: https://github.com/apache/cloudstack-go/pull/7#issuecomment-909192455 @psycofdj , Thanks for the PR, I fixed some output issues in `cloudstack/HostService.go` recently, and I was not aware of the interaction with `generate/generate.go`. -- 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-go] pdion891 merged pull request #7: Fix generator for map parameters that are lists of objects
pdion891 merged pull request #7: URL: https://github.com/apache/cloudstack-go/pull/7 -- 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
[DISCUSS] Export Virtual Router Statistics to Users
Hey there, We want to improve virtual router statistic visibility. One option that pops into my mind is to export some statistics in router VM in Prometheus format and let our customers do what they like with those data. It enabled our customers to find packet loss, memory usage, etc. Based on these data, they can create their alert and dashboard. If we implement this feature, is this going to merge into upstream? Another option is to have these data visible in cloudstack dashboard in some graph directly. Please let me know if you have a better solution to address this issue? Kind regards, Sina signature.asc Description: OpenPGP digital signature
Re: [DISCUSS] 4.15.2.0
All, Since nobody has objected or volunteered I would continue as RM for 4.15.2.0 release. The total no. of outstanding issues and PRs are around 20 with about 80 issues/PRs already merged/closed towards the milestone. The most recent test matrix smoketests on 4.15 health PR has also passed. To avoid conflicting timeline with 4.16 I propose to cut RC1 by end of this week or next week as soon as any outstanding blocker/critical/major bug fix PRs are reviewed/tested/merged. I request comments from the community on this and if anybody wants to report any blocker/critical issues/bugs found in 4.15.1.0. Thanks and regards. From: Rohit Yadav Sent: Saturday, August 21, 2021 4:36:38 PM To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: Re: [DISCUSS] 4.15.2.0 Great thanks all, looks like we all think doing a quick and stable 4.15.2.0 would be a good idea. Any volunteers for RM? I'm happy do it or help the volunteer as well. Regards. From: Nicolas Vazquez Sent: Friday, August 20, 2021 6:15:47 PM To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: Re: [DISCUSS] 4.15.2.0 +1 Regards, Nicolas Vazquez From: Rohit Yadav Sent: Thursday, August 19, 2021 7:54 AM To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] 4.15.2.0 All, I want to kick a thread to discuss and gather interest from the community on doing a 4.15.2.0 release, before Nicolas (our RM) cuts 4.16.0.0 RC1 around the end of Sept '21. We can keep the scope really tight to include only important fixes, I see about 50 closed issues/PRs already on the 4.15.2.0 milestone and some 30 remaining: https://github.com/apache/cloudstack/milestone/20 I'm hoping the 4.15.2.0 release can be a quick stable minor release, I can do it and any other volunteer RM may do it. Whoever does it, here's my proposal is: * Limit the scope to very specific do-able bug-fixes up to end the month - so gives us roughly 2 weeks * Cut RC1 in the first week of Sept * Assuming the RC1 would be stable enough as 4.15 branch is quite stable, worst case we've another RC2 * Conclude release work by mid or end of Sept before 4.16.0.0 RC1 is cut; so 4.15.2.0 release work doesn't cause delay for 4.16.0.0 Thoughts? Thanks and regards.
[GitHub] [cloudstack-documentation] harikrishna-patnala commented on pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172197 @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-go] pdion891 commented on pull request #7: Fix generator for map parameters that are lists of objects
pdion891 commented on pull request #7: URL: https://github.com/apache/cloudstack-go/pull/7#issuecomment-909192455 @psycofdj , Thanks for the PR, I fixed some output issues in `cloudstack/HostService.go` recently, and I was not aware of the interaction with `generate/generate.go`. -- 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 #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172731 -- 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-cloudmonkey] rhtyd closed issue #94: add human readable output
rhtyd closed issue #94: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/94 -- 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-cloudmonkey] rhtyd commented on issue #94: add human readable output
rhtyd commented on issue #94: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/94#issuecomment-908915481 The linked PR fixes the formatting issue, however it doesn't do what @pdion891 has asked - PL please check if the PR is sufficient to close the ticket? -- 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] sureshanaparti commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
sureshanaparti commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699043722 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. Review comment: ```suggestion Instead of those APIs, it can be performed directly using change offering for volume operation. ``` I think, no need to explicitly mention supported from UI (as the doc is primarily with respect to UI) ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. +Upon changing the disk offering the volume will be resized and/or migrated to the suitable storage pool if required according to the new disk offering. + +Global setting "match.storage.pool.tags.with.disk.offering" gives flexibility or control to choose the new disk offering. Review comment: ```suggestion The zone level setting "match.storage.pool.tags.with.disk.offering", gives flexibility or control to choose the new disk offering. ``` -- 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-cloudmonkey] rhtyd edited a comment on issue #94: add human readable output
rhtyd edited a comment on issue #94: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/94#issuecomment-908915481 The linked PR fixes the formatting issue, however it doesn't do what @pdion891 has asked - PL please check if the PR is sufficient to close the ticket as ideally the human readable change should come from API key so the CLI shouldn't alter the response too much. -- 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-go] pdion891 merged pull request #7: Fix generator for map parameters that are lists of objects
pdion891 merged pull request #7: URL: https://github.com/apache/cloudstack-go/pull/7 -- 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-cloudmonkey] rhtyd merged pull request #95: Display output in human readable format
rhtyd merged pull request #95: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/95 -- 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-go] psycofdj commented on pull request #7: Fix generator for map parameters that are lists of objects
psycofdj commented on pull request #7: URL: https://github.com/apache/cloudstack-go/pull/7#issuecomment-909104097 Everything works fine on my production environment, I removed the WIP status. -- 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] DaanHoogland commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
DaanHoogland commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699046278 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. Review comment: ```suggestion Instead of using these APIs directly, the operation can be performed in the UI using change offering in the details view for the volume. ``` -- 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] harikrishna-patnala commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala commented on a change in pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699254953 ## File path: source/adminguide/storage.rst ## @@ -661,6 +661,37 @@ The following table shows possible combinations of Service offering supported re Shrinking the Root disk is not supported via the service offering resizing workflow. All the combinations above assume a transition to Root disks with size equals or bigger than the original. Service Offerings with Root size of 0GB do not change the disk size to Zero and indicates that the offering do not enforces a Root disk size. +Change disk offering for volume +~~~ + +There are volume operations like migrate volume and resize volume and both accepts new disk offering to replace the existing disk offering of volume. +Instead of those APIs, Disk offering of a volume can be changed directly using changeOfferingForVolume API, also supported from UI. Review comment: I've updated with Daan's version. -- 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
[Discussion] Release Cycle
Hello, I would like to open a discussion regarding the project release cycle. More specifically on the following topics: 1. LTS and Regular releases 2. Releases period 3. Enhance roadmap and Release cycle for users 1 LTS and Regular releases It has been a while since the last regular release. Nowadays there are only LTS releases; maybe we should get back to having regular versions in between LTS. With a “Regular” release users would be able to trade stability for new features. Additionally, developers and users would have a “pilot” of the next LTS which could anticipate issues and result in a stable long-term release. Please, let me know what you think of this. Should we get back to releasing Regular releases in between LTS releases? For reference, here follow the past releases: +-+-+--+-+ | Release | Type| Release date | EOL | +-+-+--+-+ | 4.15| LTS | 19 Jan 2021 | 1 July 2022 | +-+-+--+-+ | 4.14| LTS | 26 May 2020 | 1 Jan 2022 | +-+-+--+-+ | 4.13| LTS | 24 Sep. 2019 | 1 May 2021 | +-+-+--+-+ | 4.12| Regular | 4 April 2019 | N/A | +-+-+--+-+ | 4.11| LTS | 12 Feb. 2018 | 1 July 2019 | +-+-+--+-+ | 4.10| Regular | 6 July 2017 | N/A | +-+-+--+-+ | 4.9 | LTS | 25 July 2016 | 1 July 2018 | +-+-+--+-+ 2 Releases period We had in the past a new LTS per year. Then, we got into two new LTS per year. This led from having 2 LTS maintained at the same time to 3. With that said, I think this is neither documented nor has it been discussed in the ML. We have the LTS minimum and maximum support dates well defined, but so far there is no definition/guidelines towards the release period. I would like to open this discussion so we can update the CloudStack wiki page [https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS] and have a clear definition of when the community should expect each release. 3 Enhance roadmap and Release cycle for users This topic is an extension of Topic 2. Once we have “Topic 2” well defined we will be able to present a draft of future releases. The main idea of this email is to look for project stability and predictability with a release cycle/roadmap similar to what is done by Ubuntu [https://ubuntu.com/about/release-cycle]. We would then be able to give users and developers a roadmap to look after. I would also suggest such a release cycle to be presented on the website, in addition to the “cwiki” page [ https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS]. Please let me know what you think. Best regards, Gabriel.
Fwd: Console proxy creation failure
*Thank you so much ! *Yes, RAM issue. I increase RAM then fix but I see different error like I can't access vm console from browser. Please see below image. ACS log file from below link. https://drive.google.com/file/d/15C20k1wYlDFNReyY1iYoyfRdJodwdxiU/view?usp=sharing *---** **Alamin.* On 8/31/2021 2:38 PM, David Jumani wrote: Hi At just a glance, It looks like there isn't sufficient memory for the Console proxy to come up (by default it needs 1024 MB) Try adding more memory or increasing the memory overprovisioning factor in the configuration / global settings tab *From:* technologyrss.mail *Sent:* Tuesday, August 31, 2021 12:31 PM *To:* us...@cloudstack.apache.org ; dev@cloudstack.apache.org *Subject:* Console proxy creation failure *Hi,* I am able to setup ACS using centos 7.9. all service are properly working fine. But when I create basic zone then I see error like below . ACS server : Centos 0s 7.9 NFS server : Centos 0s 7.8 KVM server : Centos 0s 7.8 Secondary Storage VM working fine but can't start proxy vm. what is issue? This is system capacity like as below. Please give me any idea.. *Thanks, Alamin*
Re: [Discussion] Release Cycle
Hi Gabriel, 1. I'm a +1 on having regular releases between LTS ones and the reasoning behind it. While stability is great, it will also be nice to have a "pilot" as you mentioned which the community can test and issues are resolved in the following LTS, rather than waiting for 2 - 3 releases to get something allegedly stable in, which could still have issues reported by users. 2. I'm for having 1 Regular release (Mar-Apr) followed by an LTS one (~6 months down the line) each year. Wrt the LTS releases, they should be supported for 1.5 to 2 years (at least 6 months after the following LTS is out). If that might be too much then a single alternating release annually around the same dates 3. No strong opinion on this but it does seem like a good idea, but not sure how religiously people will update the new page with every feature they intend to add and follow up on it From: Gabriel Bräscher Sent: Tuesday, August 31, 2021 11:14 PM To: dev Subject: [Discussion] Release Cycle Hello, I would like to open a discussion regarding the project release cycle. More specifically on the following topics: 1. LTS and Regular releases 2. Releases period 3. Enhance roadmap and Release cycle for users 1 LTS and Regular releases It has been a while since the last regular release. Nowadays there are only LTS releases; maybe we should get back to having regular versions in between LTS. With a “Regular” release users would be able to trade stability for new features. Additionally, developers and users would have a “pilot” of the next LTS which could anticipate issues and result in a stable long-term release. Please, let me know what you think of this. Should we get back to releasing Regular releases in between LTS releases? For reference, here follow the past releases: +-+-+--+-+ | Release | Type| Release date | EOL | +-+-+--+-+ | 4.15| LTS | 19 Jan 2021 | 1 July 2022 | +-+-+--+-+ | 4.14| LTS | 26 May 2020 | 1 Jan 2022 | +-+-+--+-+ | 4.13| LTS | 24 Sep. 2019 | 1 May 2021 | +-+-+--+-+ | 4.12| Regular | 4 April 2019 | N/A | +-+-+--+-+ | 4.11| LTS | 12 Feb. 2018 | 1 July 2019 | +-+-+--+-+ | 4.10| Regular | 6 July 2017 | N/A | +-+-+--+-+ | 4.9 | LTS | 25 July 2016 | 1 July 2018 | +-+-+--+-+ 2 Releases period We had in the past a new LTS per year. Then, we got into two new LTS per year. This led from having 2 LTS maintained at the same time to 3. With that said, I think this is neither documented nor has it been discussed in the ML. We have the LTS minimum and maximum support dates well defined, but so far there is no definition/guidelines towards the release period. I would like to open this discussion so we can update the CloudStack wiki page [https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS] and have a clear definition of when the community should expect each release. 3 Enhance roadmap and Release cycle for users This topic is an extension of Topic 2. Once we have “Topic 2” well defined we will be able to present a draft of future releases. The main idea of this email is to look for project stability and predictability with a release cycle/roadmap similar to what is done by Ubuntu [https://ubuntu.com/about/release-cycle]. We would then be able to give users and developers a roadmap to look after. I would also suggest such a release cycle to be presented on the website, in addition to the “cwiki” page [ https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS]. Please let me know what you think. Best regards, Gabriel.
[GitHub] [cloudstack-documentation] harikrishna-patnala removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala removed a comment on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172197 @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] harikrishna-patnala commented on pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909930146 @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] blueorangutan removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan removed a comment on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172731 -- 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 #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909930893 @harikrishna-patnala 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] blueorangutan commented on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909931636 Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/238. (SL-JID 135) -- 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] rhtyd removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes
rhtyd removed a comment on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-907083590 @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] blueorangutan removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan removed a comment on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-907083866 -- 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] harikrishna-patnala removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala removed a comment on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909930146 @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] blueorangutan removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan removed a comment on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909930893 -- 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] harikrishna-patnala commented on pull request #238: Update service offering section with new compute offering and disk offering changes
harikrishna-patnala commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909948663 @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] blueorangutan commented on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909949767 @harikrishna-patnala 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] blueorangutan commented on pull request #238: Update service offering section with new compute offering and disk offering changes
blueorangutan commented on pull request #238: URL: https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909950668 Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/238. (SL-JID 136) -- 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
