search

samuraictf / gatekeeper

GATEKEEPER: Inline and on-target defense
119 stars 15 forks source link

Centralized Configuration #42

Closed ghost closed 9 years ago

ghost commented 9 years ago

This doesn't have to be tied to gatekeeper, be we need some tool to

  1. Wrap around the service binaries and pipe/chain/weld to other tools (gatekeeper, gatekeeper-ebeip, ...)
  2. Be aware of what a service is- it's name, paths, etc..
  3. Manage the configuration of other tools (like gatekeeper)
  4. Periodically check to see if tools are deployed
  5. Sanity check machine (load average, file permissions, etc)
  6. Redeploy tools

Not sure what parts of this would need to be remote/local, owned by the user ctf or the appropriate service user, etc...

zachriggle commented 9 years ago

This exists, it's git push

Anything more complex is truly unnecessary

zachriggle commented 9 years ago

*Boro and git push

zachriggle commented 9 years ago

Sorry, I'll clarify a bit (just woke up)

We already have a tool for managing the game box (Boro), specifically automating the process of patching, testing, and deploying binaries to the game server. It does have some shortcomings in pushing additional configuration (eg Gatekeeper) but those are being resolved.

Additionally, we have a tool called sla-checker which is intended to be run by our team (vs used in the scrimmage for the scoreboard) to verify that everything is working.

This solves everything on the list (I believe) except load monitoring, which is part of Horo, the host-monitoring tool.