-
Notifications
You must be signed in to change notification settings - Fork 41
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
resource: integrate with resource.acquire RPC
Perform the initial resource graph data store population when the first response of resource.acquire arrives. Update the resource graph whenever subsequence responses arrive. Introduce a structure to ultimately map the keys from the responses of resource.acquire to "grow", "shrink", "up" and "down" -- to reduce churns in the future. The target update semantics is the following. - grow: grow the resource graph by attaching the acquired subgraphs to the overall graph and the resulting resource graph becomes the basis for satisfiability - shrink: shrink the resource graph by detaching the subgraphs from the graph and the resulting resource graph becomes the basis for satisfiability - up/down: mark the resource subgraph up or down. The resources that are marked down will not be used for further scheduling. However, the state changes due to the marking do not affect satisfiability. Currently there are a few deficiencies that prevent this commit from implementing this semantics fully: - resource.acquire currently reports "administrative node exclusion" as "down". Since Fluxion can't tell the difference between an exclusion event and other types of real down events that shouldn't affect satisfiability, satisfiability semantics will not be completely correct when a node is administratively excluded at runtime via resource config file reloading. - vertex/edge removal required for shrink requires more investigations due to Boost Graph Library limitation. - mark() method within traverser has not yet been implemented so marking is currently NOOP.
- Loading branch information
Showing
1 changed file
with
180 additions
and
43 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters