| commit | cb883e2810f61d74df76f0db58be7c5ad31bf8e3 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Jul 06 17:47:55 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Jul 06 17:47:55 2020 +0200 |
| tree | 2eb844cd60992866181bd061624e9cd1281f4cdc | |
| parent | a5eaeb8670b0b56f884fbda8ddb92ea0bf78fb5d [diff] |
core/internal/consensus: refactor This refactors the consensus to: - use localstorage - use the supervisor system - have a significantly simpler API for callers (no more PrecreateCertificate, etc.) - use a watcher for CRLs - actually have all bootstrap paths tested - keep the CA key in memory (keeping it in etcd only seems like odd threat modelling and can posisbly cause issues on quorum losses) This breaks the build, as is part of a multi-revision refactor of the core node service code. Test Plan: adds tests \o/ X-Origin-Diff: phab/D579 GitOrigin-RevId: fadee7785028ef806d8243a770c70cb0fb82c20e
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.