NG Tech meeting, NG2018, Munich, Wednesday - Thursday full days INITIAL list of topics ---------------------- [Welcome and agenda prioritization] [Code Development Echosystem] - Maiken: status report from the ARC release manager regarding GIT transition, pointers to most important entry points and info sources - discussiuon: Bugzilla, GIT issues, other trackers; bug & issues reporting procedures - discussion: Communication channels for developers - discussion: Community contributions to ARC - Maiken: status of automatic build & testing [ARC 6 content] - discussion: deprecated code & features, implementation of all the code cleanup & removal decisions (CREAM, unicore, windows related, solaris, JAVA bindings, BES, EMIR, JDL, JSDL, ws-monitor, old uploaders/downloaders) - Balazs: defaults & mandatory blocks, block dependencies including default functionality & service blocks in ARC.CONF - Andrii: demo of ARCHERY - discussion: ARC6 release concept & versioning - Mattias: ARC6 build & runtime dependencies - Mattias: demo of the ARC6 startup scripts & packages, metapackages - Andrii: demo of the new RTE handling in ARC6 - Aleksandr: demo of the event-driven new AREX internal - Aleksandr: demo of the new REST interface - Maiken & Mattias: demo of the "zero.conf" use case 1 i.e. apache-like out-of-box service start up right after package install - Andrii: non-trivial auhorization setups in ARC6 (LCAS, LCMAPS, VOs, authroups with queues, so on...) - David: demo of arc.conf validator - Florido/Martin/Andrii: the ARC6 config parser - David: what to do with internal config profiles - Mattias: ARC 6 and ARC 5 living together (in repositories, on CEs both server & client cases) - Balazs: new set of arc.conf variables proposed by Florido, Maiken, Alexandr - David or Vincent: Data transfer state of the art in ARC6: performance, protocols, problems (bottlenecks) [Rolling out ARC 6] - discussion: the minimal content of the ARC 6 test release (going beyond hello-world scenario) - discussion: ARC 6 Testing, testplans, test infrastructure, test reports --we a numbered list of well-defined test cases where test case is defined by: server-side arc.conf, deployment instructions, client-side commands to execute, expected output/behaviour. --a platform to execute functionality tests and collect & visualize results. -- some sort of test reports - discussion: what are the "standard" or top-priority intefaces of ARC 6, e.g. can it be the REST interface (or EMI-ES), + XRSL + whatever info schema? what are the top priority LRMS systems, build platforms, etc... - Mattias: ARC 6 in software repositories - discussion: ARC6 documentation [Post ARC 6 topics] - Martin: client-side development, what would be nice to do if only there would be available manpower? do we have a vision for ARC 7 client? - discussion: What to do with GPGPUs and other unconventional hardware? - discussion: High availability CE, failover mode - discussion: contenarization with ARC, a "vision" on how containers could be launched on ARC CE and what a user/ARC is allowed/supposed to do in that workflow. - Balazs: Infosys for anonymous monitoring & GDPR - Balazs: How much we can simplify the infosys? - Vincent: investigate howto use ARC as an unmanaged storage - discussion: ARC python native clients - discussion: life after x509, ARC security roadmap - ARC 7 development roadmap - discussion: ARC as data transfer service - David: a new, separate data staging system/architecture. liberate DTS as a separate service. - discussion: seamless connection to HPC, cloud, ….