* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Marek Domaracky
Survey
Document related concepts
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Deep packet inspection wikipedia , lookup
Network tap wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Video on demand wikipedia , lookup
Distributed operating system wikipedia , lookup
Serial digital interface wikipedia , lookup
List of wireless community networks by region wikipedia , lookup
Airborne Networking wikipedia , lookup
Distributed firewall wikipedia , lookup
Peer-to-peer wikipedia , lookup
Service-oriented architecture implementation framework wikipedia , lookup
Transcript
Welcome the Next Generation Grid-enable Collaboration [email protected] 1 April 23, 2007 Marek Domaracky EVO • Introduction • The EVO concept • Koala 2 April 23, 2007 Marek Domaracky VRVS/EVO Project Timeline Version v0.4 • 1995 Caltech/CMS group started development of a full Web based user interface for videoconferencing. v1.0 • In January 1997, pushed by strong demand from the LHC experiments, the Caltech/CMS group started a production prototype Web-based service named the Virtual Room Videoconferencing System (VRVS). v2.0 • During 1998-2000 VRVS was widely recognized by Research and Education Communities worldwide. It became a core technology for IP-based video & multimedia services in Internet2. v2.5 • July 2001 VRVS is the first system to support multiple protocols (Mbone, H.323, MPEG) for collaboration over IP networks. v3.0 • February 2003, 1st re-architecture of the VRVS System (97% Code redone) – User Authentication, Database, AccessGrid Support, .. v4.0 • December 2006, Release of the next generation collaboration system EVO, a “Globally Distributed Self Managed End- to-End Real-time3 Infrastructure” Current Usage of VRVS Currently: 28,000 Users Registered from 140 Countries, more than 1,400 worldwide meetings involving more than 7,500 different users who start VRVS sessions per month It is the first Very Large Distributed System (using the Grid concept) deployed and used today in Production. 4 April 23, 2007 Marek Domaracky HENP usage since January 2004 From January 2004 to July 2006 , at least one VRVS meeting was booked with one of the following keywords in the title. Representing a minimum of 72 different Physics Experiments that use or have used VRVS: ALICE , ALTA , AMS, ASACUSA, ATHENA, ATLAS, BaBar, Belle, BES, CASA, CAST, CDF, CESR, CLEO, CMS, COMPASS, D0, DELPHI, DIRAC, E325, E94, EDM, EMU, FLARE, FOCUS, GEANT, GEM, GENIUS, GLAST, H1, HARP, HESS, HiRes, ICECUBE, ILC, ISAC, KamLAND, KOPIO, L3, LAND, LEGS, LHC, LIGO, Linear Collider, MACRO, MAGIC, MECO, MINOS, MIPP, Muon, NEMO, OPERA, OWL, PAMELA, PHENIX, PHOBOS, PLANCK, QuarkNet, Qweak, RICE, SAMPLE, SELEX, SigN, SNAP, SNO, STAR, TERA, TOTEM, TWIST, VENUS, VIRGO (ref: http://www.hep.net/experiments/all_sites.html) 5 April 23, 2007 Marek Domaracky Current and Future Challenges • • • • Connecting conference rooms, offices, auditoria, homes, and mobile clients, thus releasing users from locating special purpose conference rooms Interconnecting any standard client protocol using any media including audio, video, document sharing, chat, etc. Operating seamlessly across local area (LAN) and wide area (WAN) IP research and education networks used by HEP, as well as the public Internet Allowing integration into physicists’ daily desktop/laptop working environments, such as the Grid-enabled Analysis Environment developed at Caltech and elsewhere 6 April 23, 2007 Marek Domaracky Process to Developing Collaborative Tools Industry products Global Science Projects Usual Method Lot of Frustrations Integration of some products Get requirements (unique for large scale collaborations) Build a Collaboration System Investment in Support and Developments April 23, 2007 Marek Domaracky 7 End-to-End Self Managed RTC Infrastructure Why can we not achieve total reliability/robustness when deploying a RTC Infrastructure ? • The Real-Time Collaborative environment is a living environment: constantly changing, evolving • In addition, devices/domains/nodes are managed by several independent technical and administrative entities. 8 April 23, 2007 Marek Domaracky Solution ? Solutions ? By creating a ”living” RTC Infrastructure capable to react/adapt to the change of the environment in real-time transparently to the end-user. 9 April 23, 2007 Marek Domaracky The Collaboration Network Infrastructure Apart from VRVS (and its successor EVO), existing conferencing and collaboration products and services are inadequate to meet the usability, quality, scalability, reliability, and cost requirements of large globally distributed collaboration The reason is that the network infrastructure component has been always the central element of the VRVS/EVO architecture design for collaboration Managing the collaboration service Managing the network 10 April 23, 2007 Marek Domaracky EVO Advanced Architecture: Fully Distributed System with no Single Point of Failure Clients Level Distributed Pure Peer-to-Peer (i.e. Skype,.) Infrastructure Level Controlled, Managed and Distributed New architecture (EVO) Servers Peer-to-Peer Centralized April 23, 2007 H.323 or similar tools Marek Domaracky Centralized Servers 11 MonALISA / EVO Integration: End-to-End Self Managed RTC Infrastructure 12 April 23, 2007 Marek Domaracky Software Agents in the Core Infrastructure: Increase functionality and reduce operational manpower Intelligent Software Agents create an Overlay Network Functionality (a partial list): Dynamic registration to high level directory services to provide a global infrastructure view Automatic re-activation of components and services Automatic and secure code update Continuous monitoring of network quality (packet loss, jitter, latency) between its peers and its possible peers Automatic rerouting to obtain the best performance/quality Encryption between central nodes and between node and clients Automatic Alarm notifications when monitored parameters (system or network) go beyond a preset threshold Dynamically provides services (video, audio, data,..) that matches the current resources/capabilities to the end users/applications Access to real-time and historical monitoring data 13 Building an End-to-End Self Managed RTC Infrastructure All Communication channels are tunneled via ONE port (UDP or TCP). Crossing Firewall and NAT environment !! IM H.323 Mbone SIP MPEG Directory Services MonALISA Local PC IM, Chat, Presence, Packet Control Video Audio … Possibility to Encrypt IM, Chat, Presence message AND/OR Video packets AND/OR Audio packets Possibility to Encrypt communication between Panda nodes End-to-End RTC Self Managed Infrastructure 14 Client software agents: To increase reliability and reduce complexity for users Intelligent Software Agents Running in the End-Systems Functionality (Partial List): • Advanced client with Multi-OS support (Java based..) • Automatic detection of system parameters (CPU, Memory,..), hardware components (Audio card, video card, …), service capabilities (video, audio, …), network environment & level of capability (wireless environment, DSL, available bandwidth, …) • Dynamically acquires services (video, audio, data,..) and sets parameters to match the current level of capability-level and available resources to the end-user’s application • Continuously monitors the network quality (packet loss, jitter) • latency), and reroutes packets if and when needed • Automatic Alarm notifications are generated when monitored parameters (system or network) go beyond a preset threshold. 15 April 23, 2007 Marek Domaracky System Features and Functions • Bookings: Book a scheduled meeting; Start an Ad-hoc meeting, invite a • • • • • • • • • buddy to a private meeting, have permanent meeting room IM Presence information, Group and Private concurrent chat sessions UDP and TCP tunneling in one Port. Network Address Translation and Firewall transversal (multiple mechanisms) Encrypt Video and/or Audio and/or IM/Chat and/or other data Meeting management: Become a meeting moderator; Mute/Umute video/audio of a participant, kick-out a participant, add a new participant as moderator Shared files in a virtual meeting space or send a file to individuals Support any type of Video client-protocols: H.323, SIP, Access Grid, Mbone, etc. Whiteboard Record Audio/Video/Chat/Whitebaord/Participants and then playback locally or broadcast to meeting. Multilanguage support, IPv6 Compliant 16 April 23, 2007 Marek Domaracky The Koala Client (Java) Multi-Language Support Bookings On-Going meetings, click to join Presence Buddy Chat Community Automatic Time Zone Adjustment Connection to the Panda 17 Global Scientific Communities subscriptions High Energy Physics Global Scientific Communities Subscribed Communities Search Engine 18 April 23, 2007 Marek Domaracky Apart 19 April 23, 2007 Marek Domaracky Whiteboard and Shared Files Marek Domaracky 20 Booking 21 April 23, 2007 Marek Domaracky H.323 and SIP 22 April 23, 2007 Marek Domaracky Recording and Playback 23 OpenGL based display mode April 23, 2007 Marek Domaracky 24 April 23, 2007 Marek Domaracky 25 EVO: End-to-End Self Managed and Secure RTC Infrastructure H.323 AccessGrid H.323 MCU Messenger -SIP 26 April 23, 2007 Marek Domaracky Thank you Enabling Virtual Organizations [email protected] 27 April 23, 2007 Marek Domaracky