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
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 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
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 2011 : Scheduler 3.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.
Main New Features
-
Web portal for a platform-independent access to the Scheduler.
-
Graphical monitoring of Workflow execution from the portal.
-
REST API for a language-independent access to the Scheduler.
-
MapReduce capabilities with Hadoop-compliant job definition.
-
Improved Matlab support, with runAsMe capabilities (i.e. running Matlab engine under the OS level user ID).
-
Completed Scilab support.
-
Compatibility with the new ProActive License Saver for automatic license token management.
-
New Node Source policies and infrastructure managers (CRON-like, CLI-like, Simple local deployment, ...).
-
Statistic usage and monitoring data, and graphical view on RCP clients.
-
Better control of job execution with :
-
Stand-alone job definition with Job Archive.
-
Support for Oracle DB.
-
Many other improvements (better database disconnection handling, access to previous incarnation tasks for better error diagnostic, better task log storage and access with preciousLogs attribute, ...).
|
| Maintenance Release Notes: | (click to expand note) | Download ProActive Parallel Suite: |  |
28 July 2011 : Scheduler 3.1.0
Bug
- [SCHEDULING-236] - SchedulerCore pings node and not TaskLauncher
- [SCHEDULING-358] - Matlab's engOpenSingleUse or engOpen calls hang when available Matlab licence cannot be found
- [SCHEDULING-414] - ProActive Scilab extension requires Scilab bin directory to be put in the system path (Windows)
- [SCHEDULING-415] - Scilab extension can't handle dual Scilab/Matlab installation on the same host (Windows)
- [SCHEDULING-417] - In ldap.cfg KeyStore and Trustore paths for LDAPLoginModule cannot be set with relative paths.
- [SCHEDULING-523] - A problem occurs only with DEBUG log for the node with Windows Agent (1 node, 1 scheduler, 1 rm on the same host on Windows XP)
- [SCHEDULING-579] - Matlab extension on Windows faces random crashes of the Matlab engine
- [SCHEDULING-590] - RM never kills OutOfMemory JVM nodes
- [SCHEDULING-617] - At RM connection time, RCP does not display some button that should be enabled
- [SCHEDULING-623] - At RM rcp startup, some button are not activated until clicking on menu or mouse right click
- [SCHEDULING-630] - At Scheduler RCP deconnection some button are not unactivated
- [SCHEDULING-735] - In Scilab integration PAsolve('func',list_args) may return incorrect result
- [SCHEDULING-736] - Scilab integration doesn't work with Scilab 5.2
- [SCHEDULING-797] - RM cannot access to the DB to store events after a long run
- [SCHEDULING-832] - The command line client path completion does not work on windows
- [SCHEDULING-883] - Matlab selection scripts with side effects should be handled correctly in the resource manager
- [SCHEDULING-926] - Ptolemy interface truncates matlab's double results
- [SCHEDULING-964] - connection lost to the resource manager - client remains in connected state
- [SCHEDULING-965] - exception when disconnecting rm rcp
- [SCHEDULING-987] - Bring back the connection dialog on failed authentication
- [SCHEDULING-1025] - Matlab Extension on Windows 64 bits requires a patch
- [SCHEDULING-1031] - Duplicate terminateProxy should not be possible when terminated RMproxy for a specific user
- [SCHEDULING-1061] - Node configuring phase should not set the node owner
- [SCHEDULING-1065] - Scheduling default policy is not so fair according priority
- [SCHEDULING-1071] - NPE in org.ow2.proactive.scheduler.common.job.factories.JobFactory_stax - line 1626 - when logger category SchedulerLoggers.FACTORY is in DEBUG mode
- [SCHEDULING-1080] - if a forked JavaTask is killed (by killjob()), the scracth directory is not deleted.
- [SCHEDULING-1089] - Limited selection in DataServer view table in Windows RCP build
- [SCHEDULING-1090] - Modal 'Add server' dialog looks weird in windows RCP
- [SCHEDULING-1094] - dll files must be copied from lib/proactive to dist/lib
- [SCHEDULING-1096] - exec duration does not take into account the input data space transfert
- [SCHEDULING-1103] - Error in documentation on forkflow graphics
- [SCHEDULING-1104] - Variables are not evaluated inside topology tag in XML descriptor
- [SCHEDULING-1108] - Improve Starting stability of Matlab Engine on Windows
- [SCHEDULING-1115] - For a NativeTask, when the executable does not exits, a npe occurs in doTask() !
- [SCHEDULING-1119] - derby ERROR 40XL1: A lock could not be obtained within the time requested
- [SCHEDULING-1128] - Windows HPC Nodesource doesn't work
- [SCHEDULING-1130] - InfrastructureManager.getDefaultCommandLineBuilder returns a wrong java path
- [SCHEDULING-1132] - When clsoing the dataserver view, the dataserver is stopped
- [SCHEDULING-1137] - Faulty task becomes Pending afeter job paused
- [SCHEDULING-1139] - Credentials#getCredentialsBase64(byte[]) hangs in some cases
- [SCHEDULING-1147] - ./scheduler-client -u rmi://localhost/ -c throws a NPE
- [SCHEDULING-1153] - At recover time, running task should move to pending status
- [SCHEDULING-1159] - missing @ActiveObject on every Active Object in Resourcing
- [SCHEDULING-1163] - Accounting does not manage some aspect as restart/preempt/kill task
- [SCHEDULING-1187] - CreateCredential windows freezes in RM RCP.
- [SCHEDULING-1188] - If Job.logFile is set, Scheduler.listenJobLogs does not retrieve all the output of already running tasks
- [SCHEDULING-1189] - Transfer from local to global is included in exectime
- [SCHEDULING-1196] - Dataspaces with ForkedJavaTask/runAsMe/Windows cannot work
- [SCHEDULING-1197] - Dataspace SCRATH dir is not removed after killTask action
- [SCHEDULING-1204] - Update eclipse .classpath
- [SCHEDULING-1207] - InternalTask#replicate is slow if the task contains large primitive arrays
- [SCHEDULING-1210] - RMCachingProxyUserInterface ignores NODE_REMOVED and NODE_STATE_CHANGED events
- [SCHEDULING-1214] - Uncommit undesired hibernate config file due to a commit error
- [SCHEDULING-1215] - patched common-vfs jars should be updated in Scheduler RCP client libraries
- [SCHEDULING-1219] - By default, logs of Forked Java Task should be written by a RollingFileAppender
- [SCHEDULING-1222] - Task arguments are not read properly in auto-init method in javaExecutable
- [SCHEDULING-1232] - getProgress with forked java executable has some issues
- [SCHEDULING-1233] - Remove ForkedJavaTaskLauncher.getProgress() method which seems to be useless
- [SCHEDULING-1236] - missing @XmlTransient on InternalTask.ideps
- [SCHEDULING-1237] - latJobFactory.getFactory().createNativeJobFromCommandsFile usage in RCP should be fixed
- [SCHEDULING-1240] - BatchJobInfrastructure should be able to read more than one line of output to extract the job ID
- [SCHEDULING-1243] - Race condition in the core AO
- [SCHEDULING-1244] - Pinger thread calling getProgress on a ForkedJavaTaskLauncher must not reached the forkedVM and throw an exception if forked VM is dead.
- [SCHEDULING-1247] - exponential recursion in JobDescriptorImpl#doReplicate
- [SCHEDULING-1248] - InternalTask#replicate takes too long
- [SCHEDULING-1249] - Scheduler fails to recover running jobs containing executed IF tasks
- [SCHEDULING-1250] - JobInfo update for a finished job should be commit in the same transaction as "last" taskInfo update in the same method (core.terminate(task))
- [SCHEDULING-1251] - bin\windows\pa-dataserver-gui.bat does not work
- [SCHEDULING-1254] - missing @ActiveObject on every Active Object in Scheduling
- [SCHEDULING-1259] - Race condition in the compact view of RM RCP
- [SCHEDULING-1264] - When defining a job classpath with / separator from a windows client, the jobclasspath jar is not correct
- [SCHEDULING-1270] - Exception when calling shutdown() in rm-client
- [SCHEDULING-1272] - missing method in SchedulerProxy
- [SCHEDULING-1276] - LocalInfrastructure doesn't work when spaces are in RM_HOME
- [SCHEDULING-1277] - SSHInfrastructure doesn't work if whitespaces are in RM_HOME
- [SCHEDULING-1292] - TestMultipleHostsRequest "seems" to work
- [SCHEDULING-1294] - reloadPermission in Scheduler client causes an exception
- [SCHEDULING-1296] - BadFileDescriptor Exception occurs sometimes when closing IOThreads
- [SCHEDULING-1300] - Typo in TestPATask (test fails because of that)
- [SCHEDULING-1301] - Deadlock occurs at least in RMCore/RMNodeConfigurator because of missing stub
- [SCHEDULING-1305] - Error when displaying PATasks(Scilab)
- [SCHEDULING-1308] - If matlab client uses RunAsMe option the matlab task must define a forkEnvScript that transmits a valid java.io.tmpdir property to the forked jvm
- [SCHEDULING-1309] - If matlab client uses RunAsMe option the matlab worker jvm can crash if the client user has never started any matlab session on the worker host
- [SCHEDULING-1312] - Topology view cannot handle the host removal
- [SCHEDULING-1315] - FastSelector fails with "*" in job outputfiles
- [SCHEDULING-1317] - StartForkProcessException when using RunAsMe on Windows
- [SCHEDULING-1319] - Fix Multiple Submits in Scilab extension
- [SCHEDULING-1328] - In KeepEngine mode (scilab), errors in remote scilab code are not reported
- [SCHEDULING-1329] - Log files must be in "append mode"
- [SCHEDULING-1331] - Typo in PAResult_PAwaitFor.sci Java exceptions not printed
- [SCHEDULING-1333] - Set PA_scheduler_dir in loader.sce
- [SCHEDULING-1334] - Error message when terminating Scheduler RCP (a widget is disposed while updating its state)
- [SCHEDULING-1337] - No default name for MapperPATask
- [SCHEDULING-1338] - StreamCorruptedException when using Fork or RunAsMe in Matlab and Scilab extensions (with Nodes deployed in rmi)
- [SCHEDULING-1339] - Build of MapReduce example is broken
Improvement
- [SCHEDULING-780] - Client correspongind to Provider connection should be removed when the node is removed.
- [SCHEDULING-802] - It should be possible to set a maximum number of nodes used by the same user at the same time
- [SCHEDULING-837] - schemaLocation in samples/jobs_descriptor/*.xml files should refer the http public url
- [SCHEDULING-1069] - Improve the way the "getNextcompatibleTasks" method is used
- [SCHEDULING-1070] - Build script must be improved using new stub generator
- [SCHEDULING-1083] - Missing chapter concerning java policy file in Matlab Documentation
- [SCHEDULING-1086] - SchedulerProxyUserInterface: add an init method that support a CredData object as parameter
- [SCHEDULING-1091] - See "All jobs" or only "My jobs" in Scheduler RCP Job view
- [SCHEDULING-1092] - Add a "You are connected as $USER" in Scheduler RCP
- [SCHEDULING-1093] - Add release script to simplify release process
- [SCHEDULING-1097] - Dataspace INPUT and OUTPUT transfert duration should be computed and logged
- [SCHEDULING-1105] - Inside XML descriptor, file path should be relative to XML file instead of path where JVM was started
- [SCHEDULING-1116] - proactive.scheduler.logs.maxsize java property should have a "to be defined" default value !
- [SCHEDULING-1126] - Adding on-the-fly selection scripts specified by the scheduler administrator
- [SCHEDULING-1129] - Create a Local Infrastructure Manager
- [SCHEDULING-1131] - RMNodeStarter.CommandLineBuilder should handle Java executable path with white spaces
- [SCHEDULING-1133] - Related to SCHEDULING-845, remove useless cast for major release when fetching progress state
- [SCHEDULING-1135] - It should be possible to blacklist nodes in the RM
- [SCHEDULING-1142] - TaskLauncher immediates services must be set by annoation instead of setIS() calls.
- [SCHEDULING-1143] - When SelScript fails, the task result should be the whole exception instead of the message only
- [SCHEDULING-1145] - Add compilation information for ptolemy on Scheduling manual
- [SCHEDULING-1154] - org.ow2.proactive.utils.console.MBeanInfoViewer should provide a method that returns mbean attributes as a map of [attribute|value]
- [SCHEDULING-1162] - Improve the display of the help command in the consoles
- [SCHEDULING-1170] - Default "4 local nodes" deployment in RM must be implemented with LocalInfraManager
- [SCHEDULING-1172] - Forked java task should be forked in an other way
- [SCHEDULING-1173] - We should use LocalInfrastructure instead of GCMD to deploy the 4 default nodes at RM startup
- [SCHEDULING-1175] - SchedulerFrontend is missing a method that renews the lease of the caller
- [SCHEDULING-1181] - Name the different threadPool used in RM and Scheduler to have better experience on reading stack dump
- [SCHEDULING-1182] - Rename "node owner" into "used by"
- [SCHEDULING-1183] - Compact view in the RM RCP consumes a lot of CPU time
- [SCHEDULING-1193] - Regroup jars in lib directory
- [SCHEDULING-1194] - Move out the generic deployment part from SSHInfrastructure
- [SCHEDULING-1200] - Clean node.dataspace.scratch dir property usage
- [SCHEDULING-1205] - Infrastructure name cannot contains spaces
- [SCHEDULING-1224] - The nodesource name property should be automatically set for any nodes.
- [SCHEDULING-1226] - The JobClasspath should not be stored for each job in Scheduler DB
- [SCHEDULING-1227] - Remove JVMs from TreeView in the RM GUI
- [SCHEDULING-1229] - Update Mysql connector/J to the latest revision available
- [SCHEDULING-1231] - Improve feedback on dataspaces issues after task execution
- [SCHEDULING-1234] - Improve accounting computation in the scheduler
- [SCHEDULING-1245] - Display the full statistic history in RM/Scheduler RCPs
- [SCHEDULING-1246] - JobID and TaskID should be available when defining input and output files
- [SCHEDULING-1253] - Reduce the memory consumption by selection script statistics and limit the statistics to avoid OOM
- [SCHEDULING-1255] - add credentials login in sched and rm rcps
- [SCHEDULING-1256] - Increase the value of spring force in the topology view
- [SCHEDULING-1257] - Rename Vm -> JVM, host -> VM (when it's vm) in RM RCP
- [SCHEDULING-1258] - Add host statistics in the stat view
- [SCHEDULING-1269] - Remove connected user history from RM statistics
- [SCHEDULING-1278] - Arguments fields must be used to escape the command properly (% escape cannot be used anymore)
- [SCHEDULING-1291] - Add jarindex in Scheduling mapreduce library
- [SCHEDULING-1293] - Make Scilab extension run in asynchronous mode
- [SCHEDULING-1310] - The selection script "MatlabReservationScript" should not be added to the matlab task if no "LicenseServerURL" is defined
- [SCHEDULING-1311] - It seems that the file_matlab_finder.rb selection script doesn't close the opened FileOutputStream to the file CheckMatlabXXXXXXX.log
- [SCHEDULING-1324] - Avoid reloading PAoptions.ini file each time PAoption function is called
- [SCHEDULING-1330] - Scilab Extension must support RunAsMe
- [SCHEDULING-1332] - The MATLAB task with RunAsMe requires a js prescript
New Feature
- [SCHEDULING-96] - Scheduler RCP should provider output per task
- [SCHEDULING-104] - Add precious log
- [SCHEDULING-343] - It would be useful to be able to kill one particular running task of a job
- [SCHEDULING-346] - Support for node deployment to DRMAA infrastructure in resource manager
- [SCHEDULING-365] - Manage connection lost between remote database and Scheduler core.
- [SCHEDULING-845] - Allow Java Tasks to update their advancement state
- [SCHEDULING-1112] - give access to previous incarnations of a faulty task
- [SCHEDULING-1164] - Add preempt (admin only), restart, and kill task in a contextual menu of the tasks view in RCP
- [SCHEDULING-1203] - Make it possible to update the configuration of the resource manager in runtime
- [SCHEDULING-1212] - Implement the CronSlotLoadBasedPolicy
- [SCHEDULING-1223] - Access to dataspaces from envScript
- [SCHEDULING-1266] - Support map-reduce framework in the Proactive Scheduler
Story
Task
- [SCHEDULING-1042] - Add Scilab extension documentation
- [SCHEDULING-1102] - duplicate setter org.ow2.proactive.scheduler.common.task.Task.setFlowBlock
- [SCHEDULING-1123] - Make Matlab & Scilab extensions work with Scheduler clients packages as well as Scheduler server
- [SCHEDULING-1176] - RM default 4 local nodes start should use the LocalInfrastructure instead of GCM application
- [SCHEDULING-1199] - Rename scheduling node configuration properties and add corresponding documentation.
- [SCHEDULING-1206] - add RM(caching)ProxyInterface classes
- [SCHEDULING-1213] - Add ZipUtils and update JarUtils in order to prepare job archive
- [SCHEDULING-1221] - Add Oracle Database compatibility to Scheduler and RM
- [SCHEDULING-1225] - Use a specific icon/color for vitual machines in RM GUI
- [SCHEDULING-1273] - Remove Java 1.5 references in documentation.
- [SCHEDULING-1314] - Update Matlab Toolbox Documentation
Story Item
- [SCHEDULING-1156] - User tasks logs events list should be packed and compressed to be stored in database.
- [SCHEDULING-1157] - User tasks logs should be written in a file at node side, user could retreive the create file through dataspace
- [SCHEDULING-1217] - Add job archive in scheduler job factory and controller
- [SCHEDULING-1218] - Add job archive submission to Scheduler RCP
|
14 November 2011 : Scheduler 3.1.1
Bug
- [SCHEDULING-1268] - Remove "Statistic HIstory" from CLI statistics
- [SCHEDULING-1274] - TestJobDataspaceSubmission doesn't work on Windows
- [SCHEDULING-1279] - TestJobFork has a bad URI API usage
- [SCHEDULING-1280] - TestJobFork doesn't work on Windows
- [SCHEDULING-1281] - TestJobKilled doesn't work when project path contains a white space
- [SCHEDULING-1282] - TestJobMultiNodesSubmission doesn't work when project path contains a white space.
- [SCHEDULING-1283] - TestJobMultiNodesTopologySubmission doesn't work when project path contains a white space.
- [SCHEDULING-1284] - TestJobNativeSubmission doesn't work on Windows or when project path contains a white space
- [SCHEDULING-1285] - TestJobPrePostSubmission doesn't work if project path contains a white space
- [SCHEDULING-1286] - TestJobSelScriptSubmission doesn't work if project path contains a white space
- [SCHEDULING-1289] - TestJobTaskFlowSubmission doesn't work if the project path contains a white space
- [SCHEDULING-1290] - TestJobWithInvalidSelectionScript doesn't work if the project path contains a white space
- [SCHEDULING-1297] - TestMultipleHostsRequest doesn't work on Windows or if the project path contains a white space
- [SCHEDULING-1298] - TestPreemptRestartKillTask doesn't work if the project path contains a white space
- [SCHEDULING-1299] - TestProcessTreeKiller doesn't work on Windows or if the project path contains a white space
- [SCHEDULING-1303] - TestWorkingDirStaticCommand doesn't work on Windows or if the project path contains a white space
- [SCHEDULING-1304] - The 6 TestWorkflowComplexJobs tests don't work if the project path contains a white space
- [SCHEDULING-1313] - TestWorkflowIterationAwareness doesn't work on Windows or if the project path contains a white space
- [SCHEDULING-1316] - TestWorkflowRecoveryFinished has a bad URI API usage
- [SCHEDULING-1318] - TestWorkflowSubmission doesn't work on windows or if the project path contains a white space
- [SCHEDULING-1320] - TestDatabaseStringArray doesn't work if the project path contains a white space
- [SCHEDULING-1321] - TestJobFactory doesn't work if the project path contains a white space
- [SCHEDULING-1326] - TestGCMCustomizedInfrastructureTimeSlotPolicy doesn't work if the project path contains a white space
- [SCHEDULING-1340] - rm-start-node in worker distrib uses scheduler-server security policy instead of using the scheduler-client one
- [SCHEDULING-1343] - java.home problem in GCMNodeSourceApplicationTemplate.xml files
- [SCHEDULING-1346] - TestJobRecover has a bad URI API usage
- [SCHEDULING-1347] - TestLoggers has a bad URI API usage
- [SCHEDULING-1351] - TestWorkingDirDynamicCommand doesn't work on Windows or if the project path contains a white space
- [SCHEDULING-1352] - TestWorkflowRecoveryInterrupted has a bad URI API usage
- [SCHEDULING-1353] - SelectionUtilsTest has a bad URI API usage
- [SCHEDULING-1354] - TestDatabaseCRUD has a bad URI API usage
- [SCHEDULING-1362] - SelectionUtilsTest doesn't work on Windows
- [SCHEDULING-1365] - TestProcessTreeKiller doesn't work on Hudson Windows computer
- [SCHEDULING-1368] - Maximum number of tasks for a job is not checkec
- [SCHEDULING-1371] - Task result of a faulty task is not preserved in case of cancelJobOnError=true if the task is replicated
- [SCHEDULING-1372] - Replicated or looped tasks name are not registered in JobResultImpl.allResults
- [SCHEDULING-1374] - PluginDescriptor, return type of RM#getSupportedNodeSourceInfrastructures, must be annotated for JAXB to work
- [SCHEDULING-1375] - update compile/build.bat from PROACTIVE-1123
- [SCHEDULING-1380] - Fix PAsolve(task1,task2, ... taskn) syntax in Scilab toolbox
- [SCHEDULING-1383] - studio-RM: NPE on selection changed
- [SCHEDULING-1389] - Security policy does not allow to grant administrative privileges to users
- [SCHEDULING-1392] - PAResult_DB is not initialized properly (Scilab)
- [SCHEDULING-1393] - Use of predef can cause unexpected behaviour of Scilab
- [SCHEDULING-1394] - Sources files are not updated when using the "Sources" PATask attribute (Scilab)
- [SCHEDULING-1395] - remove scheduler-rcp/org.ow2.proactive.scheduling.common.lib/bin/org/ow2/proactive/scheduling/common/lib/Activator.class
- [SCHEDULING-1397] - add lines(0) command in generated scilab script (Scilab Executable) to prevent pagination
- [SCHEDULING-1399] - Typo in PAsolve when using custom Selection Script(Scilab)
- [SCHEDULING-1400] - MatLab should register listener with "myEventsOnly" by default.
- [SCHEDULING-1422] - successive logs of PATask should be appended
- [SCHEDULING-1423] - packages missing from export packages list in scheduler-rcp/org.ow2.proactive.scheduling.common.lib plugin
Improvement
- [SCHEDULING-1341] - Update release scripts
- [SCHEDULING-1342] - Improve the performance of RM data base by setting indexes more correct
- [SCHEDULING-1366] - add headless build for the scheduler and resource manager rcps
- [SCHEDULING-1378] - Improve the node deployment performance in SSH infrastructure
- [SCHEDULING-1379] - Handle Scheduler disconnection in Matlab/Scilab toolboxes
- [SCHEDULING-1381] - Improve PATask display in Matlab and Scilab extensions
- [SCHEDULING-1382] - Overload matrix concatenation for PATask in Matlab and Scilab toolboxes
- [SCHEDULING-1388] - Harmonize Matlab and Scilab's PATask syntax
- [SCHEDULING-1398] - add PAdisconnect and PAisConnected functions (Matlab & Scilab)
- [SCHEDULING-1419] - add the PAconnect(url, credpath) syntax (Matlab & Scilab)
- [SCHEDULING-1420] - Add val, logs, iserror and jobid attribute to PAResult objects (Scilab)
- [SCHEDULING-1421] - Improve memory handling in Scilab toolbox
- [SCHEDULING-1427] - return result index in PAwaitAny(Matlab)
- [SCHEDULING-1428] - add PAarrayfun function (Matlab)
- [SCHEDULING-1429] - add TestTransferEnv test (Matlab)
- [SCHEDULING-1430] - Improve PAsolve and PAwaitFor calls speed
- [SCHEDULING-1436] - Add jobRemove calls to Matlab&Scilab jobs once results have been retrieved by the user
- [SCHEDULING-1443] - Matlab and Scilab selection scripts should be static
- [SCHEDULING-1445] - Rearrange PAsolve and remove "jremove" for loaded classes due to a JIMS class loading change (Scilab)
New Feature
Story
- [SCHEDULING-1348] - TestWorkingDirDynamicCommand doesn't work on Windows or if the project path contains a white space
Task
Story Item
- [SCHEDULING-1349] - The test doesn't work if the project path contains a white space
- [SCHEDULING-1350] - Problem with Windows compatibility (batch file and execution command)
|
18 January 2012 : Scheduler 3.1.2
Bug
- [SCHEDULING-1249] - Scheduler fails to recover running jobs containing executed IF tasks
- [SCHEDULING-1250] - JobInfo update for a finished job should be commit in the same transaction as "last" taskInfo update in the same method (core.terminate(task))
- [SCHEDULING-1251] - bin\windows\pa-dataserver-gui.bat does not work
- [SCHEDULING-1264] - When defining a job classpath with / separator from a windows client, the jobclasspath jar is not correct
- [SCHEDULING-1276] - LocalInfrastructure doesn't work when spaces are in RM_HOME
- [SCHEDULING-1277] - SSHInfrastructure doesn't work if whitespaces are in RM_HOME
- [SCHEDULING-1437] - Scheduler core can be blocked while killing the job
- [SCHEDULING-1449] - Unnessary getState call in AOMatSciEnvironment
- [SCHEDULING-1453] - Performance of InternalTask serialization is poor
- [SCHEDULING-1458] - Resource manager does not properly release nodes
- [SCHEDULING-1459] - "watchers" group in security.java.policy-server should be able to get RM Monitoring
Improvement
- [SCHEDULING-1438] - Execution of dynamic selection scripts for each node must be limited
- [SCHEDULING-1439] - Add the possibility to list nodes for a particular node source to CLI of RM
- [SCHEDULING-1455] - Add the possibility to specify particular users/groups when node source is created
- [SCHEDULING-1472] - RM and Scheduler GUI clients: Increase ping timeout and add busy indicator
New Feature
- [SCHEDULING-1470] - add a Scheduling Policy to restrict access to specific NodeSources
|
|