[Fiware-cloud] 24-May-2011 weekly conf call -- minutes

[FERNANDO LOPEZ AGUILAR]

Dear all,

I was checking the GE and the relationships between all of them. I suggest to review it with the following updates.

- We prefer to change the name of "Hosting of VM-Based services" to "Service Management" due to it reflects more appropriately the functionality.
* Within this GE (compound basically by Claudia assets), we can find the functionality of Autoscaling, Lifecycle Management  and Image processing.
* Image Processing is a VM Image Manager that will be used by the PaaS (see bellow).
* The functionality of the Autoscaling is provided autoscale functionality of the VM. In case of the PaaS autoscaling, we have to define specific functionality (see bellow).
* Other functionality, that we need to put here, is the Federation & Interoperability part.

- PaaS, is something more complex to be managed. It creates the Virtual Appliance and manages the different products that the services will need
* PaaS needs also autoscaling, but we can see it compounded by 2 different parts. The first one manages the configuration of the platforms (DB, Web Server, etc...) that it is needed in a Platform. Meanwhile, the autoscaling part of the Service Management will be the functional block that realizes the real autoscale of the VM, based on this configuration information.
* The name of Hosting of Application Containers is not very appropriate in this case due to PaaS is not a Platform Container itself. It tries to manage automatically the virtualization of the different components needed by an application, for example DB or Web Server. We see more appropriate the term "Platform Management (PaaS)" here.
* The scalability is applied both PaaS level and Service Management level, cue to we need to reconfigure the different platforms in which our services will be scaled furthermore.
* The same have to be applied to the monitoring in which we have to take into consideration both the services KPIs in the Service Management and the PaaS KPIs in the Platform part.
- Regarding the SLO Mgmt, I am not sure why you put the name of this GE to SLO and not to SLA, we consider it would the more general view if we consider SLA and not the part of it. What was the reason to adopt it?
* We have to considerer the different rules defined by the users through the Elasticity Rules, QoS and/or Business Criteria. If we consider this elasticity rules like SLA or related to the SLA then we need to put a relationship between the SLA and the autoscaling functionality.

- Object Storage, in this case we do not see directly what is the reason that we have to put direct connection between Self-Service Interface and it, maybe due to you have to put here protocols like CDMI? Anything else? Continue with this GE we see that it is needed a connection between Object Storage and the Hosting of VM in order to access to the data objects.

- Regarding the Policy-Driven Local and cross-data centre optimization. Question here is that it is related to the placement concept? in which GE can we put this functional block?

- Finally, accounting and billing, we see it like a transversal component not specified here but related to all piece of the Cloud Hosting.


[cid:70C132DC-5470-41ED-886A-FC0C45E26895]

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

[cid:65E3CA3A-3DFE-41B6-8F69-2AD965EA42FA at hi.inet]

El 26/05/2011, a las 18:35, Alex Glikson escribió:

Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome.
Also, see attached the latest version of the HLDesc template.
As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them.

Regards,
Alex

Attendees:

 *   IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT

Agenda:

 *   Generic Enablers
 *   HLDesc progress

Minutes:

 *   List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS)
 *   Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template

Action Items:

 *   For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30.
    *   3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge.
 *   Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE
 *

<FIWARE HLDesc Cloud v0.1.doc><ATT00001..txt>


________________________________
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/20110531/c59cee55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GE.png
Type: image/png
Size: 250731 bytes
Desc: GE.png
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20110531/c59cee55/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.tiff
Type: image/tiff
Size: 66394 bytes
Desc: PastedGraphic-1.tiff
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20110531/c59cee55/attachment.tiff>