Difference between revisions of "GOCDB/Transfer Data Format"
< GOCDB
Jump to navigation
Jump to search
Line 42: | Line 42: | ||
<certificate_dn>/DC=com/DC=quovadisglobal/DC=grid/DC=switch/DC=users/C=CH/O=SWITCH/CN=Steven Newhouse</certificate_dn> | <certificate_dn>/DC=com/DC=quovadisglobal/DC=grid/DC=switch/DC=users/C=CH/O=SWITCH/CN=Steven Newhouse</certificate_dn> | ||
</user> | </user> | ||
<downtime scope="EGI" operation="Update"> | |||
</downtime> | |||
</gocdb_data></source> | </gocdb_data></source> |
Revision as of 09:58, 23 June 2011
Introduction
The format of data transferred between a regional and central GOCDB instance is documented here. This will be a single XML document containing all objects that have been inserted, updated or deleted.
Example
This example shows a single site being synchronised. This site is either new or to be updated (operation=update).
<?xml version="1.0" encoding="UTF-8"?>
<gocdb_data>
<site scope="EGI" operation="Update">
<primary_key>4839G3</primary_key>
<short_name>RAL-LCG2</short_name>
<description>STFC, e-Science, RAL</description>
<country>UK</country>
<ngi>UKI</ngi>
<timezone>GMT</timezone>
<certification_status>certified</certification_status>
<production_status>production</production_status>
<domain>rl.ac.uk</domain>
</site>
</gocdb_data>
Example 2
This example shows both a service endpoint and a downtime being updated. It also shows a user being deleted.
<?xml version="1.0" encoding="UTF-8"?>
<gocdb_data>
<service_endpoint scope="EGI" operation="delete">
<primary_key>449G3</primary_key>
<hostname>test.host.com</hostname>
<service_type>APEL</service_type>
<ip>10.0.0.1</
<site>RAL-LCG2</site>
</service_endpoint>
<user scope="EGI" operation="delete">
<primary_key>392G3</primary_key>
<forename>Steven<forename>
<surname>Newhouse</surname>
<email>steve@egi.eu</email>
<certificate_dn>/DC=com/DC=quovadisglobal/DC=grid/DC=switch/DC=users/C=CH/O=SWITCH/CN=Steven Newhouse</certificate_dn>
</user>
<downtime scope="EGI" operation="Update">
</downtime>
</gocdb_data>