network conformance test suite plus associated documentation · 2015. 3. 1. · del-038 01 october...
TRANSCRIPT
-
GLORIA is funded by the European Union 7th Framework Programme
(FP7/2007-2013) under grant agreement n° 283783
Network conformance test suite plus associated documentation
CODE: DEL-038
VERSION: 01
DATE: October 24th, 2012
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Authors: Martin JELINEK (CSIC)Davide Ricci (INAF) Oscar LARA-GIL (CSIC)Alberto J. CASTRO-TIRADO (CSIC)Javier GOROSABEL(CSIC)Ronan CUNNIFFE (CSIC)Juan CABELLO (UMA)René Hudec (AUAV)Lorraine Hanlon (UCDNUID)
Collaborators:
Revised by: Raquel CEDAZO (UPM) Fernando IBÁÑEZ (UPM)
Approved by: Francisco Manuel SÁNCHEZ (UPM) Alberto J. CASTRO-TIRADO (CSIC)
Distribution List:
Name Affiliation DateFrancisco Manuel SÁNCHEZ UPM October 24th,, 2012
Raquel CEDAZO UPM October 24th,, 2012
Fernando IBÁÑEZ UPM October 24th,, 2012
Alberto J. CASTRO-TIRADO CSIC October 24th,, 2012
Oscar LARA-GIL CSIC October 24th,, 2012
Javier GOROSABEL CSIC October 24th,, 2012
Martin JELINEK CSIC October 24th,, 2012
Ronan CUNNIFFE CSIC October 24th,, 2012
Juan CABELLO UMA October 24th,, 2012
Davice RICCI INAF October 24th,, 2012
René Hudec AUAV October 24th,, 2012
Lorraine Hanlon (UCD) UCDNUID October 24th,, 2012
http://gloria-project.eu 3/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Change Control
Issue Date Section Page Change Description01 24/10/2012 All All Creation
Reference Documents
Nº Document Name Code VersionR.1 Bank of R.T trials DEL-017 01
R.2 API expansion and OS update DEL-025 01
R.3 Report for high level standard interfaces for RT networks DEL-021 01
http://gloria-project.eu 4/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Index1. Introduction...............................................................................................................................................................7
1.1. Purpose.............................................................................................................................................................71.2. Scope................................................................................................................................................................7
2. How to test your Robotic Telescope to get into GLORIA Network.......................................................................72.1. Overall description of registering a new telescope in GLORIA Network.......................................................72.2. Automatic Test Suite.........................................................................................................................................72.3. Testing telescope (TAD) and WSDL file ........................................................................................................72.4. Graphical User Interface used for testing (RTS Tester)...................................................................................8
2.4.1. Accessibility.............................................................................................................................................82.4.1.1. Tests 1.1...........................................................................................................................................92.4.1.2. Tests 1.2...........................................................................................................................................92.4.1.3. Tests 1.3...........................................................................................................................................92.4.1.4. Tests 2.1...........................................................................................................................................9
2.4.2. Security....................................................................................................................................................92.4.2.1. Test 1.1...........................................................................................................................................10
2.4.3. Protocol..................................................................................................................................................102.4.3.1. Tests 1.1.........................................................................................................................................102.4.3.2. Tests 1.2.........................................................................................................................................112.4.3.3. Tests 1.3.........................................................................................................................................122.4.3.4. Test 1.4...........................................................................................................................................132.4.3.5. Test 1.5...........................................................................................................................................13
2.4.4. Storage...................................................................................................................................................152.4.4.1. Test 1.1 and Test 1.2......................................................................................................................162.4.4.2. Test 3.1 ..........................................................................................................................................16
Figures IndexFigure 1: Overall aspect of the RTS Tester...................................................................................................................8Figure 2: Testing CCD status......................................................................................................................................11Figure 3: Testing DOME status..................................................................................................................................12Figure 4: Testing MOUNT status...............................................................................................................................13Figure 5: Telescope parked.........................................................................................................................................14Figure 6: Telescope moving to the Sun......................................................................................................................15Figure 7: Telescope staring at the Sun........................................................................................................................15
http://gloria-project.eu 5/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
http://gloria-project.eu 6/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
1. Introduction
By performing an automatic test, a RT owner can know the compliance level with the GLORIA interface. If there is any problem with any part of the interface the owner will be reported about it, to let him know where to put the effort in order to pass this stage, as part of the acceptance process.
1.1. Purpose
The purpose of this document is to provide GLORIA owners an easy way of registering technically them Robotic Telescopes.
1.2. Scope
This document is intended to the RTs owners, who want to include a RT into the GLORIA network.
2. How to test your Robotic Telescope to get into GLORIA Network
First of all we have to know, that the devices/operations declared in the registration form by the owner of the RT will be done by providing the URL where the WSDL file is published.
2.1. Overall description of registering a new telescope in GLORIA Network
1. First of all you must fill in the RT Registration Form at GLORIA website, all the data related to owner and RT. These data will be checked before starting the automatic test suite.
2. Then the URL where the WDSL is published will be checked.
3. Is now when the automatic test suite will examine your RT, performing a test to each service described in the Registration Form which has its own interface, GLORIA compliant. (this step is the main focus of the current document that you are reading)
4. Once all tests are done you will be reported with the outcome of them. In case of failure the integration process will be stopped until you fix those problems.
5. When your RT pass all the tests properly, and Administrative Validation process will start.
2.2. Automatic Test Suite
Next the tests that GS will perform to the RT are listed in four different categories:
− Accessibility
− Security
− Protocol
− Storage
2.3. Testing telescope (TAD) and WSDL file
In order to perform the atomic test of each step in this process of technical acceptance for a Remote Telescope the TAD (Open Dissemination Telescope) telescope at Canary Islands has been the one selected.
The testing environment used, has been the 'pre-production' one, and it is accesible through next ip:161.72.128.9:8443
The public WSDL file describing the web services avaialble at the RT by the secure layer protocol is:https://161.72.128.9:8443/RTI/gloria_rti.wsdl
The web service related to the server is available through authentication at:https://161.72.128.9:8443/RTI/services/gloria_rtiSOAP?wsdl
http://gloria-project.eu 7/18
https://161.72.128.9:8443/https://161.72.128.9:8443/RTI/gloria_rti.wsdl
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
NOTE: Please note that this environment is not always up and running, so if you have no success in checking it, please try it again later.
2.4. Graphical User Interface used for testing (RTS Tester)
The tool used to test many of the testing situations, present in this document have been carried out by the GUI developed at the University of Málaga, by the people enrolled in the project, from the ISA department.
The technology used to develop the testing tool is Java and the widget toolkit selected has been Swing.
Thanks to this testing application we can have a set of Remote Telescope Systems (note the 'Add RTS' button at the bottom-left edge) registered in the application in order to test and check the status of each device in the telescope.
Regarding the tests regarding availability and security, they will be implemented when the auto-checking procedure in order to accept a Remote Telescope will be implemented as well as the storage tests.
By now it is only possible to test the Basic Devices (camera, dome and mount) (see Figure 1)
2.4.1. Accessibility
We just need to check that the devices/operations declared in the WSDL file, provided by its URL at registration form, are the same as the provided by the latest release WSDL file of GLORIA project.
Description:
1. Get the files from the RT, using the URL base given in the registration form.
http://gloria-project.eu 8/18
Figure 1: Overall aspect of the RTS Tester
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
The files required to be present in the RT must be:
gloria_rti.wsdlgloria_rti_fault.xsdgloria_rti_device.xsd
In case of failure, the process of integration stops and G.S. notifies the owner with the problem.
2. For each device/operation included in the registration form declared by the WSDL URL, G.S. must check whether is available in the lastest WSDL file released by GLORIA Project. This check will be just a text file comparison.
In case of mismatch, the process of integration stops and G.S. notifies the owner with the problem.
3. Continue with security trials.
2.4.1.1. Tests 1.1
Verify that the file gloria_rti_fault.xsd at the RT is the same as the reference file in GS.
If the result is not null then success
If no response or error is received, then the file is not published correctly
2.4.1.2. Tests 1.2
Verify that the file gloria_rti_device.xsd at the RT is the same as the reference file in GS.
If the result is not null then success
If no response or error is received, then the file is not published correctly
2.4.1.3. Tests 1.3
Verify that the file gloria_rti.wsdl at the RT is the same as the reference file in GS.
If the result is not null then success
If no response or error is received, then the file is not published correctly
2.4.1.4. Tests 2.1
Very for each device/operation present in the WDSL provided by the RT at registration form, that is equal to the last version of WSDL released by GLORIA Project.
This check will be just a text file comparison.
2.4.2. Security
To guarantee authentication and confidentiality in communications between the RT and G.S.
Description:
1. All request must be performed through a secure connection protocol (HTTPS).
2. The communication from GS to RT must be encrypted with a specified certification, the use of a wrong certificate should give error.
3. Assure that when a message from RT enter to GS that its IP address correspond with the appropriated RT.
4. These trials will be implicitly passed in future phases of the integration process.
http://gloria-project.eu 9/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
2.4.2.1. Test 1.1
Retrieve the devices list using user and password provided by the RT owner by HTTPS without obtaining an “untrusted server exception” and using a correct certificate. The name of the server inside the certificate must be the same as the domain in the URL.
2.4.3. Protocol
To assure that the RT complies with the basic functionalities of the communication protocol with G.S.
In this case, the tests are functional tests, apart from the tests performed in the step 1, Availability, where we were just confirming that the devices declared by the owner in the registration form, are present in the latest WSDL file released by the GLORIA Project.
Description:
1. Get available devices/operations of the RT.
For each device/operation, check that the operation is responsive.
2.4.3.1. Tests 1.1
CAMERA: Retrieve the status (see Figure 2)
If the result is not null then success
If no response or error is received, then the device is not present.
WSDL:
Code:
Device dev = proxy.devGetDevice(null,"DMx41AU02.AS",true); if (dev.getCommunicationState() == CommunicationState.READY) if (dev.getAlarmState() == AlarmState.NONE)
http://gloria-project.eu 10/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Results :
2.4.3.2. Tests 1.2
DOME: Retrieve the status (see Figure 3)
If the result is not null then success
If no response or error is received, then the device is not present.
WSDL :
Code :
Device dev = proxy.devGetDevice(null,"dome",true);if (dev.getCommunicationState() == CommunicationState.READY)
if (dev.getAlarmState() == AlarmState.NONE)
http://gloria-project.eu 11/18
Figure 2: Testing CCD status
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Results :
2.4.3.3. Tests 1.3
MOUNT: Retrieve the status (see Picture 2.4)
If the result is not null then success
If no response or error is received, then the device is not present.
WSDL :
Code :
Device dev = proxy.devGetDevice(null,"Gemini",true); if (dev.getCommunicationState() == CommunicationState.READY) if (dev.getAlarmState() == AlarmState.NONE)
http://gloria-project.eu 12/18
Figure 3: Testing DOME status
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Results :
2.4.3.4. Test 1.4
[device]: Retrieve the status of any other device declared in the RT system.
If the result is not null then success
If no response or error is received, then the device is not present.
2.4.3.5. Test 1.5
Moving the telescope to a position.
Then periodically perform a call to get the current position of the mount, until the position of the RT will be the same that the position required by GS.
WSDL :
http://gloria-project.eu 13/18
Figure 4: Testing MOUNT status
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Code : Device dev = proxy.mntSlewToCoordinatesAsync(null, “MOUNT”,RA,DEC);
int timer = 0; while ((proxy.mntGetTargetDeclination(arg0, arg1) != RA ||
proxy.mntGetTargetRightAscension(arg0, arg1)) != DEC && (timer < 1000)){ timer ++;
}if (timer < 1000)
success else ERROR
Results :
Initially the telescope is parked and we want it to move it to the RA/DEC labelled with the 'Goto RA' and 'Goto DEC' at the picture (see Figure 5)
In the GUI we can see different fields.
− The ones labelled with 'RA' and 'DEC' are the current position of the telescope, in grey background colour.
− Fields labelled with 'Goto RA' and 'Goto DEC' are the ones that we must fill in order to slew the telescope to the desired position.
Using the button 'Go' and having checked the 'Goto RADEC' check-box, the telescope starts to move to the coordinates introduced.
Then the telescope starts to move, slewing to the indicated position (see Figure 6), so the current coordinates values changes.
http://gloria-project.eu 14/18
Figure 5: Telescope parked
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
Finally the telescope reaches to the desired position indicated by the user of the RTS Tester. (see Figure 7)We can see that 'RA' and 'DEC' are equivalent to 'Goto RA' and 'Goto DEC' fields.
2.4.4. Storage
In case of the RT owner wants to share some storage space with GLORIA, it is needed to verify that the offered capacity by the RT is coherent with the registration form.
Description:
1. Get and validate the total capacity shared with GLORIA.
Check this value with the one proposed by the owner in the registration form.
2. Get and validate the available capacity.
This value must be equal to the total capacity in the beginning.
3. Get and validate the space used by GLORIA.
This value must be 0 in the begining.
4. In case of failure, the process of integration stops and G.S. notifies the owner with the problem.
http://gloria-project.eu 15/18
Figure 6: Telescope moving to the Sun
Figure 7: Telescope staring at the Sun.
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
2.4.4.1. Test 1.1 and Test 1.2
Perform a call to the File System information and check that the bytes used and bytes available are in total the amount reported by the RT owner in the registration form.
WSDL:
Code:
DbFileSystemInfo dev = proxy.dbGetFileSystemInfo(null,"DBDEVICE"); if (dev.getFree() >= [size_provided_by_owner_at_registration_form])
success
2.4.4.2. Test 3.1
Perform a call to the File System information and check that the bytes used are equal to zero.
WSDL
Code :
DbFileSystemInfo dev = proxy.dbGetFileSystemInfo(null,"DBDEVICE");if (dev.getUsed()==0)
success
http://gloria-project.eu 16/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
GLORIA Partners
http://gloria-project.eu 17/18
-
DEL-038 01 October 24th, 2012 Network conformance test suite plus associated documentation
UPMUniversidad Politécnica de MadridSPAIN
ASU-CASAstronomical Institute, Academy of Sciences of the Czech RepublicCZECH REPUBLIC
CSICConsejo Superior de Investigaciones CientíficasSPAIN
CTUCzech Technical University in PragueCZECH REPUBLIC
FZU-CASInstitute of Physics of the Academy of Sciences of the Czech RepublicCZECH REPUBLIC
IACInstituto de Astrofísica de CanariasSPAIN
INAFIstituto Nazionale di AstrofisicaITALY
SAOSpecial Astrophysical Observatory of Russian Academy of SciencesRUSSIA
UCDUniversity College DublinIRELAND
UCHUniversity of ChileChile
UMAUniversity of MálagaSPAIN
UOXUniversity of OxfordUNITED KINGDOM
UWARUniwersytet Warszawski POLAND
http://gloria-project.eu 18/18
1. Introduction1.1. Purpose1.2. Scope
2. How to test your Robotic Telescope to get into GLORIA Network2.1. Overall description of registering a new telescope in GLORIA Network2.2. Automatic Test Suite2.3. Testing telescope (TAD) and WSDL file2.4. Graphical User Interface used for testing (RTS Tester)2.4.1. Accessibility2.4.1.1. Tests 1.12.4.1.2. Tests 1.22.4.1.3. Tests 1.32.4.1.4. Tests 2.1
2.4.2. Security2.4.2.1. Test 1.1
2.4.3. Protocol2.4.3.1. Tests 1.12.4.3.2. Tests 1.22.4.3.3. Tests 1.32.4.3.4. Test 1.42.4.3.5. Test 1.5
2.4.4. Storage2.4.4.1. Test 1.1 and Test 1.22.4.4.2. Test 3.1