Hi, Currently the VM autoscaling group is associated with a load balancing rule. In the coming releases we might make the LB rule as optional so the feature will work with shared/L2 networks. To support multiple LB rules, it will be more complex as It requires some design changes and database changes as well.
Do you want to scale up/down the autoscaling group ,based on cpu/memory or network in/out and number of LB connections ? -Wei On Tue, 23 Jan 2024 at 06:16, Palash Biswas <[email protected]> wrote: > Hi Daan/Community > > I've created a simplified diagram to help illustrate my requirement. > Essentially, I need to set up two Auto Scaling groups for VM3 and VM4, each > of which hosts multiple containers, each with different port numbers. > > As you may know, when creating an Auto Scaling group, it's typically > associated with a single Load Balancer (LB) and a single port. I'm seeking > advice on how to associate multiple LBs or a single LB with multiple ports, > or if there's an alternative solution that can help me achieve this > architectural setup? > > > I am using CloudStack 4.18.1.0 > [image: image.png] > > Regards, > Palash > > On Mon, Jan 22, 2024 at 6:58 PM Daan Hoogland <[email protected]> > wrote: > >> Palash, >> can you please explain your use-case more precisely? What cloudstack >> environment and configuration are you using? what dimension do you >> expect to scale? >> >> regards, >> >> On Mon, Jan 22, 2024 at 11:48 AM Palash Biswas <[email protected]> >> wrote: >> > >> > Hello community, >> > >> > Is there a way to integrate multiple load balancers into the autoscaling >> > group without using Kubernetes or Docker Swarm? I have Docker >> containers on >> > various ports, and I aim to achieve autoscaling for the VM. Please >> provide >> > guidance on implementing autoscaling with multiple running containers. >> > >> > Regards, >> > Palash Biswas >> >> >> >> -- >> Daan >> >
