[opnfv-tech-discuss] [Compass4NFV] Cancel weekly meeting of Sep 28 and Oct 5

2017-09-27 Thread Justin chi
Hi , Because rush for Euphrates release and Chinese National day vacations, so I cancel today and next weekly meeting. if you have any issues, please mail me, thanks. Regards Justin ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org

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

2017-09-27 Thread Bob Monkman
Alec, We have had this conversation with David and Ray a number of times in other areas. We definitely prefer the architecture specifier is included in all areas where there needs to be a distinction. The correct descriptor for ARM64 is actually “aarch64

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

2017-09-27 Thread Alec Hothan (ahothan)
Thanks for bringing up the multi-arch support and yes if we decide to go the route of adding the arch in the tag there is no problem doing so - although there does not seem to be any standard on where to place that string, I’ve seen tags with the arch at the front (e.g. opnfv/functest:x86_64-re

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

2017-09-27 Thread Alexandru Avadanii
+1 for the tag prefix. How about adding the architecture to that prefix? e.g. opnfv/functest:x86_64-release-5.0.0 From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan (ahothan) Sent: Wednesday, September 27, 2017 11:01 PM

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

2017-09-27 Thread Alec Hothan (ahothan)
Jose, I am fine with using the “release-” prefix instead. Any prefix can work. If we want something shorter: rel-5.0.0. We can leave that decision to David. Note that what you call “none release” can actually be as important for project owners than those with the prefix ;-) Looking at the bigge

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

2017-09-27 Thread Jose Lausuch
+1 What about using tag "release-x.y.z" instead of "opnfv-x.y.z" since the name “opnfv” is already included in the image name? e.g. opnfv/functest:release-5.0.0 This way we differentiate between an official OPNFV release artifact from a none released. - Jose - > On 27 Sep 2017, at 20:00, R

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

2017-09-27 Thread Raymond Paik
All, Please let Alec know if you have any other questions/feedback on the proposal. The plan is to have a quick vote on the TSC call next week (October 3rd). Thanks, Ray On Tue, Sep 26, 2017 at 5:38 AM, MORTON, ALFRED C (AL) wrote: > +1 and thanks for the proposal, Alex! > > > > Al > > > > *

[opnfv-tech-discuss] SFC weeekly MoMs

2017-09-27 Thread Manuel Buil
Hi, Here are the MoMs of today's weekly meeting: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc. 2017-09-27-14.00.html Regards, Manuel___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org