Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consul organization and keys #19

Closed
hntd187 opened this issue Oct 20, 2018 · 1 comment
Closed

Consul organization and keys #19

hntd187 opened this issue Oct 20, 2018 · 1 comment

Comments

@hntd187
Copy link
Member

hntd187 commented Oct 20, 2018

So using consul's kv store we can do more in terms of orchestration than just leader election (if we even want to go that route)

but basically
/service/toshi/leader true

whichever node gets the session lock on this is the leader then nodes can join the cluster and announce their address perhaps via something like

/service/toshi/cluster/tn1 hostname:port
/service/toshi/cluster/tn2 hostname:port

So on so forth, I don't have any particular attachment to this method, but just something to get started with.

@fhaynes fhaynes mentioned this issue Oct 20, 2018
17 tasks
@fhaynes
Copy link
Member

fhaynes commented Oct 20, 2018

Off the top of my head:

  • IP
  • Hostname
  • Current CPU load (5 min avg or something)
  • Free desk space
  • iowait
  • Node role if we use roles
  • Free RAM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants