1 / 22

Testing as a Service with HammerCloud: Agile Infrastructure for Dynamic Scheduling

Explore the utilization of HammerCloud for testing services, including new use cases, architectural changes, current infrastructure challenges, and the transition to a cloud-based paradigm. Discover how the Agile Infrastructure implements dynamic testing scheduling, shared storage solutions, and API integration for seamless testing operations. Learn about the vision for future scalability and efficiency in testing processes.

fagan
Télécharger la présentation

Testing as a Service with HammerCloud: Agile Infrastructure for Dynamic Scheduling

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. Testing as a Service with HammerCloud Ramón Medrano Llamas CERN, IT-SDC 15.10.2013

  2. Agenda Introduction New use cases Architectural changes Tests performed Future work Testing as a Service with HammerCloud

  3. HammerCloud • The grid testing framework • ATLAS, CMS, LHCb • 50 M jobs/year • 20 machines cluster hosted by CERN IT • voboxes Testing as a Service with HammerCloud

  4. Testing as a Service with HammerCloud

  5. Testing as a Service with HammerCloud

  6. New use cases 12,000 test/year Stress testing of sites Functional testing of sites AFT/PFT testing suite Benchmarking testingNEW! Cloud resource validation NEW! Athena nightly build system NEW! XRootD federation (FAX) NEW! ROOT I/O and WAN tests NEW! Testing as a Service with HammerCloud

  7. Example of FAX systemtesting Testing as a Service with HammerCloud

  8. Testing as a Service with HammerCloud

  9. jobs stress testing (on demand, non predictable) functional testing (predictable background) time This behavior needs some elasticity Testing as a Service with HammerCloud

  10. Testing as a Service • Need to cope with increasing demand, • Requested by users and tools on demand • Elastic testing infrastructure • Testing anything that allows: • submit() • status() • cancel() Testing as a Service with HammerCloud

  11. Current infrastructure 20 machines  manually managed Capped scalability Long time to provision Difficult lifetime management Security and updates Challenging software deployment Testing as a Service with HammerCloud

  12. The Agile Infrastructure • Private IaaS cloud • OpenStack based • FederatesMeyrin and Wigner • 15,000 hypervisors by 2015 • 300,000 VMs by 2015 • Configuration management tools • Puppet, Foreman Testing as a Service with HammerCloud

  13. Requirements Elastic infrastructure (OpenStack) Cloud orchestrator Code sanitation (Gerrit) Configuration Management (Puppet) Deployment procedures Testing as a Service with HammerCloud

  14. Dynamic testing scheduling • Test is requested (user, API, cron) • Creation of the VMs on demand • Isolation • Reliability • Elasticity • Configuration and startup of the VM • …test runs… • Cleanup and destroy Testing as a Service with HammerCloud

  15. Testing as a Service with HammerCloud

  16. Dynamic testing scheduling • Scheduling on time is hard • IaaS predictable? • Provisioning times • Boot times • HC will learn how is performing • Tool to estimate boot performance Testing as a Service with HammerCloud

  17. Provisioning latency Big improvement on OpenStack Grizzly Dynamic adaption of this time at runtime Testing as a Service with HammerCloud

  18. Shared storage Needed a way to store all the logs Ideally accessible to others NFS for now, HDFS, elasticsearch from the Agile Monitoring? Testing as a Service with HammerCloud

  19. Testing API • Tools will need an API to request tests • And get information. • Already done with LHCbRSS • Athena Nightlies API ongoing Testing as a Service with HammerCloud

  20. Current status • Orchestration framework developed • Currently deploying on OpenStack • OpenStack is now production ready • Thinking about configuration frameworks Testing as a Service with HammerCloud

  21. Conclusions New kind of testing requirements Big infrastructure changes Shift to a new cloudy paradigm Needs a transition period Testing as a Service with HammerCloud

  22. Questions? Testing as a Service with HammerCloud

More Related