soreana commented on PR #7723: URL: https://github.com/apache/cloudstack/pull/7723#issuecomment-1644047722
> > @vishesh92 This is an awesome feature and I'm looking forward for it to be merged. > > One improvement that would be useful, is to reserved resource for specific service offering. Let me clear it a bit up with an example, assume that a cluster have two hosts each with 64GB memory [`H1`, `H2`]. If we create two `32` GB vm [`V1`, `V2`] and place both of them on `H1` there would be a room to create a vm with `64` GB. So far so good. > > But the thing is, the DRS might balance the cluster and moves one of the VMs to the `H2`. In that case, it is not possible to create a new VM with `64` GB memory although there is enough capacity to deploy one in the cluster. > > It would be really nice if we can set a service offering uuid, and DRS reserves that capacity for new VMs. Let me know what do you think about this suggestion. > > @soreana There will be two Algorithms that I am implementing as part of this feature. > > 1. Balanced > 2. Condensed > > Having a Condensed algorithm will solve your use case. Right? > > I need to update the PR description, but I am introducing a configuration parameter `drs.level` which configures the threshold percentage after which DRS should run. Configuring this variable with balanced might also help with your use case. @vishesh92 Thanks for explanation, that would work for us. Another questions, when the DRS calculates the CPU and Memory, does it use the used value or the allocated value? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
