perfsonar-dev - Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI
Subject: perfsonar development work
List archive
- From: "Nina Jeliazkova" <>
- To: Roman Lapacz <>, "Vedrin Jeliazkov" <>
- Cc: "Loukik Kudarimoti" <>, "Michael Michalis" <>, "Roman Lapcz" <>, "" <>
- Subject: Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI
- Date: Wed, 14 Mar 2007 21:15:22 +0200
Roman,
Thanks for the advice. I guess the example at page 7 of
Interface_specification.doc should be updated, since it uses the old syntax of
select event. (Seems like SQL storage specific problem).
The response changed, while still reporting an error.
<?xml version="1.0" encoding="UTF-8"?>
<nmwg:message id="mdrq1_resp" messageIdRef="mdrq1"
type="SetupDataResponse" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
<nmwg:metadata id="resultCodeMetadata">
<nmwg:eventType>error.sqlma.db_connection</nmwg:eventType>
</nmwg:metadata>
<nmwg:data id="resultDescriptionData_for_resultCodeMetadata"
metadataIdRef="resultCodeMetadata">
<nmwgr:datum
xmlns:nmwgr="http://ggf.org/ns/nmwg/result/2.0/">SQLStorageManager.fetch:
Unable to fetch data</nmwgr:datum>
</nmwg:data>
</nmwg:message>
Best regards,
Nina
Roman Lapacz
<>
wrote:
> Loukik Kudarimoti wrote:
> > Roman, Michalis? Any comments?
>
> Take a look at example request:
>
>
http://anonsvn.internet2.edu/svn/perfsonar/tags/JAVA-SQL-MA-1.0-RC5/schema/example-instances/perfSONAR/SetupDataRequest-FilterRRDSelect-2.xml
>
> There are two new eventType values, for utilization and select. I see
> that you didn't change the second one.
>
> Roman
>
>
> >
> > Loukik.
> >
> >
> > Nina Jeliazkova wrote:
> >> Hi Loukik,
> >>
> >> I've tried several SetupDataRequest messages as in
> >>
>
http://anonsvn.internet2.edu/svn/perfsonar/tags/JAVA-SQL-MA-1.0-RC5/doc/ma/sqlTypeMA/Interface_Specification.doc
>
> >>
> >>
> >> but none of them are working for me (see attached). The response is
> >> the same
> >> as previous one, reported by Vedrin.
> >>
> >> Best regards,
> >> Nina
> >>
> >>
> >>
> >> "Vedrin Jeliazkov"
> >> <>
> >> wrote:
> >>
> >>
> >>> Hi again,
> >>>
> >>> After some further tests we noticed that replacing "utilization" with
> >>> "http://ggf.org/ns/nmwg/characteristic/utilization/2.0" (either in
> >>> MA.conf
> >>> (twice!) or in the Playground tab) helps, but doesn't solve all
> >>> issues. In
> >>> this case perfsonarUI retrieves successfully hostName, ifAddress,
> >>> ifName,
> >>> ifDescription and Capacity, but fails to retrieve utilization data. The
> >>> service returns the following error to the respective SetupDataRequest:
> >>>
> >>> - - - - 8< - - - -
> >>> No output metadata was returned by MessageHandler. Maybe there was
> >>> no data
> >>> trigger, or data trigger didn't have valid metadataIdRef?
> >>>
> >>> - - - - 8< - - - -
> >>>
> >>> Please see attached query and response.
> >>>
> >>> Best regards,
> >>> Vedrin
> >>>
> >>> Loukik Kudarimoti
> >>> <>
> >>> wrote:
> >>>
> >>>
> >>>> Hi Vedrin,
> >>>>
> >>>> Roman is in the cc. I hope he can comment on this.
> >>>>
> >>>> What we are aware of is that the protocol for RRD MA and SQL MA now
> >>>> accept new event types (which use namespaces) as well as old ones
> >>>> (to help you guys out in the transition phase). It looks like this
> >>>> is not the case for utilization? Roman?
> >>>>
> >>>> ps: documentation for RRD MA and SQL MA that are being closed to
> >>>> being released (still release candidates as you can see in the URLs).
> >>>>
> >>>>
> >>>>
> >>
>
http://anonsvn.internet2.edu/svn/perfsonar/tags/JAVA-RRD-MA-2.0-RC9/doc/ma/rrdTypeMA/
>
> >>
> >>
> >>
>
http://anonsvn.internet2.edu/svn/perfsonar/tags/JAVA-SQL-MA-1.0-RC5/doc/ma/sqlTypeMA/
>
> >>
> >>
> >>>> Loukik.
> >>>>
> >>>>
> >>>> Vedrin Jeliazkov wrote:
> >>>>
> >>>>> Hi Loukik,
> >>>>>
> >>>>> We've the service via the current JWS version of perfsonarUI,
> >>>>> available
> >>>>>
> >>>> online
> >>>>
> >>>>> here:
> >>>>>
> >>>>> http://perfsonar.acad.bg/
> >>>>>
> >>>>> In the Playground tab, we've entered the URL of your service and the
> >>>>>
> >>>> following
> >>>>
> >>>>> query:
> >>>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>> <nmwg:message id="1158922769968" type="MetadataKeyRequest"
> >>>>> xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/"
> >>>>>
> >>>>> xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"
> >>>>> xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/"
> >>>>> xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/">
> >>>>> <nmwg:metadata id="meta1">
> >>>>> <netutil:subject id="iusub1">
> >>>>> <nmwgt:interface/>
> >>>>> </netutil:subject>
> >>>>> <nmwg:eventType>utilization</nmwg:eventType>
> >>>>> </nmwg:metadata>
> >>>>> <nmwg:data id="data1158922770015" metadataIdRef="meta1"/>
> >>>>> </nmwg:message>
> >>>>>
> >>>>> We got the following response:
> >>>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>> <nmwg:message id="1158922769968_resp" messageIdRef="1158922769968"
> >>>>> type="MetadataKeyResponse"
> >>>>>
> >>> xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
> >>>
> >>>>> <nmwg:metadata id="resultCodeMetadata">
> >>>>> <nmwg:eventType>error.ma.query</nmwg:eventType>
> >>>>> </nmwg:metadata>
> >>>>> <nmwg:data id="resultDescriptionData_for_resultCodeMetadata"
> >>>>> metadataIdRef="resultCodeMetadata">
> >>>>> <nmwgr:datum
> >>>>>
> >>>>>
> >>
>
xmlns:nmwgr="http://ggf.org/ns/nmwg/result/2.0/">MetadataQueryGeneratorFactory.getMetadataQueryGenerator:
>
> >>
> >>
> >>>>> eventType utilization is not supported</nmwgr:datum>
> >>>>> </nmwg:data>
> >>>>> </nmwg:message>
> >>>>>
> >>>>> It looks like the configured eventType is not "utilization", but
> >>>>>
> >> something
> >>
> >>>>> else. Could you check its value and tell us what it is? This
> >>>>> parameter
> >>>>>
> >>> could
> >>>
> >>>>> be configured in MA.conf if it is known in advance. Of course, there
> >>>>>
> >> might
> >>
> >>>> be
> >>>>
> >>>>> some further unresolved issue, but let's try and see ;-)
> >>>>>
> >>>>> Best regards,
> >>>>> Vedrin
> >>>>>
> >>>>> Loukik Kudarimoti
> >>>>> <>
> >>>>> wrote:
> >>>>>
> >>>>>
> >>>>>> Hi Vedrin and Nina,
> >>>>>>
> >>>>>> I have installed SQL Measurement Archive on a dante workstation.
> >>>>>> It is accessible here:
> >>>>>>
> >>>>>>
> >>>>>>
> >>
>
http://mu.dante.org.uk:8092/perfSONAR-SQL-MA-1.0-RC5/services/MeasurementArchiveService
>
> >>
> >>
> >>>>>
> >>>>>> This measurement archive provides access to utilization data in the
> >>>>>>
> >> same
> >>>>>> way as the RRD Measurement Archive service. The only difference
> >>>>>> is that
> >>>>>>
> >>
> >>
> >>>>>> it contacts a database on the backend instead of the rrd files.
> >>>>>> Hence, the contents of the key are different as well.
> >>>>>>
> >>>>>> I tried to check if perfSONAR UI (v 0.8) can show the interfaces
> >>>>>> and data configured on the sql ma (test configuration) but it
> >>>>>> didn't. Any idea? Is it because the key is different?
> >>>>>>
> >>>>>> Loukik.
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>
> >>
> >>
> >> ------------------------------------------------------------------------
> >>
> >> <?xml version='1.0' encoding='UTF-8'?>
> >> <nmwg:message id="msg"
> >> type="SetupDataRequest"
> >>
> >> xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/"
> >> xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"
> >> xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/"
> >> xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/">
> >>
> >> <nmwg:metadata id="meta1">
> >> <netutil:subject id="iusub1">
> >> <nmwgt:interface>
> >> <nmwgt:ifAddress type="ipv4">10.1.2.3</nmwgt:ifAddress>
> >> <nmwgt:direction>in</nmwgt:direction>
> >> <nmwgt:hostName>test-hostName</nmwgt:hostName>
> >> <nmwgt:ifName>test-0</nmwgt:ifName>
> >> <nmwgt:direction>in</nmwgt:direction>
> >> <nmwgt:authRealm>TestRealm</nmwgt:authRealm>
> >> <nmwgt:capacity>1000BaseT</nmwgt:capacity>
> >> </nmwgt:interface>
> >> </netutil:subject>
> >> <nmwg:eventType>
> >> http://ggf.org/ns/nmwg/characteristic/utilization/2.0
> >> </nmwg:eventType>
> >> </nmwg:metadata>
> >>
> >> <nmwg:metadata id="meta2">
> >> <select:subject id="iusub2" metadataIdRef="meta1"/>
> >> <select:parameters id="param1">
> >> <nmwg:parameter name="startTime">1121472000</nmwg:parameter>
> >> <nmwg:parameter name="endTime">1121904000</nmwg:parameter>
> >> </select:parameters>
> >> <nmwg:eventType>select</nmwg:eventType>
> >> </nmwg:metadata>
> >>
> >> <nmwg:data id="data1" metadataIdRef="meta2"/>
> >>
> >> </nmwg:message>
> >>
> >>
> >>
> >> ------------------------------------------------------------------------
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <nmwg:message id="msg_resp" messageIdRef="msg"
> >> type="SetupDataResponse" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
> >> <nmwg:metadata id="resultCodeMetadata">
> >> <nmwg:eventType>warning.common.no_metadata</nmwg:eventType>
> >> </nmwg:metadata>
> >> <nmwg:data id="resultDescriptionData_for_resultCodeMetadata"
> >> metadataIdRef="resultCodeMetadata">
> >> <nmwgr:datum xmlns:nmwgr="http://ggf.org/ns/nmwg/result/2.0/">No
> >> output metadata was returned by MessageHandler. Maybe there was no
> >> data trigger, or data trigger didn't have valid metadataIdRef?
> >> </nmwgr:datum>
> >> </nmwg:data>
> >> </nmwg:message>
> >> ------------------------------------------------------------------------
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <nmwg:message id="mdrq1_resp" messageIdRef="mdrq1"
> >> type="MetadataKeyResponse"
> >> xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
> >> <nmwg:metadata id="meta1-test">
> >> <netutil:subject id="subj1"
> >> xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/">
> >> <nmwgt:interface
> >> xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/">
> >> <nmwgt:hostName>test-hostName</nmwgt:hostName>
> >> <nmwgt:ifName>test-0</nmwgt:ifName>
> >> <nmwgt:ifDescription>test description</nmwgt:ifDescription>
> >> <nmwgt:ifAddress type="ipv4">10.1.2.3</nmwgt:ifAddress>
> >> <nmwgt:direction>in</nmwgt:direction>
> >> <nmwgt:authRealm>TestRealm</nmwgt:authRealm>
> >> <nmwgt:capacity>1000BaseT</nmwgt:capacity>
> >> </nmwgt:interface>
> >> </netutil:subject>
> >> <nmwg:parameters id="localhost.10c25f7a:111517961b0:-3436">
> >> <nmwg:parameter
> >>
>
name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter>
>
> >>
> >> </nmwg:parameters>
> >> </nmwg:metadata>
> >> <nmwg:data id="data1-test" metadataIdRef="meta1-test">
> >> <nmwg:key id="localhost.10c25f7a:111517961b0:-3433">
> >> <nmwg:parameters id="localhost.10c25f7a:111517961b0:-3432">
> >> <nmwg:parameter name="eventType" value="
> >> http://ggf.org/ns/nmwg/characteristic/utilization/2.0"/>
> >> <nmwg:parameter
> >> name="ibatisConfig">ibatis-SqlMapConfig-utilization.xml</nmwg:parameter>
> >> <nmwg:parameter name="metadataId">meta1-test</nmwg:parameter>
> >> </nmwg:parameters>
> >> </nmwg:key>
> >> </nmwg:data>
> >> </nmwg:message>
>
<?xml version='1.0' encoding='UTF-8'?>
<nmwg:message type="SetupDataRequest"
id="mdrq1"
xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/"
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"
xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/"
xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/">
<nmwg:metadata id="meta1">
<nmwg:key id="localhost.648d2dab:10c33bffe91:-7fa9">
<nmwg:parameters id="localhost.648d2dab:10c33bffe91:-7fa8">
<nmwg:parameter name="ibatisConfig">
ibatis-SqlMapConfig-utilization.xml
</nmwg:parameter>
<nmwg:parameter name="metadataId">meta1-test</nmwg:parameter>
<nmwg:parameter name="eventType">
http://ggf.org/ns/nmwg/characteristic/utilization/2.0
</nmwg:parameter>
</nmwg:parameters>
</nmwg:key>
</nmwg:metadata>
<nmwg:metadata id="meta2">
<select:subject id="iusub2" metadataIdRef="meta1"/>
<select:parameters id="param1">
<nmwg:parameter name="startTime">1143034709</nmwg:parameter>
<nmwg:parameter name="endTime">1149070711</nmwg:parameter>
</select:parameters>
<nmwg:eventType>http://ggf.org/ns/nmwg/ops/select/2.0</nmwg:eventType>
</nmwg:metadata>
<nmwg:data id="1" metadataIdRef="meta2"/>
</nmwg:message>
- Accessing SQL MA via perfSONAR UI, Loukik Kudarimoti, 03/14/2007
- Re: Accessing SQL MA via perfSONAR UI, Vedrin Jeliazkov, 03/14/2007
- Re: Accessing SQL MA via perfSONAR UI, Loukik Kudarimoti, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Vedrin Jeliazkov, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Loukik Kudarimoti, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Loukik Kudarimoti, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/14/2007
- Re: [pS-dev] Re: Accessing SQL MA via perfSONAR UI, Vedrin Jeliazkov, 03/14/2007
- Re: Accessing SQL MA via perfSONAR UI, Loukik Kudarimoti, 03/14/2007
- Re: Accessing SQL MA via perfSONAR UI, Vedrin Jeliazkov, 03/14/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Szymon Trocha, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Loukik Kudarimoti, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Roman Lapacz, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/15/2007
- Re: [pS-dev] Accessing SQL MA via perfSONAR UI, Nina Jeliazkova, 03/15/2007
Archive powered by MHonArc 2.6.16.