[onap-discuss] Openlab

[morgan.richomme]

Y a de la demande... (au moins 5 nouvelles demande spirent sopra et jiba) 
Je tente de gérer un peu ce matin.. 

Envoyé depuis mon téléphone Orange
_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #52001] [ONAP] need a VM for integration reporting aggregation

[morgan.richomme]

Hi

just a short update

2 new dockers have been started and a new database has been added in the 
existing mongo on the opnfv testresults machine.

the reporting page for onap can be found at 
http://testresults.opnfv.org/onap-testing/
the reporting page is installer centric (oom, heat) but could be adapted. Link 
to public CI/CD could also be added if needed

for the moment only the Orange Openlab is pushing some test results (robot 
tests on Amsterdam release): 
http://testresults.opnfv.org/onap-testing/amsterdam/functest/status-heat.html
the swagger of the test API dedicated to ONAP: 
http://testresults.opnfv.org/onap/swagger/spec.html (same password than for 
OPNFV to access the page)
with some examples (no need of a password to get info from the DB through the 
API)
- list of declared ONAP pods: http://testresults.opnfv.org/onap/api/v1/pods
- list of functional testcases: 
http://testresults.opnfv.org/onap/api/v1/projects/functest/cases
- some results: 
http://testresults.opnfv.org/onap/api/v1/results?case=robot_healthcheck=orange-pod4=5
for the results you can play with all the possible filters: version, pod, case, 
installer (oom, heat), dates (from/to), last N iterations, last N days...

I imagine it could be interesting to define a DNS redirection
testresults.onap.org => testresults.opnfv.org/onap-testing/
testresults-api.onap.org => testresults.opnfv.org/onap/

/Morgan




Le mercredi 14 février 2018 à 08:59 +0100, Morgan Richomme a écrit :
Hi Jess

hmm, I showed in a demo yesterday that it was relatively easy to adaptable to 
ONAP :)
see 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670=/6593670/25433913/integration_demo_E2E_chain.pdf
 for details
I rewrote what was needed..

