Most of the services described on this page are provided for demonstration purposes and can be browsed directly from your web browser. In order to avoid warnings, you should install the default CA certificate. You may also want to install the default client test certificate.
Public GridFactory servers
- www.gridfactory.org - is a server hosted by Cabo and has a few GridWorkers attached. These are running inside Linux virtual machines and thus do not support on-demand virtualization, i.e. they can run only jobs designed for the particular Linux distribution they are running on (currently Ubuntu-10.10 and CernVM-2.3). It’s a demo service offered to give new users without their own server a place to try out some test jobs. www.gridfactory.org accepts jobs from anyone using the default test certificate shipped with the clients - with the caveats that we reserve ourselves the liberty of killing any jobs and that we will block the IP address of anyone abusing the system.
- gridfactory.nbi.dk - is a server hosted by the Niels Bohr Institute at the University of Copenhagen; it has a small, mixed and varying number of attached GridWorkers and sub-servers. Most GridWorkers run on physical machines and support on-demand virtualization. The purpose of the server is to execute CERN/ATLAS jobs for Danish physicists. gridfactory.nbi.dk pulls jobs from www.gridfactory.org if and when www.gridfactory.org has more queued jobs than it can handle itself and gridfactory.nbi.dk has free capacity.
- pcnbi1.cern.ch - is a server hosted by the Niels Bohr Institute at CERN. It has16 job slots, distributed over 5 GridWorkers each on a 4-core PC running Scientific Linux. The purpose of the server is to execute jobs for Danish physicists needing direct access to data at CERN. pcnbi1.cern.ch pulls jobs from gridfactory.nbi.dk if and when gridfactory.nbi.dk has more queued jobs than it can handle itself and pcnbi1.cern.ch has free capacity.
- gridfactory.dyndns.org - is a server hosted on Amazon’s EC2 and it is NOT running permanently. It’s a demo service offered to allow new users without their own server to try out some test jobs. Jobs are accepted from anyone using the default test certificate shipped with the clients. There are no GridWorkers permanently assigned, but anyone can start some by simply booting up instances of the pre-configured GridWorker image available on EC2. These instances are virtual machines running Ubuntu 10.10 (Maverick) implying that on-demand OS provisioning is not supported, i.e. jobs must be designed for Ubuntu 10.10.
Public virtual organizations
Virtual organizations are defined simply by text files on web servers, containing a list of distinguished names of X.509 certificates.
The virtual organization defined by
includes the distinguished name of the default certificate shipped with the GridFactory software. Members of this virtual organization (i.e. anyone without a personal certificate) are allowed to run jobs on the small attached test cluster.
The virtual organization defined by
contains the distinguished names of the users and resources in the Danish academic grid initiative grid.dk. If you would like to contribute computing power to this organization, you should start your GridWorker(s) like:
The virtual organization defined by
contains distinguished names of Danish physicists working on analyzing the data from the ATLAS detector at the LHC at CERN. If you would like to contribute computing power to this work, you should start your GridWorker(s) like:
If you would like to join one of these virtual organizations and be allowed to run more than just short test jobs on our resources, drop us a line (feedback AT gridfactory.org) explaining why.
The virtual organization defined by
https://www.gridfactory.org/vos/public.txt
includes the distinguished name of the default certificate shipped with the GridFactory software. Members of this virtual organization (i.e. anyone without a personal certificate) are allowed to run jobs on the small attached test cluster.
The virtual organization defined by
http://gridfactory.nbi.dk/vos/dcsc.dk.sh
contains the distinguished names of the users and resources in the Danish academic grid initiative grid.dk. If you would like to contribute computing power to this organization, you should start your GridWorker(s) like:
gridworker -v http://gridfactory.nbi.dk/vos/dcsc.dk.shIf you would like to join one of these virtual organizations and be allowed to run more than just short test jobs on our resources, drop us a line (feedback AT gridfactory.org) explaining why.
The virtual organization defined by
http://gridfactory.nbi.dk/vos/atlas.dk.sh
contains distinguished names of Danish physicists working on analyzing the data from the ATLAS detector at the LHC at CERN. If you would like to contribute computing power to this work, you should start your GridWorker(s) like:
gridworker -v http://gridfactory.nbi.dk/vos/atlas.dk.sh- but be aware that the computing jobs you will be running are very demanding: typically they consume 2 GB of memory, run for hours and produce output files of about 1 GB in size. Moreover, before the first job starts your GridWorker will download a virtual machine plus a software package of about 10 GB in size.
If you would like to join one of these virtual organizations and be allowed to run more than just short test jobs on our resources, drop us a line (feedback AT gridfactory.org) explaining why.
Public software catalogs
For testing purposes, the following central catalog is provided:
This is the default catalog location of freshly installed GridFactory servers. It contains a very small selection of software and virtual machine images. If you’re running your own server, you will most likely want to set up your own catalog too and add its location your server’s list of catalog locations. See the documentation for details. We welcome contributed extensions of this software catalog. If you would like to contribute a software package or virtual machine image, drop us a line.
The Niels Bohr Institute hosts a software catalog at:
This catalog contains virtual machine images and software intended for CERN/ATLAS data processing. It also contains software and images for testing various applications.
Cabo hosts a smaller catalog with sample ATLAS releases depending on CernVM:
Another catalog is hosted on Amazon’s S3 storage service:
This catalogue is meant to be used with GridPilot when running jobs on the EC back-end.
http://www.gridfactory.org/rtes.xml
This is the default catalog location of freshly installed GridFactory servers. It contains a very small selection of software and virtual machine images. If you’re running your own server, you will most likely want to set up your own catalog too and add its location your server’s list of catalog locations. See the documentation for details. We welcome contributed extensions of this software catalog. If you would like to contribute a software package or virtual machine image, drop us a line.
The Niels Bohr Institute hosts a software catalog at:
https://gridfactory.nbi.dk/rtes/rtes.xml
This catalog contains virtual machine images and software intended for CERN/ATLAS data processing. It also contains software and images for testing various applications.
Cabo hosts a smaller catalog with sample ATLAS releases depending on CernVM:
https://www.gridfactory.org/rtes/atlas.xml
Another catalog is hosted on Amazon’s S3 storage service:
https://s3.amazonaws.com/gridpilot/ec2_rtes.xml
This catalogue is meant to be used with GridPilot when running jobs on the EC back-end.
Public application repositories
The central GridPilot application repository provides a number of example applications. These can be browsed from GridPilot or by pointing your web broser to https://www.gridpilot.dk/apps/.
Contributed example applications in the central repository are very welcome. To be allowed to export applications to the central repository, send and email to gridfactory@gridfactory.org.
Notice that you can easily run your own repository: simply export your apps to another directory URL than the default one.
Contributed example applications in the central repository are very welcome. To be allowed to export applications to the central repository, send and email to gridfactory@gridfactory.org.
Notice that you can easily run your own repository: simply export your apps to another directory URL than the default one.
Hosted GridFactory server
If you don’t want to go through the effort of setting up and operating GridFactory services of your own, you may be interested in a hosted solution. Our partner Cabo offers this in three ways:
With solutions 1 and 2 you can dynamically change the number of attached worker nodes running on Irigo or EC2 respectively. You can even attach worker nodes on your own premises, but notice that this is only recommended if your jobs have small input and output files. Solution 3 allows you the same advantages as a hosted solution, but with your files never leaving your premises and allowing you to process large amounts of data on your own worker nodes without worrying about network costs.
- server hosted on Cabo’s Irigo Cloud
- server hosted on Amazon’s Elastic Compute Cloud (EC2)
- server operated by Cabo on your premises
With solutions 1 and 2 you can dynamically change the number of attached worker nodes running on Irigo or EC2 respectively. You can even attach worker nodes on your own premises, but notice that this is only recommended if your jobs have small input and output files. Solution 3 allows you the same advantages as a hosted solution, but with your files never leaving your premises and allowing you to process large amounts of data on your own worker nodes without worrying about network costs.