| commit | 6dff6d6a57b999eb91f1b9cf956e2ebc18c2defd | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Fri Jan 28 18:15:14 2022 +0100 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Wed Feb 23 16:15:54 2022 +0000 |
| tree | 4db4fa350e81b0fc52db7cf81f4c620114b28d18 | |
| parent | 636032e843efcdef0716ed9956f40642d07b8d4c [diff] |
m/n/roleserve: reactive service management Bottom line up first: this starts etcd, the curator and Kubernetes on nodes that register into the cluster. Effectively, this is multi-node support. This significantly refactors the node roleserver to start both the control plane and Kubernetes on demand, based on roles assigned by the cluster (or due to bootstrapping a new cluster). Most importantly, we pretty much remove all cluster-bootstrapping code from the node startup process, thereby making the first node and any subsequent nodes not go through different codepaths. In addition, access to the cluster Curators is now also mediated via the roleserver, which is the component aware whether the node code should connect to the local curator (if the control plane is running) or to remote curators (if the control plane is not [yet] running). This implementation is a bit verbose as we make heavy use of untyped Event Values, and we add quite a few lines repeated of code to combine data from different values into something that a goroutine can wait on. Once Go 1.18 lands we should be able to make this code much nicer. There's still a few things that need to be implemented for all flows to be working fully (notably, we can end up with stale curator clients, curator clients are not load balanced across multiple curators, and cluster directories for connecting to the curator do not get updated after startup). However, these are all features that we should be able to easily implement once this lands. Currently this is only covered by the e2e test. The individual workers within roleserver should be able to be independently tested, and this is something I plan on doing very soon as another change on top, while this one is being reviewed. With time, the two large startup components (the cluster "enrolment" manager and the roleserver) have slightly lost their original purpose and their names aren't exactly fitting anymore. I might rename them in an upcoming change, if anyone has any good naming ideas I'm all ears :). Change-Id: Iaf0fc9f6fdd2122e6aae19607be1648382063e66 Reviewed-on: https://review.monogon.dev/c/monogon/+/532 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 //...