Re: [opnfv-tech-discuss] Discussion Topics for Weekly Technical Discussion this Thursday 09/28

Bin, I think it would be a good conversation to have around hardware requirements in OPNFV and how they evolving. This is particularly interesting when thinking about OPNFV and ONAP integration. For example, the pharos specification only has a minimum

[opnfv-tech-discuss] Discussion Topics for Weekly Technical Discussion this Thursday 09/28

Hello community, Please let me know if you have any topics or issues that need to be discussed at our weekly technical discussion this Thursday 09/28. If no issues or topics, we may cancel the discussion this week. Thanks Bin ___ opnfv-tech-discuss m

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

I think I should be able to make this as well—just need to juggle my schedule a little bit. =) See you there! At Your Service, Mark T. Voelker OpenStack Architect > On Sep 25, 2017, at 11:33 AM, Andrea Frittoli > wrote: > > Hi Morgan, Ildikó, > > the schedule is fine for me. > > I guess

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

That is correct. The opnfv.x.y.z are actually tags managed by the OPNFV release not by project owners. They are always on stable branches. The x.y.z tags are always on master and controlled by project owners (if they want to have such tags as they are optional). Thanks Alec From: "Yujun

Re: [opnfv-tech-discuss] [announce] 2018 OPNFV release names

+1 for Fraser I agree that it could be problematic if we name the release after something difficult to find in map. On Tue, Sep 26, 2017 at 12:25 AM Raymond Paik wrote: > All: > > Thanks for voting on the release naming poll. > > First, for G-release

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

I had a quick look at the wiki page and try to understand the rationale behind proposal. If I understand it correctly, it is like - *opnfv-x.y.z* to sync with OPNFV official releasing cycle, i.e. Danube, Euphrates (opnfv-5.y.z). - *(optional) x.y.z* for project intermediate release which is manag

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

I plan to devote a large portion of the release meeting to this topic tomorrow. Please come prepared with your questions for Alec. I think that this change puts us on the path which will eventually lead toward a consolidated release process that incorporates the quickly evolving XCI system. I wo

Re: [opnfv-tech-discuss] Many failed docker builds

Hi, Alec, thanks for the feedback. Can we track this in https://jira.opnfv.org/browse/RELENG-315 -Aric On Mon, Sep 25, 2017 at 4:49 PM, Alec Hothan (ahothan) wrote: > > > This all ties into the versioning of artifacts since you can’t have > concurrent builds of the same repo (for example from 2 d

Re: [opnfv-tech-discuss] Many failed docker builds

This all ties into the versioning of artifacts since you can’t have concurrent builds of the same repo (for example from 2 distinct gerrit triggers on different patchsets) without proper tagging of the artifacts (you can’t just tag them with “latest”) I think it would make sense to allow only

[opnfv-tech-discuss] Quick update on the upcoming Plugfest

All, We've had a couple of bi-weekly planning calls for the Plugfest, so this is for people who have not been able to join the meeting in the past several weeks. (You can find the meeting logistics on the main Euphrates Plugfest page

[opnfv-tech-discuss] urgent euphrates git tags vote needed

I would like to get a quick vote from any person that works directly or indirectly with code in OPNFV Please reply with -1, 0 +1 For using prefixed git tags for the Euphrates release: “opnfv-5.0.0” This is a slight change to the plan on record (which was to use “5.0.0”). This does NOT impact

Re: [opnfv-tech-discuss] [announce] 2018 OPNFV release names

Ray, while there are not a ton of river “Fenix” photos, there are some, e.g http://www.soberaniachile.cl/archivosdeimagenes/fenix.jpg and http://photo500x500.mnstatic.com/f11c1c363de24a0a5ad44bb39046e2da/rio-fenix-grande.jpg – there are wiki entries such as… https://es.wikipedia.org/wiki/Desv%

[opnfv-tech-discuss] Many failed docker builds

Hello, Not sure who can help with this. Right now there are 4 or more executor slots than can execute any given opnfv-docker.sh script. The problem is with so many docker jobs being introduced in Euphrates, we are getting a lot of failures due to timeouts. For example, on arm-build4, 4 docke

