Re: [PR] Replace Hyper-V with KVM [cloudstack-documentation]
sureshanaparti commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320433501 @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] Replace Hyper-V with KVM [cloudstack-documentation]
blueorangutan commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320437120 @sureshanaparti 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] Replace Hyper-V with KVM [cloudstack-documentation]
blueorangutan commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320439584 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/430. (QA-JID 255) -- 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] Replace Hyper-V with KVM [cloudstack-documentation]
sureshanaparti commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320462516 @rajujith can you check/update here as well https://github.com/apache/cloudstack-documentation/blob/aad0fed3c97e8f4bcf1438cafb2e57427ef31c04/source/adminguide/networker_plugin.rst?plain=1#L71 -- 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] Replace Hyper-V with KVM [cloudstack-documentation]
sureshanaparti commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320511657 @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] Replace Hyper-V with KVM [cloudstack-documentation]
blueorangutan commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320514443 @sureshanaparti 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] Replace Hyper-V with KVM [cloudstack-documentation]
blueorangutan commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320516988 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/430. (QA-JID 256) -- 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] Replace Hyper-V with KVM [cloudstack-documentation]
sureshanaparti commented on PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430#issuecomment-2320521823 Verified -- 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] Replace Hyper-V with KVM [cloudstack-documentation]
sureshanaparti merged PR #430: URL: https://github.com/apache/cloudstack-documentation/pull/430 -- 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: Port Forwarding in Network
Hi Bryan, Indeed, your use case is extreme, I'd highly recommend using more networks with less autoscale groups. On making the VRs redundant, that will take even more resources than standalone routers and won't really give you much extra uptime. Regards, Alex -Original Message- From: Bryan Tiang Sent: Thursday, August 29, 2024 9:09 PM To: us...@cloudstack.apache.org; us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subject: Re: Port Forwarding in Network We update the VR offering to be 4 Core, 4GB. Its a single router setup atm but we’re going to make it redundant soon. Also, we have a 3rd case which i forgot to mention. Internet/Leased Line -> ASG LB (API GW) -> Private Gateway to another VPC within same zone -> ASG LB (Microservice 3) -> DB This scenario is meant to route traffic from VPC A (API GW only) to many other customer VPCs. Regards, Bryan On 30 Aug 2024 at 1:48 AM +0800, Wei ZHOU , wrote: > Thanks for sharing. Interesting > > How many cpu and memory does you VR have ? > > > -Wei > On Thursday, August 29, 2024, Bryan Tiang wrote: > > > Hi Alex and Wei Zhou, > > > > Thanks for the input, so it seems this new feature is more > > beneficial for those who are currently using Shared Networks. > > > > We have 50 AutoscaleGroups in a single VR because our company mainly > > distributes/broadcasts stock prices from multiple exchanges to > > public users, so lots of micro services that need to autoscale > > instantaneously when the markets suddenly spike/rally which can > > result in 1 - 10x traffic bursts. > > > > However, most of our Autoscale Groups consists of API Gateways to > > route traffic to different network tiers and micro services. This is > > what takes up lots of Autoscale Groups. > > > > We had to duplicate lots of API Gateway into multiple Autoscale > > Groups because the current feature only allows load balancing to 1 single > > port. > > > > So this is more of a workaround for us to overcome the current > > Autoscale feature limitation. > > > > I think something worth mentioning is that our Autoscale Group, load > > balances traffic to other Autoscale Groups. > > > > For example: > > > > Internet -> ASG LB (API GW) -> ASG LB (Microservice 1) -> Database > > > > And in some cases, we have this as well: > > > > Internet -> ASG LB (API GW) -> ASG LB (Microservice 1) -> ASG LB > > (Microservice 2)-> Database > > > > I guess makes the VR very busy. > > > > Happy to share more, sounds like our use is bit extreme… but it > > works so far though. Its only the CPU Utilisation that’s concerning… > > (memory is always around 40% so not a bottleneck there) > > > > Regards, > > Bryan > > On 29 Aug 2024 at 11:27 PM +0800, Alex Mattioli < > > alex.matti...@shapeblue.com>, wrote: > > > Hi Bryan, > > > > > > What's your use case for 50 autoscale groups in 1 VR? When > > > designing the > > feature we never envisioned more than 2 or 3. > > > > > > In NAT mode you should be able to get some 3gpbs through the VR, > > > in > > ROUTED mode then some 6-7gbps. Those numbers do go down > > (considerably > > sometimes) with the number of firewall rules, load balancing, etc... > > you have setup in the network. > > > > > > You'll need to create new networks in ROUTED mode, there's no > > > migration > > path from NATTED mode to ROUTED mode. > > > > > > You definitely can allow all traffic in the firewall and setup > > > firewall > > rules in each individual VM. > > > > > > In this initial implementation there's no load balancer in ROUTED > > > mode, > > so no Autoscale groups. But it is definitely a possible improvement > > for future versions. > > > > > > Cheers > > > Alex > > > > > > > > > > > > > > > -Original Message- > > > From: Bryan Tiang > > > Sent: Thursday, August 29, 2024 11:11 AM > > > To: us...@cloudstack.apache.org; us...@cloudstack.apache.org > > > Cc: dev@cloudstack.apache.org > > > Subject: RE: Port Forwarding in Network > > > > > > Hey Alex, > > > > > > It’s exiting to hear this new features coming about, and that the > > > VR > > performance will be improved as a result of pure routing. > > > > > > We have a pain point right now where our VR is at 75% CPU when > > > handling > > 200Mbps Internet Traffic. Probably because we have 50 Autoscale > > Groups within that 1 VR… (VR is 4Core,4GB). > > > > > > We have plans support 1Gb-5Gbps Internet Bandwidth within a single > > > VR > > one day, but if it’s already at 75%… kinda worrying for us. So this > > is exciting. > > > > > > I went through the design document and have few questions. Is this > > > going > > to be a new network? Or can existing VPC networks upgrade to Routed Mode? > > > > > > Since every VM will get to have its own Public IP, does it mean > > > every VM > > can have its own firewall rules now? > > > > > > Will this feature be available for Autoscale Groups? We are heavy > > > users > > of it. > > > > > > Regards, > > > Bryan > > > On 29 Aug 2024 at 4:22 A
[PR] tuning: note on db connection pool [cloudstack-documentation]
shwstppr opened a new pull request, #431: URL: https://github.com/apache/cloudstack-documentation/pull/431 Related to https://github.com/apache/cloudstack/pull/9518 -- 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
New Sponsorship Opportunity for the CloudStack Collaboration Conference
Hi All, I would like to announce that we are launching a new sponsorship opportunity for the CloudStack Collaboration Conference - Digital Sponsorship Package. We ere approached by a few small companies, which wanted to contribute to the event, but the available packages were not fitting their travel plans or budget. For this reason we tailored a package, which is budget-friendly and enables small and mid-sized companies to help the community - Digital Sponsorship. The package includes: - 2 x Sponsored social media posts on the official CloudStack social media (LinkedIn and X) - 1 sponsored blog to be featured on the event website - https://www.cloudstackcollab.org/blog/ - Your company logo to be featured on the sponsors section of the event website - Digital and verbal recognition throughout the event. This may be in the form of verbally thanking sponsors and featuring sponsors logos on session slides - An interview with a chosen in employee to be featured on the CloudStack YouTube channel. This interview will discuss topics such as why your company has chosen to support the conference, your use case with Apache CloudStack and topical topics in the cloud computing industry. The package is available on a discounted rate 950 EUR, discounted from 1500 EUR. If you are interested to take benefit, please get in touch with me! Best regards,
Re: New Sponsorship Opportunity for the CloudStack Collaboration Conference
Forgot to add the link to the full information: https://www.cloudstackcollab.org/digital-sponsorship-opportunity/ Best regards, On 30 Aug 2024, at 15:38, Ivet Petrova wrote: Hi All, I would like to announce that we are launching a new sponsorship opportunity for the CloudStack Collaboration Conference - Digital Sponsorship Package. We ere approached by a few small companies, which wanted to contribute to the event, but the available packages were not fitting their travel plans or budget. For this reason we tailored a package, which is budget-friendly and enables small and mid-sized companies to help the community - Digital Sponsorship. The package includes: - 2 x Sponsored social media posts on the official CloudStack social media (LinkedIn and X) - 1 sponsored blog to be featured on the event website - https://www.cloudstackcollab.org/blog/ - Your company logo to be featured on the sponsors section of the event website - Digital and verbal recognition throughout the event. This may be in the form of verbally thanking sponsors and featuring sponsors logos on session slides - An interview with a chosen in employee to be featured on the CloudStack YouTube channel. This interview will discuss topics such as why your company has chosen to support the conference, your use case with Apache CloudStack and topical topics in the cloud computing industry. The package is available on a discounted rate 950 EUR, discounted from 1500 EUR. If you are interested to take benefit, please get in touch with me! Best regards,
Re: Release 4.20.0.0 status update
Hi All, Time for a little status update. Now with info about 4.19.2.0 as well. We have fixed/tested/merged 31 Issues and 124 PRs in the 4.20.0.0 milestone [1]. Currently, we have 172 open items in the 4.20.0.0 milestone. Of these, we have: - 1 Blocker/Critical issues - 4 Major issues - 14 Minor issues - 35 enhancement issues/requests - 43 improvement issues/requests - 22 new features - 46 open PRs Furthermore, we currently have 22 open PRs and 84 open issues for the 4.19.2.0 milestone, any merged PRs for this milestone that are merged before the 4.20.0.0 code freeze will also be incorporated into the 4.20.0.0 version. I would also like to remind you of our release schedule: - On the second week of September, we freeze the main branch. That means any feature must be in by the first week of September. Only accept critical/blocker issues until the third week of September. - On the third week of September, cut 4.20.0.0 RC1 and further RCs if necessary, start/conclude vote, and finish release work. I hope to have your support with fixing/testing/reviewing open issues and PRs. I'll post a new update next week. [1] https://github.com/apache/cloudstack/milestone/30 On 8/28/24 04:35, Daan Hoogland wrote: thanks João, did you take into account any issues/PRs that may be open for 4.19.2 as well (i.e. bugfixes)? I suspect not, but this could be useful as well to get an idea of the amount of work. Especially the part we cannot get done before release. On Wed, Aug 21, 2024 at 2:34 PM João Jandre Paraquetti wrote: Hi All, Time for a little status update. We have fixed/tested/merged 20 Issues and 114 PRs in the 4.20.0.0 milestone [1]. Currently, we have 185 open items in the 4.20.0.0 milestone. Of these, we have: - 0 Blocker/Critical issues - 4 Major issues - 15 Minor issues - 40 enhancement issues/requests - 50 improvement issues/requests - 24 new features - 50 open PRs I would also like to remind you of our release schedule: - On the second week of September, we freeze the main branch. That means any feature must be in by the first week of September. Only accept critical/blocker issues until the third week of September. - On the third week of September, cut 4.20.0.0 RC1 and further RCs if necessary, start/conclude vote, and finish release work. I hope to have your support with fixing/testing/reviewing open issues and PRs. I'll post a new update next week. [1] https://github.com/apache/cloudstack/milestone/30 On 8/13/24 14:49, João Jandre Paraquetti wrote: Hi All, Time for a little status update. We have fixed/tested/merged 15 Issues and 107 PRs in the 4.20.0.0 milestone [1]. Currently, we have 188 open items in the 4.20.0.0 milestone. Of these, we have: - 0 Blocker/Critical issues - 3 Major issues - 17 Minor issues - 40 enhancement issues/requests - 49 improvement issues/requests - 41 new features - 53 open PRs I would also like to remind you of our release schedule: - On the second week of September, we freeze the main branch. That means any feature must be in by the first week of September. Only accept critical/blocker issues until the third week of September. - On the third week of September, cut 4.20.0.0 RC1 and further RCs if necessary, start/conclude vote, and finish release work. I hope to have your support with fixing/testing/reviewing open issues and PRs. I'll post a new update next week. [1] https://github.com/apache/cloudstack/milestone/30
