IVOA Operations Interest Group | |||||||||||||||||
Changed: | |||||||||||||||||
< < | Chair: Mark Taylor Vice Chair: Steve Groom | ||||||||||||||||
> > | |||||||||||||||||
Changed: | |||||||||||||||||
< < | IVOA Operations Interest Group Charter | ||||||||||||||||
> > | Overview | ||||||||||||||||
Added: | |||||||||||||||||
> > |
Organisation
| ||||||||||||||||
Goal of the IVOA Operations Interest GroupCoordinate and publicize activities of individuals, institutions and groups interested in facilitating robust operations of distributed astronomy applications, particularly those based upon implementations of IVOA protocols. | |||||||||||||||||
Added: | |||||||||||||||||
> > | See also the Operations IG Charter. | ||||||||||||||||
Specific responsibilities
| |||||||||||||||||
Deleted: | |||||||||||||||||
< < | Organisation | ||||||||||||||||
Changed: | |||||||||||||||||
< < | Chair: Mark Taylor | ||||||||||||||||
> > | Mailing list | ||||||||||||||||
Changed: | |||||||||||||||||
< < | Vice Chair: Steve Groom | ||||||||||||||||
> > |
| ||||||||||||||||
Added: | |||||||||||||||||
> > | |||||||||||||||||
Operations Projects | |||||||||||||||||
Deleted: | |||||||||||||||||
< < | Procedure for Removing Non-Responsive Services | ||||||||||||||||
Deleted: | |||||||||||||||||
< < | VO-Paris has presented a plan for a process for removing non-responsive services from the Registry which was presented to the Exec and discussed in the Interest Group. A revised version will be provided. A revised procedure was adoped by the IVOA in October 2016. | ||||||||||||||||
Federated Validation Services | |||||||||||||||||
Added: | |||||||||||||||||
> > | The following links are to reports from services that perform bulk validation on a regular basis of all registered services of particular types (SCS, SIA, SSA, TAP, ...). If you are the operator of a registered service, you can (and should!) go here to see whether your service is passing the validation tests. | ||||||||||||||||
Coordination of VO validation servicesIt was agreed that the three sites that are currently collecting validation statistics will try to coordinate their activities. The first step is to provide a standard set of identifiers for issues so that results from the validators can be compared. This will allow us to compare the validator results and 'validate' the validators. | |||||||||||||||||
Changed: | |||||||||||||||||
< < | NCSA/HEASARC Validation tests (Conesearch and SIA) | ||||||||||||||||
> > | |||||||||||||||||
Added: | |||||||||||||||||
> > | |||||||||||||||||
Deleted: | |||||||||||||||||
< < | VO Paris Validation Test ESA Validation Tests | ||||||||||||||||
Data from these documents has been combined into the following documents: Analysis of the results from these documents suggests that the validators are making somewhat different queries and that any given validator is only testing a subset of all poassible errors. Negative results regarding a service are generally valid. In principle a service should pass all validators. | |||||||||||||||||
Added: | |||||||||||||||||
> > | List of Validation SoftwareThe Operations IG maintains a list of available validation software is indexed by the IVOA standard whose content they check, on the wiki page IvoaValidatorsSummary. This list is usually reviewed at six-monthly Interop meetings, but if you have updates you can edit the wiki page directly.Procedure for Removing Non-Responsive ServicesVO-Paris has presented a plan for a process for removing non-responsive services from the Registry which was presented to the Exec and discussed in the Interest Group. A revised version will be provided. A revised procedure was adoped by the IVOA in October 2016. | ||||||||||||||||
Identifying Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point. | |||||||||||||||||
Changed: | |||||||||||||||||
< < | |||||||||||||||||
> > | Identifying Server Software | ||||||||||||||||
Changed: | |||||||||||||||||
< < | Mailing list | ||||||||||||||||
> > | In some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTP Server header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar. | ||||||||||||||||
Deleted: | |||||||||||||||||
< < |
| ||||||||||||||||
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||
Deleted: | |||||||||||||||||
< < | Links | ||||||||||||||||
Deleted: | |||||||||||||||||
< < | The earlier list of validators is now subsumed into the IvoaValidatorsSummary. | ||||||||||||||||
Deleted: | |||||||||||||||||
< < | Continuous hourly monitoring of VO services is available at the HEASARC | ||||||||||||||||
Deleted: | |||||||||||||||||
< < | DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group | ||||||||||||||||
| |||||||||||||||||
Added: | |||||||||||||||||
> > |
| ||||||||||||||||