wp5
play

WP5 JRA1 Testbed Management Technologies JRA1 Testbed Management - PowerPoint PPT Presentation

May 29, 2023 •362 likes •530 views

INFSO-RI-223782 WP5 JRA1 Testbed Management Technologies JRA1 Testbed Management Technologies ETICS2 first Review Alain Roy University of Wisconsin-Madison (USA) Bruxelles 3 April 2009 Bruxelles, 3 April 2009 INFSO-RI-223782 Contents

  1. INFSO-RI-223782 WP5 JRA1 Testbed Management Technologies JRA1 Testbed Management Technologies ETICS2 first Review Alain Roy University of Wisconsin-Madison (USA) Bruxelles 3 April 2009 Bruxelles, 3 April 2009

  2. INFSO-RI-223782 Contents • Goals • Major Achievements • Challenges Ch ll • Metrics and Statistics • Conclusions Conclusions WPX WP name Bruxelles, 3 April 2

  3. INFSO-RI-223782 Goals WPX WP name Bruxelles, 3 April 3 3

  4. INFSO-RI-223782 Goals • Top-level Goals: • Designing and implementing solutions for resource and Designing and implementing solutions for resource and job management across the grid on IPv4 and IPv6 networks. • Explore existing hardware virtualization techniques • Explore existing hardware virtualization techniques, in in order to integrate them into ETICS. • Deliverables due so far: 1. Job Management Web Service Interface Specification J b M t W b S i I t f S ifi ti 2. IPv6 Compliance Analysis 3. Integration of Virtualization Technologies (Prototype) g g ( yp ) • Upcoming Deliverables: 4. Job Management Web Service Implementation 5 Integration of Virtualization Technologies 5. Integration of Virtualization Technologies 6. IPv6 Compliance • Other: • Support job submission to non-Condor systems (In support of DSA 2.4) WPX WP name Bruxelles, 3 April 4

  5. INFSO-RI-223782 Other Goals • Cross-Site job submissions • Ability to share jobs between ETICS instances. CS WPX WP name Bruxelles, 3 April 5

  6. INFSO-RI-223782 Major Achievements WPX WP name Bruxelles, 3 April 6 6

  7. INFSO-RI-223782 Achievements • DJRA 1.1: We have completed the specification of the web interface for Metronome. • DJRA 1 2: We have completed the IPv6 compliance • DJRA 1.2: We have completed the IPv6 compliance analysis. • The analysis was the easy part. • The compliance is the hard part… More when we discuss “challenges” • DJRA 1.3: While this deliverable has been achieved, it needs considerable refinement and work in order to achieve the full implementation • Remote job submission: Successfully prototyped and Remote job submission: Successfully prototyped and nearly in production WPX WP name Bruxelles, 3 April 7

  8. INFSO-RI-223782 DJRA 1.3: Virtualization Prototype • Two approaches explored • Use of Condor’s Virtual Machine Universe • Pushes management to Condor P h t t C d • Upper levels do no need to understand VM instantiation • Remote bootstrapper • (Explored at CERN) • Instrument Metronome to allow startup of virtual machine • Prototype in progress: complete by May 2009 • Prototype in progress: complete by May 2009 WPX WP name Bruxelles, 3 April 8

  9. INFSO-RI-223782 Metrics and Statistics WPX WP name Bruxelles, 3 April 9 9

  10. INFSO-RI-223782 Metrics and Statistics • I’m not sure what I should put here. • Can someone provide some guidance? WPX WP name Bruxelles, 3 April 10

  11. INFSO-RI-223782 Challenges WPX WP name Bruxelles, 3 April 11 11

  12. INFSO-RI-223782 Challenge: Progress on Virtualization • To date, we have been slow on progress towards use of virtualization technologies • We believe that we can accomplish our deliverables during the ETICS 2 project. g p j WPX WP name Bruxelles, 3 April 12

  13. INFSO-RI-223782 Challenge: IPv6 Compliance • We have completed our IPv6 compliance analysis, and there are two major obstacles to achieving a pure IPv6- ready implementation. ETICS relies on Metronome, which relies on Condor, 1. and Condor is not IPv6 ready. The Condor project has requested funding for IPv6 compliance and is likely to get it, but it is unlikely to be completed before the end of ETICS 2. (The funding will not be received for a while) Metronome relies on MySQL which is not IPv6 2. compliant. Switching to a new database is feasible but p g non-trivial. We are not aware of MySQL plans for IPv6 compliance. • Do we need to rely on a bridge/tunnel solution for now? Do we need to rely on a bridge/tunnel solution for now? WPX WP name Bruxelles, 3 April 13

  14. INFSO-RI-223782 Conclusions WPX WP name Bruxelles, 3 April 14 14

  15. INFSO-RI-223782 Conclusions • Remote job submission is nearly production-ready • IPv6 Compliance faces challenges best dealt with by people outside the project people outside the project • Virtualization is a bit behind, but we expect to complete it. WPX WP name Bruxelles, 3 April 15

Recommend

More recommend