Difference between revisions of "FAQ: lcg-ce to cream-ce"
Line 3: | Line 3: | ||
'''Q1: What is cream-ce? ''' | '''Q1: What is cream-ce? ''' | ||
The [https://twiki.cern.ch/twiki/bin/view/EMI/EMIServicesDocs#gLite_Job_Management CREAM] (Computing Resource Execution And Management) Service is a simple, lightweight service that implements all the operations at the Computing Element (CE) level; its well-defined Web Service-based interface and its implementation as an extension of the Java-Axis servlet (running inside the Apache Tomcat container) provide interoperability with clients written in any programming language and running on any computer platform. | The [https://twiki.cern.ch/twiki/bin/view/EMI/EMIServicesDocs#gLite_Job_Management CREAM] (Computing Resource Execution And Management) Service is a simple, lightweight service that implements all the operations at the Computing Element (CE) level; its well-defined Web Service-based interface and its implementation as an extension of the Java-Axis servlet (running inside the Apache Tomcat container) provide interoperability with clients written in any programming language and running on any computer platform. | ||
Line 10: | Line 11: | ||
'''Q2: Wha batch systems are supported by CREAM?''' | '''Q2: Wha batch systems are supported by CREAM?''' | ||
LSF, PBS, SGE (check with Massimo) | LSF, PBS, SGE (check with Massimo) | ||
Revision as of 12:46, 14 February 2011
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
The FAQ provides the questions and answers those may arise for the user communities during the transition from lcg-ce to cream-ce.
Q1: What is cream-ce?
The CREAM (Computing Resource Execution And Management) Service is a simple, lightweight service that implements all the operations at the Computing Element (CE) level; its well-defined Web Service-based interface and its implementation as an extension of the Java-Axis servlet (running inside the Apache Tomcat container) provide interoperability with clients written in any programming language and running on any computer platform.
The CREAM interface is well-defined using the Web Service Description Language (WSDL); anyone can generate his/her CREAM client by simply filling in the stub code generated by WSDL parser (gSOAP for C/C++, Axis for Java, Perl module for perl).
The CREAM architecture is illustrated here: Diagram
Q2: Wha batch systems are supported by CREAM?
LSF, PBS, SGE (check with Massimo)
Security
User's guide
- Additional guides: Other Guides
Known Issues
Known Issues of current CREAM software in production release.
Known Issues of WMS ICE component
Cream JDL
Cream Jobs
CREAM-CE has ability to accept either direct Jobs from gLite-UI, SOAP clients or any other developed UIs based on web-services or Jobs sent through WMS.
Job States
Job Control Mechanisms
- Suspend
- Resume
- Delete
Direct Jobs Submission
Jobs Control
WMS Jobs Submission
Workload Management System (WMS), via the ICE (Interface to CREAM Environment) service can submit Jobs to the CREAM-CE using gLite-UI or other WMS interfaces.
Jobs Control
SandBox Management
Storage Element (SE)
- gridftp
CREAM-CE Information
Benchmarks
Jobs Submission
Direct Jobs Submission
- Jobs States Notifications
WMS Jobs Submission
- Jobs States Notifications
CREAM-CE Performance
CREAM Client Errors
Q: Where can I find more documentation about CREAM?
CREAM mailing lists
- cream-support AT lists.infn.it