commit | dbac6ccbf5325aa737280ac79b3cc5916e9b57f6 | [log] [tgz] |
---|---|---|
author | Lorenz Brun <lorenz@nexantic.com> | Mon Nov 30 10:57:26 2020 +0100 |
committer | Lorenz Brun <lorenz@nexantic.com> | Mon Nov 30 10:57:26 2020 +0100 |
tree | 677c4bf05829f1f5c2d586710caa1e8c2ced63aa | |
parent | 9601f26770e2aed2c8c37a490e936ce300b1a01d [diff] |
Replace temporary DHCP client with dhcp4c This replaces our temporary DHCP client with the new one. The old GetIP() interface is still preserved temporarily and will be ripped out in another revision stacked on top of this one. nanoswitch also got some updates to support renewals which it previously didn't have to do. This does leave the hacky channel system in place, supervisor observables are still in the design phase. Test Plan: E2E tests still pass X-Origin-Diff: phab/D656 GitOrigin-RevId: cc2f11e3989f4dbc6814fcfa22f6be81d7f88460
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.