| commit | b15abadcd33cc25c220a2e8987f11bd967af5765 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Thu Apr 16 11:17:12 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Thu Apr 16 11:17:12 2020 +0200 |
| tree | e9744eb8694a12238f345fa409ba1553f813d18d | |
| parent | 0db90ba4fde0be782f2dc43f4e6d269d7c1c5f0b [diff] |
Add PV provisioner This adds a new PV provisioner which works together with the CSI Node driver to provide storage to workloads on Smalltown. It talks to Kubernetes and listens for PVCs which need to be provisioned and PVs which have been released and need to be deleted. Is is implemented as a per-node agent where every node provisions the volumes scheduled onto it by kube-scheduler. Test Plan: Manually tested by running `bazel run //core/cmd/dbg -- kubectl create -f $PWD/pv-test.yml` and observing a provisioned PV that's attached to the pod. An example `test-pv.yml` is in P137. X-Origin-Diff: phab/D482 GitOrigin-RevId: 75a871b039e71dd248f937719c471e0277887964
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)
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.