1 / 6

Future support of Argus

Future support of Argus. Peter Solagna – EGI.eu. Current status. After the end of EMI SWITCH committed to support the Argus components under their responsibility for at least one year Formally this period ended on April 2014 Best effort support

emile
Download Presentation

Future support of Argus

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Future support of Argus Peter Solagna – EGI.eu

  2. Current status • After the end of EMI SWITCH committed to support the Argus components under their responsibility for at least one year • Formally this period ended on April 2014 • Best effort support • There is no dedicated effort allocated to Argus • Curently Valery Tschopp is still following up with the GGUS tickets in the Argus support unit • But the workload has increased, due to the wider deployment of the tool

  3. SWITCH position I contacted Simon Leinen (SWITCH) about the plans for the future: • SWITCH (namely Valery Tschopp) for the immediate future will continue to answer to GGUS tickets and support ARGUS, on a best effort base. Some issues may not be solved and only critical blocking bugs will be patched. • SWITCH is migrating away from the Grid operations, for the medium term Simon strongly suggests that some other institution could take over the support for Argus, meaning code support and support on GGUS. If needed, SWITCH is available to support the handover process. • EGI and WLCG should start to discuss about alternative supporters ASAP

  4. Possible post-SWITCH options • INFN is already supporting one Argus component, and technically it would be possible to support the whole Argus suite. • INFN need to assess the availability of effort for this additional task • Other NGIs and institutions may have the expertise to contribute to the support • Move Argus to a community supported tool • Still there is need of effort to wrap up the releases • Alternatives to Argus?

  5. Support of the other middleware products • As a general statement the EMI product teams committed to support their products for 12 months (at least) after the end of the project • The large majority of the product teams are still supporting their software • EGI is circulating a simple survey among product teams to update of theProduct ID cards • Support calendar for the current version in UMD-3 • Long term support calendar including new major releases

  6. Comments and ideas?

More Related