Difference between revisions of "GOCDB/Release4/Development/VSites/VOFeedXML"
< GOCDB | Release4 | Development | VSites
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
[[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP|<< Back to Virtual Sites]] | [[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP|<< Back to Virtual Sites]] | ||
=VO Feed Example= | =VO Feed Example= | ||
This VO feed will include every | VO feed for the GOCDB EGI scoped data (ATP will recognize this gocdb data as the 'OPS' VO topology feed). | ||
* This VO feed will include every 'EGI' scoped Physical Site, and each will be represented with an <atp_site> element. | |||
* All the child Services of that site will be listed as child <service> elements of the parent <atp_site> element, regardless of scope (including both EGI and Local). | |||
* The GOCDB Virtual Sites that aggregate those Services will also be listed using the child <group> element. | |||
* The feed specifies that all sites are under the ops VO using the <vo>OPS</vo> element. | |||
In summary, the GOCDB to ATP mappings are: | |||
* Site == <atp_site> | |||
* ServiceEndpoint == <service> | |||
* VSite == <group> | |||
==Questions for ATP:== | ==Questions for ATP:== | ||
Line 7: | Line 17: | ||
<br /> | <br /> | ||
<source lang="XML"> | <source lang="XML"> | ||
todo | |||
</source> | |||
<!-- | |||
<?xml version="1.0" encoding="ISO-8859-1"?> | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="atp_vo_feed_schema.xsd"> | <root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="atp_vo_feed_schema.xsd"> | ||
Line 25: | Line 38: | ||
</atp_site> | </atp_site> | ||
</root> | </root> | ||
--> |
Revision as of 14:06, 15 February 2012
VO Feed Example
VO feed for the GOCDB EGI scoped data (ATP will recognize this gocdb data as the 'OPS' VO topology feed).
- This VO feed will include every 'EGI' scoped Physical Site, and each will be represented with an <atp_site> element.
- All the child Services of that site will be listed as child <service> elements of the parent <atp_site> element, regardless of scope (including both EGI and Local).
- The GOCDB Virtual Sites that aggregate those Services will also be listed using the child <group> element.
- The feed specifies that all sites are under the ops VO using the <vo>OPS</vo> element.
In summary, the GOCDB to ATP mappings are:
- Site == <atp_site>
- ServiceEndpoint == <service>
- VSite == <group>
Questions for ATP:
- We've left the infrast="EGEE" attribute on the atp_site element. Is this correct?
todo