Hi Brandon,

Please add Functest Docker Parser 
<https://hub.docker.com/r/opnfv/functest-parser/> and Functest Docker Arm 
<https://hub.docker.com/r/opnfv/functest/>  in the Functest column.

Thanks,
Jose



> On 25 Oct 2017, at 14:16, Fatih Degirmenci <fatih.degirme...@ericsson.com> 
> wrote:
> 
> Hi,
> 
> XCI links are pointing to master versions on purpose so please do not change 
> them.
> 
> /Fatih
> 
> On 25 Oct 2017, at 14:14, Georg Kunz <georg.k...@ericsson.com 
> <mailto:georg.k...@ericsson.com>> wrote:
> 
> Hi Brandon,
>  
> Thank you for updating the links. There are a few more links which should be 
> updated.
>  
> Pointing to “latest” documentation instead of stable/euphrates:
> VSPERF Test Guide 
> <http://docs.opnfv.org/en/latest/submodules/vswitchperf/docs/testing/user/userguide/index.html>
> Barometer Overview 
> <http://docs.opnfv.org/en/latest/submodules/barometer/docs/index.html?highlight=Barometer>
> Barometer Release Notes 
> <http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/release-notes/release-notes.html>
> Barometer User Guide 
> <http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/feature.userguide.html>
> Doctor Overview 
> <http://docs.opnfv.org/en/latest/submodules/doctor/docs/development/requirements/index.html>
> Doctor Release Notes 
> <http://docs.opnfv.org/en/latest/submodules/doctor/docs/release/release-notes/releasenotes.html>
> Doctor User Guide 
> <http://docs.opnfv.org/en/latest/submodules/doctor/docs/release/userguide/index.html?highlight=Doctor>
> XCI Overview 
> <http://docs.opnfv.org/en/latest/submodules/releng-xci/docs/xci-overview.html>
> XCI Sandbox & User Guide 
> <http://docs.opnfv.org/en/latest/submodules/releng-xci/docs/xci-user-guide.html>
>  
> Best regards
> Georg
>  
> From: Brandon Wick [mailto:bw...@linuxfoundation.org 
> <mailto:bw...@linuxfoundation.org>] 
> Sent: Tuesday, October 24, 2017 3:39 PM
> To: Georg Kunz <georg.k...@ericsson.com <mailto:georg.k...@ericsson.com>>
> Cc: David McBride <dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>>; opnfv-project-leads 
> <opnfv-project-le...@lists.opnfv.org 
> <mailto:opnfv-project-le...@lists.opnfv.org>>; TECH-DISCUSS OPNFV 
> <opnfv-tech-discuss@lists.opnfv.org 
> <mailto:opnfv-tech-discuss@lists.opnfv.org>>
> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] 
> MS11 - tag repos
>  
> Thanks Georg, 
>  
> Agree it makes sense to links to Euphrates docs as much as possible from this 
> page. I updated a few links in this regard. Please let us know if you see 
> anything else. 
>  
> Best, 
> 
>  
> Brandon Wick
> OPNFV Head of Marketing, The Linux Foundation
> Mobile: +1.917.282.0960  Skype: wick.brandon
> Email / Google Talk: bw...@linuxfoundation.org 
> <mailto:bw...@linuxfoundation.org>
>  
>  
> On Tue, Oct 24, 2017 at 1:50 AM, Georg Kunz <georg.k...@ericsson.com 
> <mailto:georg.k...@ericsson.com>> wrote:
> Hi Brandon,
>  
> I fully agree with Alec and others that the OPNFV tools should be more 
> prominently featured and hence, I very much like that the new software 
> download page lists those tools as well. Great.
>  
> One comment though: I noticed that quite a few links on the download page are 
> pointing to documentation on the latest (master) branch or to stable/danube. 
> Is that intended? Shouldn’t they point to the documentation of the 
> stable/Euphrates branch instead?
>  
> Best regards
> Georg
>  
>  
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>] On Behalf Of Brandon Wick
> Sent: Monday, October 23, 2017 4:48 PM
> To: David McBride <dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>>
> Cc: opnfv-project-leads <opnfv-project-le...@lists.opnfv.org 
> <mailto:opnfv-project-le...@lists.opnfv.org>>; TECH-DISCUSS OPNFV 
> <opnfv-tech-discuss@lists.opnfv.org 
> <mailto:opnfv-tech-discuss@lists.opnfv.org>>
> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] 
> MS11 - tag repos
>  
> Hi Alec, 
>  
> Thanks for your feedback. The downloads page for Euphrates is being modified 
> to include links to testing tools, documentation, dashboards, docker, and 
> XCI. Please have a look when it goes live (tonight, 11:00 PM PT), and let us 
> know if you have any further recommendations. We can continue to evolve this 
> page over time to best fit user needs. 
>  
> Best, 
> 
>  
> Brandon Wick
> OPNFV Head of Marketing, The Linux Foundation
> Mobile: +1.917.282.0960 <tel:(917)%20282-0960>  Skype: wick.brandon
> Email / Google Talk: bw...@linuxfoundation.org 
> <mailto:bw...@linuxfoundation.org>
>  
>  
> On Mon, Oct 23, 2017 at 7:40 AM, David McBride <dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>> wrote:
> +Randy
>  
> Alec,
>  
> I think that Randy Levensalor would be a good person to talk with to get an 
> end-user perspective.  
>  
> David
>  
>  
> On Mon, Oct 23, 2017 at 7:29 AM, Alec Hothan (ahothan) <ahot...@cisco.com 
> <mailto:ahot...@cisco.com>> wrote:
>  
> The OPNFV release is currently made of a list of installers only (from the 
> link you provided mehttps://www.opnfv.org/software/downloads 
> <https://www.opnfv.org/software/downloads>)
> These installers are normally validated by the use of the matching versions 
> of OPNFV testing tools. However, the testing tools used to validate that 
> release are not available from that download page. Will the euphrates 
> download page include containers? It does not look like…
> What has been the feedback from consumers of these releases? Did they ask for 
> the testing artifacts for each release? Or were they cherry-picking the 
> containers directly from dockerhub?
>  
> We know that some test projects (such as Functest) are already used outside 
> of OPNFV labs, and quite possibly on non-OPNFV installers.
>  
> The TSC should realize there is actually quite a lot of potential interest 
> for OPNFV test projects outside of OPNFV environments and there are/will be 
> many external users who will be interested in using OPNFV test tools in their 
> own environment. So we should consider testing projects as first class 
> citizens – at the same level as installers/features.
> That is why I have been advocating for an independent versioning for OPNFV 
> test projects: make it easier for test project teams to support their 
> artifacts for more than 1 consumer (which has been limited to an OPNFV 
> release so far). I think this will only strengthen the quality of OPNFV 
> releases.
>  
> This independent versioning will also provide the right foundation for XCI.
> To get to the next level, OPNFV needs to
> empower test projects in how they can manage their own releases at their own 
> pace
> build XCI around this independent versioning model to add more control in the 
> current release process
>  
> Today, there are many hurdles to get to that level. For example, as a project 
> PTL, I still cannot build my own container using my project specific tags. 
> All I can do is trigger from gerrit a build of “latest” from master. I can’t 
> build the euphrates container for my project. The releng script was patched 
> recently to allow that but I can’t trigger it, so somebody from releng will 
> need to trigger these container builds for all the projects that have 
> containers.
>                                                                               
>                                                                               
>         
> Regards,
>  
>    Alec
>  
>  
>  
>  
>  
> From: David McBride <dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>>
> Date: Friday, October 20, 2017 at 3:46 PM
> To: "Alec Hothan (ahothan)" <ahot...@cisco.com <mailto:ahot...@cisco.com>>
> Cc: TECH-DISCUSS OPNFV <opnfv-tech-discuss@lists.opnfv.org 
> <mailto:opnfv-tech-discuss@lists.opnfv.org>>, opnfv-project-leads 
> <opnfv-project-le...@lists.opnfv.org 
> <mailto:opnfv-project-le...@lists.opnfv.org>>, Raymond Paik 
> <rp...@linuxfoundation.org <mailto:rp...@linuxfoundation.org>>, 
> "tim.irn...@ericsson.com <mailto:tim.irn...@ericsson.com>" 
> <tim.irn...@ericsson.com <mailto:tim.irn...@ericsson.com>>, Aric Gardner 
> <agard...@linuxfoundation.org <mailto:agard...@linuxfoundation.org>>
> Subject: Re: [opnfv-project-leads] [release][euphrates] MS11 - tag repos
>  
> +Ray, Tim, Aric
>  
> Thanks, Alec. 
>  
> Containers have emerged as a release vehicle, organically and informally, 
> within projects, rather than from the OPNFV project level.  So, we don't 
> currently have processes for containers.  We still need to better understand 
> how and where containers are being used within OPNFV and what process is 
> necessary to support the community in their use.  
>  
> David
>  
> On Fri, Oct 20, 2017 at 3:22 PM, Alec Hothan (ahothan) <ahot...@cisco.com 
> <mailto:ahot...@cisco.com>> wrote:
> David,
>  
> NFVbench is done <https://git.opnfv.org/nfvbench/log/?h=stable/euphrates>.
>  
> Who is triggering the corresponding container builds and when?
>  
> Regards,
>  
>   Alec
>  
>  
>  
> From: <opnfv-project-leads-boun...@lists.opnfv.org 
> <mailto:opnfv-project-leads-boun...@lists.opnfv.org>> on behalf of David 
> McBride <dmcbr...@linuxfoundation.org <mailto:dmcbr...@linuxfoundation.org>>
> Date: Friday, October 20, 2017 at 10:52 AM
> To: TECH-DISCUSS OPNFV <opnfv-tech-discuss@lists.opnfv.org 
> <mailto:opnfv-tech-discuss@lists.opnfv.org>>, opnfv-project-leads 
> <opnfv-project-le...@lists.opnfv.org 
> <mailto:opnfv-project-le...@lists.opnfv.org>>
> Subject: [opnfv-project-leads] [release][euphrates] MS11 - tag repos
>  
> IMPORTANT!! - PLEASE READ THE TAGGING INSTRUCTIONS 
> <https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Euphrates> 
> CAREFULLY, BEFORE YOU TAG YOUR REPO, SINCE THE VERSION NAMING FORMAT HAS 
> CHANGED SINCE THE LAST DANUBE RELEASE.
>  
> Team,
>  
> If you haven't already done so, t's time to tag your repos for the Euphrates 
> 5.0.0 release.  The deadline is 12 p.m. noon, Pacific Time.  See the link for 
> the tagging instructions, above. 
>  
> Let me know if you have any questions.
>  
> David
>  
> -- 
> David McBride
> Release Manager, OPNFV
> Mobile: +1.805.276.8018 <tel:%2B1.805.276.8018>
> Email/Google Talk: dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>
> Skype: davidjmcbride1
> IRC: dmcbride
> 
> 
>  
> -- 
> David McBride
> Release Manager, OPNFV
> Mobile: +1.805.276.8018 <tel:%2B1.805.276.8018>
> Email/Google Talk: dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>
> Skype: davidjmcbride1
> IRC: dmcbride
> 
> 
>  
> --
> David McBride
> Release Manager, OPNFV
> Mobile: +1.805.276.8018 <tel:%2B1.805.276.8018>
> Email/Google Talk: dmcbr...@linuxfoundation.org 
> <mailto:dmcbr...@linuxfoundation.org>
> Skype: davidjmcbride1
> IRC: dmcbride
> 
> _______________________________________________
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org <mailto:opnfv-tech-discuss@lists.opnfv.org>
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss 
> <https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss>
>  
>  
> _______________________________________________
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org <mailto:opnfv-tech-discuss@lists.opnfv.org>
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss 
> <https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss>
> _______________________________________________
> opnfv-project-leads mailing list
> opnfv-project-le...@lists.opnfv.org 
> <mailto:opnfv-project-le...@lists.opnfv.org>
> https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads 
> <https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads>
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to