[Fiware-cloud] Materializing Cloud Hosting in FI-WARE

[Alex Glikson]

Miguel -- thanks for the detailed review and the comments.

Team -- please, apply changes based on Miguel's comments below.

Thanks,
Alex



From:   Miguel Carrillo <mcp at tid.es>
To:     Alex Glikson/Haifa/IBM at IBMIL
Cc:     JUAN JOSE HIERRO SUREDA <jhierro at tid.es>
Date:   02/11/2011 07:07 PM
Subject:        Materializing Cloud Hosting in FI-WARE



Dear Alex ,

I am sending private emails to all WPLs with further comments to the "
Materializing Cloud Hosting in FI-WARE" section on the wiki. There are 
general comments (applicable to most WPs) and other that apply to your WP 
in particular.  We have prepared a simple and friendly tutorial to make 
sure that we go in the same direction (http://tinyurl.com/6gueb5t) .


General comments (for all WPs)
=============================================================
Still there are heterogeneous templates for assets. Take Samson and Hadoop 
as the reference templates for assets
IPRs in Assets are very frequently expressed in a vague manner. ?This 
product has IPR associated to it?, ?Open source?? To end with this 
situation change all assets and put this: 
Assets with patents/IPRs. Use this text: "This product will be licensed 
under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to 
pre-requisites of the FI-PPP program". 
If needed, you can add sentences like the one in SAMSON ("Licensing of the 
software under an Open Source license is currently under consideration. ") 

Open source: see Hadoop and use it as template. The text is: "This product 
is licensed under the open source XXX" where "xxx" will be replaced with 
the license that applies and a link to the detailed terms where possible. 
If you rephrase this or use variants it's ok as long as the additions are 
properly explained. 
Programming Artefacts. I see that this is frequently  removed. This is 
part of the template, it is mandatory and has to stay there. I am not sure 
if everyone is understanding this. This field elaborates on what we are 
providing to a developer(an API?, a tool? ... ) 
Delete empty sections. I see many blocks of "Themes", "Features" and "User 
Stories" (for instance) that are empty. This gives a poor impression and 
will cause trouble in the review. Please  remove blank sections, they will 
have to be re-created when the first entry is added to the wiki

Particular comments (specific to your WP)
=============================================================
If I say "ok" to one of them, do not relax. It means that there is no 
particular remark. But the general comments still apply to it and it may 
need changes.

1) COMMENTS ON ASSETS
IaaS Data Center Resource Management 
Crowbar ? ?Programming artifacts? must be removed. This is not compliant 
with the template
 xCAT T ? ?Programming artifacts? must be removed. This is not compliant 
with the template
OpenStack Nova ? template ignored
System Pools ? wrong template (it not an ?open source assets coming from 
third parties?). It needs the long template. 
ISAAC ? wrong template (it not an ?open source assets coming from third 
parties?). It needs the long template.
RESERVOIR ? not compliant with the template. Some sections are empty with 
an ?TBD?. 
Trusted Compute Pools ? ?Programming artifacts? must be removed. This is 
not compliant with the template
Open Cloud Computing Interface (OCCI) ? ?Programming artifacts? must be 
removed. This is not compliant with the template
OpenStack Glance ? template ignored
OpenStack Quantum ? template ignored
Open vSwitch ? ?Programming artifacts? must be removed. This is not 
compliant with the template
IaaS Service Management
JBoss ? ok
MySQL ? ok
Claudia ? ok
PaaS Management
Apache Tomcat - ok
PostgreSQL- ok
Ruby- ok
RubyGem- ok
Chef- ok
PaaS Management Platform- ok
Baseline Assets
OpenStack Swift? ?Programming artifacts? must be removed. This is not 
compliant with the template
Self-Service Interfaces
Apache Tomcat ? ok
MySQL ? ok
HTML ? direct link to wikipedia. If it is explicitly an asset, it must 
have a wiki page that has to be compliant with the template
CSS  ? direct link to wikipedia. If it is explicitly an asset, it must 
have a wiki page that has to be compliant with the template
Ruby on Rails ? direct link to wikipedia. If it is explicitly an asset, it 
must have a wiki page that has to be compliant with the template
Cloud Proxy
Nada Management Framework  - ?NMF has no IPR associated to it? is very 
poor. Possibly this means that it is Open Source under a license such as 
Creative Commons, or alternatively something like the text in 
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Ruby 
Monitoring
collectd - ? ?Programming artifacts? must be removed. This is not 
compliant with the template
RabbitMQ ? I suspect that this qualifies as ?open source assets coming 
from third parties?  in which case this has to use the short template, not 
this.
?Drools <- Fernando? ?  - we must remove these informal remarks.  This 
refers to an empty page with a template that is wrong
Esper ? ?Programming artifacts? must be removed. This is not compliant 
with the template
Graphite? ?Programming artifacts? must be removed. This is not compliant 
with the template
Security
 OpenStack Keystone - not compliant with the template (I assume the righ 
one is the short one in this case)


2) COMMENTS ON BACKLOG
I will send you this first thing in the morning 

Please make sure that this is properly looked at by all the concerned 
members of the WP under your supervision. 

Deadline: Friday, 4 EOB.

Thanks for your cooperation

Miguel 
-- 
----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito C 
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 5 
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N 
 _/          _/_/                         Madrid 28050 (Spain) 
                                          Tel:  (+34) 91 483 26 77 

                                          e-mail: mcp at tid.es
----------------------------------------------------------------------

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-cloud/attachments/20111102/ec5e5ab0/attachment.html>