-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bench nomad exec #4852
Bench nomad exec #4852
Conversation
a015319
to
8898923
Compare
8898923
to
8454b0d
Compare
41f05c8
to
177b9ce
Compare
a1c2c8a
to
3998d2c
Compare
528fc5e
to
e9dfef8
Compare
a897d37
to
5230b79
Compare
2604801
to
fd0a93d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fmaste, just one comment/question.
Thank you! : -)
bors merge |
4852: Bench nomad exec r=fmaste a=fmaste Exec task driver and standalone Nomad Server and Clients (no -dev mode) - Local/testing environment - - Bye bye `-dev` mode, now both Nomad Servers and Clients are started independently - - Can automate as many Nomad Clients as needed (`wb backend pass nomad server|client start|stop NAME`) - - Optional stateful Nomad Agents instead of starting and stopping on every run - - Only when using the Nomad `exec` Task Driver Clients are run as root - - Create symlinks to every Task's `stdout` and `stderr` file for easier/live monitoring and debugging - Cloud deployments - - Add a new mode called `nomadexec` that uses SRE's patched version of Nomad - - As part of the switch-over to directly-executable derivations, the Nomad Job specification file is self contained. Every script and config file is included as a template stanza only leaving outside the genesis folder. - - Created an ad-hoc "container-specs.json" file with GitHub references (towards being able to benchmark any cardano-node commit from any workbench version). - - The workbench checks that the commit being tested is publicly available on GitHub - - Fetch all Nomad (some dynamically) generated `start.sh` and `config.json` files for log and debugging purposes - Both local and cloud - - Control and monitoring of Nomad Jobs was refactored in line with the important role it has - - Removal of all locality assumptions - - Removal of all 1-1 `allocation ID`-`task name` relation assumptions - Others - - Fixed how `wb backend` calls backend specific subcommands Co-authored-by: Federico Mastellone <[email protected]>
This PR was included in a batch that successfully built, but then failed to merge into master. It will not be retried. Additional information: {"message":"Validation Failed","documentation_url":"https://docs.github.com/articles/about-protected-branches"} |
fd0a93d
to
723e9ab
Compare
bors merge |
4852: Bench nomad exec r=fmaste a=fmaste Exec task driver and standalone Nomad Server and Clients (no -dev mode) - Local/testing environment - - Bye bye `-dev` mode, now both Nomad Servers and Clients are started independently - - Can automate as many Nomad Clients as needed (`wb backend pass nomad server|client start|stop NAME`) - - Optional stateful Nomad Agents instead of starting and stopping on every run - - Only when using the Nomad `exec` Task Driver Clients are run as root - - Create symlinks to every Task's `stdout` and `stderr` file for easier/live monitoring and debugging - Cloud deployments - - Add a new mode called `nomadexec` that uses SRE's patched version of Nomad - - As part of the switch-over to directly-executable derivations, the Nomad Job specification file is self contained. Every script and config file is included as a template stanza only leaving outside the genesis folder. - - Created an ad-hoc "container-specs.json" file with GitHub references (towards being able to benchmark any cardano-node commit from any workbench version). - - The workbench checks that the commit being tested is publicly available on GitHub - - Fetch all Nomad (some dynamically) generated `start.sh` and `config.json` files for log and debugging purposes - Both local and cloud - - Control and monitoring of Nomad Jobs was refactored in line with the important role it has - - Removal of all locality assumptions - - Removal of all 1-1 `allocation ID`-`task name` relation assumptions - Others - - Fixed how `wb backend` calls backend specific subcommands Co-authored-by: Federico Mastellone <[email protected]>
This PR was included in a batch that successfully built, but then failed to merge into master. It will not be retried. Additional information: {"message":"Validation Failed","documentation_url":"https://docs.github.com/articles/about-protected-branches"} |
723e9ab
to
6dc3f9e
Compare
bors merge |
4852: Bench nomad exec r=fmaste a=fmaste Exec task driver and standalone Nomad Server and Clients (no -dev mode) - Local/testing environment - - Bye bye `-dev` mode, now both Nomad Servers and Clients are started independently - - Can automate as many Nomad Clients as needed (`wb backend pass nomad server|client start|stop NAME`) - - Optional stateful Nomad Agents instead of starting and stopping on every run - - Only when using the Nomad `exec` Task Driver Clients are run as root - - Create symlinks to every Task's `stdout` and `stderr` file for easier/live monitoring and debugging - Cloud deployments - - Add a new mode called `nomadexec` that uses SRE's patched version of Nomad - - As part of the switch-over to directly-executable derivations, the Nomad Job specification file is self contained. Every script and config file is included as a template stanza only leaving outside the genesis folder. - - Created an ad-hoc "container-specs.json" file with GitHub references (towards being able to benchmark any cardano-node commit from any workbench version). - - The workbench checks that the commit being tested is publicly available on GitHub - - Fetch all Nomad (some dynamically) generated `start.sh` and `config.json` files for log and debugging purposes - Both local and cloud - - Control and monitoring of Nomad Jobs was refactored in line with the important role it has - - Removal of all locality assumptions - - Removal of all 1-1 `allocation ID`-`task name` relation assumptions - Others - - Fixed how `wb backend` calls backend specific subcommands Co-authored-by: Federico Mastellone <[email protected]>
This PR was included in a batch that successfully built, but then failed to merge into master. It will not be retried. Additional information: {"message":"Required status check \"build-complete\" is expected.","documentation_url":"https://docs.github.com/articles/about-protected-branches"} |
Exec task driver and standalone Nomad Server and Clients (no -dev mode)
-dev
mode, now both Nomad Servers and Clients are started independentlywb backend pass nomad server|client start|stop NAME
)exec
Task Driver Clients are run as rootstdout
andstderr
file for easier/live monitoring and debuggingnomadexec
that uses SRE's patched version of Nomadstart.sh
andconfig.json
files for log and debugging purposesallocation ID
-task name
relation assumptionswb backend
calls backend specific subcommands