From GLIKSON at il.ibm.com Tue Oct 4 10:54:09 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 4 Oct 2011 10:54:09 +0200 Subject: [Fiware-cloud] web meeting link for the weekly meeting Message-ID: All, We will be using the following Web meeting for our meeting today. Talk to you soon. The main topic is backlog management (tracker, Wiki, etc) and updates to the product vision (in the wiki). Regards, Alex http://www.ibm.com/collaboration/meeting/join?id=1131085 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Tue Oct 4 12:05:41 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 4 Oct 2011 12:05:41 +0200 Subject: [Fiware-cloud] 4/10 meeting minutes Message-ID: Hi All, As I mentioned during the meeting, the Cloud Hosting chapter of the Product Vision (HLD) is now in the Wiki, and we've got the 'ok' to review it, and to start making changes (see below). I'm considering to split it to have a separate page per GE -- would appreciate your thoughts. What I did forget to mention is the work that we will need to do soon on describing the assets -- as indicated below, Juanjo will send us soon a template to organize it. Also, here is a brief summary of other topics discussed at the meeting (your comments are welcome). We have reviewed the instructions to handle the backlog items in the Wiki (FI-WARE project) and in the Tracker (FI-WARE Cloud project). It is important to notice that the content of the Wiki is public, so we shouldn't put there anything confidential. We may consider having a private wiki under the Cloud project. Next steps: All: fill in the details of the individual Epics -- both in Wiki and Tracker (by the end of the week) Andy: put a first update/draft of our Security considerations. Make sure we have a security related Epic in each relevant GE. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 04/10/2011 11:51 AM ----- From: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL Cc: "jhierro >> \"Juan J. Hierro\"" Date: 04/10/2011 11:21 AM Subject: Cloud Hosting chapter contents available on the Wiki Hi Alex, The Cloud Hosting chapter should be ok now on the Wiki. Please review that the contents are fine. Now you are free to organize how to update the contents. As already announced over the email, I will send a specific template for providing information about the assets taken as baseline for the implementation of GEs. Cheers, -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Oct 4 12:15:26 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 04 Oct 2011 12:15:26 +0200 Subject: [Fiware-cloud] 4/10 meeting minutes In-Reply-To: References: Message-ID: When you talk about the Wiki is public, it is also included there the description of the backlog entries? 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 04/10/2011, a las 12:05, Alex Glikson escribi???: Hi All, As I mentioned during the meeting, the Cloud Hosting chapter of the Product Vision (HLD) is now in the Wiki, and we've got the 'ok' to review it, and to start making changes (see below). I'm considering to split it to have a separate page per GE -- would appreciate your thoughts. What I did forget to mention is the work that we will need to do soon on describing the assets -- as indicated below, Juanjo will send us soon a template to organize it. Also, here is a brief summary of other topics discussed at the meeting (your comments are welcome). * We have reviewed the instructions to handle the backlog items in the Wiki (FI-WARE project) and in the Tracker (FI-WARE Cloud project). * It is important to notice that the content of the Wiki is public, so we shouldn't put there anything confidential. We may consider having a private wiki under the Cloud project. Next steps: * All: fill in the details of the individual Epics -- both in Wiki and Tracker (by the end of the week) * Andy: put a first update/draft of our Security considerations. Make sure we have a security related Epic in each relevant GE. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 04/10/2011 11:51 AM ----- From: Juanjo Hierro > To: Alex Glikson/Haifa/IBM at IBMIL Cc: "jhierro >> \"Juan J. Hierro\"" > Date: 04/10/2011 11:21 AM Subject: Cloud Hosting chapter contents available on the Wiki ________________________________ Hi Alex, The Cloud Hosting chapter should be ok now on the Wiki. Please review that the contents are fine. Now you are free to organize how to update the contents. As already announced over the email, I will send a specific template for providing information about the assets taken as baseline for the implementation of GEs. Cheers, -- 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 ________________________________ 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 GLIKSON at il.ibm.com Tue Oct 4 12:26:39 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 4 Oct 2011 12:26:39 +0200 Subject: [Fiware-cloud] 4/10 meeting minutes In-Reply-To: References: Message-ID: Yes. The whole world can see the details of our backlog entries in Wiki. You can make an experiment by logging out from Forge and see what can or can't you access. Alex From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "" Date: 04/10/2011 12:15 PM Subject: Re: [Fiware-cloud] 4/10 meeting minutes When you talk about the Wiki is public, it is also included there the description of the backlog entries? 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 04/10/2011, a las 12:05, Alex Glikson escribi???: Hi All, As I mentioned during the meeting, the Cloud Hosting chapter of the Product Vision (HLD) is now in the Wiki, and we've got the 'ok' to review it, and to start making changes (see below). I'm considering to split it to have a separate page per GE -- would appreciate your thoughts. What I did forget to mention is the work that we will need to do soon on describing the assets -- as indicated below, Juanjo will send us soon a template to organize it. Also, here is a brief summary of other topics discussed at the meeting (your comments are welcome). We have reviewed the instructions to handle the backlog items in the Wiki (FI-WARE project) and in the Tracker (FI-WARE Cloud project). It is important to notice that the content of the Wiki is public, so we shouldn't put there anything confidential. We may consider having a private wiki under the Cloud project. Next steps: All: fill in the details of the individual Epics -- both in Wiki and Tracker (by the end of the week) Andy: put a first update/draft of our Security considerations. Make sure we have a security related Epic in each relevant GE. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 04/10/2011 11:51 AM ----- From: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL Cc: "jhierro >> \"Juan J. Hierro\"" Date: 04/10/2011 11:21 AM Subject: Cloud Hosting chapter contents available on the Wiki Hi Alex, The Cloud Hosting chapter should be ok now on the Wiki. Please review that the contents are fine. Now you are free to organize how to update the contents. As already announced over the email, I will send a specific template for providing information about the assets taken as baseline for the implementation of GEs. Cheers, -- 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 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: From GLIKSON at il.ibm.com Tue Oct 4 16:11:45 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 4 Oct 2011 16:11:45 +0200 Subject: [Fiware-cloud] Conslidated highlights from the F2F in Turin Message-ID: Highlights and action items from the F2F at Turin 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 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). IaaS Service Management 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 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 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 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 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 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 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 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 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 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) Mashups are composite services. As all other services they should adhere to SLAs. To protect end-to-end SLAs of mashups, run-time information about performance of the services comprising a mashup should be provided to the Cloud hosting resource optimization GE. Note that this information is different from the static USDL data. Kalin [?], took it as an action point to verify whether this information can be extracted from the mashup execution engine in a reasonable fashion. We have service manifests (i.e., template) for stand alone services. Do we have a reciprocal for mashups? [Kalin, Fernando] The services comprising mashups should be deployed and running either in FiWare or outside of it, but they should exist and run as a prerequisite. If services are deployed on FiWare, then resource management GE can optimize their placement and resource allocation from a global perspective. There is a strong connection to networking. Mashups' performance critically depends on the network performance. Cloud Hosting should be network performance aware to manage infrastructure for mashups. There is a need from the WP to have WP4 services described as USDL Interlock with Data 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Wed Oct 5 21:20:43 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 5 Oct 2011 21:20:43 +0200 Subject: [Fiware-cloud] Fw: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Message-ID: All, The Wiki has been restructured a bit, and now the Epics are listed at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE (pointing to the same individual Epic pages as before). Also, we need to start providing details about the baseline assets that will be used for each GE (linked from the same page mentioned above). An template for describing each an asset can be found at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform . Please, proceed with updating both. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 05/10/2011 09:12 PM ----- From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 05/10/2011 12:01 PM Subject: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Sent by: fiware-wpl-bounces at lists.fi-ware.eu Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter ( http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3 ) In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" ( http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform ) Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: issues identified in the Question Mark section of the FI-WARE Product Vision. sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Thu Oct 6 16:24:49 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Thu, 6 Oct 2011 14:24:49 +0000 Subject: [Fiware-cloud] 4/10 meeting minutes In-Reply-To: References: Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1902B6EE@IRSMSX101.ger.corp.intel.com> I?ve closed out on the task assigned to me. If a GE had no epic related to security it is now added. I have added a page [1] on the extracted WP8 security requirements and is listed under ?Topics still being addressed at high-level? [2] Andy [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/CHSecurity [2] https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializi ng_Cloud_Hosting_in_FI-WARE#Themes_8 From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: Tuesday, October 04, 2011 11:06 AM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] 4/10 meeting minutes Hi All, As I mentioned during the meeting, the Cloud Hosting chapter of the Product Vision (HLD) is now in the Wiki, and we've got the 'ok' to review it, and to start making changes (see below). I'm considering to split it to have a separate page per GE -- would appreciate your thoughts. What I did forget to mention is the work that we will need to do soon on describing the assets -- as indicated below, Juanjo will send us soon a template to organize it. Also, here is a brief summary of other topics discussed at the meeting (your comments are welcome). * We have reviewed the instructions to handle the backlog items in the Wiki (FI-WARE project) and in the Tracker (FI-WARE Cloud project). * It is important to notice that the content of the Wiki is public, so we shouldn't put there anything confidential. We may consider having a private wiki under the Cloud project. Next steps: * All: fill in the details of the individual Epics -- both in Wiki and Tracker (by the end of the week) * Andy: put a first update/draft of our Security considerations. Make sure we have a security related Epic in each relevant GE. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 04/10/2011 11:51 AM ----- From: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL Cc: "jhierro >> \"Juan J. Hierro\"" Date: 04/10/2011 11:21 AM Subject: Cloud Hosting chapter contents available on the Wiki _____ Hi Alex, The Cloud Hosting chapter should be ok now on the Wiki. Please review that the contents are fine. Now you are free to organize how to update the contents. As already announced over the email, I will send a specific template for providing information about the assets taken as baseline for the implementation of GEs. Cheers, -- 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 -------------- 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 irenatr at gmail.com Fri Oct 7 10:30:54 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Fri, 7 Oct 2011 10:30:54 +0200 Subject: [Fiware-cloud] 4/10 meeting minutes In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1902B6EE@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE1902B6EE@IRSMSX101.ger.corp.intel.com> Message-ID: Hello, I've just made an input to the wiki related to User Portal epic and also assigned it to the tracker. Since there are already epics for UserCLI and AdminCLI, I think that the epic Admin Portal can be removed because is included in those two epics. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Cloud.SelfServiceInterfaces.UserPortal Irena On Thu, Oct 6, 2011 at 4:24 PM, Edmonds, AndrewX wrote: > I?ve closed out on the task assigned to me. If a GE had no epic related to > security it is now added. I have added a page [1] on the extracted WP8 > security requirements and is listed under ?Topics still being addressed at > high-level? [2]**** > > ** ** > > Andy**** > > ** ** > > [1] > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/CHSecurity > **** > > [2] > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Themes_8 > **** > > ** ** > > *From:* fiware-cloud-bounces at lists.fi-ware.eu [mailto: > fiware-cloud-bounces at lists.fi-ware.eu] *On Behalf Of *Alex Glikson > *Sent:* Tuesday, October 04, 2011 11:06 AM > *To:* fiware-cloud at lists.fi-ware.eu > *Subject:* [Fiware-cloud] 4/10 meeting minutes**** > > ** ** > > Hi All, > > As I mentioned during the meeting, the Cloud Hosting chapter of the Product > Vision (HLD) is now in the Wiki, and we've got the 'ok' to review it, and to > start making changes (see below). I'm considering to split it to have a > separate page per GE -- would appreciate your thoughts. > > What I did forget to mention is the work that we will need to do soon on > describing the assets -- as indicated below, Juanjo will send us soon a > template to organize it. > > Also, here is a brief summary of other topics discussed at the meeting > (your comments are welcome). **** > > - We have reviewed the instructions to handle the backlog items in the > Wiki (FI-WARE project) and in the Tracker (FI-WARE Cloud project). **** > - It is important to notice that the content of the Wiki is public, so > we shouldn't put there anything confidential. We may consider having a > private wiki under the Cloud project.**** > > > Next steps: **** > > - *All*: fill in the details of the individual Epics -- both in Wiki > and Tracker (by the end of the week) **** > - *Andy*: put a first update/draft of our Security considerations. Make > sure we have a security related Epic in each relevant GE.**** > > > Thanks, > Alex > > > ----- Forwarded by Alex Glikson/Haifa/IBM on 04/10/2011 11:51 AM ----- > > From: Juanjo Hierro > To: Alex Glikson/Haifa/IBM at IBMIL > Cc: "jhierro >> \"Juan J. Hierro\"" > Date: 04/10/2011 11:21 AM > Subject: Cloud Hosting chapter contents available on the Wiki **** > ------------------------------ > > > > > Hi Alex, > > The Cloud Hosting chapter should be ok now on the Wiki. Please > review that the contents are fine. > > Now you are free to organize how to update the contents. > > As already announced over the email, I will send a specific template > for providing information about the assets taken as baseline for the > implementation of GEs. > > Cheers, > > -- > 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**** > > ------------------------------------------------------------- > 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 > > -- Irena -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Oct 11 00:16:14 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 11 Oct 2011 00:16:14 +0200 Subject: [Fiware-cloud] [FI-WARE] Tracker & Backlog description Message-ID: <9CAA9DC6-9283-4441-8605-D5336353363F@tid.es> Dear all, I have revised our list of EPICs and Features and update them into the MediaWiki and FI-WARE Cloud Tracker. 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] ________________________________ 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 serge.defrance at technicolor.com Thu Oct 13 08:45:12 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 13 Oct 2011 08:45:12 +0200 Subject: [Fiware-cloud] Concerning EPICs and Assets Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01038939D8@MOPESMBX01.eu.thmulti.com> Dear Alex and All, We still not have an answer from Juanjo to our proposal to move our participation from WP4 to WP7 in order to clarify the interaction between the Cloud Edge and the Cloud. However, we have now to fill up the Wiki with our EPICs proposal. I propose the following contribution (see attached) which is an update of what I already circulated for the Torino meeting. In the future, depending on how we decide to share the work regarding Cloud Edge between WP4 and WP7, these description may migrate to the chapter devoted to WP7. I will be out of office tomorrow. If no other news since, I propose to update the wiki on Monday with this proposal. I shall join the call on Tuesday (Alex, any phone number ?). Regards, Serge. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TechnicolorAssetsWP4revised_v1.docx.zip Type: application/x-zip-compressed Size: 45413 bytes Desc: TechnicolorAssetsWP4revised_v1.docx.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CloudProxyWP4EPICrevised_v01.xls.zip Type: application/x-zip-compressed Size: 31201 bytes Desc: CloudProxyWP4EPICrevised_v01.xls.zip URL: From thomas.michael.bohnert at sap.com Thu Oct 13 08:53:29 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Thu, 13 Oct 2011 08:53:29 +0200 Subject: [Fiware-cloud] Concerning EPICs and Assets In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E01038939D8@MOPESMBX01.eu.thmulti.com> Message-ID: <771C9B001456D64783596DDC3801C6EA281533FE9F@DEWDFECCR09.wdf.sap.corp> Dear all, Just to clarify. We are aware of this proposal and studying it. Yesterday was a public holiday and we therefore need a bit extra time. Hope this dooes not prevent you from proceeding too much. Thanks for your understanding! Best, Thomas -- Please excuse smartphone brevity From: Defrance Serge [mailto:serge.defrance at technicolor.com] Sent: Thursday, October 13, 2011 08:45 AM To: Alex Glikson ; fiware-cloud at lists.fi-ware.eu Cc: Garino Pierangelo Subject: [Fiware-cloud] Concerning EPICs and Assets Dear Alex and All, We still not have an answer from Juanjo to our proposal to move our participation from WP4 to WP7 in order to clarify the interaction between the Cloud Edge and the Cloud. However, we have now to fill up the Wiki with our EPICs proposal. I propose the following contribution (see attached) which is an update of what I already circulated for the Torino meeting. In the future, depending on how we decide to share the work regarding Cloud Edge between WP4 and WP7, these description may migrate to the chapter devoted to WP7. I will be out of office tomorrow. If no other news since, I propose to update the wiki on Monday with this proposal. I shall join the call on Tuesday (Alex, any phone number ?). Regards, Serge. -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Sun Oct 16 23:11:26 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 16 Oct 2011 23:11:26 +0200 Subject: [Fiware-cloud] next steps Message-ID: All, I apologize for not being able to attend last week's conference call, as well as this week's one -- I have been on vacation, and still is (until the end of the week). I strongly encourage you to continue elaborating the Themes, Epics and Assets related to Cloud Hosting GEs in FIWARE wiki, at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE , as well as in the corresponding Tracker. I will continue with the Resource Management GE when I'm back (BTW, I am considering to turn some of the initial Epics under RM into 'themes', and provide additional level of details with Epics -- Similarly to what Andy did for Security). Also, remember that we need to come up with a list of 'features' for the first minor release (3 months, Nov-Jan). The features must be formulated in such a way that they can be *completed* during this period (also, remember the other INVEST/SMART criteria). Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Mon Oct 17 11:07:27 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 17 Oct 2011 11:07:27 +0200 Subject: [Fiware-cloud] next steps In-Reply-To: References: Message-ID: Hi all, Do not forget the meaning of feature and the different between it and User Story. In fact, regarding the comments from Alex, we have to provide a list of "Features" but also "User Stories". Afterwards, we have to select which of them we want to implement in the first minor release. This means that not all Features or User Stories have to be scheduled in the first minor release. Regarding the different between Feature and User Stories, you can see a Feature like a functionality that you can know that will be implemented in 60 days or 3 months of work and then corresponding to a period of time of a minor release. A User Story is just the third part of a Feature (that is 20 days or 1 month of work). At least, this is the concept that I have in mind when I talk about them. 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 16/10/2011, a las 23:11, Alex Glikson escribi?: All, I apologize for not being able to attend last week's conference call, as well as this week's one -- I have been on vacation, and still is (until the end of the week). I strongly encourage you to continue elaborating the Themes, Epics and Assets related to Cloud Hosting GEs in FIWARE wiki, at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE, as well as in the corresponding Tracker. I will continue with the Resource Management GE when I'm back (BTW, I am considering to turn some of the initial Epics under RM into 'themes', and provide additional level of details with Epics -- Similarly to what Andy did for Security). Also, remember that we need to come up with a list of 'features' for the first minor release (3 months, Nov-Jan). The features must be formulated in such a way that they can be *completed* during this period (also, remember the other INVEST/SMART criteria). Regards, Alex ________________________________ 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 mcp at tid.es Wed Oct 19 15:30:44 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 19 Oct 2011 15:30:44 +0200 Subject: [Fiware-cloud] Fwd: Assets in Materializing Cloud Hosting in FI-WARE Message-ID: <4E9ED104.7040500@tid.es> Dear all, I've found out that Alex is on holidays so I have to take the initiative. Please take note of this and update your assets accordingly. Thanks Miguel -------- Mensaje original -------- Asunto: Assets in Materializing Cloud Hosting in FI-WARE Fecha: Tue, 18 Oct 2011 19:03:59 +0200 De: Miguel Carrillo A: GLIKSON at il.ibm.com CC: JUAN JOSE HIERRO SUREDA Dear Alex, I am sending private emails to all WPLs and also WPAs with my comments to the assets on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We must get to a situation where all the WPs provide their inputs in a consistent manner and format. I know this is a bit iterative and frustrating but it has to be done. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (please check out and follow strictly http://tinyurl.com/6gueb5t). General comments (for all WPs) * There are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * In the general page of each WP, some provide a very short description together with the asset name and other don't. The page with the list of your assets has to have a short description for each one (e.g.: http://tinyurl.com/5snfngy) * IPRs are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... Particular comments (specific to your WP) Text at the bottom saying the "Security & Monitoring" remain to be addressed at high level * IaaS Data Center Resource Management * 4, no description nor linked page with description. * OpenStack Nova * OpenStack Glance * OpenStack Quantum (Open vSwitch) * KVM * IaaS Service Management * Claudia - with a couple of "TBD" in the description (IPR & Publicly available documentation) * PaaS Management * PaaS Management Platform - with a couple of "TBD" in the description (IPR & Publicly available documentation) * Object Storage * OpenStack Swift, with no link to an in detail description * Self-Service Interfaces * Empty! ( it will be developed from scratch so maybe this is ok) * Cloud Proxy * Empty! (under debate with Technicolor, it may go under I2ND. So maybe this is ok) * Monitoring * Empty! (already identified as a gap) * Security * OpenStack Keystone, with no link to an in detail description Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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: From mcp at tid.es Mon Oct 24 15:37:58 2011 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 24 Oct 2011 15:37:58 +0200 Subject: [Fiware-cloud] Status of Cloud WP Message-ID: <4EA56A36.7040901@tid.es> Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 From GLIKSON at il.ibm.com Mon Oct 24 22:13:24 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 24 Oct 2011 22:13:24 +0200 Subject: [Fiware-cloud] Fw: Status of Cloud WP Message-ID: Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA , Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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: From andrewx.edmonds at intel.com Tue Oct 25 02:25:09 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 25 Oct 2011 00:25:09 +0000 Subject: [Fiware-cloud] Fw: Status of Cloud WP In-Reply-To: References: Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE19039E1A@IRSMSX101.ger.corp.intel.com> I think it is a good idea regarding the review. If we intend to have such a review we should have it early in the morning so that any outstanding issues can be resolved by the end of business on Monday (31st). Do others? If anyone needs to talk with me tomorrow at our scheduled confcall time, I'll be available via skype (andy.edmonds) Andy 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, October 24, 2011 9:13 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: Status of Cloud WP Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo > To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA >, Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP ________________________________ Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Oct 25 09:28:30 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 25 Oct 2011 09:28:30 +0200 Subject: [Fiware-cloud] Fw: Status of Cloud WP Message-ID: The same for me. Anyway, you could take a view in my sections in order to have an idea about what is that juanjo wants for us. Regards. Fernando. Enviado desde mi HTC ----- Reply message ----- De: "Edmonds, AndrewX" Fecha: mar., oct. 25, 2011 02:25 Asunto: [Fiware-cloud] Fw: Status of Cloud WP Para: "Alex Glikson" , "fiware-cloud at lists.fi-ware.eu" I think it is a good idea regarding the review. If we intend to have such a review we should have it early in the morning so that any outstanding issues can be resolved by the end of business on Monday (31st). Do others? If anyone needs to talk with me tomorrow at our scheduled confcall time, I?ll be available via skype (andy.edmonds) Andy 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, October 24, 2011 9:13 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: Status of Cloud WP Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo > To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA >, Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP ________________________________ Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------- 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. ________________________________ 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: From andrewx.edmonds at intel.com Tue Oct 25 10:31:23 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 25 Oct 2011 08:31:23 +0000 Subject: [Fiware-cloud] Fw: Status of Cloud WP In-Reply-To: References: Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1903A108@IRSMSX101.ger.corp.intel.com> Here's a doodle so we can come to a time on Monday that suits all http://www.doodle.com/25s8akr5qspifryg Andy From: FERNANDO LOPEZ AGUILAR [mailto:fla at tid.es] Sent: Tuesday, October 25, 2011 8:29 AM To: Edmonds, AndrewX; glikson at il.ibm.com; fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Fw: Status of Cloud WP The same for me. Anyway, you could take a view in my sections in order to have an idea about what is that juanjo wants for us. Regards. Fernando. Enviado desde mi HTC ----- Reply message ----- De: "Edmonds, AndrewX" > Fecha: mar., oct. 25, 2011 02:25 Asunto: [Fiware-cloud] Fw: Status of Cloud WP Para: "Alex Glikson" >, "fiware-cloud at lists.fi-ware.eu" > I think it is a good idea regarding the review. If we intend to have such a review we should have it early in the morning so that any outstanding issues can be resolved by the end of business on Monday (31st). Do others? If anyone needs to talk with me tomorrow at our scheduled confcall time, I'll be available via skype (andy.edmonds) Andy 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, October 24, 2011 9:13 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: Status of Cloud WP Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo > To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA >, Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP ________________________________ Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------- 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. ________________________________ 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 ------------------------------------------------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVIDBR at il.ibm.com Tue Oct 25 17:02:58 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Tue, 25 Oct 2011 17:02:58 +0200 Subject: [Fiware-cloud] Fw: Status of Cloud WP In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE19039E1A@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE19039E1A@IRSMSX101.ger.corp.intel.com> Message-ID: Hi Andy, I can chip in by making a pass tomorrow. -- david ======================================= David Breitgand, Ph. D. Research Staff Member System/Service Performance Management IBM Research Laboratory in Haifa Tel: 972-3-7689-465 Fax: 972-3-768-9545 From: "Edmonds, AndrewX" To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" Date: 25/10/2011 02:25 AM Subject: Re: [Fiware-cloud] Fw: Status of Cloud WP Sent by: fiware-cloud-bounces at lists.fi-ware.eu I think it is a good idea regarding the review. If we intend to have such a review we should have it early in the morning so that any outstanding issues can be resolved by the end of business on Monday (31st). Do others? If anyone needs to talk with me tomorrow at our scheduled confcall time, I?ll be available via skype (andy.edmonds) Andy 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, October 24, 2011 9:13 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: Status of Cloud WP Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA , Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------- 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 andrewx.edmonds at intel.com Tue Oct 25 17:08:55 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 25 Oct 2011 15:08:55 +0000 Subject: [Fiware-cloud] Fw: Status of Cloud WP In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE19039E1A@IRSMSX101.ger.corp.intel.com> Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1903A42C@IRSMSX101.ger.corp.intel.com> Great, thanks David! We in Intel will also do an internal review on Friday. From: David Breitgand [mailto:DAVIDBR at il.ibm.com] Sent: Tuesday, October 25, 2011 4:03 PM To: Edmonds, AndrewX Cc: Alex Glikson; fiware-cloud at lists.fi-ware.eu; fiware-cloud-bounces at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Fw: Status of Cloud WP Hi Andy, I can chip in by making a pass tomorrow. -- david ======================================= David Breitgand, Ph. D. Research Staff Member System/Service Performance Management IBM Research Laboratory in Haifa Tel: 972-3-7689-465 Fax: 972-3-768-9545 From: "Edmonds, AndrewX" > To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" > Date: 25/10/2011 02:25 AM Subject: Re: [Fiware-cloud] Fw: Status of Cloud WP Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ I think it is a good idea regarding the review. If we intend to have such a review we should have it early in the morning so that any outstanding issues can be resolved by the end of business on Monday (31st). Do others? If anyone needs to talk with me tomorrow at our scheduled confcall time, I'll be available via skype (andy.edmonds) Andy 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, October 24, 2011 9:13 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: Status of Cloud WP Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo > To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA >, Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP ________________________________ Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------- 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 ------------------------------------------------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Oct 25 17:18:12 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 25 Oct 2011 17:18:12 +0200 Subject: [Fiware-cloud] Fw: Status of Cloud WP In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1903A42C@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE19039E1A@IRSMSX101.ger.corp.intel.com> <332A51FC2924EE4A8CDD5BB4BB05CE1903A42C@IRSMSX101.ger.corp.intel.com> Message-ID: We are doing a review on all the thinks and give you comments about the things that we have to change. 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 25/10/2011, a las 17:08, Edmonds, AndrewX escribi?: Great, thanks David! We in Intel will also do an internal review on Friday. From: David Breitgand [mailto:DAVIDBR at il.ibm.com] Sent: Tuesday, October 25, 2011 4:03 PM To: Edmonds, AndrewX Cc: Alex Glikson; fiware-cloud at lists.fi-ware.eu; fiware-cloud-bounces at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Fw: Status of Cloud WP Hi Andy, I can chip in by making a pass tomorrow. -- david ======================================= David Breitgand, Ph. D. Research Staff Member System/Service Performance Management IBM Research Laboratory in Haifa Tel: 972-3-7689-465 Fax: 972-3-768-9545 From: "Edmonds, AndrewX" > To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" > Date: 25/10/2011 02:25 AM Subject: Re: [Fiware-cloud] Fw: Status of Cloud WP Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ I think it is a good idea regarding the review. If we intend to have such a review we should have it early in the morning so that any outstanding issues can be resolved by the end of business on Monday (31st). Do others? If anyone needs to talk with me tomorrow at our scheduled confcall time, I?ll be available via skype (andy.edmonds) Andy 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, October 24, 2011 9:13 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: Status of Cloud WP Team, Please, give high priority to completing this work this week. We can have a final (?) review in the beginning of next week. I will try to send some comments before that. Unfortunately, we had holidays in the last couple of weeks, and I'm on a business trip this week -- so I was not be able to do it earlier. I will also not be able to participate the weekly call this week. Sorry about that. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 24/10/2011 10:06 PM ----- From: Miguel Carrillo > To: fiware-cloud at lists.fi-ware.eu Cc: JUAN JOSE HIERRO SUREDA >, Alex Glikson/Haifa/IBM at IBMIL Date: 24/10/2011 03:37 PM Subject: Status of Cloud WP ________________________________ Dear all, I am afraid that the activity in Cloud has been very low these days. Entire sections are not fully completed and there's still some work to do. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE Please take action as we are going to miss the deadline of the end of October (I kindly remind you that this would be a delay on top of a delay - the initial deadline was the end of September) Thanks in advance for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------- 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 ------------------------------------------------------------- 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. ________________________________ 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 GLIKSON at il.ibm.com Wed Oct 26 08:14:13 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 26 Oct 2011 08:14:13 +0200 Subject: [Fiware-cloud] WP status In-Reply-To: <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> References: <332A51FC2924EE4A8CDD5BB4BB05CE1903A4AA@IRSMSX101.ger.corp.intel.com> <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> Message-ID: Andy, Fernando -- thanks for the initiative! This is very helpful. I will send more detailed comments later. One important comment, meanwhile: Regarding user stories and sprints -- I'm not sure we should manage user stories in the same public tracker. That's why the "User Story" category and the "Sprint" field are not there. Moreover, strictly speaking, those are not supposed to be part of the Backlog -- which is by definition a set of work items which have not been scheduled to any sprint. So, besides completing and reviewing Themes and Epics in the backlog, and completing the description of baseline assets we want to use, what I would like to ask from all of you is to send me (or to the list) a much more detailed description, in whatever format is convenient for you (sets of bullets are fine for now -- we can then attach them to the wiki entry) of the following: 1) Features that you would like to include in the first minor release -- outlining specific scope of work that you expect to be completed by January, 31th, 2012, and 2) User Stories that you would like to include in the first sprint -- i.e., specific work items that will be done by November 30th. For both, I would like to see a very clear 'acceptance criteria' -- how exactly will we measure and validate whether the corresponding work items are done, and what can others expect as an outcome of this work. Thanks, Alex From: FERNANDO LOPEZ AGUILAR To: "Edmonds, AndrewX" Cc: Alex Glikson/Haifa/IBM at IBMIL Date: 25/10/2011 07:20 PM Subject: Re: WP status Thank you Andy, I write them inline. Tracker * Only 2 from Alex and the rest are from Fernando (currently only EPICs and Features) * FI-WARE Backlog Entry Type without User-Story option. * We have release box but we have to change it to FI-WARE Release Id box and FI-WARE Sprint Id box. * We need to specify there for each EPIC, Feature and User Story in which Release and Sprint we plan to develop it. * We have to select which Feature and User Stories we want to implement in the first minor release. Wiki Asset Descriptions ? None from Cloud Proxy ? None from Self-service Interfaces ? Listed but not detailed from Monitoring ? None that covers T4.2 * We have to differentiate between basseline asserts and needed assests. The real asset is explained in more detail (e.g. Claudia in IaaS SM) and the others are explained with less details (see MySQL). But the sections that we use would be the same that all the assets have to use. Wiki Epics * Here I want to give you some clarification about the different between EPICs, Features and User Stories. * EPICs is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time bigger than a minor release (3 months). * Feature is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time less than a minor release (3 months). * User Story is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time equal to a sprint (1 months). * We have provided neither Features or User Stories except for IaaS SM and PaaS Mgmt. * Anyway, I could see some Epics like FIWARE.Epic.Cloud.ResourceManager.Security.APIs which is not a EPIC (IMHO), The Epic would be FIWARE.Epic.Cloud.ResourceManager.Security. This should be a User Story. IaaS Data Center Resource Management: 9/20 not complete ? FIWARE.Epic.Cloud.ResourceManager.MgmtFabric ? FIWARE.Epic.Cloud.ResourceManager.QoS ? FIWARE.Epic.Cloud.ResourceManager.Mobility ? FIWARE.Epic.Cloud.ResourceManager.Placement ? FIWARE.Epic.Cloud.ResourceManager.PhysPlatformMgmt ? FIWARE.Epic.Cloud.ResourceManager.Capacity ? FIWARE.Epic.Cloud.ResourceManager.Toolkit ? FIWARE.Epic.Cloud.ResourceManager.Federation ? FIWARE.Epic.Cloud.ResourceManager.Security.APIs * IMHO, OCCI is not a basseline asset, it is a specific interface within the rest of baseline assets (Openstack Nova, Glance, ...). * Each Basseline assets have to describe the following subsections Brief Description Programming artifacts Technologies used Runtime pre-requisites (including Known software requirements) IPR Publicly available documentation except the needed assests like MySQL in IaaS SM that only need to describe Brief Description IPR Publicly available documentation * There are no Features and User Stories Object Storage * Openstack switch, need to describe Technologies used and Runtime pre-requisites subsections. * No Features * No User Stories (remenber that *.Security.SSO and *.Security.RBAC should be a User Stories). Security 1/2 not complete ? FIWARE.Epic.Cloud.Security.RBAC * Openstack keynote, need to describe Technologies used and Runtime pre-requisites subsections. * Check if the Epics are Features. Self-Service Interfaces: 4/5 not complete * No Baseline assets described ? FIWARE.Epic.Cloud.SelfServiceInterfaces.UserCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminPortal ? FIWARE.Epic.Cloud.SelfServiceInterfaces.Security * No Features, no User Stories Cloud Proxy: 5/8 not complete * No baseline asset described ? FIWARE.Epic.Cloud.CloudProxy.VirtualizationLayer ? FIWARE.Epic.Cloud.CloudProxy.ManagementAPI ? FIWARE.Epic.Cloud.CloudProxy.CloudAppProvisioning ? FIWARE.Epic.Cloud.CloudProxy.ManagementProxy ? FIWARE.Epic.Cloud.CloudProxy.Security * Only Epics Monitoring: 5/11 not complete * Some baseline assets without description (working in progress between Fernando and Andy) ? FIWARE.Epic.Cloud.Monitoring.Analysis.SLAIntegration ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics ? FIWARE.Epic.Cloud.Monitoring.ServiceMgrIntegration * Only Epics. Themes: 1/3 not complete ? Accounting @Andy TODO: ? Supply monitoring asset details ? FIWARE.Epic.Cloud.Security.RBAC ? FIWARE.Epic.Cloud.Security.APIs ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics @Alex TODO: * Refine the tracker page. @All * Refine the Epics, Features and User Stories * Provide baseline assets with their appropriate description information * Provide information in the tracker system (be careful, in the FIWARE Cloud track section, not in the FIWARE track section) * Provide the list of Features and User Stories to be implemented in the first minor release and put this information into the tracker system. I think that this information could be send to the rest of cloud members. I hope that I could take some light into the dark. 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 El 25/10/2011, a las 18:02, Edmonds, AndrewX escribi?: ------------------------------------------------------------- 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. 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: From GLIKSON at il.ibm.com Thu Oct 27 00:21:36 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 27 Oct 2011 00:21:36 +0200 Subject: [Fiware-cloud] WP status In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE1903A4AA@IRSMSX101.ger.corp.intel.com> <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> Message-ID: My comments below One more important thing: it is very important to outline in the description of each Epic the scope of work to be done -- which also implies that we need to mention the baseline assets that will be used. It is important that whoever reads an Epic, understands what we are trying to, why, what already exists as part of the baseline assets, and what is the 'delta', or work to be done, associated with this particular work item -- integration, enhancements, new pieces, etc. Regards, Alex P.S. I've completed the description of most of the RM epics From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 26/10/2011 08:14 AM Subject: Re: [Fiware-cloud] WP status Sent by: fiware-cloud-bounces at lists.fi-ware.eu Andy, Fernando -- thanks for the initiative! This is very helpful. I will send more detailed comments later. One important comment, meanwhile: Regarding user stories and sprints -- I'm not sure we should manage user stories in the same public tracker. That's why the "User Story" category and the "Sprint" field are not there. Moreover, strictly speaking, those are not supposed to be part of the Backlog -- which is by definition a set of work items which have not been scheduled to any sprint. So, besides completing and reviewing Themes and Epics in the backlog, and completing the description of baseline assets we want to use, what I would like to ask from all of you is to send me (or to the list) a much more detailed description, in whatever format is convenient for you (sets of bullets are fine for now -- we can then attach them to the wiki entry) of the following: 1) Features that you would like to include in the first minor release -- outlining specific scope of work that you expect to be completed by January, 31th, 2012, and 2) User Stories that you would like to include in the first sprint -- i.e., specific work items that will be done by November 30th. For both, I would like to see a very clear 'acceptance criteria' -- how exactly will we measure and validate whether the corresponding work items are done, and what can others expect as an outcome of this work. Thanks, Alex From: FERNANDO LOPEZ AGUILAR To: "Edmonds, AndrewX" Cc: Alex Glikson/Haifa/IBM at IBMIL Date: 25/10/2011 07:20 PM Subject: Re: WP status Thank you Andy, I write them inline. Tracker * Only 2 from Alex and the rest are from Fernando (currently only EPICs and Features -- this is OK, as explained above) * FI-WARE Backlog Entry Type without User-Story option. * We have release box but we have to change it to FI-WARE Release Id box and FI-WARE Sprint Id box. * We need to specify there for each EPIC, Feature and User Story in which Release and Sprint we plan to develop it. Not really. Only for the first one. The priorities might change over time, so we shouldn't try deciding up front for longer than one minor release. * We have to select which Feature and User Stories we want to implement in the first minor release. Wiki Asset Descriptions ? None from Cloud Proxy ? None from Self-service Interfaces ? Listed but not detailed from Monitoring ? None that covers T4.2 -- Updated * We have to differentiate between basseline asserts and needed assests. The real asset is explained in more detail (e.g. Claudia in IaaS SM) and the others are explained with less details (see MySQL). But the sections that we use would be the same that all the assets have to use. We should describe here *only* the baseline assets. If they have pre-requisites -- it is described in their documentation. and we may mention that within the description of the asset. But we should not mention them in the main list. Wiki Epics * Here I want to give you some clarification about the different between EPICs, Features and User Stories. * EPICs is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time bigger than a minor release (3 months). * Feature is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time less than a minor release (3 months). * User Story is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time equal to a sprint (1 months). [or less] * We have provided neither Features or User Stories except for IaaS SM and PaaS Mgmt. Yep. As I mentioned above, we must update both the Wiki and the Tracker with features for the first release, and also outline the stories for the first sprint. * Anyway, I could see some Epics like FIWARE.Epic.Cloud.ResourceManager.Security.APIs which is not a EPIC (IMHO), The Epic would be FIWARE.Epic.Cloud.ResourceManager.Security. This should be a User Story. Well, it is a matter of scope and sizing. If we figure out that the entire Epic can be covered in a single sprint (which I don't believe is the case) -- we can definitely 'downgrade' it to a story. IaaS Data Center Resource Management: 9/20 not complete ? FIWARE.Epic.Cloud.ResourceManager.MgmtFabric -- done ? FIWARE.Epic.Cloud.ResourceManager.QoS -- done ? FIWARE.Epic.Cloud.ResourceManager.Mobility -- done ? FIWARE.Epic.Cloud.ResourceManager.Placement -- done ? FIWARE.Epic.Cloud.ResourceManager.PhysPlatformMgmt ? FIWARE.Epic.Cloud.ResourceManager.Capacity -- done ? FIWARE.Epic.Cloud.ResourceManager.Toolkit ? FIWARE.Epic.Cloud.ResourceManager.Federation ? FIWARE.Epic.Cloud.ResourceManager.Security.APIs * IMHO, OCCI is not a basseline asset, it is a specific interface within the rest of baseline assets (Openstack Nova, Glance, ...). * Each Basseline assets have to describe the following subsections Brief Description Programming artifacts Technologies used Runtime pre-requisites (including Known software requirements) IPR Publicly available documentation except the needed assests like MySQL in IaaS SM that only need to describe Brief Description IPR Publicly available documentation * There are no Features and User Stories Object Storage * Openstack switch, need to describe Technologies used and Runtime pre-requisites subsections. * No Features * No User Stories (remenber that *.Security.SSO and *.Security.RBAC should be a User Stories). Security 1/2 not complete ? FIWARE.Epic.Cloud.Security.RBAC * Openstack keynote, need to describe Technologies used and Runtime pre-requisites subsections. * Check if the Epics are Features. Self-Service Interfaces: 4/5 not complete * No Baseline assets described ? FIWARE.Epic.Cloud.SelfServiceInterfaces.UserCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminPortal ? FIWARE.Epic.Cloud.SelfServiceInterfaces.Security * No Features, no User Stories Cloud Proxy: 5/8 not complete * No baseline asset described ? FIWARE.Epic.Cloud.CloudProxy.VirtualizationLayer ? FIWARE.Epic.Cloud.CloudProxy.ManagementAPI ? FIWARE.Epic.Cloud.CloudProxy.CloudAppProvisioning ? FIWARE.Epic.Cloud.CloudProxy.ManagementProxy ? FIWARE.Epic.Cloud.CloudProxy.Security * Only Epics Monitoring: 5/11 not complete * Some baseline assets without description (working in progress between Fernando and Andy) ? FIWARE.Epic.Cloud.Monitoring.Analysis.SLAIntegration ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics ? FIWARE.Epic.Cloud.Monitoring.ServiceMgrIntegration * Only Epics. Themes: 1/3 not complete ? Accounting @Andy TODO: ? Supply monitoring asset details ? FIWARE.Epic.Cloud.Security.RBAC ? FIWARE.Epic.Cloud.Security.APIs ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics @Alex TODO: * Refine the tracker page. @All * Refine the Epics, Features and User Stories * Provide baseline assets with their appropriate description information * Provide information in the tracker system (be careful, in the FIWARE Cloud track section, not in the FIWARE track section) * Provide the list of Features and User Stories to be implemented in the first minor release and put this information into the tracker system. I think that this information could be send to the rest of cloud members. I hope that I could take some light into the dark. 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 El 25/10/2011, a las 18:02, Edmonds, AndrewX escribi?: ------------------------------------------------------------- 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.defrance at technicolor.com Thu Oct 27 11:13:49 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 27 Oct 2011 11:13:49 +0200 Subject: [Fiware-cloud] WP status In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE1903A4AA@IRSMSX101.ger.corp.intel.com> <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E010FD796D2@MOPESMBX01.eu.thmulti.com> Dear All, I updated the cloud edge chapter (both epics and asset) in our Cloud hosting chapter on the mediawiki. There are other Epics mentioned in addition to the three I have added, they certainly have to be deleted (unless another partner contributes on these Epics). Another point is that the exact split of Epics between WP4 and WP7 for what regards the Cloud Edge may still slightly evolve, depending on the clarification discussion we currently have with our chief architect (and which is about to be concluded). We may discuss these points during the Monday conf call. 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: jeudi 27 octobre 2011 00:22 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] WP status My comments below One more important thing: it is very important to outline in the description of each Epic the scope of work to be done -- which also implies that we need to mention the baseline assets that will be used. It is important that whoever reads an Epic, understands what we are trying to, why, what already exists as part of the baseline assets, and what is the 'delta', or work to be done, associated with this particular work item -- integration, enhancements, new pieces, etc. Regards, Alex P.S. I've completed the description of most of the RM epics From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 26/10/2011 08:14 AM Subject: Re: [Fiware-cloud] WP status Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Andy, Fernando -- thanks for the initiative! This is very helpful. I will send more detailed comments later. One important comment, meanwhile: Regarding user stories and sprints -- I'm not sure we should manage user stories in the same public tracker. That's why the "User Story" category and the "Sprint" field are not there. Moreover, strictly speaking, those are not supposed to be part of the Backlog -- which is by definition a set of work items which have not been scheduled to any sprint. So, besides completing and reviewing Themes and Epics in the backlog, and completing the description of baseline assets we want to use, what I would like to ask from all of you is to send me (or to the list) a much more detailed description, in whatever format is convenient for you (sets of bullets are fine for now -- we can then attach them to the wiki entry) of the following: 1) Features that you would like to include in the first minor release -- outlining specific scope of work that you expect to be completed by January, 31th, 2012, and 2) User Stories that you would like to include in the first sprint -- i.e., specific work items that will be done by November 30th. For both, I would like to see a very clear 'acceptance criteria' -- how exactly will we measure and validate whether the corresponding work items are done, and what can others expect as an outcome of this work. Thanks, Alex From: FERNANDO LOPEZ AGUILAR To: "Edmonds, AndrewX" Cc: Alex Glikson/Haifa/IBM at IBMIL Date: 25/10/2011 07:20 PM Subject: Re: WP status ________________________________ Thank you Andy, I write them inline. Tracker * Only 2 from Alex and the rest are from Fernando (currently only EPICs and Features -- this is OK, as explained above) * FI-WARE Backlog Entry Type without User-Story option. * We have release box but we have to change it to FI-WARE Release Id box and FI-WARE Sprint Id box. * We need to specify there for each EPIC, Feature and User Story in which Release and Sprint we plan to develop it. Not really. Only for the first one. The priorities might change over time, so we shouldn't try deciding up front for longer than one minor release. * We have to select which Feature and User Stories we want to implement in the first minor release. Wiki Asset Descriptions * None from Cloud Proxy * None from Self-service Interfaces * Listed but not detailed from Monitoring * None that covers T4.2 -- Updated * We have to differentiate between basseline asserts and needed assests. The real asset is explained in more detail (e.g. Claudia in IaaS SM) and the others are explained with less details (see MySQL). But the sections that we use would be the same that all the assets have to use. We should describe here *only* the baseline assets. If they have pre-requisites -- it is described in their documentation. and we may mention that within the description of the asset. But we should not mention them in the main list. Wiki Epics * Here I want to give you some clarification about the different between EPICs, Features and User Stories. * EPICs is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time bigger than a minor release (3 months). * Feature is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time less than a minor release (3 months). * User Story is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time equal to a sprint (1 months). [or less] * We have provided neither Features or User Stories except for IaaS SM and PaaS Mgmt. Yep. As I mentioned above, we must update both the Wiki and the Tracker with features for the first release, and also outline the stories for the first sprint. * Anyway, I could see some Epics like FIWARE.Epic.Cloud.ResourceManager.Security.APIs which is not a EPIC (IMHO), The Epic would be FIWARE.Epic.Cloud.ResourceManager.Security. This should be a User Story. Well, it is a matter of scope and sizing. If we figure out that the entire Epic can be covered in a single sprint (which I don't believe is the case) -- we can definitely 'downgrade' it to a story. IaaS Data Center Resource Management: 9/20 not complete * FIWARE.Epic.Cloud.ResourceManager.MgmtFabric -- done * FIWARE.Epic.Cloud.ResourceManager.QoS -- done * FIWARE.Epic.Cloud.ResourceManager.Mobility -- done * FIWARE.Epic.Cloud.ResourceManager.Placement -- done * FIWARE.Epic.Cloud.ResourceManager.PhysPlatformMgmt * FIWARE.Epic.Cloud.ResourceManager.Capacity -- done * FIWARE.Epic.Cloud.ResourceManager.Toolkit * FIWARE.Epic.Cloud.ResourceManager.Federation * FIWARE.Epic.Cloud.ResourceManager.Security.APIs * IMHO, OCCI is not a basseline asset, it is a specific interface within the rest of baseline assets (Openstack Nova, Glance, ...). * Each Basseline assets have to describe the following subsections Brief Description Programming artifacts Technologies used Runtime pre-requisites (including Known software requirements) IPR Publicly available documentation except the needed assests like MySQL in IaaS SM that only need to describe Brief Description IPR Publicly available documentation * There are no Features and User Stories Object Storage * Openstack switch, need to describe Technologies used and Runtime pre-requisites subsections. * No Features * No User Stories (remenber that *.Security.SSO and *.Security.RBAC should be a User Stories). Security 1/2 not complete * FIWARE.Epic.Cloud.Security.RBAC * Openstack keynote, need to describe Technologies used and Runtime pre-requisites subsections. * Check if the Epics are Features. Self-Service Interfaces: 4/5 not complete * No Baseline assets described * FIWARE.Epic.Cloud.SelfServiceInterfaces.UserCLI * FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminCLI * FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminPortal * FIWARE.Epic.Cloud.SelfServiceInterfaces.Security * No Features, no User Stories Cloud Proxy: 5/8 not complete * No baseline asset described * FIWARE.Epic.Cloud.CloudProxy.VirtualizationLayer * FIWARE.Epic.Cloud.CloudProxy.ManagementAPI * FIWARE.Epic.Cloud.CloudProxy.CloudAppProvisioning * FIWARE.Epic.Cloud.CloudProxy.ManagementProxy * FIWARE.Epic.Cloud.CloudProxy.Security * Only Epics Monitoring: 5/11 not complete * Some baseline assets without description (working in progress between Fernando and Andy) * FIWARE.Epic.Cloud.Monitoring.Analysis.SLAIntegration * FIWARE.Epic.Cloud.Monitoring.Visualization * FIWARE.Epic.Cloud.Monitoring.Management * FIWARE.Epic.Cloud.Monitoring.Security.Metrics * FIWARE.Epic.Cloud.Monitoring.ServiceMgrIntegration * Only Epics. Themes: 1/3 not complete * Accounting @Andy TODO: * Supply monitoring asset details * FIWARE.Epic.Cloud.Security.RBAC * FIWARE.Epic.Cloud.Security.APIs * FIWARE.Epic.Cloud.Monitoring.Visualization * FIWARE.Epic.Cloud.Monitoring.Management * FIWARE.Epic.Cloud.Monitoring.Security.Metrics @Alex TODO: * Refine the tracker page. @All * Refine the Epics, Features and User Stories * Provide baseline assets with their appropriate description information * Provide information in the tracker system (be careful, in the FIWARE Cloud track section, not in the FIWARE track section) * Provide the list of Features and User Stories to be implemented in the first minor release and put this information into the tracker system. I think that this information could be send to the rest of cloud members. I hope that I could take some light into the dark. 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 El 25/10/2011, a las 18:02, Edmonds, AndrewX escribi?: ------------------------------------------------------------- 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. ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Thu Oct 27 21:34:47 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 27 Oct 2011 21:34:47 +0200 Subject: [Fiware-cloud] Open Call candidates Message-ID: All, While finalizing the backlog and the work plan for the first release & sprint, now is the time to create the initial list of gaps that we have identified -- those which we believe can not be contained within our team (with the current funding level), and hence should potentially be targeting the first Open Call. Here is an initial list -- please, provide your feedback. The deadline is EOD Monday (sorry for the short notice). Virtualization Layer (Resource Management, Object Storage) -- TBD [Andy -- can you, please, suggest what would be the impact on the virtualization layer of not having the FT team on board? and/or other significant gaps that you are aware of -- maybe based on the Epics that we've identified?] Accounting [Fernando, all -- can you, please, outline the expected scope of work here? I assume this GE might subscribe to the Monitoring system, keep the records about resource usage in some internal format/repository -- per VM, service, account, etc.. maybe also enforce things like resource quotas? anything else?] Monitoring -- TBD, pending availability of the corresponding assets from WP6 [Andy -- can you, please, assess the sizing of the work on this GE if we go for an open-source stack, based on the assets you've mentioned?] SelfServices -- Portal Cloud Edge -- cloud-side management "agent" (Note: still under discussion) Service Management -- service composition tool (that would allow the application developer to easily build the corresponding OVF package) anything else -- all? Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From irenatr at gmail.com Thu Oct 27 23:49:00 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Thu, 27 Oct 2011 23:49:00 +0200 Subject: [Fiware-cloud] WP status In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E010FD796D2@MOPESMBX01.eu.thmulti.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE1903A4AA@IRSMSX101.ger.corp.intel.com> <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> <453EEB4CD4162742B6EF3D3F84E88A6E010FD796D2@MOPESMBX01.eu.thmulti.com> Message-ID: Dear all, I updated the Self Service Interface part. The major changes are the addition of features, user stories and assets. It has been made an update to the epics as well. I will be able to attend the review call on Monday. Best, Irena On Thu, Oct 27, 2011 at 11:13 AM, Defrance Serge < serge.defrance at technicolor.com> wrote: > Dear All, **** > > ** ** > > I updated the cloud edge chapter (both epics and asset) in our Cloud > hosting chapter on the mediawiki. **** > > There are other Epics mentioned in addition to the three I have added, they > certainly have to be deleted (unless another partner contributes on these > Epics). **** > > Another point is that the exact split of Epics between WP4 and WP7 for what > regards the Cloud Edge may still slightly evolve, depending on the > clarification discussion we currently have with our chief architect (and > which is about to be concluded).**** > > We may discuss these points during the Monday conf call.**** > > 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:* jeudi 27 octobre 2011 00:22 > *To:* fiware-cloud at lists.fi-ware.eu > > *Subject:* Re: [Fiware-cloud] WP status**** > > ** ** > > My comments below > > One more important thing: it is very important to outline in the > description of each Epic the scope of work to be done -- which also implies > that we need to mention the baseline assets that will be used. It is > important that whoever reads an Epic, understands what we are trying to, > why, what already exists as part of the baseline assets, and what is the > 'delta', or work to be done, associated with this particular work item -- > integration, enhancements, new pieces, etc. > > Regards, > Alex > > P.S. I've completed the description of most of the RM epics > > > > From: Alex Glikson/Haifa/IBM at IBMIL > To: fiware-cloud at lists.fi-ware.eu > Date: 26/10/2011 08:14 AM > Subject: Re: [Fiware-cloud] WP status > Sent by: fiware-cloud-bounces at lists.fi-ware.eu **** > ------------------------------ > > > > > Andy, Fernando -- thanks for the initiative! This is very helpful. I will > send more detailed comments later. One important comment, meanwhile: > > Regarding user stories and sprints -- I'm not sure we should manage user > stories in the same public tracker. That's why the "User Story" category and > the "Sprint" field are not there. > Moreover, strictly speaking, those are not supposed to be part of the > Backlog -- which is by definition a set of work items which have not been > scheduled to any sprint. > > So, besides completing and reviewing Themes and Epics in the backlog, and > completing the description of baseline assets we want to use, what I would > like to ask from all of you is to send me (or to the list) a much more > detailed description, in whatever format is convenient for you (sets of > bullets are fine for now -- we can then attach them to the wiki entry) of > the following: > 1) Features that you would like to include in the first minor release -- > outlining specific scope of work that you expect to be completed by January, > 31th, 2012, and > 2) User Stories that you would like to include in the first sprint -- i.e., > specific work items that will be done by November 30th. > > For both, I would like to see a very clear 'acceptance criteria' -- how > exactly will we measure and validate whether the corresponding work items > are done, and what can others expect as an outcome of this work. > > Thanks, > Alex > > > > > From: FERNANDO LOPEZ AGUILAR > To: "Edmonds, AndrewX" > Cc: Alex Glikson/Haifa/IBM at IBMIL > Date: 25/10/2011 07:20 PM > Subject: Re: WP status **** > ------------------------------ > > > > > Thank you Andy, > > I write them inline. > > > Tracker > * Only 2 from Alex and the rest are from Fernando (currently only EPICs > and Features -- this is OK, as explained above) > * FI-WARE Backlog Entry Type without User-Story option. > * We have release box but we have to change it to FI-WARE Release Id box > and FI-WARE Sprint Id box. > * We need to specify there for each EPIC, Feature and User Story in which > Release and Sprint we plan to develop it. Not really. Only for the first > one. The priorities might change over time, so we shouldn't try deciding up > front for longer than one minor release. > * We have to select which Feature and User Stories we want to implement in > the first minor release. > > Wiki Asset Descriptions > ? None from Cloud Proxy > ? None from Self-service Interfaces > ? Listed but not detailed from Monitoring > ? None that covers T4.2 -- Updated > * We have to differentiate between basseline asserts and needed assests. > The real asset is explained in more detail (e.g. Claudia in IaaS SM) and the > others are explained with less details (see MySQL). But the sections that we > use would be the same that all the assets have to use. > > We should describe here *only* the baseline assets. If they have > pre-requisites -- it is described in their documentation. and we may mention > that within the description of the asset. But we should not mention them in > the main list. > > Wiki Epics > * Here I want to give you some clarification about the different between > EPICs, Features and User Stories. > * EPICs is anything that we planned to develop (or have any idea about the > expended time to develop it) in a period of time *bigger* *than* a minor > release (3 months). > * Feature is anything that we planned to develop (or have any idea about > the expended time to develop it) in a period of time *less than* a minor > release (3 months). > * User Story is anything that we planned to develop (or have any idea about > the expended time to develop it) in a period of time *equal to* a sprint > (1 months). [or less] > * We have provided neither Features or User Stories except for IaaS SM and > PaaS Mgmt. Yep. As I mentioned above, we must update both the Wiki and the > Tracker with features for the first release, and also outline the stories > for the first sprint. > * Anyway, I could see some Epics like > FIWARE.Epic.Cloud.ResourceManager.Security.APIs > which is not a EPIC (IMHO), The Epic would be > FIWARE.Epic.Cloud.ResourceManager.Security. This should be a User Story. Well, > it is a matter of scope and sizing. If we figure out that the entire Epic > can be covered in a single sprint (which I don't believe is the case) -- we > can definitely 'downgrade' it to a story. > > IaaS Data Center Resource Management: 9/20 not complete > ? FIWARE.Epic.Cloud.ResourceManager.MgmtFabric -- done > ? FIWARE.Epic.Cloud.ResourceManager.QoS -- done > ? FIWARE.Epic.Cloud.ResourceManager.Mobility -- done > ? FIWARE.Epic.Cloud.ResourceManager.Placement -- done > ? FIWARE.Epic.Cloud.ResourceManager.PhysPlatformMgmt > ? FIWARE.Epic.Cloud.ResourceManager.Capacity -- done > ? FIWARE.Epic.Cloud.ResourceManager.Toolkit > ? FIWARE.Epic.Cloud.ResourceManager.Federation > ? FIWARE.Epic.Cloud.ResourceManager.Security.APIs > * IMHO, OCCI is not a basseline asset, it is a specific interface within > the rest of baseline assets (Openstack Nova, Glance, ...). > * Each Basseline assets have to describe the following subsections > Brief Description > Programming artifacts > Technologies used > Runtime pre-requisites (including Known software requirements) > IPR > Publicly available documentation > > except the needed assests like MySQL in IaaS SM that only need to describe > Brief Description > IPR > Publicly available documentation > * There are no Features and User Stories > > Object Storage > * Openstack switch, need to describe Technologies used and Runtime > pre-requisites subsections. > * No Features > * No User Stories (remenber that *.Security.SSO and *.Security.RBAC should > be a User Stories). > > Security 1/2 not complete > ? FIWARE.Epic.Cloud.Security.RBAC > * Openstack keynote, need to describe Technologies used and Runtime > pre-requisites subsections. > * Check if the Epics are Features. > > Self-Service Interfaces: 4/5 not complete > * No Baseline assets described > ? FIWARE.Epic.Cloud.SelfServiceInterfaces.UserCLI > ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminCLI > ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminPortal > ? FIWARE.Epic.Cloud.SelfServiceInterfaces.Security > * No Features, no User Stories > > Cloud Proxy: 5/8 not complete > * No baseline asset described > ? FIWARE.Epic.Cloud.CloudProxy.VirtualizationLayer > ? FIWARE.Epic.Cloud.CloudProxy.ManagementAPI > ? FIWARE.Epic.Cloud.CloudProxy.CloudAppProvisioning > ? FIWARE.Epic.Cloud.CloudProxy.ManagementProxy > ? FIWARE.Epic.Cloud.CloudProxy.Security > * Only Epics > > Monitoring: 5/11 not complete > * Some baseline assets without description (working in progress between > Fernando and Andy) > ? FIWARE.Epic.Cloud.Monitoring.Analysis.SLAIntegration > ? FIWARE.Epic.Cloud.Monitoring.Visualization > ? FIWARE.Epic.Cloud.Monitoring.Management > ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics > ? FIWARE.Epic.Cloud.Monitoring.ServiceMgrIntegration > * Only Epics. > > Themes: 1/3 not complete > ? Accounting > > @Andy TODO: > ? Supply monitoring asset details > ? FIWARE.Epic.Cloud.Security.RBAC > ? FIWARE.Epic.Cloud.Security.APIs > ? FIWARE.Epic.Cloud.Monitoring.Visualization > ? FIWARE.Epic.Cloud.Monitoring.Management > ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics > > @Alex TODO: > * Refine the tracker page. > > @All > * Refine the Epics, Features and User Stories > * Provide baseline assets with their appropriate description information > * Provide information in the tracker system (be careful, in the FIWARE > Cloud track section, not in the FIWARE track section) > * Provide the list of Features and User Stories to be implemented in the > first minor release and put this information into the tracker system. > > > I think that this information could be send to the rest of cloud members. I > hope that I could take some light into the dark. > > 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 > > > > El 25/10/2011, a las 18:02, Edmonds, AndrewX escribi?: > > > ------------------------------------------------------------- > 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. > > **** > ------------------------------ > > 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**** > > _______________________________________________ > 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: From GLIKSON at il.ibm.com Fri Oct 28 14:20:43 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 28 Oct 2011 14:20:43 +0200 Subject: [Fiware-cloud] Planning of the 1st major release In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE1903A4AA@IRSMSX101.ger.corp.intel.com> <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> Message-ID: Team, While outlining our features and user stories for the first minor release/sprint, it is important to make sure that we are in sync in the broader perspective of the first major release (M12) -- which is our next official deliverable. Hence, I would like to outline the main objectives that we should aim at, the way I see it (Juanjo -- would appreciate your input). This will help us deciding on the exact scope of each of the two releases (Nov-Jan, Feb-Apr). Our main objectives for M12 include: detailed architecture, GEs specification design, integration of baseline assets to create functional end-to-end stack, detailed gap analysis implementation of few selected enhancements (preferably including those which can be demonstrated end-to-end) user guide, admin guide, programming guide detailed requirements specification for 2nd major release -- incorporating feedback from UC projects (M24) design of new functions to be developed targeting 2nd major release (M24) Please, take the above objectives into consideration when planning the first minor release. Of course, feel free to comment on the list above and/or suggest improvements. For Resource Management GE, I envision the following features (draft/partial list): Setup of internal testbed Basic environment up and running -- including partial set of baseline assets (OpenStack, Glance, maybe others) Education and gap analysis Selection of enhancements to be implemented for the first major release Implement few of the selected enhancements targeting the first major release (TBD) Design of individual capabilities, focusing on enhancements and new functions tentatively targeted for the second major release (M24) resource pooling, QoS, capacity mgmt, monitoring, network, storage, image library, placement, federation, security, APIs, fabric, management of physical machines, security Design of integration with Service Manager "Digest" requirements of the UC Projects related to Resource Management GE This way the last 3 months can be dedicated to implementation of the enhancements/new functions, further integration (including cross-GE), documentation of M12 deliverables (especially A and D above), etc. Please, note that although the final integration between GEs is planned for months 13-15, we should explore the integration as soon as possible (especially between Service Manager and Resource Manager) -- because I expect this to be the most significant risk in delivering and end-to-end functional stack by M15, and the way to mitigate it (and avoid surprised too late in the cycle) is to start the integration sooner rather than later -- desirably even during the first minor release. Would appreciate your input. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 27/10/2011 12:21 AM Subject: Re: [Fiware-cloud] WP status Sent by: fiware-cloud-bounces at lists.fi-ware.eu My comments below One more important thing: it is very important to outline in the description of each Epic the scope of work to be done -- which also implies that we need to mention the baseline assets that will be used. It is important that whoever reads an Epic, understands what we are trying to, why, what already exists as part of the baseline assets, and what is the 'delta', or work to be done, associated with this particular work item -- integration, enhancements, new pieces, etc. Regards, Alex P.S. I've completed the description of most of the RM epics From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 26/10/2011 08:14 AM Subject: Re: [Fiware-cloud] WP status Sent by: fiware-cloud-bounces at lists.fi-ware.eu Andy, Fernando -- thanks for the initiative! This is very helpful. I will send more detailed comments later. One important comment, meanwhile: Regarding user stories and sprints -- I'm not sure we should manage user stories in the same public tracker. That's why the "User Story" category and the "Sprint" field are not there. Moreover, strictly speaking, those are not supposed to be part of the Backlog -- which is by definition a set of work items which have not been scheduled to any sprint. So, besides completing and reviewing Themes and Epics in the backlog, and completing the description of baseline assets we want to use, what I would like to ask from all of you is to send me (or to the list) a much more detailed description, in whatever format is convenient for you (sets of bullets are fine for now -- we can then attach them to the wiki entry) of the following: 1) Features that you would like to include in the first minor release -- outlining specific scope of work that you expect to be completed by January, 31th, 2012, and 2) User Stories that you would like to include in the first sprint -- i.e., specific work items that will be done by November 30th. For both, I would like to see a very clear 'acceptance criteria' -- how exactly will we measure and validate whether the corresponding work items are done, and what can others expect as an outcome of this work. Thanks, Alex From: FERNANDO LOPEZ AGUILAR To: "Edmonds, AndrewX" Cc: Alex Glikson/Haifa/IBM at IBMIL Date: 25/10/2011 07:20 PM Subject: Re: WP status Thank you Andy, I write them inline. Tracker * Only 2 from Alex and the rest are from Fernando (currently only EPICs and Features -- this is OK, as explained above) * FI-WARE Backlog Entry Type without User-Story option. * We have release box but we have to change it to FI-WARE Release Id box and FI-WARE Sprint Id box. * We need to specify there for each EPIC, Feature and User Story in which Release and Sprint we plan to develop it. Not really. Only for the first one. The priorities might change over time, so we shouldn't try deciding up front for longer than one minor release. * We have to select which Feature and User Stories we want to implement in the first minor release. Wiki Asset Descriptions ? None from Cloud Proxy ? None from Self-service Interfaces ? Listed but not detailed from Monitoring ? None that covers T4.2 -- Updated * We have to differentiate between basseline asserts and needed assests. The real asset is explained in more detail (e.g. Claudia in IaaS SM) and the others are explained with less details (see MySQL). But the sections that we use would be the same that all the assets have to use. We should describe here *only* the baseline assets. If they have pre-requisites -- it is described in their documentation. and we may mention that within the description of the asset. But we should not mention them in the main list. Wiki Epics * Here I want to give you some clarification about the different between EPICs, Features and User Stories. * EPICs is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time bigger than a minor release (3 months). * Feature is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time less than a minor release (3 months). * User Story is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time equal to a sprint (1 months). [or less] * We have provided neither Features or User Stories except for IaaS SM and PaaS Mgmt. Yep. As I mentioned above, we must update both the Wiki and the Tracker with features for the first release, and also outline the stories for the first sprint. * Anyway, I could see some Epics like FIWARE.Epic.Cloud.ResourceManager.Security.APIs which is not a EPIC (IMHO), The Epic would be FIWARE.Epic.Cloud.ResourceManager.Security. This should be a User Story. Well, it is a matter of scope and sizing. If we figure out that the entire Epic can be covered in a single sprint (which I don't believe is the case) -- we can definitely 'downgrade' it to a story. IaaS Data Center Resource Management: 9/20 not complete ? FIWARE.Epic.Cloud.ResourceManager.MgmtFabric -- done ? FIWARE.Epic.Cloud.ResourceManager.QoS -- done ? FIWARE.Epic.Cloud.ResourceManager.Mobility -- done ? FIWARE.Epic.Cloud.ResourceManager.Placement -- done ? FIWARE.Epic.Cloud.ResourceManager.PhysPlatformMgmt ? FIWARE.Epic.Cloud.ResourceManager.Capacity -- done ? FIWARE.Epic.Cloud.ResourceManager.Toolkit ? FIWARE.Epic.Cloud.ResourceManager.Federation ? FIWARE.Epic.Cloud.ResourceManager.Security.APIs * IMHO, OCCI is not a basseline asset, it is a specific interface within the rest of baseline assets (Openstack Nova, Glance, ...). * Each Basseline assets have to describe the following subsections Brief Description Programming artifacts Technologies used Runtime pre-requisites (including Known software requirements) IPR Publicly available documentation except the needed assests like MySQL in IaaS SM that only need to describe Brief Description IPR Publicly available documentation * There are no Features and User Stories Object Storage * Openstack switch, need to describe Technologies used and Runtime pre-requisites subsections. * No Features * No User Stories (remenber that *.Security.SSO and *.Security.RBAC should be a User Stories). Security 1/2 not complete ? FIWARE.Epic.Cloud.Security.RBAC * Openstack keynote, need to describe Technologies used and Runtime pre-requisites subsections. * Check if the Epics are Features. Self-Service Interfaces: 4/5 not complete * No Baseline assets described ? FIWARE.Epic.Cloud.SelfServiceInterfaces.UserCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminPortal ? FIWARE.Epic.Cloud.SelfServiceInterfaces.Security * No Features, no User Stories Cloud Proxy: 5/8 not complete * No baseline asset described ? FIWARE.Epic.Cloud.CloudProxy.VirtualizationLayer ? FIWARE.Epic.Cloud.CloudProxy.ManagementAPI ? FIWARE.Epic.Cloud.CloudProxy.CloudAppProvisioning ? FIWARE.Epic.Cloud.CloudProxy.ManagementProxy ? FIWARE.Epic.Cloud.CloudProxy.Security * Only Epics Monitoring: 5/11 not complete * Some baseline assets without description (working in progress between Fernando and Andy) ? FIWARE.Epic.Cloud.Monitoring.Analysis.SLAIntegration ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics ? FIWARE.Epic.Cloud.Monitoring.ServiceMgrIntegration * Only Epics. Themes: 1/3 not complete ? Accounting @Andy TODO: ? Supply monitoring asset details ? FIWARE.Epic.Cloud.Security.RBAC ? FIWARE.Epic.Cloud.Security.APIs ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics @Alex TODO: * Refine the tracker page. @All * Refine the Epics, Features and User Stories * Provide baseline assets with their appropriate description information * Provide information in the tracker system (be careful, in the FIWARE Cloud track section, not in the FIWARE track section) * Provide the list of Features and User Stories to be implemented in the first minor release and put this information into the tracker system. I think that this information could be send to the rest of cloud members. I hope that I could take some light into the dark. 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 El 25/10/2011, a las 18:02, Edmonds, AndrewX escribi?: ------------------------------------------------------------- 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. 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 _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud From GLIKSON at il.ibm.com Mon Oct 31 10:04:27 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 31 Oct 2011 11:04:27 +0200 Subject: [Fiware-cloud] Planning of the 1st major release In-Reply-To: References: <332A51FC2924EE4A8CDD5BB4BB05CE1903A4AA@IRSMSX101.ger.corp.intel.com> <275A4BBF-766B-43A4-B599-514A7391D6D0@tid.es> Message-ID: Please, see attached updated list of Resource Management GE Epics. Regards, Alex Setup of internal testbed Basic environment up and running -- including partial set of baseline assets (OpenStack, Glance, maybe others) Education and gap analysis Selection of enhancements to be implemented for the first major release (M12) Implement few of the selected enhancements targeting the first major release (TBD) Initial specification of individual capabilities, focusing on enhancements and new functions tentatively targeted for the second major release (M24) Resource pooling, QoS, capacity mgmt, monitoring, network, storage, image library, placement, federation, security, APIs, fabric, management of physical machines, security Initial design of integration with other GEs in Cloud Hosting: Service Management, Monitoring "Digest" requirements of the UC Projects related to Resource Management GE From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 28/10/2011 07:11 PM Subject: [Fiware-cloud] Planning of the 1st major release Sent by: fiware-cloud-bounces at lists.fi-ware.eu Team, While outlining our features and user stories for the first minor release/sprint, it is important to make sure that we are in sync in the broader perspective of the first major release (M12) -- which is our next official deliverable. Hence, I would like to outline the main objectives that we should aim at, the way I see it (Juanjo -- would appreciate your input). This will help us deciding on the exact scope of each of the two releases (Nov-Jan, Feb-Apr). Our main objectives for M12 include: detailed architecture, GEs specification design, integration of baseline assets to create functional end-to-end stack, detailed gap analysis implementation of few selected enhancements (preferably including those which can be demonstrated end-to-end) user guide, admin guide, programming guide detailed requirements specification for 2nd major release -- incorporating feedback from UC projects (M24) design of new functions to be developed targeting 2nd major release (M24) Please, take the above objectives into consideration when planning the first minor release. Of course, feel free to comment on the list above and/or suggest improvements. For Resource Management GE, I envision the following features (draft/partial list): Setup of internal testbed Basic environment up and running -- including partial set of baseline assets (OpenStack, Glance, maybe others) Education and gap analysis Selection of enhancements to be implemented for the first major release Implement few of the selected enhancements targeting the first major release (TBD) Design of individual capabilities, focusing on enhancements and new functions tentatively targeted for the second major release (M24) resource pooling, QoS, capacity mgmt, monitoring, network, storage, image library, placement, federation, security, APIs, fabric, management of physical machines, security Design of integration with Service Manager "Digest" requirements of the UC Projects related to Resource Management GE This way the last 3 months can be dedicated to implementation of the enhancements/new functions, further integration (including cross-GE), documentation of M12 deliverables (especially A and D above), etc. Please, note that although the final integration between GEs is planned for months 13-15, we should explore the integration as soon as possible (especially between Service Manager and Resource Manager) -- because I expect this to be the most significant risk in delivering and end-to-end functional stack by M15, and the way to mitigate it (and avoid surprised too late in the cycle) is to start the integration sooner rather than later -- desirably even during the first minor release. Would appreciate your input. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 27/10/2011 12:21 AM Subject: Re: [Fiware-cloud] WP status Sent by: fiware-cloud-bounces at lists.fi-ware.eu My comments below One more important thing: it is very important to outline in the description of each Epic the scope of work to be done -- which also implies that we need to mention the baseline assets that will be used. It is important that whoever reads an Epic, understands what we are trying to, why, what already exists as part of the baseline assets, and what is the 'delta', or work to be done, associated with this particular work item -- integration, enhancements, new pieces, etc. Regards, Alex P.S. I've completed the description of most of the RM epics From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.eu Date: 26/10/2011 08:14 AM Subject: Re: [Fiware-cloud] WP status Sent by: fiware-cloud-bounces at lists.fi-ware.eu Andy, Fernando -- thanks for the initiative! This is very helpful. I will send more detailed comments later. One important comment, meanwhile: Regarding user stories and sprints -- I'm not sure we should manage user stories in the same public tracker. That's why the "User Story" category and the "Sprint" field are not there. Moreover, strictly speaking, those are not supposed to be part of the Backlog -- which is by definition a set of work items which have not been scheduled to any sprint. So, besides completing and reviewing Themes and Epics in the backlog, and completing the description of baseline assets we want to use, what I would like to ask from all of you is to send me (or to the list) a much more detailed description, in whatever format is convenient for you (sets of bullets are fine for now -- we can then attach them to the wiki entry) of the following: 1) Features that you would like to include in the first minor release -- outlining specific scope of work that you expect to be completed by January, 31th, 2012, and 2) User Stories that you would like to include in the first sprint -- i.e., specific work items that will be done by November 30th. For both, I would like to see a very clear 'acceptance criteria' -- how exactly will we measure and validate whether the corresponding work items are done, and what can others expect as an outcome of this work. Thanks, Alex From: FERNANDO LOPEZ AGUILAR To: "Edmonds, AndrewX" Cc: Alex Glikson/Haifa/IBM at IBMIL Date: 25/10/2011 07:20 PM Subject: Re: WP status Thank you Andy, I write them inline. Tracker * Only 2 from Alex and the rest are from Fernando (currently only EPICs and Features -- this is OK, as explained above) * FI-WARE Backlog Entry Type without User-Story option. * We have release box but we have to change it to FI-WARE Release Id box and FI-WARE Sprint Id box. * We need to specify there for each EPIC, Feature and User Story in which Release and Sprint we plan to develop it. Not really. Only for the first one. The priorities might change over time, so we shouldn't try deciding up front for longer than one minor release. * We have to select which Feature and User Stories we want to implement in the first minor release. Wiki Asset Descriptions ? None from Cloud Proxy ? None from Self-service Interfaces ? Listed but not detailed from Monitoring ? None that covers T4.2 -- Updated * We have to differentiate between basseline asserts and needed assests. The real asset is explained in more detail (e.g. Claudia in IaaS SM) and the others are explained with less details (see MySQL). But the sections that we use would be the same that all the assets have to use. We should describe here *only* the baseline assets. If they have pre-requisites -- it is described in their documentation. and we may mention that within the description of the asset. But we should not mention them in the main list. Wiki Epics * Here I want to give you some clarification about the different between EPICs, Features and User Stories. * EPICs is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time bigger than a minor release (3 months). * Feature is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time less than a minor release (3 months). * User Story is anything that we planned to develop (or have any idea about the expended time to develop it) in a period of time equal to a sprint (1 months). [or less] * We have provided neither Features or User Stories except for IaaS SM and PaaS Mgmt. Yep. As I mentioned above, we must update both the Wiki and the Tracker with features for the first release, and also outline the stories for the first sprint. * Anyway, I could see some Epics like FIWARE.Epic.Cloud.ResourceManager.Security.APIs which is not a EPIC (IMHO), The Epic would be FIWARE.Epic.Cloud.ResourceManager.Security. This should be a User Story. Well, it is a matter of scope and sizing. If we figure out that the entire Epic can be covered in a single sprint (which I don't believe is the case) -- we can definitely 'downgrade' it to a story. IaaS Data Center Resource Management: 9/20 not complete ? FIWARE.Epic.Cloud.ResourceManager.MgmtFabric -- done ? FIWARE.Epic.Cloud.ResourceManager.QoS -- done ? FIWARE.Epic.Cloud.ResourceManager.Mobility -- done ? FIWARE.Epic.Cloud.ResourceManager.Placement -- done ? FIWARE.Epic.Cloud.ResourceManager.PhysPlatformMgmt ? FIWARE.Epic.Cloud.ResourceManager.Capacity -- done ? FIWARE.Epic.Cloud.ResourceManager.Toolkit ? FIWARE.Epic.Cloud.ResourceManager.Federation ? FIWARE.Epic.Cloud.ResourceManager.Security.APIs * IMHO, OCCI is not a basseline asset, it is a specific interface within the rest of baseline assets (Openstack Nova, Glance, ...). * Each Basseline assets have to describe the following subsections Brief Description Programming artifacts Technologies used Runtime pre-requisites (including Known software requirements) IPR Publicly available documentation except the needed assests like MySQL in IaaS SM that only need to describe Brief Description IPR Publicly available documentation * There are no Features and User Stories Object Storage * Openstack switch, need to describe Technologies used and Runtime pre-requisites subsections. * No Features * No User Stories (remenber that *.Security.SSO and *.Security.RBAC should be a User Stories). Security 1/2 not complete ? FIWARE.Epic.Cloud.Security.RBAC * Openstack keynote, need to describe Technologies used and Runtime pre-requisites subsections. * Check if the Epics are Features. Self-Service Interfaces: 4/5 not complete * No Baseline assets described ? FIWARE.Epic.Cloud.SelfServiceInterfaces.UserCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminCLI ? FIWARE.Epic.Cloud.SelfServiceInterfaces.AdminPortal ? FIWARE.Epic.Cloud.SelfServiceInterfaces.Security * No Features, no User Stories Cloud Proxy: 5/8 not complete * No baseline asset described ? FIWARE.Epic.Cloud.CloudProxy.VirtualizationLayer ? FIWARE.Epic.Cloud.CloudProxy.ManagementAPI ? FIWARE.Epic.Cloud.CloudProxy.CloudAppProvisioning ? FIWARE.Epic.Cloud.CloudProxy.ManagementProxy ? FIWARE.Epic.Cloud.CloudProxy.Security * Only Epics Monitoring: 5/11 not complete * Some baseline assets without description (working in progress between Fernando and Andy) ? FIWARE.Epic.Cloud.Monitoring.Analysis.SLAIntegration ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics ? FIWARE.Epic.Cloud.Monitoring.ServiceMgrIntegration * Only Epics. Themes: 1/3 not complete ? Accounting @Andy TODO: ? Supply monitoring asset details ? FIWARE.Epic.Cloud.Security.RBAC ? FIWARE.Epic.Cloud.Security.APIs ? FIWARE.Epic.Cloud.Monitoring.Visualization ? FIWARE.Epic.Cloud.Monitoring.Management ? FIWARE.Epic.Cloud.Monitoring.Security.Metrics @Alex TODO: * Refine the tracker page. @All * Refine the Epics, Features and User Stories * Provide baseline assets with their appropriate description information * Provide information in the tracker system (be careful, in the FIWARE Cloud track section, not in the FIWARE track section) * Provide the list of Features and User Stories to be implemented in the first minor release and put this information into the tracker system. I think that this information could be send to the rest of cloud members. I hope that I could take some light into the dark. 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 El 25/10/2011, a las 18:02, Edmonds, AndrewX escribi?: ------------------------------------------------------------- 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. 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 _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud _______________________________________________ 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 GLIKSON at il.ibm.com Mon Oct 31 10:11:51 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 31 Oct 2011 11:11:51 +0200 Subject: [Fiware-cloud] web conference URL Message-ID: http://www.ibm.com/collaboration/meeting/join?id=1131085 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Mon Oct 31 19:33:07 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 31 Oct 2011 20:33:07 +0200 Subject: [Fiware-cloud] continue the Cloud Hosting backlog review Message-ID: Hi, Please, indicate your availability using the following poll: http://www.doodle.com/is8b3gugavx8emz8 Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Mon Oct 31 21:25:27 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Mon, 31 Oct 2011 20:25:27 +0000 Subject: [Fiware-cloud] continue the Cloud Hosting backlog review In-Reply-To: References: Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1903AFED@IRSMSX101.ger.corp.intel.com> Alternatively, could we use our regular Tues morning slot? 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, October 31, 2011 6:33 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] continue the Cloud Hosting backlog review Hi, Please, indicate your availability using the following poll: http://www.doodle.com/is8b3gugavx8emz8 Thanks, Alex ------------------------------------------------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Mon Oct 31 22:25:09 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 31 Oct 2011 22:25:09 +0100 Subject: [Fiware-cloud] continue the Cloud Hosting backlog review In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1903AFED@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE1903AFED@IRSMSX101.ger.corp.intel.com> Message-ID: <41113254-C61F-4BA7-A6FA-8FB3F56C3F29@tid.es> Tomorrow is holiday in Spain. I prefer to postpone them to Wed. 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 31/10/2011, a las 21:25, Edmonds, AndrewX escribi?: Alternatively, could we use our regular Tues morning slot? 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, October 31, 2011 6:33 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] continue the Cloud Hosting backlog review Hi, Please, indicate your availability using the following poll: http://www.doodle.com/is8b3gugavx8emz8 Thanks, Alex ------------------------------------------------------------- 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. ________________________________ 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: