Umbrella User's Manual

Last edited: May 2015

Please use the following citation for Umbrella in a scientific publication:

Overview⇗

Umbrella is a tool for specifying and materializing comprehensive execution environments, from the hardware all the way up to software and data. A user simply invokes Umbrella with the desired task, and Umbrella parses the specification, determines the minimum mechanism necessary to run the task, downloads missing dependencies, and executes the application through the available minimal mechanism, which may be direct execution, a system container (Docker, chroot, Parrot), a local virtual machine (i.e., VMware), or submission to a cloud environment (i.e., Amazon EC2) or grid environment (i.e., Condor). The following figure shows the overview of Umbrella.

The architecture of Umbrella is shown in the figure below.

Umbrella contains five parts: user inputs, Umbrella, underlying execution engines, remote archive and metadata database. User inputs include the specification, the task command, the input files, and the output directory. Umbrella connects the user's execution environment specification with the underlying execution engines, which includes local resources, clusters, cloud resources, and grid resources. The remote archive stores the OS images, software dependencies and data dependencies. The metadata database maintains the mapping relationship between the dependency name referred in the specification and the actual storage location within the remote archive.

Currently, Umbrella supports three execution engines: local, condor, ec2. Local execution engine can be further devided into three categories: parrot, docker, chroot. Parrot execution engine can be used without any special authority on the host machine; Docker execution engine requires Docker is installed on the host machine and the user is given the right authority to use Docker; chroot execution engine requires the user to be the root user.

To get started using Umbrella, please begin by installing CCTools on your system. When you are ready, proceed with the Have a Try section below. If you are interested in running your CMS applications through Umbrella, proceed with the Try CMS Applications with Umbrella.

If you want to construct umbrella specification for your own application, proceed with the Create Your Specification section below.

Note: The Docker execution engine of Umbrella can not work together with AFS. If you try to use the Docker execution engine of Umbrella, please do not install CCTools on your AFS directory.

Have a Try⇗

The part uses a Ray-Tracing application as an example to illustrate how to execute an application with Umbrella.

The specification for the application is povray.umbrella: { "comment": "A ray-tracing application which creates video frames.", "hardware": { "cores": "2", "disk": "3GB", "arch": "x86_64", "memory": "2GB" }, "kernel": { "version": ">=2.6.18", "name": "linux" }, "os": { "name": "Redhat", "format": "tgz", "checksum": "62aa9bc37afe3f738052da5545832c80", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/62aa9bc37afe3f738052da5545832c80/redhat-5.10-x86_64.tar.gz" ], "version": "5.10", "uncompressed_size": "1622159360", "id": "62aa9bc37afe3f738052da5545832c80", "size": "503195460" }, "software": { "povray-3.6.1-redhat5-x86_64": { "format": "tgz", "checksum": "9b7f2362e6b927c8ef08c3f92599e47c", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/9b7f2362e6b927c8ef08c3f92599e47c/povray-3.6.1-redhat5-x86_64.tar.gz" ], "action": "unpack", "mountpoint": "/software/povray-3.6.1-redhat5-x86_64", "mount_env": "POVRAY_PATH", "uncompressed_size": "3004423", "id": "9b7f2362e6b927c8ef08c3f92599e47c", "size": "1471457" } }, "data": { "4_cubes.pov": { "format": "plain", "checksum": "c65266cd2b672854b821ed93028a877a", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/c65266cd2b672854b821ed93028a877a/4_cubes.pov" ], "mountpoint": "/tmp/4_cubes.pov", "id": "c65266cd2b672854b821ed93028a877a", "size": "1757" }, "WRC_RubiksCube.inc": { "format": "plain", "checksum": "2f8afdd09fc3a6177c6f1977bb3bdae7", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/2f8afdd09fc3a6177c6f1977bb3bdae7/WRC_RubiksCube.inc" ], "mountpoint": "/tmp/WRC_RubiksCube.inc", "id": "2f8afdd09fc3a6177c6f1977bb3bdae7", "size": "28499" } }, "environ": { "PWD": "/tmp" }, "cmd": "povray +I/tmp/4_cubes.pov +O/tmp/frame000.png +K.0 -H50 -W50", "output": { "files": [ "/tmp/frame000.png" ], "dirs": [ ] } }

