Re: [opnfv-tech-discuss] [release][gambia] MS2 - Test case documentation in the test case database - May 25

hi I think you need to contact Dovetail project. As far as I know, the token API has been introduced to secure the reporting for dovetail. Serena should have the best view on this topic now. /Morgan Le mardi 29 mai 2018 à 10:46 +0200, ollivier.ced...@gmail.com a écrit : Hello David, Functest

Re: [opnfv-tech-discuss] Functest reporting page 404

as far as I can see a new reporting docker has been generated 50 hours ago introducing a regression the menu page functest.html (status / vIMS / Tempest) is not copied in the different version directories (fraser/master/..) all the other pages were still propertly generated

Re: [opnfv-tech-discuss] [OPNFV] [Fraser] Fraser Functest run on Orange ONAP Open lab

Hi, I will modify our CI chains in order to alternate check with fraser / master and keep on providing feedback. We may change the config to make the dashboard publically available After one week of perfect runs (last week), we started getting some errors.. api_check / refstack / tempest /

[opnfv-tech-discuss] [OPNFV] [Fraser] Fraser Functest run on Orange ONAP Open lab

Hi for information, we switched to the fraser version for our daily test on our ONAP OpenLab, a communit lab for ONAP users. Even if the lab is used by ONAP contributors for ONAP testing, we are reusing Functest test suites to be sure that the infrastructure supporting ONAP is still properly

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

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

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

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

Re: [opnfv-tech-discuss] [Functest] PTL transfer

<<< text/html; charset="windows-1252": Unrecognized >>> ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][euphrates] recommended list of scenarios for release in Euphrates 5.0

Hi, I fully support Jose's comments "I've been told (a) the test frameworks are not sufficiently mature to be used for gating release; and (b) the community prefers to leave the decision about quality to the scenario owners. So, we are left with (1) deploy status; and (2) scenario owner

[opnfv-tech-discuss] [OPNFV] xci /functest

Hi we made some tests using Functest (opnfv/functest-healthcheck and functest-smoke - eupĥrates) on xci-baremetal in our labs. we have reproducible results and would like to discuss with xci group I did not see xci/functest recent logs on our Jenkins, do I miss something? As far as I

Re: [opnfv-tech-discuss] Releasing OPNFV tools in Euphrates

Agree to extend to mailing list :) just to summarize, we started the discussion on doc for calipso for Euphrates, it triggered discussions more general topics including - a topic on how to include NFVBench in Euphrates (Operation/testing) - a discussion on OPNFV release / tooling release

[opnfv-tech-discuss] [OPNFV] [testing group] landing page: score and trust indicator

Hi we initiated the landing page some time ago: http://testresults.opnfv.org/testing/#!/landingpage/table front and back end are now ready Jack started doing an update for Yardstick It is now possible to call the Test API to set a score and see/modify trust indicator after a CI run. during

Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test results dashboard

Hi functest reporting shows what it is in test DB if you see odl_l3, it means that odl_l3 scenarios have been triggerred over the last 10 days in CI https://build.opnfv.org/ci/view/functest/job/functest-fuel-armband-virtual-daily-master/31/console if only odl scenario are triggereg,

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

Hi, thanks Wenjing! I unfortunately cannot accept the nominations. There are currently some internal reorganization on my side (as in LF networking projects...) preventing me to be fully involved in OPNFV after Euphrates, which is a prerequisite to apply for these positions. /Morgan On

[opnfv-tech-discuss] Illustration for landing pages

Hi Brandon do you think LF design team could create 2 illustrations for 2 landing pages where we have OPNFV resources - one for the testing landing page (submenu: reporting, dashboarding, testAPI, test DB,..) - one for the VNF kanding page (submenu: catalog) note that we already integrated

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

Hi I would like to nominate Gabriel Yuyang (Huawei) for the TSC Committer-at-Large election. Gabriel is the Bottlenecks PTL. He is an active member of the Testing working group. He is a leader on on the long duration/stress/robustness/resiliency testing activities that will be key in the