However instead of creating a new resources as I mentioned in my ticket, I 
think it would make sense to reuse existing OPNFV VM.
The VM has still resources, the goal is the same in ONAP and OPNFV, collecting 
cases/results and creating aggreagte view
Moreover the DB backup mechanism is automated (from OPNFV 
http://artifacts.opnfv.org/testapibackup.html)
we could
- add a new DB in mongo
- start a new test API docker (re-use of existing docker) dedicated to ONAP 
connected to this new DB
- start a new reporting docker (adaptation of the existing one, need a repo 
integration/reporting to share the core) adapted to ONAP
- reconfigure the nginx
- confidure a onap.org subdomain integration.onap.org or testresults.onap.org

I still have access to the machine, I can do the 4 first actions quickly...but 
I would need action from your side for the subdomain..

/Morgan


Le mercredi 14 février 2018 à 02:36 -0500, Jessica Wagantall via RT a écrit :
Dear Morgan,

I was talking today with Aric about this (since he has seen this working in 
opnfv).
I know from him that this system is not easily adaptable to other projects.

Are you familiar with how this system is developed?

Do you know who can help us rewriting this so that easily adaptable to other 
projects?

Thanks!
Jess

On Mon Feb 05 03:17:16 2018, 
morgan.richo...@orange.com wrote:
Hi,

would it be possible to get IT resources to host ONAP integration
results.
The idea is to collect test results from the different CI chains and
provide an aggregated view of the results (referencing jenkins runs on
different labs with different installers, on different versions
(Amsterdam, Master (Beijing),..).
It is an adaptation of what is currently done in OPNFV
(http://testresults.opnfv.org/).
The most straight forward way would be
- duplication of the testresults.opnfv.org VM managed by Linux
Foundation (nginx, docker APi, docker reporting, mongo DB, git, would
be preinstalled)
- configuration of testresults subdomain for onap main domain to point
testresults.onap.org to the IP of this duplicated VM

I would make some cleaning on the duplicated VM
- clean several accounts used in OPNFV and not needed for ONAP
- dump of the OPNFV DB
- creation of ONAP DB (installers: OOM, Heat; test cases: Functional
test cases (robot, vFW, vLB,), benchmark ..)

We should also re-use the existing jenkins Jobs in order to sync the
deployement of the dockers, backup the DB from ONAP main CI

If it is not possible to duplicate the VM, is it possible to get a
fresh VM
- 2 vCPU
- 80 Go disk
- 8 Go Ram
We could even start smaller if needed, but that is the current sizing
on OPNFV side and we had to increase it once (initial sizing was too
small)

I gave a try on my local POD and took some screenshots (attached file)
Please note that Functest here means all the functional testing (no
bijection with the OPNFV functest project) and would leverage the
robot healtcheck as well as automated functional testcases.
Benchmark corresponds to the new benchmark project

I think it is a good example of Xcommunity synergies..

Thanks

Morgan

_

Ce message et ses 

[onap-discuss] [ONPA] [Integration] test API/Reporting integration chain follow-up (ad-hoc meeting)

[morgan.richomme]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Romance Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=RICHOMME Morgan IMT/OLN:MAILTO:morgan.richo...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=chenyan.br
 i...@chinatelecom.cn:MAILTO:chenyan@chinatelecom.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DEBEAU Eri
 c IMT/OLN:MAILTO:eric.deb...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Helen.Chen
 @huawei.com:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ran.Pollak
 @amdocs.com:MAILTO:ran.pol...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=gary.i.wu@
 huawei.com:MAILTO:gary.i...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=feng.xiaow
 e...@zte.com.cn:MAILTO:feng.xiao...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Roger.Mait
 l...@amdocs.com:MAILTO:roger.maitl...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tina.Tsou@
 arm.com:MAILTO:tina.t...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=gildas.lan
 i...@huawei.com:MAILTO:gildas.lani...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=tim.irnich
 @ericsson.com:MAILTO:tim.irn...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=rpaik@linu
 xfoundation.org:MAILTO:rp...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=bryan.sull
 i...@research.att.com:MAILTO:bryan.sulli...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jwagantall
 @linuxfoundation.org:MAILTO:jwagant...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=agardner@l
 inuxfoundation.org:MAILTO:agard...@linuxfoundation.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-disc...@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, February 14\, 2018 2:30 PM-3:3
 0 PM. UTC\nWhere: zoom.us/j/44 2:30 UTC\n\n*~*~*~*~*~*~*~*~*~*\n\n
 Hi\n\nplease feel free to join on https://zoom.us/j/44\n\nto conti
 nue the discussions on the demo done yesterday and discuss the next steps 
 if any on this proposal\n\nslide deck: https://wiki.onap.org/pages/viewpag
 e.action?pageId=6593670=/6593670/25433913/integration_demo_E2E_cha
 in.pdf\n
SUMMARY;LANGUAGE=en-US:[ONPA] [Integration] test API/Reporting integration 
 chain follow-up (ad-hoc meeting)
DTSTART;TZID=Romance Standard Time:20180214T153000
DTEND;TZID=Romance Standard Time:20180214T163000
UID:04008200E00074C5B7101A82E00824084E026FA5D301000
 0100012BBB2F8975A9F4E9BC963840632832F
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180214T083712Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:zoom.us/j/44 2:30 UTC
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116187428
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #52001] [ONAP] need a VM for integration reporting aggregation

[morgan.richomme]

Hi Jess

hmm, I showed in a demo yesterday that it was relatively easy to adaptable to 
ONAP :)
see 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670=/6593670/25433913/integration_demo_E2E_chain.pdf
 for details
I rewrote what was needed..

However instead of creating a new resources as I mentioned in my ticket, I 
think it would make sense to reuse existing OPNFV VM.
The VM has still resources, the goal is the same in ONAP and OPNFV, collecting 
cases/results and creating aggreagte view
Moreover the DB backup mechanism is automated (from OPNFV 
http://artifacts.opnfv.org/testapibackup.html)
we could
- add a new DB in mongo
- start a new test API docker (re-use of existing docker) dedicated to ONAP 
connected to this new DB
- start a new reporting docker (adaptation of the existing one, need a repo 
integration/reporting to share the core) adapted to ONAP
- reconfigure the nginx
- confidure a onap.org subdomain integration.onap.org or testresults.onap.org

I still have access to the machine, I can do the 4 first actions quickly...but 
I would need action from your side for the subdomain..

/Morgan


Le mercredi 14 février 2018 à 02:36 -0500, Jessica Wagantall via RT a écrit :
Dear Morgan,

I was talking today with Aric about this (since he has seen this working in 
opnfv).
I know from him that this system is not easily adaptable to other projects.

Are you familiar with how this system is developed?

Do you know who can help us rewriting this so that easily adaptable to other 
projects?

Thanks!
Jess

On Mon Feb 05 03:17:16 2018, 
morgan.richo...@orange.com wrote:
Hi,

would it be possible to get IT resources to host ONAP integration
results.
The idea is to collect test results from the different CI chains and
provide an aggregated view of the results (referencing jenkins runs on
different labs with different installers, on different versions
(Amsterdam, Master (Beijing),..).
It is an adaptation of what is currently done in OPNFV
(http://testresults.opnfv.org/).
The most straight forward way would be
- duplication of the testresults.opnfv.org VM managed by Linux
Foundation (nginx, docker APi, docker reporting, mongo DB, git, would
be preinstalled)
- configuration of testresults subdomain for onap main domain to point
testresults.onap.org to the IP of this duplicated VM

I would make some cleaning on the duplicated VM
- clean several accounts used in OPNFV and not needed for ONAP
- dump of the OPNFV DB
- creation of ONAP DB (installers: OOM, Heat; test cases: Functional
test cases (robot, vFW, vLB,), benchmark ..)

We should also re-use the existing jenkins Jobs in order to sync the
deployement of the dockers, backup the DB from ONAP main CI

If it is not possible to duplicate the VM, is it possible to get a
fresh VM
- 2 vCPU
- 80 Go disk
- 8 Go Ram
We could even start smaller if needed, but that is the current sizing
on OPNFV side and we had to increase it once (initial sizing was too
small)

I gave a try on my local POD and took some screenshots (attached file)
Please note that Functest here means all the functional testing (no
bijection with the OPNFV functest project) and would leverage the
robot healtcheck as well as automated functional testcases.
Benchmark corresponds to the new benchmark project

I think it is a good example of Xcommunity synergies..

Thanks

Morgan

_

Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les
messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere,
deforme ou falsifie. Merci.

This message and its attachments may contain confidential or
privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have
been modified, changed or falsified.
Thank you.




_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain 

[onap-discuss] [opnfv-tech-discuss] [integration] demo E2E testing & reporting follow-up

[morgan.richomme]

Hi

I uploaded the slidedeck used for the demo
I added some screenshots 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670=/6593670/25433913/integration_demo_E2E_chain.pdf

I got the action point to organize a follow-up on this topic through another 
meeting

I am not sure I have the rights to book a zoom for an ad-hoc session (my 
personnal account allows only 40 minutes sessions)
I tried to ask the question on the IRC chan but it is not very active and I did 
not find any guideline on the wiki (could make sense to add one page).
@Gildas could you help me to book such slot? I could suggest tomorrow or 
Thursday 2h30 UTC (same time than the integration meeting)

Some open questions need LF helpdesks view (see slide "next steps").
BTW I created a ticket to ONAP heldesk on the 5th of February but did not get 
any feedback so far 
(https://rt.linuxfoundation.org/SelfService/Display.html?id=52001)
Did I miss something on the procedure regarding ONAP helpdesk?
Meanwhile I wondered if it would be possible to mutualize things if OPNFV 
community agrees (+Tim, Gabriel, Ray, Heather and Aric in CC)
The testresults.opnfv.org machine could be shared (everything is already there 
DB, dockers, mechanism to backup the DB) and a testresults.onap.org subdomain 
could be easily created (hopefully) and configured
The VM would not suffer...
[morgan@gce-opnfv-sandbox-fbrockners
 ~]$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda1   75G 29G   47G  38% /
[morgan@gce-opnfv-sandbox-fbrockners
 ~]$ free -m
  totalusedfree  shared  buff/cache   available
Mem:   74803118 320 36840403451


/Morgan






Le mardi 13 février 2018 à 16:10 +, Tina Tsou a écrit :
Dear Morgan,

This is Tina Tsou, PTL of Auto Project. I was in Integration Project meeting 
just now. We are interested at your option #1 for the test API: integration 
OPNFV - ONAP.

Would you send the meeting invitation to opnfv-tech-discussion too? So Auto 
participants can join and learn from you.


Thank you,
Tina

On Feb 13, 2018, at 6:38 AM, Roger Maitland 
> wrote:

One clarification on OOM – it’s not a just a deployment tool, it manages the 
entire lifecycle of ONAP as shown in our logo.

Cheers,
Roger



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Tuesday, February 13, 2018 2:41 AM
To: bryan.sulli...@research.att.com; 
opnfv-tech-disc...@lists.opnfv.org
Cc: feng.xiao...@zte.com.cn; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Auto] RE: [opnfv-tech-discuss] [integration] demo 
E2E testing & reporting next Tuesday?

Hi Bryan,

we can discuss it after the demo or offline
As far as I understand Auto is the equivalent of OOM, i.e. a deployment of ONAP 
based on kubernetes (but Auto is on OPNFV side) - do not hesitate to correct me 
if I am wrong
it would be possible to indicate Auto as 1 of the ONAP installer and collect 
the results of the tests
that is one of the interests to use the test API/Test DB independently from 
jenkins. Several CI chains can push results to provide an aggregate view of E2E 
Functional and later performance testing on ONAP.

and depending on the installer it is possible to customize the test list. For 
example if you have additional test cases through VES or Model projects.
/Morgan

Le vendredi 09 février 2018 à 16:54 +, SULLIVAN, BRYAN L (BRYAN L) a écrit :
Auto team,

FYI in case you have not seen this. Some of you may be collaborating with 
Morgan on the ONAP lab deployment, if not then perhaps there are some 
deployment tools you can leverage, or other ways that Orange can help the Auto 
project get off the ground with ONAP deployment for Auto use case 
development/testing.

For those cc’d who may not yet be aware of the Auto project: 
https://wiki.opnfv.org/pages/viewpage.action?pageId=12389095
Other OPNFV project focused on functional capability / use case testing which 
will support and leverage the OPNFV-ONAP integration through the Auto project 
include VES (https://wiki.opnfv.org/display/ves/VES+Home) and Models 
(https://wiki.opnfv.org/display/models/Models+Home).

Progress toward ONAP-OPNFV integration will also support the OPNFV Lab As A 
Service (LaaS) use cases shown at 
https://wiki.opnfv.org/display/INF/Lab+as+a+Service, which will enable ONAP 
developers to access OPNFV deployed VIM/NFVI environments (and vice versa). 
This and other work in the Models project above will help setup a diverse 
VIM/NFVI environment for supporting 

Re: [onap-discuss] [integration][OpenLab] Orange Open labs +integration repos

[morgan.richomme]

OK let's use this slot

I am not sure to undertand the time table, shall we understand that the meeting 
is planned on Tuesday the 6th 2 PM - 3 PM UTC ? with lots of // meetings? and 
conflict with the integration weekly meeting?

/Morgan

Le mercredi 31 janvier 2018 à 17:11 +0800, Chengli Wang a écrit :
Hi All,

We will have a special LAB topic during next week virtual F2F meeting, would 
you mind use this session to kick off the related discussion?
The event topic linked here, 
https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2017
  we can reserve 60 minutes if needed.

Chengli


在 2018年1月31日，上午2:13，Yunxia Chen 
> 写道：

Hi, Morgan,
That’s the great news. What does Orange lab plan to offer to the community?  
Could you please call a 30 minutes working session to sort this out with the 
following people?
• Chengli Wang
• Rich Bennett
• Gary Wu
• Gildas Lanilis
• Stephen Gooch

They all on the “To” list as well. Let’s not duplicate the content. I am fine 
with either way you guys come out.

Regards,

Helen Chen

From: "morgan.richo...@orange.com" 
>
Date: Tuesday, January 30, 2018 at 8:34 AM
To: "bin.y...@windriver.com" 
>, Kang Xi 
>, Helen Chen 00725961 
>, 
"wangchen...@chinamobile.com" 
>, 
"ran.pol...@amdocs.com" 
>, 
"lxin...@vmware.com" 
>, "ROSE, DANIEL V" 
>, Gary Wu 
>, "Yang Xu (Yang, Fixed 
Network)" >, "PLATANIA, MARCO 
(MARCO)" >, yangyi 
>, 
"spondon...@att.com" 
>
Cc: Eric Debeau >, 
BLAISONNEAU David IMT/OLN 
>, 
onap-discuss >
Subject: [onap-discuss] [integration][OpenLab] Orange Open labs + integration 
repos


Hi Helen



regarding my action point

#AP 4: morgan_orange check with Eric on the Orange Open Lab schedule (when 
could we communicate at teh community level)



I am pleased to announce that the Orange Open Lab will be open on the 14th of 
February after some internal tests currently in progress.



I was wondering if if would make sense to create new repos to manage that

- integration/installation to host heat related activities

- integration/tests to host testing

- integration/infrastructure to manage the different labs

- integration/tooling



Note for the testing part I would even suggest to split it into

integration/functestional_tests (or functest :))

integration/benchmark



having only 1 repo will be misleading

If so my colleague David could push the code we are currently using to automate 
the creation of accounts for remote access (ansible roles) to an ONAP rebound.

And I assume it will be also the right place for Tlab owner to share stuff.



is it also up to the integration project to manage the federation of labs, as 
far as I understand there is also a comittee dealing with that?

if so I would suggest to reference somewhere (in integration/infrastructure for 
example) the IPs of the different labs

in order to easily tune the FW rules and let ONAP open lab discuss one with the 
others.

May I add a topic on this for next week?



/Morgan

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this 

[onap-discuss] [integration][OpenLab] Orange Open labs + integration repos

[morgan.richomme]

Hi Helen


regarding my action point

#AP 4: morgan_orange check with Eric on the Orange Open Lab schedule (when 
could we communicate at teh community level)


I am pleased to announce that the Orange Open Lab will be open on the 14th of 
February after some internal tests currently in progress.


I was wondering if if would make sense to create new repos to manage that

- integration/installation to host heat related activities

- integration/tests to host testing

- integration/infrastructure to manage the different labs

- integration/tooling


Note for the testing part I would even suggest to split it into

integration/functestional_tests (or functest :))

integration/benchmark


having only 1 repo will be misleading

If so my colleague David could push the code we are currently using to automate 
the creation of accounts for remote access (ansible roles) to an ONAP rebound.

And I assume it will be also the right place for Tlab owner to share stuff.


is it also up to the integration project to manage the federation of labs, as 
far as I understand there is also a comittee dealing with that?

if so I would suggest to reference somewhere (in integration/infrastructure for 
example) the IPs of the different labs

in order to easily tune the FW rules and let ONAP open lab discuss one with the 
others.

May I add a topic on this for next week?


/Morgan

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP] [Benchmark] questions

[morgan.richomme]

Hi,

I had a look at the page https://wiki.onap.org/display/DW/ONAP+Benchmark
I have some questions.
What kind of framework do you plan to use? leverage?

I was involved in OPNFV functional testing and in OPNFV testing group where we 
worked on these issues.
Do you know the OPNFV testing ecosystem? 
http://docs.opnfv.org/en/stable-euphrates/testing/ecosystem/overview.html
Benchmarking (of the infrastructure) was split into several testing sub 
projects to address different aspects (storage, hardware, network, compute)

I had in mind to reuse Functest framework for ONAP as soon as the automation of 
the installation would have been stabilized a little bit more...
I think that the Yardstick or Bottlenecks framework could also be used for ONAP.
Lots of benchmarking tools are already integrated in a consistent way using 
docker containers including collection of results (Test DB, Test API), 
integration in CI, analytics (using ELK)

The functest framework has been used for 4 years and is usable to onboard VNFs 
such as vIMS or very recently vEPC using different orchestrators (CI runs every 
day).
ONAP would be one of them (we already had tests witjh Open-O before it was 
merged with Ecomp).
I believed it would be nice to onboard the current ONAP test cases (vFW and 
vCPE)
The centralized DB + associated Test API is also for me very valuable for the 
community and provide a good visibility on the tests. We use it for our CI and 
for plugfests.

I would be happy to contribute to benchmark project on these aspects.
Would it make sense to organize a session to describe the different framework 
in OPNFV and/or plan a XCommunity meetingn?

Regards

Morgan



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration] Integration Weekly Meeting

