[cosmic-users] CoSMIC 0.8.1 released
James H. Hill
hillj at cs.iupui.edu
Sun Aug 22 12:57:49 CDT 2010
Hi folks,
We are pleased to announce that CoSMIC 0.8.1 has been released. You can
download it from the following location:
http://www.dre.vanderbilt.edu/cosmic/html/download.php
Below is a list of the changes that went into this version. As always,
if you experience any problems, please let us know!
Thanks,
James
. Delegation of extended/mirror ports. An extended/mirror
port can be delegated to 0..1 delegation ports. Supporting
delegation to multiple delegation ports will results in
deployments that are not able to deploy via DAnCE.
. Support for generating valid descriptor information for
ami4ccm connectors. The ami4ccm support works similar to
the dds4ccm support. To generate the necessary pragma
statements in IDL for ami4ccm, you must enable the async
attribute on both the Object and RequiredRequestPort.
. First version of supporting process/thread specification for
plan locality managers. Right now, PICML treats locality manager
as regular components. This means you set the process/thread
affinity using properties attached to a locality manager
instance. The property names are as follows:
- LocalityManager.ProcessName (String)
- LocalityArguments (String)
As more is learned about locality managers, the design and
implementation of locality managers will be improved.
. First version of supporting specification of CPU or CPU core
affinity for each process/thread. The realization of this is
similar to the process/thread specification above. The name
of the property for specifying affinity is:
- edu.vanderbilt.dre.DAnCE.LocalityManager.CPUAffinity
. Complete support for managing ComplexType elements via the
Property Manager, and expose the Property Manager icon on
the toolbar. In particular, you can move elements in a array
up/down and delete them. In you must close the dialog and
re-open it after you add a new element to an array consisting
of complex types to view the members of the newly added complex
type.
. Generation of a nodemap.dat file in conjunction with the
auto-generated .cdd file. The name of the auto-generated file
will be the same as the deployment plan. To include an entry
in a .nodemap, attach a Property element of type String to the
target NodeReference element, and set its name to StringIOR.
The value of the Property element is a valid string IOR (i.e.,
corbaname:, corbaloc:, IOR:).
. When making a connection between a Facet/Receptacle and
Connector the PICML Model Intelligence either (1) auto-complete
the connection name or (2) display a dialog for selecting the
correct connection name.
. Support for deployment of ComponentAssembly elements under
the new modeling semantics for PICML.
. Implemented the the first version of the ConnectorInstance
decorator that displays the name and implementation type of a
connector instance.
More information about the cosmic-users
mailing list