Re: [opnfv-tech-discuss] PDF feedback and questions from our experience with Fuel

Hi, The part about net_config was confusing because it was not (yet) part of the official PDF spec. After today’s infra meeting, and some more discussion on IRC, it looks like net_config will become part of the spec, but we need to sort out some network naming issues first. However, ‚admin’, ‚m

[opnfv-tech-discuss] [Infra] Infra WG Meeting minutes - Sept. 25th

September 25th Agenda: Experiences with PDF, David Blaisonneau, Guillermo Herrero, Alexandru Avadanii complete discussion from last week follow up on action items and status status of Pharos projects (LaaS and Dashboard)

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

Hi Morgan, Ildikó, the schedule is fine for me. I guess we won't be able to answer the questions from the agenda in the allocated time, but it should be enough to get the conversation started; we can the follow up over other communication channels (IRC? Else?). Andrea On Sun, Sep 24, 2017 at 5:

[opnfv-tech-discuss] [announce] 2018 OPNFV release names

All: Thanks for voting on the release naming poll. First, for G-release the winner is Gambia (the first African river for OPNFV). For the F-release, the top vote getter was Fenix in Argentina. However, after some research it looks this is a tributary of another river (Deseado

Re: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E release.

+1 Bryan, "Thank You" and "Well Done" doesn't say enough... best wishes in *all* your endeavors, Maryam! Thank you for your willingness to step-up, Aaron! Al From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, BRYAN L (BR

[opnfv-tech-discuss] OpenDaylight DDF

Hello, OPNFV Community! OpenDaylight will be holding it's Oxygen Developer Design Forum in Santa Clara, CA on October 9th and 10th. We would like to invite interested members from the OPNFV Community to join us. If you wish to host a topic or view currently submitted topics please visit this wiki

[opnfv-tech-discuss] Canceled: SampleVNF Weekly meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:India Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0530 TZOFFSETTO:+0530 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0530 TZOFFSETTO:+0530 END:DAYLIGHT EN

[opnfv-tech-discuss] [Auto] More RAM for Auto

Dear Lincoln, So far Auto got 16G RAM x86 based pod from LaaS at UNH LoL. Since it is ONAP verifications onto OPNFV, it needs more memory. Would you add some more memory to it? The Arm based pod needs a couple of weeks before final arrival, because of the lead time. Thank you, Tina IMPORTANT

Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two SFC's

Hi Manuel, I am able to run the usecase ‘sfc_two_chains_SSH_and_HTTP.py’. The issue is with the sequence of executing commands. First SFC Classifier flows are not adding in Compute Node, if we have two active Service Function Chains. So, I created SFC1 and added required classifiers with that ch

Re: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E release.

And thanks to you, Maryam, for your excellent work as PTL. I'm sure over the last couple of releases the team picked up some great pointers from you on how to do this job right, so we should be in good hands. Thanks, Bryan Sullivan | AT&T From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailt

[opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E release.

Hi folks, After much consideration, I have decided to step down as the PTL for barometer after the E release. I have really enjoyed my time as the PTL and the support of a great team. I and the team would like to remain involved/stay on as a project committers and contributors. But I think it

Re: [opnfv-tech-discuss] PDF feedback and questions from our experience with Fuel

Hi Alexandru, thanks for this big set of patches and a sum up of our last pdf discussions. The part about net_config is quite confuse, specially because you sum up many problems already solved by net_config, but talking about PDF not having it, then talking about what add net_config... but it

Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two SFC's

Hey Srikanth, You are not getting any classification rule because it can't find an RSP, which means it was not able to create the chain. There is something fishy going on and it should not be there if you do a complete restart of ODL. To completely restart ODL, you must stop it, remove the directo

Re: [opnfv-tech-discuss] VxLAN workaround for OPNFV Danube 3.0

Hi Srikanth, It is still required. Regards, Manuel On Sat, 2017-09-23 at 14:04 +, Srikanth Lingala wrote: > > > Hi, > > I am trying to implement SFC with Opendaylight is OPNFV Danube 3.0 release. > > Is “VxLAN Workaround in Compute node” still required in OPNFV Danube 3.0 release also? Or