Opendaylight I&V strategy


Luis Gomez <luis.gomez@...>
 

Hi all,

My name is Luis am I am very new in the Opendaylight project (just joined yesterday), my background is System Integration & Verification and E2E testing (Ericsson and Multi-vendor). I have just been appointed to coordinate and drive Integration&Verification efforts to have a successful Opendaylight release.

With this purpose we will be doing a short presentation next Hackfest that will conver things like:

- Release plan: pretty much in place, only release vehicles (Basic, Service Provider, Cloud editions, etc...) are still under discussion
- Anatomy map: ODL components and dependencies/interfaces among them
- Release-Anatomy plan: how the release plan (time based) fits with anatomy map (function based)
- Test strategy: different kind of tests (unit, continuous integration, continuous system integration, system, etc...), responsibilities (project, community) and flow (how often, when to run the different tests)
- System Test Plan: Description of TCs and resources needed to do a system test

So for now and till the Hackfest I would like to ask the community:

- Collaboration: Anyone that wants to join and collaborate with common test activities please contact me
- Information: I am looking for any high level view of ODL components and dependencies (specially within the controller project that seems to be the more complicated), also information on any system test performed by the controller or any other project is very welcome.

Thanks
Luis


Luis Gomez <luis.gomez@...>
 

Excellent, I will contact you on a separate mail. I will also remind doors are still open for those interested in collaborating in join test effort, please just contact me.

BR/Luis

-----Original Message-----
From: Liguangpeng (Roc, IPTechnologyResearchDept&HW) [mailto:guangpeng.li@...]
Sent: Sunday, September 08, 2013 8:20 PM
To: Luis Gomez
Cc: tsc@...; controller-dev@...; discuss@...
Subject: RE: Opendaylight I&V strategy

Hi Luis,

Sorry for my delayed response. I am interested in OpenFlow plugin project. If possible, I am glad to join the test Collaboration.

Thanks
Guangpeng

-----Original Message-----
From: controller-dev-bounces@...
[mailto:controller-dev-bounces@...] On Behalf Of Luis
Gomez
Sent: Saturday, September 07, 2013 5:12 AM
To: controller-dev@...; discuss@...
Cc: tsc@...
Subject: [controller-dev] Opendaylight I&V strategy

Hi all,

My name is Luis am I am very new in the Opendaylight project (just joined
yesterday), my background is System Integration & Verification and E2E testing
(Ericsson and Multi-vendor). I have just been appointed to coordinate and drive
Integration&Verification efforts to have a successful Opendaylight release.

With this purpose we will be doing a short presentation next Hackfest that will
conver things like:

- Release plan: pretty much in place, only release vehicles (Basic, Service
Provider, Cloud editions, etc...) are still under discussion
- Anatomy map: ODL components and dependencies/interfaces among them
- Release-Anatomy plan: how the release plan (time based) fits with anatomy
map (function based)
- Test strategy: different kind of tests (unit, continuous integration, continuous
system integration, system, etc...), responsibilities (project, community) and
flow (how often, when to run the different tests)
- System Test Plan: Description of TCs and resources needed to do a system test

So for now and till the Hackfest I would like to ask the community:

- Collaboration: Anyone that wants to join and collaborate with common test
activities please contact me
- Information: I am looking for any high level view of ODL components and
dependencies (specially within the controller project that seems to be the more
complicated), also information on any system test performed by the controller
or any other project is very welcome.

Thanks
Luis


_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev