Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] BWCTL MP & LS

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] BWCTL MP & LS


Chronological Thread 
  • From: Verena Venus <>
  • To: Rodesch Christian <>
  • Cc:
  • Subject: Re: [perfsonar-user] BWCTL MP & LS
  • Date: Wed, 28 May 2008 11:17:06 +0200

Hi Christian,

see my comments below.

Am Mittwoch, 28. Mai 2008 10:44:18 schrieb Rodesch Christian:
> Hi everybody,
>
> so after RRD MA has successfully registered to the LS, I'd like the
> other services also to register to the LS.
>
> So currently I deployed the following services:
>
> - RRD MA Service (working 100%)
>
> - BWCTL MP (half working due to xml message problem with perfsonarUI
> although the service is working fine)
>
> - SSH/Telnet (currently not working at all due to the java error I
> posted yesterday)
>
> - AS service (Installed, configured with the Web IF but I'm waiting for
> the edugain certificates in order to check if authentication is working
> although registration to LS is working )
>
> - LookupService (Installed,configured, and self-registration working)
>
> So now I'd like to add the bwctl MP to the LS. Therefore I edited the
> file perfsonar.conf in the directory /opt/perfsonar/services/etc like this:
>
> ###########################################################################
>#### #
> # The following options handle Lookup Service communication:
> #
> ###########################################################################
>####
>
> #enable Lookup Service registration, defaults to 0, can be 0 or 1
> ls_register 1
>
> #keepalive interval in seconds, defaults to 3600 (1 hour)
> keepalive 3600
>
> #Location of Lookup Server (examples)
> ls_url
> "http://perfsonar.restena.lu:8080/xml-ls/services/LookupService";
>
> #Some information to be sent to the Lookup Server:
> hostname "eomer.restena.lu"
> port 8090
> organization "Restena"
> contact
> ""
>
> ###########################################################################
>#### #
> # Options for Authentication:
> #
> ###########################################################################
>####
>
> #enable authentication, defaults to 0, can be 0 or 1
> #auth 0
>
> #Location of Authentication Server
> #as_url
> "http://homer.rediris.es:8080/perfSONAR-AS/services/AuthService";
>
> ###########################################################################
>#### #
> # Configuring services
> #
> ###########################################################################
>#### #
> # The following section contains (at least) one or more entries for
> different
> # perfSONAR services.
> #
> # Each entry is defined by its service name. The service name starts
> with
> # either MA or MP (for Measurement Archive or Measurement Point),
> followed by
> # the type of data or tool and last by domainname or something similar.
> These
> # three parts are seperated by slashes, and represent the endpoint URI
> of the
> # service. The last part, describing the domain is not mandatory. If you
> e.g.
> # have a measurement point service using BWCTL, you would add an entry
> named
> # "MP/BWCTL". Assuming that your service is running on port 8090 and
> your
> # hostname is e.g. "server.mydomain.abc", a client can reach the
> service at
> # "http://server.mydomain.abc:8090/services/MP/BWCTL";.
> #
> #
> # The following examples show a configuration for MP and MA
> #
> ###############
> # MP example: #
> ###############
>
> <service MP/BWCTL>
>
> module MP::BWCTL #name of module to load
> servicetype MP #servicetype: MP or MA
> #name and description, will be reported to Lookup Server
> name "BWCTL Measurement Point"
> description "Measurement Point for doing on-demand BWCTL tests"
>
> #measurement metric(s): (More than one element definition possible)
> metric "bandwidth"
>
> tool "bwctl" #tool name
>
> #list of supported eventtypes: (More than one element definition possible)
> eventtype "bwctl"
> eventtype "http://ggf.org/ns/nmwg/tools/bwctl/2.0/";
> eventtype "http://ggf.org/ns/nmwg/tools/iperf/2.0/";
>
> #command to execute e.g. "/usr/bin/bwctl" or "/bin/bwctl". Omitting path,
> #searches $PATH
> command "bwctl"
>
> </service MP/BWCTL>
>
>
>
> Is this correct? Anyhow, if I launch bwctl MP, it does not register to
> the LS...
>

There might be a problem, but I'm not sure if this is due to mail formatting:

> ls_url
> "http://perfsonar.restena.lu:8080/xml-ls/services/LookupService";

This should be on one line. Configuration file parsing assumes that each new
line cointains a new key-value pair.

Can you launch the MP with --debug and --verbose flag and tell me, if it says
something about LS registration?

Thanks,
Verena

P.S.: the bwctl plugin problem is solved. However, I have to update the old
bwctl MPs running in JRA1, they are not working with the new plugin any more.
I'll let you know when everything is running correctly again.


--
Verena Venus, DFN-Labor
Friedrich-Alexander-Universität Erlangen-Nürnberg
Regionales RechenZentrum Erlangen (RRZE)
Martensstraße 1, 91058 Erlangen, Germany
Tel. +49 9131 85-28738, -28800, Fax +49 9131 302941


www.win-labor.dfn.de


  • BWCTL MP & LS, Rodesch Christian, 05/28/2008
    • Re: [perfsonar-user] BWCTL MP & LS, Verena Venus, 05/28/2008

Archive powered by MHonArc 2.6.16.

Top of Page