Welcome

1April 23, 2007 Marek Domaracky

the Next Generation Grid-enable Collaboration

[email protected]

WelcomeWelcome


EVOEVO

• Introduction

• The EVO concept

• Koala

33

VRVS/EVO Project TimelineVRVS/EVO Project TimelineVRVS/EVO Project TimelineVRVS/EVO Project Timeline

• 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 support multiple protocols (Mbone, H.323, MPEG) for collaboration over IP networks.

• February 2003, 1st re-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”

v0.4

v1.0

v2.0

v2.5

v3.0

v4.0

Version

44

CurrentlyCurrently: :

28,00028,000 Users Registered from Users Registered from 140140 Countries, Countries, more than more than 1,400 1,400 worldwide meetings involving worldwide meetings involving more than more than 7,5007,500 different users who start VRVS different users who start VRVS sessions per month sessions per month

It is the first It is the first Very Large Distributed System Very Large Distributed System (using the Grid concept) deployed and used (using the Grid concept) deployed and used today in Production.today in Production.

Current Usage of VRVSCurrent Usage of VRVSCurrent Usage of VRVSCurrent Usage of VRVS

April 23, 2007 Marek Domaracky

5

HENP usage since January 2004HENP 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)


6

• 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

Current and Future ChallengesCurrent and Future ChallengesCurrent and Future ChallengesCurrent and Future Challenges


7

Process to Developing Collaborative ToolsProcess to Developing Collaborative ToolsProcess to Developing Collaborative ToolsProcess to Developing Collaborative Tools

Global Science Projects

Industry products

Usual Method Lot of Frustrations

Get requirements (unique for large scale collaborations) Build a Collaboration System

Integration of some products

Investment in Support and Developments



End-to-End Self Managed RTC End-to-End Self Managed RTC InfrastructureInfrastructure

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.


Solution ?Solution ?

By creating a By creating a ”living” RTC Infrastructure ”living” RTC Infrastructure capable tocapable to react/adapt react/adapt to the change of the to the change of the environment in environment in real-time transparently real-time transparently to the to the end-userend-user..

Solutions ?

10

The Collaboration Network InfrastructureThe Collaboration Network InfrastructureThe Collaboration Network InfrastructureThe Collaboration Network Infrastructure

Apart from VRVS (and its successor EVO), existing Apart from VRVS (and its successor EVO), existing conferencing and collaboration products and services are conferencing and collaboration products and services are inadequate to meet the inadequate to meet the usability, quality, scalability, usability, quality, scalability, reliability, and cost requirementsreliability, and cost requirements of of large globally large globally distributed collaborationdistributed 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 serviceManaging the collaboration service

Managing the networkManaging the network


11Centralized ServersH.323 or similar tools

Pure Peer-to-Peer (i.e. Skype,.)

New architecture (EVO)Servers Peer-to-Peer

EVO Advanced Architecture:EVO Advanced Architecture:Fully Distributed System with no Single Point of FailureFully Distributed System with no Single Point of FailureEVO Advanced Architecture:EVO Advanced Architecture:Fully Distributed System with no Single Point of FailureFully Distributed System with no Single Point of Failure

Clients Level

Infrastructure Level

Centralized

Distributed

Controlled, Managed andDistributed


12

MonALISA / EVO Integration:MonALISA / EVO Integration:End-to-End Self Managed RTC InfrastructureEnd-to-End Self Managed RTC InfrastructureMonALISA / EVO Integration:MonALISA / EVO Integration:End-to-End Self Managed RTC InfrastructureEnd-to-End Self Managed RTC Infrastructure


13

Functionality (a partial list):Functionality (a partial list): Dynamic registrationDynamic registration to high level directory services to to high level directory services to provide a global infrastructure view provide a global infrastructure view Automatic re-activation Automatic re-activation of components and servicesof components and services Automatic and secureAutomatic and secure code updatecode update ContinuousContinuous monitoring of network quality (packet loss,monitoring of network quality (packet loss, jitter, latency) between its peers and its possible peers jitter, latency) between its peers and its possible peers Automatic reroutingAutomatic rerouting to obtain the best performance/qualityto obtain the best performance/quality EncryptionEncryption between central nodes and between node and clientsbetween central nodes and between node and clients Automatic Alarm notifications Automatic Alarm notifications when monitored parameters when monitored parameters

(system or network) go beyond a (system or network) go beyond a preset thresholdpreset threshold Dynamically provides servicesDynamically provides services (video, audio, data,..) that matches(video, audio, data,..) that matches the current the current resources/capabilities resources/capabilities to the end users/applicationsto the end users/applications Access toAccess to real-time and historical monitoring datareal-time and historical monitoring data

Software Agents in the Core Infrastructure:Software Agents in the Core Infrastructure:Increase functionality and reduce operational manpowerIncrease functionality and reduce operational manpower

Software Agents in the Core Infrastructure:Software Agents in the Core Infrastructure:Increase functionality and reduce operational manpowerIncrease functionality and reduce operational manpower

Intelligent Software Agents create an Overlay Network

14

Directory Services

IMH.323MboneSIPMPEG…

Local PC

End-to-End RTC Self Managed Infrastructure