[morgan.richomme]

MoM: 
http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2017/onap-int.2017-12-06-14.33.html
please fell free to froward to onap mailing list if you want
As you can see there is no action point, but usually there are, and we start 
the meeting by the follow-up of such action points
there is no way to force people to work, but when they have precise action 
point in public minutes meeting, it can be motivating...

according to me, such minutes are much easier to read than watching a video
it allows to follow offline (when timetable is not reasonable for attendees)
it gives an history of the progress
most of the Open Source communities are using it

/Morgan

Le mercredi 06 décembre 2017 à 06:46 +, Yunxia Chen a écrit :
[integration] Integration Weekly Meeting
Lieu : https://zoom.us/j/44
Heure de début : Aujourd’hui 15:30
Heure de fin : Aujourd’hui 16:30

When: Wednesday, December 06, 2017 6:30 AM-7:30 AM. (UTC-08:00) Pacific Time 
(US & Canada)
Where: https://zoom.us/j/44

*~*~*~*~*~*~*~*~*~*


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] integration jenkins

[morgan.richomme]

Hi,

we shared a presentation last week by mail on our goal regarding ONAP CI/CD in 
Orange labs.
It seems that we have common goals.. :)
We planned to present it during the integration meeting this week

We connected to the weekly meeting on Tuesday but it seems it was neither the 
right time nor the right place
Could you confirm that the integration weekly meeting takes place on Tuesday 2 
PM UTC - (title of the wiki page not up to date as 2 PM UT is now 6 AM PST not 
7) or on Wednedsay 2:30PM UTC (first line) 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670
Where can we see the agenda and the IRC meeting minutes of the previous 
meetings? I can see only video in the minute page.

