| commit | 0de189355c6afad6f677029d90fa40dee824141b | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Thu Mar 11 00:36:48 2021 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Thu Mar 11 00:36:48 2021 +0100 |
| tree | 3e926e04415d4310b120cc641e4cd7893c5a6b61 | |
| parent | 735119f8efcd1ce8689703fe455e39f2146b0b3e [diff] |
Add QEMU into the monorepo This adds QEMU and all its dependencies into the monorepo. Enough features are enabled that this QEMU should be both usable for running tests for Metropolis as well as running customer VMs in containers. Thus we can also get rid of the QEMU ambient dependency. All dependencies have their includes fully rewritten as to be reusable without a huge effort. QEMU itself relies on `includes` attributes since the patch would otherwise be enormous and it is a binary and thus any include path madness ends there. Overall though this is quite nice, the final QEMU build with full optimization is <10MiB and has no further ambient dependencies. It also has full io_uring support, which works very well with our 5.10 kernel. TPM support is also included. This is not used anywhere, replacing the ambient dependency and shipping a container will be in an upcoming revision. Test Plan: Manually tested to run a Ubuntu cloud image with io_uring and virtio. Automated tests will follow as part of its roles in this repo. X-Origin-Diff: phab/D712 GitOrigin-RevId: 9c2607d75c875b1d65346e3cdac1a5e08467ea33
This is the main repository containing Monogon's public source code, including Metropolis.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
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. 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.
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:
bazel run //:launch
Run a kubectl command:
bazel run //metropolis/cli/dbg -- kubectl describe