[Fiware-cloud] some suggestions

Lorenzo Cantelmi lorenzo.cantelmi at inria.fr
Wed Mar 21 11:03:49 CET 2012


Hi all, 

I make my own humble suggestions for wiki, that could be interesting: 

    • in t he Guiding Design Principles at this page we should insert the reference to NIST Roadmap and similar; 
    • in the FIware Extensions [ here ], at 2. point it is probably tpc , instead of tcp ; 
    • in the Components subsection [ here ], at bullet Provisioning it is written that Provisioning is "responsible of deleting the actions that, it takes from the Action Queue", but you can not deduce it from the relative picture: basically a feedback arrow is missing; 
    • about Cloud Edge chapter, Cloud Proxy is basically a router evolved till application layer, a cloud consumer directly (via connection) will work with. So, assuming its hardware fails, consumer is stuck and can not work with deployed applications/services. In the light of that, I guess we should specify that cloud proxy should assure redundancy HW (supply, hdd, etc). 
    • we use to speak about QoS, but, according with FG Cloud Technical Report Part 1 ( III.2 Details on SLA measurement subsection, page 54 - 59 if we consider the offset), in such a new cloud environment we should speak of 2QoS , that stands for Quality and Quantity of Service , to remark the evolution/innovation of the scenario we are offering. I don not know if this acronym is already in use, but sounds good for me. what do you think about? 

Let me know your kind opinions. 


Ciao, 

Lorenzo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20120321/547e3a0d/attachment.html>


More information about the Old-Fiware-cloud mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy