Self-Replicating Management Services for Distributed Computing Architectures

Patent metadata

Field	Value
Publication number	US-2019268408-A1
Application number	US-201815907011-A
Country	US
Kind code	A1
Filing date	Feb 27, 2018
Priority date	Feb 27, 2018
Publication date	Aug 29, 2019
Grant date	—

Abstract

Self-replicating management services for distributed computing architectures are provided herein. An example system method includes providing one or more nodes providing services; maintaining a quorum of a plurality of management servers by: providing at least a distributed coordination service for the one or more nodes on each of the plurality of management servers, the distributed coordination service being a datastore; managing, via a director, requests for data on the distributed coordination service from the one or more nodes; and promoting at least one of the one or more nodes to being one of the plurality of management servers, wherein promoting comprises replicating the distributed coordination service thereon.

First claim

What is claimed is:

1 . A system comprising:
one or more nodes providing services; and a plurality of management servers, each of the plurality of management servers comprising:
at least a distributed coordination service for the one or more nodes, the distributed coordination service being a datastore;
a director that manages the distributed coordination service, the director being configured to:
manage requests for data of the distributed coordination service from the one or more nodes; and
promote at least one of the one or more nodes to being one of the plurality of management servers, wherein promoting comprises replicating the distributed coordination service thereon.

2 . The system according to claim 1 , wherein the at least one of the one or more nodes that was promoted to being one of the plurality of management servers is also configured to promote at least one of the one or more nodes to being one of the plurality of management servers.

3 . The system according to claim 1 , wherein a number of the one or more nodes the director promoted by the director is based on a server quorum value.

4 . The system according to claim 1 , wherein the director is further configured to write distributed coordination service configuration files in such a way that a uniqueness of an identification of the distributed coordination service is maintained.

5 . The system according to claim 1 , wherein the director is further configured to verify that replication of the distributed coordination service on the at least one of the one or more nodes has resulted in synchronization with the plurality of management servers.

6 . The system according to claim 1 , wherein the director is further configured to maintain secure tunnels between the plurality of management servers and the one or more nodes providing services, the encryption infrastructure providing transparent encryption of traffic.

7 . The system according to claim 1 , wherein the director is further configured to discover all other directors on the plurality of management servers.

8 . The system according to claim 1 , wherein the plurality of management servers each comprise a dedicated management interface providing unrestricted access to the distributed coordination service.

9 . The system according to claim 1 , wherein the plurality of management servers each comprise one or more client ports.

10 . The system according to claim 9 , wherein the director is further configured to:
issue certificates to any of the one or more nodes that desire to connect to any of the plurality of management servers; and grant access to certificate bearing nodes on the one or more client ports.

11 . The system according to claim 1 , wherein each of the plurality of management servers comprise a client forwarder that cooperates with the director to forward a known set of local ports and transparently handle encryption of traffic and automatically update the forwarded ports when any of the directors of the plurality of management servers are unavailable.

12 . The system according to claim 1 , wherein the director is further configured to implement a blueprinter that assigns each of the one or more nodes to at least one of the plurality of management servers based on a role associated with the one or more nodes.

13 . The system according to claim 11 , wherein the blueprinter is further configured to dynamically reassign a node of the one or more nodes when the role changes or a role of a currently assigned management server is changed.

14 . The system according to claim 13 , wherein the role is defined using a token, wherein the blueprinter cryptographically verifies that the token is valid and untampered.

15 . The system according to claim 14 , wherein the blueprinter is configured to ensure that automatically assigned management server relationships do not conflict with manually assigned management server relationships.

16 . A method, comprising:
providing one or more nodes providing services; and maintaining a quorum of a plurality of management servers by:
providing at least a distributed coordination service for the one or more nodes on each of the plurality of management servers, the distributed coordination service being a datastore;
managing, via a director, requests for data on the distributed coordination service from the one or more nodes; and
automatically promoting at least one of the one or more nodes to being one of the plurality of management servers, wherein promoting comprises replicating the distributed coordination service thereon.

17 . The method according to claim 16 , further comprising:
receiving a request from at least one or more nodes providing services to connect with the distributed coordination service; and connecting the at least one or more nodes to the distributed coordination service through a client forwarder.

18 . The method according to claim 17 , wherein the at least one of the one or more nodes that is promoted is the at least one or more nodes that has connected to the distributed coordination service through the client forwarder.

19 . The method according to claim 19 , wherein promoting further comprises writing distributed coordination service configuration files to the at least one of the one or more nodes in such a way that a uniqueness of an identification of the distributed coordination service is maintained.

20 . The method according to claim 16 , further comprising maintaining secure tunnels between the plurality of management servers and the one or more nodes providing services, the secure tunnels providing transparent encryption of traffic.

Assignees

• Elasticsearch Bv

Inventors

• Brasetvik Alex
• Karevoll Njal

Classifications

• H04L41/28

  Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• H04L67/1095 Primary

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L9/3213 Primary

  using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807) · CPC title

• H04L9/3226

  using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083) · CPC title