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
|
|
July 2012 : Matlab Connector 1.0
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.
New in Matlab Connector 1.0 :
- Reorganisation and repackaging of ProActive Matlab Connector, which is now separated from ProActive Scheduler
- It is now shipped as two separate archives one for Matlab and one for Scilab which integrates a toolbox, a documentation, and a scheduler plugin which can be installed in the addons folder of the scheduler server in order to use Matlab or Scilab within the scheduler.
- Interactions between the Matlab/Scilab toolboxes and the scheduler are now done via a separate JVM.
- New mechanism for worker configurations which allows to do a single configuration for several machine groups
- Improved connection and disconnection process to the scheduler, added optional SSH key files
- Added more configurable options in PAoptions
- Improved TansferEnv option to transfer both local and global variables, added support for TransferEnv in Scilab
- Improved overall stability
|
| Maintenance Release Notes: | (click to expand note) | Download ProActive Parallel Suite: |  |
20 July 2012 : Matlab Connector 1.0.0
Bug
- [MSC-3] - Ruby exception in selection script when using Matlab/Scilab extensions from the addons directory
- [MSC-4] - Middleman JVM is not killed properly on exit if the matlab session is not connected to a scheduler any more.
- [MSC-6] - Matlab connection to middleman doesn't work on MacOS (X Lion)
- [MSC-19] - Scilab extension doesn't work on jdk 1.5
- [MSC-26] - Cannot open help in matlab 2009b (and later) after using ProActive
- [MSC-31] - Wrong java path of Middleman JVM on Windows (Matlab&Scilab)
- [MSC-32] - unwanted selection script debug info are printed (Windows)
- [MSC-33] - Error when setting custom script to null (Matlab & Scilab)
- [MSC-37] - The scilab CheckScilabXXXX.log file is not deletable after task execution.
- [MSC-39] - NPE in method compressLogs (ResultsAndLogs)
- [MSC-41] - exceptions thrown by hasLicense call to LicenseSaver due to duplicate ids should be caught (Matlab)
- [MSC-42] - login is not stored when connecting with credentials, which can create a conflict with LicenseSaver (Matlab)
- [MSC-50] - Missing macro file "who_user1.sci" in Scilab toolbox
- [MSC-51] - Typo in TestPATask (test fails because of that)
- [MSC-173] - ClassNotFoundException in login when an unexpected problem appears
- [MSC-175] - Bug in PAoptions parser on Windows 7
- [MSC-176] - log4j-client file used in the toolboxes must not use the NULL appender
- [MSC-177] - Force kill of Middleman JVM when reconnecting to the scheduler
- [MSC-179] - The README.txt is not up to date
- [MSC-184] - release-prepare.sh should build either Matlab or Scilab dist
Improvement
- [MSC-7] - Add the possibility to specify a private SSH key in PAconnect (Matlab & Scilab)
- [MSC-8] - Improve Error messages when scheduler is disconnected from Matlab/Scilab toolboxes
- [MSC-12] - The scilab doc contains unix only paths
- [MSC-27] - Transfer Scheduler interaction to a separate JVM (Matlab & Scilab)
- [MSC-28] - Refactor Matlab/Scilab code
- [MSC-29] - Improve TransferEnv option (Matlab and Scilab)
- [MSC-35] - Close log files properly in Matlab and Scilab extensions
- [MSC-43] - PAwaitFor and PAwaitAny should print warnings in case of Task errors (instead of throwing an Error) (Matlab/Scilab)
- [MSC-44] - Custom selection scripts should be configurable as static or dynamic (Matlab & Scilab)
- [MSC-45] - Add support of scheduler's GlobalSpace in Matlab/Scilab
- [MSC-48] - On Matlab client side centralize all communication related code in teh forked jvm.
- [MSC-171] - Group Matlab & Scilab worker configuration files to a single file
- [MSC-178] - CheckMatSci selection script should be configurable static or dynamic for debugging purpose
- [MSC-181] - The ScilabWorkerConfiguration.xml should contain examples in comments
- [MSC-182] - Remove duplicates in the Scilab release
Task
- [MSC-1] - Import Matlab/Scilab connector code from the Scheduler
- [MSC-5] - Change Matlab and Scilab node configuration scheme after removing Matlab/Scilab from the scheduler project
- [MSC-9] - Update Matlab&Scilab doc with MiddleMan JVM changes
- [MSC-30] - Remove KeepEngine option
- [MSC-40] - Remove path checks on Matlab and Scilab selection scripts
- [MSC-47] - Remove matlab xml job files from samples
- [MSC-49] - Change Matlab and Scilab job names and job description
- [MSC-170] - Add functional Tests to Matlab/Scilab connector
- [MSC-172] - Package Matlab and Scilab toolboxes in separate zips
- [MSC-174] - Organize matlab/scilab connector release packaging
- [MSC-183] - finalize documentation of release 1.0.0
|
|