欢迎来到麦多课文档分享! | 帮助中心 海量文档,免费浏览,给你所需,享你所想!
麦多课文档分享
全部分类
  • 标准规范>
  • 教学课件>
  • 考试资料>
  • 办公文档>
  • 学术论文>
  • 行业资料>
  • 易语言源码>
  • ImageVerifierCode 换一换
    首页 麦多课文档分享 > 资源分类 > PPT文档下载
    分享到微信 分享到微博 分享到QQ空间

    Lecture 6 - Other Distributed Systems.ppt

    • 资源ID:372967       资源大小:1.37MB        全文页数:53页
    • 资源格式: PPT        下载积分:2000积分
    快捷下载 游客一键下载
    账号登录下载
    微信登录下载
    二维码
    微信扫一扫登录
    下载资源需要2000积分(如需开发票,请勿充值!)
    邮箱/手机:
    温馨提示:
    如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
    如需开发票,请勿充值!如填写123,账号就是123,密码也是123。
    支付方式: 支付宝扫码支付    微信扫码支付   
    验证码:   换一换

    加入VIP,交流精品资源
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    Lecture 6 - Other Distributed Systems.ppt

    1、Lecture 6 - Other Distributed Systems,CSE 490h Introduction to Distributed Computing, Spring 2007,Except as otherwise noted, the content of this presentation is licensed under the Creative Commons Attribution 2.5 License.,Outline,DNS BOINC PlanetLab OLPC & Ad-hoc Mesh Networks Lecture content wrap-u

    2、p,DNS: The Distributed System in the Distributed System,Domain Name System,Mnemonic identifiers work considerably better for humans than IP addresses“? Surely you mean 66.102.7.99!”Who maintains the mappings from nameIP?,A Manageable Problem, 2006 Computer History Museum. All rights reserved. puterh

    3、istory.org,In the beginning,Every machine had a file named hosts.txt Each line contained a name/IP mapping New hosts files were updated and distributed via email This clearly wasnt going to scale,DNS Implementations,Modern DNS system first proposed in 1983 First implementation in 1984 (Paul Mockapet

    4、ris) BIND (Berkeley Internet Name Domain) written by four Berkeley students in 1985. Many other implementations today,Hierarchical Naming,DNS names are arranged in a hierarchy:www.cs.washington.eduEntries are either subdomains or hostnames subdomains contain more subdomains, or hosts (up to 127 leve

    5、ls deep!) Hosts have individual IP addresses,Mechanics: Theory,DNS Recurser (client) parses address from right to left Asks root server (with known, static IP address) for name of first subdomain DNS server Contacts successive DNS servers until it finds the host,Mechanics: In Practice,ISPs provide a

    6、 DNS recurser for clients DNS recursers cache lookups for period of time after a requestGreatly speeds up retrieval of entries and reduces system load,BOINC,What is BOINC?,“Berkeley Open Infrastructure for Network Computing” Platform for Internet-wide distributed applications Volunteer computing inf

    7、rastructure Relies on many far-flung users volunteering spare CPU power,Some Facts,1,000,000+ active nodes 521 TFLOPS of computing power 20 active projects (SETIHome, FoldingHome, Malaria Control) and several more in development(Current as of March 2007),Comparison to MapReduce,Both are frameworks o

    8、n which “useful” systems can be built Does not prescribe particular programming style Much more heterogeneous architecture Does not have a formal aggregation step Designed for much longer-running systems (months/years vs. minutes/hours),Architecture,Central server runs LAMP architecture for web + da

    9、tabase End-users run client application with modules for actual computation BitTorrent used to distribute data elements efficiently,System Features,Homogenous redundancy Work unit “trickling” Locality scheduling Distribution based on host parameters,Client software,Available as regular application,

    10、background “service”, or screensaver Can be administered locally or LAN-administered via RPC Can be configured to use only “low priority” cycles,Client/Task Interaction,Client software runs on variety of operating systems, each with different IPC Uses shared memory message passing to transmit inform

    11、ation from “manager” to actual tasks and vice versa,Why Participate?,Sense of accomplishment, community involvement, or scientific duty Stress testing machines/networks Potential for fame (if your computer “finds” an alien planet, you can name it!) “Bragging rights” for computing more units “BOINC C

    12、redits”,Credit & Cobblestones,Work done is rewarded with “cobblestones” 100 cobblestones = 1 day of CPU time for a computer with performance equaling 1,000 double-precision floating-point MIPS (Whetstone) & 1,000 integer VAX MIPS (Dhrystone) Computers are benchmarked by the BOINC system and receive

    13、credit appropriate to their machine,Anti-Cheating Measures,Work units are computed redundantly by several different machines, and results are compared by the central server for consistency Credit is awarded after the internal server validates the returned work units Work units must be returned befor

    14、e a deadline,Conclusions,Versatile infrastructure SETI tasks take a few hours Climate simulation tasks take months Network monitoring tasks are not CPU-bound at all! Scales extremely well to internet-wide applications Provides another flexible middleware layer to base distributed applications on Vol

    15、unteer computing comes with addl considerations (rewards, cheating),PlanetLab,What if you wanted to:,Test a new version of Bittorrent that might generate GBs and GBs of data? Design a new distributed hashtable algorithm for thousands of nodes? Create a gigantic caching structure that mirrored web pa

    16、ges in several sites across the USA?,Problem Similarities,Each of these problems requires: Hundreds or thousands of servers Geographic distribution An isolated network for testing and controlled experiments Developing one-off systems to support these would be Costly Redundant,PlanetLab,A multi-unive

    17、rsity effort to build a network for large-scale simulation, testing, and research “Simulate the Internet”,Usage Stats,Servers: 722+ Slices: 600+ Users: 2500+ Bytes-per-day: 3 - 4 TB IP-flows-per-day: 190M Unique IP-addrs-per-day: 1M,As of Fall, 2006,Project Goals,Supports short- and long-term resear

    18、ch goals System put up “as fast as possible” PlanetLab design evolves over time to meet changing needs PlanetLab is a process, not a result,Simultaneous Research,Projects must be isolated from one another Code from several researchers: Untrustworthy? Possibly buggy? Intellectual property issues? Tim

    19、e-sensitive experiments must not interfere with one another Must provide realistic workload simulations,Architecture,Built on Linux, ssh, other standard tools Provides “normal” environment for application development Hosted at multiple universities w/ separate admins Requires trust relationships wit

    20、h respect to previous goals,Architecture (cont.),Network is divided into “slices” server pools created out of virtual machines Trusted intermediary “PLC” system grants access to network resources Allows universities to specify who can use slices at each site Distributed trust relationships Central s

    21、ystem control Federated control,Resource allocation,PLC authenticates users and understands relationships between principals; issues tickets SHARP system at site validates ticket + returns lease,User Verification,Public-key cryptography used to sign modules entered into PlanetLab X.509 + SSL keys ar

    22、e used by PLC + slices to verify user authenticity Keys distributed “out of band” ahead of time,Final Thoughts,Large system with complex relationships Currently upgrading to version 4.0 New systems (GENI) are being proposed Still provides lots of resources to researchers CoralCache, several other pr

    23、ojects run on PlanetLab,OLPC,“They want to deliver vast amounts of information over the Internet. And again, the Internet is not something you just dump something on. Its not a big truck. Its a series of tubes.”,The Internet is a series of tubes,The internet is composed of a lot of infrastructure: C

    24、lients and servers Routers and switches Fiber optic trunk lines, telephone lines, tubes and trucks And if we map the density of this infrastructure, it probably looks something like this,Photo: cmu.edu,How do we distribute knowledge when there are no tubes?,What if we wanted to share a book? Pass it

    25、 along, door-to-door. What if we wanted to share 10,000 books? Build community library. How about 10 million books? Or 300 copies of one book? A very large library?,Solutions,We need to build infrastructure to make large-scale distribution easy (i.e., computers and networking equipment) We need to b

    26、e cheap Most of those dark spots dont have much money We need reliability where reliable power is costly Again, did you notice that there werent so many lights? Its because theres no electricity!,The traditional solution: a shared computer with Internet,India 75% of people in rural villages 90% of p

    27、hones in urban areas Many villagers share a single phone, usually located in the town post office Likewise, villages typically share a few computers, located at the school (or somewhere with reliable power) Whats the downside to this model? It might provide shared access to a lot of information, but

    28、 it doesnt solve the “300 copies of a book” case,The distributed solution: the XO,AKA: Childrens Machine, OLPC, $100 laptop A cheap ($150) laptop designed for children in developing countries,OLPC = One Laptop Per Child.,Photo: laptop.org,XO design,Low power consumption No moving parts (flash memory

    29、, passive cooling) Dual-mode display In color, the XO consumes 2-3 watts In high-contrast monochrome, less than 1 watt Can be human powered by a foot-pedal Rugged, child-friendly design Low material costs Open-source software,XO networking,The XO utilizes far-reaching, low-power wireless networking

    30、to create ad-hoc mesh networks If any single XO is connected to the Internet, other nearby computers can share the connection in a peer-to-peer scheme Networks can theoretically sprawl as far as ten miles, even connecting nearby villages,XO storage and sharing,XO relies on network for content and co

    31、llaboration Content is stored on a central servers Textbooks Cached websites (Wikipedia) User content Software makes it easy to see other users on the network and share content,XO distribution,XO must be purchased in orders of 1 million units by governments in developing nations (economies of scale

    32、help to lower costs) Governments are responsible for distribution of laptops Laptops are only for children, designed solely as a tool for learning,XO downfalls,Distribution downfalls What about children in developed nations? Sell to developed markets at a higher price to subsidize costs for developi

    33、ng nations. Can governments effectively distribute? What about black markets? OLPC could perhaps partner with local schools and other NGOs to aid in distribution, training and maintenance Too expensive? Some nations can only afford as much $20 per child per year. How can we cater to them?,What can t

    34、he XO achieve?,Today, only 16 percent of the worlds population is estimated to have access to the Internet Develop new markets Microcredit Make small loans to the impoverished without requiring collateral Muhammad Yunus and the Grameen Bank won the 2006 Nobel Peace Prize for their work here The powe

    35、r of the village economy As millions of users come online in developing nations, there will be many new opportunities for commerce. Helps those in developing nations to advance their economies and develop stronger economic models,Why give the XO to children?,UN Millennium Development Goal #2: “achie

    36、ve universal primary education” Empower children to think and compete in a global space Children are a nations greatest resource Backed by a bolstered economy, they will grow to solve other issues (infrastructure, poverty, famine),The Course Again (in 5 minutes),So what did we see in this class? Moo

    37、res law is starting to fail More computing power means more machines This means breaking problems into sub problems Sub-problems cannot interfere with or depend on one another Have to “play nice” with shared memory,MapReduce,MapReduce is one paradigm for breaking problems up Makes the “playing nice”

    38、 easy by enforcing a decoupled programming model Handles lots of the behind-the-scenes work,Distributed Systems & Networks,The network is a fundamental part of a distributed system Have to plan for bandwidth, latency, etc Wed like to think of the network as an abstraction Sockets = pipes RPC looks l

    39、ike a normal procedure call, handles tricky stuff under the hood Still have to plan for failures of all kinds,Distributed Filesystems,The network allows us to make data available across many machines Network file systems can hook into existing infrastructure Specialized file systems (like GFS) can o

    40、ffer better performance with loss of generality Raises issues of concurrency, process isolation, and how to combat stale data,And finally,There are lots of distributed systems out there MapReduce, BOINC, MPI, several other architectures, styles, problems to solve You might be designing an important one soon yourself!,


    注意事项

    本文(Lecture 6 - Other Distributed Systems.ppt)为本站会员(ideacase155)主动上传,麦多课文档分享仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文档分享(点击联系客服),我们立即给予删除!




    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

    copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
    备案/许可证编号:苏ICP备17064731号-1 

    收起
    展开