1 / 12

CoolEmAll Advisory board Meeting London October 2013

CoolEmAll Advisory board Meeting London October 2013. Andrew Donoghue, 451 Research Ariel Oleksiak , PSNC Eugen Volk, HLRS. Advisory board members. Scientific advisors Paul Brenner, Associate Director, Center for Research Computing, University of Notre Dame

ilya
Download Presentation

CoolEmAll Advisory board Meeting London October 2013

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. CoolEmAll Advisory board MeetingLondon October 2013 Andrew Donoghue, 451 Research Ariel Oleksiak, PSNC Eugen Volk, HLRS London, October 2013

  2. Advisory board members • Scientific advisors • Paul Brenner, Associate Director, Center for Research Computing, University of Notre Dame • Vincent Keller, Applications Analyst in CADMOS project at EPFL. • Hermann de Meer, Chair of Computer Networks and Computer Communications. University of Passau • Laurent Lefevre, Permanent researcher at INRIA (The French Institute for Research in Computer Science) ✔ • Jon Summers, Leeds University, school of mechanical engineering (ICEOTOPE) • Commercial advisors • Mark Acton, Critical Product Director, Norland Managed Services ✔ • Hans Witdouck, chief executive, Racktivity • DhesikanAnanchaperumal, CA, Vice President of CA’s ecoSoftware business unit • James Wilman, sales and marketing manager, Future Tech ✔ • John Booth – Carbon3IT ✔ • Phil Collerton, Uptime Institute and Sylvie Neau Le Roy, Uptime Institute. • Hassan Moezzi and Matt Warner, Future Facilities✔ • Aaron Rallo, chief executive, TSO Logic London, October 2013

  3. Project structure Main contacts • Ariel Oleksiak (PSNC) – Project coordinator • Eugen Volk (HRLS) – Technical coordinator • Andrew Donoghue (451G) – Dissemination, standardisation, and exploitation Projectstructure • Simulation, visualisation and decision support toolkit - HLRS • ComputeBox/DEBB prototypes - Christmann • Workload and resource management policies - PSNC • Energy efficiency metrics – IREC • Use cases and validation scenarios - ATOS • Dissemination exploitation and standardisation – 451G London, October 2013

  4. Project overview Scientific partners + Commercial partners London, October 2013

  5. Evolution of DCIM & Data centre design tools • \ Datacentres CEE, Warszawa, 26 Sept 2013

  6. Who is CoolEmAllaimed at?

  7. CoolEmAll adoption London, October, 2013

  8. Role of advisory board HowAB and CoolEmALl consortium can cooperate: • Scientific + Commercial AB:Promotion of project press release, tweet, conference presentations • Scientific + Commercial AB: Provide regular external feedback on the development of the project • Scientific + Commercial AB: Looking for early adopters and testers of the components. • Real-world facility level data (power use etc.) • Commercial AB: Lack the resources to develop a fully mature product so looking for collaborators/partners in exploiting results (licensing/partnering etc.) London, October 2013

  9. Discussion topics • General • Is holistic (application centric) approach to DC design/operation practical? • SVD Toolkit • Where in the design/build lifecycle should tools be deployed. • IT defined as black boxes • Applications in the design-phase • More suited to design versus operation • Growing importance of simulation in operation versus design London, October 2013

  10. What stage is CoolemAll useful? London, October 2013

  11. Discussion topic AB members • Metrics • What metrics should we focus on: • Partial PUE • FVER • ACE – Future Facilities • Standardization • How important is standardization for the adoption of new tools/hardware • Not only technical interoperability but also contributing to standards bodies. • Open source (OpenDCIM) • DC Code of Conduct London, October 2013

  12. Next steps • Final tools ready early 2014 • Another webcast demo • Follow-up survey • Discuss technical integration • Sharing components/data • Real-world data to verify models • Plan use by AB or customers • AB Involvement in future projects • RenewIT • Others London, October 2013

More Related