[opnfv-tech-discuss] [OPNFV] url changes on testing group reporting pages

Hi for information, we modified the test reporting configuration on testresults.opnfv.org. The target based on docker is now available under http://testresults.opnfv.org/reporting/ (previously reporting2). Note that Vsperf has been added recently on master

Re: [opnfv-tech-discuss] [FuncTest] Test Database Swagger URI changed?

credentials are no more public access is for OPNFV PTL I sent you the info directly On 31/08/2017 21:18, Bryan Sullivan wrote: The testresults DB password seems to have changed. The value on the wiki @ https://wiki.opnfv.org/pages/viewpage.action?pageId=6828013

[opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

Hi, 2 pending questions regarding the way we are managing our docker files 1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest Docker repositories) in order to create new docker repositories: opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf As it

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] Milestone 6 - August 25

Hi David for Functest - healthcheck/smoke tests running on the master branch for the 5 installers. Still troubleshooting to do of course http://testresults.opnfv.org/reporting2/display/master/functest/status-apex.html

Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

the trend line can cover a long period, it is based on the local file storing all the results but a trend line is associated with a scenario and the list of scenarios is built based on the results over the last 10 days that is why if there is no run since 10 days, we have an empty page In deed

Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

regarding the reporting link, it always deals with a sliding windows processing the results from the last 10 days if no results since 10 days for the given version => no results so currently no Danube results, some runs on master =>

[opnfv-tech-discuss] [OPNFV] testing group - testing ecosystem for Euphrates

Hi The testing group started discussions on documentation for Euphrates. One of the key asset is the graph of the ecosystem: http://docs.opnfv.org/en/stable-danube/_images/OPNFV_testing_working_group1.png This figure provides a synthetic view of the test projects involved in a release and has

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

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

Re: [opnfv-tech-discuss] Interested in joining the opnfv community

Hi, OPNFV is an open community, everybody is welcome to contribute The only prerequisites is the Linux Foundation account see https://wiki.opnfv.org/display/DEV/Developer+Getting+Started https://wiki.opnfv.org/display/DEV/Developer+On-boarding /Morgan On 22/08/2017 11:03, Sreeramachandra

[opnfv-tech-discuss] [OPNFV] follow-up vIMS load test automation initiated during last plugfest

