| commit | be74284cb84581b7217a934d2a771edb7c948223 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Mon Apr 04 13:18:50 2022 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Wed Apr 06 09:52:24 2022 +0000 |
| tree | c943b51d32f0f0c0f81b97faa4660a9099b3caee | |
| parent | fe7134b0b25b620b6f40b1f41f37ab93fca6d3c0 [diff] |
m/test: implement SOCKS proxy in cluster tests This uses the new socksproxy package to run a proxy server in the nanoswitch, and uses it within tests to access the test cluster's nodes. The cluster test code (and nanoswitch) still forward traffic to the first node, but this will be gradually removed as SOCKS support is implemented in metroctl and the debug tool. Forwards from host ports to different node can then be implemented as part of the dbg tool (instead of the cluster launch code) to maintain a simple interface during debug and development. We also use the opportunity to make the non-cluster launch code not Metropolis specific (by removing an assumption that all ports on all nodes are Metropolis ports). In the long term, we will probably remove non-cluster launches entirely (or further turn this code into just being a 'launch qemu' wrapper). Change-Id: I9b321bde95ba74fbfaa695eaaad8f9974aba5372 Reviewed-on: https://review.monogon.dev/c/monogon/+/648 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
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...