180 likes | 292 Views
Scenario Grid Networks. Overlay networks impact to VPNs WP4 NOBEL. The Grid Scenario. The CERN will use GRID technologies to make computations Computers that will make computations and are located in several type of networks, (Access, Metro, Core)
E N D
Scenario Grid Networks Overlay networks impact to VPNs WP4 NOBEL
The Grid Scenario • The CERN will use GRID technologies to make computations • Computers that will make computations and are located in • several type of networks, (Access, Metro, Core) • The network is owned and operated by one carrier, with • several domain • Several type of transmission is used (ADSL, Ethernet, SONET) • Virtual Private Networks are used (VPN L1, VPN L2, VPN L3) • GMPLS- networks are available • Results will be distributed to several Universities/Countries
Background information of Grid networks • What is the GRID? Several explanations • “A Grid provides an abstraction for resource sharing and • Collaboration across multiple administrative domains…” • (Source: NGG Expert Group 16-Jun-2003 “European Grid • Research 2005-2010) Definition: • Analogy to the term „Power Grid“ • Consistent, pervasive, dependable, transparent access to ressources • Geographically dispersed • Seamless integrated computational and collaborative environment Difference to P2P: • Sometimes difficult (many similarities) • GRIDs are centrally managed • GRIDs are running in more trusted environments • See even chapter 3 in Deliverable 6
Grid evolutions • GRID started in a local premises and will evolve to be a • global service oriented Grid with several types of applications • Local GRID (network 100Mb Ethernet) • Cluster GRID (network 1GbE) • Campus GRID (varying bandwidth) • Global GRID (varying bandwidth)
Some Grid links • http://www.nextgrid.org/ • http://www.nextgrid.org/publications.htm • CERN ( networking) • http://egee-sa2.web.cern.ch/egee%2Dsa2/ • https://edms.cern.ch/file/414132/2.1/DataGrid-07-D7-4-0206-2.0.doc • Requirements • http://egee-sa2.web.cern.ch/egee%2Dsa2/ • Global Grid links • http://www.ngs.ac.uk/ • Nasa Grid • http://www.nas.nasa.gov/About/legacy.html • Particle Physics Data GRID • http://www.ppdg.net/
Grid network topology in Cern Source:http://egee-sa2.web.cern.ch/egee%2Dsa2/
VPNs AND GRID IN NOBEL • Not much have been done in networking area of Grid. • The “BIG FAT PIPE” is asked between Grid sites • We in NOBEL should consider networking aspect • Such as: Dynamicity, Services, Network management, • Control plane, Service identification • To support GRID services VPNs are suitable if • - QoS is needed • - End-to-End protection • - Bandwidth reservations/adjustments • - Separation from other traffic is needed • - High availability
Grid Network in one carrier domain Access network = Transport /VPN Corporate Network =Grid Computers Broadband Access network METRO Network Core network Enterprise network
CPU Server Example : Cern HEP Network Topologyand bandwidth Tomorrow’s network topology Today’s network topology Gigabit Ethernet (WAN) 10 Gigabit Ethernet (WAN) Backbone Backbone 20 * 1000 Mbit/s 200 * 10000 Mbit/s Gigabit Ethernet 10 GBit Ethernet Disk Server Tape Server GBit Ethernet Fast Ethernet CPU Server Disk Server Tape Server
Example of Grid Datafarm • Large scale parallel filesystem • Petabyte scale data computing • Example node: • 18 TB Storage • 6.6GByte/s transfer speed • 1 TFLOP/s
Data Grid Requirements Overview • Applications • HEP – High Energy Physics • LHC – Large Hadron Collider • 12-14 PBytes/Year • Processing power of ~70.000 PCs needed • International connectivity > 10GBit/s • Biology and Medical Applications • Simulations (weather, business models, etc) • Earth Observation Applications • 100 GByte image data/day
Control plane aspects • Signalling proposal • -RSVP signalling in VPN level • -NSIS(Next Steps In Signalling) signalling in GRID level • -Interface is needed between application signalling, resource • management and transport to make bandwidth adjustments.
Management plane aspects in VPN • Resource monitoring in VPN tunnels • How to monitor ? • tunnel head • tunnel tail • transfer entries • QoS resources • Timers (hello intervals) • Errors between boundaries • Error notifications • Recovery functions • Policies
MANAGEMENT- PLANE MANAGEMENT- PLANE USER- PLANE USER- PLANE CONTROL- PLANE CONTROL- PLANE Control and Management plane interaction • User plane send a request to get more bandwidth • The application signalling NSIS should have a signalling interface to Control plane in MPLS/GMPLS • RSVP informs management plane of changed bandwidth E-NNI NSIS control plane NSIS control plane RSVP-TE
Service Identification • Network services and application service • can be identified by • a number (should be standardized) • a filter
Requirements • Very high bandwidth needed • 100 MBit/s to 10/40 GBit/s • Long distances to cover (intercontinental) • Dynamic usage (BoD) • Dynamic topology between nodes • Depending on applications/scenarios bandwidth requirements are changing fast • Provisioning on demand • Point to Point and Point to Multipoint communication needed • Bulk data transfer • Streaming • Group communication • Reliable • Protection, Restoration
How to continue • Collect and analyse requirements from GRID • Make estimation of traffic capacity • Design network topology • Analyse interaction with NM, VPN and GRID application • Expand the scenario in Multi carrier scenario