...
# | Use CaseFunctional Requirement Nonfunctional Requirement | Test Cases | Lab | IntegrationTest Lead | Status(remaining days of effort) | TSC Feedback | Details | Doc status | CI integration* | Components involved | Comments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Model Driven Control Loop Design | Testing with GRA_API in VID/SO/SDNC (vDNS is part of scale out use case below #11) | Intel / Windriver Azure | Recommended for a GO
(need to regression on final dockers) | Recommended for a GO | Distribtion
Instantiation
Control Loop
Work around applied for appc.properties in Jira | https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_vfw.html#docs-vfw minor updates
Blocker:
| ? | SDC Dmaap SDNC SO AAI Policy Appc ... | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 | vCPE with TOSCA
| vCPE(tosca) - Integration test cases | CMCC / Intel |
| Recommended for a GO | https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vCPE_with_Tosca_VNF.html minor updates | Yes | SDC Dmaap AAI Multicloud VFC UUI Modeling ... | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 | 5G - Realtime PM and High Volume Stream Data Collection | 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Cases | Intel / Windriver |
| Recommended for a GO | Test Cases passed on RC0 Test status: 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Cases | https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_5g_rtpm.html#docs-realtime-pm | Yes | DCAE | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 | 5G - PNF PnP
| 5G - PNF PnP - Integration Test Cases | Intel / Windriver |
| Recommended for a GO | Test Cases passed on RC0 | https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_5g_pnf_pnp.html#docs-5g-pnf-pnp minor updates | Already in CI gate | 16.04: Currently released image for SO-BPMN (1.6.0 form27'th of March) is not working. Image from today 16.04 is sufficient and works. v2/onap/so/bpmn-infra/manifests/1.6.0-20200416T0645 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 | 5G - Bulk PM
| 5G - Bulk PM - Test Status | Ericsson Lab | James Cuddy |
| Recommended for a GO |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 | 5G - Configuration with NETCONF | 5G - PNF Configuration via Netconf - Test Status | Intel/ Windriver | This item is duplicate. Please see line #37 for work related to this feature in R6. | Minor updates | Yes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |
| 5G - Preonboarding/Onboarding - Test Status | Intel / Windriver | PNF Preonboarding (VNF SDK): PNF Onboarding (SDC): |
| Recommended for a GO | SOL004 option 1 need to be checked manually in VNFSDK
| 16.04: New image has been released /onap/vnfsdk/refrepo:1.5.1
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 | 5G - OOF SON: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | Integration Test | OWL / Windriver |
updated on 6th May | Recommended for a GO | Test is in progress. | Use case: https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_5G_oof_pci.html SON-Handler MS (DCAE): https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/services/son-handler/index.html Updates for Frankfurt submitted (INT-1466 and DCAEGEN2-2104) | Stretch goal, will take this up in next release | DCAE (SON-Handler MS), Policy, SDN-C, OOF | Use case integration test cases status can be found in below page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 | E2E Network Slicing | Test Status | Windriver/CMCC |
| Recommended for a GO | Test is in progress. | Use case documentation submitted (INT-1468). | Stretch goal, will take this up in next release. | UUI, EXT-API, SO, OOF (Test only: SDC, A&AI, Poilcy) |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 | Scale Out | Scale Out - Integration Test Cases and Status | Intel / Windriver | Recommended for a GO #2 Any blocker? If yes then please provide JIRA Ticket | minor updates | APPC VID DCAE SO Policy ... | Some new platform capabilities have been developed in SO and CDS. If they can’t be used for some reason, we’ll fall back to using the current process. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12 | CCVPN-E LINE over OTN NNI | CCVPN Integration Test Cases | Huawei |
| Recommended for a GO #1 Any blocker? If yes then please provide JIRA Ticket | SDNC-1184 : we We have an outstanding issue in the SDNC DG SDNC DG (SDNC-1184), which will be fixed by May 12th. After that, the integration test will be completed. | https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_CCVPN.html#docs-ccvpn updates will be based on Frankfurt scope | SDNC AAI OOF UUI | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12.1 | CCVPN - MDONS | MDONS Integration Test Case | Fujitsu/Orange |
| Recommended for a GO | Test Environment:
Current blocker: | https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_CCVPN.html#docs-ccvpn updates will be based on Frankfurt scope | SO - C A&AI - C SDN-C - C UUI - C SDC - TO ExtAPI - TO | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
13 | HPA vFW/vDNS | vFW/vDNS HPA Testing(Test Plan 1 inHPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver |
| Recommended for a GO | Testing has been started in OOF project - Windriver lab Manual testing has been progressing Current issue affecting/blocking progress is:
Other known issues: Using patch from
As with line 20 below, manual workaround for the following is being used:
| https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_vfwHPA.html#docs-vfw-hpa | SO SDC VID OOF Policy SDNC AAI | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
15 | Change Management Frankfurt Extensions
| Steps: 1) Instantiation of vFWDT 2) Configuration of OOF Policies for vFWDT 3) Execution of OSDF/HAS requests for data collection 4) Configuration of VNF profiles in CDT 5) Configuration of Ansible Server 6) Execution of the workflow | Intel / Windriver |
Requires functional integration lab to complete Policy/OOF integration test. Updated 7th of May | Recommended for a GO | 1) PASS 2) IN PROGRESS/BLOCKED 3) PASS 4) PASS 5) PASS 6) PASS 90% Completed BLOCKED by non-functional OOF instance to continue tests on SB-00.
| El Alto doc good: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vFWDT.html#docs-vfw-traffic but major updates needed (as the use cases evolved) Major documentation change completed https://gerrit.onap.org/r/c/integration/+/102853 Minor change with policy upload change still to be updated. | No Use case will be semi-automated. All the steps can be performed with scripts but still CI scripts needs to be build. Planned for next release. | SDC AAI SO VID OOF Policy APPC | Use case will be renamed and include upgrade | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
16 | PNF Software Upgrade
| Steps: 1) Execute custom PNF SW Upgrade WF from SO 2) SO send conventional LCM API to SDNC/CCSDK 3) Controller send ansible commands to AS 4) AS contact EM with ansible | Huawei |
| Recommended for a GO | Test results: Test Status of Enhancement on PNF S/W Upgrade with EM with Ansible | Documentation containing new scenarios will be upadted in R6.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
18 | BBS Broadband Service Use Case (Frankfurt) | BBS Integration Test Cases (Frankfurt) | BBS Swisscom Lab |
Swisscom lab is closed. Waiting on the set up of a second lab at UNH-IOL (ongoing) Update: UNH-IOL lab set up needs additional 1-2 days We will do our best to finish BBS tests by May 14th, but it is challenging | Recommended for a GO | Frankfurt doc: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_BBS.html | No, planned for future releases | we need to find a solution to emulate 3rd party controllers first. Our use case relies on physical equipment and external controllers and we can only test it in the Swisscom lab at the moment. We may have a second lab with the required equipment in UNH-IOL, but it is not confirmed yet. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
19 | VSP Compliance and Validation Check within SDC (Frankfurt) - Phase 2 | VSP Compliance Check within SDC - Integration Test Plan | Vodafone |
| Recommended for a GO | https://onap-sdc.readthedocs.io/en/latest/consumedapis.html https://onap-doc.readthedocs.io/projects/onap-sdc/en/latest/externaltesting.html | No | SDC VTP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
20 | K8S based Cloud Region Support - vFW Use case | Deploy vFW Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud
| intel / Windriver |
| Recommended for a GO | completed test with manual workaround for following 3 items: Known issues:
After above are fixed, a retest can be made to verify. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 | K8S based Cloud Region Support - EdgeXFoundry Use case | Deploy EdgeXFoundry Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud | Intel/ Windriver |
| Recommended for a GO | same as line above: initial tests completed using the workarounds described in line #20. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
22 | ORAN A1 Adapter Implemented in ONAP (SDNR) | A1 Adapter Test Cases | Intel/Windriver |
| Recommended for a GO | Need to re-test SSL enabled HTTPS ports among DMAAP message router, SDNC DMAAP listener and SDNC dockers
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
23 | PNF Software Upgrade using direct Netconf/Yang interface with PNF | PNF Software Upgrade Using direct NETCONF/YANG interfacewithPNFTestCases | Intel |
| Recommended for a GO |
Documentation is updated with new use cases in Frankfurt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
24 | Enable PNF software version at onboarding | PNF Software Information Onboarding Test Cases | Ericsson Lab | André Schmid |
| Recommended for a GO | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
25 | K8s CDS Support (vFW_CDS_CNF)
|
| Private lab + Intel/Windriver community lab |
Updated 07.05 | Recommended for a GO | Currently successfully verified with workarounds. Raw recording of live verification session in Windriver lab BLOCKERS:
Fixes under these Jira are currently under verification | https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vFW_CNF_CDS.html but needs to be updated according to latest verification status | Automation of usecase targeted for G release | 07.05: Currently usecase has been verified to work both in internal and windriver lab with workaround. Ongoing tests regarding verifying fixes provided under blocker jiras. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
26 | ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM |
Manual testing for package management is done. Due to delay on the package management notification issues for SDC and ETSI Catalog Manager SOL001 VNFD handling discrepancies, CSIT test has been delayed. Now, the discrepancies are resolved. Will update the status again by May 6th based on the progress.
| Recommended for a GO #2 Any blocker? If yes then please provide JIRA Ticket | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
27 | SOL 004 (VNF Package Security) | 5G - Preonboarding/Onboarding - Test Status | Ericsson, Intel / Windriver | All activities, status (incl. days to completion) of this item are embedded into “5G - Preonboarding/Onboarding - Test Status” | Please see item “5G - Preonboarding/Onboarding - Test Status” | Please see item “5G - Preonboarding/Onboarding - Test Status” | Please see item “5G - Preonboarding/Onboarding - Test Status” | Please see item “5G - Preonboarding/Onboarding - Test Status” | All activities, status (incl. days to completion) of this item are embedded into “5G - Preonboarding/Onboarding - Test Status” | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
28 | xNF communication security enhancements. | xNF communication security enhancements - Tests Description and Status |
| Recommended for a GO | Tes Cases passed on RC0. Test status: xNF communication security enhancements - Tests Description and Status | Yes | DCAE | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
30 | PNF Software Upgrade
| PNF software upgrade in R6 Frankfurt | Huawei |
| Recommended for a GO | Test results: Test Status of PNF S/W Upgrade with EM with Netconf/Yang interface |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
31 | 5G - 5G NRM Network Resource Model (Configuration Mgmt) | 5G Network Resource Model (NRM) Configuration in R6 Frankfurt | Huawei |
| Recommended for a GO | New documentation to be created, as it is a new use case for Frankfurt
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
37 | Configuration with NETCONF in Frankfurt/R6
| Detailed Steps carried out for performing E2E Testcases can be found at : E2E Integration Testing for NETCONF over TLS Configuration- Test Case | Ajay Deep Singh |
| Recommended for a GO | At present one test case is getting failed due to :
Expected to be completed by next week. |
| Yes | AAF-Certservice, SDNC, Netconf-Pnp-Simulator | Currently Blocked on below issues:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
38 | E2E Automation vLB w/CDS Use Case (Frankfurt) NOTE: SO is using Config Assign & Config Deploy building blocks. SO Marco Instantiation using Controller Execution Building Block [new for Frankfurt] for vLB Instantiation will be a separate test case.[row below] | Steps: Design Time 1) CBA Package onboarding CDS 2) SDC VSP, VF, Service Creation and onbaording for vLB. Run Time: 1) SO send Marcro requst to SDNC GR-API 2) SDNC GR-API send request to CDS, Netbox, Naming for instantiation resource auto resolution 3) SO sends request to CDS for Config Assign. 4) SO sends request to Openstack for vLB Instantiation 5) SO send request to CDS for ConfigDeploy | Intel / Windriver |
| Recommended for a GO | CDS, SDNC, SO, Policy, Naming MS, Netbox | SO issue with heat stack creation. Jira is open.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
39 | Steps:
| Telstra |
| Recommended for a GO
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
40 |
| WinLAB |
| Recommended for a NO GO Candidate to be descoped from Frankfurt since no update or to move under POC #1 Can you please provide an estimate about how many days of effort left/Target date completion? #2 Any blocker? If yes then please provide JIRA Ticket Benjamin Cheung to update status by May 8. | Integration work will be part of OOF / SON / PCI Use Case. will have the same integration status as that use case. | (Read the Docs entry in progress) being done under Integration Jira-1526
| SDN-C (CC-SDK) using MariaDB | Sandeep is leading the Integration & Development. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use cases without resources for Frankfurt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 | Use Case: Residential Broadband vCPE (Approved) | vCPE Integration Test Case | Intel / Windriver | PROGRESSING <90% ??? During May 4 PTL meeting, Morgan Richomme reports that this issue may need to be de-scoped since there are no resources available for integration test. | Not restested as part of Frankfurt release | https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vCPE.html | No | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
14 | Change Management - Flexible Designer & Orchestrator | Steps: 1) Designing custom workflows with Workflow Designer 2) Distributing custom workflows to SO 3) Deploying the custom workflow in SO 4) Sending workflow metadata to VID 5) Triggering custom workflow execution from VID 6) Executing custom workflows in SO | Intel / Windriver |
| Not restested as part of Frankfurt release | 1) Designing custom workflows with Workflow Designer – 100% 2) Distributing custom workflows to SO – Was 100% in Dublin Issues arose with SDC Distribution in El Alto and remain unresolved – 80% working now. However, SO does work properly with manual WF distribution and workaround notes are posted on the wiki 3) Deploying the custom workflow in SO – 100% 4) Sending workflow metadata to VID – 100% 5) Triggering custom workflow execution from VID – 100% 6) Executing custom workflows in SO – Execution mechanism 100%, Building Blocks – 60% (Had many issues with test environment & APPC blocking testing from Nov-Jan) 7) Pause for Manual Task – 100% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
17 | Change Management - Schedule Optimization | Intel / Windriver |
| Not restested as part of Frankfurt release | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 | HPA vIPsec | vIPsec HPA testing | Intel / Windriver | Not tested | Not restested as part of Frankfurt release | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Pairwise testing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
32 | TOSCA Compliant Policy types | Pairwise Testing | Intel / Windriver |
| Recommended for a GO #1 Can you please provide your tests results? #2 Any automated tests? | Testing completed via CLAMP/Policy pairwise testing over the time period between M4 and RC1 in SB01/SB00. Additional testing is covered via the vFW, Scale Out, vFW CDS use cases. Automated test for vFW updated:
No other automated tests for CLAMP as this was tested manually using CLAMP GUI. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
33 | Policy Update Notifications | Pairwise Testing | Intel / Windriver |
| Recommended for a GO #1 Can you please provide your tests results? #2 Any automated tests? | Testing completed via POLICY/DCAE pairwise testing completed by RC0. No automated tests. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
34 | CLAMP Deployment of Policies to PDP Groups | Pairwise Testing | Intel / Windriver |
| Recommended for a GO #1 Can you please provide your tests results? #2 Any automated tests? | Testing completed via CLAMP/Policy pairwise testing over the time period between M4 and RC1 in SB01/SB00. Additional testing is covered via the vFW, Scale Out, vFW CDS use cases. No automated tests as this is done manually via the CLAMP GUI. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
35 | Integration of CDS as an Actor | Integration Testing | Intel / Windriver |
| Recommended for a GO #1 Can you please provide your tests results? #2 Any automated tests? | Policy - CDS integration test was successfully completed in SB01 lab for vFW use case. CLAMP - Policy integration test was successfully completed in SB01 lab for vFW use case. |
https://docs.onap.org/en/latest/submodules/policy/parent.git/docs/development/actors/cds/cds.html | Policy Framework CDS A&AI CLAMP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
36 | Component Upgrades to the new Policy Lifecycle API | Pairwise Testing | Intel / Windriver |
| Recommended for a GO #1 Can you please provide your tests results? #2 Any automated tests? | Policy/CCSDK testing was successfully completed via pairwise testing in SB01 by RC0. Policy/OOF testing successfully completed by RC1 and was done in SB01. No automated tests. |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Misc | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Robot Keyword Testing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
init | BDF | OK | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
health | Integrated in gate |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
eteHelm-k8.sh | BDF* | OK | Not integrated in gate but onap-k8s and onap-helm (not based on Robot) Integrated in Gate | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
healthdist | Integrated in gate |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiateVFWCLGRA | BDF | OK | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
demo-k8s.sh -n onap vfwclosedloop <png_ip> | BDF | OK | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiateVFWDTGRA | BDF | OK | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
distributeVCPE | BDF | OK | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
distributeVCPEResCust | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sdc-dcae-d | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
vcpe.py | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
postinstall | Integrated in gate |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
72 Hour Stability Run | onboard/instantiate | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
closedloop | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HTTP Certificate Expiry Test (verify_cert.sh) | clamp 3/2020 dmaap 3/2020 | Tobe integrated in gate, raise an error in CI when 1 of the certificates is about to expire (in 2 weeks?) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
27 | Component/memory optimization: Ongoing Assessment | OOM | Addressed by OOM in Guilin | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 | S3P- Geo-Redundancy | Integration | Not tested as part of Frankfurt release | No resources | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
35 | Health Checks for PODS | Percentage coverage of Health Checks for Running PODS | Integration | Hard to define...and to test | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
36 | New Installation Tests in 4 labs | Intel/Windriver | Integration | Reccurent activity | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Orange (Rocky) | Morgan Richomme | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ericsson Lab (Rocky) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DT |
...