[Fiware-iot] [GE splitting]

[t.elsaleh at surrey.ac.uk]

Hello Fermin,

Thanks for the addtions!

With regards to the NB/SB TM interfaces, we do plan to support NGSI-9, but also other interfaces.

With regards to the Unit Test Plan, this will be defined after the NB/SB interfaces themselves have been finalized.

Best regards,
Tarek



From: Fermín Galán Márquez [mailto:fermin at tid.es]
Sent: 07 December 2012 11:17
To: Elsaleh T Mr (Electronic Eng)
Cc: Tobias.Jacobs at neclab.eu; fiware-iot at lists.fi-ware.eu
Subject: Re: [Fiware-iot] [GE splitting]

Dear Tarek,

I have added DiscoveryEngine to the splitting status page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Things_Management_GE_splitting_page), adding the placeholders for wiki pages that you mention in your email.

I think that the DiscoveryEngine doesn't play a role in the northbound and southbound ThingManagement interfaces, so I haven't added it to these rows. In addition, I'm assuming that part of the existing Unit Test plan is needed for the Discovery Engine (otherwise, please remove the DiscoveryEngine stuff in this row).

In addition, could you have a look to the Excel that I sent in my other email to rename the issues belonging to DiscoveryEngine, setting the "new_name" column for them, please? I think that using the following rule:

X.IoT.Backend.ThingsManagement.Y -> X.IoT.Backend.ThingsManagement.DiscoveryEngine.Y

Best regards,

------
Fermín

El 07/12/2012 12:01, t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk> escribió:
Hello Fermin,

With regards to the Discovery Engine, we are planning to have our own GE for this, as done with the Configuration Management and the IoT Broker.

We will also set up a private wiki page for this under the FIWARE IoT chapter Architecture, and then modify the technical roadmap, and revise the epics/features defined.

It would be great if you could point to us to where we should put in the private wiki, i.e. the document path. Otherwise we'll just create one somewhere for now.

Best regards,
Tarek



From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Fermín Galán Márquez
Sent: 07 December 2012 10:47
To: Tobias Jacobs
Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: Re: [Fiware-iot] [GE splitting]

Dear Tobias,

In order to ease the "Tracker items" task, I've taken an snapshoot of the trac (attached). For each one of the currently existing issues, we should define a new name, using the following rule:

X.IoT.Backend.ThingsManagement.Y -> X.IoT.Backend.ThingsManagement.IoTBroker.Y or X.IoT.Backend.ThingsManagement.ConfigMan.Y

Tobias, could you please do a first pass to the attached Excel completing the new_name column for the issues related with IoT Broker, please? I'm not sure which they are...

In addition, if we are splitting the Thing Management GE into two GEs (IoT Broker and ConfMan) we should define where Discovery Engine and Geo-Discover components are located. Considering the internal structure (see attachment) I tend to think that they would belong to ConfMan, but I would like to confirm if the other partners in Thing Managament GE (NEC and USurrey) think the same.

Best regards,

------
Fermín

PD. I've created a backlog entry (workitem) for the wiki and trac work on splitting: FIWARE.WorkItem.IoT.Backend.ThingsManagement.Splitting<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3250&group_id=11&atid=193> . It should be assigned to both TID and NEC (as we are doing this splitting), but given that AFAIK our trac doesn't allow assign a ticket to two different people, asignee is set to "Nobody".

El 03/12/2012 11:37, Fermín Galán Márquez escribió:
Dear Tobias,

I think is a good approach. I will take care of the ConfMan pages.

Best regards,

------
Fermín

El 26/11/2012 16:27, Tobias Jacobs escribió:
Dear all,

We are about to start implementing the split between the Things Management GE and the Configuration Management GE. What we have done up to now is to create an overview of the places where there are changes that need to be done:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Things_Management_GE_splitting_page

The page also contains placeholders for the modified pages.

The question now is how much of the old Things Management GE to leave in these pages.
What we would propose is to bring everything into a status which simulates that the TM GE has never existed, and only mention at certain places that the TM GE now is actually two GEs. Although this might create some confusion, the alternative would be to have some things described in terms of the old GE and other things described in terms of the new GE - where the confusion would be considerably greater, I think.

In particular.

-          All tracker items become associated to one of the new GEs, or both

-          All Things Management GE features/epics/... become features of one of the new GEs, or of both

-          In the technical roadmap the release 1 could stay like it is, but the linked features are changed to the new features.

-          In the catalogue the old TM GE will stay at least until the 2nd release, but the documentation links need to be updated.

Please let me know your opinion.

Best regards
Tobias


_______________________________________________

Fiware-iot mailing list

Fiware-iot at lists.fi-ware.eu<mailto:Fiware-iot at lists.fi-ware.eu>

http://lists.fi-ware.eu/listinfo/fiware-iot


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20121207/7dc6543b/attachment.html>