| commit | 66e589595ecbefdc1466ea5e98e9c237e3300f8e | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Tue Oct 05 17:06:56 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Mon Oct 11 13:27:02 2021 +0000 |
| tree | c5bf14131ce984dea96ee6825c12b5e3cf7a342a | |
| parent | a1a96b454eb3c21d03b7f95f1917dd6ce1b84b8a [diff] |
m/test: refactor cluster launch code, use for e2e tests This is a light dust-off pass for the existing cluster launch code. Notably, we separate Metropolis-specific code into a subpackage (allowing us to make the package itself depend on the required node/kernel images, without introducing dependency loops or unnecessary dependencies on the Metropolis node image). We also make the LaunchCluster code return an already authenticated Management client, and subsequent changes will use this client to add more nodes to the running cluster. We then move the E2E test to use LaunchCluster instead of LaunchNode, in preparation for running a multi-node cluster in the E2E test. We also add some more log calls and clean up the existing ones to make it clear which subsystem (launch, launch/cluster or e2e) is respondible for each message. Change-Id: I838bdc75073831fe94b9cdcef4fb3ab6bf8cba2c Reviewed-on: https://review.monogon.dev/c/monogon/+/343 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 //...