Using network packet logs to compare VOSpace service with exiting FileManager^?

Test procedure

One tomcat running all of the core AstroGrid services, including FileManager^? and VOSpace.

Two community accounts, alpha and beta, configured to use the FileManager^? and VOSpace services for their myspace accounts.

Running the python tests included in the vospace source code :

• test-000.py

Using WireShark network analyzer to capture raw network packets, filtered to listen on localhost port 8080.

Export the data from WireShark as a plain text file, producing 'raw' logs files for the myspace and vospace tests :

Raw log files for each test run :

• myspace.003.raw.log
• vospace.003.raw.log

The raw log files contain a lot of additional information about the network packets :

    Frame 1 (74 bytes on wire, 74 bytes captured)
        Arrival Time: Dec 20, 2007 06:39:53.119814000
        [Time delta from previous captured frame: 0.000000000 seconds]
        [Time delta from previous displayed frame: 0.000000000 seconds]
        [Time since reference or first frame: 0.000000000 seconds]
        Frame Number: 1
        Frame Length: 74 bytes
        Capture Length: 74 bytes
        [Frame is marked: False]
        [Protocols in frame: eth:ip:tcp]
        [Coloring Rule Name: TCP SYN/FIN]
        [Coloring Rule String: tcp.flags & 0x02 || tcp.flags.fin == 1]
    Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst: 00:00:00_00:00:00 (00:00:00:00:00:00)
        Destination: 00:00:00_00:00:00 (00:00:00:00:00:00)
            Address: 00:00:00_00:00:00 (00:00:00:00:00:00)
            .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
            .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        Source: 00:00:00_00:00:00 (00:00:00:00:00:00)
            Address: 00:00:00_00:00:00 (00:00:00:00:00:00)
            .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
            .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        Type: IP (0x0800)
    Internet Protocol, Src: localhost.localdomain (127.0.0.1), Dst: localhost.localdomain (127.0.0.1)
        Version: 4
        Header length: 20 bytes
        Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)

Process the raw log files using the following sed scripts to remove network packet data, leaving just the SOAP XML messages.

    sed -n '
    s/    <\//<\//
    / *<soapenv:Envelope/,/< *\/soapenv:Envelope/p
    '  < myspace.003.raw.log > myspace.003.xml.log

    sed -n '
    s/    <\//<\//
    / *<soapenv:Envelope/,/< *\/soapenv:Envelope/p
    '  < vospace.003.raw.log > vospace.003.xml.log

Processed log files for each test run :

• myspace.003.xml.log
• vospace.003.xml.log

The processed log files contain just the SOAP XML messages for each test run :

    <soapenv:Envelope
        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <soapenv:Body>
            <ns1:GetResource
                xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10"
                xmlns:ns1="http://www.ivoa.net/schemas/services/QueryRegistry/wsdl">
                <identifier>
                    ivo://org.astrogrid.junit/8a80808816eb0ddf0116eb0edf040007
                </identifier>
            </ns1:GetResource>
        </soapenv:Body>
    </soapenv:Envelope>

Easiest way to compare the log files is to use a graphical diff tool, like Meld

Test results

Tests show a good match between the original FileManager^? and the new VOSpace services. Two differences still remaining :

community.home.space attribute

The original FileManager^? service adds a home space attribute to the root node:

    <attributes>
        <key>
            community.home.space
        </key>
        <value>
            ivo://org.astrogrid.demo/alpha
        </value>
    </attributes>

This can probably be fixed by adding a community.home.space property to the node if it is created by a call to the myspace addAccount() method.

Node xsi:type and namespace

The new VOSpace service adds a xsi:type attribute and namespace to each Node element:

    <node xsi:type="ns3:Node" xmlns:ns3="urn:astrogrid:schema:filemanager:FileManager:v0.1">
        ....
    </node> 

This does not seem to cause any side effects, so we can probably leave this as-is.

-- DaveMorris - 20 Dec 2007