| commit | a105db57640d6abf6de368ec0c33a3a5b4f93893 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Apr 12 19:57:46 2021 +0200 |
| committer | Leopold Schabel <leo@nexantic.com> | Tue Apr 13 19:51:13 2021 +0200 |
| tree | dc96244d0b2922768d7f29431bab2a9ac581a1a6 | |
| parent | c75c9d4f30174c089cce47c608683bf09396fa30 [diff] |
m/n/core/cluster: migrate to events and etcd namespaced client This moves the status of the cluster manager to use a local event variable. Watchers (like the node startup code) can now use this to get updates on the state of the node and its cluster membership in a way that's more abstracted from a sequential startup. This will permit us to move a lof othe startup code into code common across different node lifecycle paths. Test Plan: Refactor, exercised by e2e. X-Origin-Diff: phab/D757 GitOrigin-RevId: 31a3600ad2aab90a1e7f84d741e7ea40a0422724
This is the main repository containing the source code for the Monogon Project.
⚠️ This is pre-release software that happens to be publicly available. Nothing to see here, please move along.
Our build environment requires a working Podman binary (your distribution should have one).
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)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
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.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...