| commit | 35e8d79e695b290d371d82dbcc5b15cea429d424 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Tue Oct 11 11:32:30 2022 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Tue Oct 25 13:16:12 2022 +0000 |
| tree | 7bd2a6707cb34b0ae20742f5182df88f1cb2e226 | |
| parent | ee17d8303258980270587755f75dc4b6412e3a31 [diff] |
cloud/bmaas/bmdb: init This adds the initial Bare Metal Database structure. This change focuses on a session/work mechanism which is the foundation on which we will build worker components. It allows lease-like mechanics on machines, letting us not have to use 'standard' work queues in the BMaaS project. Change-Id: I42c3f4384c64fd90dbeab8ff9652a6f611be81d4 Reviewed-on: https://review.monogon.dev/c/monogon/+/953 Tested-by: Jenkins CI 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 - feel free to look around, and check back later for our first release!
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 -c dbg
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -c dbg -- kubectl describe
Run tests:
scripts/bin/bazel test -c dbg //...