| commit | 3be483247a07a6ebe73dd044f6ad299e19a04c7b | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Tue Oct 05 17:24:26 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Wed Oct 06 14:49:50 2021 +0000 |
| tree | 91e414202d66fd57a7064d9cd6ff975530b56143 | |
| parent | 826a9e94db7345bbb1932fa51049bc6e090391e3 [diff] |
m/n/c/curator: share locks across leader service instances This is needed to lock access to nodes between the Curator and Managment instances. Change-Id: I4609d87a961339235a13af57236f80c9976819ed Reviewed-on: https://review.monogon.dev/c/monogon/+/339 Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
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-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
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.
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 //...