[Fiware-cloud] [FIWARE] IaaS SM interfaces

[Alex Glikson]

Fernando, all, 

Have you considered leveraging TOSCA (
http://www.oasis-open.org/committees/tosca/charter.php)? Sounds relevant..

Regards,
Alex



From:   FERNANDO LOPEZ AGUILAR <fla at tid.es>
To:     Alex Glikson/Haifa/IBM at IBMIL
Cc:     "fiware-cloud at lists.fi-ware.eu" <fiware-cloud at lists.fi-ware.eu>, 
JUAN JOSE HIERRO SUREDA <jhierro at tid.es>, JAVIER MARTINEZ ELICEGUI 
<eli at tid.es>, HENAR MUÑOZ FRUTOS <henar at tid.es>
Date:   23/01/2012 03:06 AM
Subject:        [FIWARE] IaaS SM interfaces



Dear all,

  We have internally carried out an extensive analysis in order to decide 
what should be the best decisions regarding evolution of the Claudia 
platform, which is the baseline asset adopted for development of the IaaS 
Service Management GE in FI-WARE as you know. This email is to share with 
you a summary of this analysis as well as the derived decisions which we 
would be willing to implement in the context of FI-WARE, since we believe 
that they will also benefit the project.
1.      We currently think there is some degree of uncertainity regarding 
final adoption of the future DMTF CIMI standard by the market.   This due 
to the fact that the standard is not yet mature enough, still there are 
not so many committed endorsement by a significant number of Cloud 
providers and we are working in a fast-moving market.
2.      The OpenStack initiative is progressively gaining momentum and may 
lead to definition of a "de facto" standard in the market
3.      Based on the above, a safe strategy may consist in that the IaaS 
Service Management component in FI-WARE implements the OpenStack API for 
the first release of FI-WARE.   We believe this will ease a wider adoption 
and a greater visibility of FI-WARE results in the short term.
4.      Parallel to that, we will monitor progress of the DMTF CIMI 
standardization process and will keep being active there.  However, 
Implementation of a CIMI-compliant API in FI-WARE will be postponed to 
future releases of FI-WARE (second or third).   Implementation of that API 
would, of course, be subject to momentum gained by the CIMI standard, 
definitively discarded if the standard doesn't take off.
5.      The OpenStack API provides a very basic set of functionalities. It 
doesn't integrate aspects regarding support to elasticity management, for 
example, which will be one of the key differential functions to be 
supported by the IaaS Service Management component in FI-WARE. Therefore, 
work within the first release of FI-WARE will comprise definition of an 
API that is complementary to that one from OpenStack, based on the one 
currently supported by Claudia, which deals with this added-value 
functions.
6.      We intend to deliver the definition of the complementary API 
described in 5. to the OpenStack community.   We believe this will 
definitively enhance the visibility of FI-WARE results, while at the same 
time protect the investments made in FI-WARE.
7.      We believe that the IaaS Service Management GE in FI-WARE has to 
be designed as to be able to rely on different products, at the Resource 
Management layer, implementing different interfaces.   This will ease 
legacy integration or federation with other Cloud Resource Management 
technologies.   Thus, besides support to integration with OCCI-compliant 
Resource Management products, we intend to demostrate the support of 
integration with other products, in particular Joyent.
 
  We have double-checked with Juanjo Hierro whether these decisions could 
fit well within FI-WARE's overall strategy and he agrees they fit rather 
well.
  Of course, we are happy to elaborate on this in much more detail during 
our F2F meeting this week.
  Best regards,
Fernando López Aguilar
Cloud Computing
fla at tid dot es
+34 914 832 729
Telefónica I+D (R&D)
Ronda de la Comunicación s/n
Distrito C, Edificio Oeste 1, Planta 5
28050 Madrid, Spain




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/20120205/61a0c199/attachment.html>