Difference: CloudSchedulerVMParameters (1 vs. 4)

Revision 42010-04-13 - patricka

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

VM Parameters for Job Submission

Line: 18 to 18
 
VMNetwork The network association that the VM will have when started. Depends on cluster. Usually 'public' or 'private'
VMCPUArch The CPU architecture that the job requires. Currently, either x86 or x86_64
VMLoc The location (http url) of the image the job will run on
Added:
>
>
VMAMI The AMI of the image on which the job will run
 
VMMem The amount of RAM memory that the VM executing the job requires
VMCPUCores The number of CPU cores that the VM executing the job requires
VMStorage The amount of scratch storage space the job requires

Revision 32009-11-25 - dpb

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

VM Parameters for Job Submission

Line: 13 to 13
 VM Parameters:

Parameter Name Description
Changed:
<
<
VMNAME The name of the VM (a.k.a, the file name or "type" of the VM)*
VMCPUs The number of CPU cores that the VM executing the job requires
VMMemory The amount of RAM memory that the VM executing the job requires
VMStorage The amount of scratch storage space the job requires
VMArch The CPU architecture that the job requires. Currently, either x86 or x86_64
VMIPType The type of IP that the VM running the job requires ('public' for external network access, or 'private')
>
>
Requirements = VMType \=?\= The "type" of VM that the job must run on. Specified in the condor_config file of the specified image
VMName The name of the VM (a.k.a, the file name or "type" of the VM)*
VMNetwork The network association that the VM will have when started. Depends on cluster. Usually 'public' or 'private'
VMCPUArch The CPU architecture that the job requires. Currently, either x86 or x86_64
VMLoc The location (http url) of the image the job will run on
VMMem The amount of RAM memory that the VM executing the job requires
VMCPUCores The number of CPU cores that the VM executing the job requires
VMStorage The amount of scratch storage space the job requires
 

*: This is the filename of the VM that the cloud scheduler will search for in image repositories. This may also support file locations (such as an image URL).

Added:
>
>

A sample job file:

####################                    
# Condor job submission file for Cloud Scheduler Testing
####################                                                    

# Astronomy-job specifications
Universe   = vanilla
Executable = red.sh
Arguments  = W3-3+3 W3%2D3%2B3
Log        = red10.log
Output     = red10.out
Error      = red10.error
should_transfer_files = YES
when_to_transfer_output = ON_EXIT

# Run-environment requirements
Requirements = VMType =?= "red"
+VMName        = "Red10"
+VMNetwork     = "private"
+VMCPUArch     = "x86"
+VMLoc         = "http://vmrepo.phys.uvic.ca/vms/red.img.gz"
+VMMem         = "512"
+VMCPUCores    = "1"
+VMStorage     = "20"

Queue
  -- DuncanPenfoldBrown - 2009-06-12 \ No newline at end of file

Revision 22009-06-15 - dpb

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

VM Parameters for Job Submission

Changed:
<
<
This document will describe the parameters that can be set in job description files in order to define and characterize the VMs that a job will run on. Currently, we are working with the condor job scheduler (condor job pool). As such, the job description files referred to are condor job submission files. However, these parameters for specifying VM attributes will be used independently of specific job schedulers.
>
>
This document will describe the parameters that can be set in job description files in order to define and characterize the VMs that a job will run on. Currently, we are working with the condor job scheduler (condor job pool). As such, the job description files referred to are condor job submission files. However, these parameters for specifying VM attributes will be used independent of specific job schedulers.
 
Changed:
<
<
These parameters are derived from the information submitted to Nimbus in order to create virtual workspaces (cloud resources). The VMCPUs and VMStorage) parameters listed below, however, are independent. This information will be gathered by a cloud registry service (the cloud MDS).
>
>
These parameters are derived from the information submitted to Nimbus in order to create virtual workspaces (cloud resources). The VMCPUs and VMStorage parameters listed below, however, are independent. This information will be gathered by a cloud registry service (the cloud MDS).
 
Changed:
<
<
In condor job submission files, there is a requirements field. It is within this field that all VM attributes will be specified. The following list describes all potential VM parameters that will be supported by the cloud scheduler.
>
>
Condor job submission files contain a requirements field. It is within this field that all VM attributes will be specified. The following list describes all potential VM parameters that will be supported by the cloud scheduler.
  An example job submission file with complete VM parameters will be added shortly (6/12/2009).

Revision 12009-06-12 - dpb

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

VM Parameters for Job Submission

This document will describe the parameters that can be set in job description files in order to define and characterize the VMs that a job will run on. Currently, we are working with the condor job scheduler (condor job pool). As such, the job description files referred to are condor job submission files. However, these parameters for specifying VM attributes will be used independently of specific job schedulers.

These parameters are derived from the information submitted to Nimbus in order to create virtual workspaces (cloud resources). The VMCPUs and VMStorage) parameters listed below, however, are independent. This information will be gathered by a cloud registry service (the cloud MDS).

In condor job submission files, there is a requirements field. It is within this field that all VM attributes will be specified. The following list describes all potential VM parameters that will be supported by the cloud scheduler.

An example job submission file with complete VM parameters will be added shortly (6/12/2009).

VM Parameters:

Parameter Name Description
VMNAME The name of the VM (a.k.a, the file name or "type" of the VM)*
VMCPUs The number of CPU cores that the VM executing the job requires
VMMemory The amount of RAM memory that the VM executing the job requires
VMStorage The amount of scratch storage space the job requires
VMArch The CPU architecture that the job requires. Currently, either x86 or x86_64
VMIPType The type of IP that the VM running the job requires ('public' for external network access, or 'private')


*: This is the filename of the VM that the cloud scheduler will search for in image repositories. This may also support file locations (such as an image URL).

-- DuncanPenfoldBrown - 2009-06-12

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 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