From igc.apc.org!notes Sun Nov 29 15:37:11 1992 From: arni@web.apc.org (Arni Mikelsons) Date: 24 Nov 92 13:17 PST Subject: - Host software development To: Recipients of conference "tech.smallsys" Message-Id: <269400019%web.apc.org@igc.apc.org> Host System: Software, Documentation and Administration The host software is run on a central computer which communicates either internationally or with another network in the region. The most urgent need in this area is to provide appropriate documentation for system operators. This documentation should outline aspects of technical operations and provide a basic guide to systems adminstration. A number of critical lessons have been learned about system operation and administration and it is important that these be passed on to new system operators. The host software is currently far less developed than the user software. It consists of a commented batch file and the technical documentation that accompanies the component pieces of software. Two trains of thought came out of the Global Networking Workshop with respect to development of host software. On the one hand, it was felt that it should be possible to run a host with only a slight modification to the user software. This would make it possible for a user to start a host with a short training course, or diligent reading of the accompanying documentation. On the other hand, busy hosts need to take advantage of programmes that are more robust and will work faster to minimise the amount of time the system is off-line. Both of these situations could be accommodated by two host upgrades. A standard upgrade would use the same component software as ELF, but have added modules that are required for running a host. The advanced upgrade would have further enhancements including a possible recommendation for node operators to purchase existing commercial software (e.g. GoldEd, TB-Edit, and SQUISH) that may cost as much as US$500. Efforts are currently underway to arrange for reduced cost or free distribution of these products to networks in developing countries. Both upgrades would have both generic and specific documentation. Conference manager capabilities are perhaps the most important addition to the host software. These enable the operator to establish or cut off conference feeds to users or other systems. A new packer, and a tool that allows editing of the compiled node list files as well as billing software are also badly needed. One important and necessary feature of the host upgrade is system performance tracking using tools such as message trackers, utilities for message format conversion, and destination redirection. Most of these tasks are done by separate utilities that pass over the message base several times. Incorporation of these tools together into one tool would save both time and wear and tear on the hard disk. The most important of these utilities is the message tracking software which generates a listing stating the size of each message, who sent it and who it was sent to. This file would be entered into the billing software to generate invoices. Currently, one of the shortfalls of message tracking programmes is that they cannot track conference volumes. Specific required modifications to the existing host software include: - improvements to the ability to monitor and account for messages moving to and from the system. This requirement is essential for the installation of an effective means of billing for these messages; - improved systems for addressing messages to and from academic, commercial and nonprofit systems in the developed world; - developing utilities and programs to make the software multi-lingual - installing better systems for maintaining on-line conferences - an easy-to-use and robust billing system to invoice for both local system usage and international electronic mail traffic. Short term host software development In the short term (0 - 3 months) final decisions will be made on programmes to be included in the standard and advanced host upgrades. Then, the new programmes will be incorporated into the batch file that runs the host, GOFDHOST (2 days). Medium term host software development In the medium term (3 - 6 months), new features will start to be incorporated into the host upgrade to ELF. The following improvements will be included: - configuration for easy modification to routing files. Currently, the routing configuration file must be edited with a text editor (5 days); - a conference management tool that is geared to maintaining conferences. A user seldom has to perform many more functions than reading conference items, and deleting them if there are too many. A host operator will need to use tools automatically do these functions. The interface for doing this needs to be improved (7 days); - integrate and develop tools such as message trackers, utilities for message format conversion and destination redirection and editors for compiled nodelist files (12 days); - incorporate billing software into host system. (5 days). Improvements must be made to the logging software. Some of these things are done separately, what is needed is a logging programme that will perform all of these functions in one pass through the message base. The features include: - logging the amount of traffic going through the system, who is sending it and where it is being sent . This will form the basis of the billing software (5 days); - tracking conference volumes. This will be useful for billing users who will want networked private conferences and assessing costs of carrying various conferences (5 days); - recognising the @ symbol in a user@host string and to address the message to the "host". Currently, systems carry the user lists for all APC systems, which takes up a lot of disk space. If the system were to recognise the host name, then the correct address could be inserted without having to know all the users on every system. (1 day); - scanning messages for redirection to other systems, which could be users or hosts. Because of the addressing system in Fido, each user is a point. If a message is received on a host for Jane Doe, in the above format, the logging software will ensure the message gets translated into Fido language and goes to the correct point (3 days); - reformatting the headers correctly, for systems that are Internet gateways. This is to ensure that until the message reaches a gateway system the message remains in the fido format (8 days); - releasing a test version of host upgrade to ELF. Evaluate ease of use of the current set-up and improvements that could be made in conjunction with documentation of the system. Long term host software development In the long term (6 - 12 months), the following activities will be performed: - software evaluation and incorporation the results into the ELF Host Upgrade. This will be done in conjunction with documentation of the software. (12 days); - Official release of ELF host upgrade with documentation.