[Fiware-cloud] HLDesc update

[FERNANDO LOPEZ AGUILAR]

Dear Alex,

It answer inline. I hope that it is what do you want to reflect here. If you consider that I need to improve it say me.

BR, Fernando.-

From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson
Sent: Thursday, June 23, 2011 9:35 AM
To: fiware-cloud at lists.fi-ware.eu
Subject: Re: [Fiware-cloud] HLDesc update

Thanks to everyone who has been contributing to the document so far!

Few TODO's that I'm aware of:

 1.  Andy and David has volunteered to review our usage of terminology related to KPIs/metrics and SLAs/SLOs (correspondingly). Please, coordinate between you and send the updates sequentially (so that it won't be needed to merge)

 1.  We need to elaborate a bit our expected dependencies on other work packages, in the "Question Marks" section. Juanjo mentioned that we can learn from the way it is organized in the "Data/Context Management" chapter (https://forge.fi-ware.eu/docman/view.php/7/100/FI-WARE+High-Level+Desc+Data-Context+v2.0+11-06-22+valid+until+11-06-24.doc). Please, provide your feedback by the end of the week. In particular:
    *   The dependency on the Business Framework from WP3 (task 3.3), which we are supposed to use for monetization of cloud services (billing, etc). Since TID is leading this task in WP3, I would like to ask Fernando to briefly follow-up on this, and summarize in a couple of paragraphs (to be placed in the corresponding Question Mark section).
In order to guarantee the dependency on the Business Framework from WP3 (task 3.3) with the Cloud Hosting, it is necessary to include the service or application hosting cost defined in the Business Framework. It means that it it necessary to define clearly the interfaces both Business Framework and Cloud Hosting in order to allow the relationship between the Accounting part in the Cloud and the Billing part in the Business Framework and send the necessary information related to the payment of the service/application deploys in the Cloud . In addition, other requirement that the Business Framework have to take into consideration are the SLA violations with means that we need to applied some compensation policies over the required service, which means that the accounting and billing system are dynamic data and can change during the execution of a service.

    *   The dependencies in the area of Security (WP8) -- we need to designate someone to follow-up on this, and summarize our initial expectations there. Andy has agreed to give it a try.

 1.
Is there anything else that I'm missing? Of course, any other comments are welcome.

Regards,
Alex

P.S. I've renamed the document following Juanjo's convention more closely, now it is at https://forge.fi-ware.eu/docman/view.php/7/107/FI-WARE+High-level+Desc+Cloud+v0.7+11-06-22.doc



From:        Alex Glikson/Haifa/IBM at IBMIL
To:        fiware-cloud at lists.fi-ware.eu<mailto:fiware-cloud at lists.fi-ware.eu>, jhierro at tid.es<mailto:jhierro at tid.es>
Date:        22/06/2011 11:01 PM
Subject:        [Fiware-cloud] HLDesc update
Sent by:        fiware-cloud-bounces at lists.fi-ware.eu<mailto:fiware-cloud-bounces at lists.fi-ware.eu>
________________________________



Hi,

I've uploaded an integrated version of the Cloud chapter of the HLDesc (https://forge.fi-ware.eu/docman/view.php/7/107/FIWARE+HLDesc+Cloud+v0.7.doc),

Regards,
Alex

P.S. BTW, I've removed most of the comments -- apologize I've removed something which was not addressed yet._______________________________________________
Fiware-cloud mailing list
Fiware-cloud at lists.fi-ware.eu<mailto:Fiware-cloud at lists.fi-ware.eu>
http://lists.fi-ware.eu/listinfo/fiware-cloud

________________________________
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/20110624/261631c5/attachment.html>