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 t

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 http://testresults.op

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 / rally

[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 wo

[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 DTSTART:16010101T0200

[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&preview=/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 t

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 judgm

[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 remember,

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 decorr

Re: [opnfv-tech-discuss] New Project Proposal: Dovestack

Hi, I went quickly through the proposal and I probably need additional information to understand the need and the role of such project. For me, as far as I understand it now, it is useless and overlapping, I do not see what kind of problem it solves. The Functest framework allows since E to

[opnfv-tech-discuss] [OPNFV] [OpenStack] cross collaboration on testing activities

Hi, I discussed with Georg on the opportunity to formalize a possible cross collaboration on testing between OpenStack and OPNFV. He attended the PTG last week and it seems there are possibly more synergies between the 2 groups. I booked a slot for the next Testing group meeting planned on Se

[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, reference

Re: [opnfv-tech-discuss] OpenContrail support in OPNFV

Hi Orange is also very interested in a scenario including OpenContrail. We expect it since Brahmaputra. As mentioned during last Summit, we are leveraging OPNFV tooling chain and CI/CD pipeline in our integration Center (https://www.youtube.com/watch?v=YVSFZegMj04); some configurations deal wi

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 07/

[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 th

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 futur

[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 http://testresults.opnfv.org/repo

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 http://testresults.opnfv.org/reporting2/display/master/functest/status-compas

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 => http://testresults.opnfv.org/reporting/yardstick/release/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 i

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 Murth

[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 part

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 O

[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 https://wiki.opnfv.org/

[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. Cedr

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) wrot

[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&modificationDate=14997887

[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. https://git.opnfv.org/releng/tree/ut

Re: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

+1 On 28/06/2017 20:11, David McBride wrote: TSC, After examining status and considering various alternatives, Ray and I have agreed to propose July 14 as the new release date for Danube 3. We believe that this will give project and installer teams time to overcome current issues, as well a

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 ter

Re: [opnfv-tech-discuss] [opnfv-tsc] New meeting time for the TSC call

+1/+1 same position than Dave Morgan On 22/06/2017 10:36, Dave Neary wrote: +1 for time change. I am fortunate to be in a time zone where it does not affect me much. Also +1 for cancelling July 4 meeting. Thanks, Dave. On 06/22/2017 03:39 PM, Frank Brockners (fbrockne) wrote: +1 for the

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" *Cc: *"opnfv-tech-discuss@lists.opnfv.org" *Subject: *[opnfv-tech-discuss]

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 d'Or

[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 date TSC members, Apologie

[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 , TECH-DISCUSS OPNFV Objet : Re: [opnfv-tech-discuss] proposed delay to Danube 3.0 rele

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 de

[opnfv-tech-discuss] [OPNFV] [Test working group] Test strategy & resources for Euphrates

Hi I tried to capture our discussions on the CI resources needed for Euphrates - the need for stability for long duration/robustness/stree tests I created a draft wiki page: https://wiki.opnfv.org/display/testing/Euphrates+Testing+needs feel free to complete/modify/comment/criticize We can disc

[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 Databas

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 : > > Hi

[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 à 16:

[opnfv-tech-discuss] [OPNFV] Status on test case catalogue and Landing page

Hi update on the landing page and test catalog we mentioned in Danube priorities for the testing group Jack made great progress, we put the reporting docker on testresults.opnfv.org you can access to it at http://testresults.opnfv.org/reporting2/reporting/index.html please note that this docker a

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 contri

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, othe

[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 Po

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, > > > Tha

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. > > https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal-daily-master/1251

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 https://wiki.opnfv.org/display/meetings/TestPerf?preview=/2926539/9569090/stres

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 │ └── relea

[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] [project proposal] samplevnf

Hi, great! I assume it is what Clive De Souza introduced in OPNFV summit #1, right? we will be happy to play with these VNF approximations representative from the traffic in Functest (it was already identified as a possible task for Danube). We already had some discussions on that some months ago

Re: [opnfv-tech-discuss] Functest ODL-SFC

Hi Pau on which scenario/installer did you try to execute this test? according to the dependencies delcared by the SFC team for Colorado version (https://git.opnfv.org/functest/tree/ci/testcases.yaml?h=stable/colorado) odl-sfc has the following constraints |name: odl-sfc criteria: 'status == "PAS

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 look

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 https://hub.docker.com/r/opnfv/functest/

[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 th

[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 ident

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 specifi

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

I do appologize for the mess basically the GTM bridge were already booked and I misbooked the bridge (bad date) sorry again /Morgan Le 11/01/2017 à 17:44, Margaret Chiosi a écrit : > ok that worked > > On Wed, Jan 11, 2017 at 11:25 AM, Rautakumpu, Mika (Nokia - FI/Espoo) > mailto:mika.rautaku...

[opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A 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 DTSTART:16010101T0200

Re: [opnfv-tech-discuss] [polestar] Reminder of call this thursday 11AM US EST - also send me suggestions on when to do a F2F

yep, my colleague Jamil and Xiaolong are working on that and discussing with Ray /Morgan Le 11/01/2017 à 16:51, SULLIVAN, BRYAN L a écrit : > > The OPNFV Hackfest is still in discussion, but at Orange labs in Paris > or north of Paris (can’t recall the city). Morgan will know. > > > > Thanks,

[opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A 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 DTSTART:16010101T0200

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

Le 10/01/2017 à 08:27, Prakash Ramchandran a écrit : > > Morgan, > > > > Went through the code for VNF On boarding still trying to understand > the logic. > > Point 1 that you are on boarding the VNF with or without Orchestrator > (why not call it nfvo and being opera or orchestra) similarly why

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 t

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

Dear Orchestra, Opera, OAI teams I would like to know the status on VNF onboarding for Danube. My last view was that you all were candidates to integrate a testcase integrating an orchestrator (respectivelly Openbaton, Open-O, Juju for OAI) to deploy a VNF (respectively ??, vIMS, vEPC(OAI)). I

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 > http://testresults.opnfv.org/test/swagger/spec.html#!/spec/updat

[opnfv-tech-discuss] [OPNFV] [Danube] joid status

Hi Narinder during our weekly meeting this morning I took the point to sync with you on joid for Danube. As far we can see in Jenkins, there were no joid deployment on bare metal since 1 week (but I assume Intel Infra is not available at the moment and all the joid deployments were done on Intel)

[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 d'ori

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. > > https://wiki.opnfv.org/displ

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 impleme

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 containe

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 ca

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 co

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 cla

Re: [opnfv-tech-discuss] [odl-sfc] Change test names in functest DB

Hi comments below Morgan Le 25/11/2016 à 16:55, Juan Vidal Allende a écrit : > > Hi, > > I have a couple of suggestions: > > 1) The '&' character has a special meaning in some environments > (e.g. bash), so I would avoid it. > > 2) Let's be consistent, either use camelCase for all the name,

[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 bu

Re: [opnfv-tech-discuss] Testing view and Case Selection [OPNFV] testing meeting APAC slot

Hi Jack I submitted a patch for the reorganization of the reporting https://gerrit.opnfv.org/gerrit/#/c/24433/ see comments in line Le 16/11/2016 à 12:52, chenjiankun a écrit : > > Hi Morgan, > > > > Thank you for your clarification. This help a lot for me. > > > > To finish the test case se

Re: [opnfv-tech-discuss] [OPNFV] testing meeting APAC slot

Hi Jack see comments in the mail /Morgan Le 14/11/2016 à 05:46, chenjiankun a écrit : > > Hi Morgan, > > > > I am Jack from yardstick. How is it going? > fine and you? > > > > I have attended the last APAC Testing meeting. I really appreciate > your work in Testing view and Case Selection. >

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 http://testresult

Re: [opnfv-tech-discuss] [OPNFV] testing meeting APAC slot

Hi no problem, I put Bottleneck update instead regarding the meeting, let' discuss 5 minutes tomorrow. I do not know if the second meeting of the month would be easier than the rule the second wednesday of the month. so for me in December the APAC slot should be the 14th of December (not the 1st

Re: [opnfv-tech-discuss] Any graphic for an overview of Colorado senarios?

Hi Yingjun regarding scenarios - a wiki page describing the naming: https://wiki.opnfv.org/display/INF/CI+Scenario+Naming - see also section "Automated testing" in http://artifacts.opnfv.org/functest/colorado/docs/userguide/index.html each version lists the candidate scenarios - colorado: https:/

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 un

[opnfv-tech-discuss] Jose Lausuch is the New Functest PTL

Hi TSC, I would like to inform that the Functest project elected this morning his new PTL. We just applied the recommendations we voted in Functest (https://wiki.opnfv.org/display/functest/Functest+admin) Jose - you all know him - will take the lead of the project. He has been very active in

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 = f

[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: Bite

[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 infor

  1   2   >