CCAR: replace the old way to take the python global interpreter lock
by calls to PyGILState_Ensure/PyGILState_Release in C++ container
so that GIL management be coherent from GUI embedded interpreter to embedded
python container.
CCAR: add a message in case of error when loading a component.
The dlerror output for dlopen plus the traceback for the import of the python module
The import_component python function now returns a string instead of a boolean.
If the string is empty, the import is OK.
The C++ code in container MPIContainer and ParallelContainer has been adapted.
adam [Tue, 8 Sep 2009 08:41:04 +0000 (08:41 +0000)]
Update according new version of
make_common_starter.am in which is defined
AM_CXXFLAGS = -I$(top_builddir)/salome_adm/unix -include SALOMEconfig.h
AM_CPPFLAGS = -I$(top_builddir)/salome_adm/unix -include SALOMEconfig.h
caremoli [Thu, 27 Aug 2009 16:12:13 +0000 (16:12 +0000)]
CCAR: I have added a way to define the directory for the container log files
If the environment variable SALOME_TMP_DIR is defined and is a directory the
log files are created in this directory and not in /tmp.
This modification has only be done for Linux and only for the container logs.
Other temporary files go in /tmp as before.
srn [Tue, 30 Jun 2009 12:46:32 +0000 (12:46 +0000)]
Now Study is saved firstly in the temporary directory and after copied into the chosen by the user destination directory. So in case of crash the Study files is not damaged
caremoli [Fri, 22 May 2009 08:53:41 +0000 (08:53 +0000)]
CCAR: add automatic management of GenericObj in study.
If a GenericObj id publish in study, its reference count must be incremented (call to Register()).
When it is unpublished, its reference count must be decremented (call to Destroy()).
This was not done when calling SetValue on a AttributeIOR so if someone manages
GenericObj in the right way, the references in study could be lost.
caremoli [Mon, 18 May 2009 17:11:32 +0000 (17:11 +0000)]
CCAR: add a python module for automatic management of genericobj
reference counting.
The module is not active by default.
It must be imported to activate the automatic reference counting
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.
