Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Relax the requirement that an objective function has to be a scalar expression #82

Closed
lalithsuresh opened this issue Mar 17, 2021 · 0 comments

Comments

@lalithsuresh
Copy link
Contributor

If it's not a scalar expression (e.g., preference for certain assignments to hold true), we can simply encode it as a sum on behalf of the user.

lalithsuresh added a commit that referenced this issue Mar 17, 2021
…alar expression

Objective functions until now have been a scalar expression whose value DCM will
try to maximize. We've now simplified this to also allow for column expressions.
The objective function in the latter case will maximize the sum of the individual
column values.

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
lalithsuresh added a commit that referenced this issue Mar 17, 2021
…alar expression

Objective functions until now have been a scalar expression whose value DCM will
try to maximize. We've now simplified this to also allow for column expressions.
The objective function in the latter case will maximize the sum of the individual
column values.

Fixed #82

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
lalithsuresh added a commit that referenced this issue Mar 17, 2021
…function syntax

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
lalithsuresh added a commit that referenced this issue Mar 17, 2021
…function syntax

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
lalithsuresh added a commit that referenced this issue Mar 18, 2021
…function syntax

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
lalithsuresh added a commit that referenced this issue Jun 22, 2021
…100)

With #82 being fixed, there is little reason to have a different query structure for hard and soft constraints. We can instead structure both constraints as a view that produces a set of records, followed by a CHECK or MAXIMIZE clause, followed by an expression. This would allow a user to easily switch between hard/soft constraints if they want.

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
askiad pushed a commit to askiad/declarative-cluster-management that referenced this issue Jun 23, 2021
…nd objectives (vmware-archive#100)

With vmware-archive#82 being fixed, there is little reason to have a different query structure for hard and soft constraints. We can instead structure both constraints as a view that produces a set of records, followed by a CHECK or MAXIMIZE clause, followed by an expression. This would allow a user to easily switch between hard/soft constraints if they want.

Signed-off-by: Lalith Suresh <lsuresh@vmware.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant