DOC PREVIEW
CMU CS 15744 - Lecture

This preview shows page 1-2 out of 6 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

PortlandTrend of Data CenterRequirements for future data centerOverall Idea of PortLandQuestions in discussion boardDiscussion pointsJ. K. KimPortlandTrend of Data CenterBy J. Nicholas Hoover , InformationWeek June 17, 2008 04:00 AM 200 million EuroData centers will be larger and larger in the future cloud computing era to benefit from commodities of scale. Tens of thousand  Hundreds of thousands in # of serversMost important things in data center management- Commodities of scale- Keep High utilization of their expensive equipment- Maximize revenue- Saving administration cost- Low power consumption (http://www.energystar.gov/ia/partners/prod_development/downloads/EPA_Datacenter_Report_Congress_Final1.pdf)http://gigaom.com/cloud/google-builds-megadata-center-in-finland/http://www.datacenterknowledge.comRequirements for future data centerTo catch up with the trend of mega data center, DCN technology should meet the requirements as belowHigh ScalabilityTransparent VM migration (high agility)Easy deployment requiring less human administrationEfficient communicationLoop free forwardingFault Tolerant•Current DCN technology can’t meet the requirements.Layer 3 protocol can not support the transparent VM migration.Current Layer 2 protocol is not scalable due to the size of forwarding table and native broadcasting for address resolution.Overall Idea of PortLandAdd a new hostTransfer a packetKey features - Layer 2 protocol based on tree topology - PMAC encode the position information - Data forwarding proceeds based on PMAC- Edge switch’s responsible for mapping between PMAC and AMAC- Fabric manger’s responsible for address resolution- Edge switch makes PMAC invisible to end host- Each switch node can identify its position by itself- Fabric manager keep information of overall topology. Corresponding to the fault, it notifies affected nodes.Questions in discussion boardQuestion about Fabric Manager oHow to make Fabric Manager robust ?oHow to build scalable Fabric Manager ? Redundant deployment or cluster Fabric manager could be solution Question about reality of base-line tree topologyoIs the tree topology common in real world ?  Yes, multi-rooted tree topology has been a traditional topology in data center.[A scalable, commodity data center network architecture Mohammad La-Fares and et el, SIGCOMM ‘08]Discussion pointsoIs the PortLand applicable to other topology ? The Idea of central ARP management could be applicable. To solve forwarding loop problem, TRILL header-like method would be necessary. The benefits of PMAC ? It would require larger size of forwarding table. Question about benefits from VM migrationoVM migration helps to reduce traffic going through aggregate/core switches.oHow about user requirement change?oHow about power consumption ?ETCoFeasibility to mimic PortLand on layer 3 protocol.oHow about using pseudo IP ?oDelay to boot up whole data


View Full Document

CMU CS 15744 - Lecture

Documents in this Course
Lecture

Lecture

25 pages

Lecture

Lecture

10 pages

Lecture

Lecture

10 pages

Lecture

Lecture

45 pages

Lecture

Lecture

48 pages

Lecture

Lecture

19 pages

Lecture

Lecture

97 pages

Lecture

Lecture

39 pages

Lecture

Lecture

49 pages

Lecture

Lecture

33 pages

Lecture

Lecture

21 pages

Lecture

Lecture

52 pages

Problem

Problem

9 pages

03-BGP

03-BGP

13 pages

Lecture

Lecture

42 pages

lecture

lecture

54 pages

lecture

lecture

21 pages

Lecture

Lecture

18 pages

Lecture

Lecture

18 pages

Lecture

Lecture

58 pages

lecture

lecture

17 pages

lecture

lecture

46 pages

Lecture

Lecture

72 pages

Lecture

Lecture

44 pages

Lecture

Lecture

13 pages

Lecture

Lecture

22 pages

Lecture

Lecture

48 pages

lecture

lecture

73 pages

17-DNS

17-DNS

52 pages

Lecture

Lecture

10 pages

lecture

lecture

53 pages

lecture

lecture

51 pages

Wireless

Wireless

27 pages

lecture

lecture

14 pages

lecture

lecture

18 pages

Lecture

Lecture

16 pages

Lecture

Lecture

14 pages

lecture

lecture

16 pages

Lecture

Lecture

16 pages

Lecture

Lecture

37 pages

Lecture

Lecture

44 pages

Lecture

Lecture

11 pages

Lecture

Lecture

61 pages

Multicast

Multicast

61 pages

Lecture

Lecture

19 pages

Lecture

Lecture

8 pages

Lecture

Lecture

81 pages

Lecture

Lecture

9 pages

Lecture

Lecture

6 pages

Lecture

Lecture

63 pages

Lecture

Lecture

13 pages

Lecture

Lecture

63 pages

Lecture

Lecture

50 pages

lecture

lecture

35 pages

Lecture

Lecture

47 pages

Lecture

Lecture

29 pages

Lecture

Lecture

92 pages

Load more
Download Lecture
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?