Our goal is to setup a CI/CD chain in our lab for the community (connected to 
LF Jenkins) where we would like to daily automaticallly:
- deploy an ONAP master version on a bare metal infra / HA mode
- run tests module by module (current robot healthchecks)
- run E2E tests (vFW, vWhatever,...)
- report status

we already have an internal beta CI/CD chain (OPNFV XCI / Kolla HA on 5 servers 
(3 control and 2 compute nodes) - ONAP/Heat )
David who is involved in OPNFV XCI will show it during the OPNFV plugfest next 
week in Portland

/Morgan

Le vendredi 01 décembre 2017 à 06:05 +, Guo, Ruijing a écrit :
Hi, Helen

I am trying to automate ONAP installation including VNFs in one box.
The installation can be for demo, integration or code dev/debug.
The code is in http://gerrit.onap.org/r/demo/vagrant.


1.  Install openstack in 4 VMs (1 openstack controller, 2 openstack 
compute, 1 onap)

2.  Install ONAP by openstack heat

3.  Launch VNFs ( Not yet)

4.  Run closed-loop (Not yet)

There are 2 issues here:

1.  Docker pull in VM is slow ( I found the root-cause now)

2.  ONAP Heat was updated  ( I think it is stable now)

I am trying to leverage your knowledge to complete step 3 & 4.

