SALSA

Cornell Information Technologies uses Project SALSA technology to provide a mechanism through which
users can get software distributions and updates delivered right to
their own computers. Exactly what software is delivered depends on
what packages you are subscribed to. For most of campus, the "Bear
Access" package is the most popular one. This mechanism relies on
the end user clicking on a service, getting prompted to download a number of files and then authorizing the architecture to download the
files with an affirmative response. The current deployment at Cornell utilizes one Project SALSA server from which all applications are served. For further information
see: http://salsa.cit.cornell.edu/

Three projects have been proposed:

1. Remote Workstation Maintenance through Project SALSA

Client

Project outline

We would like to add a new component to the architecture which allows an administrator to forcibly update a given machine using the same Project SALSA infrastructure. This would likely involve writing a mini "server" which runs on the client platforms listening for instructions from an administrative tool which would signal that there is new software to download. Key issues will be designing the technology to run on all target platforms as well as designing a method of broadcasting to all listening clients.

Technical

This software should run on Windows, MacOS and UNIX workstations, but the
initial implementation may not support all three

2. Project SALSA Server Manager for X/Windows

Client

Project outline

The tools used to populate the Project SALSA servers with software to distribute only run under MacOS and Windows. We would like to see an X/Windows interface for this tool so that UNIX users may easily upload software to be distributed as well.

Technical

The interface should run on Solaris, AIX, Linux computers.

3. Project SALSA Administrative Tool for UNIX/Linux

Client

Project outline

The SALSA mechanism does not adequately address the issues) of users who need to update key system files but who do not have appropriate permissions. It is also not the most effective way to download one-time software patches as it presumes the service launched will be used over and over again by the user thereby making it necessary to check every time for newer versions.

Imagine a client application which is run by a privileged user on a UNIX/Linux box and is used to obtain and automatically install system-level software. Such a tool could then be used to peruse available software packages for the particular UNIX OS you are running. The user can select the packages needed and click a button which will force them all to download and be installed.