[Fiware-cloud] Proxylets - draft end-to-end scenario and tasks

[BESSON Lionel]

Dear all,

Please find attached a document to be used as a basis for our discussion on proxylet next Monday

Best regards,

Lionel

De : Alex Glikson [mailto:GLIKSON at il.ibm.com]
Envoyé : mercredi 24 octobre 2012 10:00
À : fiware-cloud at lists.fi-ware.eu; LOPEZ RAMOS Mario; BESSON Lionel
Objet : Proxylets - draft end-to-end scenario and tasks

Dear all,

Following our previous discussion on enhanced Cloud Proxy capabilities, below is an attempt to outline an end-to-end scenario -- comments are welcome.

Concepts:

 *   Proxylet
    *   Attributes: name, description, version, runtime type, runtime version, binary, dependencies (runtime/device capabilities, other proxylets running on the same runtime) -- TBD: reuse existing definition language and runtime? (looks similar to OSGi/Eclipse bundles/features)
 *   Proxylet Engine (PE) -- VM running in CP, containing the proxylets runtime (Node.js?)
 *   Proxylet Catalog (PC) -- will potentially reuse the code of Image Library in DCRM (Glance) or of Service Catalog in SM -- TBD (or maybe the two would converge?)

Flow:

 1.  gateway ships with CP virtualization platform and management API

 1.  admin installs PE image using CP mgmt API, configures PE runtime

 1.  developer designs service comprising a proxylet -- in additional to 'traditional' components of a web application (client side, server side)

 1.  developer uploads proxylet to PC

 1.  developer registers the service in SM catalog

 1.  service instance is deployed, creating instances of "regular" VMs comprising the service.
    *   Note: PC is not duplicated, can be shared between applications/instances (stateless). TBD: access rights?
    *   Note: proxylets are *not* deployed on CP/PE by SM.

 1.  user runs the client side component of the vApp on a mobile device (javascript)

 1.  authenticates with IdM, receives token

 1.  the client side of the vApp initializes proxylets of given app (generic or specific) on PE
    *   checks if PE available, acquires its runtime type, version, capabilities, etc
    *   queries availability of proxylets of given app that can run on such PE
    *   instructs the PE to download and install the proxylets on behalf of the authenticated user (update if newer version is available)
       *   Note: PE would also provide a mgmt interface to manually install proxylets, to clean up unnecessary proxylets, manage resources, etc
       *   Note: we need to provide client-side library that automates the above flow

 1.  vApp start working leveraging the proxylet(s)


TASKS:

 *   PE runtime, basic life cycle of proxylets (incl. API, management interface)
 *   PE client-side library
 *   PE management on CP: packaging, automated installation, resource management
 *   PC runtime & mgmt API
 *   Secure access to PC
 *   SM extension & integration (e.g., proxylet registration in PC during service deployment)
 *   Proxylets compatibility, versioning, updates, etc

 *   Advanced proxylet capabilities (Open Call)
    *   interdependencies, inter-invocation, etc
    *   intelligent data caching and replication
    *   disconnected operation
    *   etc


====================================================================================================
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml
Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20121116/3ac76342/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Proxylet_approach_thales_v03.doc
Type: application/msword
Size: 902144 bytes
Desc: Proxylet_approach_thales_v03.doc
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20121116/3ac76342/attachment.doc>