Thanks,
-Ruijing

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Thursday, November 30, 2017 10:57 AM
To: Guo, Ruijing 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] integration jenkins

Hi, Ruijing,
We don’t have a Jenkins for vCPE or VoLTE yet. Our plan is to do it at Beijing 
release for vFW/vDNS, and vCPE after we automate all steps for testing vCPE.

Regards,

Helen Chen

From: "Guo, Ruijing" >
Date: Wednesday, November 29, 2017 at 6:50 PM
To: Helen Chen 00725961 >
Cc: onap-discuss 
>
Subject: [onap-discuss] integration jenkins

Hi,  Helen

I am looking for document & Jenkins log to setup closed-loop demo
Did your team setup integration Jenkins for vCPE and VoLTE case?
Where is Jenkins setup code & Jenkins URL?
I just know https://gerrit.onap.org/r/demo & 
https://gerrit.onap.org/r/integration

Thanks,
-Ruijing

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] information on contributors and committers in repo

[morgan.richomme]

Hi

I wonder if it would not be helpful for the whole community to manage 
the list of project contributors and commiters in the repo.


in OPNFV we got an INFO file when we list the people. See example for 
one of the project here: https://git.opnfv.org/functest/tree/INFO


in this file we got the list of committers (with +2 right) the regular 
contributors (+1), the IRC, the JIRA, ...


