[Fiware-i2nd] FiWare T7.3: Work on NetIC API

[BANNIZA, Thomas-Rolf]

Dear Andi,

 many thanks for your input. 

Reading the file, OpenFlow appears potentially being able to report in a quite detailed way on the resources in the network under control. But this level of detail might bear also a problem: we have to find a way to 'abstract' the information to make it manageable for a potential user/application. Presumably, 1) the network provider might not be willing to disclose all the details of his network and 2) the potential user might get easily buried with the details.

So our next steps of work should comprise selecting a subset of information which 1) is really anticipated by an interface user and 2) is (ideally) as much as possible technology independent (if the user really needs deeper information, which is technology specific, we might have another query type for this).

@ other task 3 members: are there any further ideas/suggestions/comments on this topic?

@ other tasks, in particular task 4: are there already some ideas, what they expect from NetIC? 

Best regards,
Thomas



-----Ursprüngliche Nachricht-----
Von: Andi [mailto:andi at dis.uniroma1.it] 
Gesendet: Dienstag, 29. November 2011 14:35
An: BANNIZA, Thomas-Rolf
Cc: marco.castrucci at dis.uniroma1.it; vincenzo.suraci at dis.uniroma1.it; pietrabissa at dis.uniroma1.it; lorant.nemeth at nsn.com; jozsef.varga at nsn.com; Hans.Einsiedler at telekom.de; CIMMINO, Antonio; DONADIO, Pasquale; PARLADORI, Giorgio; WUENSTEL, Klaus; fiware-i2nd at lists.fi-ware.eu
Betreff: Re: FiWare T7.3: Work on NetIC API

Dear Thomas and Klaus,

I have just uploaded a document that describes the information that can 
be obtained using the OpenFlow protocol. Please find the document in 
this link:
https://forge.fi-ware.eu/docman/view.php/10/662/FI-WARE_NetIC_OpenFlow+statistics_v0.2.docx

Best regards,
Andi



On 11/23/2011 04:39 PM, BANNIZA, Thomas-Rolf wrote:
> Dear partners,
>
>   in our meeting in Berlin last week we concluded that next step in our task work is the NetIC API specification.
>
> As a first step, we agreed to set up a list of resources (might be e.g. nodes, links, ports, but could be also something different) and associated parameters which are of interest to be exchanged via the interface.
> We should separate the list entries into 2 sections:
> a) information from network (e.g. topology, link load), and
> b) influence on network (e.g. set up/change virtual networks, resource reservation).
> We should first focus on a).
>
> To come to this list we have to tackle some points (among others, this list is not exhaustive!):
> - As we aim for a technology independent IF, we should have (at least) the core of the API technology independent, therefore we have to come to a technology independent answer to the question: what is a resource, and what are potential associated parameters.
> - If we assume a resource on the level of network elements, we need a function which maps path-related requests (i.e. from one endpoint in the network to another) to the affected resources.
>
> As we have discussed this item intensively in Berlin, we would assume that work on it is already on the way by the partners. We kindly ask you to send us your first contributions in the next days, by this we should be able to have a first version of the list until Friday, 2.12. Early feedback is highly wellcome, this would help also to come to a common 'style' of description.
>
> If there is anything unclear or if you have further ideas or suggestions to bring forward this issue, please don't hesitate to contact us.
>
> Best regards,
> Thomas&  Klaus
>
>
>
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>   Thomas R. Banniza
>   Alcatel-Lucent Deutschland AG
>   Bell Labs Germany
>   Dept. ZFZ/N
>
>   Lorenzstrasse 10
>   70435 Stuttgart, Germany
>
>   Phone:   +49 711 821-32232
>   Fax:     +49 711 821-32185
>
>   email:   Thomas-Rolf.Banniza at alcatel-lucent.com
>   Web:     www.alcatel-lucent.com
>
>   Alcatel-Lucent Deutschland AG
>   Sitz der Gesellschaft: Stuttgart · Amtsgericht Stuttgart HRB 4026
>   Vorsitzender des Aufsichtsrates: Michael Oppenhoff
>   Vorstand:  Alf Henryk Wulf (Vorsitzender) · Hans-Jörg Daub ·
>              Dr. Rainer Fechner · Peter Kury
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>            Alcatel-Lucent : At the Speed of Ideas
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Diese E-Mail-Nachricht und ihre etwaigen Anlagen können vertrauliche Informationen
> enthalten. Wenn Sie diese E-Mail-Nachricht irrtümlich erhalten haben, bitten wir Sie,
> uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon
> gefertigte Kopien umgehend zu vernichten. Die irrtümlich erhaltene E-Mail und
> ihre etwaigen Anlagen dürfen weder weitergeleitet noch anderweitig verwendet werden.
>
> This e-mail and its attachments, if any, may contain confidential information.
> If you have received this e-mail in error, please notify us and delete or destroy
> the e-mail and its attachments, if any, immediately. If you have received this e-mail
> in error, you must not forward or make use of the e-mail and its attachments, if any.
>
>
>
>
>
>
>
>
>
>