[petsc-dev] Fwd: [ECP-ST-PIs] Plan for Regular ECP Software Stack Releases - your feedback sought

[Barry Smith]

> Begin forwarded message:
> 
> From: "Neely, Rob" <neely4 at llnl.gov>
> Subject: Re: [ECP-ST-PIs] Plan for Regular ECP Software Stack Releases - your feedback sought
> Date: October 10, 2017 at 9:55:29 PM GMT+2
> To: "ecp-st-pis at exascaleproject.org" <ecp-st-pis at exascaleproject.org>
> Cc: "ecp-lab-leadership at exascaleproject.og" <ecp-lab-leadership at exascaleproject.og>, Andrew Siegel <siegela at uchicago.edu>, Phillip Colella <pcolella at lbl.gov>
> 
> ST Project PIs,
>  
> Some of you provided feedback to our proposed ECP software release plan, and we’re taking all of that into account and will come back with a refined set of software release plans soon – but in the meantime, we’ve gotten the go ahead from Paul (and now Doug) to start this effort.
>  
> One of the early pieces we want to get in place is a solid system for allowing continuous integration (CI) at the various DOE HPC facilities. After months of discussion in a working group understanding what CI systems are being prototyped at the various DOE centers, and where the pain points are – we feel like we have relative consensus on a preferred path forward. The details are all provided here, and I invite you to take a look at provide some feedback:
> https://docs.google.com/document/d/1n2640n7FGoKM2NYVw074tkBUErwpflEZx_IpMv7mYm0/edit#heading=h.qb76z9iuhwd <https://docs.google.com/document/d/1n2640n7FGoKM2NYVw074tkBUErwpflEZx_IpMv7mYm0/edit#heading=h.qb76z9iuhwd>
>  
> TL;DR - we’re proposing to extend the open source GitLab CI tool to address some of the key issues that virtually all CI tools have that make them difficult to use in an HPC environment. For projects that don’t use GitLab (or don’t want to), we believe there is a sufficiently smooth pathway to integrate with either github.com <http://github.com/> via plugins, or to automatically mirror your git repos to our gitlab enterprise site, and thus this represents the best solution. We welcome your feedback, as we’re close to putting out an RFQ to get the necessary features added by a 3rd party. Please leave your comments on the google doc site, or email me directly. Something in the next week (say, by COB on 10/19) would be most helpful.
>  
> Our goal is nothing short of making CI as easy to use on DOE HPC systems as you’re used to with your cloud-based offerings!
>  
> --Rob
>  
> From: Rob Neely <neely4 at llnl.gov <mailto:neely4 at llnl.gov>>
> Date: Friday, September 8, 2017 at 1:07 PM
> To: "ecp-st-pis at exascaleproject.org <mailto:ecp-st-pis at exascaleproject.org>" <ecp-st-pis at exascaleproject.org <mailto:ecp-st-pis at exascaleproject.org>>
> Cc: "ecp-lab-leadership at exascaleproject.og <mailto:ecp-lab-leadership at exascaleproject.og>" <ecp-lab-leadership at exascaleproject.og <mailto:ecp-lab-leadership at exascaleproject.og>>, Andrew Siegel <siegela at uchicago.edu <mailto:siegela at uchicago.edu>>, Phillip Colella <pcolella at lbl.gov <mailto:pcolella at lbl.gov>>, "Julia C. White" <whitejc at ornl.gov <mailto:whitejc at ornl.gov>>
> Subject: Plan for Regular ECP Software Stack Releases - your feedback sought
>  
> ST Projects PIs,
>  
> As part of our long-term goals to integrate our ST products and support the AD projects and DOE HPC facilities, we (the ST L2's/L3's in concert with the broader ECP management team) have produced a draft plan for doing a regular release of the ECP software stack. There is a confluence page set up athttps://confluence.exascaleproject.org/display/1ST/Plan+for+Regular+ECP+Software+Stack+Releases <https://confluence.exascaleproject.org/display/1ST/Plan+for+Regular+ECP+Software+Stack+Releases> where we invite you to take a look and provide any feedback.
>  
> This plan emerged out of initial ST integration planning activities, early discussions with the HPC facilities on support for continuous integration and support for our software stack (https://confluence.exascaleproject.org/pages/viewpage.action?pageId=25990689 <https://confluence.exascaleproject.org/pages/viewpage.action?pageId=25990689>), and broader ECP management team discussions on ways to highlight our software projects as a comprehensive and cohesive product of the ECP ST activities.
>  
> We are asking for a quick turnaround on comments (by Sept 15th) so we can move forward as quickly as possible with final approvals, and beginning the tasks of building up the team and identifying resources necessary to begin an execution phase. This will ultimately impact most, if not all, of the ST projects - so your input is critical. We ask that comments be left on the confluence page, but if you prefer to keep your input private - you can send it directly to me (Rob Neely <https://confluence.exascaleproject.org/display/~neely4@llnl.gov>).
>  
> See: Plan for Regular ECP Software Stack Releases <https://confluence.exascaleproject.org/display/1ST/Plan+for+Regular+ECP+Software+Stack+Releases>
>  
> --Rob Neely, on behalf of the ST leadership team
>  
> _______________________________________________
> ECP-ST-PIs mailing list
> ECP-ST-PIs at elist.ornl.gov <mailto:ECP-ST-PIs at elist.ornl.gov>
> https://elist.ornl.gov/mailman/listinfo/ecp-st-pis <https://elist.ornl.gov/mailman/listinfo/ecp-st-pis>
> To unsubscribe, send a blank email to ecp-st-pis-unsubscribe at elist.ornl.gov <mailto:ecp-st-pis-unsubscribe at elist.ornl.gov>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20171011/482d02e2/attachment-0001.html>