commit | 0ed2f96a3a86aff2c9ce36289aa5d58a75f4d59b | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@nexantic.com> | Mon Mar 15 16:39:30 2021 +0100 |
committer | Serge Bazanski <serge@nexantic.com> | Mon Mar 15 16:39:30 2021 +0100 |
tree | afbe1fb6cd0a1667e981edfe97969338437bdaca | |
parent | 056042962060369bd7607ecfea51c515fc3a8140 [diff] |
metropolis/proto: EnrolmentConfig -> NodeParameters This starts off the move to a node configuration API conforming to the lifecycle management design document. Instead of an Enrolment Config used only to join an existing cluster, we move to a NodeParameters proto that must always be given to a node if it's supposed to either bootstrap a new cluster or join an existing one. This links the existing cluster management code (and its state machine) to work with this file. However, that state machine will be removed very soon, anyway. We also remove everything related to golden tickets. This breaks multi-node tests. X-Origin-Diff: phab/D710 GitOrigin-RevId: f22615fbccab975f2d5e6928bdc7387ab3aa5714
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