Skip to content

Improve the WAGED rebalancer soft constraint design #482

@jiajunwang

Description

@jiajunwang

Our current implementation is based on POC work, which returns the evaluated score based on the ratio between current usage versus the estimated usage.
However, the estimated usage could be difficult to derive. For example, tags could impact expected usage.
In order to address these corner cases, we need to revisit all the soft constraint definition.
The requirement is basically:

  1. Continous distribution.
  2. Normalized to a [0.0 ~1.0] number.
  3. Any two estimated scores should be comparable and different if the two potential assignment will cause different usages.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions