1 / 16

DIS Project Proposal: Robust Content Distribution Network

DIS Project Proposal: Robust Content Distribution Network. By Software Implementation. R92725016 周亦方 R92725050 莊豐源 R92725051 黃世翔. 資管所 研一. Motivation. The cooperative servers of super enterprise lacks: Load balancing Transparency Fail over Data consistency

libba
Download Presentation

DIS Project Proposal: Robust Content Distribution Network

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. DIS Project Proposal: Robust Content Distribution Network By Software Implementation R92725016 周亦方 R92725050 莊豐源 R92725051 黃世翔 資管所 研一

  2. Motivation • The cooperative servers of super enterprise lacks: • Load balancing • Transparency • Fail over • Data consistency • Status of other server peer

  3. A Generic CDN

  4. Scenario • Websites of an super enterprise have common contents and specific contents. • Main load bottleneck is specific content. • Common contents (*.html, …): served by web servers. • Specific contents (*. mpg, *.tar.gz, *.zip, …): served by CDN nodes. Ex: http://www.cpp.com

  5. Goals & System Description • Distribute the common contents with several web servers by the nature of DNS (LB, FO) • Distribute the specific contents with CDN nodes (LB, FO) Ex: http://www.cdn.com

  6. User can access the most efficient CDN node without location knowledge (TP). • The specific contents of CDN nodes are synchronized (DC). • The ability of CDN nodes are equal, so that when the root node fails we can elect a new root. (FO) • Root node can monitor other nodes, but other nodes also have the ability. (ST)

  7. Diagram System Diagram – ButterFly, RFC 9999 http://www.cpp.com/index.html http://www.cdn.com/www.cpp.com/matrix4.mpg

  8. Rules of Selecting the Most Efficient CDN Node: • Select the most efficient CDN node by judging where client source IP address (or ISP) belongs to. • Internet routing tables (BGP tables) • Round trip time estimates • Other measurement data…

  9. System Requirements (Sever-Side) • Any OS running Java Virtual Machine (Linux) • Any web server (application server) supporting J2EE (Apache + Tomcat) • DNS server (bind)

  10. Implementation • Web Servers: Several Apache (+ Tomcat) web servers serving common contents • CDN nodes: Several Apache web servers (or FTP servers) serving specific contents • DNS servers: bind • CDN module: A Java multi-thread pre-DNS server written by us, which can be combined with bind DNS server to select the best CDN node for client user. • Peer health status monitor: mirmon • Data consistency: rsync

  11. Monitor CDN Nodes: (mirmon) Mirmon helps administrators in keeping an eye on the mirror sites. http://www.cs.uu.nl/people/henkp/mirmon/

  12. Maintain Data Consistency: (rsync) • http://rsync.samba.org/ • rsync is an open source utility that provides fast incremental file transfer. rsync is freely available under the GNU General Public License

  13. Project Participants • CBO (Francis 亦方): • Chief Beautiful Officer • CHO (Grant 世翔): • Chief Handsome Officer • QOO (Frank 豐源): • Queen of Officers

  14. Project Timeline

  15. 謝謝您

More Related