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 Windows Agent 2.3
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.
New features (since 2.3.0):
-
The ProActive Agent can be controlled by non-admin users (specified during the installation).
-
The java runtime spawned by the ProActive Agent now runs in the security context of a non-admin user (specified during the installation).
-
All processes spawned by ProActive Agent are eventually killed in order to leave the resource completely clean.
-
Support of UNC (Unified Naming Convention) paths.
|
| Maintenance Release Notes: | (click to expand note) | Download ProActive Parallel Suite: |  |
14 January 2011 : ProActive Windows Agent 2.3.0
Bug
- [AGENT-63] - It seems that Agent uninstall does not remove all the files in C:/PF/PAG/
- [AGENT-70] - Error in the log
- [AGENT-72] - Add a better error handling for problem related to paths that contains mounted network drives.
- [AGENT-78] - System.NullReferenceException in addUserDefinedJvmParameters
- [AGENT-84] - SubInAcl is not installed by Agent installer
- [AGENT-88] - Guest account cannot run Agent Controller GUI
- [AGENT-89] - Only admin users can uninstall the ProActive Agent
- [AGENT-90] - On some jdk/jre distributions the jvm crashes due to hardcoded -Xms option
- [AGENT-92] - The default configuration file contains invalid values.
- [AGENT-93] - The pnp communication protocol is not supported by the agent
- [AGENT-94] - The configuration file is not writable by another user
- [AGENT-95] - The created user is not added to the Performance Analyser group during the installation
- [AGENT-97] - The Notepad opens en error message if there are no logs yet
- [AGENT-106] - User option not persisted - number of cpus
- [AGENT-109] - Agent GUI - number of runtimes not saved in configuration file
- [AGENT-114] - Agent Control for All Users is not functionnal
- [AGENT-117] - Registry key access restriction does not work on Windows 7 - 64 bits
- [AGENT-121] - When stopping the agent the parunas tool is killed without freeing ACE this can lead to SetUserObjectSecurity() will fails with ERROR_NOT_ENOUGH_QUOTA
Improvement
- [AGENT-39] - Account used to launch the ProActive Agent requires Log on as a service rigth assignment
- [AGENT-47] - Ask a "Restart Application Now ?" after configuration changes
- [AGENT-75] - The check for admin rights should be done in the .onInit Function
- [AGENT-76] - The UAC should be supported
- [AGENT-77] - The minimum required .NET Framework version should 3.5
- [AGENT-79] - It should be possible to install the service under a non-administrator account
- [AGENT-80] - When installed as non administrator account the ProActive Agent should be able to log to the user home dir
- [AGENT-81] - A non admin account should be able to control an installed ProActive Agent
- [AGENT-82] - Write logs to %TEMP% and config to %APPDATA%
- [AGENT-85] - Add info about the account created if not existing in config panel
- [AGENT-86] - Error message if service logon right is not set should be improved.
- [AGENT-87] - The config file should be copied if the config directory is customized at install time.
- [AGENT-91] - Rename "Add/Remove JVM Parameter" to "Add/Remove JVM Option"
- [AGENT-99] - When installed put the agent doc inside a doc directory.
- [AGENT-101] - Add "Runtime" to the Memory Limit in the GUI editor
- [AGENT-104] - Add double-click selection of the available Network Interface
- [AGENT-105] - Add Icon to the GUi editor window
- [AGENT-107] - The Resource Manager connection must use as default java class the 'unique' node starter
- [AGENT-110] - Children processes should not be able to escape from ProActive Agent JobObject.
- [AGENT-111] - When the agent service is installed under LocalSystem account the window of the spawned runtime(s) should be hidden from the logged user.
- [AGENT-118] - Reuse the iexplore process when viewing Logs
- [AGENT-119] - Reduce parunas verbosity
- [AGENT-120] - Use the same date layout in log files
New Feature
- [AGENT-73] - During agent installation create an account that will be used to install the ProActive Agent as a windows service
- [AGENT-113] - The agent service must be installed under LocalSystem and the login/password must be stored in a registry key with a restricted acces
Task
- [AGENT-83] - Updated doc for 2.3
- [AGENT-112] - The ProActive Agent must spawn runtimes under a non-admin user account
- [AGENT-115] - Update GPL v3 to AGPL v3 and headers in .cs files
- [AGENT-116] - Add pnps to the gui protocol list
|
02 February 2011 : ProActive Windows Agent 2.3.1
Bug
- [AGENT-122] - The parunas tool does not log errors
- [AGENT-123] - The ProActive Agent does not support Domain User Accounts (ie non-local accounts)
- [AGENT-125] - The GUI action to open the logs dir does not handle not existing directory
- [AGENT-129] - On Windows Server 2008, user creation fails
Improvement
- [AGENT-126] - During installation if the Domain is not local "." inform the user that the account cannot be created
Task
- [AGENT-128] - Update 2011 copyright header in the Agent GUI this is required for SCHEDULING-1073
|
28 July 2011 : ProActive Windows Agent 2.3.2
Main New Features:
Bug
- [AGENT-149] - Always available mode restarts weekly
- [AGENT-152] - The Screen Saver must affect all screens
- [AGENT-153] - During the installation the agent account login and password do not support unicode chars
- [AGENT-154] - the password of the ProActive Runtime account must encrypted
- [AGENT-162] - Update the dependency to Microsoft Visual C++ 2010 Redistributable Package
- [AGENT-163] - The cd must be agent install dir before calling pacrypt.dll from C#
- [AGENT-164] - If the user refuses to download SubInACL tool the installer doesn't show the correct warning message
- [AGENT-165] - The installer must forbid the use of "." as default local domain and use the %COMPUTERNAME% instead
Improvement
- [AGENT-148] - Add delay between multi-runtime start
- [AGENT-151] - if the PA Screen Saver is activated if the started runtime exits by itself it must be restarted with a delay
- [AGENT-155] - ProActive Agent Control should be able to change the runtime account
- [AGENT-156] - The enabled connection should appear as a select box
- [AGENT-157] - The Runtime Incoming Protocol should be moved from Connection tab to General tab.
- [AGENT-158] - The Runtime Incoming Protocol should be moved from Connection tab to General tab.
- [AGENT-159] - The aes key must be randomly generated at each installation
- [AGENT-160] - The aes keyfile permissions must be restricted to admin users and local system only
- [AGENT-161] - Add "Change Account" button explanation in the doc
|
|