[Fiware-cloud] [Fiware-i2nd] WP4 WP7 - Overlapping Epics

[jeanpierre.lerouzic at orange.com]

Hi all,

 

Serge,

 

If I understand correctly the cloud proxy concept, it means that:

·         From the point of view of the home devices, all services are accessed through the cloud proxy which unifies the services interfaces (hence the name cloud proxy).

·         From the point of view of services the cloud proxy, doesn't unify the home devices.

 

At a technical level, I understood during the WP7 session in Turin that the Cloud proxy, is a kind of bare metal  OS that executes applications in the form of light VMs. Cloud applications would download those light VMs on the bare metal OS which would run them. The rationale being that broadband connection may be sometimes slow and it's better to execute applications locally. 

 

I think that in WP4 EPICS you use the word "network" more with the meaning of a computer network interface (Ethernet and so on), than a Telecom network. This is IMO well described in one of WP4 EPIC: FIWARE.Epic.Cloud.ResourceManager.Network <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Cloud.ResourceManager.Network> , especially the mention of L2/L3.

 

But if we decide than computers are not permanently connected through their network interfaces (which is suggested by the whole concept of a "cloud proxy"), the difference between a computer network and a telecom network is quite blurred IMO as you will have to introduce connection protocols (like PPP over xyz).

 

It seems to me that there is in WP4 a collision course between two network notions. My own understanding of OpenStack Quantum is that it deals with virtual NIC which in my opinion doesn't align well with the "cloud proxy" concept which is more about application running on devices (but not as native applications). If the WP4 "cloud proxy" is it about virtualized local applications then what Chris suggested as overlap seems to me correct, or  the WP4 "cloud proxy" is about virtualized NICs (L2/L3) which is a different topic where I agree there is not much overlap with WP7 network API EPICS.

 

If my understanding happens to be correct I think it would be nice to:

·         Have a project agreement on vocabulary and concepts (what is a network?)

·         Have a project policy to reduce the usage of overloaded concepts (for ex: "user", when there are many kind of users as you rightly suggested).

·         Try to clarify what the "cloud proxy" is about (is it about virtualized local applications or is it about virtualized NIC?)

 

Best regards,

 

Jean-Pierre

 

 

De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Defrance Serge
Envoyé : jeudi 24 novembre 2011 10:28
À : Woods, Chris; fiware-i2nd
Cc : fiware-cloud at lists.fi-ware.eu
Objet : Re: [Fiware-i2nd] WP4 WP7 - Overlapping Epics

 

Hi Chris,

 

Regarding the section of your document « WP4 and WP7 overlaps » devoted to cloud edge, I think there is a misunderstanding.

 

You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention.

 

Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case).

 

Hoping my comments help,

Cheers,

Serge.

 

From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris
Sent: mercredi 23 novembre 2011 10:53
To: fiware-i2nd
Cc: fiware-cloud at lists.fi-ware.eu
Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics

 

Hello Folks,

 

Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review.  My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. 

 

This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage.

 

I hope you'll find these documents useful.

 

Attached & Forge Link

 

Wp4 and wp7 overlaps.docx <https://forge.fi-ware.eu/docman/view.php/10/644/WP4+and+WP7+Overlaps.docx> 

This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4

Wp4wp7overlap-study.mm <https://forge.fi-ware.eu/docman/view.php/10/645/wp4wp7overlap-study.mm> 

Working document (Mind-Map) showing related Epics between WP4 and WP7

 

Chris Woods

-------------------------------------------------------------
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20111125/955e354a/attachment.html>