| commit | 1ebd1e133bac1a7fe0d667ec2ac95f87f63c3701 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Jul 13 19:17:16 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Jul 13 19:17:16 2020 +0200 |
| tree | c84bca5f68d4bbe959006215bf4711050af04288 | |
| parent | c2c7ad97b50194a550e77b875570ece90259f4ea [diff] |
core/internal/cluster: add new single-node cluster code This adds a cluster library, that consists of: - a Node object that can be loaded from and saved into etcd, representing a node of the cluster that can have different 'role tags' assigned to it - a cluster Manager, that is responsible for bringing up the local node into a cluster (by creaating a new cluster, enrolling into or joining a cluster) This also gets wired into core/cmd/init, and as such completes a chunk of The Refactor. This code should pass tests. Test Plan: this should work! should be covered by existing e2e tests. X-Origin-Diff: phab/D590 GitOrigin-RevId: e88022164e4353249b29fc16849a02805f15dd49
This is the monorepo storing all of nexantic's internal projects and libraries.
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)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official 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.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.