[Fiware-iot] R: Tracker and Materializing Wiki

[Farkas, Lorant (NSN - HU/Budapest)]

Hi Sabrina,

 

Thank you very much for the action.

Please find my comments inline.

 

Thanks & Br,

 

Lorant

 

 

From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Guerra Sabrina
Sent: Friday, June 15, 2012 6:55 PM
To: fiware-iot at lists.fi-ware.eu
Subject: [Fiware-iot] R: Tracker and Materializing Wiki

 

Hi Denes and Lorant,

thanks for your work in which you've reorganized the backlogs. We've analyzed the issues assigned to me and we report our observations:

·         Many issues are related to the Advanced Connectivity GE that, as far as I know, is not covered by any assets, both in the backend and in the gateway. They are 

97 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=97&group_id=11&atid=193>  FIWARE.Epic.IoT.Backend.AdvancedConnectivity.MobilityManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=97&group_id=11&atid=193>  

101 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=101&group_id=11&atid=193>  FIWARE.Epic.IoT.Backend.AdvancedConnectivity.TrafficFlowManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=101&group_id=11&atid=193> 

104 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=104&group_id=11&atid=193>  FIWARE.Epic.IoT.Backend.AdvancedConnectivity.QualityOfServiceControl <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=104&group_id=11&atid=193>  

1840 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1840&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.MobilityManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1840&group_id=11&atid=193> 

1841 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1841&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.SessionManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1841&group_id=11&atid=193> 

1842 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1842&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.TrafficFlowManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1842&group_id=11&atid=193> 

1843 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1843&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.QualityOfServiceControl <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1843&group_id=11&atid=193> 

1861 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1861&group_id=11&atid=193>  FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.M2MDeviceSessionManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1861&group_id=11&atid=193> 

1862 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1862&group_id=11&atid=193>  FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.NativeDeviceSessionManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1862&group_id=11&atid=193> 

Yes, advanced connectivity is a new GE accoring to the new streamlined architecture and there is no identified asset so far for them. If you check the technical roadmap, we should provide this GE in the backend by the 2nd major release (Q3 of 2013). In addition, there is nothing mentioned in the technical roadmap about QoS control, traffic flow management etc, just the discontinuous connectivity. Additionally, advanced connectivity is not mentioned in the gateway scope at all.

Action items as a result (I would recommend to please put them as "work items" in the forge to show progress - if not done by EOB tomorrow, I would do it myself on Wednesday, we were criticized because of not showing progress of the work in the tracker):

1. identify assets for advanced connectivity GE - Sabrina/Gian Piero. I would start this by asking around from partners with more detailed info on how you see such an asset. This could be even a topic for our next weekly call. One could maybe start with exploring those assets that provide backend/gateway side device management. You could organize a meeting with the owners of device management-related assets in the first round. Name of the work item could end with AssetIdentification or something like that

2. if no assets are identified, propose this as a topic for the next open call - Sabrina/Gian Piero. No need to record this as a work item now

3. start editing the technical roadmap from the perspective of this GE, put the features of the advanced connectivity GE in the releases - Sabrina/Gian Piero. As a safe approach one could put every item in the final release, for now, and then follow it up, once we have the feedback from the asset owner dealing with discontinuous connectivity. Name of the work item could end with RoadmapUpdate or something like that

 

·         There are two issues that perhaps have a wrong name because the ConnectivityStatusManagement in my opinion is actually the DiscontinuousConnectivity in the Device Management GE

555 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=555&group_id=11&atid=193>  FIWARE.Epic.IoT.Backend.AdvancedConnectivity.ConnectivityStatusManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=555&group_id=11&atid=193> 

1844 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1844&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.ConnectivityStatusManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1844&group_id=11&atid=193> 

4. Change the info in the technical roadmap concerning the statement on advanced connectivity - discontinuous connectivity belongs to Device Management - Sabrina/Gian Piero. No need to record this as a work item

5. Please put these epics under the Device Management GE - Sabrina/Gian Piero. No need to record this as a work item

·         About the Security GE I don't know who is the partner which will provide it. So there are two epics that are in the Security GE

102 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=102&group_id=11&atid=193>  FIWARE.Epic.IoT.Backend.Security.AccessPolicyControl <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=102&group_id=11&atid=193>  

1845 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1845&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.Security.AccessPolicyControl <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1845&group_id=11&atid=193> 

6. Action on Lorant/Denes/Thierry to have a work item on identifying an asset, communicating with the security WP leader etc.

 

·         A question for Ericsson: does your asset implement AddressTranslation module (that is: The IoT resources must be addressable both at application and at device/gateway level so there must be a mechanism to translate the incoming addresses to an internal unified platform address to identify each resource)?

558 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=558&group_id=11&atid=193>  FIWARE.Epic.IoT.Gateway.DeviceManagement.AddressTranslation <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=558&group_id=11&atid=193>  

7. Could you please directly address this question to them, they might not even read this row hidden in the details, but if they see their name, they will react - Gian Piero/Sabrina

 

·         Finally there are some themes that perhaps have an incorrect name. ConnectivityManagement should be AdvancedConnectivity and Service Control should be DeviceManagement

584 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=584&group_id=11&atid=193>  FIWARE.Theme.IoT.Backend.ConnectivityManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=584&group_id=11&atid=193> 

1868 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1868&group_id=11&atid=193>  FIWARE.Theme.IoT.Gateway.ConnectivityManagement <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1868&group_id=11&atid=193> 

585 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=585&group_id=11&atid=193>  FIWARE.Theme.IoT.Backend.ServiceControl <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=585&group_id=11&atid=193> 

1867 <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1867&group_id=11&atid=193>  FIWARE.Theme.IoT.Gateway.ServiceControl <https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1867&group_id=11&atid=193> 

8. We agree, could you please update them? - Gian Piero/Sabrina

 

Do you agree with our observations or do you have any other opinions?

Best regards,

Sabrina and Gian Piero

 

Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Bisztray, Denes (NSN - HU/Budapest)
Inviato: venerdì 15 giugno 2012 15:51
A: fiware-iot at lists.fi-ware.eu
Oggetto: [Fiware-iot] Tracker and Materializing Wiki

 

Dear All,

Lorant and myself compared the updated Materializing Internet of Things (IoT) Services Enablement in FI-WARE wikipage with the Forge Tracker. Now they are in complete sync. 

1.      Please check the tracker in case we made some errors.

2.      Whenever someone makes changes to one, should change the other as well. Please keep this in mind.

Best,

Dénes

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. 

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. 

 Rispetta l'ambiente. Non stampare questa mail se non è necessario. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120618/361f5901/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120618/361f5901/attachment.gif>