Design Paradigm

1

Design ParadigmTransparent to the user

Component add-on rather than alterationGINI remains independentOnly altered the Configuration file

GINI on a Cloud © November 09

David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

2

Design ParadigmUse of flexible communication library:

twistedGINI already in PythonFlexibleAvailable source codeStableHigh-level functions



3

Improvements Overview


Front End Dispatcher

Database

Scheduler

Back End

Back End

Back End

Back End

Server Workers

Client


4

Current Access to remote server


5

Connection to server


6



Front End

Back End

SSH Tunnel

7

Addition to GINI


8

Addition to GINI


9

Gateway to the cloud


10

Sequence of Events1. Send Dummy variable


Database

NoWorker



11

Sequence of Events2. Dispatcher searches for a worker


Database

Best Worker?



12

Sequence of Events3. Returns worker or dummy variable


Database

Worker’s IP



13

Why the dummy variable?


Need to establish TCP communicationRecycled as an error flagCould be user to convey info in future

upgrade

14

End Result: Unaltered GINI


15



Hidden location of back end

Front End

Back End

SSH Tunnel

16

FlexibilityNon-fixed data types being passedCurrently a string: IP, DNS or anything else


17

DrawbackTemporary TCP connection: Port expiration at

timeoutMost Clients don’t have DNS


18

Design Dilemma


EitherMaintain permanent client-dispatcher

connection Resources consuming Might not bring any benefits Requires heavy alterations to gServer

Drop the connection after delivering the goods Lightweight component No resources used Impossible (or difficult) to retrieve clients

19GINI on a Cloud © November 09

Design Paradigm

Documents