From GLIKSON at il.ibm.com Tue Nov 1 00:25:01 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 1 Nov 2011 01:25:01 +0200 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: I have a conflict at this particular slot this week (due to a visitor here in the lab).. Alex From: "Edmonds, AndrewX" To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" Date: 31/10/2011 10:25 PM Subject: RE: [Fiware-cloud] continue the Cloud Hosting backlog review 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 jhierro at tid.es Wed Nov 2 08:10:27 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 02 Nov 2011 08:10:27 +0100 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: <4EB0ECE3.5050704@tid.es> On 28/10/11 14:20, Alex Glikson wrote: > 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) According to the DoW, the architecture should be available by end of month 9, i.e., end of January 2012. We have to determine what format we will follow for this deliverable as to avoid too much paperwork. A different story are GEs specifications which actually have to be available by end of month 12, i.e., end of April 2012, the same way the rest of the items you have mentioned. With this minor amendment, I agree that the main objectives by end of month 12 (first major release) are the ones you described. Focus of the first major release actually should be on delivering a full IaaS Cloud Service that works end-to-end, including a self-service portal for IaaS. PaaS support may deferred to the second major release (planned to be delivered by end of month 24). It would be nice that some of the features/epics requested by any of the UC projects be covered in this first major release as long as they are related to IaaS. > 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. I'm not sure I do understand this description of features ... Features should have a clear link to some functionality to be developed in the product (the Resource Management GE in this case). They shouldn't map into steps of a process, like if we were following a waterfall process ... I haven't reviewed each and every Epic linked to the Resource Management GE, but they should map into functionality of the product, not process steps. Then, as I explained in a recent email sent to WPLs/WPAs, Features can be obtained by just selecting those Epics that we believe can be addressed in the first minor release. User Stories should also map to functionality to be developed in the product. Since we may be developing a feature during a 3 months-period, we will have to refine the feature into user stories, each covering the development of some part of the functionality described in the feature. This means, that for the first sprint, we should take the features we have identified for the first minor release and derive a number of user-stories for each of them, then decide which ones will be addressed in the first sprint. Some of the activities you describe map to work to be done by the development team during sprints, but not necessarily linked to a concrete functionality of the product. Question mark here is whether we should produce an entry in the backlog for these activities. Some Agile experts suggest that Backlogs should not only comprise entries linked to functionality to be covered but also any sort of work item to be performed by the development teams. We need to discuss at WPLs/WPAs level whether we want to have this sort of entries in our backlogs or not. On one hand, it's nice because it helps to monitor the work each team is doing and will help to show it to the external world (e.g., reviewers of the project). It will be also helpful during those periods of times where we don't plan to have so much development work, mostly designing and setting up the integration of components within GEs or between GEs. On the other hand, it may lead to a explosion of entries in the backlog. For the time being, please don't create items of this nature in the backlog. Let's try to address this in our next joint WPL/WPA confcall. I'll raise this as a topic for discussion in the WPL/WPA mailing list. > > 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. Fully agree on this. Hope my comments help. Best regards, -- Juanjo > > 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 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 Wed Nov 2 20:39:55 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 2 Nov 2011 21:39:55 +0200 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: <4EB178E2.5040106@tid.es> References: <4EB178E2.5040106@tid.es> Message-ID: Miguel -- thanks for the detailed review and the comments. Team -- please, apply changes based on Miguel's comments below. Thanks, Alex From: Miguel Carrillo To: Alex Glikson/Haifa/IBM at IBMIL Cc: JUAN JOSE HIERRO SUREDA Date: 02/11/2011 07:07 PM Subject: Materializing Cloud Hosting in FI-WARE Dear Alex , I am sending private emails to all WPLs with further comments to the " Materializing Cloud Hosting in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets IPRs in Assets are very frequently expressed in a vague manner. ?This product has IPR associated to it?, ?Open source?? To end with this situation change all assets and put this: Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. If you rephrase this or use variants it's ok as long as the additions are properly explained. Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS IaaS Data Center Resource Management Crowbar ? ?Programming artifacts? must be removed. This is not compliant with the template xCAT T ? ?Programming artifacts? must be removed. This is not compliant with the template OpenStack Nova ? template ignored System Pools ? wrong template (it not an ?open source assets coming from third parties?). It needs the long template. ISAAC ? wrong template (it not an ?open source assets coming from third parties?). It needs the long template. RESERVOIR ? not compliant with the template. Some sections are empty with an ?TBD?. Trusted Compute Pools ? ?Programming artifacts? must be removed. This is not compliant with the template Open Cloud Computing Interface (OCCI) ? ?Programming artifacts? must be removed. This is not compliant with the template OpenStack Glance ? template ignored OpenStack Quantum ? template ignored Open vSwitch ? ?Programming artifacts? must be removed. This is not compliant with the template IaaS Service Management JBoss ? ok MySQL ? ok Claudia ? ok PaaS Management Apache Tomcat - ok PostgreSQL- ok Ruby- ok RubyGem- ok Chef- ok PaaS Management Platform- ok Baseline Assets OpenStack Swift? ?Programming artifacts? must be removed. This is not compliant with the template Self-Service Interfaces Apache Tomcat ? ok MySQL ? ok HTML ? direct link to wikipedia. If it is explicitly an asset, it must have a wiki page that has to be compliant with the template CSS ? direct link to wikipedia. If it is explicitly an asset, it must have a wiki page that has to be compliant with the template Ruby on Rails ? direct link to wikipedia. If it is explicitly an asset, it must have a wiki page that has to be compliant with the template Cloud Proxy Nada Management Framework - ?NMF has no IPR associated to it? is very poor. Possibly this means that it is Open Source under a license such as Creative Commons, or alternatively something like the text in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Ruby Monitoring collectd - ? ?Programming artifacts? must be removed. This is not compliant with the template RabbitMQ ? I suspect that this qualifies as ?open source assets coming from third parties? in which case this has to use the short template, not this. ?Drools <- Fernando? ? - we must remove these informal remarks. This refers to an empty page with a template that is wrong Esper ? ?Programming artifacts? must be removed. This is not compliant with the template Graphite? ?Programming artifacts? must be removed. This is not compliant with the template Security OpenStack Keystone - not compliant with the template (I assume the righ one is the short one in this case) 2) COMMENTS ON BACKLOG I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. 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 andrewx.edmonds at intel.com Thu Nov 3 14:01:06 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Thu, 3 Nov 2011 13:01:06 +0000 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: References: <4EB178E2.5040106@tid.es> Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1903B92D@IRSMSX101.ger.corp.intel.com> I've looked after anything I originally supplied. 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: Wednesday, November 02, 2011 7:40 PM To: Miguel Carrillo; fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE Miguel -- thanks for the detailed review and the comments. Team -- please, apply changes based on Miguel's comments below. 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 irenatr at gmail.com Thu Nov 3 14:54:58 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Thu, 3 Nov 2011 14:54:58 +0100 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1903B92D@IRSMSX101.ger.corp.intel.com> References: <4EB178E2.5040106@tid.es> <332A51FC2924EE4A8CDD5BB4BB05CE1903B92D@IRSMSX101.ger.corp.intel.com> Message-ID: I have also made the changes for the Self Service Interfaces. Irena On Thu, Nov 3, 2011 at 2:01 PM, Edmonds, AndrewX wrote: > I?ve looked after anything I originally supplied.**** > > 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:* Wednesday, November 02, 2011 7:40 PM > *To:* Miguel Carrillo; fiware-cloud at lists.fi-ware.eu > *Subject:* Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE**** > > ** ** > > Miguel -- thanks for the detailed review and the comments. > > Team -- please, apply changes based on Miguel's comments below. > > 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. > > _______________________________________________ > 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 Thu Nov 3 14:56:19 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Thu, 03 Nov 2011 14:56:19 +0100 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE1903B92D@IRSMSX101.ger.corp.intel.com> References: <4EB178E2.5040106@tid.es> <332A51FC2924EE4A8CDD5BB4BB05CE1903B92D@IRSMSX101.ger.corp.intel.com> Message-ID: <0BB5F6D1-40CE-4021-9F8C-2812B1F6EFF1@tid.es> The same for me and I modify the monitoring part that I had written. 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 03/11/2011, a las 14:01, Edmonds, AndrewX escribi?: I?ve looked after anything I originally supplied. 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: Wednesday, November 02, 2011 7:40 PM To: Miguel Carrillo; fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE Miguel -- thanks for the detailed review and the comments. Team -- please, apply changes based on Miguel's comments below. 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: From fla at tid.es Mon Nov 7 11:47:03 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 07 Nov 2011 11:47:03 +0100 Subject: [Fiware-cloud] =?iso-8859-1?q?=5BFI-WARE=5D=A0Pending_Questions?= Message-ID: <33043CA2-4BBA-4EB7-8540-EB73811AD5FF@tid.es> Dear all, I send you the answer from some questions that we had. * How do we store/mngt. the credentials (e.g. EC2 Amazon)? Claudia does not store/manage the credentials. We asume that there is other component upper which would manage them. In case of management of users credentials, it is the same, Claudia only manage VDC, Services, VMs and so on but no user. * What is the possibility of scaling Claudia? Currently Claudia could be installed over a VM. The scalability of Claudia itself theoretically could be a possibility but we have not tested it. We include a EPIC/Feature to manage it in order to secure the scalability of the baseline asset. * It is possible to update the service manifest (OVF) dynamically (I suppose yes) OVF is only the deployment descriptor. If we wat to update the service manifest dynamically, we have to use the Cloud Standard API. * There are not trivial dependencies between Claudia and IaaS Data Center Mngt. Of course, all the functionalities that Claudia will have to provide, depends on the functionalities that the IaaS DCRM can export through the OCCI interface. * Why do we need to use clone VMs? Can we provide some UCs? We use the VM clone in case in which we want to make a deployment of a VM with specific configured software in it. An use case would be when we deployment a web server in a VM based on a specific template, then we need to do several changes on it like configure de IP direction, configure the web server and so on. When we have finished the configuration of this Web Server (within a specific VM), we have the possibility to make a VM clones in order to deploy automatically a new one due to scalability problems in it without the necessity to configure again all. This is a specific use case related to the PaaS in which the scalability of a platform is used with VM Clones and not templates. * Integration with SLA-SLO. Which type of SLA we are using. How Claudia manages the SLAs? Currently, Claudia does not manage SLA itself. We have some similar to explicit SLA based on scalability rules. * Why are we using TCloud between User Portal and PaaS? We prefer to extend a common standard API (OVF) and not use another one from the beginning. We want to use the same API that we are using in the IaaS SM. Also the interface that PaaS GE provide is Cloud Standard API based on OVF. * Imagine that the user wants data persistence in a DB. How can we specify the elasticity rules in terms of PaaS? 4CaaSt is currently starting which means that the scalability concepts have not started to be studied. When a solution will be developed, it would be incorporated into the FI-WARE solution (work in progress). * (Cloud Foundry, Crowbar) vs Chef We decide to use tools based on configuration engine and not image generation due to we want to offer management of those deploys VM and not only a image generation. Cloud Foundry is a PaaS, Crowbar is used to installed OpenStack, Chef is a configuration engine used as base for the PaaS Management (SDC). * Seguridad: Intrusion Detection System? We see it like a service that could be provide by the PaaS but not a functionality that the PaaS have to provide. * Seguridad: Anti-malware service The same for it like previous question. * Seguridad: Anti-virus service The same for it like previous question. * Revocation Currently, I am not sure what it means. I mean we have to know how we have to interact with it and if WP8 provide some tools or API to do it. * Non-repudiation The same for it like previous question. * Role based Control Integrate with WP8 We define a specific Use Case to deal with this issue, but we need to clarify the integration with WP8, although it is not a mandatory decision for the first sprint/release. * Security policy compliance TBD. * Event logging - Auditing All layers - related to monitoring We need to clarify what it means. What kind of things we have to take into control and so on. By default we have (of course) some event logging system in order to see any execution of IaaS SM and PaaS, not only related to monitoring system. But do we have to develop anything else? Best Regards, PD: I am trying to modify the tracker system in order to change the Sprint Id and Release Id of the Epic/Features of IaaS SM and PaaS GE but I cannot access to it. 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 GLIKSON at il.ibm.com Mon Nov 7 17:58:13 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 7 Nov 2011 18:58:13 +0200 Subject: [Fiware-cloud] Cloud chapter tracker Message-ID: Team, Bad news, I'm afraid.. I've accidentally removed the Cloud chapter tracker (while being sure I'm removing a field..). Since the backups are being done for the entire FusionForge database, unfortunately, it is not possible to recover the individual tracker. So, seems that we would need to re-populate our tracker content, based on the content of the Wiki (which holds the actual content, luckily). What the support team *was* able to retrieve is a snapshot of the content of the tracker entries, in a form of a spreadsheet -- attached below. I'm trying to re-create the tracker itself, and am having some issues too.. Will let you know when the tracker is ready. Then, everyone will need to re-populate their Themes/Epics/Features/User Stories/Work Items. Really sorry about the hassle.. Regards, Alex P.S. there is a chance that some of the newer entries are not in the spreadsheet, since backups are done once in a while -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cloud_issues.xls Type: application/vnd.ms-excel Size: 41984 bytes Desc: not available URL: From fla at tid.es Mon Nov 7 18:48:38 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 07 Nov 2011 18:48:38 +0100 Subject: [Fiware-cloud] Cloud chapter tracker In-Reply-To: References: Message-ID: <64E8F567-AAAC-40E1-A1B2-96AAB35447A8@tid.es> Really bad news, Well, this means that you have to pay a round of drinks in the next F2F meeting... ;) Do not worry Alex, but try to not repeat it again in future, please. We try to do our best to complete it. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain [cid:65E3CA3A-3DFE-41B6-8F69-2AD965EA42FA at hi.inet] El 07/11/2011, a las 17:58, Alex Glikson escribi?: Team, Bad news, I'm afraid.. I've accidentally removed the Cloud chapter tracker (while being sure I'm removing a field..). Since the backups are being done for the entire FusionForge database, unfortunately, it is not possible to recover the individual tracker. So, seems that we would need to re-populate our tracker content, based on the content of the Wiki (which holds the actual content, luckily). What the support team *was* able to retrieve is a snapshot of the content of the tracker entries, in a form of a spreadsheet -- attached below. I'm trying to re-create the tracker itself, and am having some issues too.. Will let you know when the tracker is ready. Then, everyone will need to re-populate their Themes/Epics/Features/User Stories/Work Items. Really sorry about the hassle.. Regards, Alex P.S. there is a chance that some of the newer entries are not in the spreadsheet, since backups are done once in a while ________________________________ 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 Mon Nov 7 15:17:48 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 7 Nov 2011 16:17:48 +0200 Subject: [Fiware-cloud] Fw: Planning of the 1st major release Message-ID: Team, Following Juanjo's comments below, I would like to ask you to upload to the Wiki the description of features for the first minor release as well as user stories for the first sprint (which has actually started). If you have concerns regarding confidential information in description of user-stories or features, you can use the wiki space under Cloud Hosting project in Forge, and add a link there (instead of keeping everything in the public wiki). We may also have work items not directly related to product features/user stories -- we will describe them separately (no need to have a Wiki page for them -- just a reasonable description in the tracker). As some of you might have noticed, there are some technical issues with the Tracker, so we can't finish reflecting the epics/features/stories/work items in the tracker yet (I will send a separate email on this later today). So, for now, let's make sure our Wiki is fully compliant with the project management requirements. The deadline is November 10th. We will review the plan for 1st minor release & sprint at our tomorrow's weekly call (11am CET). Please, send me your list of features and user stories/work items (essentially, things that you plan to do/accomplish in the upcoming 1 and 3 months) by the end of the day today. If you still don't have everything specified in the Wiki -- a bullet list (with some details) would be sufficient. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 07/11/2011 04:04 PM ----- From: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , MIGUEL CARRILLO PACHECO , "jhierro >> \"Juan J. Hierro\"" Date: 02/11/2011 09:10 AM Subject: Re: Planning of the 1st major release On 28/10/11 14:20, Alex Glikson wrote: > 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) According to the DoW, the architecture should be available by end of month 9, i.e., end of January 2012. We have to determine what format we will follow for this deliverable as to avoid too much paperwork. A different story are GEs specifications which actually have to be available by end of month 12, i.e., end of April 2012, the same way the rest of the items you have mentioned. With this minor amendment, I agree that the main objectives by end of month 12 (first major release) are the ones you described. Focus of the first major release actually should be on delivering a full IaaS Cloud Service that works end-to-end, including a self-service portal for IaaS. PaaS support may deferred to the second major release (planned to be delivered by end of month 24). It would be nice that some of the features/epics requested by any of the UC projects be covered in this first major release as long as they are related to IaaS. > 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. I'm not sure I do understand this description of features ... Features should have a clear link to some functionality to be developed in the product (the Resource Management GE in this case). They shouldn't map into steps of a process, like if we were following a waterfall process ... I haven't reviewed each and every Epic linked to the Resource Management GE, but they should map into functionality of the product, not process steps. Then, as I explained in a recent email sent to WPLs/WPAs, Features can be obtained by just selecting those Epics that we believe can be addressed in the first minor release. User Stories should also map to functionality to be developed in the product. Since we may be developing a feature during a 3 months-period, we will have to refine the feature into user stories, each covering the development of some part of the functionality described in the feature. This means, that for the first sprint, we should take the features we have identified for the first minor release and derive a number of user-stories for each of them, then decide which ones will be addressed in the first sprint. Some of the activities you describe map to work to be done by the development team during sprints, but not necessarily linked to a concrete functionality of the product. Question mark here is whether we should produce an entry in the backlog for these activities. Some Agile experts suggest that Backlogs should not only comprise entries linked to functionality to be covered but also any sort of work item to be performed by the development teams. We need to discuss at WPLs/WPAs level whether we want to have this sort of entries in our backlogs or not. On one hand, it's nice because it helps to monitor the work each team is doing and will help to show it to the external world (e.g., reviewers of the project). It will be also helpful during those periods of times where we don't plan to have so much development work, mostly designing and setting up the integration of components within GEs or between GEs. On the other hand, it may lead to a explosion of entries in the backlog. For the time being, please don't create items of this nature in the backlog. Let's try to address this in our next joint WPL/WPA confcall. I'll raise this as a topic for discussion in the WPL/WPA mailing list. > > 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. Fully agree on this. Hope my comments help. Best regards, -- Juanjo > > 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 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 jhierro at tid.es Mon Nov 7 20:27:41 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 07 Nov 2011 20:27:41 +0100 Subject: [Fiware-cloud] Cloud chapter tracker In-Reply-To: <64E8F567-AAAC-40E1-A1B2-96AAB35447A8@tid.es> References: <64E8F567-AAAC-40E1-A1B2-96AAB35447A8@tid.es> Message-ID: <27C0A116-469A-48D7-9692-4BC1D6E775DA@tid.es> Hi, Please don't start to recreate the tracker manually yet because we'll try one solution for restoring the tracker contents tomorrow morning. I believe it's worth waiting untill we test it. We'll keep you informed. Let's cross fingers Cheers, -- Juanjo Enviado desde mi iPad El 07/11/2011, a las 18:48, "FERNANDO LOPEZ AGUILAR" > escribi?: Really bad news, Well, this means that you have to pay a round of drinks in the next F2F meeting... ;) Do not worry Alex, but try to not repeat it again in future, please. We try to do our best to complete it. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain El 07/11/2011, a las 17:58, Alex Glikson escribi?: Team, Bad news, I'm afraid.. I've accidentally removed the Cloud chapter tracker (while being sure I'm removing a field..). Since the backups are being done for the entire FusionForge database, unfortunately, it is not possible to recover the individual tracker. So, seems that we would need to re-populate our tracker content, based on the content of the Wiki (which holds the actual content, luckily). What the support team *was* able to retrieve is a snapshot of the content of the tracker entries, in a form of a spreadsheet -- attached below. I'm trying to re-create the tracker itself, and am having some issues too.. Will let you know when the tracker is ready. Then, everyone will need to re-populate their Themes/Epics/Features/User Stories/Work Items. Really sorry about the hassle.. Regards, Alex P.S. there is a chance that some of the newer entries are not in the spreadsheet, since backups are done once in a while ________________________________ 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 ________________________________ 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 Mon Nov 7 20:40:32 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 7 Nov 2011 21:40:32 +0200 Subject: [Fiware-cloud] Cloud chapter tracker In-Reply-To: <64E8F567-AAAC-40E1-A1B2-96AAB35447A8@tid.es> References: <64E8F567-AAAC-40E1-A1B2-96AAB35447A8@tid.es> Message-ID: FERNANDO LOPEZ AGUILAR wrote on 07/11/2011 07:48:38 PM: > > Really bad news, > > Well, this means that you have to pay a round of drinks in the next > F2F meeting... ;) Sure, you can count on it :-) Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Tue Nov 8 12:58:09 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 8 Nov 2011 11:58:09 +0000 Subject: [Fiware-cloud] OpenStack Reference Architecture Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE1903C6B9@IRSMSX101.ger.corp.intel.com> http://www.referencearchitecture.org/ ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From fla at tid.es Tue Nov 8 18:24:55 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 08 Nov 2011 18:24:55 +0100 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: There are my 8 points of development and their distribution in the different Releases and Sprints. 1. Setup of internal testbed 2. Basic environment up and running -- including baseline asset (Claudia) 3. Education and gap analysis 4. Selection and Implementation of enhancements (in order) to be implemented for the first major release about IaaS SM (M12) * Work Items: * Definition of the architecture of Monitoring (FIWARE.Release.1.1 FIWARE.Sprint.1.1.1) * User Stories: * FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.OVFCompatibility (FIWARE.Release.1.1 FIWARE.Sprint.1.1.1) * FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.OCCIClient (FIWARE.Release.1.1 FIWARE.Sprint.1.1.1) * FIWARE.Epic.Cloud.ServiceManager.VDCManagement.VDCDeploy (FIWARE.Release.1.1 FIWARE.Sprint.1.1.2) * FIWARE.Epic.Cloud.ServiceManager.VDCManagement.VDCUndeploy (FIWARE.Release.1.1 FIWARE.Sprint.1.1.2) * FIWARE.Epic.Cloud.ServiceManager.VDCManagement.UpdateVDCConf (FIWARE.Release.1.1 FIWARE.Sprint.1.1.2) * FIWARE.Epic.Cloud.ServiceManager.Monitoring.VMProbeInstalling (FIWARE.Release.1.1 FIWARE.Sprint.1.1.2) * FIWARE.Epic.Cloud.ServiceManager.Monitoring.ColletcData (FIWARE.Release.1.1 FIWARE.Sprint.1.1.3) * FIWARE.Epic.Cloud.ServiceManager.Monitoring.PublishSubscribe (FIWARE.Release.1.1 FIWARE.Sprint.1.1.3) * FIWARE.Epic.Cloud.ServiceManager.ServiceAutoScalling.GetMonitoringMetrics (FIWARE.Release.1.2 FIWARE.Sprint.1.2.1) * FIWARE.Epic.Cloud.ServiceManager.ServiceAutoScalling.ElastRules (FIWARE.Release.1.2 FIWARE.Sprint.1.2.1) * FIWARE.Epic.Cloud.ServiceManager.ServiceAutoScalling.AutomaticProcessingRules (FIWARE.Release.1.2 FIWARE.Sprint.1.2.2) * FIWARE.Epic.Cloud.ServiceManager.Template.GetTemplateInformation (FIWARE.Release.1.2 FIWARE.Sprint.1.2.3) * FIWARE.Epic.Cloud.ServiceManager.Template.VM2Template (FIWARE.Release.1.2 FIWARE.Sprint.1.2.3) * FIWARE.Epic.Cloud.ServiceManager.Snapshot.CreateSnapshot (FIWARE.Release.1.2 FIWARE.Sprint.1.2.3) * FIWARE.Epic.Cloud.ServiceManager.Snapshot.RestoreSnapshot (FIWARE.Release.1.2 FIWARE.Sprint.1.2.3) * FIWARE.Epic.Cloud.ServiceManager.Snapshot.DeleteSnapshot (FIWARE.Release.1.2 FIWARE.Sprint.1.2.3) 5. Initial specification of individual capabilities, focusing on enhancements and new functions tentatively targeted for the second major release about IaaS SM (M24) * User Stories: * FIWARE.Epic.Cloud.ServiceManager.VMClone.CreateVMClone (FIWARE.Release.2.1 FIWARE.Sprint.2.1.1) * FIWARE.Epic.Cloud.ServiceManager.VMClone.RestoreVMClone (FIWARE.Release.2.1 FIWARE.Sprint.2.1.1) * FIWARE.Epic.Cloud.ServiceManager.VMClone.DeleteVMClone (FIWARE.Release.2.1 FIWARE.Sprint.2.1.1) * FIWARE.Epic.Cloud.ServiceManager.CDMI.OVFextension (FIWARE.Release.2.1 FIWARE.Sprint.2.1.1) * FIWARE.Epic.Cloud.ServiceManager.CDMI.CIMIextension (FIWARE.Release.2.1 FIWARE.Sprint.2.1.2) * FIWARE.Epic.Cloud.ServiceManager.CDMI.CDMIClient (FIWARE.Release.2.1 FIWARE.Sprint.2.1.2) * FIWARE.Epic.Cloud.ServiceManager.CDMI.ContainersMgmt (FIWARE.Release.2.1 FIWARE.Sprint.2.1.2) * FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.CIMIImplementation (FIWARE.Release.2.1 FIWARE.Sprint.2.1.3) * FIWARE.Epic.Cloud.ServiceManager.Security.SSO (not scheduled yet) * FIWARE.Epic.Cloud.ServiceManager.Security.RBAC (not scheduled yet) * Epics: * FIWARE.Epic.Cloud.ServiceManager.Federation (not scheduled yet) * FIWARE.Feature.Cloud.ServiceManager.ClaudiaScale (not scheduled yet) 1. Initial specification of individual capabilities, focusing on enhancements and new functions tentatively targeted for the second major release about PaaS Management (M24) * Epics: * FIWARE.Epic.Cloud.PaaS.OVF+ (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.PaaSScaling (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.AplicationMgmt (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.PaaSConfigurationMgmt (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.InstalationMgmt (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.PlatformMgmt (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.DeploymentDesign (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.Monitoring (not scheduled yet) * FIWARE.Epic.Cloud.PaaS.Security (not scheduled yet) 2. Initial design of integration with other GEs in Cloud Hosting: IaaS DCRM, Monitoring, PaaS GE 3. "Digest" requirements of the UC Projects related to IaaS SM and PaaS GE. 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 31/10/2011, a las 10:04, Alex Glikson escribi?: Please, see attached updated list of Resource Management GE Epics. Regards, Alex 1. Setup of internal testbed 2. Basic environment up and running -- including partial set of baseline assets (OpenStack, Glance, maybe others) 3. Education and gap analysis 4. Selection of enhancements to be implemented for the first major release (M12) 5. Implement few of the selected enhancements targeting the first major release (TBD) 6. 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 7. Initial design of integration with other GEs in Cloud Hosting: Service Management, Monitoring 8. "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 ________________________________ 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 Tue Nov 8 19:57:44 2011 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 08 Nov 2011 19:57:44 +0100 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: References: <4EB178E2.5040106@tid.es> Message-ID: <4EB97BA8.30305@tid.es> Dear all, We have been struggling to get back the old tracker with very little luck. So unfortunately we will have to retype all the entries on the tracker (or, better, copy-paste from the wiki) I did not want to leave today without sending this warning (tomorrow is a bank holiday in Madrid) Best regards, Miguel 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 Tue Nov 8 21:46:21 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 8 Nov 2011 22:46:21 +0200 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: <4EB97BA8.30305@tid.es> References: <4EB178E2.5040106@tid.es> <4EB97BA8.30305@tid.es> Message-ID: All, I've re-created the Cloud Chapter tracker. As discussed, please, proceed with re-populating the entries. Don't forget to assign release and sprint to those Features & User Stories/Work Items planned for the first release/sprint. Just to remind you that the deadline is November, 10th. Thanks, Alex From: Miguel Carrillo To: "fiware-cloud at lists.fi-ware.eu" Cc: Alex Glikson/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 08/11/2011 08:57 PM Subject: Materializing Cloud Hosting in FI-WARE Dear all, We have been struggling to get back the old tracker with very little luck. So unfortunately we will have to retype all the entries on the tracker (or, better, copy-paste from the wiki) I did not want to leave today without sending this warning (tomorrow is a bank holiday in Madrid) Best regards, Miguel 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 serge.defrance at technicolor.com Wed Nov 9 08:59:46 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Wed, 9 Nov 2011 08:59:46 +0100 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: References: <4EB178E2.5040106@tid.es> <4EB97BA8.30305@tid.es> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0121C9C222@MOPESMBX01.eu.thmulti.com> Dear all, I ? repopulated ? the Cloud Chapter tracker for what concern Cloud Edge. Do we also have to include feature in the tracker ? (I only included "Epic" as everybody up to now). 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: mardi 8 novembre 2011 21:46 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE All, I've re-created the Cloud Chapter tracker. As discussed, please, proceed with re-populating the entries. Don't forget to assign release and sprint to those Features & User Stories/Work Items planned for the first release/sprint. Just to remind you that the deadline is November, 10th. Thanks, Alex From: Miguel Carrillo To: "fiware-cloud at lists.fi-ware.eu" Cc: Alex Glikson/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 08/11/2011 08:57 PM Subject: Materializing Cloud Hosting in FI-WARE ________________________________ Dear all, We have been struggling to get back the old tracker with very little luck. So unfortunately we will have to retype all the entries on the tracker (or, better, copy-paste from the wiki) I did not want to leave today without sending this warning (tomorrow is a bank holiday in Madrid) Best regards, Miguel 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 Wed Nov 9 09:38:08 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 9 Nov 2011 10:38:08 +0200 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E0121C9C222@MOPESMBX01.eu.thmulti.com> References: <4EB178E2.5040106@tid.es> <4EB97BA8.30305@tid.es> <453EEB4CD4162742B6EF3D3F84E88A6E0121C9C222@MOPESMBX01.eu.thmulti.com> Message-ID: Thanks, Serge. Yes, we definitely need to include Features -- at least those associated with the first minor release, as well as User Stories and/or Work Items -- at least for the first sprint. I personally haven't done it yet for Resource Management, but plan to finish it by the deadline (which is tomorrow). Would appreciate if everyone else could do the same. Thanks, Alex From: Defrance Serge To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" Date: 09/11/2011 10:03 AM Subject: RE: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE Dear all, I ? repopulated ? the Cloud Chapter tracker for what concern Cloud Edge. Do we also have to include feature in the tracker ? (I only included ?Epic? as everybody up to now). 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: mardi 8 novembre 2011 21:46 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE All, I've re-created the Cloud Chapter tracker. As discussed, please, proceed with re-populating the entries. Don't forget to assign release and sprint to those Features & User Stories/Work Items planned for the first release/sprint. Just to remind you that the deadline is November, 10th. Thanks, Alex From: Miguel Carrillo To: "fiware-cloud at lists.fi-ware.eu" Cc: Alex Glikson/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 08/11/2011 08:57 PM Subject: Materializing Cloud Hosting in FI-WARE Dear all, We have been struggling to get back the old tracker with very little luck. So unfortunately we will have to retype all the entries on the tracker (or, better, copy-paste from the wiki) I did not want to leave today without sending this warning (tomorrow is a bank holiday in Madrid) Best regards, Miguel 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 irenatr at gmail.com Wed Nov 9 20:07:20 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Wed, 9 Nov 2011 20:07:20 +0100 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: References: <4EB178E2.5040106@tid.es> <4EB97BA8.30305@tid.es> <453EEB4CD4162742B6EF3D3F84E88A6E0121C9C222@MOPESMBX01.eu.thmulti.com> Message-ID: Hi Alex when I open the link FI-WARE Theme/Epic/Feature Requestsin the tracker, I get the same database error. I will try to populate it tomorrow trying to log from another account. Irena On Wed, Nov 9, 2011 at 9:38 AM, Alex Glikson wrote: > Thanks, Serge. > > Yes, we definitely need to include Features -- at least those associated > with the first minor release, as well as User Stories and/or Work Items -- > at least for the first sprint. > I personally haven't done it yet for Resource Management, but plan to > finish it by the deadline (which is tomorrow). Would appreciate if everyone > else could do the same. > > Thanks, > Alex > > > > From: Defrance Serge > To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" < > fiware-cloud at lists.fi-ware.eu> > Date: 09/11/2011 10:03 AM > Subject: RE: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE > ------------------------------ > > > > Dear all, > > I ? repopulated ? the Cloud Chapter tracker for what concern Cloud Edge. > Do we also have to include feature in the tracker ? (I only included ?Epic? > as everybody up to now). > 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:* mardi 8 novembre 2011 21:46* > To:* fiware-cloud at lists.fi-ware.eu* > Subject:* Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE > > All, > > I've re-created the Cloud Chapter tracker. As discussed, please, proceed > with re-populating the entries. Don't forget to assign release and sprint > to those Features & User Stories/Work Items planned for the first > release/sprint. > Just to remind you that the deadline is November, 10th. > > Thanks, > Alex > > > > > From: Miguel Carrillo > To: "fiware-cloud at lists.fi-ware.eu" > Cc: Alex Glikson/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA < > jhierro at tid.es> > Date: 08/11/2011 08:57 PM > Subject: Materializing Cloud Hosting in FI-WARE > > ------------------------------ > > > > > Dear all, > > We have been struggling to get back the old tracker with very little > luck. So unfortunately we will have to retype all the entries on the > tracker (or, better, copy-paste from the wiki) > > I did not want to leave today without sending this warning (tomorrow is > a bank holiday in Madrid) > > Best regards, > > Miguel > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at.* > **http://www.tid.es/ES/PAGINAS/disclaimer.aspx* > > > _______________________________________________ > Fiware-cloud mailing list > Fiware-cloud at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-cloud > > -- Irena -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Wed Nov 9 20:31:45 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Wed, 9 Nov 2011 19:31:45 +0000 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: References: <4EB178E2.5040106@tid.es> <4EB97BA8.30305@tid.es> <453EEB4CD4162742B6EF3D3F84E88A6E0121C9C222@MOPESMBX01.eu.thmulti.com> Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE190456CE@IRSMSX101.ger.corp.intel.com> That looks to be the wrong tracker - this is the one with all the current WP4 items https://forge.fi-ware.eu/tracker/?atid=204&group_id=14&func=browse From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Irena Trajkovska Sent: Wednesday, November 09, 2011 7:07 PM To: Alex Glikson Cc: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE Hi Alex when I open the link FI-WARE Theme/Epic/Feature Requests in the tracker, I get the same database error. I will try to populate it tomorrow trying to log from another account. Irena On Wed, Nov 9, 2011 at 9:38 AM, Alex Glikson > wrote: Thanks, Serge. Yes, we definitely need to include Features -- at least those associated with the first minor release, as well as User Stories and/or Work Items -- at least for the first sprint. I personally haven't done it yet for Resource Management, but plan to finish it by the deadline (which is tomorrow). Would appreciate if everyone else could do the same. Thanks, Alex From: Defrance Serge > To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" > Date: 09/11/2011 10:03 AM Subject: RE: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE ________________________________ Dear all, I ? repopulated ? the Cloud Chapter tracker for what concern Cloud Edge. Do we also have to include feature in the tracker ? (I only included "Epic" as everybody up to now). 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: mardi 8 novembre 2011 21:46 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE All, I've re-created the Cloud Chapter tracker. As discussed, please, proceed with re-populating the entries. Don't forget to assign release and sprint to those Features & User Stories/Work Items planned for the first release/sprint. Just to remind you that the deadline is November, 10th. Thanks, Alex From: Miguel Carrillo > To: "fiware-cloud at lists.fi-ware.eu" > Cc: Alex Glikson/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA > Date: 08/11/2011 08:57 PM Subject: Materializing Cloud Hosting in FI-WARE ________________________________ Dear all, We have been struggling to get back the old tracker with very little luck. So unfortunately we will have to retype all the entries on the tracker (or, better, copy-paste from the wiki) I did not want to leave today without sending this warning (tomorrow is a bank holiday in Madrid) Best regards, Miguel Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -- Irena ------------------------------------------------------------- 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 GLIKSON at il.ibm.com Wed Nov 9 21:32:29 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 9 Nov 2011 22:32:29 +0200 Subject: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE190456CE@IRSMSX101.ger.corp.intel.com> References: <4EB178E2.5040106@tid.es> <4EB97BA8.30305@tid.es> <453EEB4CD4162742B6EF3D3F84E88A6E0121C9C222@MOPESMBX01.eu.thmulti.com> <332A51FC2924EE4A8CDD5BB4BB05CE190456CE@IRSMSX101.ger.corp.intel.com> Message-ID: Good catch -- thanks, Andy. Regards, Alex From: "Edmonds, AndrewX" To: Irena Trajkovska , Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 09/11/2011 11:31 PM Subject: RE: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE That looks to be the wrong tracker ? this is the one with all the current WP4 items https://forge.fi-ware.eu/tracker/?atid=204&group_id=14&func=browse From: fiware-cloud-bounces at lists.fi-ware.eu [ mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Irena Trajkovska Sent: Wednesday, November 09, 2011 7:07 PM To: Alex Glikson Cc: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE Hi Alex when I open the link FI-WARE Theme/Epic/Feature Requests in the tracker, I get the same database error. I will try to populate it tomorrow trying to log from another account. Irena On Wed, Nov 9, 2011 at 9:38 AM, Alex Glikson wrote: Thanks, Serge. Yes, we definitely need to include Features -- at least those associated with the first minor release, as well as User Stories and/or Work Items -- at least for the first sprint. I personally haven't done it yet for Resource Management, but plan to finish it by the deadline (which is tomorrow). Would appreciate if everyone else could do the same. Thanks, Alex From: Defrance Serge To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" < fiware-cloud at lists.fi-ware.eu> Date: 09/11/2011 10:03 AM Subject: RE: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE Dear all, I ? repopulated ? the Cloud Chapter tracker for what concern Cloud Edge. Do we also have to include feature in the tracker ? (I only included ?Epic? as everybody up to now). 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: mardi 8 novembre 2011 21:46 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Materializing Cloud Hosting in FI-WARE All, I've re-created the Cloud Chapter tracker. As discussed, please, proceed with re-populating the entries. Don't forget to assign release and sprint to those Features & User Stories/Work Items planned for the first release/sprint. Just to remind you that the deadline is November, 10th. Thanks, Alex From: Miguel Carrillo To: "fiware-cloud at lists.fi-ware.eu" Cc: Alex Glikson/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA < jhierro at tid.es> Date: 08/11/2011 08:57 PM Subject: Materializing Cloud Hosting in FI-WARE Dear all, We have been struggling to get back the old tracker with very little luck. So unfortunately we will have to retype all the entries on the tracker (or, better, copy-paste from the wiki) I did not want to leave today without sending this warning (tomorrow is a bank holiday in Madrid) Best regards, Miguel Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -- Irena ------------------------------------------------------------- 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 andrewx.edmonds at intel.com Thu Nov 10 09:54:12 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Thu, 10 Nov 2011 08:54:12 +0000 Subject: [Fiware-cloud] FW: [Fiware-security] Slides to be used in the internal FI-WARE workshop on Security Identity, Access Control and Privacy Management GEs In-Reply-To: <4EBB8E51.5030604@tid.es> References: <4EBB8E51.5030604@tid.es> Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE19045971@IRSMSX101.ger.corp.intel.com> FYI -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Thursday, November 10, 2011 8:42 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-security at lists.fi-ware.eu; fiware at lists.fi-ware.eu Subject: [Fiware-security] Slides to be used in the internal FI-WARE workshop on Security Identity, Access Control and Privacy Management GEs Hi all, Slides that will be used in the workshop this morning have been uploaded to FusionForge and is available at: https://forge.fi-ware.eu/docman/view.php/7/584/Meeting_WP8-Use_Case_Projects_v05.ppt Best regards, -- Juanjo 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-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From GLIKSON at il.ibm.com Sat Nov 12 16:40:05 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sat, 12 Nov 2011 17:40:05 +0200 Subject: [Fiware-cloud] absence Message-ID: FYI, I will be out of office Sunday-Wednesday, without email access. Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVIDBR at il.ibm.com Mon Nov 14 14:06:48 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 15:06:48 +0200 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: <4EC10497.1010802@tid.es> References: <4EC10497.1010802@tid.es> Message-ID: Dear Miguel, The request for this report came to my attention only an hour ago. AFAIK, the request came to the attention of Alex, the WP leader, on Friday, which is a weekend in Israel. Alex is on the leave till Thursday this week without an access to email. I will be surprised if the task leaders in WP4 expected this short notice more than I did today. And to me it came out of the blue. In any case, I will substitute for Alex to coordinate the WP report preparation in an attempt to prepare a coherent deliverable in the short period of time we are given. Miguel, I forward your request to the task leaders of our WP to solicit their contributions to get them informed. Dear partners, please refer to the template sent by Miguel (in the attachements) and send me the specific section numbers you can contribute fully or partially, and the expected hour of your contribution. If you cannot contribute today on such a short notice, please explicitly indicate so in your reply and suggest an alternative. I need to get these initial messages from you a.s.a.p. to plan my time working on this report. The total size of the WP4 report should be in the range of 6-7 pages. I will also make myself available on Skype (david.breitgand), if you need to talk to me directly. Best regards. -- 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: Miguel Carrillo To: Alex Glikson/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, Dagan Gilat/Haifa/IBM at IBMIL, David Breitgand/Haifa/IBM at IBMIL Cc: MARIA ISABEL ALONSO MEDIAVILLA , JAVIER DE PEDRO SANCHEZ , JUAN JOSE HIERRO SUREDA Date: 14/11/2011 02:08 PM Subject: WP4 reporting Dear all, Juanjo has spoken to you about the subject so I guess this does not come as a surprise. The dealine for this passed days ago and the problem is that it should be delivered today to the EC. We'll see what we can do but for the time being start putting all together. I enclose two messages with instructions. I will send an example from other WP later today, in case it helps. Best regards and thanks for all the effort, 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 ----- Message from JAVIER DE PEDRO SANCHEZ on Mon, 07 Nov 2011 16:21:58 +0100 ----- To: MIGUEL CARRILLO PACHECO , "Bohnert, Thomas Michael" , Yaron Wolfsthal , "thierry.nagellen at orange-ftgroup.com" , CARLOS RALLI UCENDO , Garino Pierangelo , BISSON Pascal , stefano de panfilis , "nuria.delama at atos.net" cc: "subsidies at tid.es" Subject: FI-WARE: Technical information of WPx Dear all, you are receiving this e-mail because you are a WP leader of FI-WARE. If you are in the process of editing your contributions to the reporting, please make sure that you take this into account: Please do not forget to mention the WP objectives for the reporting period (M1-M6) in the first paragraphs Please make sure that each one of the tasks has an explicit section. Those not started in the reporting period must have a short text explaining why not. These examples would be fine: "It will start on Mx", &q! uot;It wi tion of the task xxx, planned for Mx" Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. Please do not forget to include the list of Deliverables and Milestones of your WP and their status. BR Javier. - ----- Message from JAVIER DE PEDRO SANCHEZ on Tue, 08 Nov 2011 12:07:43 +0100 ----- To: MIGUEL CARRILLO PACHECO Subject: RV: FI-WARE: first official review report (M1-M6) De: JAVIER DE PEDRO SANCHEZ Enviado el: viernes, 21 de octubre de 2011 15:44 Para: 'fiware-administrative at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: FI-WARE: first official review report (M1-M6) Dear all First official review is around the corner and the following approach is going to be followed: Technical issues: 1.- All partners to write out their report describing the technical activities carried out during the last six months. Please, use enclosed word file called: ?FI-WARE - technical activities -name_partner? Deadline: October 28th 2.- TID to compile activities per WP and send to every WP leader a file containing all technical activities carried out in their WP. Deadline: November 3st 3.- WP leaders to integrate these activities in a readable section. WP leaders submit their section to TID Deadline: November 8th Administrative issues: 4. All partners to send actual costs during this period. Please, use enclosed excel file called: ?FI-WARE - actual costs -name_partner? Deadline: October 28th 5.- TID to send to each partner excel file of follow-up of real effort (done until M5) Deadline: November 3st 6. All partners to send real effort filling out the previous follow-up file. Deadline: November 8th 7. TID to integrate all WP technical activities description, costs and efforts in the first semester report. Please, keep subsidies at tid.es in the recipient list. We would appreciate an email from you to indicate that you have received this e-mail. Thank you very much. Best regards Javier -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 19427 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 19427 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - technical activities -name_partner.docx Type: application/octet-stream Size: 230106 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - actual costs -name_partner.xlsx Type: application/octet-stream Size: 42010 bytes Desc: not available URL: From DAVIDBR at il.ibm.com Mon Nov 14 15:50:24 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 16:50:24 +0200 Subject: [Fiware-cloud] Fw: WP4 reporting Message-ID: Hi Guys, I'm sorry for nudging you. Until now I didn't get response from any of the WP4 partners on this: "please refer to the template sent by Miguel (in the attachements) and send me the specific section numbers you can contribute fully or partially, and the expected hour of your contribution. If you cannot contribute today on such a short notice, please explicitly indicate so in your reply and suggest an alternative." I understand that you all must be busy with what you are doing at the moment. However, this report is important for successful review of the project, so please try giving this a priority. We need to coordinate quickly to get this done a.s.a.p., hence my request for the contribution plan from you. Thanks. -- 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 ----- Forwarded by David Breitgand/Haifa/IBM on 14/11/2011 04:40 PM ----- From: David Breitgand/Haifa/IBM To: Miguel Carrillo Cc: Alex Glikson/Haifa/IBM at IBMIL, Dagan Gilat/Haifa/IBM at IBMIL, MARIA ISABEL ALONSO MEDIAVILLA , JAVIER DE PEDRO SANCHEZ , JUAN JOSE HIERRO SUREDA , Yaron Wolfsthal/Haifa/IBM at IBMIL, fiware-cloud at lists.fi-ware.eu, andrewx.edmonds at intel.com, FERNANDO LOPEZ AGUILAR Date: 14/11/2011 03:06 PM Subject: Re: WP4 reporting Dear Miguel, The request for this report came to my attention only an hour ago. AFAIK, the request came to the attention of Alex, the WP leader, on Friday, which is a weekend in Israel. Alex is on the leave till Thursday this week without an access to email. I will be surprised if the task leaders in WP4 expected this short notice more than I did today. And to me it came out of the blue. In any case, I will substitute for Alex to coordinate the WP report preparation in an attempt to prepare a coherent deliverable in the short period of time we are given. Miguel, I forward your request to the task leaders of our WP to solicit their contributions to get them informed. Dear partners, please refer to the template sent by Miguel (in the attachements) and send me the specific section numbers you can contribute fully or partially, and the expected hour of your contribution. If you cannot contribute today on such a short notice, please explicitly indicate so in your reply and suggest an alternative. I need to get these initial messages from you a.s.a.p. to plan my time working on this report. The total size of the WP4 report should be in the range of 6-7 pages. I will also make myself available on Skype (david.breitgand), if you need to talk to me directly. Best regards. -- 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: Miguel Carrillo To: Alex Glikson/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, Dagan Gilat/Haifa/IBM at IBMIL, David Breitgand/Haifa/IBM at IBMIL Cc: MARIA ISABEL ALONSO MEDIAVILLA , JAVIER DE PEDRO SANCHEZ , JUAN JOSE HIERRO SUREDA Date: 14/11/2011 02:08 PM Subject: WP4 reporting Dear all, Juanjo has spoken to you about the subject so I guess this does not come as a surprise. The dealine for this passed days ago and the problem is that it should be delivered today to the EC. We'll see what we can do but for the time being start putting all together. I enclose two messages with instructions. I will send an example from other WP later today, in case it helps. Best regards and thanks for all the effort, 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 ----- Message from JAVIER DE PEDRO SANCHEZ on Mon, 07 Nov 2011 16:21:58 +0100 ----- To: MIGUEL CARRILLO PACHECO , "Bohnert, Thomas Michael" , Yaron Wolfsthal , "thierry.nagellen at orange-ftgroup.com" , CARLOS RALLI UCENDO , Garino Pierangelo , BISSON Pascal , stefano de panfilis , "nuria.delama at atos.net" cc: "subsidies at tid.es" Subject: FI-WARE: Technical information of WPx Dear all, you are receiving this e-mail because you are a WP leader of FI-WARE. If you are in the process of editing your contributions to the reporting, please make sure that you take this into account: Please do not forget to mention the WP objectives for the reporting period (M1-M6) in the first paragraphs Please make sure that each one of the tasks has an explicit section. Those not started in the reporting period must have a short text explaining why not. These examples would be fine: "It will start on Mx", &q! uot;It wi tion of the task xxx, planned for Mx" Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. Please do not forget to include the list of Deliverables and Milestones of your WP and their status. BR Javier. - ----- Message from JAVIER DE PEDRO SANCHEZ on Tue, 08 Nov 2011 12:07:43 +0100 ----- To: MIGUEL CARRILLO PACHECO Subject: RV: FI-WARE: first official review report (M1-M6) De: JAVIER DE PEDRO SANCHEZ Enviado el: viernes, 21 de octubre de 2011 15:44 Para: 'fiware-administrative at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: FI-WARE: first official review report (M1-M6) Dear all First official review is around the corner and the following approach is going to be followed: Technical issues: 1.- All partners to write out their report describing the technical activities carried out during the last six months. Please, use enclosed word file called: ?FI-WARE - technical activities -name_partner? Deadline: October 28th 2.- TID to compile activities per WP and send to every WP leader a file containing all technical activities carried out in their WP. Deadline: November 3st 3.- WP leaders to integrate these activities in a readable section. WP leaders submit their section to TID Deadline: November 8th Administrative issues: 4. All partners to send actual costs during this period. Please, use enclosed excel file called: ?FI-WARE - actual costs -name_partner? Deadline: October 28th 5.- TID to send to each partner excel file of follow-up of real effort (done until M5) Deadline: November 3st 6. All partners to send real effort filling out the previous follow-up file. Deadline: November 8th 7. TID to integrate all WP technical activities description, costs and efforts in the first semester report. Please, keep subsidies at tid.es in the recipient list. We would appreciate an email from you to indicate that you have received this e-mail. Thank you very much. Best regards Javier -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 19427 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 19427 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - technical activities -name_partner.docx Type: application/octet-stream Size: 230106 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - actual costs -name_partner.xlsx Type: application/octet-stream Size: 42010 bytes Desc: not available URL: From fla at tid.es Mon Nov 14 15:57:17 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 14 Nov 2011 15:57:17 +0100 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: References: Message-ID: Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. ________________________________ 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: 01 - FI-WARE - technical activities (TID-WP4).docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 247742 bytes Desc: 01 - FI-WARE - technical activities (TID-WP4).docx URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVIDBR at il.ibm.com Mon Nov 14 16:15:01 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 17:15:01 +0200 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: References: Message-ID: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , "andrewx.edmonds at intel.com" , MIGUEL CARRILLO PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] -------------- next part -------------- An HTML attachment was scrubbed... URL: From irenatr at gmail.com Mon Nov 14 16:34:35 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Mon, 14 Nov 2011 16:34:35 +0100 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: References: Message-ID: Hi David, following the example of Fernando, I added the activities of UPM together with the ones of Telefonica bellow the Task 4.5: Self-service Portal/API and PaaS hosting enablementI am sending the merged file in attachment. Greetings Irena On Mon, Nov 14, 2011 at 4:15 PM, David Breitgand wrote: > Hi Fernando, > > I did not know about this. Is Xavier doing the aggregation work for the > WP4 report? The reason I'm asking is that there was a gap in communication > among the partners. Should we send our contributions for WP4 to Xavier for > aggregation??? I'm kind of confused who is responsible for what. In any > case, I would gladly let Xavier doing this work of aggregation. Please > confirm that he is responsible for this. > > Concerning the content of your contribution. As Miguel specified in his > instructions: > > "Do *not* provide a breakdown of what each partner has done. The > description is general and presents the results as the outcome of teamwork. > Punctual mentions to specific partners with specific and clearly defined > tasks are allowed but avoid enumerations of partners everywhere! That is to > say, you must describe the achievements of your work package as a whole, > not the achievements of each partner, going one by one. " > > Can you please take a few minutes to slightly edit your contribution to > follow this instructions? In your tasks, you start with "TID as a leader", > etc. > > Thanks for promptly responding on the section numbers. > Dear partners, please follow Fernando's example and communicate your > contributions to me promptly. > > Thanks. > > -- 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: FERNANDO LOPEZ AGUILAR > To: David Breitgand/Haifa/IBM at IBMIL > Cc: "fiware-cloud at lists.fi-ware.eu" , > "andrewx.edmonds at intel.com" , MIGUEL CARRILLO > PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron > Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA > Date: 14/11/2011 04:57 PM > Subject: Re: WP4 reporting > ------------------------------ > > > > Dear David, > > I sent this information in a previous request from Javier de Pedro, anyway > I give you again. Give me some feedback if you have any problem to open it. > > > ------------------------------ > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - > technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] > [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] > [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] > [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] > > _______________________________________________ > Fiware-cloud mailing list > Fiware-cloud at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-cloud > > -- Irena -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 01 - FI-WARE - technical activities (TID+UPM-WP4).odt Type: application/vnd.oasis.opendocument.text Size: 225424 bytes Desc: not available URL: From mcp at tid.es Mon Nov 14 17:11:08 2011 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 14 Nov 2011 17:11:08 +0100 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: References: Message-ID: <4EC13D9C.6080308@tid.es> Dear all, The WP leader should be aggregating everyone's inputs and chasing up those who did not send the info. In this case, you should have requested this info from TID (Fernando, Javier or whoever). I understand the situation but please let us not change the general scenario, WPLs are responsible for this. I am personally aggregating WP1 and WP12 and I am getting texts like that. And I simply edit it as I deem it reasonable, without going to each one. I just leave a general description taking the info when it is usefuil and dismissing where it's not. I am not extreme about deleting mentions to partners, but I avoid a mere enumeration of individual partners, which is normally not a good sign (un-integrated work). Thanks Miguel El 14/11/2011 16:15, David Breitgand escribi?: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , "andrewx.edmonds at intel.com" , MIGUEL CARRILLO PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting ________________________________ Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] -- ---------------------------------------------------------------------- _/ _/_/ 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 DAVIDBR at il.ibm.com Mon Nov 14 17:18:19 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 18:18:19 +0200 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: <4EC13D9C.6080308@tid.es> References: <4EC13D9C.6080308@tid.es> Message-ID: No problem, Miguel. Since Alex is on the leave, as I wrote already, I will substitute for him and aggregate all the inputs. Thanks. -- david From: Miguel Carrillo To: David Breitgand/Haifa/IBM at IBMIL Cc: FERNANDO LOPEZ AGUILAR , "andrewx.edmonds at intel.com" , Dagan Gilat/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" , JUAN JOSE HIERRO SUREDA , Yaron Wolfsthal/Haifa/IBM at IBMIL Date: 14/11/2011 06:11 PM Subject: Re: WP4 reporting Dear all, The WP leader should be aggregating everyone's inputs and chasing up those who did not send the info. In this case, you should have requested this info from TID (Fernando, Javier or whoever). I understand the situation but please let us not change the general scenario, WPLs are responsible for this. I am personally aggregating WP1 and WP12 and I am getting texts like that. And I simply edit it as I deem it reasonable, without going to each one. I just leave a general description taking the info when it is usefuil and dismissing where it's not. I am not extreme about deleting mentions to partners, but I avoid a mere enumeration of individual partners, which is normally not a good sign (un-integrated work). Thanks Miguel El 14/11/2011 16:15, David Breitgand escribi?: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , "andrewx.edmonds at intel.com" , MIGUEL CARRILLO PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] -- ---------------------------------------------------------------------- _/ _/_/ 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 Nov 14 18:00:50 2011 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 14 Nov 2011 18:00:50 +0100 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: <4EC13D9C.6080308@tid.es> References: <4EC13D9C.6080308@tid.es> Message-ID: <4EC14942.4090405@tid.es> I nearly forgot. I said I was going to send a reasonable example in case it could help. Please see the reporting sent by WP7, I like it. El 14/11/2011 17:11, Miguel Carrillo escribi?: Dear all, The WP leader should be aggregating everyone's inputs and chasing up those who did not send the info. In this case, you should have requested this info from TID (Fernando, Javier or whoever). I understand the situation but please let us not change the general scenario, WPLs are responsible for this. I am personally aggregating WP1 and WP12 and I am getting texts like that. And I simply edit it as I deem it reasonable, without going to each one. I just leave a general description taking the info when it is usefuil and dismissing where it's not. I am not extreme about deleting mentions to partners, but I avoid a mere enumeration of individual partners, which is normally not a good sign (un-integrated work). Thanks Miguel El 14/11/2011 16:15, David Breitgand escribi?: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , "andrewx.edmonds at intel.com" , MIGUEL CARRILLO PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting ________________________________ Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] -- ---------------------------------------------------------------------- _/ _/_/ 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: D121-FI-WARE_Project Report.doc Type: application/msword Size: 80384 bytes Desc: not available URL: From andrewx.edmonds at intel.com Mon Nov 14 18:19:29 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Mon, 14 Nov 2011 17:19:29 +0000 Subject: [Fiware-cloud] WP4 reporting Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE190465B0@IRSMSX101.ger.corp.intel.com> WP4 reporting contribution from Intel. If anything else is needed let me know ASAP. Andy. Task T4.1's (lead by Intel) objective is to provide the enabling technologies to power virtualisation within WP4. The work is closely aligned with T4.2 (Resource Management) and there has been active collaboration between these two tasks. It will be the virtualised resources offered out as services, which will form an essential service on which other WPs and UAs can build upon. In particular, the following work has been carried out beginning in M1 up to M6: - Analysis of required functionality. This has been based on the partner's knowledge and reflected in the FI-ware wiki [1]. Education, exploration and experimentation with various key baseline assets of WP4 is also ongoing. - Contributed to the high level description deliverable, which also includes the high level architecture of WP4. - Identification, initial assessment and detailing of baseline assets including appropriate standards (OCCI, CDMI). Those assets can be seen on the FI-ware wiki page [1]. - Definition of epics, features and tasks related to T4.1 have been placed on the FI-ware wiki [1] and corresponding entries in the Cloud Hosting tracker [2]. - Lead monitoring activities within WP4, including identification of baseline assets, description of epics and features. Also contributed a monitoring architecture. A prototype implementation was also assembled for further evaluation. Other activities related to this Task were: - Supervised the WP4 to WP8 (security) integration and reflected the outputs of considering input from WP8 upon the FI-ware wiki. - Participation in Madrid kick off - Participation in Turin F2F [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE [2] https://forge.fi-ware.eu/tracker/?atid=204&group_id=14&func=browse From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Irena Trajkovska Sent: Monday, November 14, 2011 3:35 PM To: David Breitgand Cc: fiware-cloud at lists.fi-ware.eu; Yaron Wolfsthal Subject: Re: [Fiware-cloud] WP4 reporting Hi David, following the example of Fernando, I added the activities of UPM together with the ones of Telefonica bellow the Task 4.5: Self-service Portal/API and PaaS hosting enablementI am sending the merged file in attachment. Greetings Irena On Mon, Nov 14, 2011 at 4:15 PM, David Breitgand > wrote: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR > To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" >, "andrewx.edmonds at intel.com" >, MIGUEL CARRILLO PACHECO >, Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA > Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting ________________________________ Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -- Irena ------------------------------------------------------------- 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 jhierro at tid.es Mon Nov 14 19:54:05 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Nov 2011 19:54:05 +0100 Subject: [Fiware-cloud] Detailed comments on the Cloud Backlog information available on the Wiki/Tracker In-Reply-To: <4EC0FD21.6070406@tid.es> References: <4EC0FD21.6070406@tid.es> Message-ID: <4EC163CD.9080209@tid.es> Dear Alex and rest of the Cloud Hosting team, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB tomorrow (none of them affect the Wiki contents so that they won't affect generation of the .pdf book linked to second release of the FI-WARE Product Vision Deliverable). Despite the short time I'm giving you to react, I believe this is feasible because they are rather few and responsibility to fix them can be properly distributed so that changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). I copy the rest of WPLs and WPAs so that they can monitor comments to the different WPs. Best regards, -- Juanjo Cloud Hosting: * General comments: * Despite the language used for describing goals in the template defined in August for backlog entries has not been followed for some entries, it's true that Goals linked to Cloud Hosting GEs do not adapt so well to that formula, so we will keep things as they are. Some people may argue that description of goals doesn't follow the standard Agile conventions but we'll see. * You have defined FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis as two WorkItems that you will carry out in order to refine the General Architecture and conduct a gap analysis. Both being linked to all GEs. That's pretty fine (and good practice). However ... Do you plan to carry out these WorkItems during Sprint 1.1.1 ? If so, you should assign the "FIWARE.Sprint.1.1.1" value to the "FI-WARE Sprint Id" field in the corresponding ticket. * Resource Manager: * You haven't followed the defined convention for values of the "FI-WARE Release Id" and "FI-WARE Sprint Id" field * You have identified a WorkItem named as FIWARE.WorkItem.Cloud.ResourceManager.SvcMgrIntegration.InitialDesign ... Are you going to carry out this item during Sprint 1.1.1 ? The WorkItem may have been just identified but be still pending of planning ... that would be fine but wanted to double-check) * There are some Stories that have been assigned a value of 1.1.2 to the Sprint Id. However, you should not plan Stories or Work Items in Sprints after the current/about-to-start sprint. This would be against Agile Principles. While we will try to "plan" Features linked to releases, this "planning" will not apply to User Story and Work Items. This is a simple change because you just need to delete value of the "FI-WARE Sprint Id" field for those User Stories or Work Items that won't fit in FI-WARE.Sprint.1.1.1 * There are several Stories that are not assigned to Sprint 1.1.1. This is fine (you have identified the Stories but you have decided not to address them in Sprint 1.1.1). However, I want to double-check that you didn't simply forget to assign a value to the FI-WARE Sprint Id field. * Service Manager: * It has no sense to assign a User Story or a Work Item to another Sprint different that the current/about-to-start Sprint, as mentioned for the Resource Manager GE. * There are Epics and Features listed in the User Stories section on the Wiki. Just place the entries in the right section. * I see Epics that are assigned to a Sprint (e.g., FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.OCCIClient) ... this doesn't make sense (only User-Stories or WorkItems are carried out in a Sprint). Please fix ... * I see Features that are assigned to a Sprint (e.g., FIWARE.Feature.Cloud.ServiceManager.ServiceAutoScalling.ElastRules). Features are just assigned to releases. * Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? * PaaS Management: * Work Items do not need to be declared linked to a minor release. What is relevant to declare linked to releases are Features. On the other hand ... Shouldn't the ones being identified be linked to sprint 1.1.1 ? * Object Storage: * What type of entry is FIWARE.Epic.Cloud.ObjectStorage.Security.SSO. Apparently an Epic but has not been labeled as such on the tracker. * Wouldn't any of the identified Features be linked to the 1st minor release ? Couldn't you plan them ? * Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? * Cloud Edge: * Don't see the ticket on the tracker that should be linked to the FIWARE.Feature.Cloud.CloudProxy.APIFirstRelease entry. * Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? * Monitoring: * Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? * Wouldn't any of the identified Features be linked to the 1st minor release ? Couldn't you plan them ? * Self-Service Interface: * Tickets linked to entries declared on the Wiki haven't been created ! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From DAVIDBR at il.ibm.com Mon Nov 14 20:01:32 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 21:01:32 +0200 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE190465B0@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE190465B0@IRSMSX101.ger.corp.intel.com> Message-ID: Hi Guys, I hope you've been following the thread on WP4 reporting today and the situation that we are trying to resolve is clear to you. Sorry again for nudging at this late hour, but I still miss contributions from Cloud Edge and Self-Help Portal partners. Please provide this a.s.a.p. I have the contribution from Intel, TID, and IBM. Thanks everybody for providing your inputs on such a short notice. Best. -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVIDBR at il.ibm.com Mon Nov 14 21:11:16 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 22:11:16 +0200 Subject: [Fiware-cloud] Fw: WP4 reporting Message-ID: A correction to my previous (attached) mail. The contribution regarding Self-Help Portal was sent by Irena and it is just fine. Thanks, Irena. Sorry, I over-looked this on the first read. The missing input is the Cloud Edge at the moment. Thanks. -- david ----- Forwarded by David Breitgand/Haifa/IBM on 14/11/2011 10:07 PM ----- From: David Breitgand/Haifa/IBM To: "fiware-cloud at lists.fi-ware.eu" Cc: juan.quemada at upm.es, JUAN JOSE HIERRO SUREDA , Dagan Gilat/Haifa/IBM at IBMIL, Miguel Carrillo Date: 14/11/2011 09:01 PM Subject: WP4 reporting Hi Guys, I hope you've been following the thread on WP4 reporting today and the situation that we are trying to resolve is clear to you. Sorry again for nudging at this late hour, but I still miss contributions from Cloud Edge and Self-Help Portal partners. Please provide this a.s.a.p. I have the contribution from Intel, TID, and IBM. Thanks everybody for providing your inputs on such a short notice. Best. -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVIDBR at il.ibm.com Mon Nov 14 22:35:43 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Mon, 14 Nov 2011 23:35:43 +0200 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: <4EC14942.4090405@tid.es> References: <4EC13D9C.6080308@tid.es> <4EC14942.4090405@tid.es> Message-ID: Miguel, Please find attached the WP4 progress report. Contributions: ----------------------------------- IBM: yes Intel: yes UPM: yes TID: yes Technicolor: pending ----------------------------------- Since I didn't have the Technicolor contribution, I compiled something myself based on the wiki and tracker. Serge, Pascal, please review and modify the Technicolor part as you see fit Everybody, please review and provide additional feedback to Miguel and Juanjo. Thanks for making this effort on such a short notice! Good night. -- 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: Miguel Carrillo To: David Breitgand/Haifa/IBM at IBMIL Cc: FERNANDO LOPEZ AGUILAR , "andrewx.edmonds at intel.com" , Dagan Gilat/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" , JUAN JOSE HIERRO SUREDA , Yaron Wolfsthal/Haifa/IBM at IBMIL Date: 14/11/2011 07:00 PM Subject: Re: WP4 reporting I nearly forgot. I said I was going to send a reasonable example in case it could help. Please see the reporting sent by WP7, I like it. El 14/11/2011 17:11, Miguel Carrillo escribi?: Dear all, The WP leader should be aggregating everyone's inputs and chasing up those who did not send the info. In this case, you should have requested this info from TID (Fernando, Javier or whoever). I understand the situation but please let us not change the general scenario, WPLs are responsible for this. I am personally aggregating WP1 and WP12 and I am getting texts like that. And I simply edit it as I deem it reasonable, without going to each one. I just leave a general description taking the info when it is usefuil and dismissing where it's not. I am not extreme about deleting mentions to partners, but I avoid a mere enumeration of individual partners, which is normally not a good sign (un-integrated work). Thanks Miguel El 14/11/2011 16:15, David Breitgand escribi?: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , "andrewx.edmonds at intel.com" , MIGUEL CARRILLO PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] -- ---------------------------------------------------------------------- _/ _/_/ 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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[attachment "D121-FI-WARE_Project Report.doc" deleted by David Breitgand/Haifa/IBM] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D121-FI-WARE_Project Report_WP4.doc Type: application/octet-stream Size: 165863 bytes Desc: not available URL: From fla at tid.es Mon Nov 14 23:05:10 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 14 Nov 2011 23:05:10 +0100 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: References: <4EC13D9C.6080308@tid.es> <4EC14942.4090405@tid.es> Message-ID: <5001DC04-770E-4D5E-8588-F27362AC3644@tid.es> Dear David, Juanjo and Miguel, I provide a new version of the document with missing compiled parts regarding the T4.5. ________________________________ 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: D121-FI-WARE_Project Report_WP4_TID.rtf Type: text/rtf Size: 189256 bytes Desc: D121-FI-WARE_Project Report_WP4_TID.rtf URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 14 23:56:33 2011 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 14 Nov 2011 23:56:33 +0100 Subject: [Fiware-cloud] WP4 reporting In-Reply-To: References: <4EC13D9C.6080308@tid.es> <4EC14942.4090405@tid.es> Message-ID: <4EC19CA1.2060403@tid.es> Thanks a lot to everyone and particularly to David for such an effort! El 14/11/2011 22:35, David Breitgand escribi?: Miguel, Please find attached the WP4 progress report. Contributions: ----------------------------------- IBM: yes Intel: yes UPM: yes TID: yes Technicolor: pending ----------------------------------- Since I didn't have the Technicolor contribution, I compiled something myself based on the wiki and tracker. Serge, Pascal, please review and modify the Technicolor part as you see fit Everybody, please review and provide additional feedback to Miguel and Juanjo. Thanks for making this effort on such a short notice! Good night. -- 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: Miguel Carrillo To: David Breitgand/Haifa/IBM at IBMIL Cc: FERNANDO LOPEZ AGUILAR , "andrewx.edmonds at intel.com" , Dagan Gilat/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" , JUAN JOSE HIERRO SUREDA , Yaron Wolfsthal/Haifa/IBM at IBMIL Date: 14/11/2011 07:00 PM Subject: Re: WP4 reporting ________________________________ I nearly forgot. I said I was going to send a reasonable example in case it could help. Please see the reporting sent by WP7, I like it. El 14/11/2011 17:11, Miguel Carrillo escribi?: Dear all, The WP leader should be aggregating everyone's inputs and chasing up those who did not send the info. In this case, you should have requested this info from TID (Fernando, Javier or whoever). I understand the situation but please let us not change the general scenario, WPLs are responsible for this. I am personally aggregating WP1 and WP12 and I am getting texts like that. And I simply edit it as I deem it reasonable, without going to each one. I just leave a general description taking the info when it is usefuil and dismissing where it's not. I am not extreme about deleting mentions to partners, but I avoid a mere enumeration of individual partners, which is normally not a good sign (un-integrated work). Thanks Miguel El 14/11/2011 16:15, David Breitgand escribi?: Hi Fernando, I did not know about this. Is Xavier doing the aggregation work for the WP4 report? The reason I'm asking is that there was a gap in communication among the partners. Should we send our contributions for WP4 to Xavier for aggregation??? I'm kind of confused who is responsible for what. In any case, I would gladly let Xavier doing this work of aggregation. Please confirm that he is responsible for this. Concerning the content of your contribution. As Miguel specified in his instructions: "Do not provide a breakdown of what each partner has done. The description is general and presents the results as the outcome of teamwork. Punctual mentions to specific partners with specific and clearly defined tasks are allowed but avoid enumerations of partners everywhere! That is to say, you must describe the achievements of your work package as a whole, not the achievements of each partner, going one by one. " Can you please take a few minutes to slightly edit your contribution to follow this instructions? In your tasks, you start with "TID as a leader", etc. Thanks for promptly responding on the section numbers. Dear partners, please follow Fernando's example and communicate your contributions to me promptly. Thanks. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" , "andrewx.edmonds at intel.com" , MIGUEL CARRILLO PACHECO , Dagan Gilat/Haifa/IBM at IBMIL, Yaron Wolfsthal/Haifa/IBM at IBMIL, JUAN JOSE HIERRO SUREDA Date: 14/11/2011 04:57 PM Subject: Re: WP4 reporting ________________________________ Dear David, I sent this information in a previous request from Javier de Pedro, anyway I give you again. Give me some feedback if you have any problem to open it. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "01 - FI-WARE - technical activities (TID-WP4).docx" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00001..htm" deleted by David Breitgand/Haifa/IBM] [attachment "PastedGraphic-1.tiff" deleted by David Breitgand/Haifa/IBM] [attachment "ATT00002..htm" deleted by David Breitgand/Haifa/IBM] -- ---------------------------------------------------------------------- _/ _/_/ 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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[attachment "D121-FI-WARE_Project Report.doc" deleted by David Breitgand/Haifa/IBM] -- ---------------------------------------------------------------------- _/ _/_/ 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 DAVIDBR at il.ibm.com Tue Nov 15 10:38:04 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Tue, 15 Nov 2011 11:38:04 +0200 Subject: [Fiware-cloud] Detailed comments on the Cloud Backlog information available on the Wiki/Tracker In-Reply-To: <4EC163CD.9080209@tid.es> References: <4EC0FD21.6070406@tid.es> <4EC163CD.9080209@tid.es> Message-ID: Dear Juanjo, You require multiple changes to be made in a very short period of time. As you might know Alex is on the leave till Thursday. I would like to help, but I won't be able to lead this activity today and I cannot commit to completing it by the end of the day today. Does anybody of the task leaders wish to step in and lead this activity? Best. -- 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: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" Cc: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 14/11/2011 08:54 PM Subject: [Fiware-cloud] Detailed comments on the Cloud Backlog information available on the Wiki/Tracker Sent by: fiware-cloud-bounces at lists.fi-ware.eu Dear Alex and rest of the Cloud Hosting team, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB tomorrow (none of them affect the Wiki contents so that they won't affect generation of the .pdf book linked to second release of the FI-WARE Product Vision Deliverable). Despite the short time I'm giving you to react, I believe this is feasible because they are rather few and responsibility to fix them can be properly distributed so that changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). I copy the rest of WPLs and WPAs so that they can monitor comments to the different WPs. Best regards, -- Juanjo Cloud Hosting: General comments: Despite the language used for describing goals in the template defined in August for backlog entries has not been followed for some entries, it's true that Goals linked to Cloud Hosting GEs do not adapt so well to that formula, so we will keep things as they are. Some people may argue that description of goals doesn't follow the standard Agile conventions but we'll see. You have defined FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis as two WorkItems that you will carry out in order to refine the General Architecture and conduct a gap analysis. Both being linked to all GEs. That's pretty fine (and good practice). However ... Do you plan to carry out these WorkItems during Sprint 1.1.1 ? If so, you should assign the "FIWARE.Sprint.1.1.1" value to the "FI-WARE Sprint Id" field in the corresponding ticket. Resource Manager: You haven't followed the defined convention for values of the "FI-WARE Release Id" and "FI-WARE Sprint Id" field You have identified a WorkItem named as FIWARE.WorkItem.Cloud.ResourceManager.SvcMgrIntegration.InitialDesign ... Are you going to carry out this item during Sprint 1.1.1 ? The WorkItem may have been just identified but be still pending of planning ... that would be fine but wanted to double-check) There are some Stories that have been assigned a value of 1.1.2 to the Sprint Id. However, you should not plan Stories or Work Items in Sprints after the current/about-to-start sprint. This would be against Agile Principles. While we will try to "plan" Features linked to releases, this "planning" will not apply to User Story and Work Items. This is a simple change because you just need to delete value of the "FI-WARE Sprint Id" field for those User Stories or Work Items that won't fit in FI-WARE.Sprint.1.1.1 There are several Stories that are not assigned to Sprint 1.1.1. This is fine (you have identified the Stories but you have decided not to address them in Sprint 1.1.1). However, I want to double-check that you didn't simply forget to assign a value to the FI-WARE Sprint Id field. Service Manager: It has no sense to assign a User Story or a Work Item to another Sprint different that the current/about-to-start Sprint, as mentioned for the Resource Manager GE. There are Epics and Features listed in the User Stories section on the Wiki. Just place the entries in the right section. I see Epics that are assigned to a Sprint (e.g., FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.OCCIClient) ... this doesn't make sense (only User-Stories or WorkItems are carried out in a Sprint). Please fix ... I see Features that are assigned to a Sprint (e.g., FIWARE.Feature.Cloud.ServiceManager.ServiceAutoScalling.ElastRules). Features are just assigned to releases. Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? PaaS Management: Work Items do not need to be declared linked to a minor release. What is relevant to declare linked to releases are Features. On the other hand ... Shouldn't the ones being identified be linked to sprint 1.1.1 ? Object Storage: What type of entry is FIWARE.Epic.Cloud.ObjectStorage.Security.SSO. Apparently an Epic but has not been labeled as such on the tracker. Wouldn't any of the identified Features be linked to the 1st minor release ? Couldn't you plan them ? Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? Cloud Edge: Don't see the ticket on the tracker that should be linked to the FIWARE.Feature.Cloud.CloudProxy.APIFirstRelease entry. Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? Monitoring: Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? Wouldn't any of the identified Features be linked to the 1st minor release ? Couldn't you plan them ? Self-Service Interface: Tickets linked to entries declared on the Wiki haven't been created ! Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "ATT00001..txt" deleted by David Breitgand/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVIDBR at il.ibm.com Tue Nov 15 11:02:01 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Tue, 15 Nov 2011 12:02:01 +0200 Subject: [Fiware-cloud] Detailed comments on the Cloud Backlog information available on the Wiki/Tracker In-Reply-To: <4EC163CD.9080209@tid.es> References: <4EC0FD21.6070406@tid.es> <4EC163CD.9080209@tid.es> Message-ID: Hi All, Sorry if you receive this message multiple times. I had a glitch with my mail tool, so I am not sure whether you received my previous mail. Alex, is on the leave till Thursday. I will not be able to lead this activity today and cannot commit to completing these tasks by the end of the day today. Does anybody of the task leaders whish to step in and lead this? I will be happy to help to the extent possible given my constraints today. Thank you. -- 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: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" Cc: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 14/11/2011 08:54 PM Subject: [Fiware-cloud] Detailed comments on the Cloud Backlog information available on the Wiki/Tracker Sent by: fiware-cloud-bounces at lists.fi-ware.eu Dear Alex and rest of the Cloud Hosting team, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB tomorrow (none of them affect the Wiki contents so that they won't affect generation of the .pdf book linked to second release of the FI-WARE Product Vision Deliverable). Despite the short time I'm giving you to react, I believe this is feasible because they are rather few and responsibility to fix them can be properly distributed so that changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). I copy the rest of WPLs and WPAs so that they can monitor comments to the different WPs. Best regards, -- Juanjo Cloud Hosting: General comments: Despite the language used for describing goals in the template defined in August for backlog entries has not been followed for some entries, it's true that Goals linked to Cloud Hosting GEs do not adapt so well to that formula, so we will keep things as they are. Some people may argue that description of goals doesn't follow the standard Agile conventions but we'll see. You have defined FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis as two WorkItems that you will carry out in order to refine the General Architecture and conduct a gap analysis. Both being linked to all GEs. That's pretty fine (and good practice). However ... Do you plan to carry out these WorkItems during Sprint 1.1.1 ? If so, you should assign the "FIWARE.Sprint.1.1.1" value to the "FI-WARE Sprint Id" field in the corresponding ticket. Resource Manager: You haven't followed the defined convention for values of the "FI-WARE Release Id" and "FI-WARE Sprint Id" field You have identified a WorkItem named as FIWARE.WorkItem.Cloud.ResourceManager.SvcMgrIntegration.InitialDesign ... Are you going to carry out this item during Sprint 1.1.1 ? The WorkItem may have been just identified but be still pending of planning ... that would be fine but wanted to double-check) There are some Stories that have been assigned a value of 1.1.2 to the Sprint Id. However, you should not plan Stories or Work Items in Sprints after the current/about-to-start sprint. This would be against Agile Principles. While we will try to "plan" Features linked to releases, this "planning" will not apply to User Story and Work Items. This is a simple change because you just need to delete value of the "FI-WARE Sprint Id" field for those User Stories or Work Items that won't fit in FI-WARE.Sprint.1.1.1 There are several Stories that are not assigned to Sprint 1.1.1. This is fine (you have identified the Stories but you have decided not to address them in Sprint 1.1.1). However, I want to double-check that you didn't simply forget to assign a value to the FI-WARE Sprint Id field. Service Manager: It has no sense to assign a User Story or a Work Item to another Sprint different that the current/about-to-start Sprint, as mentioned for the Resource Manager GE. There are Epics and Features listed in the User Stories section on the Wiki. Just place the entries in the right section. I see Epics that are assigned to a Sprint (e.g., FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.OCCIClient) ... this doesn't make sense (only User-Stories or WorkItems are carried out in a Sprint). Please fix ... I see Features that are assigned to a Sprint (e.g., FIWARE.Feature.Cloud.ServiceManager.ServiceAutoScalling.ElastRules). Features are just assigned to releases. Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? PaaS Management: Work Items do not need to be declared linked to a minor release. What is relevant to declare linked to releases are Features. On the other hand ... Shouldn't the ones being identified be linked to sprint 1.1.1 ? Object Storage: What type of entry is FIWARE.Epic.Cloud.ObjectStorage.Security.SSO. Apparently an Epic but has not been labeled as such on the tracker. Wouldn't any of the identified Features be linked to the 1st minor release ? Couldn't you plan them ? Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? Cloud Edge: Don't see the ticket on the tracker that should be linked to the FIWARE.Feature.Cloud.CloudProxy.APIFirstRelease entry. Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? Monitoring: Do you plan only to carry out the FIWARE.WorkItem.Cloud.General.Architecture and FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? Wouldn't any of the identified Features be linked to the 1st minor release ? Couldn't you plan them ? Self-Service Interface: Tickets linked to entries declared on the Wiki haven't been created ! Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "ATT00001..txt" deleted by David Breitgand/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Nov 15 15:47:56 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 15 Nov 2011 15:47:56 +0100 Subject: [Fiware-cloud] Fwd: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) In-Reply-To: <4EC2232E.70701@tid.es> References: <4EC2232E.70701@tid.es> Message-ID: <4EC27B9C.2050504@tid.es> Hi all, Unfortunately, it seems like a number of actions I asked the different WPLs to implement didn't go through until you because the absence of Alex. Not a big deal because they were rather minor in the case of Cloud. Indeed, just one AP dealing with adding a reference to game consoles in the case of the Cloud Proxy element (see attached email and document) May someone from Technicolor deal with this comment ? As I said, I honestly believe that this is a matter of a few minutes editing the Wiki. Sorry for the short notice. I miss that Alex was not there ... Cheers, -- Juanjo -------- Original Message -------- Subject: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) Date: Tue, 15 Nov 2011 09:30:38 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We expect you have dealt with a number of APs we had identified regarding contents of the FI-WARE Product Vision in your respective chapters. Attached you will find the comments from reviewers in Word format. I have marked in red those paragraphs that should lead to some enhancement of the FI-WARE Product Vision on the Wiki. I assume that the rest may be handled through responses on your presentations during the review. As I told you yesterday, I need to know whether you have actually dealt with the APs to know when I can close and produce a .pdf book with the contents of the Wiki. I EXPECT that you return to me a response to this email ASAP (deadline 14:30) elaborating on the points in red and confirming you have made the necessary changes on the Wiki. Thanks for your effort. Best regards, -- Juanjo ________________________________ 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: Comments on FI-WARE Vision by Reviewers.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 169679 bytes Desc: not available URL: From fla at tid.es Tue Nov 15 15:59:14 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 15 Nov 2011 15:59:14 +0100 Subject: [Fiware-cloud] [FI-WARE] Update wiki & tracker Message-ID: Dear Alex, David et all, Andy and me have updated the entries in the mediawiki and tracker in order to cover the Juanjo's comments. The only thing that we have to cover now is a specific comment to Technicolor guys. Serge, could you provide the infomation that Juanjo request to you ASAP (the deadline is 17.00h) 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] ________________________________ 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 Tue Nov 15 16:35:16 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Tue, 15 Nov 2011 16:35:16 +0100 Subject: [Fiware-cloud] [FI-WARE] Update wiki & tracker In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0123414F15@MOPESMBX01.eu.thmulti.com> Fernando, I updated the tracker chapter of cloud hosting one or two hours ago in order to take into account Juanjo comments. I added two tickets, one feature and one work item. It seems to me that everything is ok now, tell me if not. I try to do my best, I am out of office since yesterday afternoon, attending the WP7 fiware meeting in Berlin. Regards, Serge From: FERNANDO LOPEZ AGUILAR [mailto:fla at tid.es] Sent: mardi 15 novembre 2011 15:59 To: David Breitgand Cc: Alex Glikson; AndrewX Edmonds; fiware-cloud at lists.fi-ware.eu; Defrance Serge Subject: [FI-WARE] Update wiki & tracker Importance: High Dear Alex, David et all, Andy and me have updated the entries in the mediawiki and tracker in order to cover the Juanjo's comments. The only thing that we have to cover now is a specific comment to Technicolor guys. Serge, could you provide the infomation that Juanjo request to you ASAP (the deadline is 17.00h) 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:image001.png at 01CCA3B4.14357430] ________________________________ 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: image001.png Type: image/png Size: 20118 bytes Desc: image001.png URL: From DAVIDBR at il.ibm.com Tue Nov 15 17:13:39 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Tue, 15 Nov 2011 18:13:39 +0200 Subject: [Fiware-cloud] [FI-WARE] Update wiki & tracker In-Reply-To: References: Message-ID: Dear Fernando, Andrew, Serge, Thank you very much for this effort! I wish I could help more today, but I had a really hectic day. -- 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: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: Alex Glikson/Haifa/IBM at IBMIL, AndrewX Edmonds , "fiware-cloud at lists.fi-ware.eu" , Defrance Serge Date: 15/11/2011 04:59 PM Subject: [FI-WARE] Update wiki & tracker Dear Alex, David et all, Andy and me have updated the entries in the mediawiki and tracker in order to cover the Juanjo's comments. The only thing that we have to cover now is a specific comment to Technicolor guys. Serge, could you provide the infomation that Juanjo request to you ASAP (the deadline is 17.00h) 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 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 Nov 15 17:17:21 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 15 Nov 2011 17:17:21 +0100 Subject: [Fiware-cloud] [FI-WARE] Minutes of the T4.5 PhC Message-ID: <7ED93EED-0563-4A10-A662-2058FA3BC16C@tid.es> Dear all, I just put into the wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/cloud/index.php/Task_4.5:_Self-service_Portal/API_and_PaaS_hosting_enablement#List_of_PhC_meetings) the document of the first PhC regarding this task. Please use this mediawiki in order to upload the information related to WP4. I think this is the beginning of a beautiful friendship... 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 Tue Nov 15 17:27:12 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Tue, 15 Nov 2011 17:27:12 +0100 Subject: [Fiware-cloud] Fwd: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) In-Reply-To: <4EC27B9C.2050504@tid.es> References: <4EC2232E.70701@tid.es> <4EC27B9C.2050504@tid.es> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0123415030@MOPESMBX01.eu.thmulti.com> Dear Juanjo, I have added the following to chapter 3.2.5.1 on the product vision chapter on the media wiki. Regards, Serge. Gaming feature support Gaming functions are well suited to cloud computing because of computing power required and multi-user aspects. However, some acceleration features may be advantageously supported in a virtual machine running on the could proxy. 3D functions may also be supported in the cloud proxy although, mainly due to cost considerations, this may only possible in some years. Lastly, cloud proxy gaming functions may also take benefit of display facilities available in the home network, as far as no video output is directly present on the cloud proxy device. From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: mardi 15 novembre 2011 15:48 To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fwd: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) Hi all, Unfortunately, it seems like a number of actions I asked the different WPLs to implement didn't go through until you because the absence of Alex. Not a big deal because they were rather minor in the case of Cloud. Indeed, just one AP dealing with adding a reference to game consoles in the case of the Cloud Proxy element (see attached email and document) May someone from Technicolor deal with this comment ? As I said, I honestly believe that this is a matter of a few minutes editing the Wiki. Sorry for the short notice. I miss that Alex was not there ... Cheers, -- Juanjo -------- Original Message -------- Subject: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) Date: Tue, 15 Nov 2011 09:30:38 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We expect you have dealt with a number of APs we had identified regarding contents of the FI-WARE Product Vision in your respective chapters. Attached you will find the comments from reviewers in Word format. I have marked in red those paragraphs that should lead to some enhancement of the FI-WARE Product Vision on the Wiki. I assume that the rest may be handled through responses on your presentations during the review. As I told you yesterday, I need to know whether you have actually dealt with the APs to know when I can close and produce a .pdf book with the contents of the Wiki. I EXPECT that you return to me a response to this email ASAP (deadline 14:30) elaborating on the points in red and confirming you have made the necessary changes on the Wiki. Thanks for your effort. Best regards, -- Juanjo ________________________________ 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 jhierro at tid.es Tue Nov 15 17:34:19 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 15 Nov 2011 17:34:19 +0100 Subject: [Fiware-cloud] Fwd: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E0123415030@MOPESMBX01.eu.thmulti.com> References: <4EC2232E.70701@tid.es> <4EC27B9C.2050504@tid.es> <453EEB4CD4162742B6EF3D3F84E88A6E0123415030@MOPESMBX01.eu.thmulti.com> Message-ID: <4EC2948B.8010505@tid.es> Perfect ! Thanks for your quick reaction ! -- Juanjo On 15/11/11 17:27, Defrance Serge wrote: Dear Juanjo, I have added the following to chapter 3.2.5.1 on the product vision chapter on the media wiki. Regards, Serge. Gaming feature support Gaming functions are well suited to cloud computing because of computing power required and multi-user aspects. However, some acceleration features may be advantageously supported in a virtual machine running on the could proxy. 3D functions may also be supported in the cloud proxy although, mainly due to cost considerations, this may only possible in some years. Lastly, cloud proxy gaming functions may also take benefit of display facilities available in the home network, as far as no video output is directly present on the cloud proxy device. From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: mardi 15 novembre 2011 15:48 To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fwd: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) Hi all, Unfortunately, it seems like a number of actions I asked the different WPLs to implement didn't go through until you because the absence of Alex. Not a big deal because they were rather minor in the case of Cloud. Indeed, just one AP dealing with adding a reference to game consoles in the case of the Cloud Proxy element (see attached email and document) May someone from Technicolor deal with this comment ? As I said, I honestly believe that this is a matter of a few minutes editing the Wiki. Sorry for the short notice. I miss that Alex was not there ... Cheers, -- Juanjo -------- Original Message -------- Subject: URGENT: Report on actions on the Wiki (FI-WARE Product Vision) Date: Tue, 15 Nov 2011 09:30:38 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We expect you have dealt with a number of APs we had identified regarding contents of the FI-WARE Product Vision in your respective chapters. Attached you will find the comments from reviewers in Word format. I have marked in red those paragraphs that should lead to some enhancement of the FI-WARE Product Vision on the Wiki. I assume that the rest may be handled through responses on your presentations during the review. As I told you yesterday, I need to know whether you have actually dealt with the APs to know when I can close and produce a .pdf book with the contents of the Wiki. I EXPECT that you return to me a response to this email ASAP (deadline 14:30) elaborating on the points in red and confirming you have made the necessary changes on the Wiki. Thanks for your effort. Best regards, -- Juanjo ________________________________ 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 fla at tid.es Wed Nov 16 18:52:23 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 16 Nov 2011 18:52:23 +0100 Subject: [Fiware-cloud] [FI-WARE] Portal API Message-ID: <60593F22-2797-4694-BE21-C166D3BEC041@tid.es> Dear all, In the last PhC of T4.5, we have a question regarding the Portal APIs. I answered that the only API in the portal would be CDMI to access directly to the Object Storage and TCloud - CIMI to access to the PaaS and IaaS SM. But I would like to confirm this decision with you. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain [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 DAVIDBR at il.ibm.com Thu Nov 17 07:45:31 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Thu, 17 Nov 2011 08:45:31 +0200 Subject: [Fiware-cloud] [FI-WARE] Portal API In-Reply-To: <60593F22-2797-4694-BE21-C166D3BEC041@tid.es> References: <60593F22-2797-4694-BE21-C166D3BEC041@tid.es> Message-ID: Hi Fernando, Just to make sure we are talking the same language, is PhC == Phone Call? What is the urgency of this issue with respect to the review deliverables we are preparing at the moment? If this does not affect the review next week, I suggest we discuss this topic at our weekly call. What do you think? -- david From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 16/11/2011 07:52 PM Subject: [Fiware-cloud] [FI-WARE] Portal API Sent by: fiware-cloud-bounces at lists.fi-ware.eu Dear all, In the last PhC of T4.5, we have a question regarding the Portal APIs. I answered that the only API in the portal would be CDMI to access directly to the Object Storage and TCloud - CIMI to access to the PaaS and IaaS SM. But I would like to confirm this decision with you. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain 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 fla at tid.es Thu Nov 17 09:35:21 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Thu, 17 Nov 2011 09:35:21 +0100 Subject: [Fiware-cloud] [FI-WARE] Portal API In-Reply-To: References: <60593F22-2797-4694-BE21-C166D3BEC041@tid.es> Message-ID: <4549AB0A-32FC-4B26-88FF-61AF55B75454@tid.es> Dear David, Yes PhC is Phone Call, sorry if I suppose that you understood it. Regarding the urgency of preparing the deliverables, well I just sent the question, you will decide when answer it, I t just was an AP (Action Point) to me in our PhC in the T4.5 Agree with you, but I supposed that it was a decision taking some months ago. Fernando 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 17/11/2011, a las 07:45, David Breitgand escribi?: Hi Fernando, Just to make sure we are talking the same language, is PhC == Phone Call? What is the urgency of this issue with respect to the review deliverables we are preparing at the moment? If this does not affect the review next week, I suggest we discuss this topic at our weekly call. What do you think? -- david From: FERNANDO LOPEZ AGUILAR > To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" > Date: 16/11/2011 07:52 PM Subject: [Fiware-cloud] [FI-WARE] Portal API Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Dear all, In the last PhC of T4.5, we have a question regarding the Portal APIs. I answered that the only API in the portal would be CDMI to access directly to the Object Storage and TCloud - CIMI to access to the PaaS and IaaS SM. But I would like to confirm this decision with you. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain ________________________________ 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 ________________________________ 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 DAVIDBR at il.ibm.com Thu Nov 17 13:27:40 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Thu, 17 Nov 2011 14:27:40 +0200 Subject: [Fiware-cloud] [FI-WARE] Portal API In-Reply-To: <4549AB0A-32FC-4B26-88FF-61AF55B75454@tid.es> References: <60593F22-2797-4694-BE21-C166D3BEC041@tid.es> <4549AB0A-32FC-4B26-88FF-61AF55B75454@tid.es> Message-ID: Fernando, I don't want to be misinterpreted. I asked you because I -- personally -- did not understand your question, the time framework, and the relative priority of this issue. That's why I suggested using a phone call (I should start using PhC acronym :) discussion. If "it was a decision taking some months ago" [sic], then I guess we should stick to the decisions we made long time ago. Since Alex is now back, I think he might wish to refer to this issue and maybe he has more detailed answers. Cheers. -- david From: FERNANDO LOPEZ AGUILAR To: David Breitgand/Haifa/IBM at IBMIL Cc: Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" , "fiware-cloud-bounces at lists.fi-ware.eu" Date: 17/11/2011 10:35 AM Subject: Re: [Fiware-cloud] [FI-WARE] Portal API Dear David, Yes PhC is Phone Call, sorry if I suppose that you understood it. Regarding the urgency of preparing the deliverables, well I just sent the question, you will decide when answer it, I t just was an AP (Action Point) to me in our PhC in the T4.5 Agree with you, but I supposed that it was a decision taking some months ago. Fernando 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 17/11/2011, a las 07:45, David Breitgand escribi?: Hi Fernando, Just to make sure we are talking the same language, is PhC == Phone Call? What is the urgency of this issue with respect to the review deliverables we are preparing at the moment? If this does not affect the review next week, I suggest we discuss this topic at our weekly call. What do you think? -- david From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 16/11/2011 07:52 PM Subject: [Fiware-cloud] [FI-WARE] Portal API Sent by: fiware-cloud-bounces at lists.fi-ware.eu Dear all, In the last PhC of T4.5, we have a question regarding the Portal APIs. I answered that the only API in the portal would be CDMI to access directly to the Object Storage and TCloud - CIMI to access to the PaaS and IaaS SM. But I would like to confirm this decision with you. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain 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 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 Sat Nov 19 22:15:11 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sat, 19 Nov 2011 23:15:11 +0200 Subject: [Fiware-cloud] Cloud chapter slides for the review Message-ID: Juanjo, all, Please, find attached the current draft of the Cloud chapter slides for the project review. Comments are welcome. Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Sat Nov 19 23:14:25 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 20 Nov 2011 00:14:25 +0200 Subject: [Fiware-cloud] Cloud chapter slides for the review In-Reply-To: References: Message-ID: ... and now with the attachment. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: Juanjo Hierro Cc: fiware-cloud at lists.fi-ware.eu, "fiware-wpl at lists.fi-ware.eu" Date: 19/11/2011 11:15 PM Subject: [Fiware-cloud] Cloud chapter slides for the review Sent by: fiware-cloud-bounces at lists.fi-ware.eu Juanjo, all, Please, find attached the current draft of the Cloud chapter slides for the project review. Comments are welcome. Thanks, Alex _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M6 Review Cloud 11-11-22 v1.ppt Type: application/octet-stream Size: 762880 bytes Desc: not available URL: From jhierro at tid.es Sun Nov 20 14:31:09 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 20 Nov 2011 14:31:09 +0100 Subject: [Fiware-cloud] Cloud chapter slides for the review In-Reply-To: References: Message-ID: <4EC9011D.3000407@tid.es> Hi Alex, Thanks. I see it rather close to final. Some comments: * Saying that "Cloud Infrastructure is the Foundation of the Core Platform" is a bit too much ... In the "FI-WARE Overall Vision" of the FI-WARE Product Vision we say that Cloud Hosting is "the fundamental layer which provides the computation, storage and network resources, upon which services are provisioned and managed" ... sounds like a bit more fair ... don't you think so ? * I believe you should skip on "Innovation Areas" because was not part of the template. However, I feel like much of its contents could go into the "Target features for the 1st Release" (note that I changed a bit the title in the last template I distributed) * Contents of the High/Lows slide may need further discussion but we can leave this for the rehearsal meeting Cheers, -- Juanjo On 19/11/11 23:14, Alex Glikson wrote: ... and now with the attachment. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: Juanjo Hierro Cc: fiware-cloud at lists.fi-ware.eu, "fiware-wpl at lists.fi-ware.eu" Date: 19/11/2011 11:15 PM Subject: [Fiware-cloud] Cloud chapter slides for the review Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Juanjo, all, Please, find attached the current draft of the Cloud chapter slides for the project review. Comments are welcome. Thanks, Alex _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From irenatr at gmail.com Mon Nov 21 14:51:25 2011 From: irenatr at gmail.com (Irena Trajkovska) Date: Mon, 21 Nov 2011 14:51:25 +0100 Subject: [Fiware-cloud] Cloud chapter slides for the review In-Reply-To: <4EC9011D.3000407@tid.es> References: <4EC9011D.3000407@tid.es> Message-ID: Hi Aleks, we have a doubt why in the following response for the reviewers, it is written that no partner has been identified for the portal and toolkit. "Some description of what consumers of the self-service interfaces should expect within the portals/APIs/toolkit is expected, but missing. APIs are described in sections describing the corresponding GEs providing the corresponding functions (IaaS, Object Storage, etc). Regarding portal/toolkit ? no partner has been identified who will provide this capability, as already mentioned in the DoW, and hence this is a candidate for an Open Call, and is not likely to be available in the 1 st release. Therefore, less focus has been made on this in the product vision. However, some capabilities should be considered to be made available for the application developer through Developer Tools." Regards, Irena On Sun, Nov 20, 2011 at 2:31 PM, Juanjo Hierro wrote: > Hi Alex, > > Thanks. I see it rather close to final. Some comments: > > - Saying that "Cloud Infrastructure is the Foundation of the Core > Platform" is a bit too much ... In the "FI-WARE Overall Vision" of the > FI-WARE Product Vision we say that Cloud Hosting is "the fundamental layer > which provides the computation, storage and network resources, upon which > services are provisioned and managed" ... sounds like a bit more fair ... > don't you think so ? > - I believe you should skip on "Innovation Areas" because was not part > of the template. However, I feel like much of its contents could go into > the "Target features for the 1st Release" (note that I changed a bit the > title in the last template I distributed) > - Contents of the High/Lows slide may need further discussion but we > can leave this for the rehearsal meeting > > Cheers, > > -- Juanjo > > > On 19/11/11 23:14, Alex Glikson wrote: > > ... and now with the attachment. > > Regards, > Alex > > > > > > From: Alex Glikson/Haifa/IBM at IBMIL > To: Juanjo Hierro > Cc: fiware-cloud at lists.fi-ware.eu, "fiware-wpl at lists.fi-ware.eu" > > Date: 19/11/2011 11:15 PM > Subject: [Fiware-cloud] Cloud chapter slides for the review > Sent by: fiware-cloud-bounces at lists.fi-ware.eu > ------------------------------ > > > > Juanjo, all, > > Please, find attached the current draft of the Cloud chapter slides for > the project review. > > Comments are welcome. > > Thanks, > Alex _______________________________________________ > Fiware-cloud mailing list > Fiware-cloud at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-cloud > > > ------------------------------ > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > 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 Mon Nov 21 16:44:11 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 21 Nov 2011 17:44:11 +0200 Subject: [Fiware-cloud] M6 review: updated Cloud slides Message-ID: Comments are welcome. Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M6 Review Cloud 11-11-22 v4.ppt Type: application/octet-stream Size: 532992 bytes Desc: not available URL: From fla at tid.es Mon Nov 21 18:56:05 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 21 Nov 2011 18:56:05 +0100 Subject: [Fiware-cloud] Cloud chapter slides for the review In-Reply-To: <4EC9011D.3000407@tid.es> References: <4EC9011D.3000407@tid.es> Message-ID: Hi Alex, Juanjo some comments. Slides 2 ? Goal: support life cycle management and composition and multi-VM workloads (services) together with provisioning of Cloud Storage containers: definition, provisioning, elasticity and QoS, etc ? An emerging DMTF IaaS API (CIMI) together with OVF plus extension is considered as the main candidate API in which we are contributing in its standard definition. * Additional capabilities include cloned of VMs, elasticity management of Services, which include management of VM, network capabilities and storage, based on defined rules, rules processing to cope with elasticity. Slides 3 * Goal: Leverage the results from 4CaaSt project together with the development of a PaaS architecture within the FI-WARE. Life management of blueprints, automatically deploy of VM with the appropriate platform and probes need to execute services. * Built on top of the IaaS SM infraestructure. * An emerging DMTF IaaS API CIMI together with OVF plus PaaS extenssion is considered also as the main candidate API. * Development target by the second year deliverable. Slides 6 * IaaS DCRM: I do not understand why we put there collectd? * Monitoring: ?Rocksteady? Is ir described in the wiki? I do not see collectd which is described in the wiki... And Drools? * Self Service and Programatic Interface: reference to Openstack Dashboard do not describe in the assets and not inclusion of Ruby on Rails * Security? Slides 8 Although, currently no partner has been identified who will responsible for building the monitoring framework, both INTEL and TID was working in the specification of it. Slides 12 * Accounting and Billing * Inter-Cloud Broker? well excuse me but i do not know if i hear it before. * Advanced Monitoring, the decision is not taking if we move to a open call or not. * Service composition tool? What does it mean? I would like to have more time to send feedback but I do not have more time due to I read the email today and I had to review. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain [cid:65E3CA3A-3DFE-41B6-8F69-2AD965EA42FA at hi.inet] El 20/11/2011, a las 14:31, Juanjo Hierro escribi?: Hi Alex, Thanks. I see it rather close to final. Some comments: * Saying that "Cloud Infrastructure is the Foundation of the Core Platform" is a bit too much ... In the "FI-WARE Overall Vision" of the FI-WARE Product Vision we say that Cloud Hosting is "the fundamental layer which provides the computation, storage and network resources, upon which services are provisioned and managed" ... sounds like a bit more fair ... don't you think so ? * I believe you should skip on "Innovation Areas" because was not part of the template. However, I feel like much of its contents could go into the "Target features for the 1st Release" (note that I changed a bit the title in the last template I distributed) * Contents of the High/Lows slide may need further discussion but we can leave this for the rehearsal meeting Cheers, -- Juanjo On 19/11/11 23:14, Alex Glikson wrote: ... and now with the attachment. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: Juanjo Hierro Cc: fiware-cloud at lists.fi-ware.eu, "fiware-wpl at lists.fi-ware.eu" Date: 19/11/2011 11:15 PM Subject: [Fiware-cloud] Cloud chapter slides for the review Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Juanjo, all, Please, find attached the current draft of the Cloud chapter slides for the project review. Comments are welcome. Thanks, Alex _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: From andrewx.edmonds at intel.com Tue Nov 22 10:54:12 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 22 Nov 2011 09:54:12 +0000 Subject: [Fiware-cloud] Mindmap of Cloud hosting Epics, Features and Stories Message-ID: <332A51FC2924EE4A8CDD5BB4BB05CE190497EC@IRSMSX101.ger.corp.intel.com> I found it a little easier to see dependencies/possible redundancies this way. You'll need xmind.net to edit. Andy ------------------------------------------------------------- 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 -------------- A non-text attachment was scrubbed... Name: WP4 Cloud Hosting.xmind Type: application/octet-stream Size: 589824 bytes Desc: WP4 Cloud Hosting.xmind URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP4CloudHosting.jpg Type: image/jpeg Size: 683807 bytes Desc: WP4CloudHosting.jpg URL: From GLIKSON at il.ibm.com Tue Nov 22 12:58:39 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 22 Nov 2011 13:58:39 +0200 Subject: [Fiware-cloud] Mindmap of Cloud hosting Epics, Features and Stories In-Reply-To: <332A51FC2924EE4A8CDD5BB4BB05CE190497EC@IRSMSX101.ger.corp.intel.com> References: <332A51FC2924EE4A8CDD5BB4BB05CE190497EC@IRSMSX101.ger.corp.intel.com> Message-ID: Looks very nice, thanks! Alex From: "Edmonds, AndrewX" To: "fiware-cloud at lists.fi-ware.eu" Date: 22/11/2011 01:21 PM Subject: [Fiware-cloud] Mindmap of Cloud hosting Epics, Features and Stories Sent by: fiware-cloud-bounces at lists.fi-ware.eu I found it a little easier to see dependencies/possible redundancies this way. You'll need xmind.net to edit. Andy ------------------------------------------------------------- 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. [attachment "WP4 Cloud Hosting.xmind" deleted by Alex Glikson/Haifa/IBM] [attachment "WP4CloudHosting.jpg" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Nov 22 13:07:09 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 22 Nov 2011 13:07:09 +0100 Subject: [Fiware-cloud] Mindmap of Cloud hosting Epics, Features and Stories Message-ID: <9E7E860E-AFAB-43C3-8795-1DCBCD648CAB@tid.es> Good job. Enviado desde mi HTC ----- Reply message ----- De: "Alex Glikson" Fecha: mar., nov. 22, 2011 12:59 Asunto: [Fiware-cloud] Mindmap of Cloud hosting Epics, Features and Stories Para: "Edmonds, AndrewX" CC: "fiware-cloud at lists.fi-ware.eu" Looks very nice, thanks! Alex From: "Edmonds, AndrewX" To: "fiware-cloud at lists.fi-ware.eu" Date: 22/11/2011 01:21 PM Subject: [Fiware-cloud] Mindmap of Cloud hosting Epics, Features and Stories Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ I found it a little easier to see dependencies/possible redundancies this way. You'll need xmind.net to edit. Andy ------------------------------------------------------------- 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. [attachment "WP4 Cloud Hosting.xmind" deleted by Alex Glikson/Haifa/IBM] [attachment "WP4CloudHosting.jpg" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Tue Nov 22 12:56:42 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 22 Nov 2011 13:56:42 +0200 Subject: [Fiware-cloud] project review Message-ID: Team, I've just finished presenting the Cloud Hosting WP to the project reviewers. It went well, no major comments or questions (except for the concern that we might end up having gaps if some of the Open Call candidates end up not being included after all). Also, our content in the wiki and tracker was used to (briefly) demonstrate the reviewers how the backlog process is supposed to work. I would like to thank everyone who worked hard on the various aspects of the project by now -- well done, and keep the good work :-) Thanks, Alex P.S. some of you might not be aware that the project review is happening today in Brussels -- hence I couldn't attend the weekly call. sorry about that. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Tue Nov 22 13:51:55 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 22 Nov 2011 13:51:55 +0100 Subject: [Fiware-cloud] project review Message-ID: <6D72F4C5-87EB-473C-AE60-A00BFA9976D7@tid.es> Good news. Now we have to wait the comments from them. Fernando Enviado desde mi HTC ----- Reply message ----- De: "Alex Glikson" Fecha: mar., nov. 22, 2011 13:07 Asunto: [Fiware-cloud] project review Para: "fiware-cloud at lists.fi-ware.eu" Team, I've just finished presenting the Cloud Hosting WP to the project reviewers. It went well, no major comments or questions (except for the concern that we might end up having gaps if some of the Open Call candidates end up not being included after all). Also, our content in the wiki and tracker was used to (briefly) demonstrate the reviewers how the backlog process is supposed to work. I would like to thank everyone who worked hard on the various aspects of the project by now -- well done, and keep the good work :-) Thanks, Alex P.S. some of you might not be aware that the project review is happening today in Brussels -- hence I couldn't attend the weekly call. sorry about that. ________________________________ 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 Nov 22 17:17:45 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 22 Nov 2011 17:17:45 +0100 Subject: [Fiware-cloud] M6 review: updated Cloud slides In-Reply-To: References: Message-ID: Dear Alex, Regarding Federation and Inter-cloud broker we could be interested to work with it, regarding monitoring we are preparing some slides about monitoring in order to show you what are our intention in this area before taking a decision about this GE. Our Intention is show them in the next meeting. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain [cid:65E3CA3A-3DFE-41B6-8F69-2AD965EA42FA at hi.inet] El 21/11/2011, a las 16:44, Alex Glikson escribi?: Comments are welcome. 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 chris.woods at intel.com Wed Nov 23 10:53:20 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 23 Nov 2011 09:53:20 +0000 Subject: [Fiware-cloud] WP4 WP7 - Overlapping Epics Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: wp4wp7overlap-study.mm Type: application/octet-stream Size: 47615 bytes Desc: wp4wp7overlap-study.mm URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP4 and WP7 Overlaps.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 29592 bytes Desc: WP4 and WP7 Overlaps.docx URL: From fla at tid.es Wed Nov 23 11:59:26 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 23 Nov 2011 11:59:26 +0100 Subject: [Fiware-cloud] [FI-WARE] Minutes of the T4.5 PhC In-Reply-To: <7ED93EED-0563-4A10-A662-2058FA3BC16C@tid.es> References: <7ED93EED-0563-4A10-A662-2058FA3BC16C@tid.es> Message-ID: Dear all, This is a reminder of our bi-weekly PhC to following by skype tomorrow from 15.00 to 17.00. The preliminary agenda can be found in the folder https://forge.fi-ware.eu/plugins/mediawiki/wiki/cloud/index.php/Task_4.5:_Self-service_Portal/API_and_PaaS_hosting_enablement#List_of_PhC_meetings Feel free to modify the agenda if you think that you could provide something to comment in the audio. Please, upload the presentations to the doc folder in the forge and links it to the mediawiki. In order that the people could read the presentations this would be uploaded today EoB. 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 15/11/2011, a las 17:17, FERNANDO LOPEZ AGUILAR escribi?: Dear all, I just put into the wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/cloud/index.php/Task_4.5:_Self-service_Portal/API_and_PaaS_hosting_enablement#List_of_PhC_meetings) the document of the first PhC regarding this task. Please use this mediawiki in order to upload the information related to WP4. I think this is the beginning of a beautiful friendship... 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 ________________________________ 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 jeanpierre.lerouzic at orange.com Wed Nov 23 11:20:59 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 23 Nov 2011 11:20:59 +0100 Subject: [Fiware-cloud] [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris and all, Thanks for the effort, it's not a small work. Here are three comments. (1) I think there is also some overlap between WP7 and WP8: * Epic Device Connectivity "As a FI-Ware application developer I need to ensure a great user experience by having access to information about and control of device connectivity" * User Profile "As connected device application user I want to access to my applications through secure and easy to use identification and authentication procedures, and with consistent privacy policies supported. * Subscriber Privacy Protection" "As a FI-Ware provider I have to ensure that users of my platform can trust the FI-Ware platform and the applications which run on and within that platform" (2) IMO there is certainly an overlap between technologies such as Openstack/Quantum or OpenSwitch in one hand and WP7.3 (NetIc) in the other hand, but not with WP7.4 (S3C). (3) OpenStack Keystone IMO is related to WP8, not WP7 as it's an identity service similar to the WP8 Identity enabler. Furthermore I think WP4 misunderstood some security or even basic management aspects when it wrote sentences like "In order to manage access and role-based rights of cloud resources (e.g. SSO, RBAC), I as the end user require an API to manipulate these aspects in a automated fashion." It's only my opinion. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Woods, Chris Envoy? : mercredi 23 novembre 2011 10:53 ? : fiware-i2nd Cc : fiware-cloud at lists.fi-ware.eu Objet : [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 Wed Nov 23 18:26:05 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 23 Nov 2011 18:26:05 +0100 Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides Message-ID: <4D896AFB-C7FB-4225-8201-EF6A3C7C9D63@tid.es> Dear all, I send you the reference of the slides for our PhC tomorrow. You can find it in the following link https://forge.fi-ware.eu/docman/view.php/14/649/%232+2011-11-24+FI-WARE+Portal+presentation.pptx See you tomorrow. 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 GLIKSON at il.ibm.com Thu Nov 24 08:29:14 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 24 Nov 2011 09:29:14 +0200 Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides In-Reply-To: <4D896AFB-C7FB-4225-8201-EF6A3C7C9D63@tid.es> References: <4D896AFB-C7FB-4225-8201-EF6A3C7C9D63@tid.es> Message-ID: Well done! Let's review the outcomes in one of our upcoming weekly meetings. Perhaps, we should launch similar parallel tracks for other tasks. Thoughts? Regards, Alex From: FERNANDO LOPEZ AGUILAR To: "fiware-cloud at lists.fi-ware.eu" Date: 23/11/2011 07:26 PM Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides Sent by: fiware-cloud-bounces at lists.fi-ware.eu Dear all, I send you the reference of the slides for our PhC tomorrow. You can find it in the following link https://forge.fi-ware.eu/docman/view.php/14/649/%232+2011-11-24+FI-WARE+Portal+presentation.pptx See you tomorrow. 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 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 Nov 24 10:27:43 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 24 Nov 2011 10:27:43 +0100 Subject: [Fiware-cloud] WP4 WP7 - Overlapping Epics In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Hi Chris, Regarding the section of your document < WP4 and WP7 overlaps > devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 Thu Nov 24 11:20:29 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Thu, 24 Nov 2011 11:20:29 +0100 Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides In-Reply-To: References: <4D896AFB-C7FB-4225-8201-EF6A3C7C9D63@tid.es> Message-ID: <82BCEAFF-15CB-46E5-95C9-A0B170A4D974@tid.es> Sure, I am thinking now in the list of APs that we have to manage in the T4.4 in order to prepare an Agenda for the next and first tentative PhC (I am thinking in the week from 12 to 13). More information will be sent soon, but comments or ideas will be welcome. 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 24/11/2011, a las 08:29, Alex Glikson escribi?: Well done! Let's review the outcomes in one of our upcoming weekly meetings. Perhaps, we should launch similar parallel tracks for other tasks. Thoughts? Regards, Alex From: FERNANDO LOPEZ AGUILAR > To: "fiware-cloud at lists.fi-ware.eu" > Date: 23/11/2011 07:26 PM Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Dear all, I send you the reference of the slides for our PhC tomorrow. You can find it in the following link https://forge.fi-ware.eu/docman/view.php/14/649/%232+2011-11-24+FI-WARE+Portal+presentation.pptx See you tomorrow. 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 ________________________________ 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 ________________________________ 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 fla at tid.es Thu Nov 24 12:00:09 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Thu, 24 Nov 2011 12:00:09 +0100 Subject: [Fiware-cloud] [FI-WARE] Selection of our bi-weekly T4.4 PhC Message-ID: Dear all, Please fill this doodle in order to select the schedule of our tentative T4.4 PhC. http://www.doodle.com/prbrtusi5u6bd8kv 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] ________________________________ 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 Nov 24 12:24:51 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 24 Nov 2011 12:24:51 +0100 Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides In-Reply-To: References: <4D896AFB-C7FB-4225-8201-EF6A3C7C9D63@tid.es> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01237E6CC6@MOPESMBX01.eu.thmulti.com> Hi Alex, For what regards T4.3, we have not yet planned any phone call yet. Do you still plan to have regular ConfCall at the Work package level ? 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 24 novembre 2011 08:29 To: FERNANDO LOPEZ AGUILAR; fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides Well done! Let's review the outcomes in one of our upcoming weekly meetings. Perhaps, we should launch similar parallel tracks for other tasks. Thoughts? Regards, Alex From: FERNANDO LOPEZ AGUILAR To: "fiware-cloud at lists.fi-ware.eu" Date: 23/11/2011 07:26 PM Subject: [Fiware-cloud] [FI-WARE] T4.5 Portal Slides Sent by: fiware-cloud-bounces at lists.fi-ware.eu ________________________________ Dear all, I send you the reference of the slides for our PhC tomorrow. You can find it in the following link https://forge.fi-ware.eu/docman/view.php/14/649/%232+2011-11-24+FI-WARE+Portal+presentation.pptx See you tomorrow. 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 ________________________________ 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 fla at tid.es Thu Nov 24 14:56:38 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Thu, 24 Nov 2011 14:56:38 +0100 Subject: [Fiware-cloud] [FI-WARE.Cloud.T4.5] Reminder of our bi-weekly PhC Message-ID: <59BBF35A-9520-4725-91DC-7A1C7A4264EE@tid.es> Dear all, This is a reminder of our bi-weekly PhC using skype. Please connect to http://sketchpad.cc/fZ7prhkYwM BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain [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 chris.woods at intel.com Thu Nov 24 16:49:21 2011 From: chris.woods at intel.com (Woods, Chris) Date: Thu, 24 Nov 2011 15:49:21 +0000 Subject: [Fiware-cloud] WP4 WP7 - Overlapping Epics In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B39585F@irsmsx503.ger.corp.intel.com> Hi Serge, + Adding Wolfgang Great feedback! - Could you update the document on the Forge site(Wp4 and wp7 overlaps.docx), to remove any erroneous overlaps wrt cloud edge? I would appreciate your insights on the following questions - I'm not sure I completely understand your thinking especially on the security issues. Question: What security mechanism will the cloud proxy apply to ensure that 3rd party code running on the proxy doesn't access resources for which it does not have permission? e.g. how does the developer of a proxy application signal that the proxy application needs access to users shared hard drives? How does the user (consumer) accept this request? OR user's remote control device? What happens if the app turns out to be bad? How does the user (consumer or a network operator) black list the app or limit it's capabilities? Question: Is there an overlap with RBAC? Or Security.Network? Question: Will the developer of the could proxy need to learn a new security framework for the proxy? Question: Can the developer of the could proxy use the same API and security structure used in the cloud? I see large overlaps across Cloud Proxy, CDI, WP4, and WP8 on these topics? Having a unified vision for security would be compelling from a security POV (presenting a unified security interface), from a developer adoption and convince POV, and from a resources POV, having a streamlined set of security requirements will aid development time. Chris From: Defrance Serge [mailto:serge.defrance at technicolor.com] Sent: Thursday, November 24, 2011 9:28 AM To: Woods, Chris; fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: RE: WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document < WP4 and WP7 overlaps > devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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. ------------------------------------------------------------- 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 serge.defrance at technicolor.com Thu Nov 24 17:51:22 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 24 Nov 2011 17:51:22 +0100 Subject: [Fiware-cloud] WP4 WP7 - Overlapping Epics In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B39585F@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> <187F4CC97FD0B6488FAE608A8038FF143B39585F@irsmsx503.ger.corp.intel.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01237E72BB@MOPESMBX01.eu.thmulti.com> Chris, I propose to remove : - for epic < Home system Modelling >, all epics related to < Cloud.ResourceManager >, - for epic "Other Drivers", the three epics related to "Cloud.CloudProxy". I am not surprised that you are not sure to understand my thinking on security issues. Neither do I ! In fact, security issues are still very unclear for me and, if I agree with the questions you've mentioned, I must admit that presently I almost have no answer. What I can say, is that when receiving a piece of code from the cloud, the cloud proxy should be able to check via a certificate the originator. In addition, requirements in term of home resources access have also to be given (by the originator to the cloud proxy). Exact mechanisms for these operations, I don't know yet. I also agree that they are certainly overlaps on these topics inside our WP (between CDI and Cloud Edge) and with WP8 and possibly WP4. Having a unified vision for security is certainly an objective for us. Serge. From: Woods, Chris [mailto:chris.woods at intel.com] Sent: jeudi 24 novembre 2011 16:49 To: Defrance Serge; fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu; Wolfgang.Steigerwald at telekom.de Subject: RE: WP4 WP7 - Overlapping Epics Hi Serge, + Adding Wolfgang Great feedback! - Could you update the document on the Forge site(Wp4 and wp7 overlaps.docx), to remove any erroneous overlaps wrt cloud edge? I would appreciate your insights on the following questions - I'm not sure I completely understand your thinking especially on the security issues. Question: What security mechanism will the cloud proxy apply to ensure that 3rd party code running on the proxy doesn't access resources for which it does not have permission? e.g. how does the developer of a proxy application signal that the proxy application needs access to users shared hard drives? How does the user (consumer) accept this request? OR user's remote control device? What happens if the app turns out to be bad? How does the user (consumer or a network operator) black list the app or limit it's capabilities? Question: Is there an overlap with RBAC? Or Security.Network? Question: Will the developer of the could proxy need to learn a new security framework for the proxy? Question: Can the developer of the could proxy use the same API and security structure used in the cloud? I see large overlaps across Cloud Proxy, CDI, WP4, and WP8 on these topics? Having a unified vision for security would be compelling from a security POV (presenting a unified security interface), from a developer adoption and convince POV, and from a resources POV, having a streamlined set of security requirements will aid development time. Chris From: Defrance Serge [mailto:serge.defrance at technicolor.com] Sent: Thursday, November 24, 2011 9:28 AM To: Woods, Chris; fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: RE: WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document < WP4 and WP7 overlaps > devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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. ------------------------------------------------------------- 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 GLIKSON at il.ibm.com Fri Nov 25 09:06:37 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 25 Nov 2011 10:06:37 +0200 Subject: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET Message-ID: Team, We are going to hold a virtual face-to-face meeting (i.e., all-day conference call + web conference) on December 1st, between 10am and 6pm CET. Tentative agenda: - walk-through of an end-to-end scenario of provisioning, monitoring and policy-based auto-scaling of a composite service comprising a multi-tier application - discuss workplan towards demonstrating the above scenario by the end of year-one Call-in numbers are at https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=5546993&accessNumber=1809417783 Participant Code: 5546993 Web conference URL: http://www.ibm.com/collaboration/meeting/join?id=1131085 Please, let me know whether you plan to attend. Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.defrance at technicolor.com Fri Nov 25 14:00:55 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Fri, 25 Nov 2011 14:00:55 +0100 Subject: [Fiware-cloud] [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E012833D63A@MOPESMBX01.eu.thmulti.com> Hi Jean Pierre, The cloud proxy is a device located at the boundary between the private home network and the cloud (public network). It may offer assistance to home devices to access cloud services (not mandatory, home devices can still directly access to cloud services), like data caching when uploading a big amount of data. The cloud proxy is unique, WP7 "cloud proxy" and WP4 "cloud proxy" is the same device. The reason of the split between WP4 and WP7 is that some functions of the cloud proxy may more relate to - one hand to cloud functions like the API (and associated functional in the cloud proxy) used by a cloud application to authenticate to the cloud proxy and download code to be executed on the cloud proxy (WP4), - and on the other hand to network and devices interfaces like a kind of a SDK that the downloaded code may use to access home network resources (resources located in the home as storage or simple devices). Presently, we (Technicolor) do not consider the cloud proxy as part of the cloud, but more as a particular device (a super gateway) which is almost always present (cloud application may rely on) and which offer standardized APIs. Virtualisation on the cloud proxy is mainly for the sake of isolation between processes which are executed on it, as far as some code may be downloaded from the cloud from more or less trustworthy sources. I hope this help to a better understanding. However, I may have missed some of your points. Cheers, Serge. From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: vendredi 25 novembre 2011 10:35 To: Defrance Serge; chris.woods at intel.com Cc: fiware-cloud at lists.fi-ware.eu; fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hi all, Serge, If I understand correctly the cloud proxy concept, it means that: ? From the point of view of the home devices, all services are accessed through the cloud proxy which unifies the services interfaces (hence the name cloud proxy). ? From the point of view of services the cloud proxy, doesn't unify the home devices. At a technical level, I understood during the WP7 session in Turin that the Cloud proxy, is a kind of bare metal OS that executes applications in the form of light VMs. Cloud applications would download those light VMs on the bare metal OS which would run them. The rationale being that broadband connection may be sometimes slow and it's better to execute applications locally. I think that in WP4 EPICS you use the word "network" more with the meaning of a computer network interface (Ethernet and so on), than a Telecom network. This is IMO well described in one of WP4 EPIC: FIWARE.Epic.Cloud.ResourceManager.Network, especially the mention of L2/L3. But if we decide than computers are not permanently connected through their network interfaces (which is suggested by the whole concept of a "cloud proxy"), the difference between a computer network and a telecom network is quite blurred IMO as you will have to introduce connection protocols (like PPP over xyz). It seems to me that there is in WP4 a collision course between two network notions. My own understanding of OpenStack Quantum is that it deals with virtual NIC which in my opinion doesn't align well with the "cloud proxy" concept which is more about application running on devices (but not as native applications). If the WP4 "cloud proxy" is it about virtualized local applications then what Chris suggested as overlap seems to me correct, or the WP4 "cloud proxy" is about virtualized NICs (L2/L3) which is a different topic where I agree there is not much overlap with WP7 network API EPICS. If my understanding happens to be correct I think it would be nice to: ? Have a project agreement on vocabulary and concepts (what is a network?) ? Have a project policy to reduce the usage of overloaded concepts (for ex: "user", when there are many kind of users as you rightly suggested). ? Try to clarify what the "cloud proxy" is about (is it about virtualized local applications or is it about virtualized NIC?) Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Defrance Serge Envoy? : jeudi 24 novembre 2011 10:28 ? : Woods, Chris; fiware-i2nd Cc : fiware-cloud at lists.fi-ware.eu Objet : Re: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document ? WP4 and WP7 overlaps ? devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 jeanpierre.lerouzic at orange.com Fri Nov 25 10:34:39 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Fri, 25 Nov 2011 10:34:39 +0100 Subject: [Fiware-cloud] [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Message-ID: Hi all, Serge, If I understand correctly the cloud proxy concept, it means that: ? From the point of view of the home devices, all services are accessed through the cloud proxy which unifies the services interfaces (hence the name cloud proxy). ? From the point of view of services the cloud proxy, doesn't unify the home devices. At a technical level, I understood during the WP7 session in Turin that the Cloud proxy, is a kind of bare metal OS that executes applications in the form of light VMs. Cloud applications would download those light VMs on the bare metal OS which would run them. The rationale being that broadband connection may be sometimes slow and it's better to execute applications locally. I think that in WP4 EPICS you use the word "network" more with the meaning of a computer network interface (Ethernet and so on), than a Telecom network. This is IMO well described in one of WP4 EPIC: FIWARE.Epic.Cloud.ResourceManager.Network , especially the mention of L2/L3. But if we decide than computers are not permanently connected through their network interfaces (which is suggested by the whole concept of a "cloud proxy"), the difference between a computer network and a telecom network is quite blurred IMO as you will have to introduce connection protocols (like PPP over xyz). It seems to me that there is in WP4 a collision course between two network notions. My own understanding of OpenStack Quantum is that it deals with virtual NIC which in my opinion doesn't align well with the "cloud proxy" concept which is more about application running on devices (but not as native applications). If the WP4 "cloud proxy" is it about virtualized local applications then what Chris suggested as overlap seems to me correct, or the WP4 "cloud proxy" is about virtualized NICs (L2/L3) which is a different topic where I agree there is not much overlap with WP7 network API EPICS. If my understanding happens to be correct I think it would be nice to: ? Have a project agreement on vocabulary and concepts (what is a network?) ? Have a project policy to reduce the usage of overloaded concepts (for ex: "user", when there are many kind of users as you rightly suggested). ? Try to clarify what the "cloud proxy" is about (is it about virtualized local applications or is it about virtualized NIC?) Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Defrance Serge Envoy? : jeudi 24 novembre 2011 10:28 ? : Woods, Chris; fiware-i2nd Cc : fiware-cloud at lists.fi-ware.eu Objet : Re: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document ? WP4 and WP7 overlaps ? devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 jsalvachua at dit.upm.es Fri Nov 25 11:16:50 2011 From: jsalvachua at dit.upm.es (Joaquin Salvachua) Date: Fri, 25 Nov 2011 11:16:50 +0100 Subject: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET In-Reply-To: References: Message-ID: Hello, We will attend, but due to some lectures i have give this day i will be in an out. Best Regards Joaqu?n El 25/11/2011, a las 09:06, Alex Glikson escribi?: > Team, > > We are going to hold a virtual face-to-face meeting (i.e., all-day conference call + web conference) on December 1st, between 10am and 6pm CET. > > Tentative agenda: > - walk-through of an end-to-end scenario of provisioning, monitoring and policy-based auto-scaling of a composite service comprising a multi-tier application > - discuss workplan towards demonstrating the above scenario by the end of year-one > > Call-in numbers are at https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=5546993&accessNumber=1809417783 > Participant Code: 5546993 > Web conference URL: http://www.ibm.com/collaboration/meeting/join?id=1131085 > > Please, let me know whether you plan to attend. > > Thanks, > Alex > _______________________________________________ > Fiware-cloud mailing list > Fiware-cloud at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Fri Nov 25 10:55:44 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Fri, 25 Nov 2011 10:55:44 +0100 Subject: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET In-Reply-To: References: Message-ID: <27657D59-78AC-4540-BFDE-5912CD462DC7@tid.es> Well That is wonderful, then to obtain a super-productive day I suggest that from now till next week we prepare some slides about the open questions. In my case, I will try to prepare several related to monitoring architecture that we use, how to resolve the federation and Inter-cloud broker with Claudia, together with other one in which I describe the extension of OVF that we are using if a had time for it. But I suggest to have also presentations about how to manage the policy-driven local and cross data centre optimization, the description of services to de deployed in the Cloud-Proxy, and so on. In fact those will be the Action Points (AP) that I wanted to fix for the PhC of T4.4 (except the part of Cloud Proxy that is more related to all WP4). Regarding the Task 4.5 we can provide a summarize about our current discussion and work in progress. I suggest that we do the same for all the Task involve in this WP. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain [cid:65E3CA3A-3DFE-41B6-8F69-2AD965EA42FA at hi.inet] El 25/11/2011, a las 09:06, Alex Glikson escribi?: Team, We are going to hold a virtual face-to-face meeting (i.e., all-day conference call + web conference) on December 1st, between 10am and 6pm CET. Tentative agenda: - walk-through of an end-to-end scenario of provisioning, monitoring and policy-based auto-scaling of a composite service comprising a multi-tier application - discuss workplan towards demonstrating the above scenario by the end of year-one Call-in numbers are at https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=5546993&accessNumber=1809417783 Participant Code: 5546993 Web conference URL: http://www.ibm.com/collaboration/meeting/join?id=1131085 Please, let me know whether you plan to attend. Thanks, 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 GLIKSON at il.ibm.com Fri Nov 25 16:24:53 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 25 Nov 2011 17:24:53 +0200 Subject: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET In-Reply-To: <27657D59-78AC-4540-BFDE-5912CD462DC7@tid.es> References: <27657D59-78AC-4540-BFDE-5912CD462DC7@tid.es> Message-ID: Sure, doing some preparation can be helpful. Regarding the scope -- I would really like to focus on a relatively simple scenario (like the one I've outlined in the suggested agenda). Being agile, we shouldn't try addressing all the scenarios at once. In particular, I suggest leaving cross-DC, inter-cloud and cloud edge aspects to another meeting. Regarding status -- we can use the weekly slot on Tuesday for that (as well as to discuss the agenda for the vF2F in more detail). Regards, Alex From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 25/11/2011 05:12 PM Subject: Re: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET Well That is wonderful, then to obtain a super-productive day I suggest that from now till next week we prepare some slides about the open questions. In my case, I will try to prepare several related to monitoring architecture that we use, how to resolve the federation and Inter-cloud broker with Claudia, together with other one in which I describe the extension of OVF that we are using if a had time for it. But I suggest to have also presentations about how to manage the policy-driven local and cross data centre optimization, the description of services to de deployed in the Cloud-Proxy, and so on. In fact those will be the Action Points (AP) that I wanted to fix for the PhC of T4.4 (except the part of Cloud Proxy that is more related to all WP4). Regarding the Task 4.5 we can provide a summarize about our current discussion and work in progress. I suggest that we do the same for all the Task involve in this WP. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain El 25/11/2011, a las 09:06, Alex Glikson escribi?: Team, We are going to hold a virtual face-to-face meeting (i.e., all-day conference call + web conference) on December 1st, between 10am and 6pm CET. Tentative agenda: - walk-through of an end-to-end scenario of provisioning, monitoring and policy-based auto-scaling of a composite service comprising a multi-tier application - discuss workplan towards demonstrating the above scenario by the end of year-one Call-in numbers are at https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=5546993&accessNumber=1809417783 Participant Code: 5546993 Web conference URL: http://www.ibm.com/collaboration/meeting/join?id=1131085 Please, let me know whether you plan to attend. Thanks, 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: From serge.defrance at technicolor.com Mon Nov 28 13:30:11 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Mon, 28 Nov 2011 13:30:11 +0100 Subject: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET In-Reply-To: References: <27657D59-78AC-4540-BFDE-5912CD462DC7@tid.es> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0136C13456@MOPESMBX01.eu.thmulti.com> Alex, Could you please send me back the coordinates for tomorrow conf call. Note that I do not have the possibility to run skype (internal safety rules). Thanks, 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: vendredi 25 novembre 2011 16:25 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET Sure, doing some preparation can be helpful. Regarding the scope -- I would really like to focus on a relatively simple scenario (like the one I've outlined in the suggested agenda). Being agile, we shouldn't try addressing all the scenarios at once. In particular, I suggest leaving cross-DC, inter-cloud and cloud edge aspects to another meeting. Regarding status -- we can use the weekly slot on Tuesday for that (as well as to discuss the agenda for the vF2F in more detail). Regards, Alex From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 25/11/2011 05:12 PM Subject: Re: [Fiware-cloud] virtual F2F on Resource Management and Service Management on December 1st, 10am-6pm CET ________________________________ Well That is wonderful, then to obtain a super-productive day I suggest that from now till next week we prepare some slides about the open questions. In my case, I will try to prepare several related to monitoring architecture that we use, how to resolve the federation and Inter-cloud broker with Claudia, together with other one in which I describe the extension of OVF that we are using if a had time for it. But I suggest to have also presentations about how to manage the policy-driven local and cross data centre optimization, the description of services to de deployed in the Cloud-Proxy, and so on. In fact those will be the Action Points (AP) that I wanted to fix for the PhC of T4.4 (except the part of Cloud Proxy that is more related to all WP4). Regarding the Task 4.5 we can provide a summarize about our current discussion and work in progress. I suggest that we do the same for all the Task involve in this WP. BR, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain El 25/11/2011, a las 09:06, Alex Glikson escribi?: Team, We are going to hold a virtual face-to-face meeting (i.e., all-day conference call + web conference) on December 1st, between 10am and 6pm CET. Tentative agenda: - walk-through of an end-to-end scenario of provisioning, monitoring and policy-based auto-scaling of a composite service comprising a multi-tier application - discuss workplan towards demonstrating the above scenario by the end of year-one Call-in numbers are at https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=5546993&accessNumber=1809417783 Participant Code: 5546993 Web conference URL: http://www.ibm.com/collaboration/meeting/join?id=1131085 Please, let me know whether you plan to attend. Thanks, 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: From GLIKSON at il.ibm.com Tue Nov 29 18:27:14 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 29 Nov 2011 19:27:14 +0200 Subject: [Fiware-cloud] 29/11 weekly call -- minutes Message-ID: Comments are welcome. Attendees: IBM (Alex, David), Intel (Andy), TID (Fernando), Technicolor (Serge) Agenda: 1st project review last week 1st sprint wrap-up and 2nd sprint planning Expectations towards the vF2F on Thursday Minutes: The project review last week went well, focusing on overall project plans, the way to make impact on the industry, collaboration with UC projects, etc. We are on track with most of the user stories and work items planned for sprint 1.1.1. Few will continue into 1.1.2. Having the second sprint end at the end of December is an issue due to holidays. Action Item [Alex]: follow up with Juanjo, report back to the team ASAP We agreed that by our next week's weekly call we will 1) update the status in tracker of stories assigned to sprint 1.1.1, and 2) assign stories/work items for the following sprint, 1.1.2. Action Item [Task Leads, by December 5th]: update stories in tracker associated with sprints 1.1.1 and 1.1.2 We need to document the outcomes of the user stories/work items pursued during the current sprint. It was agreed to use our project private Wiki for that, and add link from the corresponding tracker item. Action Item [Task Leads, by December 5th]: create a page in the private wiki for each story/work items assigned to sprint 1.1.1 or 1.1.2, document the results for stories which have been completed, as well as expected outcomes ('acceptance criteria') for stories being scheduled for sprint 1.1.2. Add an additional link to the "URL" field in the tracker. Action Item [Alex]: create main page for the private wiki, with some hierarchy (note: should not be a prereq for completing the previous TODO) We need to decide what level of support for Object Storage should be included in the first major release (this might influence other things we might or might not be able to deliver). Action Item [Alex]: check whether UC projects express any particular interest in Object Storage, or any of its specific features. Action Item [Alex]: Report to the team on the progress/outcomes of reviewing the tickets submitted by UC projects. On Thursday, the main focus will be on scenarios across SM and RM, interfaces between them, etc. Mandatory for people involved in those two GEs, optional for everyone else. Action Item [Alex]: summary of the main outcomes, to be shared with the rest of the team (e.g., during our next weekly meeting) We need to schedule a meeting to review the proposed architecture for Cloud Edge, including an initial take on the life cycle scenario. Action Item [Serge]: come back with the earliest possible date to conduct such a review (even a preliminary one, during December if possible). -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Nov 30 13:34:15 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 30 Nov 2011 13:34:15 +0100 Subject: [Fiware-cloud] Need your help: vote for a submission from FI-WARE Message-ID: <4ED622C7.4030905@tid.es> Dear all, Acting on behalf of FI-WARE, Thierry Nagellen has just submitted a topic for workshop in the Future Internet Assembly to be celebrated in Aalborg. This topic could have the FI PPP as sponsor and we should have technical presentations (from FI-Ware partners but also from other contributors as Smart Santander or IoT-A projects) and some new Use Cases to improve the requirements picture We need your support to get there and there is very little time left. We would appreciate it if you could go to this link, login with a gmail user and vote if you like it: http://www.future-internet.eu/home/shape-fia.html?modSeries=111dab&modTopic=40&modSubmission=5c4fe7 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 From GLIKSON at il.ibm.com Wed Nov 30 16:53:29 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 30 Nov 2011 17:53:29 +0200 Subject: [Fiware-cloud] Fw: [Fiware-wpl] IMPORTANT: Approach for Architecture Specification Deliverable Message-ID: Please, see below an email from Juanjo elaborating on guidelines for the month 9 (January) deliverable. Clearly, we have lots to do (and to discuss) in order to get to this level of details for each of the GEs. Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 30/11/2011 05:49 PM ----- From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 30/11/2011 04:39 PM Subject: [Fiware-wpl] IMPORTANT: Approach for Architecture Specification Deliverable Sent by: fiware-wpl-bounces at lists.fi-ware.eu Hi all, As you know, we have to start working on the Architecture Specifications, which is one of the deliverables that is due in month 9, that is, end of January. My intention is to adopt a pragmatic approach, trying to generate something that can be integrated as part of the GE Open Specifications that we have to produce by month 12. My vision is that all GE Open Specifications should start with a chapter where an overview of the envisioned Architecture for the GE is described. While style would be narrative, the description should be enough concrete, i.e., formulated over actual data type, interface and operation names and elaborating on the base interaction scenarios involving the different entities exporting the defined interfaces. Then, after that chapter, the detailed specification of all data types and interfaces with their operations, are provided (this including signature of operations and accurate description of expected behaviour linked to operations) Then, the Architecture Specification deliverable would be just the result of developing this overview chapter. But nothing better than an example, so let me use one taken from OMG's set of CORBA Services Specifications. Along my many years involved in different standardization efforts, I have found that OMG CORBA Service specs are rather comprehensive and close to what programmers (our ultimate customers!) love to see. Please find enclosed the CORBA Event Service Specifications. What I would then select as the Architecture description are the contents of the following sections: The whole chapter 1 Section 2.2 and 2.4 (which some people may have argued should have been included in chapter 1 :-) Note that anyone who reads the mentioned sections would get a CLEAR picture of what is the Architecture of the service and what are going to be the entities and interfaces/operations that will be supported in a compliant implementation. The conceptual and programming model would be also rather clear from a programmer's perspective. Therefore, rather valuable information for an application developer perspective which is what really should matter to us. A side benefit is that what will remain as pending regarding GE Open Specifications will be less, that is, the detailed specification of data types and interfaces/operations. One thing that we will have to define is the set of conventions that we should all follow whenever we need to draw any figure, like figures 1-x or 2-x. For this, Thomas and me will come soon to you with a proposal in short time. Please take your time to analyze this carefully and formulate any question you may have. From now on, I assume that you will start planning activities in Sprint 2 and 3 dealing with development of these specifications within each of your chapters. This may well take the form of Work Items in the tracker. Best regards, -- Juanjo 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Event Service Specification 04-10-02.pdf Type: application/octet-stream Size: 515254 bytes Desc: not available URL: