Swedish National Infrastructure for Computing

SweGrid - The Swedish GRID Initiative

SweGrid: e-Infrastructure for distributed computing and storage

SNIC forms the Swedish National Grid Initiative (NGI) in the European Grid Infrastructure (EGI), and as such SNIC participates in the EGI collaboration at many levels.

Part of the SNIC's resources makes up Sweden's contribution to the WLCG collaboration: computational elements and storage for the Swedish part of the Nordic Tier-1, organised through NeIC, and, computational elements and storage for the Swedish Tier-2.

A few SNIC resources are also grid-enabled for usage other than WLCG.

SweGrid Support

Getting support

The SweGrid systems use the SNIC National helpdesk for support as other SNIC resources. To send a support request regarding the SweGrid resources use the following email address:

    support (at) swegrid.se

It is important that us use this email address instead of contacting the system administrators directly as it opens a support ticket that will be visible to all administrators in SweGrid.

Applying for time

Time on SweGrid can be applied to in the same way as other SNIC resources:

Large size application
Large scale applications 

Medium size application
Medium scale application 

Test accounts (8000 ch/m)
Please contact the SweGrid site-administrator at your nearest location.


Answers frequently asked questions

Q: Can I install the ARC client on Windows or Mac OS X

Currently it is not possible to install the ARC client software on Windows or Mac OS X. A solution to this problem is to use some kind of virtualisation technology such as VMWare Fusion/Workstation, Sun Virtual Box or Parallels to install a Linux operating system supported by ARC.

Q: What is a certificate?

A central concept in grid authentication is the certificate. Every user and service on the Grid is identified via a certificate, which contains information vital to identifying and authenticating the user or service.

A grid certificate includes four primary pieces of information:

  • A subject name, which identifies the person or object that the certificate represents.
  • The public key belonging to the subject.
  • The identity of a Certificate Authority (CA) that has signed the certificate to certify that the public key and the identity both belong to the subject.
  • The digital signature of the named CA.

Note that a third party (a CA) is used to certify the link between the public key and the subject in the certificate. In order to trust the certificate and its contents, the CA's certificate must be trusted. The link between the CA and its certificate must be established via some non-cryptographic means, or else the system is not trustworthy.

Grid certificates are encoded in the X.509 certificate format, a standard data format for certificates established by the Internet Engineering Task Force (IETF). These certificates can be shared with other public key-based software, including commercial web browsers from Microsoft and Netscape.

Q: What is a proxy certificate

Proxies are certificates signed by the user, or by another proxy, that do not require a password to submit a job. They are intended for short-term use, when the user is submitting many jobs and cannot be troubled to repeat his password for every job. The subject of a proxy certificate is the same as the subject of the certificate that signed it, with /CN=proxy added to the name. The gatekeeper will accept any job requests submitted by the user, as well as any proxies he has created.

Proxies provide a convenient alternative to constantly entering passwords, but are also less secure than the user's normal security credential. Therefore, they should always be user-readable only, and should be deleted after they are no longer needed (or after they expire).

To create a proxy with the default expiration (12 hours), run the grid-proxy-init program. For example:

% grid-proxy-init

The grid-proxy-init program can also take arguments to specify the expiration and proxy key length. For example:

% grid-proxy-init -hours 8 -bits 512

To delete a proxy that was previously created with grid-proxy-init, run:

% grid-proxy-destroy