Migrate to self-hosted zerotier network #265

raucao · 2020-12-11T18:41:24Z

raucao commented

2020-12-11 18:41:24 +00:00

@greg and I have moved all current zerotier nodes to the new network virgo that is controlled by our self-hosted network controller on zerotier-1.

We upgraded all the systems on the way and ran Chef against every node we moved.

The migration itself is thus complete. Next improvement would be to change haproxy to use zerotier IPs instead of virtual network ones.

closes #247

@greg and I have moved all current zerotier nodes to the new network `virgo` that is controlled by our self-hosted network controller on `zerotier-1`. We upgraded all the systems on the way and ran Chef against every node we moved. The migration itself is thus complete. Next improvement would be to change haproxy to use zerotier IPs instead of virtual network ones. closes #247

raucao added the

kredits-2

ops

labels 2020-12-11 18:41:24 +00:00

greg was assigned by raucao

2020-12-12 09:15:42 +00:00

raucao self-assigned this 2020-12-12 09:15:44 +00:00

raucao referenced this issue from a commit

2020-12-13 12:39:14 +00:00

Merge pull request 'Migrate to self-hosted zerotier network' (#265) from chore/zerotier_migration into master Reviewed-on: https://gitea.kosmos.org/kosmos/chef/pulls/265

raucao merged commit 95c8b9fea9 into master

2020-12-13 12:39:14 +00:00

raucao deleted branch chore/zerotier_migration

2020-12-13 12:39:19 +00:00

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#265