Access to Resources: Difference between revisions

From Lsdf
Jump to navigationJump to search
No edit summary
mNo edit summary
 
(36 intermediate revisions by 5 users not shown)
Line 1: Line 1:
In order to get access to the LSDF first read the [[LSDF_Usage|Usage Policy]].
<nowiki>============= Request for Cloud resources =============</nowiki>
- Name, email, institute


Contact Jos van Wezel <jos.vanwezel@kit.edu> at SCC. In the end we need the following information:
- Other persons involved in the intended activities who do already have access to OpenNebula resources? (ie, do you belong to a group who requests access)


* Name, email, institute
- Short description of the intended activities to be performed on the cloud infrastructure
* Other persons (name, email) involved in the intended activities who do already have access to DIS Storage or Hadoop? (ie, do you belong to a group who requests access)
* Short description of the intended activities
* Tentative timeline (start, end, any intermediate milestones?)


For Hadoop usage please state:
- Tentative timeline (start, end, any intermediate milestones?)


* Expected nr. of jobs
- Resources:
* Expected running time of average job
* Requested resources:
Nr. of VM's, nr. of CPUs per VM, disk space per VM, RAM per VM
* Nr. of map-tasks (and CPUs) per job foreseen
* Amount of RAM per job needed

* Expected disk space usage in HDFS
<nowiki>=====================================================</nowiki>

Latest revision as of 10:28, 29 July 2016

In order to get access to the LSDF first read the Usage Policy.

Contact Jos van Wezel <jos.vanwezel@kit.edu> at SCC. In the end we need the following information:

  • Name, email, institute
  • Other persons (name, email) involved in the intended activities who do already have access to DIS Storage or Hadoop? (ie, do you belong to a group who requests access)
  • Short description of the intended activities
  • Tentative timeline (start, end, any intermediate milestones?)

For Hadoop usage please state:

  • Expected nr. of jobs
  • Expected running time of average job
  • Nr. of map-tasks (and CPUs) per job foreseen
  • Amount of RAM per job needed
  • Expected disk space usage in HDFS