Warning Livedoc is no longer being updated and will be deprecated shortly. Please refer to https://documentation.tjhsst.edu.

Difference between revisions of "User:2016fwilson/Conductor"

From Livedoc - The Documentation Repository
Jump to: navigation, search
(Created page with "'''Conductor''' will be a web-based container management tool. == Architecture == The system is built to support many clients and many container hosts, so it uses a service-o...")
 
 
Line 1: Line 1:
'''Conductor''' will be a web-based container management tool.
+
'''Conductor''' will be a web-based container management tool. It aims to make maintaining systems for non-critical projects (senior research, software testing, etc) very easy.
  
 
== Architecture ==
 
== Architecture ==
 
The system is built to support many clients and many container hosts, so it uses a service-oriented architecture. On each container host, an agent listens for container management commands. An API server keeps track of container hosts, and interfaces with the agent on each host. Frontend clients, including the web interface, interface with the API server and a user. Communication is secured between layers using SSL certificates.
 
The system is built to support many clients and many container hosts, so it uses a service-oriented architecture. On each container host, an agent listens for container management commands. An API server keeps track of container hosts, and interfaces with the agent on each host. Frontend clients, including the web interface, interface with the API server and a user. Communication is secured between layers using SSL certificates.

Latest revision as of 23:32, 27 November 2015

Conductor will be a web-based container management tool. It aims to make maintaining systems for non-critical projects (senior research, software testing, etc) very easy.

Architecture

The system is built to support many clients and many container hosts, so it uses a service-oriented architecture. On each container host, an agent listens for container management commands. An API server keeps track of container hosts, and interfaces with the agent on each host. Frontend clients, including the web interface, interface with the API server and a user. Communication is secured between layers using SSL certificates.