systemimager and bitt orrent a p2p approach to large
play

SystemImager and BitT orrent: a p2p approach to large scale OS - PowerPoint PPT Presentation

SystemImager and BitT orrent: a p2p approach to large scale OS deployment Andrea Righi <a.righi@cineca.it> Bernard Li <bli@bcgsc.ca> Brian Elliott Finley <brian@thefinleys.com> Erich Focht <efocht@hpce.nec.com> LinuxT


  1. SystemImager and BitT orrent: a p2p approach to large scale OS deployment Andrea Righi <a.righi@cineca.it> Bernard Li <bli@bcgsc.ca> Brian Elliott Finley <brian@thefinleys.com> Erich Focht <efocht@hpce.nec.com> LinuxT ag 2007 (May 29 – Jun 2)

  2. The problem You have to install a lot of computers ✔ PC labs, ✔ Server farms, ✔ HPC clusters, ✔ Complex grid-computing environments, ✔ Etc. But you don't have enough time! LinuxT ag 2007 (May 29 – Jun 2)

  3. A practical example LinuxT ag 2007 (May 29 – Jun 2)

  4. The tool SystemImager is a software which automates GNU/Linux installs, software distributions and production deployment LinuxT ag 2007 (May 29 – Jun 2)

  5. Major Goals Support all Linux distributions Support a large number of architectures Make it easy to add support for new distro and architectures Make it solve massive installation problems Create a centralized point of installation and maintenance LinuxT ag 2007 (May 29 – Jun 2)

  6. What does it do for me? System Installation System Updates Build replicants of machines File system or block device migration LinuxT ag 2007 (May 29 – Jun 2)

  7. Advantage of SystemImager File-oriented approach ✔ Distribution agnostic ✔ Hardware independence ✔ Filesystem independence ✔ Plain filesystem dump: exclude swap space or unused partitions ✔ Block device independence ✔ Live customization (manipulate cloned filesystems directly) LinuxT ag 2007 (May 29 – Jun 2)

  8. Basic concepts LinuxT ag 2007 (May 29 – Jun 2)

  9. Basic concept: image Image: ✔ Live snapshot of a machine containing files and directories from the root of that machine's filesystem ✔ chroot -able filesystem stored in /var/lib/systemimager/images/$NAME ✔ Examples: ✔ /var/lib/systemimager/images/RHEL4 ✔ /var/lib/systemimager/images/Debian_Etch ✔ /var/lib/systemimager/images/HPC_1.0 ✔ ... LinuxT ag 2007 (May 29 – Jun 2)

  10. Basic concept: image server Image Server: ✔ a server that has all the images available for the installation ✔ “ Jukebox ” of images LinuxT ag 2007 (May 29 – Jun 2)

  11. Basic concept: client Client: ✔ a machine to be auto-installed with a (single) selected image ✔ Example: the dancing penguins are the clients :-) LinuxT ag 2007 (May 29 – Jun 2)

  12. Basic concept: transport Transport: ✔ the protocol used to distribute images from the image server to the clients ✔ push/pull/p2p approach ✔ Examples: ✔ rsync, multicast, SSL, BitT orrent, ... LinuxT ag 2007 (May 29 – Jun 2)

  13. Application stack (SIS) Image Server (SystemImager) HPC clusters HPC-1.0 RHEL4 SUSE10 Debian4 HA-clusters SystemImager transports + SystemConfigurator Web farms Software (Debootstrap, YaST, Golden client PC labs yum, SystemInstaller, ...) LinuxT ag 2007 (May 29 – Jun 2)

  14. Transports LinuxT ag 2007 (May 29 – Jun 2)

  15. rsync transport rsync (plain / SSL encrypted): ✔ Client-server approach ✔ Limited in scalability ✔ Limited in reliability with a lot of clients ✔ Max Theoretical Bandwidth: Us / N LinuxT ag 2007 (May 29 – Jun 2)

  16. rsync diagram Image server Upload bandwidth = U s Client 1 Client 2 ... Client N Download bandwidth = U s / N LinuxT ag 2007 (May 29 – Jun 2)

  17. Multicast (Flamethrower) transport Flamethrower: ✔ Multicast approach: ✔ Perfect scalability ✔ But limited in reliability ✔ Max Theoretical Bandwidth: Us LinuxT ag 2007 (May 29 – Jun 2)

  18. Multicast (Flamethrower) diagram Image server Upload bandwidth = U s Client 1 Client 2 ... Client N Download bandwidth = U s LinuxT ag 2007 (May 29 – Jun 2)

  19. BitTorrent overview BitT orrent is a TCP/IP p2p oriented protocol designed for transferring files Peers connect to each other directly to send and receive chunks of data There is a central server (tracker) which coordinates the action of all such peers The tracker does not have any knowledge of the contents of the files being distributed Users upload ( transmit outbound ) at the same time they are downloading ( receiving inbound ) LinuxT ag 2007 (May 29 – Jun 2)

  20. BitTorrent transport BitT orrent: ✔ p2p approach: scalability && reliability ✔ Qiu and Srikant model ✔ T otal upload rate:  x  t  y  t  ✔ Steady state: d x  t  ✔ x(t) downloaders => = 0 d t d x  t  ✔ y(t) uploaders => = 0 d t ✔ Max Theoretical Bandwidth: ✔ Us (steady state) LinuxT ag 2007 (May 29 – Jun 2)

  21. BitTorrent diagram Image server (+tracker) Upload bandwidth = U s Client 1 Client 2 ... Client N Download bandwidth = U s (in steady state) LinuxT ag 2007 (May 29 – Jun 2)

  22. BitTorrent fun! Image server LinuxT ag 2007 (May 29 – Jun 2)

  23. T estbed environment LinuxT ag 2007 (May 29 – Jun 2)

  24. BCX/5120 cluster @ IBM BCX/5120, with 5120 cores, is the largest computer in Italy for Scientific Computing 2 dual-core AMD Opteron(tm) 2.4GHz, 8GB RAM per node It is the 44th most powerful computer in the world (TOP500). LinuxT ag 2007 (May 29 – Jun 2)

  25. BCX network topology IBM e326m Cisco Catalyst 6513 (image server) 1 Gb/s link 1 Gb/s x 4 uplinks IBM LS21 switch IBM Bladecenter H (from 1 up to 11) BladeCenter H internal bus (1Gb/s) IBM Blade LS21 (x 14) 1 14 ... LinuxT ag 2007 (May 29 – Jun 2)

  26. Experimental results LinuxT ag 2007 (May 29 – Jun 2)

  27. Deployment time LinuxT ag 2007 (May 29 – Jun 2)

  28. Rsync: 50 clients (download rate) LinuxT ag 2007 (May 29 – Jun 2)

  29. Multicast: 50 clients (download rate) LinuxT ag 2007 (May 29 – Jun 2)

  30. BitTorrent: 50 clients (download rate) LinuxT ag 2007 (May 29 – Jun 2)

  31. Rsync: 50 clients (aggregated bandwidth) LinuxT ag 2007 (May 29 – Jun 2)

  32. Multicast: 50 clients (aggregated bandwidth) LinuxT ag 2007 (May 29 – Jun 2)

  33. BitTorrent: 50 clients (aggregated bandwidth) LinuxT ag 2007 (May 29 – Jun 2)

  34. Conclusion LinuxT ag 2007 (May 29 – Jun 2)

  35. Advantages Quicker deployment of images Safer deployment (better error handling) Less load on the image server ✔ no need to buy a powerful machine LinuxT ag 2007 (May 29 – Jun 2)

  36. Disadvantages No time to have a coffee while the clients are imaging More disk space consumption! ✔ tarballs of images Images and tarballs must be kept in-sync ✔ Re-generate tarball and .torrent at each image change LinuxT ag 2007 (May 29 – Jun 2)

  37. Future work Optimize performance in LAN environments and dedicated HPC networks Improve security (encryption of BT tarballs) Virtual cluster deployment (re-imaging using the same physical resource pool) Exploit the p2p approach to create distributed and redundant repositories of custom image Use BT transport also for updates (pushing changes/differences of images) => a path to image version management LinuxT ag 2007 (May 29 – Jun 2)

  38. References Web: ✔ http://www.systemimager.org Mailing list: ✔ sisuite-users@lists.sourceforge.net ✔ sisuite-devel@lists.sourceforge.net IRC: ✔ #sisuite (irc.freenode.net) LinuxT ag 2007 (May 29 – Jun 2)

  39. T ank you for attending!!! LinuxT ag 2007 (May 29 – Jun 2)

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend