ouv [Wed, 6 May 2009 13:08:35 +0000 (13:08 +0000)]
Improvement of "setenv.py" script - setting of custom enviroment by those modules, which have it, is performed by their own "<module_name>_setenv.py" scripts situated in their "bin" folders.
CCAR: several changes in Container Manager and Resources Manager
1- remove unused members in MachineParameters, keep only members for requests
the members removed are : alias, protocol, username, applipath, mpiImpl, batch
2- remove the enum policy which is replaced by a new member in MachineParameters (policy)
3- add a new member computerList in MachineParameters structure to specify a list of machines
in a request to Container Manager
3- remove no more used parameters (policy, possibleComputers, componentList
in FindOrStartContainer, FindOrStarParallelContainer, StartContainer,
GiveContainer and GetFittingResources. These operations now take only
one argument : a MachineParameters structure.
4- adapt LifeCycle to these changes
CCAR:
1- add mode member to MachineParameters. This string member can be "start" or "get" or "getorstart"
if mode=="start" a new container is launched on each request.
if mode=="get" an old container with the requested parameters is used if it exists.
if mode=="getorstart" an old container is used or a new one if the old one does not exist.
2- add policy member to MachineParameters. This string member replaces the enum policy argument
of GiveContainer and StartContainer. This argument is left for compatibility but will be removed soon.
3- replace LoadRateManager methods by three objects. These objects are referenced in a map (_resourceManagerMap)
that can be extended without changing IDL interface.
4- add a Find method to ResourceManager IDL for testing purpose.
CCAR:
1- add a new type MachineDefinition in ContainerManager idl
to separate machine definition parameters and machine parameters for requests
to container manager (MachineParameters)
2- in Resource manager replace module by component. Selection of a resource is now
done with a component name and no more with a module name.
Now in CatalogResource.xml, we can specify for a resource that it supports
a list of components or modules.
Syntax for a component is:
<component name="xxxx" moduleName="yyy" />
Syntax for a module is:
<modules moduleName="yyyy"/>
When a module is added, a component with the same name is also added.
CCAR:
1- execute python script files (runSalome -u) in globals and not in globals,locals
as it was done before
2- don't use obsolete omniORB initref form in runRemote.sh
3- put _narrow (SALOMEDS_Study_i.cxx) into a try catch : _narrow can throw CORBA::Exception
caremoli [Fri, 13 Feb 2009 10:43:51 +0000 (10:43 +0000)]
CCAR: documentation update
Now user documentation is built in gui/KERNEL directory
and developer documentation is built in tui/KERNEL directory
They are installed in directories with same names (so GUI module must be changed to access it)
Old documentation files have been removed and new files have been added in gui and tui
directories except .dox files in salome directory.
Example files have been moved to salome/examples directory
User documentation is built with EXTRACT_ALL=NO doxygen option and no template parsing
to produce a smaller doc. Many source files have been modified to add descriptions (brief,
class, module, file) because of EXTRACT_ALL option.
admin [Tue, 3 Feb 2009 10:06:18 +0000 (10:06 +0000)]
This commit was generated by cvs2git to create branch 'V5_1_main'.
Sprout from master 2009-02-03 10:06:10 UTC prascle <prascle> 'merge from branch BR_V5_DEV'
Cherrypick from IMPORT 2003-05-16 10:27:43 UTC admin <salome-admin@opencascade.com> 'Initialisation de la base KERNEL avec la version operationnelle de KERNEL_SRC issue de SalomePro1.1a.':
resources/CatalogDataType.xml
resources/CatalogModulePersonnel.xml_skel
resources/channel.cfg
