route client console connections to the appropriate server

What new or enhanced feature are you proposing?

Allow the client to connect to a console, and have the underlying network 
connection automagically routed to the appropriate server managing that console.

What goal would this enhancement help you achieve?

This would increase scalability by allowing the server load for a large number 
of consoles to be distributed across several nodes in a manner that is 
transparent to the client.

Please provide any additional information below.

Brian Luckau writes:

  I would like to be able to set it up so that running "conman node1"
  actually contacts another server running conman and opens the
  console that way.

https://groups.google.com/forum/?fromgroups=#!topic/conman-users/Dea57L7YC9U

Note that this complicates broadcast sessions.  Are broadcasts to multiple 
consoles restricted to those managed by a single server, or can broadcasts span 
multiple servers?  If the latter, what happens to a client's broadcast session 
if one of the connected servers stops responding?  And then what happens 
if/when the connection to this server is re-established?

Original issue reported on code.google.com by chris.m.dunlap on 28 Mar 2013 at 9:28

tacho / conman

route client console connections to the appropriate server #18