This is the decision!!! I will review the roadmap accordingly. Regards, Matteo -------- Messaggio originale -------- Oggetto: Re: [Fiware-wpl] Detailed comments on Technical Roadmap deliverable Data: Wed, 14 Mar 2012 10:54:58 +0100 Mittente: Juanjo Hierro <jhierro at tid.es> A: matteo.melideo at eng.it <matteo.melideo at eng.it> CC: fiware-wpl at lists.fi-ware.eu <fiware-wpl at lists.fi-ware.eu>, fiware-wpa at lists.fi-ware.eu <fiware-wpa at lists.fi-ware.eu> This is my fault. I thought that we already agreed that testing tools would be deferred to the second Release, but you are right that we finally agreed that I was going to review the contents anyway in order to make a concrete proposal (this basically to confirm whether testing tools were the points to be deferred or even some additional aspects should be postponed). Well, the point is that I have actually carried out the revision and do keep my position in favor of postponing delivering of testing tools to the second release. You can keep the rest regarding the First Release (first version of the IDE and catalogue) Cheers, -- Juanjo On 14/03/12 09:28, Matteo Melideo wrote: > Juanjo Hi, > why in capital letters the reminder to Wp9? Are there any problems? > I was honestly waiting for your inputs. Reading at the minutes the > only point I can see is: "Development tools: Juanjo will check what is > there and make a proposal on what items to be postponed for second > release of FI-WARE" > > Said that sorry if I missed this agreement! > > M. > > > Il 14/03/2012 08:22, Juanjo Hierro ha scritto: >> Hi, >> >> Here you have a list of issues/doubts that have came to my mind >> while reading the Technical Roadmap of each chapter. I believe it >> would be worth solving them prior final publication. >> >> I'm still working on the comments for the IoT and Data/Context >> Management Chapter. I couldn't bring comments on the I2ND and >> Development Support Tools chapters because changes recently agreed >> hadn't been incorporated yet and I prefer to make comments on a >> revised version. >> >> *Apps Chapter:* >> >> * First Release: >> o You say ... "This is handled in conjunction with the 1st Open >> Call" ... But ... What is handled in conjunction with the 1st >> Open Call ? The sentence that is below or the list of >> functions enumerated above the sentence ? It was unclear. >> Using a semicolon, it would be more clear. >> o I will assume that what is handled in conjunction with the >> 1st Open Call ... However, it is not that clear what do we >> intend to provide when we say that we will support the >> "Ability to expose a REST Service through SOAP protocol in >> order to enable a Compositor Editor supporting SOAP to >> compose REST Services". My assumption is that you aim to >> rely on the ability to implement a service interface and >> describe it in a technology/protocol-neutral way using the >> IDL that the middleware to be developed as a result of the >> 1st Open Call will support. Operations in the service >> interface will then be accessible through several protocols >> (i.e., REST, SOAP, IIOP, ...). Is my assumption correct >> ? If so, I would suggest explain it a bit better ... (I >> hope that the above description may help) >> o It seems like there is some missing indentation in the last >> bullet list (the one after "These features will be ...") ... >> I mean when you say "Basic interaction of the Composition >> Engine with the Marketplace regarding" ... shouldn't the two >> following items indented ? how many of the following items ? >> o I guess that when you say "Ability of the Composition >> Environment to read/write service description into the >> Repository using USDL" it would be more accurate to say >> "Ability of the Composition Environment to read/write service >> descriptions from/into the Repository that are described >> using USDL" >> o It is not very clear what you mean when you say "Use of the >> Mediator Proxy generator through a Web Interface to generate >> a proxy to mediate SOAP to REST" ... what kind of Web >> interface are we talking about ? I would suggest saying >> instead "ability to compose both SOAP and REST services using >> the capacities of a Mediator Proxy generator" but ... >> anything more clear >> o We shouldn't refer to companies or products. We are >> delivering what are going to be Open Specifications of >> FI-WARE GEs and a reference implementation of those >> specifications. Therefore, it doesn't make sense to talk >> about the "DT Mashup Platform". >> o What do we mean by "mediated SOAP services" ? mediated >> through what ? from where ? to what ? >> o typo: "die GEs" ... I guess should be "these GEs" >> o Saying "The general integration between die GEs will not yet >> provided for the first release and will become a focus of the >> second release" may confuse a bit because there is some >> degree of integration between some of the GEs that will be >> achieved in the first release. Please elaborate more on >> what will NOT be integrated. >> * Second Release: >> o Elaborate a bit on what new functions will come as a result >> of a closer integration of the store and the marketplace. >> Add some "(e.g., xxx)" may help >> o I don't understand what does "Adaptation of the service >> language USDL to the integrated technical setting" exactly >> means. >> o You should elaborate (at least giving some examples) of how >> you intend to integrate Identity Management. >> o You should elaborate (at least giving some examples) of how >> you intend to integrate aspects related to the Internet of >> Things >> * Future releases: >> o No particular comment >> >> >> *Cloud Chapter:* >> >> * General comments: >> o Drop-out the text in bold coming from the guidelines >> >> * First Release: >> o I would shift the reference to the cloud portal to the >> beginning. For instance, I would rewrite the first bullet as >> follows: >> + Management of Individual virtual machines and associated >> resources in a datacenter through a set of standardized >> APIs as well as a Cloud Portal: >> # Ability to automate the provision, as well as >> management of the lifecycle, of virtual machines and >> the associated compute, storage and network resources >> # Ability to define and maintain a library of >> pre-configured virtual machine images that can be >> used for the automated provisioning of new virtual >> machines >> o Is the concept of "enhanced hardware-supported trust" >> described in the Architecture Description ? If so, try to >> have a hyperlink to the proper section from here >> o Same for the concept of "composite multi-VM services" >> o Weren't we going to distinguish between what will be >> delivered at the beginning and at the end of 3Q2012 ? >> * Second Release: >> o We talk about "network bandwith" management in the first >> bullet ... do we mean it referred only to internal datacenter >> connectivity (i.e., VLANs) ? Managing it end to end (i.e., >> from application clients to applications running on the >> backend hosted in a Cloud datacenter) would require using >> interfaces defined in the I2ND chapter ... and I wonder >> whether we are postponing management of those interfaces to >> future releases (this would be what makes sense IMHO). We >> need to clarify this. >> o While we focus on simple VMs allocation in the first release >> ... what about allocation of VLANs and virtual disk storage >> shared by several VMs ? Wouldn't we support this level of >> allocation in the second release ? >> o We talk about "federation" but we don't talk about >> cloudbursting - hybrids clouds. If you consider them >> special cases of "federation", please explain that. >> o What do we mean by "Image management for cloud edge >> appliances" ? >> * Future Releases: >> o I would reword the sentence saying "Exposing more software >> defined networking capabilities of the Interface to Connected >> Devices chapter through Cloud Hosting service interfaces" by >> something like "Ability to elastically manage allocation of >> network resources outside datacenter boundaries along the >> whole communication path between the end user and the >> applications backends, using interfaces produced in the I2ND >> chapter" >> >> * >> I2ND Chapter:* >> >> * NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM >> OUR LAST DISCUSSION !! >> >> >> *Security Chapter:* >> >> * General comments: >> o For the shake of consistency across all chapter >> contributions, I wouldn't number the list of features, just >> use bullets. >> >> * First Release: >> o Explain what IDM stands for the first time the acronym >> appears (Identity Management) >> o I understand that the web interface that the IDM GE will >> expose will be a Restful interface ... therefore I would >> move the reference to REST API to the first bullet of the >> General Remarks subsection, which I would simply rewrite as >> follows: >> + The IDM GE will provide a common Restful API to clients >> o You should postpone optional Security GEs to the second >> release as per discussion during our last joint WPLs/WPAs >> follow-up confcall. Only if UC projects requires any of >> them explictly, we will evaluate how they can be delivered in >> upgrades of the Testbed after delivery of the first release. >> o Honestly speaking, I believe that it would be better if we >> move the Context-based Security and Compliance GE to the >> second release because my understanding is that it has to be >> closely integrated within the architecture of the Apps >> Chapter ... Has such integration been carefully designed ? >> What are we going to be able to provide in a first release if >> not ? I guess it makes sense to address such integration >> for the second release, once the Architecture of the Apps >> chapter is more consolidated. Unless a UC projects requires >> this, let's commit this for the second release. >> o "offered for Release 1" to be dropped in the last bullet >> (point 5) >> >> * Second Release: >> o "offered for Release 2" should be dropped in many of the >> points (just redundant, since the bullets are within a >> section titled "Second Release") >> o Integration with Data/Context Management GEs should be >> addressed in the Data Handling GE for the Second Release >> (include an additional point on the matter) >> >> * Future Releases: >> o For the sake of consistency across the different points, I >> would re-title the first bullet as "Security Monitoring GE >> functionalities" >> o Merge the point on Ovalyzer with the corresponding >> sub-bullet, making it just one bullet >> >> >> *Development Support Tools Chapter:* >> >> * NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM >> OUR LAST DISCUSSION (i.e., moving testing tools to second >> release) !! >> >> -- Juanjo >> >> ------------- >> Product Development and Innovation (PDI) - Telefonica Digital >> website:www.tid.es >> email:jhierro at tid.es >> twitter: twitter.com/JuanjoHierro >> >> FI-WARE (European Future Internet Core Platform) Chief Architect >> >> You can follow FI-WARE at: >> website:http://www.fi-ware.eu >> facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 >> twitter:http://twitter.com/FIware >> linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 >> >> ------------------------------------------------------------------------ >> 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 >> >> >> _______________________________________________ >> Fiware-wpl mailing list >> Fiware-wpl at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-wpl ------------------------------------------------------------------------ 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-tools/attachments/20120314/afc97e57/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-tools/attachments/20120314/afc97e57/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy