What Alex says is fine for me and makes sense with the DoW just like TCloud within T4.4. Andy PS: the diagram I sent was simply an edit of the existing one, with the only difference being a) a split between user and service-provider and the inclusion of OCCI (as requested by Alex). From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: Monday, June 20, 2011 10:06 PM To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Cloud HLDesc update I think we can assume TCloud for IaaS Service Management, and OCCI for IaaS Resource Management -- at least for now. Naturally, the "Interfaces" section should cover interfaces of all the GEs. 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> Date: 20/06/2011 11:54 PM Subject: Re: [Fiware-cloud] Cloud HLDesc update _____ Dear Alex, In the same way, I think that the Dow in the "IaaS Service Management" GE only talk about TCloud and OVF. I am not talking about the interface defined in the "IaaS Resource Management" only talking about the "IaaS Service Management". Regarding a new version of the Andy's diagram, let me some time in order to finalize a new version of the HLDesc and I send you a new version of the Andy's diagram. And finally, I do not have any problem to share the the source files of the various diagrams but we have to check if all of you have the same applications to read them. BR, 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 El 20/06/2011, a las 22:03, Alex Glikson escribió: Dear Fernando, I think it is mentioned in the DoW that what we call now the "IaaS Resource Management" GE will expose OCCI interface. I am not up-to-speed with the details of the different standard interfaces to have a strong opinion (yet). If you have some objections to Andy's diagram -- can you propose your own version, which incorporates OCCI on top of IaaS Resource Management? BTW, it could be helpful to share the source files of the various diagrams in the document.. Thanks, Alex From: FERNANDO LOPEZ AGUILAR < <mailto:fla at tid.es> fla at tid.es> To: "Edmonds, AndrewX" < <mailto:andrewx.edmonds at intel.com> andrewx.edmonds at intel.com> Cc: Alex Glikson/Haifa/IBM at IBMIL, " <mailto:fiware-cloud at lists.fi-ware.eu> fiware-cloud at lists.fi-ware.eu" < <mailto:fiware-cloud at lists.fi-ware.eu> fiware-cloud at lists.fi-ware.eu> Date: 20/06/2011 10:50 PM Subject: Re: [Fiware-cloud] Cloud HLDesc update _____ Upps, Here we have a strong opinion about the diagram that you send today. Firstly we want to know what is the meaning of the different box here (PaaS and IaaS), if we consider them like the different GE that we are working on. And making the association between PaaS and PaaS Management, we have not planned to offer OCCI to the Portal/Toolkit/Script in the PaaS Management. The same in the IaaS Service Management, if the association is between IaaS and IaaS Service Management, we have not planned to offer OCCI interface to the upper layer (PaaS Management and Portal/Script/Toolkit) too. If the IaaS is related to the IaaS Resource Management I cannot comment anything there maybe Alex could give you some more comments. In case of CDMI, ok, we planned to offer CDMI to the IaaS Service Management in order to take control over Object Storage and to deal with the Cloud Storage. We can extend this functionality to the upper layer if we want to offer a service in the PaaS in order to access the data in the Cloud. In that case we could see an extension of IaaS Service Management to use the CDMI to the upper layer. But the PaaS Management itself is not offering CDMI to the upper layer due to it is only need to define the applications and the platform to manage them through the Application Description. 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 El 20/06/2011, a las 19:13, Edmonds, AndrewX escribió: Attached is a possible replacement image related to an open comment (#51) assigned to me. Alex can you merge it with the next rev. of the doc? Andy From: <mailto:fiware-cloud-bounces at lists.fi-ware.eu> fiware-cloud-bounces at lists.fi-ware.eu [ <mailto:fiware-cloud-bounces at lists.fi-ware.eu> mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf OfAlex Glikson Sent: Saturday, June 18, 2011 10:57 PM To: <mailto:fiware-cloud at lists.fi-ware.eu> fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Cloud HLDesc update All, Thanks to everyone who reviewed the document. Please, see a new integrated draft at https://forge.fi-ware.eu/docman/view.php/7/107/FIWARE+HLDesc+Cloud+v0.5.doc (sorry for the delay). Few things for your attention: 1. I've reviewed all the comments, added some new comments and added "STATUS" within the text of each of them (after an initial cleanup and consolidation). * For those marked "Closed" -- the authors of the comments are requested to indicate whether they still think that something needs to be done (otherwise the comment will be deleted in the next revision). * For those marked "Open", I've also assigned an "OWNER". The owners are requests to address the comments ASAP and send the updates to the list (if possible -- by the EOD Monday). 2. I've replaced the architecture diagrams with a new one, and made few changes to the GEs -- please, review. I am going to make another round of reviewing the document on Sunday, and plan to send more comments -- stay tuned :-) Regards, Alex <apiFIware.png><smime.p7s><ATT00001..txt><ATT00002..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> http://www.tid.es/ES/PAGINAS/disclaimer.aspx <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> 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/20110621/1940fb25/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20110621/1940fb25/attachment.bin> -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy