clustering

[ahmadnassri]

Discussion started in #15 need to define requirements for cluster awareness.

• cluster status API, similar to /status but for the whole cluster
• add remove nodes from cluster with API ?

[subnetmarco]

Supported commands in the first version will be:

• join
• members
• keygen (Utility method to generate base64-encoded 16-byte key for encryption)
• leave
• force-leave

The configuration options available will be:

######
## Cluster settings
cluster:

  ######
  ## Address to bind network listeners to.
  bind: "0.0.0.0:7946"

  ######
  ## Network interface to bind to. Can be used instead of bind if the interface is known but 
  ## not the address. If both are provided, then Kong verifies that the interface has the bind 
  ## address that is provided.
  iface: ""

  ######
  ## Address to bind the RPC listener.
  rpc-addr: "127.0.0.1:7373"

  ######
  ## Key for encrypting network traffic within Kong. Must be a base64-encoded 16-byte key.
  encrypt: "foo"

I am also considering to optionally support adding the nodes in the configuration, so that the node will auto-join them without further commands, like:

cluster:

  ######
  ## Optional list of nodes to auto-join on startup.
  nodes:
    - "1.1.1.1:7042"
    - "2.2.2.2:7042"
    - "3.3.3.3:7042"

[ahmadnassri]

can we not have clustering be done through admin API, rather than yml/config?

seems to me it would be more powerful to dynamically setup rather to do on init.

e.g.

• POST /cluster/join/
• GET /cluster/members/

[subnetmarco]

can we not have clustering be done through admin API, rather than yml/config?

Yes. Very good point.

[nijikokun]

can we not have clustering be done through admin API, rather than yml/config?

👍

[ahmadnassri]

@thefosk can this be closed now with the features introduced in 0.6.0-RC?