Difference: CrossOSGCE (1 vs. 7)

Revision 72014/07/29 - Main.IgorSfiligoi

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

CrossOSG CE Web page

Added:
>
>
Note: This page is deprecated!
 This page contains information pertaining the CrossOSG CE installation.

Description

Line: 19 to 21
  From a user point of view, the CrossOSG CE is just another OSG CE.
However, at least for the time being, only a limited set of VO pilot administrators are allowed to use it.
If you are interested in getting access, please contact isfiligoi at ucsd.edu.
Changed:
<
<
The recommended way to get access to this CE is through the OSG glidein factory.
Direct access is however, at least in theory, still possible. For more details, see the usage page.
>
>
The recommended way to get access to this CE is through the OSG glidein factory.
Direct access is however, at least in theory, still possible. For more details, see the usage page.
 

System components and instructions

Revision 62013/05/16 - Main.IgorSfiligoi

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

CrossOSG CE Web page

Line: 7 to 7
  The CrossOSG CE is a glideinWMS-based instance of a standard HTCondor-based OSG CE.
Changed:
<
<
... to be finished ...

Components

>
>
For a conceptual point of view, it is trying to solve two problems:
  • How do we get all VOs to easily get access to each and every CPU slot out there
  • How can OSG management regulate who gets how much opportunistic resources

Architecturally, we achieve this by creating a glidein pool out of all the opportunistic resources and then tell VOs to get access to them via this glidein pool.

Technically, this means creating the glidein infrastructure and provide a CE on top of it so VOs can submit into it.

How to use it

From a user point of view, the CrossOSG CE is just another OSG CE.
However, at least for the time being, only a limited set of VO pilot administrators are allowed to use it.
If you are interested in getting access, please contact isfiligoi at ucsd.edu.

The recommended way to get access to this CE is through the OSG glidein factory.
Direct access is however, at least in theory, still possible. For more details, see the usage page.

System components and instructions

  The CrossOSG CE hosted at UCSD has the follow components:
  • A HTCondor Collector where all the glideins register to, together with a Negotiator which handles user priorities

Revision 52013/05/10 - Main.IgorSfiligoi

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

CrossOSG CE Web page

Line: 14 to 14
 
  • A HTCondor Collector where all the glideins register to, together with a Negotiator which handles user priorities
  • A glideinWMS Fronend that implementsthe provisioning logic
Added:
>
>
 

Revision 42013/05/03 - Main.IgorSfiligoi

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

CrossOSG CE Web page

Line: 19 to 19
  -- IgorSfiligoi - 2013/05/02
Changed:
<
<
META FILEATTACHMENT attachment="80_crossosgce_domain.config" attr="h" comment="Condor config file containing the CrossOSGCE specific bits" date="1367597962" name="80_crossosgce_domain.config" path="80_crossosgce_domain.config" size="278" stream="80_crossosgce_domain.config" tmpFilename="/tmp/fUFCJLy1qd" user="IgorSfiligoi" version="1"
>
>
META FILEATTACHMENT attachment="80_crossosgce_domain.config" attr="" comment="Condor config file containing the CrossOSGCE specific bits" date="1367597962" name="80_crossosgce_domain.config" path="80_crossosgce_domain.config" size="278" stream="80_crossosgce_domain.config" tmpFilename="/tmp/fUFCJLy1qd" user="IgorSfiligoi" version="1"

Revision 32013/05/03 - Main.IgorSfiligoi

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

CrossOSG CE Web page

Line: 17 to 17
 
Deleted:
<
<
 -- IgorSfiligoi - 2013/05/02 \ No newline at end of file
Added:
>
>
META FILEATTACHMENT attachment="80_crossosgce_domain.config" attr="h" comment="Condor config file containing the CrossOSGCE specific bits" date="1367597962" name="80_crossosgce_domain.config" path="80_crossosgce_domain.config" size="278" stream="80_crossosgce_domain.config" tmpFilename="/tmp/fUFCJLy1qd" user="IgorSfiligoi" version="1"

Revision 22013/05/02 - Main.IgorSfiligoi

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

CrossOSG CE Web page

Line: 15 to 15
 
  • A glideinWMS Fronend that implementsthe provisioning logic
  • An OSG CE, together with the HTCondor Schedd subsystem, where user jobs live
Changed:
<
<

>
>
  -- IgorSfiligoi - 2013/05/02

Revision 12013/05/02 - Main.IgorSfiligoi

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

CrossOSG CE Web page

This page contains information pertaining the CrossOSG CE installation.

Description

The CrossOSG CE is a glideinWMS-based instance of a standard HTCondor-based OSG CE.

... to be finished ...

Components

The CrossOSG CE hosted at UCSD has the follow components:

  • A HTCondor Collector where all the glideins register to, together with a Negotiator which handles user priorities
  • A glideinWMS Fronend that implementsthe provisioning logic
  • An OSG CE, together with the HTCondor Schedd subsystem, where user jobs live

-- IgorSfiligoi - 2013/05/02

 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback