You are here

LCFG log server replacement

Project ID: 
57
Current stage: 
Manager: 
Unit: 
What: 

Description: The current log server does a lot more than just server LCFG logs from the client machines. It also serves documentation, resource and status information. It would be good to replace the log server with a new info server which would feature improved internals and preferably a set of templates for the interface to extract the html interface from the Perl code.

There are a number of additional features that would be very useful to have available. These include:

  • Authentication and authorisation - Based on some standard system so that sites could plug in their own system. For Informatics we could use cosign for user authentication but other places have different systems.
  • Delivery of all logs via https - Some logs possibly contain sensitive data which cannot be transferred over the wire in the clear. Currently several logs are locked out so that the log server cannot deliver them. If we provided https support and strong authentication/authorization we could securely deliver all logs and status information.
  • Single point of access - Currently the logs are not visible outside of the local network. With the user authentication and authorization and https support in place we could securely deliver the information to any host. There is a problem though that we would probably need to open up the firewall on this port for every client machine. This might produce an unacceptable security hole. What could be better would be to produce a secure proxy server through which all the information is delivered to external hosts.

Deliverables:

Why: 

Customer:

Case statement:

When: 

Status: Pending - probably best wait until after LCFG core refactoring project

Timescales:

Priority: Wish list

Time:

How: 

Proposal:

Resources:

Plan:

Other: 

Dependencies:

Risks:

Milestones

Proposed date Achieved date Name Description