8
OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

Embed Size (px)

Citation preview

Page 1: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

OPNFV Test Dashboard

10/09/2015M.Richomme, Orange

Page 2: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

2

Introduction

• Test projects are producing results (hopefully)

• Results have different forms (html, json, logs, …)

• Some results are stored, some not

• Results are not post processed for the moment (great community testbed federation not leveraged yet)

• Soon same test shall be automatically run on different hardware, with different installers and different

July 2015 OPNFV Confidential

Page 3: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

3

Introduction

July 2015 OPNFV Confidential

Page 4: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

4

Need to collect and process results

July 2015 OPNFV Confidential

Page 5: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

519 September 2014 OPNFV Confidential

Call flow

Page 6: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

6

Demo

Page 7: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

7

Next steps• Consolidate API

– Work on data model (version, installer ….are missing)– More unit tests– Add unit tests in CI– Add API auto doc (pyswagger)

• Move to LF DB

• Functest

– Push results for the other testcases (Tempest, Rally, ODL, ..)– Develop and Commit Test2Dashboard scripts and generate all the required json

files for dashboard

• Test with other test projects (Yardstick, Qtip, …)

• Proof of Concept of the Dashboard

• Secure DB (backup/Restore mechanisms)

July 2015 OPNFV Confidential

Page 8: OPNFV Test Dashboard 10/09/2015 M.Richomme, Orange

8

Thanks