Utah CPU Broker, Version 1.2.0
			------------------------------

The Flux Research Group at the University of Utah announces a new release of
the Utah CPU Broker, version 1.2.0.  This is a maintenance release that adds
support for TimeSys Linux version 4.1 and the usual variety of bug fixes.

Download the CPU Broker software, documentation, and papers at:
	<http://www.cs.utah.edu/flux/alchemy/>

Our recent RTAS 2004 paper describes and evaluates the CPU Broker in detail:
	<http://www.cs.utah.edu/flux/papers/cpubroker-rtas04-base.html>

The CPU Broker is a reservation-based resource manager for CPU time.  The
broker mediates between multiple real-time applications and the facilities of
an underlying real-time operating system: it implements a configurable CPU
management policy, monitors resource use, and adjusts allocations over time.
This architecture helps to ensure that the QoS needs of "important" tasks are
satisfied, especially when the relative importance of various tasks changes
dynamically.  An additional and important benefit is that the broker can
automatically determine many of the scheduling parameters of its client
applications.

The CPU Broker is implemented as a CORBA server that uses the TimeSys Linux
resource kernel APIs to manage CPU reservations.

The CPU Broker is currently being applied to the Unmanned Aerial Vehicle (UAV)
portion of the PCES Joint OEP.  The broker enables dynamic adaptation and
reallocation of CPU resources for UAV deployments: such adaptation is required
in response to the changing importance of various information flows (e.g., the
identification of time-critical targets), changing battlefield conditions
(e.g., assets and asset status), changing mission modes, and/or changing
missions.  The broker supports feedback and configurable strategy-based
policies for adaptation and handling conflicting reservations.  These
strategies can be driven or implemented by other QoS-enabling middleware, such
as QuO, and integrated with other resource management facilities (e.g., network
reservations and application-level adaptation strategies) as part of an overall
end-to-end QoS management solution.

Please send bug reports, questions, and comments to:
	<alchemy-users@flux.cs.utah.edu>