Difference: Cream113ReleaseNotes (1 vs. 3)

Revision 32011-06-24 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="ReleaseNotes"

Release Notes for CREAM 1.13

Line: 19 to 19
 
Changed:
<
<
>
>
  • Several bug fixes.

Relevant Savannah task: http://savannah.cern.ch/task/?18534

  -- MassimoSgaravatto - 2011-05-05

Revision 22011-05-10 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="ReleaseNotes"

Release Notes for CREAM 1.13

Line: 7 to 7
 
    • the grid Java Authorization Framework (gJAF)
 
In the former case a ARGUS box (usually at site level) where to define policies for the CREAM CE box is needed.
Changed:
<
<
>
>
  • Support for description and allocation of resources in a multi-core environment. Support for the new JDL attributes WholeNodes (whether whole nodes should be used), HostNumber (how many nodes should be used) and SMPGranularity (How cores should be distributed over the cluster). See http://wiki.italiangrid.org/twiki/bin/view/CREAM/JdlGuide
 
  • Support for glite-cluster. glite-CLUSTER is a node type that can publish information about clusters and subclusters in a site, referenced by any number of compute elements. glite-CLUSTER can be deployed in the same host of the CREAM-CE or in a different one.
 
The following deployment models are possible:
Line: 17 to 17
 
  • Initial experimental publishing of computing service information in Glue 2.0 format
Changed:
<
<
>
>
 

Revision 12011-05-05 - MassimoSgaravatto

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="ReleaseNotes"

Release Notes for CREAM 1.13

  • CREAM can be optionally configured to use ARGUS as authorization system. The CREAM CE can be configured to use as authorization system:
    • the ARGUS authorization framework OR
    • the grid Java Authorization Framework (gJAF)
 
In the former case a ARGUS box (usually at site level) where to define policies for the CREAM CE box is needed.

  • Support for glite-cluster. glite-CLUSTER is a node type that can publish information about clusters and subclusters in a site, referenced by any number of compute elements. glite-CLUSTER can be deployed in the same host of the CREAM-CE or in a different one.
 
The following deployment models are possible:
  • CREAM-CE can be configured without worrying about the glite-CLUSTER node. This can be useful for small sites who don't want to worry about cluster/subcluster configurations because they have a very simple setup. In this case CREAM-CE will publish a single cluster/subcluster. This is called no cluster mode.
  • CREAM-CE can work on cluster mode using the glite-CLUSTER node type. The CREAM-CE can be in the same host or in a different host from the glite-CLUSTER node.
 
More information about glite-CLUSTER can be found at https://twiki.cern.ch/twiki/bin/view/LCG/CLUSTER

  • Initial experimental publishing of computing service information in Glue 2.0 format

-- MassimoSgaravatto - 2011-05-05

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback