1 / 27

Welcome

Welcome. the Next Generation Grid-enable Collaboration. Marek.Domaracky@cern.ch. EVO. Introduction The EVO concept Koala. VRVS/EVO Project Timeline. Version. v0.4. 1995 Caltech/CMS group started development of a full Web based user interface for videoconferencing.

reed
Download Presentation

Welcome

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. Welcome the Next Generation Grid-enable Collaboration Marek.Domaracky@cern.ch Marek Domaracky

  2. EVO • Introduction • The EVO concept • Koala Marek Domaracky

  3. VRVS/EVO Project Timeline Version v0.4 • 1995 Caltech/CMS group started development of a full Web • based user interface for videoconferencing. • 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). • 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. • July 2001 VRVS is the first system to supportmultiple protocols • (Mbone, H.323, MPEG) for collaboration over IP networks. • February 2003, 1stre-architecture of the VRVS System (97% Code • redone) – User Authentication, Database, AccessGrid Support, .. • December 2006, Release of the next generation collaboration system EVO, a “Globally Distributed Self Managed End- to-End Real-time Infrastructure” v1.0 v2.0 v2.5 v3.0 v4.0 3

  4. Current Usage of VRVS • Currently: • 28,000Users 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 Marek Domaracky

  5. HENP usage since January 2004 From January 2004 to July 2006 , at least one VRVS meeting was booked with one of the following keywordsin 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) Marek Domaracky

  6. Current and Future Challenges • Connectingconference rooms, offices, auditoria, homes, and mobile clients, thus releasing users from locating special purpose conference rooms • Interconnectingany standard client protocol using any media including audio, video, document sharing, chat, etc. • Operating seamlesslyacross local area (LAN) and wide area (WAN) IPresearch 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 Marek Domaracky

  7. 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 Marek Domaracky

  8. 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. Marek Domaracky

  9. Solution ? Solutions ? • By creating a ”living” RTC Infrastructure capable toreact/adapt to the change of the environment in real-time transparently to the end-user. Marek Domaracky

  10. 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 componenthas been always the central element of theVRVS/EVO architecture design for collaboration Managing the collaboration service Managing the network Marek Domaracky

  11. 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 H.323 or similar tools Centralized Servers Centralized Marek Domaracky

  12. MonALISA / EVO Integration:End-to-End Self Managed RTC Infrastructure Marek Domaracky

  13. Software Agents in the Core Infrastructure:Increase functionality and reduce operational manpower Intelligent Software Agents create an Overlay Network • Functionality (a partial list): • Dynamic registrationto high level directory services to provide a global infrastructure view • Automatic re-activation of components and services • Automatic and securecode update • Continuousmonitoring of network quality (packet loss, jitter, latency) between its peers and its possible peers • Automatic reroutingto obtain the best performance/quality • Encryptionbetween 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 currentresources/capabilities to the end users/applications • Access toreal-time and historical monitoring data

  14. 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 !! Directory Services MonALISA IM H.323 Mbone SIP MPEG … 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

  15. Client software agents: To increase reliability and reduce complexity for users Intelligent Software Agents Running in the End-Systems • Functionality (Partial List): • Advancedclientwith Multi-OS support (Java based..) • Automatic detectionofsystem parameters(CPU, Memory,..),hardware components(Audio card, video card, …),service capabilities(video, audio, …),network environment & level ofcapability(wireless environment, DSL, available bandwidth, …) • Dynamicallyacquires services (video, audio, data,..) and sets parameters to match the currentlevel of capability-level and available resourcesto the end-user’s application • Continuously monitorsthe network quality (packet loss, jitter) • latency), andreroutes packetsif and when needed • Automatic Alarm notificationsare generated when monitored parameters (system or network) go beyond apreset threshold. Marek Domaracky

  16. 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 Presenceinformation, Group and Privateconcurrent chat sessions • UDP and TCP tunneling in one Port.Network Address Translation and Firewall transversal (multiple mechanisms) • EncryptVideo and/or Audio and/or IM/Chat and/or other data • Meeting management: Become ameeting moderator; Mute/Umute video/audio of a participant, kick-out a participant, add a new participant as moderator • Shared filesin a virtual meeting space or send a file to individuals • Support any type ofVideo client-protocols: H.323, SIP, Access Grid, Mbone, etc. • Whiteboard • Record Audio/Video/Chat/Whitebaord/Participants and then playbacklocally or broadcast to meeting. • Multilanguagesupport, IPv6Compliant Marek Domaracky

  17. 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

  18. Global Scientific Communities subscriptions High Energy Physics Global Scientific Communities Subscribed Communities Search Engine Marek Domaracky

  19. Apart April 23, 2007 Marek Domaracky

  20. Whiteboard and Shared Files Marek Domaracky

  21. Booking April 23, 2007 Marek Domaracky

  22. H.323 and SIP April 23, 2007 Marek Domaracky

  23. Recording and Playback

  24. OpenGL based display mode Marek Domaracky

  25. Marek Domaracky

  26. H.323 MCU Messenger -SIP EVO EVO: End-to-End Self Managed and Secure RTC Infrastructure H.323 AccessGrid Marek Domaracky

  27. Thank you Enabling Virtual Organizations evobeta@vrvs.org Marek Domaracky

More Related