Hi, End of July, Valentin (Orange) and Arturo (Ixia) finalized the automation of load test using Ixia loader based on cloudify_ims testcase. This work was initiated during the Plugfest in Paris. So far, the cloudify_ims was dealing with 3 steps - deployement of cloudify (orchestrator

Re: [opnfv-tech-discuss] [ONOSFW] Functest CI on ARM pods

Hi, as far as I understand, what you want is an onos scenario on ARM in CI. Functest tests are triggered according to the installer and the scenario today ONOS specific tests are defined as |case_name: onos project_name: functest criteria: 100 blocking: true description: >- Test Suite for the

[opnfv-tech-discuss] [OPNFV] Copper, Opera (and Multisite, Netready) status for Euphrates (Functest integration)

Hi, as Functest is currently integrating the feature projects - see several pending patches including a better control of the requirements, I had questions on the status of some feature projects that used to be integrated in Functest in previous versions according to

[opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

Hi, I did not find the list of the target versions for the main components integrated in Euphrates version. it would make sense to explicitely reference them on one of the wiki pages dedicated to the release https://wiki.opnfv.org/display/SWREL/Euphrates In functest, we need to know it.

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

I will be in PTO too :) Unfortunately the weekly meeting was today at 8 UTC (APAC slot) we will use the slot of tomorrow to organize an ad-hoc meeting with Bitergia on result vizualization not sure we will have 15 minutes for another topic It is maybe possible to organize an ad-hoc meeting on

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

topic added for the next meeting (20th of July) https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting Mark and Jose are already involved in several activities dealing with docker. Cedric has a good view on this topic. /Morgan On 12/07/2017 17:27, Alec Hothan (ahothan)

[opnfv-tech-discuss] [OPNFV] [Infra] [Testing) Stress/resiliency Testing evolution in OPNFV (draft)

Hi Infra group, I got an action point this afternoon during the TSC meeting after the presentation on the behalf of the testing working group on our vizion of test evolution (https://wiki.opnfv.org/download/attachments/9568526/testing%20evolution%20v1_3.pptx?version=2=1499788745000=v2) We

[opnfv-tech-discuss] [OPNFV] Testing group weekly meeting

Hi reminder: this week => APAC meeting on Wednesday we keep however the Thursday slot for an adhoc meeting with Bitergia see agenda https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting /Morgan

Re: [opnfv-tech-discuss] Including externally licensed code

Hi, chartjs is under MIT license so no compatibility issue with the default apache 2.0 I think both options are possible but if you clone it in your repo, I would suggest to create a 3rd-party directory to separate internal code from 3rd party code (e.g.

Re: [opnfv-tech-discuss] [opnfv-tsc] [dovetail] TSC and DoveTail meeting to discuss scope and needs for CVP testing

Hi, my view is that the difficulty we have to converge to a clear consensus is directly linked to what we are producing I fully agree with Fatih's comment on the mail https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-June/016799.html Second release had probably the best quality in

Re: [opnfv-tech-discuss] TSC vote requested for security fix

+1 no preference Morgan On 21/06/2017 06:54, Stuart Mackie wrote: +1 - Either Stuart -914 886 2534 *From: * on behalf of Raymond Paik *Date: *Tuesday, June 20, 2017 at 3:07 PM *To: *"opnfv-...@lists.opnfv.org"

Re: [opnfv-tech-discuss] [vsperf] Survey of VSPERF Users and Contributors

Hi see answers below /Morgan On 19/06/2017 18:22, Cooper, Trevor wrote: I am collecting feedback about VSPERF from users and contributors … the main purpose is to help me motivate for our ongoing investment in the project. I already approached a few people … even if you have already given

[opnfv-tech-discuss] RE : SFC functionality test

Hi BuildTag is used to push the result in the test DB in CI mode. The info that it is missing is printed as INFO so there is no problem on this side Regarding the logs I would suggest to have a look at the logs in /home/opnfv/functest/results/sfc.log Morgan Envoyé de mon Galaxy Note 4

[opnfv-tech-discuss] RE : Vote for the new Danube 3.0 release date

+1 Envoyé de mon Galaxy Note 4 d'Orange Message d'origine De : Raymond Paik Date : 08/06/2017 09:05 (GMT+08:00) À : opnfv-...@lists.opnfv.org Cc : opnfv-tech-discuss@lists.opnfv.org Objet : [opnfv-tech-discuss] Vote for the new Danube 3.0 release

[opnfv-tech-discuss] RE : proposed delay to Danube 3.0 release

No objection from my side Morgan Envoyé de mon Galaxy Note 4 d'Orange Message d'origine De : "HU, BIN" Date : 07/06/2017 11:38 (GMT+08:00) À : Ray Paik , David McBride Cc : TSC OPNFV

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #41190] [linuxfoundation.org #41190] Re: [opnfv-tsc][test-wg][yardstick] Yardstick New PTL Election Done

congratulations to Kubi and Ross! Great work, Yardstick is a key project for telco Cloud. All the best for Euphrates and the next rivers... /Morgan De : opnfv-tech-discuss-boun...@lists.opnfv.org [opnfv-tech-discuss-boun...@lists.opnfv.org] de la part

[opnfv-tech-discuss] [OPNFV] [Fun] [DIY] OPNFV trender / IoT to get Jenkins status

Hi, I documented the procedure to create little objects (called Trender in our Fablab) to visualize OPNFV Jenkins status Trender-opnfv.png You will find the laser cutter rld file as well as the code http://wiki.fablab-lannion.org/index.php?title=Trender_OPNFV enjoy /Morgan

[opnfv-tech-discuss] [OPNFV] testing working group - test case domain definition

Hi I refactored the testing working group page (update figures, logos, unreference old discussions from the main pages) feel free to give your feedback and modify/correct/complete We discussed during the plugfest on the fact that we should update the description of our test cases in the

Re: [opnfv-tech-discuss] [test-wg] [yardstick] Yardstick PTL Election

"Be a yardstick of quality. Some people aren't used to an environment where excellence is expected" S.Jobs Thanks to you and the yardstick team, more and more people are used to it. Thanks for everything: great job from a great PTL! Morgan Le 05/05/2017 à 14:43, Gaoliang (kubi) a écrit : > >

[opnfv-tech-discuss] [OPNFV] Split of releng repo?

Hi I think we already initiated this discussion some times ago but would it make sense to split releng repo into releng-jjb and releng-utils as there are at least 2 very different areas (jenkins and Xproject tooling/lib) /Morgan

Re: [opnfv-tech-discuss] [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Thnaks Trevor I added some points that reflect the notes for the next test weekly meeting planned on the 4th of May: https://wiki.opnfv.org/display/meetings/TestPerf feel free to add additional points I will not be able to join this time, could you chair the meeting? /Morgan Le 28/04/2017 à

Re: [opnfv-tech-discuss] [functest] Security Scanning

Hi Luke let's discuss it during the plugfest /Morgan Le 03/04/2017 à 18:35, Luke Hinds a écrit : > Hi Functest'ers, > > I am aware I have not been as active on security scanning as I > originally hoped, largely due to being v-busy working on upstream. I > have also not seen much uptake in

Re: [opnfv-tech-discuss] [FUNCTEST] [SNAPS-OO] Danube release

for Danube, it could somehow be considered as a part of Functest (it is documented in Functest) it fully make sense to branch it if it would have been a cable labs external lib, we would have probably used a git commit id to fix the version, keep it simple and branch... for the next releases,

[opnfv-tech-discuss] [OPNFV] minutes weekly meeting 410/03

http://irc.opnfv.fr/opnfv-orange/2017/opnfv-orange.2017-03-10-10.01.html - Note 1: etherpad available to collect ideas/sync proposals for the Beijing Summit (deadline March 27th) http://etherpad.rd.francetelecom.fr/p/CfpBeijing @Eric I put your proposals here @Ruan => your demo will be in the

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

I do confirm most of the Fuel scenarios seem OK from a Doctor point of view now :) However Doctor is still FAIL on Apex and Joid scenarios and is not run on Compass for Danube do you plan any restrictions on some installers? /Morgan Le 06/03/2017 à 15:11, Ryota Mibu a écrit : > Morgan, > > >

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

cool wait for CI to work, the weather shall become sunny in many scenarios /Morgan Le 06/03/2017 à 15:11, Ryota Mibu a écrit : > Morgan, > > > Thanks! Now, we got "OK" for doctor test in functest daily job. > >

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

Hi Ryota, when we produce Functest docker, we are currently cloning the Doctor master repo the last Functest docker has been successfully produced 1 h ago (started at at 6:10 - Jenkins Time) - previous one was produced on the 3rd of March so I assume your changes are taken into account since this

Re: [opnfv-tech-discuss] [OPNFV] [Danube] [Documentation] Organization of testing section

yes see minutes http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2017/opnfv-testperf.2017-03-02-15.00.html docs ├── release │ └── release-notes └── testing ├── developer └── user see https://git.opnfv.org/functest/tree/docs as an illustration and for the title (not written

Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

Gabriel and Kubi made an update recently on 2 stress tests that should be defined/available/documented for Danube https://wiki.opnfv.org/display/meetings/TestPerf?preview=/2926539/9568872/Stress%20Testing%20Update.pptx

Re: [opnfv-tech-discuss] [OPNFV] [Danube] [Documentation] Organization of testing section

And just to precise - the last table from my first mail could be mlisleading (we will exchange tomorrow during the weekly meeting) you shall now create a docs/testing directory reflecting the target view and put your docs there (as shown in Jose's patch) in your repo docs ├── release │ └──

[opnfv-tech-discuss] [OPNFV] [Danube] [Documentation] Organization of testing section

Hi, during the last release meeting we had a discussion on the structure of the testing documentation for Danube we suggest to adopt the following approach for the test projects |/docs| ||_ release| |...| | |_ release-notes // release note of the projects involved in the release| |

Re: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

Hi Sofia For Danube, the testing group initiated an umbrella doc, currently hosted in opnfvdocs/docs/testing/ecosystem is it OK? Morgan Le 07/02/2017 à 15:49, Sofia Wallin a écrit : > > Hi Gerald, > > The documentation is divided into 3 different entry points/areas so > the structure will

Re: [opnfv-tech-discuss] [functest][apex] functest container not updating

Hi Tim in theory no...it is done automatically the docker integrating your patch has been successfully produced https://build.opnfv.org/ci/view/functest/job/functest-docker-build-push-master/883/ several latest Functest docker have been produced meanwhile

[opnfv-tech-discuss] [OPNFV] Infra/testing group crossover

Hi during past testing weekly meeting, several topics involving infra and testing were discussed - bitergia/dashboard: bitergia is already dealing with infra group (jenkins tab) and will soon also be involved with testing community (producing graph by consuming existing test API) - feedback/best

Re: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Le 27/01/2017 à 18:49, Wenjing Chu a écrit : > > I agree more information is better, however it is not obvious where > that information will come from. > > > > -Test case run result history > > Do we keep records of old runs in Colorado for functest & yardsticks? > If we do, let’s link

[opnfv-tech-discuss] [OPNFV] Danube community priorities

Hi please find attached the pdf discussed on community priorities for Danube by the TSC: https://wiki.opnfv.org/display/SWREL/Danube+priorities In the first part we tried to indicate the main achievements of the first OPNFV versions and indicate some metrics. In the second part we tried to

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

Le 18/01/2017 à 11:07, Tapio Tallgren a écrit : > Good topic, I also felt that the criteria were not too clear. > > My interpretation was that if we are testing a feature that should be > in all OPNFV platforms and which is generally available in the > industry, and which does not require a

[opnfv-tech-discuss] [OPNFV] VNF on boarding: Q Functest versus orchestrator projects

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

Re: [opnfv-tech-discuss] [OPNFV] [FUNCTEST] [Danube] VNF OnBoarding

Hi Guiseppe I think I got your point As you mentioned we should differentiate 2 things - VNF onboarding: testing the capability to deploy a VNF with or without an orchestrator and test the VNF - Mano stack validation see as a feature available in scenario(s) the proposal was related to the first

Re: [opnfv-tech-discuss] [OPNFV] [FUNCTEST] [Danube] VNF OnBoarding

Thaj & Leibo added to patch review (@Yang Yu, I did not find you in gerrit) do not hesitate to comment the review and/or contact us if you have any quesiton /Morgan Le 06/01/2017 à 19:53, Yingjun Li a écrit : > Add Thaj, Yang Xu and Leibo from OPERA team to the list. They are preparing > vIMS

Re: [opnfv-tech-discuss] [FuncTest] Test Database Swagger URI changed?

Serena fixed the issue Probably bad config introduced by an update 3 weeks ago (and I am probably the one to blame...) /Morgan Le 03/01/2017 à 17:45, SULLIVAN, BRYAN L a écrit : > > Hi all, > > > > I tried to verify the API URL >

[opnfv-tech-discuss] RE : Help - First Patch - Gerrit Upload Denied Error

If it is a first patch, you needed to be declared in a DB (even if you already signed the CLA) You may ask Copper or Releng PTL or contact the help desk (in copy) Once done you will be able to commit patches in a any project /Morgan Envoyé de mon Galaxy Note 4 d'Orange Message

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

cool thanks Yujun Le 15/12/2016 à 14:05, Yujun Zhang a écrit : > Hi testers, > > I have replaced the previous image of TestPerf EcoSystem with an > editable diagram in the overview section of testperf wiki page[1]. > Please review and amend if something is missing. > >

Re: [opnfv-tech-discuss] committer list maintainance

in line with Yujun no need to attend TSC to remove non active committers usually we can do it through a patch of INFO file the only case I can see a need to attend TSC is in case of conflict but I never saw that so far during OpenStack Barcelona, we mentioned that it would be also nice to

Re: [opnfv-tech-discuss] [functest][apex] New smoke tests in master verify

Le 13/12/2016 à 02:30, Tim Rozet a écrit : > Hi Morgan, > Thanks for the patch to move those tests. Also it is great to see the > integration of Steve's framework! > > On our latest verify we see that it is still running those tests. Is that > because we have to wait for a new functest

Re: [opnfv-tech-discuss] [functest][apex] New smoke tests in master verify

Hi Tim, api_check is part of new SNAPS tests (framework developed by Steve and integrated in Danube) - 2 in healthcheck: connection_check and api_check - 1 in smoke: snaps_smoke we integrated them end of next week, it seems that we need to troubleshoot a little bit :) we had a discussion on the

Re: [opnfv-tech-discuss] [Yardstick] Agenda for Yardstick meeting 13 Dec

Hi Ok let's discuss it during next meeting we have already something in Functest so we should take care not bringing confusion here an earlier discussion said that VNF onboarding could be done in Functest (as we have the vIMS and should have additional ones for Danube) based on that, Yardstick

Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

+1 for UTC /Morgan Le 05/12/2016 à 10:11, Kunzmann, Gerald a écrit : > > Hi everyone, > > > > Independent on which timezone we use, this will result in conflicts in > some regions. I agree with Bob that for US/EU this would mean a shift > in meeting time for months and might lead to meeting

[opnfv-tech-discuss] RE : [Functest] [Yardstick] Test Results API (testresults.opnfv.org/test/api) Documentation

Do not hesitate to use the swagger interface described in http://artifacts.opnfv.org/functest/docs/devguide/index.html There are discussions on the etherpad on the evolution of the data model, feel free to contribute /Morgan Envoyé de mon Galaxy Note 4 d'Orange Message d'origine

[opnfv-tech-discuss] [OPNFV] Danube ( and beyond) community priorities

Hi, There is a discussion at the TSC on the need to define community priorities for the next versions. An etherpad has been created to collect community views: https://etherpad.opnfv.org/p/CommunityGoals As mentioned in the pad the goal is not to create artificial competition between projects

Re: [opnfv-tech-discuss] [opnfvdocs] documentation landing page

+2 short way: redirection docs.opnfv.org to http://artifacts.opnfv.org/opnfvdocs/colorado/docs/documentation/index.html to be done, I think we can send a ticket to helpdesk but then only colorado will be referenced mid way: we can also reuse the structure done for test reporting

Re: [opnfv-tech-discuss] Kicking off nominations for Q3'2016 OPNFV Quarterly Awards

Hi, * Code development: Serena Feng (ZTE) for her work on the refactoring ot the test api. She consolidated the code, developped the swagger documentation part for Tornado (the python web server we are using), dockerize it, add function for upgrade of the mongo DB, backup, add

Re: [opnfv-tech-discuss] Interpretation of yardstick test results

Hi, I think the question was already asked in Brahmaputra :) We got an update on grafana last week but it was more on the capabilities of the tools than on the interpretation of the results. I think we should clearly have a discussion on this topic. It is probably complex to define thresholds =

[opnfv-tech-discuss] [OpenStack Summit] [OPNFV] Functest@OpenStack Summit Barcelona

Hi, I started looking at Barcelona planning. I already planned - 25/10 2-5PM: Functest meetup - draw Danube roadmap (note: another meetup is planned in Lannion (France) on the 14th to prepare this one) - 26/10 3.05PM-3:45: presentation on OPNFV/Functest/vIMS with gigaspace - 27/10 2-4PM:

[opnfv-tech-discuss] Notice of intent to participate in OPNFV Danube release

by these presents you are notified that the Functest project intends to participate in the Danube release. /Morgan _ Ce message et ses pieces jointes peuvent contenir des

[opnfv-tech-discuss] [OPNFV] [functest] [D release]

Hi based on the discussion initiated during last Functest weekly meeting, I created the Danube page for the project. https://wiki.opnfv.org/display/functest/Functest+Danube as mentioned in the beginning of the page, this page is a draft The goal is to collect element to prepare the D

Re: [opnfv-tech-discuss] Labelling your Colorado repo for the release.

Done for Functest Le 22/09/2016 à 14:11, Gray, Mark D a écrit : > > Done for ovsnfv. > > > > *From:*opnfv-tech-discuss-boun...@lists.opnfv.org > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of > *Christopher Price > *Sent:* Wednesday, September 21, 2016 6:24 PM > *To:*

[opnfv-tech-discuss] [Functest] Project organization

Hi, as discussed quickly this morning during our weekly meeting, I would like to plan the next Functest PTL election. My idea for Functest is to call for PTL election every 2 releases. The PTL will thus be legitimate by the core developpers, it should help reflecting the diversity within the

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule

OK but in this case we need to have CI for the release and CI for the master, which is not the case today for all the installers As said, the only argument for me to branch is to be able to break master before going to release gate and then secure the release but today, in some cases we do not

[opnfv-tech-discuss] Functest meetup poll

Hi, I would like to organize a Functest meetup Europe. For Colorado, the event was kindly hosted by Nokia in Finland, Orange will be very happy to welcome the participants in Lannion (Brittany) - 1h flight from Paris, 15 minutes from the coast

Re: [opnfv-tech-discuss] [opnfv-tsc] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

ok I move to the 29 no problem Morgan Le 13/09/2016 à 15:37, Carella, Giuseppe a écrit : > Hi Morgan, > > next week I’ll be at NFV#15, the week after would be better for me. > > Cheers, > Giuseppe > > Join us at the IEEE 5G Week in November in > Berlin (http://www.berlin5gweek.org/) > >> On 13

Re: [opnfv-tech-discuss] [opnfv-tsc] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

Hi I put this point to the agenda of the meeting planned on the 22nd of September (2PM UTC) https://wiki.opnfv.org/display/meetings/TestPerf I planned 20 minutes, is it OK? * *IRC channel:* |#opnfv-testperf| @ Freenode * Join the

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule

Hi +1 / Frank branching make sense for // development and probably for feature development but for integration/testing, we saw in Brahmaputra and in Colorado that we systematically cherry pick the only argument could be that we cherry pick with delay (1-2 days), so we check first on master then

Re: [opnfv-tech-discuss] [opnfv-tsc] Nomations for the 2016 OPNFV Committer Board Election

Uli, Tapio thank you very much for the nomination. It is with regret I must decline due to new commitments in TSC I would like to back the nominations for Chris Price even if I would like to convince him to stay as TSC chair... /Morgan Le 13/09/2016 à 10:32, Tallgren, Tapio (Nokia - FI/Espoo) a

Re: [opnfv-tech-discuss] [opnfv-tsc] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

Hi, it is a task identified in Functest for D I created an internship proposal (see Title: Open Source VNF catalog inhttps://wiki.opnfv.org/display/functest/Functextnexttaks ) on this topic Bertand got the green light to be a co-mentor so we will publish it soon (this morning) One of of our goal

Re: [opnfv-tech-discuss] Shout out: Julien Zhang

+1 Le 18/08/2016 à 00:31, Jack Morgan a écrit : > OPNFV, > > I would like to take a moment to recognize Julien Zhang for his hard > work and dedication during this Colorado release cycle. I really > appreciate his input even though I as the Pharos PTL didn't provide much > direction. Julien worked

Re: [opnfv-tech-discuss] [RELENG] Vote to make Trevor a submitter on releng.

+1 Le 27/07/2016 02:58, Meimei a écrit : > +1 > > > 在 2016/7/22 5:42, Jose Lausuch 写道: >> +1 >> >> -Original Message- >> From: Aric Gardner [mailto:agard...@linuxfoundation.org] >> Sent: Thursday, July 21, 2016 20:05 PM >> To: OPNFV Tech >> Cc: Fatih Degirmenci; Jose Lausuch; Meimei;