The umbrella command for Parrot execution engine:

umbrella \ --spec povray.umbrella \ --localdir /tmp/umbrella_test/ \ --output "/tmp/frame000.png=/tmp/umbrella_test/parrot_povray" \ --sandbox_mode parrot \ --log umbrella.log \ run

After this umbrella command is finished, you can find the output file, frame000.png, at /tmp/frame000.png. The output png file should look like:

You can check the help document of umbrella for the option settings by running the command: umbrella -h

You can try other execution engines following the instructions in the Different Execution Engines of Umbrella section.

To construct umbrella specification for your own application, proceed with the Create Your Specification section below.

To try other behaviors supported by Umbrella, process with the Behaviors of Umbrella section below.

Try CMS Applications with Umbrella⇗

The part uses a CMS application as an example to illustrate how to execute a CMS application with Umbrella.

The specification for the application is cms_complex.umbrella: { "comment": "a CMS application whose software dependencies are all from CVMFS, and whose data dependencies are not from CVMFS.", "hardware": { "cores": "2", "disk": "3GB", "arch": "x86_64", "memory": "2GB" }, "kernel": { "version": ">=2.6.32", "name": "linux" }, "os": { "name": "Redhat", "format": "tgz", "checksum": "669ab5ef94af84d273f8f92a86b7907a", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/669ab5ef94af84d273f8f92a86b7907a/redhat-6.5-x86_64.tar.gz" ], "version": "6.5", "uncompressed_size": "1743656960", "id": "669ab5ef94af84d273f8f92a86b7907a", "size": "633848940" }, "software": { "cmssw-5.2.5-slc5-amd64": { "mountpoint": "/cvmfs/cms.cern.ch", "mount_env": "CMS_DIR", "id": "cvmfs://cvmfs/cms.cern.ch", "source": [ "cvmfs://cvmfs/cms.cern.ch" ] } }, "data": { "final_events_2381.lhe": { "format": "plain", "checksum": "cb9878132aad42e7db30eabd214be8e2", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/cb9878132aad42e7db30eabd214be8e2/final_events_2381.lhe" ], "action": "none", "mountpoint": "/tmp/final_events_2381.lhe", "mount_env": "INPUT_FILE", "id": "cb9878132aad42e7db30eabd214be8e2", "size": "17840176" }, "cms_complex.sh": { "format": "plain", "checksum": "9f8587e9ef90ab4f5de8b3c9ab5cf0cb", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/9f8587e9ef90ab4f5de8b3c9ab5cf0cb/cms_complex.sh" ], "mountpoint": "/tmp/cms_complex.sh", "id": "9f8587e9ef90ab4f5de8b3c9ab5cf0cb", "size": "399" } }, "environ": { "PWD": "/tmp", "CMS_VERSION": "CMSSW_5_2_5", "SCRAM_ARCH": "slc5_amd64_gcc462" }, "cmd": "/bin/sh /tmp/cms_complex.sh", "output": { "files": [], "dirs": [ "/tmp/sim_job" ] } } The CMS analysis code is cms_complex.sh: #!/bin/sh rm -rf sim_job mkdir sim_job cd sim_job . /cvmfs/cms.cern.ch/cmsset_default.sh scramv1 project -f CMSSW ${CMS_VERSION} cd ${CMS_VERSION} eval `scram runtime -sh` cd .. cmsDriver.py Hadronizer_MgmMatchTuneZ2star_8TeV_madgraph_cff.py -s GEN \ --eventcontent=RAWSIM --datatier GEN -n 10 \ --filein=file:/tmp/final_events_2381.lhe \ --filetype=LHE --conditions=START52_V9::All The analysis code will create a directory called sim_job and put the CMSSW software dependencies under it.

The umbrella command for Parrot execution engine:

umbrella \ --sandbox_mode parrot \ --log umbrella.log \ --spec cms_complex.umbrella \ --localdir /tmp/umbrella_test/ \ --output "/tmp/sim_job=/tmp/umbrella_test/parrot_cms_complex_output" \ --cvmfs_http_proxy http://cache01.hep.wisc.edu:3128 \ run

After umbrella finishes executing the CMS application, you can see the analysis result: 21-May-2015 11:05:45 EDT Initiating request to open LHE file file:/tmp/final_events_2381.lhe 21-May-2015 11:05:45 EDT Successfully opened LHE file file:/tmp/final_events_2381.lhe Begin processing the 1st record. Run 1, Event 1, LumiSection 1 at 21-May-2015 11:05:45.202 EDT Begin processing the 2nd record. Run 1, Event 2, LumiSection 1 at 21-May-2015 11:05:45.204 EDT Begin processing the 3rd record. Run 1, Event 3, LumiSection 1 at 21-May-2015 11:05:45.210 EDT Begin processing the 4th record. Run 1, Event 4, LumiSection 1 at 21-May-2015 11:05:45.214 EDT Begin processing the 5th record. Run 1, Event 5, LumiSection 1 at 21-May-2015 11:05:45.216 EDT Begin processing the 6th record. Run 1, Event 6, LumiSection 1 at 21-May-2015 11:05:45.235 EDT Begin processing the 7th record. Run 1, Event 7, LumiSection 1 at 21-May-2015 11:05:45.244 EDT Begin processing the 8th record. Run 1, Event 8, LumiSection 1 at 21-May-2015 11:05:45.248 EDT Begin processing the 9th record. Run 1, Event 9, LumiSection 1 at 21-May-2015 11:05:45.249 EDT Begin processing the 10th record. Run 1, Event 10, LumiSection 1 at 21-May-2015 11:05:45.264 EDT ============================================= MessageLogger Summary type category sev module subroutine count total ---- -------------------- -- ---------------- ---------------- ----- ----- 1 fileAction -s AfterSource 2 2 type category Examples: run/evt run/evt run/evt ---- -------------------- ---------------- ---------------- ---------------- 1 fileAction BeforeEvents BeforeEvents Severity # Occurrences Total Occurrences -------- ------------- ----------------- System 2 2 The analysis directory sim_job will be put in the output directory, /tmp/umbrella_test/parrot_cms_complex_output.

You can check the help document of umbrella for the option settings by running the command: umbrella -h

For more information about the Umbrella support for CMS applications, please check the Umbrella Support for CMS Application section.

You can check the help document of umbrella for the option settings by running the command: umbrella -h

You can try other execution engines following the instructions in the Different Execution Engines of Umbrella section.

To construct umbrella specification for your own application, proceed with the Create Your Specification section below.

To try other behaviors supported by Umbrella, process with the Behaviors of Umbrella section below.

Create Your Specification⇗

The Umbrella specification for an application is also a JSON file. Here is the specification file for a Ray-Tracing application:

{ "comment": "A ray-tracing application which creates video frames.", "hardware": { "cores": "2", "disk": "3GB", "arch": "x86_64", "memory": "2GB" }, "kernel": { "version": ">=2.6.18", "name": "linux" }, "os": { "name": "Redhat", "format": "tgz", "checksum": "62aa9bc37afe3f738052da5545832c80", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/62aa9bc37afe3f738052da5545832c80/redhat-5.10-x86_64.tar.gz" ], "version": "5.10", "uncompressed_size": "1622159360", "id": "62aa9bc37afe3f738052da5545832c80", "size": "503195460" }, "software": { "povray-3.6.1-redhat5-x86_64": { "format": "tgz", "checksum": "9b7f2362e6b927c8ef08c3f92599e47c", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/9b7f2362e6b927c8ef08c3f92599e47c/povray-3.6.1-redhat5-x86_64.tar.gz" ], "action": "unpack", "mountpoint": "/software/povray-3.6.1-redhat5-x86_64", "mount_env": "POVRAY_PATH", "uncompressed_size": "3004423", "id": "9b7f2362e6b927c8ef08c3f92599e47c", "size": "1471457" } }, "data": { "4_cubes.pov": { "format": "plain", "checksum": "c65266cd2b672854b821ed93028a877a", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/c65266cd2b672854b821ed93028a877a/4_cubes.pov" ], "mountpoint": "/tmp/4_cubes.pov", "id": "c65266cd2b672854b821ed93028a877a", "size": "1757" }, "WRC_RubiksCube.inc": { "format": "plain", "checksum": "2f8afdd09fc3a6177c6f1977bb3bdae7", "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/2f8afdd09fc3a6177c6f1977bb3bdae7/WRC_RubiksCube.inc" ], "mountpoint": "/tmp/WRC_RubiksCube.inc", "id": "2f8afdd09fc3a6177c6f1977bb3bdae7", "size": "28499" } }, "environ": { "PATH": "/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin", "PWD": "/tmp" }, "cmd": "povray +I/tmp/4_cubes.pov +O/tmp/frame000.png +K.0 -H50 -W50", "output": { "files": [ "/tmp/frame000.png" ], "dirs": [ ] } }

An Umbrella specification includes multiple parts: hardware, kernel, os, software, data, environ, cmd and output. You can have other sections for comments, such as the comment section in the example.

hardware Section (required):

kernel Section (required):

os Section (required):

software Section (optional):

Each software dependency has a case-sensitive name. The name of a software dependency is in the format of 'A-B-C-D', where A is the software name, B is the software version, C is OS distro name (the OS name followed by the main version number, e.g., redhat5), D is hardware architecture. povray-3.6.1-redhat5-x86_64 is an example of this category.

data Section (optional):

Each data dependency has a name. There is no special limitation on the name of a data dependency. WRC_RubiksCube.inc is an example of this category.

environ Section (optional):

A list of key-value pairs. For example, "HOME": "/home/hmeng", which sets the HOME environment variable used by the sandbox to execute the applicition. Case sensitive.

cmd Section (optional):

The command to execute in the format of a string.

output Section (optional):

This section allows the creator of an Umbrella spec to specify the output files and directories. Correspondingly, there are two subsections: files (a list of strings representing the output files) and dirs (a list of strings representing the output dirs).

Common Attributes of OS, Software, Data Dependencies:

Each OS, software and data dependency can have the following attributes: source, checksum, size, format, uncompressed_size, and id.

Relationship of id and checksum and source. The checksum of each package can be used as the id of the package. However, it is not necessary for them to be identical to each other. You can implement your own mechanism once the id of each package is unique for one dependency. In case when the checksum of one dependency is not provided or feasible, the first item of the source section can be used as the value of the id attribute. For example, in the CMS example, cmssw-4.2.8-slc5-amd64 is delivered through cvmfs during runtime, and no checksum is provided, the url from the source section, cvmfs://cvmfs/cms.cern.ch is used as the id of this package.

To create your own umbrella metadata database, please check Create Your Own Metadata Database.

Behaviors of Umbrella⇗

Execute your Application through Umbrella⇗

For the following examples, cms_opendata_S.umbrella is a self-contained umbrella specification, cms_opendata.umbrella is an umbrella specification which does not include any metadata information.

The metadata information here includes: source, checksum, size, format, and uncompressed_size.

An Example for Umbrella run behavior:

umbrella \ --spec cms_opendata_S.umbrella \ --localdir /tmp/umbrella_test/ \ --output "/tmp/sim_job=/tmp/umbrella_test/parrot_cms_opendata_output" \ --sandbox_mode parrot \ --log umbrella.log \ --cvmfs_http_proxy http://cache01.hep.wisc.edu:3128 \ run

cms_opendata_S.umbrella is self-contained, so no metadata database is needed.

This example uses parrot execution engine, for other execution engines, please check the Different Execution Engines of Umbrella section.

The cvmfs_http_proxy option is used to specify a http proxy for cvmfs access. If your application does not need to access cvmfs, ignore this option.

You can check the help document of umbrella for the option settings by running the command: umbrella -h

Validate an Umbrella Spec File⇗

Validate a self-contained Umbrella specificiation:

umbrella \ --spec cms_opendata_S.umbrella \ validate

Validate an Umbrella specificiation with the help of a metadata db:

umbrella \ --spec cms_opendata.umbrella \ --meta http://ccl.cse.nd.edu/software/umbrella/database/packages.json \ validate

Split an Umbrella Spec File into Spec and Meta⇗

Split an umbrella spec file into spec and meta:

umbrella \ --spec cms_opendata_S.umbrella \ --log umbrella.log \ split f2 db2

After the command is done, f2 becomes an umbrella specification without any metadata information, db2 only includes the metadata information of the dependencies.

Expand an Umbrella Spec File into a Self-Contained Spec⇗

Expand an umbrella spec file into a self-contained spec:

umbrella \ --spec cms_opendata.umbrella \ --meta http://ccl.cse.nd.edu/software/umbrella/database/packages.json \ --sandbox_mode parrot \ --log umbrella.log \ expand f1

After this command, f1 becomes self-contained including both the specification and metadata info of its dependencies. The metadata info are abstract from the metadata db provided through the --meta option.

Filter the Meta Info for an Umbrella Spec File from a Huge Metadata DB⇗

Filter the meta information for an umbrella spec file from a huge metadata db:

umbrella \ --spec cms_opendata.umbrella \ --meta http://ccl.cse.nd.edu/software/umbrella/database/packages.json \ --sandbox_mode parrot \ --log umbrella.log \ filter db1

After this command, db1 only includes the metadata information of the dependencies involved in cms_opendata.umbrella.

Different Execution Engines of Umbrella⇗

At runtime, Umbrella evaluates the local execution environment to see if it is compatible with the specification. Umbrella evaluates the hardware resources available, the kernel and OS distribution, and the software and data dependencies. It then selects the mechanism necessary to deliver the desired environment. In the case where Umbrella can not construct the desired environment on the local machine, the user will be notified.

Local Cache and Mounting Mechanism. One cache directory will be set on each execution node involved in the execution engine to avoid download the same data from the remote archive repeatedly. Umbrella downloads and caches OS images, software dependencies, and data dependencies in the host machine, and then creates a sandbox to execute the application. To enable software reusability by multiple users, Umbrella constructs the sandbox for each application through mounting-based sandbox techniques.

The following figure shows the relationship between the remote archive, the local cache and the sandbox for each application. Sandbox 1 uses the root filesystem of the host machine as the root filesystem and mounts the needed software and data dependencies (A and G) into it. Sandbox 2 needs to construct a separate root filesystem which groups together the needed OS image (C), software dependency (A).

The following parts uses a Ray-Tracing application as an example to illustrate how to use different execution engines of Umbrella to execute the application. The --meta option and the --ec2 option are both not set in the following command, so the default metadata database and the default ec2 metadata database will be downloaded and used on the execution node during runtime.

The specification for the application is povray.umbrella. There are two input files 4_cubes.pov and WRC_RubiksCube.inc. The command for this application is:povray +I4_cubes.pov +Oframe000.png +K.0 -H50 -W50 Suppose you do your umbrella test under /tmp/umbrella. First download the specification and the two input files into /tmp/umbrella.

Execute your Application through Umbrella - Parrot⇗

The umbrella command for Parrot execution engine:

umbrella \ --spec povray.umbrella \ --localdir /tmp/umbrella_test/ \ --output "/tmp/frame000.png=/tmp/umbrella_test/parrot_povray" \ --sandbox_mode parrot \ --log umbrella.log \ run

Execute your Application through Umbrella - Docker⇗

The umbrella command for Docker execution engine:

umbrella \ --spec povray.umbrella \ --localdir /tmp/umbrella_test/ \ --output "/tmp/frame000.png=/tmp/umbrella_test/docker_povray" \ --sandbox_mode docker \ --log umbrella.log \ run

Don't do the Docker execution engine test under your AFS, it will fail due to the AFS ACL.

Execute your Application through Umbrella - local⇗

The umbrella command for local execution engine:

umbrella \ --spec povray.umbrella \ --localdir /tmp/umbrella_test/ \ --output "/tmp/frame000.png=/tmp/umbrella_test/local_povray" \ --sandbox_mode local \ --log umbrella.log \ run

The local execution engine of Umbrella first check whether Docker exists on the host machine, if yes, use docker execution engine; if not, use parrot execution engine. If your workstation has both AFS and Docker installed, you should avoid do the test under your AFS. The local execution engine just focuses on docker and parrot, ignoring chroot, because to render a task includes lots of mount and umount oprations, which are dangerous. If you really want to use chroot to finish your task, please set the --sandbox_mode option to be chroot.

Create Your Own Metadata Database⇗

When your have multiple relavant applications which share lots of their dependencies, instead of putting metadata information of each dependency into the Umbrella specification, you can ceate a metadata database which includes all the metadata information. Here is one example of an Umbrella metadata database, which is a JSON file.

Here is an example of metadata database: "povray-3.6.1-redhat5-x86_64": { "9b7f2362e6b927c8ef08c3f92599e47c": { "source":[ "http://ccl.cse.nd.edu/research/data/hep-case-study/9b7f2362e6b927c8ef08c3f92599e47c/povray-3.6.1-redhat5-x86_64.tar.gz" ], "format": "tgz", "checksum": "9b7f2362e6b927c8ef08c3f92599e47c", "uncompressed_size": "3004423", "size": "1471457" }, "c9da9e46b3ce0f7f9885ce60077c45c5": { "source":[ "http://ccl.cse.nd.edu/research/data/hep-case-study/c9da9e46b3ce0f7f9885ce60077c45c5/povray-3.6.1-redhat5-x86_64.tar.gz" ], "format": "tgz", "checksum": "c9da9e46b3ce0f7f9885ce60077c45c5", "uncompressed_size": "3004423", "size": "1471457" } }, "redhat-5.10-x86_64": { "62aa9bc37afe3f738052da5545832c80": { "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/62aa9bc37afe3f738052da5545832c80/redhat-5.10-x86_64.tar.gz" ], "format": "tgz", "checksum": "62aa9bc37afe3f738052da5545832c80", "uncompressed_size": "1622159360", "size": "503195460" } }, "cmssw-4.2.8-slc5-amd64": { "cvmfs://cvmfs/cms.cern.ch": { "source": [ "cvmfs://cvmfs/cms.cern.ch" ] } }, "final_events_2381.lhe": { "cb9878132aad42e7db30eabd214be8e2": { "source": [ "http://ccl.cse.nd.edu/research/data/hep-case-study/cb9878132aad42e7db30eabd214be8e2/final_events_2381.lhe" ], "format": "plain", "checksum": "cb9878132aad42e7db30eabd214be8e2", "size": "17840176" } }

Naming Rules of Dependencies:

The name of a software dependency is in the format of 'A-B-C-D', where A is the software name, B is the software version, C is OS distro name, D is hardware architecture. povray-3.6.1-redhat5-x86_64 is an example of this category.

The name of an OS image dependency is in the format of 'A-B-C', where A is the OS name, B is the OS version, C is hardware architecture. redhat-5.10-x86_64 is an example of this category.

There is no special limitation on the name of a data dependency. final_events_2381.lhe is an example of this category.

Multiple Packages for One Dependency. According to the building and compilation settings, there may be multiple packages for one dependency. In this case, all the packages for one dependency will be organized together and the `id` attribute of each package will be used as item key to differentiate different packages. For example, for the software dependency povray-3.6.1-redhat5-x86_64, there are two different packages: one with the id of 9b7f2362e6b927c8ef08c3f92599e47c and one with the id of c9da9e46b3ce0f7f9885ce60077c45c5.

Each package may include the following attributes: source, checksum, size, format, and uncompressed_size.

Relationship of id and checksum and source. The checksum of each package in the archive can be used as the id of the package in our implementation of metadata database. However, it is not necessary for them to be identical to each other. You can implement your metadata database in a different semantics once the id of each package is unique for one dependency. In case when the checksum of one dependency is not provided or feasible, the first item of the source section will be used. For example, in the above example, cmssw-4.2.8-slc5-amd64 is delivered through cvmfs during runtime, and no checksum is provided, the url from the source section, cvmfs://cvmfs/cms.cern.ch is used as the id of this package.

Organization of the Local Cache. Within the local cache, the id of each package dependency will be used to create a directory under the <localdir>/cache, then the package will be put into <localdir>/cache/<idgt;/<name>. Therefore, <localdir>/cache/9b7f2362e6b927c8ef08c3f92599e47c/povray-3.6.1-redhat5-x86_64.tar.gz will be the local location of the first povray package shown in the above example. The uncompressed directory of the tarball will be <localdir>/cache/9b7f2362e6b927c8ef08c3f92599e47c/povray-3.6.1-redhat5-x86_64.

Organization of the Remote Archive. Within the remote archive, to differentiate multiple packages for the same dependency and the different dependencies, a directory with the name of the checksum of each package will be created and functions as the direct parent directory of the package. Therefore, in the remote archive, there is a directory named 9b7f2362e6b927c8ef08c3f92599e47c, under which exists povray-3.6.1-redhat5-x86_64.tar.gz However, the organization of the remote archive can be in other format, once you have a way to differentiate the packages.

If you want to customize your own metadata database, please follow the requirements above and then tell umbrella through --meta option to use your own metadata database. For Example:

umbrella \ --spec povray.umbrella \ --meta http://ccl.cse.nd.edu/software/umbrella/database/packages.json \ --localdir /tmp/umbrella_test/ \ --output "/tmp/frame000.png=/tmp/umbrella_test/local_povray" \ --sandbox_mode local \ --log umbrella.log \ run

There are two ways to create an Umbrella metadata database: (1) use umbrella --spec spec_filename split new_spec_filename db_filename to abstract all the metadata information from a self-contained umbrella specification. (2) Follow the format of the metadata database and create your own metadata database manually.

EC2 Metadata Database⇗

When the ec2 execution engine is used, Umbrella tries to map the specification into an AMI and an EC2 instance type with the help of the EC2 metadata database, which is a JSON file and can be specified by the --ec2 option of Umbrella. If the --ec2 is not set, the default EC2 metadata database will be downloaded and used on the execution node during runtime.

Here is an example of an EC2 metadata database:

{ "redhat-6.5-x86_64": { "ami-2cf8901c": { "ami": "ami-2cf8901c", "root_device_type": "ebs", "virtualization_type": "papavirtual", "user": "ec2-user" } }, "redhat-5.10-x86_64": { "ami-d76a29e7": { "ami": "ami-d76a29e7", "root_device_type": "ebs", "virtualization_type": "hvm", "user": "root" } }, "instances": { "m1.large": { "cores": "4", "memory": "2GB", "disk": "20GB" } } ... }

There are two types of items in an EC2 metadata: OS images and instance types.

The name of an OS image shares the same specification with the name used in the general metadata database. There may exist multiple versions of images for an OS like redhat-5.10-x86_64. An identifier of each version is needed to differentiate these versions and function as the name of each OS image version. Currently, the AMI is used as the identifier. Correspondingly, the id attribute of the os section of an specification should also be an AMI.

An OS image includes four attributes:

The name of each instance type is the same as the one provided by the Amazon EC2(e.g., m1.large). Each instance type has three attributes:

Umbrella Support for CMS Application⇗

As for CMS applications which need software from CVMFS, Umbrella first checks whether the execution node has CVMFS installed or not. If CVMFS is installed and its CMS repository is mounted as /cvmfs/cms.cern.ch, the application can run directly without the help from sandboxing techniques. If CVMFS is not installed or the mountpoint /cvmfs/cms.cern.ch is not found, Parrot will be used to help access software from CVMFS.

Like other software dependencies, the dependency of CMSSW will be specified inside the software section of the specification, however, you only need to specify the mountpoint attribute. The id and action attributes for the CMSSW dependency will be ignored even if they are specified. In fact, the support for CMS applications are hardcoded inside the source code of Umbrella, not inside the metadata database.

If you want to run this CMS application through Umbrella, please check the Try CMS Applications with Umbrella.