| commit | b0272187ee577a94edb803b81413165b7c1a89ba | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Nov 02 18:39:44 2020 +0100 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Nov 02 18:39:44 2020 +0100 |
| tree | e270e4fc6d3497b4a6c8624ea7cd8ebbe7246a59 | |
| parent | 967be21df6e1f0e14ab66e904f5904261962f099 [diff] |
core: plug logtree into NodeDebugService This introduces a new Proto API for accessing debug logs. Currently this is implemented to be used by the debug service. However, these proto definitions will likely be reused for production cluster APIs. The implementation mostly consists of adding the proto, implementing to/from conversion methods, and altering the debug service to use the new API. We also move all of the debug service implementation into a separate file, to slightly clean up main.go. This produces an unfortunately colorful diff, but it's just moving code around. Test Plan: Manually tested using the dbg tool. We currently don't properly test the debug service. I suppose we should do that for the production cluster APIs, and just keep on going for now. X-Origin-Diff: phab/D649 GitOrigin-RevId: ac454681e4b72b2876e313b3aeababa179eb1fa3
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.