IM, Chat, Presence, Packet Control

Video Audio

Possibility to EncryptIM, Chat, Presence messageAND/OR Video packetsAND/OR Audio packets

All Communication channels are tunneled via ONE port (UDP or TCP). Crossing Firewall and NAT environment !!

Possibility to Encrypt communication between Panda nodes

Building an End-to-End Self Managed RTC Building an End-to-End Self Managed RTC InfrastructureInfrastructure

Building an End-to-End Self Managed RTC Building an End-to-End Self Managed RTC InfrastructureInfrastructure

MonALISA

15

Functionality (Partial List):Functionality (Partial List):• AdvancedAdvanced clientclient with Multi-OS support (Java based..)with Multi-OS support (Java based..)

• Automatic detectionAutomatic detection ofof system parameterssystem parameters (CPU, Memory,..),(CPU, Memory,..), hardware componentshardware components (Audio card, video card, …),(Audio card, video card, …), service service capabilitiescapabilities (video, audio, …),(video, audio, …), network environment & level ofnetwork environment & level of capabilitycapability (wireless environment, DSL, available bandwidth, …)(wireless environment, DSL, available bandwidth, …)

• DynamicallyDynamically acquires services (video, audio, data,..) and sets acquires services (video, audio, data,..) and sets parameters to match the currentparameters to match the current level of capability-level and available level of capability-level and available resourcesresources to the end-user’s applicationto the end-user’s application

• Continuously monitorsContinuously monitors the network quality (packet loss, jitter)the network quality (packet loss, jitter)

• latency), andlatency), and reroutes packetsreroutes packets if and when neededif and when needed

• Automatic Alarm notificationsAutomatic Alarm notifications are generated when monitored are generated when monitored parameters (system or network) go beyond aparameters (system or network) go beyond a preset threshold.preset threshold.

Client software agents: Client software agents:

To increase reliability and reduce complexity for usersTo increase reliability and reduce complexity for users Client software agents: Client software agents:

To increase reliability and reduce complexity for usersTo increase reliability and reduce complexity for users

Intelligent Software Agents Running in the End-Systems


16

• BookingsBookings:: Book a scheduled meeting; Start an Ad-hoc meeting, invite a Book a scheduled meeting; Start an Ad-hoc meeting, invite a buddy to a private meeting, have permanent meeting roombuddy to a private meeting, have permanent meeting room

• IM PresenceIM Presence informationinformation, , Group and PrivateGroup and Private concurrent chat sessionsconcurrent chat sessions• UDP and TCP tunneling in one Port.UDP and TCP tunneling in one Port. Network Address Translation and Network Address Translation and

Firewall transversal (multiple mechanisms)Firewall transversal (multiple mechanisms)• EncryptEncrypt Video and/or Audio and/or IM/Chat and/or other dataVideo and/or Audio and/or IM/Chat and/or other data• Meeting management: Become aMeeting management: Become a meeting moderatormeeting moderator; ; Mute/Umute Mute/Umute

video/audio of a participant, kick-out a participant, add a new participant video/audio of a participant, kick-out a participant, add a new participant as moderatoras moderator

• Shared filesShared files in a virtual meeting space or send a file to individualsin a virtual meeting space or send a file to individuals• Support any type ofSupport any type of Video client-protocolsVideo client-protocols: H.323, SIP, : H.323, SIP,

Access Grid, Mbone, etc. Access Grid, Mbone, etc. • WhiteboardWhiteboard • Record Record Audio/Video/Chat/Whitebaord/Participants and then Audio/Video/Chat/Whitebaord/Participants and then playbackplayback

locallylocally or or broadcastbroadcast to meeting. to meeting. • MultilanguageMultilanguage supportsupport, , IPv6IPv6 CompliantCompliant

System Features and FunctionsSystem Features and FunctionsSystem Features and FunctionsSystem Features and Functions


17Connection to the Panda

Automatic Time Zone Adjustment

On-Going meetings, click to join

Multi-Language Support

Presence

Chat

Bookings

The Koala Client (Java)The Koala Client (Java)The Koala Client (Java)The Koala Client (Java)

Community

Buddy

18

Subscribed Communities

High Energy Physics

Search Engine

Global Scientific Communities subscriptionsGlobal Scientific Communities subscriptionsGlobal Scientific Communities subscriptionsGlobal Scientific Communities subscriptions

Global Scientific Communities


19


ApartApart

20Marek Domaracky

Whiteboard and Shared FilesWhiteboard and Shared Files

21


BookingBooking

22


H.323 and SIP H.323 and SIP

23

Recording and PlaybackRecording and Playback


OpenGL based display mode

26

Messenger -SIPMessenger -SIP

H.323 MCUH.323 MCU AccessGridAccessGrid

H.323H.323

EVO: EVO: End-to-End Self Managed and End-to-End Self Managed and Secure RTC InfrastructureSecure RTC Infrastructure

EVO: EVO: End-to-End Self Managed and End-to-End Self Managed and Secure RTC InfrastructureSecure RTC Infrastructure


27

Enabling Virtual Organizations

Thank youThank you


[email protected]

Welcome

Documents

Transcript of Welcome