From andrewx.edmonds at intel.com Mon Sep 5 14:30:09 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Mon, 5 Sep 2011 12:30:09 +0000 Subject: [Fiware-cloud] Confcall tomorrow? Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1901548F@IRSMSX101.ger.corp.intel.com> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- 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. From GLIKSON at il.ibm.com Mon Sep 5 17:20:19 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 5 Sep 2011 18:20:19 +0300 Subject: [Fiware-cloud] conf call tomorrow Message-ID: Hi All, As planned, we are going to have a conf call tomorrow, at our regular time slot (11am CET). The GEs that we still need to cover (in terms of architecture, existing assets, gaps, leading to a list of work items to bridge the gaps): Service Management, PaaS enablement, Cloud Edge, Self-service interfaces. We might not be able to cover all of them tomorrow, so we might need to continue the discussions during the F2F next week. Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Tue Sep 6 11:52:27 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 6 Sep 2011 09:52:27 +0000 Subject: [Fiware-cloud] Monitoring In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1901440E@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE1901440E@IRSMSX101.ger.corp.intel.com> Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE19015648@IRSMSX101.ger.corp.intel.com> Resending as the topic on monitoring occurred on the bridge again. Andy -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Edmonds, AndrewX Sent: Thursday, August 25, 2011 2:01 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Monitoring I've put down some of my thoughts on monitoring that I've talked about before on confcalls. Comments etc very welcome! HTH, Andy -------------- next part -------------- A non-text attachment was scrubbed... Name: monitoring.pdf Type: application/pdf Size: 60942 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- 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. From andrewx.edmonds at intel.com Tue Sep 6 11:54:06 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 6 Sep 2011 09:54:06 +0000 Subject: [Fiware-cloud] Extracted Security Requirements Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE19015655@IRSMSX101.ger.corp.intel.com> Attached. Please review the excel sheet (assembled from the attached .doc file) and if your task/GE is not listed or listed incorrectly please reply. Andy -------------- next part -------------- A non-text attachment was scrubbed... Name: security requirements.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 41919 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE-Security Issues WP4 - WP8 input document.doc Type: application/msword Size: 32768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- 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. From GLIKSON at il.ibm.com Tue Sep 6 21:12:23 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 6 Sep 2011 22:12:23 +0300 Subject: [Fiware-cloud] preparation towards the Cloud Hosting session at the Torino F2F next week Message-ID: All, In order to make the Cloud Hosting session during the Torino F2F next week as productive as possible, I would like to ask each of the GE leads to prepare (together with the contributing companies) few slides outlining the following details for the corresponding GE: summary of the main GE requirements, as outlined in the HLDesc -- 1-2 slides architecture of the GE, including main components (including some details on how they are used to meet the above requirements), interfaces between components, as well as external interfaces of the GE (towards the 'user' and/or other GEs) -- a diagram (1 slide) plus a bullet on each component/interface (1-2 slides) short description of the assets, as well as their mapping to the architecture -- 1 slide per asset, plus augmented architecture slide from #2 showing the mapping integration challenges, if any -- up to 1-2 slides gaps (i.e., components from #2 which are not fully covered by assets from #3) -- a bullet on each gap (1-2 slides in total), plus augmented architecture slide from #2 showing the gaps work items to address the gaps -- 1 slide on each work item, providing a bit more details on the work needed to address the gaps, associated challenges, etc Let's plan having 1-2 hours long sessions on each GE, to discuss the above. Also, we will need to allocate time to discuss topics applicable to several GEs, like metrics exchange infrastructure, security, interlock with other WPs, etc (I will try to come up with a tentative agenda before the F2F). The GEs and the owners are: Resource Management -- Alex Service Management -- Fernando Object Storage -- Andy Cloud Edge -- Serge PaaS enablement -- Fernando Monitoring -- Andy Portal -- Joaquin Accounting -- Any comments/suggestions are welcome. Thanks! Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Sun Sep 11 16:55:01 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 11 Sep 2011 17:55:01 +0300 Subject: [Fiware-cloud] Fw: [Fiware] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin Message-ID: All, Please, see attached the proposed agenda for the Cloud Hosting Parallel Sessions. Comments are welcome! In order to ensure we use the F2F time efficiently, please, come well-prepared for discussions, based on the outline I've sent in a separate email (requirements, architecture, interfaces, assets, gaps, etc). Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 11/09/2011 05:50 PM ----- From: Juanjo Hierro To: "fiware at lists.fi-ware.eu" , "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 11/09/2011 11:09 AM Subject: [Fiware] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin Sent by: fiware-bounces at lists.fi-ware.eu Hi all, Please find enclosed the agenda for our Plenary (General Assembly) meeting in Turin. If you have any particular comment or request, don't hesitate to contact me. See you in Turin, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 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 [attachment "FI-WARE GA Sep 2011 Agenda vfinal.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE GA Sep 2011 Agenda - Cloud.xls Type: application/vnd.ms-excel Size: 37888 bytes Desc: not available URL: From fla at tid.es Mon Sep 12 10:46:01 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 12 Sep 2011 10:46:01 +0200 Subject: [Fiware-cloud] FW: WP collaboration sessions at the Turin meeting In-Reply-To: References: Message-ID: <8EE61BA0CAEDBD4E9DA928D1206463D2A185165F53@EXCLU2K7.hi.inet> Hi Alex, We need to change the agenda due to it? BR, Fernando From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: lunes, 12 de septiembre de 2011 10:04 To: fiware at lists.fi-ware.eu Subject: [Fiware] WP collaboration sessions at the Turin meeting Dear all GA participants, at the GA in Turin there will be parallel workshops for the individual work packages. That's fine. However, I think we should use the time also for discussing cross WP collaboration. As I noticed there is already a meeting planned for Wednesday morning 9-12, where experts from Data, IoT, and Apps will come together. I believe there are other constellations that should meet, at least from the perspective of the Apps WP. f.e.: * Cloud - Apps * Security - Apps * Interface to the network - Apps I suggest to use the Wednesday morning timeslot for parallel cross WP sessions. This would also produce valuable details for the following backlog etc. discussions Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From serge.defrance at technicolor.com Mon Sep 12 13:46:29 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Mon, 12 Sep 2011 13:46:29 +0200 Subject: [Fiware-cloud] Fw: [Fiware] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6EFBED3939@MOPESMBX01.eu.thmulti.com> Dear all, In preparation of our coming meeting, please find attached two documents related the GE ? cloud edge ?. These may be a support for our discussion. I circulated equivalent documents in WP7. Regards, Serge. From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: dimanche 11 septembre 2011 16:55 To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: [Fiware] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin All, Please, see attached the proposed agenda for the Cloud Hosting Parallel Sessions. Comments are welcome! In order to ensure we use the F2F time efficiently, please, come well-prepared for discussions, based on the outline I've sent in a separate email (requirements, architecture, interfaces, assets, gaps, etc). Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 11/09/2011 05:50 PM ----- From: Juanjo Hierro To: "fiware at lists.fi-ware.eu" , "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 11/09/2011 11:09 AM Subject: [Fiware] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin Sent by: fiware-bounces at lists.fi-ware.eu ________________________________ Hi all, Please find enclosed the agenda for our Plenary (General Assembly) meeting in Turin. If you have any particular comment or request, don't hesitate to contact me. See you in Turin, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 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 [attachment "FI-WARE GA Sep 2011 Agenda vfinal.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TechnicolorAssetsWP4.docx.zip Type: application/x-zip-compressed Size: 52022 bytes Desc: TechnicolorAssetsWP4.docx.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CloudEdgeWP4_EPIC_v00.xls.zip Type: application/x-zip-compressed Size: 29473 bytes Desc: CloudEdgeWP4_EPIC_v00.xls.zip URL: From GLIKSON at il.ibm.com Tue Sep 13 23:06:44 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 14 Sep 2011 00:06:44 +0300 Subject: [Fiware-cloud] [Fiware] Proposal for parallel sessions In-Reply-To: References: Message-ID: Hi, >From Cloud perspective, we need interlocks with Security, I2ND, Data and Apps -- about 1 hour each. Regards, Alex From: Garino Pierangelo To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Cc: "'fiware at lists.fi-ware.eu' (fiware at lists.fi-ware.eu)" Date: 13/09/2011 11:43 PM Subject: [Fiware] Proposal for parallel sessions Sent by: fiware-bounces at lists.fi-ware.eu Hi All, this is the proposal for parallel sessions tomorrow (and Thursday morning), according to what discussed at the end of plenary session today and to the requests I received so far (rearrangements are in red). BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations ? Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. [attachment "FI-WARE GA Sep 2011 Agenda vfinal-PG3.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From andrewx.edmonds at intel.com Wed Sep 14 09:53:37 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Wed, 14 Sep 2011 07:53:37 +0000 Subject: [Fiware-cloud] Presentations on Object Storage, Monitoring & Security Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE190166F9@IRSMSX101.ger.corp.intel.com> http://dl.dropbox.com/u/165239/fiware-monitoring-turin-0911.pptx http://dl.dropbox.com/u/165239/fiware-object-storage-turin-0911.pptx http://dl.dropbox.com/u/165239/fiware-security-turin-0911.pptx Andy -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- 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. From fla at tid.es Wed Sep 14 09:58:44 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 14 Sep 2011 09:58:44 +0200 Subject: [Fiware-cloud] Presentations on IaaS Service Mngt. & PaaS Mngt. In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE190166F9@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE190166F9@IRSMSX101.ger.corp.intel.com> Message-ID: <717018EC-1296-446C-B271-C0723702CF8B@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: -------------- next part -------------- A non-text attachment was scrubbed... Name: IaaS Service Management + PaaS Management (Turin Sept'11) 3.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 717061 bytes Desc: IaaS Service Management + PaaS Management (Turin Sept'11) 3.pptx URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From joaquin.salvachua at upm.es Wed Sep 14 10:13:35 2011 From: joaquin.salvachua at upm.es (Joaquin Salvachua) Date: Wed, 14 Sep 2011 10:13:35 +0200 Subject: [Fiware-cloud] Presentation about Portal and Self-service API Message-ID: Hello, Here i include the presentation. Joaqu?n -------------- next part -------------- A non-text attachment was scrubbed... Name: FI_WARE-CLOUDPORTAL.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 3228972 bytes Desc: not available URL: From GLIKSON at il.ibm.com Mon Sep 19 21:36:02 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 19 Sep 2011 22:36:02 +0300 Subject: [Fiware-cloud] IMPORTANT: Next Steps Message-ID: Hi All, It was great to see many of you in Turino last week. First, I'm out of office tomorrow, so there will be no weekly call. However, I would like us to make progress offline, as follows. 1. Highlights and action items from the F2F at Turin Please, send me your notes regarding highlights (main accomplishments and issues) and action items from the F2F discussions last week. I will consolidate them and will send to Juanjo (per his request). For your convenience, here is a list of sessions: Cloud Edge, Cloud Edge RM [Serge, Alex] IaaS Service Management [Fernando] PaaS [Fernando] IaaS DataCenter Resource Management [Alex, Andy] Object Storage [Andy] Self-Service Interfaces [Juaquin] Monitoring [Andy] Security [Andy] Interlock with I2ND Interlock with Security [Andy] Interlock with Apps [David] Interlock with Data [Andy] Of course, not only the people mentioned above can contribute. Please, send me your input by EOD Wednesday. Make it brief (concise bullets). 2. Epics spreadsheets As you know, we need to come up with a list of Epics for each GE, outlining the main areas of work we envision in the project (focusing on the first release). Please, send me by the end of the week your initial lists, with some details for each Epic. Let's follow the format in the attached Excel -- it is an 'optimized' version of the original template (I've copied few of Fernando's epics into the new table format, as an example). Please, remember that the work items should focus on work that is still to be done, by our team. So, when considering various assets, the work items should only refer to their integration and enhancements -- and not to features which are already there, or are developed by someone else. There are many cool features in Excel that can potentially make the usage of Excel to manage the Epics rather convenient, but let's wait until the Agile tooling topics becomes more clear (I'm not sure Tracker is better than Excel, for our internal use). Let's discuss both topics in our next week's call, following the input that each of us provides. Thanks! Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Backlog entries description v0.1 TID - Alex.xls Type: application/vnd.ms-excel Size: 115200 bytes Desc: not available URL: From GLIKSON at il.ibm.com Wed Sep 21 17:29:45 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 21 Sep 2011 18:29:45 +0300 Subject: [Fiware-cloud] IMPORTANT: Next Steps In-Reply-To: References: Message-ID: Below is my initial input for highlights and action items. Please, augment with your input (please, use a different color). Thanks. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 19/09/2011 10:36 PM Subject: [Fiware-cloud] IMPORTANT: Next Steps Sent by: fiware-cloud-bounces at lists.fi-ware.eu Hi All, It was great to see many of you in Turino last week. First, I'm out of office tomorrow, so there will be no weekly call. However, I would like us to make progress offline, as follows. 1. Highlights and action items from the F2F at Turin Please, send me your notes regarding highlights (main accomplishments and issues) and action items from the F2F discussions last week. I will consolidate them and will send to Juanjo (per his request). For your convenience, here is a list of sessions: General -- main accomplishments: Socializing among team members, including additional team members which did not attend the kick-off in May. Improved team atmosphere and trust. Gained common understanding of the architecture, main assets, interfaces, potential integration challenges and gaps -- for the entire WP as a whole, as well as for individual GEs Identified several significant gaps (see below), some of which may become topics for open calls Conducted highly productive joint sessions with other WPs (see more details below) Met in person key representatives of other teams, thus improving future collaboration Gained better understanding of what other WPs are doing Identified and verified potential integration points and assets/GEs that can be leveraged Cloud Edge, Cloud Edge RM [Serge, Alex] Reviewed the architecture of the Cloud Proxy Reviewed end-to-end scenario of provisioning of an application hosted in the cloud, having a component designed to run close to the end-user (on a Cloud Proxy) Refined WP architecture to address the distinction between the Cloud Proxy device (running outside of the centralized cloud infrastructure) and the management component that would typically run within the centralized infrastructure and act as a proxy between the centralized cloud management stack and the numerous Cloud Proxy devices located close to the end-uses. Identified a gap in providing the above management component. Action Item [Serge]: find out whether this gap can be contained (e.g., by re-balancing the Cloud Proxy related work between WP4 and WP7). Note: this issue was discussed at the PCC, and it was mentioned that the chances to be able to handle this gap via the open calls mechanisms are not high (as this is a mandatory component to provide the end-to-end functionality of Cloud Proxy, which should have been taken into account in the original plan) IaaS Service Management [Fernando] TBD It should be possible to design services that comprise components that run on Cloud Proxy (and potentially also end-devices -- see comment from I2ND interlock), as well as object storage resources. This should be reflected in service manifest, as well as handled during provisioning and life cycle management of services. A service composition tool should be part of the ecosystem provided to the application developer/provider. Should be considered for the Open Call. Scalability and security aspects of Claudia should be considered. PaaS [Fernando] TBD The current approach for PaaS provisioning is to install middleware components into an existing running OS (with Chef), which has been installed separately (in our case -- as part of the provisioning of the corresponding VM). A unified approach should be considered, in which the VM images already include the middleware components pre-installed, and they just need to be customized during provisioning. It is not clear whether OVF-based manifest would be a good fit to describe PaaS-level services. Other alternatives should be considered. IaaS DataCenter Resource Management [Alex, Andy] Reviewed WP architecture, mapped assets and gaps A need for common monitoring infrastructure was stressed The resource management layer should provide capability of orchestrating operations across groups of VMs -- e.g., in a scenario of service snapshot. We should consider supporting non-virtualized workloads Object Storage [Andy] Self-Service Interfaces [Juaquin] A collaboration-driven approach to Cloud Portal was presented Action Item [Alex, Joaquin]: assess whether this can be contained within the existing funding. It might make sense to focus on have a fully-functional cloud portal as a subject for an Open Call. Monitoring [Andy] Security [Andy] Interlock with I2ND It was mentioned that in some cases a cloud application may include a component designed to run at the end-user device (e.g., a mobile phone) -- either within the Web browser, or as a 'rich client' component. In a way, this can be considered as another 'tier', besides the centralized cloud infrastructure and the cloud proxy. This should be taken into account when designing the service manifest, as well as during provisioning and service life cycle management. Interlock with Security [Andy] Reviewed security considerations which might apply to Cloud Hosting Action Item [Andy to coordinate]: need to refine our security considerations in the HLD (once transferred to the Wiki) It was noted that the security WP is interested in leveraging the common infrastructure for monitoring and CMDB. Cloud Hosting does not intend having a centralized CMDB, but having a single monitoring system which can be augmented with security probes definitely makes sense. Action Item [Alex] need to follow-up on monitoring infrastructure, across GEs and WPs Interlock with Apps [David] In order to drive business processes related to applications deployed in the cloud (e.g., SLAs), resource-related metrics produced by Cloud WP components must be accessible by the components of the Apps WP. Mashup execution engines might be hosted on the cloud (PaaS would probably make more sense than IaaS) Interlock with Data [Andy, David] In order to develop a common monitoring system, 3 components have been identified that will be provided by the Data Management WP: pub/sub broker, Big Data and Complex Event Processing. Need to follow-up on architecture, requirements, interfaces, schedule, etc. Of course, not only the people mentioned above can contribute. Please, send me your input by EOD Wednesday. Make it brief (concise bullets). 2. Epics spreadsheets As you know, we need to come up with a list of Epics for each GE, outlining the main areas of work we envision in the project (focusing on the first release). Please, send me by the end of the week your initial lists, with some details for each Epic. Let's follow the format in the attached Excel -- it is an 'optimized' version of the original template (I've copied few of Fernando's epics into the new table format, as an example). Please, remember that the work items should focus on work that is still to be done, by our team. So, when considering various assets, the work items should only refer to their integration and enhancements -- and not to features which are already there, or are developed by someone else. There are many cool features in Excel that can potentially make the usage of Excel to manage the Epics rather convenient, but let's wait until the Agile tooling topics becomes more clear (I'm not sure Tracker is better than Excel, for our internal use). Let's discuss both topics in our next week's call, following the input that each of us provides. Thanks! Alex [attachment "Backlog entries description v0.1 TID - Alex.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Wed Sep 21 22:33:27 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 21 Sep 2011 22:33:27 +0200 Subject: [Fiware-cloud] IMPORTANT: Next Steps In-Reply-To: References: Message-ID: <5689E0B2-41F5-4152-BEED-61C430CA1098@tid.es> My contributions in red... 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 21/09/2011, a las 17:29, Alex Glikson escribi?: Below is my initial input for highlights and action items. Please, augment with your input (please, use a different color). Thanks. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 19/09/2011 10:36 PM Subject: [Fiware-cloud] IMPORTANT: Next Steps Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Hi All, It was great to see many of you in Turino last week. First, I'm out of office tomorrow, so there will be no weekly call. However, I would like us to make progress offline, as follows. 1. Highlights and action items from the F2F at Turin Please, send me your notes regarding highlights (main accomplishments and issues) and action items from the F2F discussions last week. I will consolidate them and will send to Juanjo (per his request). For your convenience, here is a list of sessions: * General -- main accomplishments: * Socializing among team members, including additional team members which did not attend the kick-off in May. Improved team atmosphere and trust. * Gained common understanding of the architecture, main assets, interfaces, potential integration challenges and gaps -- for the entire WP as a whole, as well as for individual GEs * Identified several significant gaps (see below), some of which may become topics for open calls * Conducted highly productive joint sessions with other WPs (see more details below) * Met in person key representatives of other teams, thus improving future collaboration * Gained better understanding of what other WPs are doing * Identified and verified potential integration points and assets/GEs that can be leveraged * Cloud Edge, Cloud Edge RM [Serge, Alex] * Reviewed the architecture of the Cloud Proxy * Reviewed end-to-end scenario of provisioning of an application hosted in the cloud, having a component designed to run close to the end-user (on a Cloud Proxy) * Refined WP architecture to address the distinction between the Cloud Proxy device (running outside of the centralized cloud infrastructure) and the management component that would typically run within the centralized infrastructure and act as a proxy between the centralized cloud management stack and the numerous Cloud Proxy devices located close to the end-uses. * Identified a gap in providing the above management component. * Action Item [Serge]: find out whether this gap can be contained (e.g., by re-balancing the Cloud Proxy related work between WP4 and WP7). * Note: this issue was discussed at the PCC, and it was mentioned that the chances to be able to handle this gap via the open calls mechanisms are not high (as this is a mandatory component to provide the end-to-end functionality of Cloud Proxy, which should have been taken into account in the original plan) * * IaaS Service Management [Fernando] * TBD * It should be possible to design services that comprise components that run on Cloud Proxy (and potentially also end-devices -- see comment from I2ND interlock), as well as object storage resources. This should be reflected in service manifest, as well as handled during provisioning and life cycle management of services. It must be studied. * A service composition tool should be part of the ecosystem provided to the application developer/provider. Should be considered for the Open Call. A Service composition tool should be part of the Portal or a specific tool provided by the specific WP within FI-WARE (TBD). IMHO It is not part of the SM. * Scalability and security aspects of Claudia should be considered. The security aspects must be applied to all GE. BTW, we need more discussion about this topics due to we need to clarify all the security requirements. * How do we store/mngt. the credentials (e.g. EC2 Amazon)? [AI Fernando] * What is the possibility of scaling Claudia? [AI Fernando] * It is possible to update the service manifest dynamically (I suppose yes) [AI Fernando] * There are not trivial dependencies between Claudia and IaaS Data Center Mngt. * Why do we need to use clone VMs? Can we provide some UCs? * Integration with SLA-SLO. Which type of SLA we are using. How Claudia manages the SLAs? * Interoperability between Cloud Standard API (DMTF CIMI) and OCCI through OVF. Especify the OVF exchanges messages in common (the same for CDMI could be applied) [AI Fernando Andy Alex] * * PaaS [Fernando] * TBD * The current approach for PaaS provisioning is to install middleware components into an existing running OS (with Chef), which has been installed separately (in our case -- as part of the provisioning of the corresponding VM). A unified approach should be considered, in which the VM images already include the middleware components pre-installed, and they just need to be customized during provisioning * * It is not clear whether OVF-based manifest would be a good fit to describe PaaS-level services. Other alternatives should be considered. We prefer to extend a common standard API (OVF) and not use another one from the beginning. We want to use the same protocol that we are using in the SM. Also the interface that PaaS GE provide is Cloud Standard API based on OVF. * How can we specify the elasticity rules in terms of PaaS? [AI Fernando] * Why do we use Chef for the PaaS? [AI Fernando] * * IaaS DataCenter Resource Management [Alex, Andy, Fernando] * Reviewed WP architecture, mapped assets and gaps * A need for common monitoring infrastructure was stressed * The resource management layer should provide capability of orchestrating operations across groups of VMs -- e.g., in a scenario of service snapshot. * We should consider supporting non-virtualized workloads * proximity policies * translate the requirements of the SM to the policies of the CDRM * * Object Storage [Andy, Fernando] * Interface to openflow (?) * Cloud Standard API - CMDI - OVF interoperability * Action Item [Fernando]: CDMI interface specification of the SM * Self-Service Interfaces [Juaquin] * A collaboration-driven approach to Cloud Portal was presented * Action Item [Alex, Joaquin]: assess whether this can be contained within the existing funding. It might make sense to focus on have a fully-functional cloud portal as a subject for an Open Call. * where is the user management? permission, accounting, etc? * How to manage the SSO? and how to translate it to each GE? * * Monitoring [Andy] * Security [Andy] * Interlock with I2ND * It was mentioned that in some cases a cloud application may include a component designed to run at the end-user device (e.g., a mobile phone) -- either within the Web browser, or as a 'rich client' component. In a way, this can be considered as another 'tier', besides the centralized cloud infrastructure and the cloud proxy. This should be taken into account when designing the service manifest, as well as during provisioning and service life cycle management. * Interlock with Security [Andy] * Reviewed security considerations which might apply to Cloud Hosting. How to protect the services in the Cloud? * Action Item [Andy to coordinate]: need to refine our security considerations in the HLD (once transferred to the Wiki) * It was noted that the security WP is interested in leveraging the common infrastructure for monitoring and CMDB. Cloud Hosting does not intend having a centralized CMDB, but having a single monitoring system which can be augmented with security probes definitely makes sense. * Action Item [Alex] need to follow-up on monitoring infrastructure, across GEs and WPs * Interlock with Apps [David] * In order to drive business processes related to applications deployed in the cloud (e.g., SLAs), resource-related metrics produced by Cloud WP components must be accessible by the components of the Apps WP. * Mashup execution engines might be hosted on the cloud (PaaS would probably make more sense than IaaS) * If we move one service from one Data Center to another. How does the user know the way to access it? * * Interlock with Data [Andy, David] * In order to develop a common monitoring system, 3 components have been identified that will be provided by the Data Management WP: pub/sub broker, Big Data and Complex Event Processing. Need to follow-up on architecture, requirements, interfaces, schedule, etc. Of course, not only the people mentioned above can contribute. Please, send me your input by EOD Wednesday. Make it brief (concise bullets). 2. Epics spreadsheets As you know, we need to come up with a list of Epics for each GE, outlining the main areas of work we envision in the project (focusing on the first release). Please, send me by the end of the week your initial lists, with some details for each Epic. Let's follow the format in the attached Excel -- it is an 'optimized' version of the original template (I've copied few of Fernando's epics into the new table format, as an example). Please, remember that the work items should focus on work that is still to be done, by our team. So, when considering various assets, the work items should only refer to their integration and enhancements -- and not to features which are already there, or are developed by someone else. There are many cool features in Excel that can potentially make the usage of Excel to manage the Epics rather convenient, but let's wait until the Agile tooling topics becomes more clear (I'm not sure Tracker is better than Excel, for our internal use). Let's discuss both topics in our next week's call, following the input that each of us provides. Thanks! Alex [attachment "Backlog entries description v0.1 TID - Alex.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: From andrewx.edmonds at intel.com Fri Sep 23 11:29:29 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Fri, 23 Sep 2011 09:29:29 +0000 Subject: [Fiware-cloud] IMPORTANT: Next Steps In-Reply-To: <5689E0B2-41F5-4152-BEED-61C430CA1098@tid.es> References: <5689E0B2-41F5-4152-BEED-61C430CA1098@tid.es> Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE19028FEF@IRSMSX101.ger.corp.intel.com> I?ve added additional pieces below (yellow). Apologies for the delay. Andy Hi All, It was great to see many of you in Turino last week. First, I'm out of office tomorrow, so there will be no weekly call. However, I would like us to make progress offline, as follows. 1. Highlights and action items from the F2F at Turin Please, send me your notes regarding highlights (main accomplishments and issues) and action items from the F2F discussions last week. I will consolidate them and will send to Juanjo (per his request). For your convenience, here is a list of sessions: * General -- main accomplishments: * Socializing among team members, including additional team members which did not attend the kick-off in May. Improved team atmosphere and trust. * Gained common understanding of the architecture, main assets, interfaces, potential integration challenges and gaps -- for the entire WP as a whole, as well as for individual GEs * Identified several significant gaps (see below), some of which may become topics for open calls * Conducted highly productive joint sessions with other WPs (see more details below) * Met in person key representatives of other teams, thus improving future collaboration * Gained better understanding of what other WPs are doing * Identified and verified potential integration points and assets/GEs that can be leveraged * Cloud Edge, Cloud Edge RM [Serge, Alex] * Reviewed the architecture of the Cloud Proxy * Reviewed end-to-end scenario of provisioning of an application hosted in the cloud, having a component designed to run close to the end-user (on a Cloud Proxy) * Refined WP architecture to address the distinction between the Cloud Proxy device (running outside of the centralized cloud infrastructure) and the management component that would typically run within the centralized infrastructure and act as a proxy between the centralized cloud management stack and the numerous Cloud Proxy devices located close to the end-uses. * Identified a gap in providing the above management component. * Action Item [Serge]: find out whether this gap can be contained (e.g., by re-balancing the Cloud Proxy related work between WP4 and WP7). * Note: this issue was discussed at the PCC, and it was mentioned that the chances to be able to handle this gap via the open calls mechanisms are not high (as this is a mandatory component to provide the end-to-end functionality of Cloud Proxy, which should have been taken into account in the original plan) * * IaaS Service Management [Fernando] * TBD * It should be possible to design services that comprise components that run on Cloud Proxy (and potentially also end-devices -- see comment from I2ND interlock), as well as object storage resources. This should be reflected in service manifest, as well as handled during provisioning and life cycle management of services. It must be studied. * A service composition tool should be part of the ecosystem provided to the application developer/provider. Should be considered for the Open Call. A Service composition tool should be part of the Portal or a specific tool provided by the specific WP within FI-WARE (TBD). IMHO It is not part of the SM. * Scalability and security aspects of Claudia should be considered. The security aspects must be applied to all GE. BTW, we need more discussion about this topics due to we need to clarify all the security requirements. * How do we store/mngt. the credentials (e.g. EC2 Amazon)? [AI Fernando] * What is the possibility of scaling Claudia? [AI Fernando] * It is possible to update the service manifest dynamically (I suppose yes) [AI Fernando] * There are not trivial dependencies between Claudia and IaaS Data Center Mngt. * Why do we need to use clone VMs? Can we provide some UCs? * Integration with SLA-SLO. Which type of SLA we are using. How Claudia manages the SLAs? * Interoperability between Cloud Standard API (DMTF CIMI) and OCCI through OVF. Especify the OVF exchanges messages in common (the same for CDMI could be applied) [AI Fernando Andy Alex] * OGF33: Venus-C (venus-c.eu) has a OVF to OCCI tool * France telecom participation in WP4 discussed * Gap related to billing/accounting noted * * PaaS [Fernando] * TBD * The current approach for PaaS provisioning is to install middleware components into an existing running OS (with Chef), which has been installed separately (in our case -- as part of the provisioning of the corresponding VM). A unified approach should be considered, in which the VM images already include the middleware components pre-installed, and they just need to be customized during provisioning ? * It is not clear whether OVF-based manifest would be a good fit to describe PaaS-level services. Other alternatives should be considered. We prefer to extend a common standard API (OVF) and not use another one from the beginning. We want to use the same protocol that we are using in the SM. Also the interface that PaaS GE provide is Cloud Standard API based on OVF. * How can we specify the elasticity rules in terms of PaaS? [AI Fernando] * Why do we use Chef for the PaaS? [AI Fernando] * * IaaS DataCenter Resource Management [Alex, Andy, Fernando] * Reviewed WP architecture, mapped assets and gaps * A need for common monitoring infrastructure was stressed * The resource management layer should provide capability of orchestrating operations across groups of VMs -- e.g., in a scenario of service snapshot. * We should consider supporting non-virtualized workloads * proximity policies * translate the requirements of the SM to the policies of the CDRM * number of WP7 folks are interested in Network-as-a-Service, something that OpenStack/Quantum can provide ? @andy to discuss further with respective WP7 people * * Object Storage [Andy, Fernando] * Interface to openflow (?) * This is NOT related to Object Storage. * Cloud Standard API - CMDI - OVF interoperability * Action Item [Fernando]: CDMI interface specification of the SM * @andy Further investigations required for CDMI on swift * Self-Service Interfaces [Juaquin] * A collaboration-driven approach to Cloud Portal was presented * Action Item [Alex, Joaquin]: assess whether this can be contained within the existing funding. It might make sense to focus on have a fully-functional cloud portal as a subject for an Open Call. * where is the user management? permission, accounting, etc * How to manage the SSO? and how to translate it to each GE? * Monitoring [Andy] * Monitoring architecture presented * Noted that Analysis should cover both online (e.g. CEP) and offline (e.g. MapReduce) * Noted that Storage should cover both optimized time series storage (e.g. rrdtool, graphite) and BigData storage (e.g. Hadoop/HDFS) * Metric sources should have the possibility to be configured (policies) from a central location * Visualisation noted as a deficiency and possibly subject to an open call * Security [Andy] * Presented extracted security requirements * Andy to continue as mediator between WP4 and WP8 * Representative pleased to see WP4?s consideration of requirements * @all Plan to 1st specify WP4 EPICs and then add/modify to account for security requirements * Noted that OpenStack keystone can be considered as an asset providing SSO * Interlock with I2ND * It was mentioned that in some cases a cloud application may include a component designed to run at the end-user device (e.g., a mobile phone) -- either within the Web browser, or as a 'rich client' component. In a way, this can be considered as another 'tier', besides the centralized cloud infrastructure and the cloud proxy. This should be taken into account when designing the service manifest, as well as during provisioning and service life cycle management. * Interest in Network as a Service from WP7 people. Need to understand better integration point here. * Interlock with Security [Andy] * Reviewed security considerations which might apply to Cloud Hosting. How to protect the services in the Cloud? * Action Item [Andy to coordinate]: need to refine our security considerations in the HLD (once transferred to the Wiki) * It was noted that the security WP is interested in leveraging the common infrastructure for monitoring and CMDB. Cloud Hosting does not intend having a centralized CMDB, but having a single monitoring system which can be augmented with security probes definitely makes sense. * Action Item [Alex] need to follow-up on monitoring infrastructure, across GEs and WPs * Interlock with Apps [David] * In order to drive business processes related to applications deployed in the cloud (e.g., SLAs), resource-related metrics produced by Cloud WP components must be accessible by the components of the Apps WP. * Mashup execution engines might be hosted on the cloud (PaaS would probably make more sense than IaaS) * If we move one service from one Data Center to another. How does the user know the way to access it? * There is a need from the WP to have WP4 services described as USDL * Interlock with Data [Andy, David] * In order to develop a common monitoring system, 3 components have been identified that will be provided by the Data Management WP: pub/sub broker, Big Data and Complex Event Processing. Need to follow-up on architecture, requirements, interfaces, schedule, etc. * Presented monitoring architecture using GEs as building blocks Of course, not only the people mentioned above can contribute. Please, send me your input by EOD Wednesday. Make it brief (concise bullets). 2. Epics spreadsheets As you know, we need to come up with a list of Epics for each GE, outlining the main areas of work we envision in the project (focusing on the first release). Please, send me by the end of the week your initial lists, with some details for each Epic. Let's follow the format in the attached Excel -- it is an 'optimized' version of the original template (I've copied few of Fernando's epics into the new table format, as an example). Please, remember that the work items should focus on work that is still to be done, by our team. So, when considering various assets, the work items should only refer to their integration and enhancements -- and not to features which are already there, or are developed by someone else. There are many cool features in Excel that can potentially make the usage of Excel to manage the Epics rather convenient, but let's wait until the Agile tooling topics becomes more clear (I'm not sure Tracker is better than Excel, for our internal use). Let's discuss both topics in our next week's call, following the input that each of us provides. Thanks! Alex [attachment "Backlog entries description v0.1 TID - Alex.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- 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. From andrewx.edmonds at intel.com Mon Sep 26 20:00:06 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Mon, 26 Sep 2011 18:00:06 +0000 Subject: [Fiware-cloud] Epics Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1902984A@IRSMSX101.ger.corp.intel.com> Here are the current descriptions of epics: http://dl.dropbox.com/u/165239/FIWare%20WP4%20Epics.html I would also ask all in cloud hosting to pay attention to the extracted security requirements [1], I presented in Turin when you are describing your epics. Andy [1] http://dl.dropbox.com/u/165239/fiware-security-turin-0911.pptx -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- 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. From GLIKSON at il.ibm.com Mon Sep 26 22:31:30 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 26 Sep 2011 23:31:30 +0300 Subject: [Fiware-cloud] Epics In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1902984A@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE1902984A@IRSMSX101.ger.corp.intel.com> Message-ID: Thanks Andy, I will work on combining your epics with my list (focusing on resource management). The granularity of work items seems a bit different than what I had in mind, though. We can discuss during the meeting. Below is my view of this (rather aligned with Juanjo's, I think). Time line: - sprint -- a period of 1 months length - release, or "minor release" -- a period of 3 months (comprising 3 sprints) - major release -- an official FI-WARE deliverable (there are 3 such releases, in months 12, 24 and 33). After each major release, there will be a minor release that will focus on integration and testbed support Work items: - Epic or Theme -- a significant technical area of work to be covered by the project. Is likely to include work items with few or no dependencies on other themes (but as fine-grained as possible without violating this criteria). Llikely to remain "open" throughout the releases. The level of investment in each Theme is derived from prioritization of features (as defined below). - Feature -- part of a Theme, having well-defined functionality, scope and acceptance criteria, scheduled for a specific (minor) release. - Story -- part of a Feature, having well-defined functionality, scope and acceptance criteria, scheduled for a specific sprint. All -- would appreciate your input regarding work items for other GEs. BTW, the project Wiki will be ready soon, so we will be able to populate it with the details of the work items. Regards, Alex From: "Edmonds, AndrewX" To: "fiware-cloud at lists.fi-ware.eu" Date: 26/09/2011 09:02 PM Subject: [Fiware-cloud] Epics Sent by: fiware-cloud-bounces at lists.fi-ware.eu Here are the current descriptions of epics: http://dl.dropbox.com/u/165239/FIWare%20WP4%20Epics.html I would also ask all in cloud hosting to pay attention to the extracted security requirements [1], I presented in Turin when you are describing your epics. Andy [1] http://dl.dropbox.com/u/165239/fiware-security-turin-0911.pptx [attachment "smime.p7s" deleted by Alex Glikson/Haifa/IBM] ------------------------------------------------------------- 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. _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Sep 27 00:48:52 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 27 Sep 2011 00:48:52 +0200 Subject: [Fiware-cloud] Epics In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE1902984A@IRSMSX101.ger.corp.intel.com> Message-ID: Here you are my second version (not fully completed) ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Backlog entries description v0.2 TID.xls Type: application/octet-stream Size: 70656 bytes Desc: Backlog entries description v0.2 TID.xls URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From irenatr at gmail.com Tue Sep 27 17:42:51 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Tue, 27 Sep 2011 17:42:51 +0200 Subject: [Fiware-cloud] Epics In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE1902984A@IRSMSX101.ger.corp.intel.com> Message-ID: Hi this is the input from UPM. Irena On Tue, Sep 27, 2011 at 12:48 AM, FERNANDO LOPEZ AGUILAR wrote: > Here you are my second version (not fully completed) > > > ------------------------------ > 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 > > _______________________________________________ > Fiware-cloud mailing list > Fiware-cloud at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-cloud > > -- Irena -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Backlog entries description v0.1 UPM .xls Type: application/vnd.ms-excel Size: 10752 bytes Desc: not available URL: From GLIKSON at il.ibm.com Wed Sep 28 09:28:01 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 28 Sep 2011 10:28:01 +0300 Subject: [Fiware-cloud] Fw: Updated slides with very next steps and planning of activities during October in FI-WARE project Message-ID: Please, see attached the slides from the meeting I've mentioned during the call yesterday, with the details regarding next steps. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 28/09/2011 10:25 AM ----- From: Juanjo Hierro To: fiware-wpa at lists.fi-ware.eu, "fiware-wpl at lists.fi-ware.eu" Date: 28/09/2011 03:03 AM Subject: Re: [Fiware-wpa] Updated slides with very next steps and planning of activities during October in FI-WARE project Sent by: fiware-wpa-bounces at lists.fi-ware.eu > > I have updated the presentation we shared during our follow-up > confcall on Monday so that we can use it as a term of reference for the > work to be done (both very next steps and work during October) > > Please, share it with your teams. > > Cheers, > > Juanjo Hierro > Chief Technologist on Software Technologies > Telefonica R&D Labs -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE joint WPL-WPAs 11-09-28.pptx Type: application/octet-stream Size: 429053 bytes Desc: not available URL: