opensciencegrid/topology repository overview

⁠Topology

This repository contains the registry of OSG projects, site resources, and Virtual Organizations, as well as scripts for managing and displaying this information.

For registration instructions, please see this document⁠.

The information was sourced from the former OIM site that was hosted at oim.grid.iu.edu. This README contains the following sections:

• Structure of the Registry⁠
• Viewing the Registry⁠
• Getting Help⁠

⁠Structure of the Registry

The data is organized as files in YAML format⁠ as follows:

• projects/ contains information about research projects that run jobs on OSG. Each project has its own file, named <PROJECT>.yaml

• virtual-organizations/ contains information about Virtual Organizations (VOs). Each VO has its own file, named <VO>.yaml. Additionally, there is a REPORTING_GROUPS.yaml file that contains information about WLCG metric reporting groups for each VO.

• topology/ contains information about the topology of the resources that OSG sites provide. Resources such as HTCondor-CE, GridFTP, XRootD, or Squid are collected into "resource groups." Each resource group has its own file, which are further organized by facility, and then by site. Resource group files are named <FACILITY>/<SITE>/<RESOURCEGROUP>.yaml

  For example, the OSG resources in the Center for High Throughput Computing can be found in the following file: topology/University of Wisconsin/CHTC/CHTC.yaml

⁠Viewing the Registry

Registry data can be accessed in two formats: the YAML files can be accessed directly through the GitHub interface or from a clone of the GitHub repository. Alternatively, the registry data can be accessed in XML format at the following URLs:

These XML pages are compatible with the XML format once provided by myosg.grid.iu.edu.

⁠XML page arguments

Some of the XML pages listed above accept arguments for filtering queries. These are compatible with the arguments once used by myosg.grid.iu.edu.

⁠For the Resource Topology (rgsummary) and Resource Downtime (rgdowntime) pages

Boolean filters:

* Note lack of service_hidden=on argument
** There is no way to show only resources without WLCG information; has_wlcg=off doesn't work

ID-based filters:

These select by a numeric ID on facilities, sites, support centers, resource groups, and services, and VOs. Multiple IDs may be specified for an attribute, in which case resources that match any of the IDs listed will be shown. There are two equivalent formats for the arguments:

• <ATTRIB>=on&<ATTRIB>_<ID1>=on&<ATTRIB>_<ID2>=on&<ATTRIB>_<ID3>=on
• <ATTRIB>=on&<ATTRIB>_sel[]=<ID1>&<ATTRIB>_sel[]=<ID2>&<ATTRIB>_sel[]=<ID3>

For example, either of the two following sets of arguments will show resources that are in ANL (10089), Fermilab (10009), or UW-Madison (10011):

• facility=on&facility_10089=on&facility_10009=on&facility_10011=on
• facility=on&facility_sel[]=10089&facility_sel[]=10009&facility_sel[]=10011

If multiple filters are specified, only resources that match all filters will be shown.

Finally, you may restrict how much past downtime is shown in the Resource Downtime XML with:

• downtime_attrs_showpast=all: show all past downtime
• downtime_attrs_showpast=<DAYS>: show downtime that ended no earlier than <DAYS> days ago. For example downtime_attrs_showpast=7 shows downtime that ended within the past 168 hours (7 days * 24 hours per day).
• downtime_attrs_showpast=0: show no past downtime; this is the default if not specified

⁠For the Virtual Organization (vosummary) page

Boolean filters:

ID-based filter:

This selects based on a numeric ID on VOs. Multiple IDs may be specified, in which case VOs that match any of the IDs listed will be shown. There are two equivalent formats for the arguments:

• vo=on&vo_<ID1>=on&vo_<ID2>=on&vo_<ID3>=on
• vo=on&vo_sel[]=<ID1>&vo_sel[]=<ID2>&vo_sel[]=<ID3>

For example, either of the following will match GLOW (13), HCC (67), and IceCube (38):

• vo=on&vo_13=on&vo_67=on&vo_38=on
• vo=on&vo_sel[]=13&vo_sel[]=67&vo_sel[]=38

⁠Getting Help

If you have any questions or encounter any issues with the registry, please open a ticket through the system appropriate for the VO(s) that you support:

Or email us at [email protected]⁠.