1 / 29

VRVS Next Development (1/2)

Next Generation Grid Enable Collaborative System. VRVS Next Development (1/2). Session Introduction: P. Galvez ; 5’ Current and New Collaborative Architecture (From VRVS to EVO): P. Galvez ; 15’

beata
Download Presentation

VRVS Next Development (1/2)

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. Next Generation Grid Enable Collaborative System VRVS Next Development (1/2) • Session Introduction: P. Galvez; 5’ • Current and New Collaborative Architecture (From VRVS to EVO): P. Galvez; 15’ • MonALISA (A Monitoring Agents Using Large Integrated Services Architecture) – I. Legrand; 15’ (by Video) • Advanced Collaborative End Applications: P. Farkas; 15’ • Demonstration: 20’ • EVO: a End-to-End Secure and Self-Adaptive Real-Time Collaboration Infrastructure • We will try to break the system !, auto recovery, redundancy,… • Questions: 5’

  2. VRVS worldwide collaborative production service • From VRVS to EVO • Philippe Galvez • California Institute of Technology • I2 Spring Meeting, May 4th, 2005

  3. VRVS Next Development (1/2) Outlines • VRVS: Background Information • VRVS Deployment; • VRVS Usage and Statistics • From VRVS To EVO: An End-to-End Self Managed RTC Infrastructure

  4. VRVS: What it is ? • VRVS is arealtime distributed systemwhich provides ascalable communication infrastructureforlarge collaborationdispersed all over the world. • Different technologies and protocolsare supported (and mixed) and allow users to connect their preferred videoconference. • SupportsMbone, H.323, SIP, QuickTime, Access Grid, JMF and MPEG2. • The system is composed of1 main serverandseveral reflectors(network servers) spread around the world.

  5. VRVS Web Service Design • Unified Web User Interfaceto schedule and join/leave a meetingindependently of the application. • Multi-platform:Windows, Linux, MacOS and Unix. • Easy to use: Everybody knows how to click on a web page today. • Virtual Room Concept, Scheduling; Create a virtual space were people can exchange real-time information. • Join or Leave a Collaborative session anytime. Do not need to know in advance how many participants and booked ports capacity. Just announce the meeting and people will join from anywhere. • FullDocumentation and Tutorial • Self service:Don’t need a technician or expert to organize and join a conference.

  6. VRVS Reflectors Deployment World Wide 82 Reflectors deployed world wide

  7. VRVS registered users and current usageuntil May 4th, 2005 15,700 different Users Registered from120 Countries Switzerland, Germany, Brazil, UK, Slovakia, Taiwan, Chile, Greece, Argentina, Japan, Russia, Canada, etc… • Average of 1100 world wide meetings involving more than 4500 users (total 6000 hours) per month

  8. VRVS Worldwide Collaboration The VRVS team collaborates withResearch and Education Networks and major Research Projectsaround the globe to provide the academic community with aunique and reliable real-time infrastructure supporting all protocols for advanced collaboration • VRVS National Research and Education Network (NREN) Communities: • Internet2(U.S),GEANT2/DANTE(Europe),RedIRIS(Spain),RNP(Brazil),REUNA(Chile),RENATER(France),SANET(Slovakia),INFN(Italy),FUNET(Finland),REACCIUN2 (Venezuela) and AMPATH(America). Others are in process. • VRVS Disciplines communities:HENP, ASTRO, FUSION, MEDICAL • VRVS Particular Project Communities:VRVS TEAM, ACCESSGRID,..

  9. From a Boeing 747 at 12,000 m over the Ocean

  10. What’s Next ?

  11. Robustness ? From VRVS To EVO: End-to-End Self Managed RTC Infrastructure Developing/Deploying a Very RobustandScalable Real-Time Collaborative(RTC) Infrastructure is a real problem thatno-onewas able to fix yet ! • Main critical RTC issues: • Manageability • Reliability • Scalability • Security • Functionality / Usability

  12. From VRVS To EVO: End-to-End Self Managed RTC Infrastructure • What’s wrong ? 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 managing by several independent technical and administrative entities

  13. Solutions ? • By creating a“living” RTC Infrastructurecapable toreact/adaptto the change of theenvironment inreal-time transparentlyto theend-user

  14. Building a Scalable RTC Infrastructure • Multicast Network: It is not any more a global solution • After more than 10 years of development/deployment, It reaches its maximum level of reliability/robustness • It is just a transport mechanism • No QoS • No awareness of the Application level • No data processing as required by the some application (mixing audio, select video streams, ….) • Extremely difficult to troubleshot because it crosses several administrative domains • Today’s solution: • Building an Overlay Network by deploying intelligent Software Agents communicating using Unicast connections and capable of using Multicast transport when it makes more sense

  15. Building a Core RTC Infrastructure Directory Services Directory Services Register the Service offered Notification to others members Access Monitoring Information and Remote Administrated the Different Services Monitoring Service • Send Monitoring Information in real-time • CPU, Memory, Network Status, Packet loss, Latency/Jitter with its peers, number of clients connected, etc.. • Send Alarms to Administrators: Packet lost, CPU high, etc.. Overlay Network built using Intelligent Software Agent: Panda GUI for Monitoring

  16. Outlines

  17. Building an End-to-End Self Managed RTC Infrastructure Directories Services • (1) Give me the best Panda nodes available: • Best network connectivity • Best latency/jitter • no packet lost • minimum of client clients connected (load balancing) (2) 3 best nodes provided (5) Publish local monitoring information Koala: A Software Agent running In Computer End-User IM H.323 Mbone SIP MPEG … • Local Monitoring Agent • Provides information in real-time: • CPU, Memory, Network Status, Packet loss, Latency/Jitter to/from its connected Panda • Send Alarms: Packet lost, CPU high, etc.. • AND takes automatic actions to correct the problem (3) Check network quality (Latency, jitter, packet lost) and select the best one (4) Connect to the best node RTC Core Infrastructure End-to-End RTC Self Managed Infrastructure

  18. 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 !! Directories Services IM H.323 Mbone SIP MPEG … Local Computer IM, Chat, Presence, Control Packet Video Audio Logging and scheduling packets information communication done via the tunneled connection with the Panda Possibility to Encrypt IM, Chat, Presence message AND/OR Video packet AND/OR Audio packet Possibility to Encrypt communication between Panda nodes End-to-End RTC Self Managed Infrastructure

  19. The Koala Client (Java) Multi-Languages Support Bookings On-Going meetings, click to join Chat Presence Automatic Time Zone Adjustment Connection to the Panda

  20. H.323 MCU Messenger -SIP EVO EVO: End-to-End Self Managed and Secure RTC Infrastructure AG H.323 EVO

  21. Demonstration: Let’s break the System ! 3- Overloading the user machine and see automatic actions to adjust the problem 1- Breaking a core node and automatic topology reconnection X 3 1 X X 2 2 - Breaking a Panda node where Users are connected and automatic reconnection to a new Panda node

  22. Thank you www.VRVS.org Contact@VRVS.org Support@VRVS.org

  23. Additional Slides

  24. Panda Software Agent functionalities • It will provide communication channel not only for audio/video but • also for shared applications, Instant Messaging. • Dynamic registration to high level directory services • 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 reflectors and between reflector and VRVS • 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 • Provides access to real-time and historical data

  25. Koala Software Agent Functionality • New Java-based VRVS client that will perform Dynamic • Registration to high level directory services – (Multi-OS support) • Automatic detection of the system parameters (CPU, Memory,..) • hardware components (Audio card, video card, …), services • capabilities (video, audio, …), network environment and • capabilities (wireless environment, DSL, available bandwidth, …) • Dynamicallygets services (video, audio, data,..) that matches the • current resources/capabilities to end users/applications • Continuous monitoring of network quality (packet loss, jitter) • latency) and Automatic rerouting of packets • Automatic Alarm notifications when monitored parameters • (system or network) go beyond a preset threshold.

  26. GUI: Koala Software Agent www.VRVS.org Contact@VRVS.org Support@VRVS.org

  27. Admin GUI with Panda and Koala nodes

  28. Monalisa / EVO GUI

  29. Additional Admin. GUI Snapshot

More Related