Use Ohai plugin to store zerotier node info #263
Closed
opened 2020-12-11 16:50:38 +00:00 by raucao
·
3 comments
No Branch/Tag Specified
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
Milestone
No items
No Milestone
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#263
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
At least IP address and client ID.
Create Ohai plugin to store zerotier node info in custom attributesto Use Ohai plugin to store zerotier node infoTurns out their official Chef cookbook already comes with an Ohai plugin: https://github.com/zerotier/chef-zerotier
And it also comes with recipes for joining networks and such, in case we need it later.
We recently found the problem with the attribute whitelist that prevented us from finishing this task. It's that knife zero is not changing the whitelist in the local knife config on the machine when it changes in the Chef repo after bootstrapping the node.
The whitelist problem has been resolved, so we can add new attributes to a whitelist yaml file now, and they will be allowed immediately.