WP4 Summary Patrick Fuhrmann for the WP4 Tream RIA

Some quick reminders  Partners INDIGO-DataCloud RIA NameCountryTotal (PM) 4.1 Computing 4.2 Storage 4.3 Network Names INFNItaly To be defined REPLYIt/De10 Stefano, Dante CSICSpain3030 (Alvaro)Alvaro UPVSpain12Miguel, German ATOSSpain15 Ana, Mick LIPPortugal403010Mario, Goncalo KITDE (Marcus)Marcus N.A. DESYDE60 Patrick, Paul CNRSFrance20 Julein, Mattie CESNETCzech R.2828 (Zdenek)Zdenek IBCH PASPoland20 Macei CERNCH10 Tim, Ricardo

Deliverables and Milestones  D4.1, Month 6 (DEC/PU): Software Design Document for WP4 [DESY]  This deliverable contains the software design document of the technical areas of WP4, compliant with the overall Technical Design Plan including WP5 and WP6. The design will be based on the requirement analysis from WP2.  M4.1 [Month 6] : Software Design Document  Providing the Software Design Document for WP4 (=D4.1)  M4.6 [Month 15]: Containers, Trusted Repositories and OCCI  Support for container execution with trusted container repository and standard interfaces.  M4.9 [Month 15]: Spot instance mechanism (Open Stack ?)  Implementation of spot-instances mechanisms  M4.13 [Month 15]  Reference Implementation Prototype for QoS classes and policies in at least one INDIGO-DC storage implementation.  M4.16 [Month 15]  Providing prototype implementation with at least one INDIGO-DC storage system for seamless access of data through cloud, web, object store and fast local access protocols. INDIGO-DataCloud RIA

Task leaders  Task leaders:  Alvaro (CSIC)  Marcus (KIT)  Zdenek (CESNET) INDIGO-DataCloud RIA

Task 4.1 Computing INDIGO-DataCloud RIA

Task 4.2 Virtualized Storage  Partners: INFN, DESY, KIT, IBCH PAS  All our partner are very knowledgeable in storage  Main Activities  Storage OoS definition  Storage Media choice, Access Latency Retention Policy  Cross Protocol Access  Access Object Store via POSIX and vice versa ?  Integrate existing storages into INDIGO AAI INDIGO-DataCloud RIA

Task 4.3 Virtual Networks  Task 4.3 Virtual Networks:  Partners: CESNET, LIP, INFN, Santer Reply  Expertise in IaaS cloud provisioning, cloud management framework instrumentation.  Experience from existing infrastructures  Initial goals:  Reliable on-demand [private] networks for VMs  establishing them and connecting virtual machines to them (Standard ?)  lot of required functionality already there, but there are missing pieces  these 'gaps' will be identified and filled in.  Additional tools/appliances for these networks (Useful for WP5)  controlling and monitoring their behavior on VMs in the network (firewalls, vulnerabilities)  service appliances for such networks (NAT, DHCP, VPN...) INDIGO-DataCloud RIA

Issues  How should we make services available  Standards  Native API’s and protocols  We found that WP2 might only of limited help as customers really don’t care.  From WP2 we need the high level objectives. That might very much influence WP6.  Those have to be mapped to implementation decisions together with WP5 and possibly WP6  What is our relationship to EGI Fed Cloud INDIGO-DataCloud RIA

WP Interactions  WP3 (Many questions, we would need a session on this)  How is the development process managed ?  How is quality assurance handled for contributions to other projects (e.g. OpenStack)  Do we distinguish between  our own code  External Code, we modified  Completely external modules, packages  WP5/6 details on they assume us to interface  WP2:  high level description on : Full Data Life Cycle  We need examples of Data Management plans of WP2 customers.  How do we organize x-WP activities, AAI and Service Discovery and Monitoring  Is SD and Monitoring just WP responsibility INDIGO-DataCloud RIA

Next steps  We need to agree on (two) F2F meetings rather soon  Private WP4 for detailed work distribution to the partners.  WP 4/5/6 interactions for the first design document.  Regular Phone meetings in preparation of the F2F will be arranged by the talks leaders. INDIGO-DataCloud RIA