workload validation before registering elektron. #19
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
fix
good first issue
help wanted
invalid
major
question
testing
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: spdf/elektron#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issues/issue-18-workload-validation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Added a utility to help with validating structs. This utility accepts
validators and runs them. If any of the validators fail, then the
error is wrapped with a given base message and returned.
Added validators for checking different attributes of a task
definition.
Added test code to test task validators.
Retrofitted scheduler.go to just log the task validation error and
terminate. If task validation does not report any error, then the
tasks are provided to the scheduler and elektron registers itself
with Mesos.
@ -58,0 +67,4 @@
return tasks, err
}
}
Awesome idea
Do we need to keep this around?
Yeah, the example might be an overkill. I'll get rid of it.