|
Linux Virtual Server Development STATUS:
Last modified at [$Date: 1999/3/18 $]
Plan:
Everyone with plans on things they want to do for Linux Virtual Server
should add them to the repository now.
Open issues:
* Porting the virtual server patch to kernel 2.2
Status: nobody has volunteered yet
* Minimizing the overhead of timing of masquerading entries
+1: peter, wensong
-0:
Status: peter has volunteered
* The separate virtual service handling modules.
Since the ip_masq application modules are provided for the masquerading
users to access the remote service, the virtual server handling is just
in the reverse for the protocol that transmit addresses or port numberes
as application data. If we just change those ip_masq application to
support virtual service for those protocols (like current virtual FTP
service implementation, it is not efficent solution. A good solution
is to develop separate virtual service handling modules.
+1: wensong
-0:
Status: nobody has volunteered yet.
* Implement the dispatching technology of IBM Network Dispatcher into
the virtual server patch.
See http://www.software.ibm.com/enetwork/dispatcher
+1:
-0:
* The easy-install and easy-use cluster management software
+1:
-0:
* Integrate (improve if needed) Alan's heartbeat code in the virtual server
to setup a backup of LinuxDirector.
See http://www.henge.com/~alanr/ha/
+1: wensong
-0:
Status: Wensong used the heartbeat code to build a backup of
LinuxDirector. The backup will take over the virtual IP
address if it cannot hear the heartbeat message "I'm alive"
from the primary in two seconds. wensong will put the
setup instruction on the web page soon.
* Load-informed scheduling
The agents running on real servers collect the load and memory information
and send them to the agent running on the LinuxDirector, and the agent
give load information to the ippfvs in the kernel, the ippfvs balances
packets over real servers according to load information.
+1: wensong
-1:
Status: someone may have already implemented this function.
Closed issues:
|
