Configure a zerotier-one network controller #260

raucao · 2020-12-10T21:58:35Z

raucao commented

2020-12-10 21:58:35 +00:00

Turns out every zerotier client already automatically acts as a controller, with an HTTP API running on localhost port 9993.

However, there's no CLI to interact with it. I found a nice CLI script to make things a little bit easier until we have more automation/integration, so all the controller recipe does is to deploy that script for now.

I have manually added the haproxy forward of 9993 traffic to the new zerotier-1 VM on centaurus, and joined my own computer to verify that it can find the network I created on the VM controller.

So basically, we're all ready to switch every machine in the network to the new network instead. Leaving the issue open for that operational task.

refs #247

Turns out every zerotier client already automatically acts as a controller, with an HTTP API running on localhost port 9993. However, there's no CLI to interact with it. I found a nice CLI script to make things a little bit easier until we have more automation/integration, so all the controller recipe does is to deploy that script for now. I have manually added the haproxy forward of 9993 traffic to the new `zerotier-1` VM on centaurus, and joined my own computer to verify that it can find the network I created on the VM controller. So basically, we're all ready to switch every machine in the network to the new network instead. Leaving the issue open for that operational task. refs #247

raucao added the

feature

kredits-1

ops

labels 2020-12-10 21:58:35 +00:00

greg approved these changes 2020-12-11 10:42:06 +00:00

greg left a comment

👍

greg referenced this issue from a commit

2020-12-11 10:42:40 +00:00

Merge pull request 'Configure a zerotier-one network controller' (#260) from feature/zerotier_controller into master Reviewed-on: https://gitea.kosmos.org/kosmos/chef/pulls/260

greg merged commit 8896beab67 into master