Dec. 12, 2012 ProActive V5.3.2 is out!
|
Studio 1.2
The goal of ProActive Matlab Connector is to equip Matlab with a generic interface to Grid and Cloud computing. It is composed of a Matlab toolbox. It allows the deployment of Matlab instances on several nodes of various infrastructures, and to use these instances like computing engines. The submission of Matlab tasks to be distributed over nodes is achieved seamlessly and directly from the usual Matlab interactive environments.
This package features :
-
Run functions on remote computers, Grids, and Clouds.
-
Do not block the local session while remote results are being produced.
-
Seamlessly retrieve results when you need them, just as if the functions were run locally.
-
Provide you with detailed remote log/output information, altogether with errors if any occurred.
-
Disconnected mode, where the local session doesn't need to remain open while the job is processing.
-
Automatic source transfer, data file transfer, transfer of local workspace, and other configurable options.
| Matlab Connector 1.1
The goal of ProActive Scilab Connector is to equip Scilab with a generic interface to Grid and Cloud computing. It is composed of a Scilab toolbox. It allows the deployment of Scilab instances on several nodes of various infrastructures, and to use these instances like computing engines. The submission of Scilab tasks to be distributed over nodes is achieved seamlessly and directly from the usual Scilab interactive environments.
This package features :
-
Run functions on remote computers, Grids, and Clouds.
-
Do not block the local session while remote results are being produced.
-
Seamlessly retrieve results when you need them, just as if the functions were run locally.
-
Provide you with detailed remote log/output information, altogether with errors if any occurred.
-
Disconnected mode, where the local session doesn't need to remain open while the job is processing.
-
Automatic source transfer, data file transfer, transfer of local workspace, and other configurable options.
| Scilab Connector 1.1
The ProActive Scheduler allows easy distribution of all your applications (Native, Java, Scripts, Matlab, Scilab, GPU, etc.), together withDynamic Workflows. It provides automatic input and output file transfer, fault tolerance, resource selection and configuration through scripting (Javascript, Ruby, Python), multi-core and topology control.
| Scheduler 3.3
ProActive Java Active Objects (Programming) is an open source Java library aiming to simplify the programming of multithreaded, parallel, and distributedapplications for Clouds, Grids, multi-cores, clusters, and data-centers.
Java Active Objects features a concurrent and parallel programming model, offers distributed and asynchronous communications, mobility and a deployment framework. | Java Active Objects 5.3
The Scheduling and Resource Management Rest APIs provide a language-independent access to the Scheduler.
Use this interface to seamlessly integrate orchestration and scheduling in you own portal.
Main Features:
| Rest API 1.3
The Scheduler Web portal provides a platform-independent access to the Scheduler.
Main Features:
-
Full visualization of Job and Task details
-
Full access to output and logs in streaming mode
-
GUI and Activation for Data Servers (File Transfer)
-
Remote Visualization of Graphical Tasks
-
Graphical monitoring of Workflow execution directly from the portal.
| Scheduler Web Portal 1.3
The Cloud & Grid IaaS Web portal provides a platform-independent access to the Resource Manager.
Main Features:
- Full visualization of resources, physical and virtual machines
- Full control on resources, deploy or remove resources on desktop PCs, clusters, clouds...
- Graphical monitoring of resource usage
| Cloud & Grid IaaS Web Portal 1.3
The ProActive Cloud & Grid IaaS Server is the software for coupling distributed resources in order to solve large-scale problems. The distributed resources are represented by Java virtual machines launched on desktop computers, clusters or clouds.
The Cloud & Grid IaaS Server provides a single point of access to all resources enabling an effective way of selecting them for computations with different criteria.
| Resource Manager 3.3
The ProActive Linux Agent allows to automatically start and monitor resources on Linux machines.
Main Features:
-
Automatic start, stop according to a weekly schedule.
-
Automatic monitoring and restart of forked processes.
-
Limit available system resources (cpu, I/O, memory).
-
Integrated with ProActive Cloud & Grid IaaS.
-
Same XML configuration file than the ProActive Windows Agent.
-
Can be started as a system daemon or as a regular executable without any special permissions.
| Linux Agent 1.0
ProActive Windows Agent is a Windows Service: a long-running executable designed not to require user intervention. The agent is able to create a ProActive computational resource on the local machine. This resource will be provided to ProActive applications (such as the Cloud & Grid IaaS Server) according to the user defined planning.
Main features:
-
User defined weekly planning.
-
Local Registration of a ProActive node.
-
Cloud & Grid IaaS Server registration of a ProActive node.
-
Automatic restart of the spawned java process in case of failures.
-
RAM limitation of the spawned processes.
-
CPU limitation (throttling) of the spawned processes.
| Windows Agent 2.4
|
|
January 2011 : ProActive Linux Agent 1.0.0
The ProActive Linux Agent allows to automatically start and monitor resources on Linux machines.
Main Features:
-
Automatic start, stop according to a weekly schedule.
-
Automatic monitoring and restart of forked processes.
-
Limit available system resources (cpu, I/O, memory).
-
Integrated with ProActive Cloud & Grid IaaS.
-
Same XML configuration file than the ProActive Windows Agent.
-
Can be started as a system daemon or as a regular executable without any special permissions.
|
| Maintenance Release Notes: | (click to expand note) | Download ProActive Parallel Suite: |  |
28 January 2011 : ProActive Linux Agent 1.0.1
Bug
- [LINAGENT-57] - Old release of libxml2 are not able to parse agent-linux.xsd
- [LINAGENT-60] - <ionice [....]> can throw unhandled exception on Centos
- [LINAGENT-61] - Bad handling of ionice/classdata in JVMStarter._pinit
- [LINAGENT-62] - Capture the output of a forked process ASAP instead of waiting its termination
- [LINAGENT-64] - CLASSPATH should be extracted from programming and scheduling instead of listing /dist/lib/
- [LINAGENT-69] - The testsuite is not compatible with older version of coverage.py
- [LINAGENT-70] - Code coverage is always enabled when the test suite is run
Improvement
- [LINAGENT-58] - Better error message when the default configuration file is not found
- [LINAGENT-59] - Provide a script to easily workaround bug #347316 in libxml2 when the system libxml2 cannot be updated
- [LINAGENT-67] - TestNumberOfCPU should not fail when lscpu is not available
- [LINAGENT-68] - build_lxml should use http instead of ftp to download libxml2 and libxslt
- [LINAGENT-72] - More portable default config file
Task
- [LINAGENT-63] - Add copyright
- [LINAGENT-65] - Rename AUTHORS in AUTHORS.txt to be consistent with other txt files
- [LINAGENT-66] - Add lxml related file into the distribution
|
20 July 2012 : ProActive Linux Agent 1.0.2
Bug
- [LINAGENT-52] - Cannot start the agent due to missing cgcreate command
- [LINAGENT-54] - agent status is not clean after calling /etc/init.d/proactive-agent stop
- [LINAGENT-56] - RPM does not build on Centos 5.5
- [LINAGENT-73] - Bad error handling when cgroup filesystem is not mounted
Improvement
- [LINAGENT-71] - Better RPM Packaging
- [LINAGENT-74] - Exclude lxml directory from find_package()
- [LINAGENT-75] - Default configuration file should be /etc/proactive/agent/agent.xml rather than /etc/proactive/agent.xml
- [LINAGENT-76] - Add daemon option
- [LINAGENT-77] - redhat/agent.xml should work on RHEL 5
- [LINAGENT-78] - init script compatibility with RHEL 5
Task
- [LINAGENT-79] - Remove distribution specific scripts from the sources
- [LINAGENT-80] - Remove doc/ from sdist
- [LINAGENT-82] - current centos package does not work with centos 6
|
|