PerfSONAR service definition

From GEANT2-JRA1 Wiki

[edit]

What is a service in the context of perfSONAR?


[edit]

What is perfSONAR-compliant service?

perfSONAR community would like to promote its model and protocol and ensure that our tools are as broadly available as possible. As pS protocol is available openly we want to ensure that different implementors use it as a basis for implementation and at the same time allowing for multiple technology and implementations. Through a specification of perfSONAR-compliant service we want to provide our users with interoperability across different pS applications based on the common use of the same protocol and a set of functionalities that must be supported.

[edit]

What is JRA1-supported service?

The Multi-Domain Monitoring (MDM) service being deployed in the GN2 community enables a user to gain an ubiquitous access to a set of network performance data or to perform network monitoring actions across different network domains. The MDM relies on perfSONAR web-services. JRA1 activity developing the core of MDM services helps maintain and provides problem resolution only for these services that go into MDM. We call them JRA1-supported services. JRA1-supported service must fulfill perfSONAR-compliant requirements and due to customer-oriented application meet some more expectations to deliver high-quality products and effective usage.


[edit]

perfSONAR-compliant service requirements

In order to call the service perfSONAR-compliant we require it to:

  • Implement NMWG schema in request and response messages
    • When extensions to NMWG schema are required, they have to be proposed, discussed and documented.
  • Implement SOAP web services
    • NMWG requires use of document style & literal encoding type of Web Service (shortly called doc/lit or document/literal).
    • perfSONAR compliant web services will have to use doc/lit type of Web Services
  • Use Result codes whenever a service cannot do a normal operation
  • Implement Lookup Service registration
  • Implement Echo functionality


What is the process for allowing a service to call itself perfSONAR-compliant?


[edit]

JRA1-supported service requirements

In order to call the service perfSONAR-supported we require it to be perfSONAR-compliant and:

  • Use perfSONAR-base as generously as possible (avoid repetition of functionality)
    • This currently applies to software developed in Java only
  • Use Ant for installation scripts (or alternatives for non-Java developments) providing following steps (functionalities within each item to be defined):
    • pre-install
    • configure
    • deploy
    • test
    • undeploy
  • Include documentation:
    • Functional specification
    • Interface specification
    • Change log
      • Changes between two consecutive releases of the web service product will have to be logged
  • Obey service naming scheme (specification to be detailed)
  • Stricly follow a well-defined versioning scheme for software releases
  • Have license


What is the process for calling a Web Service as perfSONAR-supported?


PLEASE NOTE: In order to improve perfSONAR services, we regularly update these definitions. We will communicate such updates via our mailing lists (perfsonar-dev and perfsonar-user). We will provide sufficient lead times before requiring new definitions to be applied to existing Web Service implementations.

Back to PerfSONAR_and_JRA1_Resources

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/PerfSONAR_service_definition"
Personal tools