PacketFire / gemini

Cluster container orchestration tool
Apache License 2.0
0 stars 0 forks source link

Further node registration questions #46

Closed RaasAhsan closed 5 years ago

RaasAhsan commented 5 years ago

Node identifier

Should node IDs be permanent for a node or should they change on refresh/restart?

Registration and rejoining

Should there be a separate process for nodes that have shut down (they already have a node ID) to rejoin the cluster?

We could have it such that on registration, the master will generate the node a permanent password. The password is permanently stored, and is used to join and rejoin the cluster. The purpose of the password is to uniquely authenticate a particular node such that another node can't impersonate that node without its password. When joining/rejoining the cluster, the node will receive an authorization token that should be used for the remainder of the session communication between node and master.

The join call would then be used only for new (or corrupted) nodes to join the cluster, and we would have another rejoin call for existing nodes (that already have a node ID and password) to call on startup.

Of course, we only need this if it is necessary/beneficial for nodes to retain their identity across restarts (I think it will be)