We use this file as reference when we need to promote 
(https://wiki.opnfv.org/display/DEV/Committer+Promotions) or when a 
contributor/commiter is leaving.


At the moment I can see that such information is sometimes available in 
the wiki, but it probably corresponds to the status at the creation of 
the project, not necessarily the current situation.


Wikis are hard to maintain in a proper way. Using git/gerrit is cleaner.

This information is important when you are new on the project especially 
to know who could reasonably review your patch.


Of course you can filter on gerrit but if all the projects adopt this 
description file it is easier for newcomers.


/Morgan





_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] When is the documentation project meetings?

[morgan.richomme]

<<< text/html; charset="utf-8": Unrecognized >>>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [OPNFV] [testing group] feedback on automation of stress test on OPNFV vIMS Functets test case

[morgan.richomme]

Hi,

during the 31st of August OPNFV weekly Testing group meeting  (3PM UTC, 
https://global.gotomeeting.com/join/819733085, #opnfv-testperf), we 
planned to share our feedback on the automation of vIMS stress test on 
OPNFV solution.


This work has been initiated during the last OPNFV plugfest in Paris 
(stress test) and has been finalized end of July (automation of the 
stress test for CI).


Based on the existing cloudify_ims test case (automation of 
cloudify/clearwater + signaling testing) developed by Valentin and 
automated since Brahmaputra, we are now able to generate realistic 
signaling load (more than 100.000 calls within 10 minutes) using Ixia 
loader.


Please note that tests have been executed on Orange OPNFV community lab 
including power consumption monitoring also introduced during last plugfest


The presentation will deal with:
- reminder on cloudify_ims test case
- Introduction of the new stress test
- Automation of this test
- Conclusions
- Q

Feel free to invite whom it may concern
Testing group meeting are open

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss