From GLIKSON at il.ibm.com Fri May 13 15:46:28 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 13 May 2011 16:46:28 +0300 Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff Message-ID: I have started uploading kickoff materials to http://forge.fi-ware.eu/docman/index.php?group_id=14&selected_doc_group_id=12&language_id=1 (there are some technical issues, though -- seems that it is impossible for now to upload files larger than 2MB). Please, complete the instructions below to register, and let me know. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 13/05/2011 04:15 PM ----- From: Juanjo Hierro To: fiware at lists.fi-ware.eu Date: 13/05/2011 01:34 PM Subject: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff Sent by: fiware-bounces at lists.fi-ware.eu Hi all, This email is to explain you what the are the next steps you should follow to be able to start using the tools for sharing documents, etc. The forge infrastructure associated to the overall FI-WARE collaborative infrastructure has already been set up. This is currently based on FusionForge. FusionForge will provide the basic tool for uploading/publish/downloading documents and attach URLs to them. Here it is the list of steps that we will follow to have everything ready. 1. Registration as users of FusionForge This is pretty simple. You just have to go to: http://forge.fi-ware.eu/ then click on "New Account" in the upper right corner It should drive you to a screen where you will assign yourself a nickname. It should be valid UNIX login name, so that "." are not allowed. I would suggest using "_" instead. You have to fill a form and after doing so, click "Register". Once we do this, you have to check your email (you should provide it in the form) and then complete registration. WPLs are entitled to ask people working in their WPs to perform this step as soon as possible. Please note that maybe not all people are registered in fiware at lists.fi-ware.eu so you should forward this message also to your lists with any other specific instruction you may want to add. 2. Give Admin privileges to WPLs All WPs have a "project" in Fussion Forge. You can already see them listed at: http://forge.fi-ware.eu/ on the right bottom corner under section "Recently Registered Projects" Once WPLs have registered them as users in the Forge, they should send me an email informing about this. Then I will register them as Admin users in the project corresponding to the WP they lead. 3. Give access to partners in each of the WPLs Once WPLs have admin privileges, they should take care of adding the users in FusionForge to their projects. Doing this is also easy. Once step 2 has been completed and you login as users in FusionForge, you may click on your project. Then, you should click on the Admin Tab and then click on the "Users" menu option right below the Tab. It would then allow you to add users to your project. You should ask people working in your WP to let you know what user nicknames they have choosen in FusionForge (although I guess you may easily find them using the "Add Users From List" option. Note that you have to decide what privileges you assign users in your project. You may add more Admins or assign it that of a Senior Developer or Doc Writer, I would suggest. 4. Sharing documents Once you perform the steps above, it should be quite easy to share documents. I will send an email giving a brief tutorial on this. So, please, start performing steps 1 and 2 and make it as quickly as you can so that we can have everything setup asap. I hope you are not experiencing any problem with the mailing lists so far. But I don't see movement in some mailing lists so I'm a bit worried. Please send us any feedback you may have to fiware-support at lists.fi-ware.eu 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 [attachment "jhierro.vcf" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware From fla at tid.es Fri May 13 15:58:30 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Fri, 13 May 2011 15:58:30 +0200 Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff In-Reply-To: References: Message-ID: <8EE61BA0CAEDBD4E9DA928D1206463D2A184EBE6CA@EXCLU2K7.hi.inet> Dear Alex, My user is flopez, I think that you have to add us in the list of users (Admin tag...) BR, Fernando.- -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: viernes, 13 de mayo de 2011 15:46 To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff I have started uploading kickoff materials to http://forge.fi-ware.eu/docman/index.php?group_id=14&selected_doc_group_id=12&language_id=1 (there are some technical issues, though -- seems that it is impossible for now to upload files larger than 2MB). Please, complete the instructions below to register, and let me know. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 13/05/2011 04:15 PM ----- From: Juanjo Hierro To: fiware at lists.fi-ware.eu Date: 13/05/2011 01:34 PM Subject: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff Sent by: fiware-bounces at lists.fi-ware.eu Hi all, This email is to explain you what the are the next steps you should follow to be able to start using the tools for sharing documents, etc. The forge infrastructure associated to the overall FI-WARE collaborative infrastructure has already been set up. This is currently based on FusionForge. FusionForge will provide the basic tool for uploading/publish/downloading documents and attach URLs to them. Here it is the list of steps that we will follow to have everything ready. 1. Registration as users of FusionForge This is pretty simple. You just have to go to: http://forge.fi-ware.eu/ then click on "New Account" in the upper right corner It should drive you to a screen where you will assign yourself a nickname. It should be valid UNIX login name, so that "." are not allowed. I would suggest using "_" instead. You have to fill a form and after doing so, click "Register". Once we do this, you have to check your email (you should provide it in the form) and then complete registration. WPLs are entitled to ask people working in their WPs to perform this step as soon as possible. Please note that maybe not all people are registered in fiware at lists.fi-ware.eu so you should forward this message also to your lists with any other specific instruction you may want to add. 2. Give Admin privileges to WPLs All WPs have a "project" in Fussion Forge. You can already see them listed at: http://forge.fi-ware.eu/ on the right bottom corner under section "Recently Registered Projects" Once WPLs have registered them as users in the Forge, they should send me an email informing about this. Then I will register them as Admin users in the project corresponding to the WP they lead. 3. Give access to partners in each of the WPLs Once WPLs have admin privileges, they should take care of adding the users in FusionForge to their projects. Doing this is also easy. Once step 2 has been completed and you login as users in FusionForge, you may click on your project. Then, you should click on the Admin Tab and then click on the "Users" menu option right below the Tab. It would then allow you to add users to your project. You should ask people working in your WP to let you know what user nicknames they have choosen in FusionForge (although I guess you may easily find them using the "Add Users From List" option. Note that you have to decide what privileges you assign users in your project. You may add more Admins or assign it that of a Senior Developer or Doc Writer, I would suggest. 4. Sharing documents Once you perform the steps above, it should be quite easy to share documents. I will send an email giving a brief tutorial on this. So, please, start performing steps 1 and 2 and make it as quickly as you can so that we can have everything setup asap. I hope you are not experiencing any problem with the mailing lists so far. But I don't see movement in some mailing lists so I'm a bit worried. Please send us any feedback you may have to fiware-support at lists.fi-ware.eu 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 [attachment "jhierro.vcf" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ 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 andrewx.edmonds at intel.com Fri May 13 16:00:37 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Fri, 13 May 2011 15:00:37 +0100 Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff In-Reply-To: References: Message-ID: I've added the slides from Intel... Andy -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: Friday, May 13, 2011 2:46 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff I have started uploading kickoff materials to http://forge.fi-ware.eu/docman/index.php?group_id=14&selected_doc_group_id=1 2&language_id=1 (there are some technical issues, though -- seems that it is impossible for now to upload files larger than 2MB). Please, complete the instructions below to register, and let me know. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 13/05/2011 04:15 PM ----- From: Juanjo Hierro To: fiware at lists.fi-ware.eu Date: 13/05/2011 01:34 PM Subject: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff Sent by: fiware-bounces at lists.fi-ware.eu Hi all, This email is to explain you what the are the next steps you should follow to be able to start using the tools for sharing documents, etc. The forge infrastructure associated to the overall FI-WARE collaborative infrastructure has already been set up. This is currently based on FusionForge. FusionForge will provide the basic tool for uploading/publish/downloading documents and attach URLs to them. Here it is the list of steps that we will follow to have everything ready. 1. Registration as users of FusionForge This is pretty simple. You just have to go to: http://forge.fi-ware.eu/ then click on "New Account" in the upper right corner It should drive you to a screen where you will assign yourself a nickname. It should be valid UNIX login name, so that "." are not allowed. I would suggest using "_" instead. You have to fill a form and after doing so, click "Register". Once we do this, you have to check your email (you should provide it in the form) and then complete registration. WPLs are entitled to ask people working in their WPs to perform this step as soon as possible. Please note that maybe not all people are registered in fiware at lists.fi-ware.eu so you should forward this message also to your lists with any other specific instruction you may want to add. 2. Give Admin privileges to WPLs All WPs have a "project" in Fussion Forge. You can already see them listed at: http://forge.fi-ware.eu/ on the right bottom corner under section "Recently Registered Projects" Once WPLs have registered them as users in the Forge, they should send me an email informing about this. Then I will register them as Admin users in the project corresponding to the WP they lead. 3. Give access to partners in each of the WPLs Once WPLs have admin privileges, they should take care of adding the users in FusionForge to their projects. Doing this is also easy. Once step 2 has been completed and you login as users in FusionForge, you may click on your project. Then, you should click on the Admin Tab and then click on the "Users" menu option right below the Tab. It would then allow you to add users to your project. You should ask people working in your WP to let you know what user nicknames they have choosen in FusionForge (although I guess you may easily find them using the "Add Users From List" option. Note that you have to decide what privileges you assign users in your project. You may add more Admins or assign it that of a Senior Developer or Doc Writer, I would suggest. 4. Sharing documents Once you perform the steps above, it should be quite easy to share documents. I will send an email giving a brief tutorial on this. So, please, start performing steps 1 and 2 and make it as quickly as you can so that we can have everything setup asap. I hope you are not experiencing any problem with the mailing lists so far. But I don't see movement in some mailing lists so I'm a bit worried. Please send us any feedback you may have to fiware-support at lists.fi-ware.eu 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 [attachment "jhierro.vcf" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From GLIKSON at il.ibm.com Fri May 13 16:44:43 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 13 May 2011 17:44:43 +0300 Subject: [Fiware-cloud] FI-WARE WP4 functions and capabilities - draft for review & discussion Message-ID: All, Based on the WP description in the DoW and the discussion we had during the kickoff, I've tried to outline the main functions and capabilities of Cloud Hosting, as well as few other aspects (scenarios, users, non-functional aspects). I'm sure there are many things missing -- please, review and comment. Hopefully, this list can become the outline of our chapter in the High Level Description that we need to deliver by June, 20th. During the upcoming conference call on Tuesday (let me know if you don't have the call details), we can review the latest version of this list (with your updates and comments), and decide on responsibilities to elaborate on each of the items in the HLDesc. Regards, Alex P.S. it is still not clear to me how to 'partition' the list below into small number of 'generic enablers'.. However, I'm also not sure it is strictly necessary, as long as we provide the necessary details to understand what this WP is about to provide., Juanjo, others -- any thoughts? ------------------------------ Object store Management fabric - communication, synchronization, health monitoring, persistent store Node deployment engine Resource management -- Single 'compute' target ("node"), Group of 'compute' targets ("cluster"), Group of clusters (cloud) - request orchestration and dispatching - capacity management & admission control - placement optimization (for multiple targets) - QoS management & resource allocation guarantees - resource reservation (for certain time period) - storage control (internal, shared) - network control (internal, external) Storage management Network connectivity management Image repository Service management - request orchestration and dispatching - catalog - elasticity governance - SLOs (management, enforcement) - metering PaaS Cloud Proxy Interfaces (APIs, portal, toolkit) - Admin interface - User interface ------ E2E Scenarios - catalog browsing - provisioning & deployment management - monitoring & metering - SLO-driven capacity overbooking & elasticity governance - cloud administration Non-functional Aspects - Security: e.g., user authentication & authorization, compute/network/storage isolation, OVF certificate validation, etc - Scalability - Performance - Resiliency - APIs - etc Users of Cloud Hosting admin of the IaaS provider, managing the IaaS infrastructure admin of the PaaS provider, managing the PaaS infrastructure IaaS user, directly consuming IaaS infrastructure and services (Note: could be the UC Project developer, which uses hosted VMs to perform development/testing or to deploy in 'production' a UCP product/application) PaaS user (e.g., UC Project developer), directly consuming PaaS infrastructure and services to build a 3rd part application/service End-user of the application hosted in the cloud -- Not a Direct User!? From jhierro at tid.es Sun May 15 18:07:07 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 15 May 2011 18:07:07 +0200 Subject: [Fiware-cloud] List of experts from the Security WP who we should involve in the different WP mailing lists Message-ID: <4DCFFA2B.1060006@tid.es> Dear colleagues, One of the actions that we agreed to implement during our kick-off meeting in Madrid was to identify people working in the Security WP that will be in charge of monitoring work in the different WPs in order to ensure that Security aspects are taken into account in the design. Besides, they can act as contact points to the WPs whenever they want to raise any question or launch any consultation on any Security matter relevant to work in their WP. Following is the list that Pascal Bisson, Security WPL, has forwarded to me in order to implement the described action. * WP3 -Service ecosystem AT * Andreas Schaad (andreas.schaad at sap.com) * Pascal Bisson (Pascal.bisson at thalesgroup.com) * Daniel Gidoin (daniel.gidoin at thalesgroup.com) * WP4 - Cloud AT * ALVARO ARMENTEROS PACHECO (aap at tid.es) * Pascal Bisson (Pascal.bisson at thalesgroup.com) * Daniel Gidoin (daniel.gidoin at thalesgroup.com) * Philippe Leleu (Philippe.LELEU at fr.thalesgroup.com) * WP5 - Internet of things AT * Vania Conan (Vania.CONAN at fr.thalesgroup.com) * Mario Lopez-ramos (Mario.LOPEZRAMOS at fr.thalesgroup.com) * Richard Egan (richard.egan at thalesgroup.com) * Xavier Aghina (xavier.aghina at orange-ftgroup.com) * WP6 - Data/Context Management AT * Pedro Soria-Rodriguez (pedro.soria at atosresearch.eu) * Pascal Bisson (Pascal.bisson at thalesgroup.com) * Daniel Gidoin (daniel.gidoin at thalesgroup.com) * WP7 - Interface to the Network * Wolfgang Steigerwarld (Wolfgang.Steigerwald at telekom.de) * Vania Conan (Vania.CONAN at fr.thalesgroup.com) Unless we hear any objection from you tomorrow EOB, we will add them in your corresponding mailing lists. 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From serge.defrance at technicolor.com Mon May 16 14:29:31 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Mon, 16 May 2011 14:29:31 +0200 Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E44453723@MOPESMBX01.eu.thmulti.com> Dear all, I've added the slides form Technicolor. My user name is "defrances". Hear you soon, Serge. -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Edmonds, AndrewX Sent: vendredi 13 mai 2011 16:01 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff I've added the slides from Intel... Andy -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: Friday, May 13, 2011 2:46 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff I have started uploading kickoff materials to http://forge.fi-ware.eu/docman/index.php?group_id=14&selected_doc_group_id=1 2&language_id=1 (there are some technical issues, though -- seems that it is impossible for now to upload files larger than 2MB). Please, complete the instructions below to register, and let me know. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 13/05/2011 04:15 PM ----- From: Juanjo Hierro To: fiware at lists.fi-ware.eu Date: 13/05/2011 01:34 PM Subject: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff Sent by: fiware-bounces at lists.fi-ware.eu Hi all, This email is to explain you what the are the next steps you should follow to be able to start using the tools for sharing documents, etc. The forge infrastructure associated to the overall FI-WARE collaborative infrastructure has already been set up. This is currently based on FusionForge. FusionForge will provide the basic tool for uploading/publish/downloading documents and attach URLs to them. Here it is the list of steps that we will follow to have everything ready. 1. Registration as users of FusionForge This is pretty simple. You just have to go to: http://forge.fi-ware.eu/ then click on "New Account" in the upper right corner It should drive you to a screen where you will assign yourself a nickname. It should be valid UNIX login name, so that "." are not allowed. I would suggest using "_" instead. You have to fill a form and after doing so, click "Register". Once we do this, you have to check your email (you should provide it in the form) and then complete registration. WPLs are entitled to ask people working in their WPs to perform this step as soon as possible. Please note that maybe not all people are registered in fiware at lists.fi-ware.eu so you should forward this message also to your lists with any other specific instruction you may want to add. 2. Give Admin privileges to WPLs All WPs have a "project" in Fussion Forge. You can already see them listed at: http://forge.fi-ware.eu/ on the right bottom corner under section "Recently Registered Projects" Once WPLs have registered them as users in the Forge, they should send me an email informing about this. Then I will register them as Admin users in the project corresponding to the WP they lead. 3. Give access to partners in each of the WPLs Once WPLs have admin privileges, they should take care of adding the users in FusionForge to their projects. Doing this is also easy. Once step 2 has been completed and you login as users in FusionForge, you may click on your project. Then, you should click on the Admin Tab and then click on the "Users" menu option right below the Tab. It would then allow you to add users to your project. You should ask people working in your WP to let you know what user nicknames they have choosen in FusionForge (although I guess you may easily find them using the "Add Users From List" option. Note that you have to decide what privileges you assign users in your project. You may add more Admins or assign it that of a Senior Developer or Doc Writer, I would suggest. 4. Sharing documents Once you perform the steps above, it should be quite easy to share documents. I will send an email giving a brief tutorial on this. So, please, start performing steps 1 and 2 and make it as quickly as you can so that we can have everything setup asap. I hope you are not experiencing any problem with the mailing lists so far. But I don't see movement in some mailing lists so I'm a bit worried. Please send us any feedback you may have to fiware-support at lists.fi-ware.eu 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 [attachment "jhierro.vcf" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud From fla at tid.es Mon May 16 15:48:29 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Mon, 16 May 2011 15:48:29 +0200 Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff In-Reply-To: References: Message-ID: <8EE61BA0CAEDBD4E9DA928D1206463D2A184EBE75C@EXCLU2K7.hi.inet> I finally upload the slides from TID... Fernando -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Edmonds, AndrewX Sent: viernes, 13 de mayo de 2011 16:01 To: fiware-cloud at lists.fi-ware.eu Subject: Re: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff I've added the slides from Intel... Andy -----Original Message----- From: fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] On Behalf Of Alex Glikson Sent: Friday, May 13, 2011 2:46 PM To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Fw: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff I have started uploading kickoff materials to http://forge.fi-ware.eu/docman/index.php?group_id=14&selected_doc_group_id=1 2&language_id=1 (there are some technical issues, though -- seems that it is impossible for now to upload files larger than 2MB). Please, complete the instructions below to register, and let me know. Thanks, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 13/05/2011 04:15 PM ----- From: Juanjo Hierro To: fiware at lists.fi-ware.eu Date: 13/05/2011 01:34 PM Subject: [Fiware] ACTIONS to be done so that we can start to share documents and other stuff Sent by: fiware-bounces at lists.fi-ware.eu Hi all, This email is to explain you what the are the next steps you should follow to be able to start using the tools for sharing documents, etc. The forge infrastructure associated to the overall FI-WARE collaborative infrastructure has already been set up. This is currently based on FusionForge. FusionForge will provide the basic tool for uploading/publish/downloading documents and attach URLs to them. Here it is the list of steps that we will follow to have everything ready. 1. Registration as users of FusionForge This is pretty simple. You just have to go to: http://forge.fi-ware.eu/ then click on "New Account" in the upper right corner It should drive you to a screen where you will assign yourself a nickname. It should be valid UNIX login name, so that "." are not allowed. I would suggest using "_" instead. You have to fill a form and after doing so, click "Register". Once we do this, you have to check your email (you should provide it in the form) and then complete registration. WPLs are entitled to ask people working in their WPs to perform this step as soon as possible. Please note that maybe not all people are registered in fiware at lists.fi-ware.eu so you should forward this message also to your lists with any other specific instruction you may want to add. 2. Give Admin privileges to WPLs All WPs have a "project" in Fussion Forge. You can already see them listed at: http://forge.fi-ware.eu/ on the right bottom corner under section "Recently Registered Projects" Once WPLs have registered them as users in the Forge, they should send me an email informing about this. Then I will register them as Admin users in the project corresponding to the WP they lead. 3. Give access to partners in each of the WPLs Once WPLs have admin privileges, they should take care of adding the users in FusionForge to their projects. Doing this is also easy. Once step 2 has been completed and you login as users in FusionForge, you may click on your project. Then, you should click on the Admin Tab and then click on the "Users" menu option right below the Tab. It would then allow you to add users to your project. You should ask people working in your WP to let you know what user nicknames they have choosen in FusionForge (although I guess you may easily find them using the "Add Users From List" option. Note that you have to decide what privileges you assign users in your project. You may add more Admins or assign it that of a Senior Developer or Doc Writer, I would suggest. 4. Sharing documents Once you perform the steps above, it should be quite easy to share documents. I will send an email giving a brief tutorial on this. So, please, start performing steps 1 and 2 and make it as quickly as you can so that we can have everything setup asap. I hope you are not experiencing any problem with the mailing lists so far. But I don't see movement in some mailing lists so I'm a bit worried. Please send us any feedback you may have to fiware-support at lists.fi-ware.eu 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 [attachment "jhierro.vcf" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ 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 lorant.farkas at nsn.com Mon May 16 14:20:47 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 16 May 2011 15:20:47 +0300 Subject: [Fiware-cloud] [Fiware-iot] List of experts from the Security WP who we should involve in the different WP mailing lists In-Reply-To: <4DCFFA2B.1060006@tid.es> References: <4DCFFA2B.1060006@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A201C640C5@FIESEXC014.nsn-intra.net> Dear Juanjo, I would like to ask to please include my colleague Roberd Seidl at least in monitoring WP5 and WP7 which are the WP-s the most interesting from NSN perspective. Additional reasoning would be that WP5 is monitored by 3 colleagues from Thales which is a bit overrepresentation in my view, while for WP7 there are only two colleagues monitoring compared to 4 in the other work packages, so why not adding a third colleage. Thanks & Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Sunday, May 15, 2011 6:07 PM To: fiware-apps at lists.fi-ware.eu; fiware-cloud at lists.fi-ware.eu; fiware-data at lists.fi-ware.eu; fiware-i2nd at lists.fi-ware.eu; fiware-iot at lists.fi-ware.eu; fiware-security at lists.fi-ware.eu Subject: [Fiware-iot] List of experts from the Security WP who we should involve in the different WP mailing lists Dear colleagues, One of the actions that we agreed to implement during our kick-off meeting in Madrid was to identify people working in the Security WP that will be in charge of monitoring work in the different WPs in order to ensure that Security aspects are taken into account in the design. Besides, they can act as contact points to the WPs whenever they want to raise any question or launch any consultation on any Security matter relevant to work in their WP. Following is the list that Pascal Bisson, Security WPL, has forwarded to me in order to implement the described action. * WP3 -Service ecosystem AT * Andreas Schaad (andreas.schaad at sap.com) * Pascal Bisson (Pascal.bisson at thalesgroup.com) * Daniel Gidoin (daniel.gidoin at thalesgroup.com) * WP4 - Cloud AT * ALVARO ARMENTEROS PACHECO (aap at tid.es) * Pascal Bisson (Pascal.bisson at thalesgroup.com) * Daniel Gidoin (daniel.gidoin at thalesgroup.com) * Philippe Leleu (Philippe.LELEU at fr.thalesgroup.com) * WP5 - Internet of things AT * Vania Conan (Vania.CONAN at fr.thalesgroup.com) * Mario Lopez-ramos (Mario.LOPEZRAMOS at fr.thalesgroup.com) * Richard Egan (richard.egan at thalesgroup.com) * Xavier Aghina (xavier.aghina at orange-ftgroup.com) * WP6 - Data/Context Management AT * Pedro Soria-Rodriguez (pedro.soria at atosresearch.eu) * Pascal Bisson (Pascal.bisson at thalesgroup.com) * Daniel Gidoin (daniel.gidoin at thalesgroup.com) * WP7 - Interface to the Network * Wolfgang Steigerwarld (Wolfgang.Steigerwald at telekom.de) * Vania Conan (Vania.CONAN at fr.thalesgroup.com) Unless we hear any objection from you tomorrow EOB, we will add them in your corresponding mailing lists. 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 May 17 09:22:57 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 17 May 2011 09:22:57 +0200 Subject: [Fiware-cloud] List of experts from the Security WP who we should involve in the different WP mailing lists In-Reply-To: <8153_1305452104_4DCF9E48_8153_2170_1_094ce59f-1f65-4b0d-b41a-80eca3a6647e@THSONEA01HUB01P.one.grp> References: <4DCC0F71.2050208@tid.es> <8153_1305452104_4DCF9E48_8153_2170_1_094ce59f-1f65-4b0d-b41a-80eca3a6647e@THSONEA01HUB01P.one.grp> Message-ID: <4DD22251.8070301@tid.es> Done. On 15/05/11 11:35, BISSON Pascal wrote: > Dear Juanjo, > > Apologize for my late answer, here are the names of our Security people to enroll in the other WPs: > > WP3 -Service ecosystem AT > Andreas Schaad andreas.schaad at sap.com > Pascal Bisson (Pascal.bisson at thalesgroup.com) > Daniel Gidoin (daniel.gidoin at thalesgroup.com) > WP4 - Cloud AT > ALVARO ARMENTEROS PACHECO (aap at tid.es) > Pascal Bisson (Pascal.bisson at thalesgroup.com) > Daniel Gidoin daniel.gidoin at thalesgroup.com > Philippe Leleu (Philippe.LELEU at fr.thalesgroup.com) > WP5 - Internet of things AT > Vania Conan (Vania.CONAN at fr.thalesgroup.com) > Mario Lopez-ramos (Mario.LOPEZRAMOS at fr.thalesgroup.com) > Richard Egan (richard.egan at thalesgroup.com) > Xavier Aghina (xavier.aghina at orange-ftgroup.com) > WP6 - Support Services AT > Pedro Soria-Rodriguez (pedro.soria at atosresearch.eu) > Pascal Bisson (Pascal.bisson at thalesgroup.com) > Daniel Gidoin daniel.gidoin at thalesgroup.com > WP7 - Interface to the Network > Wolfgang Steigerwarld (Wolfgang.Steigerwald at telekom.de) > Vania Conan (Vania.CONAN at fr.thalesgroup.com) > > > > -----Message d'origine----- > De : Juanjo Hierro [mailto:jhierro at tid.es] > Envoy? : jeudi 12 mai 2011 18:49 > ? : BISSON Pascal > Cc : jhierro>> "Juan J. Hierro" > Objet : List of experts from the Security WP who we should involve in the different WP mailing lists > > Dear Pascal, > > You mentioned that within the Security WP you have designated a concrete expert who should take care of the liason with other WPs and the discussion of Security-related issues. > > May you provide a list of who will be those experts so that we can register them in the corresponding WP mailing list ? Of course, I need their e-mail address. > > 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 -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From fla at tid.es Tue May 17 10:56:01 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 17 May 2011 10:56:01 +0200 Subject: [Fiware-cloud] FI-WARE WP4 functions and capabilities - draft for review & discussion In-Reply-To: References: Message-ID: <44D7E49E-C44B-451B-9B85-B20A0E41B86E@tid.es> Dear Alex et all, We just extend the section about PaaS with the following context in order to talk about it during the PhC today: PaaS: - application/service definition (extensions to OVF to support platform concepts). - Deployment design (establish the concrete structure of the application deployment: number of VMs, software in each VM, final network structure, etc. - Provisioning and deployment: Configuring and passing of information to the different elements in the PaaS to prepare and later deploy the application/service into the IaaS. During the deployment phase different components need to be orchestrated: the configuration interfaces of the services offered integrated into the Platform (e.g. database services), configuration of the monitoring and accounting system, configuration of the VM (drive the creation of the VM with the application components inside), etc. - IaaS/NaaS control layer, which interacts with the IaaS provider to deploy the VM, install and configure the software into the different VMs. - Adaptation and scalability of the application/services deployed. Based on rules defined by the service provider or to enforce the SLAs in place. BR, 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:image001.jpg at 01CB21A4.CCF8C640] El 13/05/2011, a las 16:44, Alex Glikson escribi?: All, Based on the WP description in the DoW and the discussion we had during the kickoff, I've tried to outline the main functions and capabilities of Cloud Hosting, as well as few other aspects (scenarios, users, non-functional aspects). I'm sure there are many things missing -- please, review and comment. Hopefully, this list can become the outline of our chapter in the High Level Description that we need to deliver by June, 20th. During the upcoming conference call on Tuesday (let me know if you don't have the call details), we can review the latest version of this list (with your updates and comments), and decide on responsibilities to elaborate on each of the items in the HLDesc. Regards, Alex P.S. it is still not clear to me how to 'partition' the list below into small number of 'generic enablers'.. However, I'm also not sure it is strictly necessary, as long as we provide the necessary details to understand what this WP is about to provide., Juanjo, others -- any thoughts? ------------------------------ Object store Management fabric - communication, synchronization, health monitoring, persistent store Node deployment engine Resource management -- Single 'compute' target ("node"), Group of 'compute' targets ("cluster"), Group of clusters (cloud) - request orchestration and dispatching - capacity management & admission control - placement optimization (for multiple targets) - QoS management & resource allocation guarantees - resource reservation (for certain time period) - storage control (internal, shared) - network control (internal, external) Storage management Network connectivity management Image repository Service management - request orchestration and dispatching - catalog - elasticity governance - SLOs (management, enforcement) - metering PaaS Cloud Proxy Interfaces (APIs, portal, toolkit) - Admin interface - User interface ------ E2E Scenarios - catalog browsing - provisioning & deployment management - monitoring & metering - SLO-driven capacity overbooking & elasticity governance - cloud administration Non-functional Aspects - Security: e.g., user authentication & authorization, compute/network/storage isolation, OVF certificate validation, etc - Scalability - Performance - Resiliency - APIs - etc Users of Cloud Hosting admin of the IaaS provider, managing the IaaS infrastructure admin of the PaaS provider, managing the PaaS infrastructure IaaS user, directly consuming IaaS infrastructure and services (Note: could be the UC Project developer, which uses hosted VMs to perform development/testing or to deploy in 'production' a UCP product/application) PaaS user (e.g., UC Project developer), directly consuming PaaS infrastructure and services to build a 3rd part application/service End-user of the application hosted in the cloud -- Not a Direct User!? _______________________________________________ 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: image001.jpg Type: image/jpeg Size: 6541 bytes Desc: image001.jpg URL: From jhierro at tid.es Tue May 17 16:52:55 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 17 May 2011 16:52:55 +0200 Subject: [Fiware-cloud] Template for FI-WARE documents (including template for deliverables) available in documentation management tool Message-ID: <4DD28BC7.9020607@tid.es> Dear colleagues, The document management tool is now finally configured so that we are now able to use it for sharing documents. I'll send you a brief document describing how it works in order to upload/publish documents later this evening. In the meantime, let me share with you the template we would like you to follow for creating FI-WARE documents. You can download it from: http://forge.fi-ware.eu/docman/view.php/7/42/FI-WARE+Public+Document+template+11-05-17.doc You may also find a template for meeting minutes useful. You can download it from: http://forge.fi-ware.eu/docman/view.php/7/41/FI-WARE+Minutes+template+11-05-17.doc Both documents are private, so that only users properly registered in the FI-WARE project in the FI-WARE FusionForge will be able to download them :-) I hope this will persuade most of you to register in the FI-WARE project @ FusionForge if you haven't still done so :-) A mail reminding to register with a detailed (updated) description of steps to be followed will arrive to you in the next message. 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From GLIKSON at il.ibm.com Tue May 17 16:53:25 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 17 May 2011 17:53:25 +0300 Subject: [Fiware-cloud] FI-Ware WP4 (Cloud Hosting) weekly conf call -- 17-May-2011 minutes Message-ID: All, Please, see bellow minutes from today's conference call. Please, let me know if you have any comments (or if you can't see the formatting well). Also, please, let me know if the person that will be responsible for action items and deliverables mentioned below on behalf of your company is different than the one I've indicated. Thanks! Alex Attendees: IBM, TID, TRDF, UPM (missing: Intel, INRIA, FT) Agenda: update on finalizing the role of each partner further meetings to work on the content of HLDesc(M2) deliverable review & update the list of functions and capabilities action items until next meeting, owners, schedule Minutes: FT still has not representative in WP4 (was escalated to Juanjo) The exact role of INRIA is still not clear, due to inconsistency in the DoW (was escalated to Juanjo) We will have weekly 1-hour conference calls to work on the HLDesc towards the M2 milestone. it was agreed to use the same time slot as today (every Tuesday) It should be mentioned in the HLDesc that per Agile process, some of the capabilities described in the M2 deliverable may be identified as low priority during the backlog prioritization phases, and hence could be deferred or dropped The list of functions & capabilities was reviewed and updated. Also, owners were identified for each function/capability (see below). It was agreed that the goal for the upcoming week is to produce the first version of high-level description of each function/capability -- few paragraphs per function/capability, plus the initial set of important terms which should be defined in the HLDesc (derived from the description of the function/capability). In order to let all the partners to review the outcome of what others have done *before* the next conf call, it was agreed that the deadline for providing the above content is Monday, 23/5, noon (CET). Action Items: Schedule next meetings [Alex, done. All: please, confirm that you've received the invitation and can see the details properly] Follow-up with Juanjo regarding the role and representation of FT, as well as the role of INRIA [Alex, sent a note] Provide initial content and list of keywords/terms for each of the functions/capabilities [Andy, Marina, Alex, David, Fernando, Serge, Juaquin -- send to the mailing list by Monday, 23/5, noon (CET)] List of functions/capabilities and owners (see more details below): Physical & virtual resource infrastructure -- Intel/Andy Resource management Note-level -- Intel/Andy + IBM/Marina Cluster-level -- IBM/Alex Cloud-level -- IBM/David Management fabric -- IBM/Alex Service management - TID/Fernando + IBM/David + FT/?? (??) PaaS -- TID/Fernando + INRIA/Denis? Cloud Proxy -- TRDF/Serge Interfaces -- UPM/Joaquin (portal), TID/Fernando (APIs) Detailed list of functions and capabilities (working draft): Physical & virtual resource infrastructure Object store Block storage infrastructure Network infrastructure Image repository Resource management: Note-level, Cluster-level, Cloud-level Request orchestration and dispatching Capacity management & admission control (note: related to elasticity/SLOs aspects of service management) Placement optimization (for multiple targets) QoS management & resource allocation guarantees Resource reservation (e.g., for certain time period) Monitoring Management fabric communication, synchronization, health monitoring, etc Service management Request orchestration and dispatching Catalog Service definition & life cycle management Elasticity governance SLOs (management, enforcement) Monitoring Metering PaaS Application/service definition (extensions to OVF to support platform concepts). Deployment design (establish the concrete structure of the application deployment: number of VMs, software in each VM, final network structure, etc. Provisioning and deployment: Configuring and passing of information to the different elements in the PaaS to prepare and later deploy the application/service into the IaaS. During the deployment phase different components need to be orchestrated: the configuration interfaces of the services offered integrated into the Platform (e.g. database services), configuration of the monitoring and accounting system, configuration of the VM (drive the creation of the VM with the application components inside), etc. IaaS/NaaS control layer, which interacts with the IaaS provider to deploy the VM, install and configure the software into the different VMs. Adaptation and scalability of the application/services deployed. Based on rules defined by the service provider or to enforce the SLAs in place. Cloud Proxy Interfaces Admin vs User API vs Portal vs Toolkit From jhierro at tid.es Tue May 17 16:55:12 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 17 May 2011 16:55:12 +0200 Subject: [Fiware-cloud] Reminder and updated instructions for registering at FusionForge and be able to access to shared documentation Message-ID: <4DD28C50.20104@tid.es> Dear all, Following is a list of instructions you should follow to register in FusionForge and be able to upload as well as to share documents. Registering in the FI-WARE project is quite easy. We will ask you to perform the following steps (*important note*: this is an update of the instructions I sent a couple of days ago): 1. Registration as users of FusionForge This is pretty simple. You just have to go to: http://forge.fi-ware.eu/ then click on "New Account" in the upper right corner It should drive you to a screen where you will assign yourself a nickname. It should be valid UNIX login name, so that "." are not allowed. I would suggest using "_" instead. You have to fill a registration form and after doing so, click "Register". Once we do this, you have to check your email (you should provide your email address in the registration form) and then complete registration. WPLs are entitled to ask people working in their WPs to perform this step as soon as possible. Please note that maybe not all people are registered in fiware at lists.fi-ware.eu so you should forward this message also to your lists with any other specific instruction you may want to add. Note that registering in FusionForge is a step necessary to perform the following steps and finally be able to get access to private documents uploaded in FusionForge. 2. Give Admin privileges to WPLs All WPs have a "project" in Fussion Forge. You can already see them listed at: http://forge.fi-ware.eu/ on the right bottom corner under section "Recently Registered Projects" Once WPLs have registered them as users in the Forge, they should send me an email informing about this. Then I will register them as Admin users in the project corresponding to the WP they lead as well as in FI-WARE. Pascal Bisson (Security WP), Torsten Leidig (Apps/Services Ecosystem WP), Alex Glikson (Cloud Hosting WP), myself (Data/Context Management WP), Hans Joachim Einsiedler and Pierangelo Garino (I2ND WP) have already registered and have been assigned Admin privileges both in FI-WARE and their WP. Still missing: IoT Services Enablement WP, Exploitation WP and the Developers Community Tools WP. 3. Give access to partners in each of the WPLs Once WPLs get admin privileges, they should take care of registering members of their WP team in their projects as well as the FI-WARE project @ FusionForge. Admins at TID will also help to add them to FI-WARE. There are two ways a given person already registered in FusionForge can join a project as member: * Option 1: * Tell this to your WPL and me by email. Your WPL (or someone from TID for the FI-WARE project) has to go to the space assigned to the project. You can see all available projects at: * http://forge.fi-ware.eu/softwaremap/full_list.php * After navigating to the project he/she manages, the WPL should click on the Admin Tab and then click on the "Users" menu option (right below the Admin Tab) and finally select "Add Users from List". Then he/she just needs to look for the user he wants to register in the project and mark the "Add User" option (you'll see it on the right side). Once he has marked all users he/she wants to add, just needs to click on the "Finish" button * This bring him/her to a screen where he can decide on the role assigned to each selected user (we recommend you to assign a "Senior Developer" rol) and finally click on "Add all" * Option 2: * The partner who wants to join a given project goes to the space linked to that project by clicking on the corresponding URL at: * http://forge.fi-ware.eu/softwaremap/full_list.php * Then the partner goes to the box at the right hand of the screen where the names of Admins and developers of the project are listed and clicks on the "Request to join" link there * The WPL and TID will check requests to join and will approve them when appropriate. Note that WPLs have to decide what privileges you assign users in their corresponding projects. They may add more Admins or assign it that of a Senior Developer or Doc Writer, I would suggest Senior Developer. 4. Sharing documents Once you perform the steps above, it should be quite easy to share documents. I will send an email giving a brief tutorial on this later this evening. ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Tue May 17 18:40:18 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 17 May 2011 18:40:18 +0200 Subject: [Fiware-cloud] Problems accessing FI-WARE documents (including template for deliverables) available in documentation management tool In-Reply-To: References: <4DD28BC7.9020607@tid.es> Message-ID: <4DD2A4F2.1050304@tid.es> Dear Wolfgang, I copy all the project because my response to your question might be useful for all. What happens to you is because: * you have not requested to join the FI-WARE project (you should request joining FI-WARE and the project linked to WPs you are involved in) OR * you have not send an email to your WPL asking him/her to register you in the FI-WARE project (and the project linked to the WP he/she leads) This was explained in my previous message. Probably the easiest method would be the first one. You just need to get access to the project page (through http://forge.fi-ware.eu/softwaremap/full_list.php) and then click on the "Request to join" link you will find on the right side of your screen: [cid:part1.00070202.05070106 at tid.es] Once you request to join, either one of the WPLs or some Admin from TID will grant you access (also explained in my previous mail). Note for the Admins: you should grant access but assigning a "Senior Developer" role. Note that EVERYONE in the world might register in our FusionForge instance (that's the way it works). This ease administration and also enables third parties to approach us. However, only FusionForge users that are registered in a project can access documents labeled as "private" to that project. In the case of the referred documents, we decided to label them as private to the project. Hope this helps, -- Juanjo On 17/05/11 17:48, Wolfgang.Steigerwald at telekom.de wrote: Hello Juanjo, even so I'm registered on FusionForge I receive "Permission denied" Best regards Wolfgang Deutsche Telekom AG T-Labs (Research & Development) Wolfgang Steigerwald Goslarer Ufer 35, 10589 Berlin +49 30 3497-2058 (Tel.) +49 391 53475396 (Fax) +49 171 5664350 (Mobil) E-Mail: wolfgang.steigerwald at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Edward R. Kozel, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an ? Ressourcen schonen und nicht jede E-Mail drucken. ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Dienstag, 17. Mai 2011 16:53 An: fiware at lists.fi-ware.eu; fiware-apps at lists.fi-ware.eu; fiware-cloud at lists.fi-ware.eu; fiware-data at lists.fi-ware.eu; fiware-iot at lists.fi-ware.eu; fiware-i2nd at lists.fi-ware.eu; fiware-security at lists.fi-ware.eu; fiware-tools at lists.fi-ware.eu Betreff: [Fiware-i2nd] Template for FI-WARE documents (including template for deliverables) available in documentation management tool Dear colleagues, The document management tool is now finally configured so that we are now able to use it for sharing documents. I'll send you a brief document describing how it works in order to upload/publish documents later this evening. In the meantime, let me share with you the template we would like you to follow for creating FI-WARE documents. You can download it from: http://forge.fi-ware.eu/docman/view.php/7/42/FI-WARE+Public+Document+template+11-05-17.doc You may also find a template for meeting minutes useful. You can download it from: http://forge.fi-ware.eu/docman/view.php/7/41/FI-WARE+Minutes+template+11-05-17.doc Both documents are private, so that only users properly registered in the FI-WARE project in the FI-WARE FusionForge will be able to download them :-) I hope this will persuade most of you to register in the FI-WARE project @ FusionForge if you haven't still done so :-) A mail reminding to register with a detailed (updated) description of steps to be followed will arrive to you in the next message. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: moz-screenshot-14.png Type: image/png Size: 94944 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From fla at tid.es Wed May 18 11:51:51 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 18 May 2011 11:51:51 +0200 Subject: [Fiware-cloud] [FI-WARE.Cloud] New member from TID Message-ID: <0F8EFDBD-563F-4510-B603-6E8673B7CE14@tid.es> Dear all, I would like to please introduce my colleague Jos? Manuel L?pez L?pez (josemll at tid.es) in the WP4 mailing list, who is going to work together with me in the FI-WARE-Cloud part. Thanks & 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:image001.jpg at 01CB21A4.CCF8C640] ________________________________ 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.jpg Type: image/jpeg Size: 6541 bytes Desc: image001.jpg URL: From fla at tid.es Wed May 18 15:59:14 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 18 May 2011 15:59:14 +0200 Subject: [Fiware-cloud] [FI-WARE.Cloud] New member from TID In-Reply-To: <0F8EFDBD-563F-4510-B603-6E8673B7CE14@tid.es> References: <0F8EFDBD-563F-4510-B603-6E8673B7CE14@tid.es> Message-ID: Dear all, I just put the sections into the template document that we have to use in the project. Also you can see a first distribution of subsections per each section (more or less identified with T4.4 and T4.5 activities). Regarding the distribution of partners per each subsection, I just made some distributions based on the presentation and DoW but feel free to put yourself what do you want else if you consider that you can provide information in some others, but please make me note it in order to make the integration of all parts. Missing parts here are the Catalog (nobody volunteers it?) Regarding the way to proceed with it, I suggest that you send me your contributions in this section (with track changes activated), in order that I can make the integration of all contributions and make Alex's life easier ;) For this purpose I suggest that all the contributions in those sections have to be sent Monday morning. Do not forget that we need only a brief description in these subsections per each partner in order to start to work. Comments and suggestions are always welcome. BR, ________________________________ 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: Deliverable x.doc Type: application/msword Size: 640000 bytes Desc: Deliverable x.doc URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6541 bytes Desc: image001.jpg URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Wed May 18 18:44:03 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Wed, 18 May 2011 18:44:03 +0200 Subject: [Fiware-cloud] [FI-WARE.Cloud] New member from TID In-Reply-To: References: <0F8EFDBD-563F-4510-B603-6E8673B7CE14@tid.es> Message-ID: <73BBB592-DA22-4646-8389-6E2B2B3A89D5@tid.es> Dear all, I had a little misunderstanding regarding the subsection "Deployment Lifecycle Management" in which I forgot to include ourselves :-P Please consider that we provide also contributions in that subsection. Sorry for my mistake. 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.jpg at 01CB21A4.CCF8C640] El 18/05/2011, a las 15:59, FERNANDO LOPEZ AGUILAR escribi?: Dear all, I just put the sections into the template document that we have to use in the project. Also you can see a first distribution of subsections per each section (more or less identified with T4.4 and T4.5 activities). Regarding the distribution of partners per each subsection, I just made some distributions based on the presentation and DoW but feel free to put yourself what do you want else if you consider that you can provide information in some others, but please make me note it in order to make the integration of all parts. Missing parts here are the Catalog (nobody volunteers it?) Regarding the way to proceed with it, I suggest that you send me your contributions in this section (with track changes activated), in order that I can make the integration of all contributions and make Alex's life easier ;) For this purpose I suggest that all the contributions in those sections have to be sent Monday morning. Do not forget that we need only a brief description in these subsections per each partner in order to start to work. Comments and suggestions are always welcome. BR, ________________________________ 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.jpg Type: image/jpeg Size: 6541 bytes Desc: image001.jpg URL: From GLIKSON at il.ibm.com Wed May 18 22:54:25 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 18 May 2011 23:54:25 +0300 Subject: [Fiware-cloud] Fw: FI-Ware WP4 (Cloud Hosting) weekly conf call -- 17-May-2011 minutes Message-ID: Resending, this time you should be able to see the rich formatting -- bullets, bold, etc (let me know if you don't). Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 18/05/2011 11:52 PM ----- From: Alex Glikson/Haifa/IBM To: fiware-cloud at lists.fi-ware.eu Date: 17/05/2011 05:53 PM Subject: FI-Ware WP4 (Cloud Hosting) weekly conf call -- 17-May-2011 minutes All, Please, see bellow minutes from today's conference call. Please, let me know if you have any comments (or if you can't see the formatting well). Also, please, let me know if the person that will be responsible for action items and deliverables mentioned below on behalf of your company is different than the one I've indicated. Thanks! Alex Attendees: IBM, TID, TRDF, UPM (missing: Intel, INRIA, FT) Agenda: update on finalizing the role of each partner further meetings to work on the content of HLDesc(M2) deliverable review & update the list of functions and capabilities action items until next meeting, owners, schedule Minutes: FT still has not representative in WP4 (was escalated to Juanjo) The exact role of INRIA is still not clear, due to inconsistency in the DoW (was escalated to Juanjo) We will have weekly 1-hour conference calls to work on the HLDesc towards the M2 milestone. it was agreed to use the same time slot as today (every Tuesday) It should be mentioned in the HLDesc that per Agile process, some of the capabilities described in the M2 deliverable may be identified as low priority during the backlog prioritization phases, and hence could be deferred or dropped The list of functions & capabilities was reviewed and updated. Also, owners were identified for each function/capability (see below). It was agreed that the goal for the upcoming week is to produce the first version of high-level description of each function/capability -- few paragraphs per function/capability, plus the initial set of important terms which should be defined in the HLDesc (derived from the description of the function/capability). In order to let all the partners to review the outcome of what others have done *before* the next conf call, it was agreed that the deadline for providing the above content is Monday, 23/5, noon (CET). Action Items: Schedule next meetings [Alex, done. All: please, confirm that you've received the invitation and can see the details properly] Follow-up with Juanjo regarding the role and representation of FT, as well as the role of INRIA [Alex, sent a note] Provide initial content and list of keywords/terms for each of the functions/capabilities [Andy, Marina, Alex, David, Fernando, Serge, Juaquin -- send to the mailing list by Monday, 23/5, noon (CET)] List of functions/capabilities and owners (see more details below): Physical & virtual resource infrastructure -- Intel/Andy Resource management Note-level -- Intel/Andy + IBM/Marina Cluster-level -- IBM/Alex Cloud-level -- IBM/David Management fabric -- IBM/Alex Service management - TID/Fernando + IBM/David + FT/?? (??) PaaS -- TID/Fernando + INRIA/Denis? Cloud Proxy -- TRDF/Serge Interfaces -- UPM/Joaquin (portal), TID/Fernando (APIs) Detailed list of functions and capabilities (working draft): Physical & virtual resource infrastructure Object store Block storage infrastructure Network infrastructure Image repository Resource management: Note-level, Cluster-level, Cloud-level Request orchestration and dispatching Capacity management & admission control (note: related to elasticity/SLOs aspects of service management) Placement optimization (for multiple targets) QoS management & resource allocation guarantees Resource reservation (e.g., for certain time period) Monitoring Management fabric communication, synchronization, health monitoring, etc Service management Request orchestration and dispatching Catalog Service definition & life cycle management Elasticity governance SLOs (management, enforcement) Monitoring Metering PaaS Application/service definition (extensions to OVF to support platform concepts). Deployment design (establish the concrete structure of the application deployment: number of VMs, software in each VM, final network structure, etc. Provisioning and deployment: Configuring and passing of information to the different elements in the PaaS to prepare and later deploy the application/service into the IaaS. During the deployment phase different components need to be orchestrated: the configuration interfaces of the services offered integrated into the Platform (e.g. database services), configuration of the monitoring and accounting system, configuration of the VM (drive the creation of the VM with the application components inside), etc. IaaS/NaaS control layer, which interacts with the IaaS provider to deploy the VM, install and configure the software into the different VMs. Adaptation and scalability of the application/services deployed. Based on rules defined by the service provider or to enforce the SLAs in place. Cloud Proxy Interfaces Admin vs User API vs Portal vs Toolkit -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu May 19 09:52:58 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 19 May 2011 09:52:58 +0200 Subject: [Fiware-cloud] VERY IMPORTANT: Template and tips for FI-WARE High-level description deliverable (D.2.2) Message-ID: <4DD4CC5A.1090502@tid.es> Dear colleagues, You will find at: http://forge.fi-ware.eu/docman/view.php/7/46/FI-WARE+High-Level+Description+11-06-1+v0.1.doc a word template for deliverable D.2.2 with a number of tips which will serve as helpful hints for completing it. Please follow this templates and provided tips. This is crucial to deliver an harmonized document which is not just a collection of separate contributions. WP teams are entitled to submit their contributions under the contrib document group which belons to the group we have created for this deliverable. As already announced a couple of days ago, all teams are entitled to contribute final versions of their chapters by June 20th EOB. A first draft of is expected for interim review (bilateral meetings between the Chief Architect, that is myself, and co-chief, Thomas Bohnert) by end of May. Don't hesitate to ask any question you may have. While developing this template, we have found a number of things to be fixed in the previously submitted template. Therefore, we have updated the generic template for documentation and make it available at: http://forge.fi-ware.eu/docman/view.php/7/50/FI-WARE+Public+Document+template+11-05-19+v1.0.doc Therefore, we kindly ask you to update the template if you had downloaded it previously. Apologize for any inconvenience this may cause. Take into account that most probably we will have to refine the template while producing this first deliverable. 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu May 19 10:46:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 19 May 2011 10:46:32 +0200 Subject: [Fiware-cloud] VERY IMPORTANT: Template and tips for FI-WARE High-level description deliverable (D.2.2) In-Reply-To: <4DD4CC5A.1090502@tid.es> References: <4DD4CC5A.1090502@tid.es> Message-ID: <4DD4D8E8.9080608@tid.es> The first link was wrong. It was due to mistake I made copying and pasting the link. Apologizes for the inconvenience. You should find it at: http://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.1.doc In something like this happens again, please try to find the document by navigating the Document system from: http://forge.fi-ware.eu/docman/index.php?group_id=7 Thanks for raising the problem. Best regards, -- Juanjo On 19/05/11 09:52, Juanjo Hierro wrote: Dear colleagues, You will find at: http://forge.fi-ware.eu/docman/view.php/7/46/FI-WARE+High-Level+Description+11-06-1+v0.1.doc a word template for deliverable D.2.2 with a number of tips which will serve as helpful hints for completing it. Please follow this templates and provided tips. This is crucial to deliver an harmonized document which is not just a collection of separate contributions. WP teams are entitled to submit their contributions under the contrib document group which belons to the group we have created for this deliverable. As already announced a couple of days ago, all teams are entitled to contribute final versions of their chapters by June 20th EOB. A first draft of is expected for interim review (bilateral meetings between the Chief Architect, that is myself, and co-chief, Thomas Bohnert) by end of May. Don't hesitate to ask any question you may have. While developing this template, we have found a number of things to be fixed in the previously submitted template. Therefore, we have updated the generic template for documentation and make it available at: http://forge.fi-ware.eu/docman/view.php/7/50/FI-WARE+Public+Document+template+11-05-19+v1.0.doc Therefore, we kindly ask you to update the template if you had downloaded it previously. Apologize for any inconvenience this may cause. Take into account that most probably we will have to refine the template while producing this first deliverable. 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jimenez at tid.es Thu May 19 10:51:24 2011 From: jimenez at tid.es (JOSE JIMENEZ DELGADO) Date: Thu, 19 May 2011 10:51:24 +0200 Subject: [Fiware-cloud] Register to Future internet Message-ID: <0986BE7EB220D848BEF7ADDF53B6341957A3E1E10E@EXCLU2K7.hi.inet> Dear all May I remind you that Fiware is part of the PPP program and that there is a common page for all the projects It may be good you visit the page and register to the common library http://www.fi-ppp.eu/library/registration/ BR ------ Jose Jimenez Telefonica I+D Madrid jimenez at tid.es +34 91 483 2660 ________________________________ 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 May 23 09:18:48 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 23 May 2011 10:18:48 +0300 Subject: [Fiware-cloud] Cloud Hosting GEs Message-ID: All, As part of the work on the HLDesc, I've tried to identify the components which can become our "Generic Enablers", according to the criteria defined in the DoW. In particular, it is important to make sure that each GE has a clear set of functions and capabilities which are meaningful to the GE user (in our case -- cloud provider or cloud user working directly with the GE, and optionally other GEs). I'm attaching a diagram which shows the GEs -- please, review and comment. We will need to structure the HLDesc according to the set of GEs (as specified in the template). Thanks, Alex P.S. I'm also including this in the HLDesc -- will send my portion of the initial content in a separate email P.P.S. for those of you who can't see the diagram for some reason, here is the list of GEs: 1. Hosting of Virtual Machines (IaaS) 2. Hosting of VM-based Services [depends on 1] 3. Elasticity and Auto-Scaling [depends on 2] 4. SLO management [depends on 1 and 2] 5. Object Storage 6. Hosting of Application Containers (PaaS) [depends on 1] 7. Cloud Edge -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 13335 bytes Desc: not available URL: From GLIKSON at il.ibm.com Mon May 23 09:57:24 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 23 May 2011 10:57:24 +0300 Subject: [Fiware-cloud] Cloud HLDesc -- overview, GEs, hosting of VMs Message-ID: All, Please, see attached my initial input to the HLDesc. Comments are welcome. Please, remember to send your input for the HLDesc, as agreed during our last interlock, by noon CET today -- to let others review it before our conf call tomorrow (11am CET). I will also try to merge the inputs into the new template/outline later today. Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE HLDesc Cloud v0.1.doc Type: application/octet-stream Size: 586240 bytes Desc: not available URL: From jhierro at tid.es Mon May 23 10:59:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 23 May 2011 10:59:33 +0200 Subject: [Fiware-cloud] [Fiware-tools] Template for FI-WARE documents (including template for deliverables) available in documentation management tool In-Reply-To: <4DDA212E.1090208@eng.it> References: <4DD28BC7.9020607@tid.es> <4DDA212E.1090208@eng.it> Message-ID: <4DDA21F5.6020709@tid.es> Point taken. We'll prepare something. On 23/05/11 10:56, Davide Dalle Carbonare wrote: Dear Juanjo, is there an already selected license to apply to the public documents? I think it would be useful for everyone to have it in the next template version. thank you and Best Regards, Davide On 17/05/2011 16.52, Juanjo Hierro wrote: Dear colleagues, The document management tool is now finally configured so that we are now able to use it for sharing documents. I'll send you a brief document describing how it works in order to upload/publish documents later this evening. In the meantime, let me share with you the template we would like you to follow for creating FI-WARE documents. You can download it from: http://forge.fi-ware.eu/docman/view.php/7/42/FI-WARE+Public+Document+template+11-05-17.doc You may also find a template for meeting minutes useful. You can download it from: http://forge.fi-ware.eu/docman/view.php/7/41/FI-WARE+Minutes+template+11-05-17.doc Both documents are private, so that only users properly registered in the FI-WARE project in the FI-WARE FusionForge will be able to download them :-) I hope this will persuade most of you to register in the FI-WARE project @ FusionForge if you haven't still done so :-) A mail reminding to register with a detailed (updated) description of steps to be followed will arrive to you in the next message. 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-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From serge.defrance at technicolor.com Mon May 23 11:46:15 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Mon, 23 May 2011 11:46:15 +0200 Subject: [Fiware-cloud] Cloud HLDesc -- overview, GEs, hosting of VMs In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E44C9C330@MOPESMBX01.eu.thmulti.com> Hi Alex and all, Please find here below a provisional proposal for the chapter "Cloud Edge": 1? Cloud Proxy 1.1 definition and why (manage relationship with home devices and cloud, offer local computing and storage) 1.2 use cases 1.2.1 from cloud to user 1.2.2 from user to cloud 1.2.3 peer-assisted application 2? Functions of the cloud proxy 1.1 Home network organization 1.2 Virtualization 1.3 Communications with the cloud Hear you tomorrow, 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: lundi 23 mai 2011 09:57 To: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-cloud] Cloud HLDesc -- overview, GEs, hosting of VMs All, Please, see attached my initial input to the HLDesc. Comments are welcome. Please, remember to send your input for the HLDesc, as agreed during our last interlock, by noon CET today -- to let others review it before our conf call tomorrow (11am CET). I will also try to merge the inputs into the new template/outline later today. Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Mon May 23 12:04:19 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Mon, 23 May 2011 11:04:19 +0100 Subject: [Fiware-cloud] T4.1 Descr. Message-ID: All, Attached is the initial draft high level description that pertains to T4.1 that can be used for our ongoing discussions. There are a number of TODOs within the documents that will be iterated over in the follows days. Andy -------------- next part -------------- A non-text attachment was scrubbed... Name: t4.1-hl-descr.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 26952 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From jsalvachua at dit.upm.es Mon May 23 12:03:36 2011 From: jsalvachua at dit.upm.es (Joaquin Salvachua) Date: Mon, 23 May 2011 12:03:36 +0200 Subject: [Fiware-cloud] Cloud HLDesc -- overview, GEs, hosting of VMs In-Reply-To: References: Message-ID: <12E30ACC-E57F-44B9-98EC-8C20A3739400@dit.upm.es> Hello, Here i include an initial input from UPM. There is some parts that needs collaboration from TID. Best Regards Joaqu?n El 23/05/2011, a las 09:57, Alex Glikson escribi?: > All, > > Please, see attached my initial input to the HLDesc. Comments are welcome. > Please, remember to send your input for the HLDesc, as agreed during our last interlock, by noon CET today -- to let others review it before our conf call tomorrow (11am CET). I will also try to merge the inputs into the new template/outline later today. > > 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-WAREPortal.doc Type: application/msword Size: 47104 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From joaquin.salvachua at upm.es Mon May 23 12:09:48 2011 From: joaquin.salvachua at upm.es (Joaquin Salvachua) Date: Mon, 23 May 2011 12:09:48 +0200 Subject: [Fiware-cloud] T4.1 Descr. In-Reply-To: References: Message-ID: Hello, Here i include an initial input from UPM. There is some parts that needs collaboration from TID. Best Regards Joaqu?n -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WAREPortal.doc Type: application/msword Size: 47104 bytes Desc: not available URL: -------------- next part -------------- ------------------------------------------------------------------------ Joaquin Salvachua tel: +34 91 549 57 00 x.3026 Associated Professor +34 91 549 57 62 x.3026 dpt. Telematica E.T.S.I. Telecomunicacion Ciudad Universitaria S/N fax: +34 91 336 73 33 E-28040 MADRID SPAIN mailto:jsalvachua at dit.upm.es // http://www.dit.upm.es/~jsr Blog: http://jsalvachua.blogspot.com/ -------------------------------------------------------------------------- From joaquin.salvachua at upm.es Mon May 23 12:19:19 2011 From: joaquin.salvachua at upm.es (Joaquin Salvachua) Date: Mon, 23 May 2011 12:19:19 +0200 Subject: [Fiware-cloud] T4.1 Descr. Message-ID: <7BF2180B-A33D-49D3-B6B8-AF46647E8618@upm.es> Hello, After some minor problems with the mailing list, here i include an initial input from UPM. There is some parts that needs collaboration from TID. Best Regards Joaqu?n ------------------------------------------------------------------------ Joaquin Salvachua tel: +34 91 549 57 00 x.3026 Associated Professor +34 91 549 57 62 x.3026 dpt. Telematica E.T.S.I. Telecomunicacion Ciudad Universitaria S/N fax: +34 91 336 73 33 E-28040 MADRID SPAIN mailto:jsalvachua at dit.upm.es // http://www.dit.upm.es/~jsr Blog: http://jsalvachua.blogspot.com/ -------------------------------------------------------------------------- ------------------------------------------------------------------------ Joaquin Salvachua tel: +34 91 549 57 00 x.3026 Associated Professor +34 91 549 57 62 x.3026 dpt. Telematica E.T.S.I. Telecomunicacion Ciudad Universitaria S/N fax: +34 91 336 73 33 E-28040 MADRID SPAIN mailto:jsalvachua at dit.upm.es // http://www.dit.upm.es/~jsr Blog: http://jsalvachua.blogspot.com/ -------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WAREPortal.doc Type: application/msword Size: 47104 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From Denis.Caromel at sophia.inria.fr Mon May 23 20:56:34 2011 From: Denis.Caromel at sophia.inria.fr (Denis Caromel) Date: Mon, 23 May 2011 20:56:34 +0200 Subject: [Fiware-cloud] FI-Ware Cloud Hosting [WP4] conf call & some logistics In-Reply-To: References: Message-ID: <4DDAADE2.6030806@sophia.inria.fr> Dear all, It is my pleasure to introduce: Brian Amedro , in cc. a senior researcher in my team at INRIA Sophia Antipolis that will work on the FI-Ware project with me. Alex, Can you add Brian to the WP 4 mailing list ? Thanks very much in advance, Best regards, Denis On 11/05/2011 09:59, Alex Glikson wrote: > Dear All, > > It was pleasure to meet you in Madrid! > > First, it seems that it could be a good idea to have a more instant channel > to communicate than email.. My Skype username is alex.glikson -- feel free > to add me to your contact list, and to send me your details (we can then > consolidate the contact details on the private Wiki, once it is ready). > > Moreover, those of you who attended the closing session on Friday, might > have noticed that we have plenty of work for the upcoming weeks, in order > to come up with the M2 deliverable on time (first release of the High Level > Description). In particular, it seems necessary now to start having weekly > calls to track our progress, to discuss open questions, etc. > You should have received a Doodle pool notification, for our first > conference call. > PLEASE, NOTICE THE TIME ZONE! (there is a drop-down to choose yours). The > first proposed time slot is tomorrow (Thursday), 5-6pm Israeli time, which > is 4-5pm CET. > > Also, let me introduce Marina Biberstein and David Breitgand from IBM, who > will be actively contributing to the Cloud Hosting work. > Please, let me know if there is anyone from your company who should be > added to (or removed from) the conf call invitation (and further email > exchange -- which would be done via a mailing list once it is ready). > > Regards, > Alex > -- Denis Caromel mailto:caromel at unice.fr Tel.: +33 49 238 7631 Fax: 7644 Professor http://www-sop.inria.fr/oasis/caromel IUF, Institut universitaire de France Univ. de Nice Sophia Antipolis INRIA, 2004 Rt. des Lucioles,BP93 OASIS, INRIA - I3S CNRS - UNSA F-06902 Sophia Antipolis Cedex From fla at tid.es Tue May 24 00:36:02 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 24 May 2011 00:36:02 +0200 Subject: [Fiware-cloud] T4.4 and T4.5 Descr. In-Reply-To: <7BF2180B-A33D-49D3-B6B8-AF46647E8618@upm.es> References: <7BF2180B-A33D-49D3-B6B8-AF46647E8618@upm.es> Message-ID: Dear all, I just the integration of TID together with the contribution of UPM in this Task. Note that I do not have all the contributions (including myself). Sorry for my delay. See you in T4.4 and T4.5 contributions (TID) (Deliverable x v0.1.doc) 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] El 23/05/2011, a las 12:19, Joaquin Salvachua escribi?: Hello, After some minor problems with the mailing list, here i include an initial input from UPM. There is some parts that needs collaboration from TID. Best Regards Joaqu?n ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: From GLIKSON at il.ibm.com Tue May 24 11:00:25 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 24 May 2011 12:00:25 +0300 Subject: [Fiware-cloud] Cloud Hosting HLDesc - Optimization Message-ID: Attached David's contribution to the "optimization" part of task 4.4 -- for technical reasons, it was not merged yet. Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Deliverable x.doc Type: application/octet-stream Size: 2850304 bytes Desc: not available URL: From GLIKSON at il.ibm.com Thu May 26 18:35:37 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 26 May 2011 19:35:37 +0300 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes Message-ID: Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome. Also, see attached the latest version of the HLDesc template. As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them. Regards, Alex Attendees: IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT Agenda: Generic Enablers HLDesc progress Minutes: List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS) Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template Action Items: For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30. 3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge. Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE HLDesc Cloud v0.1.doc Type: application/octet-stream Size: 612864 bytes Desc: not available URL: From fla at tid.es Tue May 31 01:47:19 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 31 May 2011 01:47:19 +0200 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes In-Reply-To: References: Message-ID: <311A9AD2-4C23-41ED-87F5-4C608FC46427@tid.es> Dear all, I was checking the GE and the relationships between all of them. I suggest to review it with the following updates. - We prefer to change the name of "Hosting of VM-Based services" to "Service Management" due to it reflects more appropriately the functionality. * Within this GE (compound basically by Claudia assets), we can find the functionality of Autoscaling, Lifecycle Management and Image processing. * Image Processing is a VM Image Manager that will be used by the PaaS (see bellow). * The functionality of the Autoscaling is provided autoscale functionality of the VM. In case of the PaaS autoscaling, we have to define specific functionality (see bellow). * Other functionality, that we need to put here, is the Federation & Interoperability part. - PaaS, is something more complex to be managed. It creates the Virtual Appliance and manages the different products that the services will need * PaaS needs also autoscaling, but we can see it compounded by 2 different parts. The first one manages the configuration of the platforms (DB, Web Server, etc...) that it is needed in a Platform. Meanwhile, the autoscaling part of the Service Management will be the functional block that realizes the real autoscale of the VM, based on this configuration information. * The name of Hosting of Application Containers is not very appropriate in this case due to PaaS is not a Platform Container itself. It tries to manage automatically the virtualization of the different components needed by an application, for example DB or Web Server. We see more appropriate the term "Platform Management (PaaS)" here. * The scalability is applied both PaaS level and Service Management level, cue to we need to reconfigure the different platforms in which our services will be scaled furthermore. * The same have to be applied to the monitoring in which we have to take into consideration both the services KPIs in the Service Management and the PaaS KPIs in the Platform part. - Regarding the SLO Mgmt, I am not sure why you put the name of this GE to SLO and not to SLA, we consider it would the more general view if we consider SLA and not the part of it. What was the reason to adopt it? * We have to considerer the different rules defined by the users through the Elasticity Rules, QoS and/or Business Criteria. If we consider this elasticity rules like SLA or related to the SLA then we need to put a relationship between the SLA and the autoscaling functionality. - Object Storage, in this case we do not see directly what is the reason that we have to put direct connection between Self-Service Interface and it, maybe due to you have to put here protocols like CDMI? Anything else? Continue with this GE we see that it is needed a connection between Object Storage and the Hosting of VM in order to access to the data objects. - Regarding the Policy-Driven Local and cross-data centre optimization. Question here is that it is related to the placement concept? in which GE can we put this functional block? - Finally, accounting and billing, we see it like a transversal component not specified here but related to all piece of the Cloud Hosting. [cid:70C132DC-5470-41ED-886A-FC0C45E26895] 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 26/05/2011, a las 18:35, Alex Glikson escribi?: Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome. Also, see attached the latest version of the HLDesc template. As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them. Regards, Alex Attendees: * IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT Agenda: * Generic Enablers * HLDesc progress Minutes: * List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS) * Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template Action Items: * For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30. * 3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge. * Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE * ________________________________ 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: GE.png Type: image/png Size: 250731 bytes Desc: GE.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: From GLIKSON at il.ibm.com Tue May 31 09:09:10 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 31 May 2011 10:09:10 +0300 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes In-Reply-To: <311A9AD2-4C23-41ED-87F5-4C608FC46427@tid.es> References: <311A9AD2-4C23-41ED-87F5-4C608FC46427@tid.es> Message-ID: Fernando -- thanks for insightful comments! All, We need to start thinking about the capabilities that we provide to our users -- those who would directly consume the GEs (e.g., UC project developer, Cloud Hosting provider), rather than functional components. GEs should represent groups of requirements, exposed externally. I know it is not easy, but all of us need to do this mental switch. For example, "service management" is a component, bit it is not necessarily a GE. What a UC developer will be looking for is the capability to host his (multi-VM) services somewhere. We know that this capability is provided by the Service Management component, on top of pool management, VM resource management, hypervisors, etc. But HLDesc should focus on the users and the capabilities we provide them, rather than on internal components - at least for now. Similarly, "platform management" is a component, rather than a GE The user doesn't really need to know that it runs on top of VMs, manages those VMs in a certain way, etc. Those details are important, but not at this level. I had a similar discussion yesterday with Andy regarding internal components of VM hosting GE -- what the users (or other GEs using VM hosting) are really interested in, is to be able to host their VMs. Whether or not there is a component called "node manager" somewhere underneath -- they probably wouldn't care much. Same for monitoring -- unless we refer to some unique monitoring capabilities that we provide externally, like the Amazon's CloudWatch (which I don't know if we plan to do). So, being Agile, let's focus on the needs of the target audience of the HLDesc -- which is mainly UC projects and wider audience interested in capabilities, and not internals. Regarding auto-scaling, and whether or not it should be a separate GE.. I don't mind merging them, and specifying 'auto-scaling' as one of the (optional) functions provided by the (compound) service hosting GE. SLAs vs SLOs -- "SLA" is a business/legal term, while what we provide is the infrastructure to monitor & enforce the *objectives* derived fro those *agreements*. Object Storage -- this is analogous to Amazon S3. It is a service that is surfaced separately, not necessarily related to VM hosting. VM hosting can use Object Storage -- as anyone else, internal or external to Cloud Hosting offering (we could consider some optimization for internal access -- but I think this is far beyond the level of details that we currently need). policy-driven optimization -- I see it as a part of the VM hosting GE. Let me know if you think differently. Accounting and billing -- the business side of this should be provided by WP3. On the infrastructure side -- what functions do you envision besides resource usage metering? BTW, I assume we might want to elaborate on this further once someone from FT (who is associated with this function) joins the discussion and the HLDesc effort. As discussed in our last meeting, the inter-relationships between auto-scaling, service hosting and application container hosting should be more flexible than on my original diagram. See below an updated version of the diagram. Comments are welcome! From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 31/05/2011 02:47 AM Subject: Re: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes Dear all, I was checking the GE and the relationships between all of them. I suggest to review it with the following updates. - We prefer to change the name of "Hosting of VM-Based services" to "Service Management" due to it reflects more appropriately the functionality. * Within this GE (compound basically by Claudia assets), we can find the functionality of Autoscaling, Lifecycle Management and Image processing. * Image Processing is a VM Image Manager that will be used by the PaaS (see bellow). * The functionality of the Autoscaling is provided autoscale functionality of the VM. In case of the PaaS autoscaling, we have to define specific functionality (see bellow). * Other functionality, that we need to put here, is the Federation & Interoperability part. - PaaS, is something more complex to be managed. It creates the Virtual Appliance and manages the different products that the services will need * PaaS needs also autoscaling, but we can see it compounded by 2 different parts. The first one manages the configuration of the platforms (DB, Web Server, etc...) that it is needed in a Platform. Meanwhile, the autoscaling part of the Service Management will be the functional block that realizes the real autoscale of the VM, based on this configuration information. * The name of Hosting of Application Containers is not very appropriate in this case due to PaaS is not a Platform Container itself. It tries to manage automatically the virtualization of the different components needed by an application, for example DB or Web Server. We see more appropriate the term "Platform Management (PaaS)" here. * The scalability is applied both PaaS level and Service Management level, cue to we need to reconfigure the different platforms in which our services will be scaled furthermore. * The same have to be applied to the monitoring in which we have to take into consideration both the services KPIs in the Service Management and the PaaS KPIs in the Platform part. - Regarding the SLO Mgmt, I am not sure why you put the name of this GE to SLO and not to SLA, we consider it would the more general view if we consider SLA and not the part of it. What was the reason to adopt it? * We have to considerer the different rules defined by the users through the Elasticity Rules, QoS and/or Business Criteria. If we consider this elasticity rules like SLA or related to the SLA then we need to put a relationship between the SLA and the autoscaling functionality. - Object Storage, in this case we do not see directly what is the reason that we have to put direct connection between Self-Service Interface and it, maybe due to you have to put here protocols like CDMI? Anything else? Continue with this GE we see that it is needed a connection between Object Storage and the Hosting of VM in order to access to the data objects. - Regarding the Policy-Driven Local and cross-data centre optimization. Question here is that it is related to the placement concept? in which GE can we put this functional block? - Finally, accounting and billing, we see it like a transversal component not specified here but related to all piece of the Cloud Hosting. 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 26/05/2011, a las 18:35, Alex Glikson escribi?: Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome. Also, see attached the latest version of the HLDesc template. As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them. Regards, Alex Attendees: IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT Agenda: Generic Enablers HLDesc progress Minutes: List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS) Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template Action Items: For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30. 3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge. Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE 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: not available Type: image/gif Size: 18223 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 250731 bytes Desc: not available URL: From GLIKSON at il.ibm.com Tue May 31 10:01:09 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 31 May 2011 11:01:09 +0300 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes In-Reply-To: References: Message-ID: All, Please, see below the current version of the document. Based on the mail exchange, I've updated a bit the GEs diagram (even further than the draft I sent earlier in a mail), and also the corresponding subsections. Now we have 5 sections under 'GEs' (IaaS, PaaS, Composite Services, Storage and Cloud Edge), and 2 sections under 'non-functional' (interfaces and SLOs -- need to see if we need more). A kind reminder to everyone to send their input (the deadline was EOD yesterday -- please, make an effort to send it before the call today). Please, make sure you follow the editing conventions specified on pages 2-4 (I removed them in the previous draft -- now they are present again, for everyone's convenience). In particular, no copy-paste with formatting from other programs/documents (only paste as unformatted text). Thanks, Alex From: Alex Glikson/Haifa/IBM To: fiware-cloud at lists.fi-ware.eu Date: 26/05/2011 07:35 PM Subject: 24-May-2011 weekly conf call -- minutes Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome. Also, see attached the latest version of the HLDesc template. As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them. Regards, Alex Attendees: IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT Agenda: Generic Enablers HLDesc progress Minutes: List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS) Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template Action Items: For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30. 3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge. Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE HLDesc Cloud v0.2.doc Type: application/octet-stream Size: 832512 bytes Desc: not available URL: From DAVIDBR at il.ibm.com Tue May 31 10:46:22 2011 From: DAVIDBR at il.ibm.com (David Breitgand) Date: Tue, 31 May 2011 11:46:22 +0300 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes In-Reply-To: References: <311A9AD2-4C23-41ED-87F5-4C608FC46427@tid.es> Message-ID: Hi All, To add my two cents on this insightful thread: 1) >> Regarding auto-scaling, and whether or not it should be a separate GE.. I don't mind merging them, and specifying 'auto-scaling' as one of the (optional) functions provided by the (compound) service hosting GE. >> Will auto-scaling in Fi-WARE only refer to the horizontal scaling or also to the vertical one? 2) I believe the second diagram better positions SLO management GE as a set functional capabilities that can be optionally used by a provider who builds a cloud solution, to protect compound services and individual VMs. I wonder whether we envision SLOs associated with the ObjectStore. I think to put us on par with the competition there should be such SLOs. 3) I argue in favor of a separate Autoscaling GE. This is a functionality that user is directly exposed to (see EC2) and thus should not be treated as an internal component. 4) GE are of two types: (1) GEs that embody functionality directly consumable by the users of a cloud solution and (2) GEs that are used by the providers of a Cloud solution. As an example consider GE that deals with capacity management that comprises over-booking management, reservation management, capacity planning. 5) "Image Processing" is not a good term in our context. This term is used for visual signal processing. We should use the term "Image Management". Image Management is n example of GE that embodies functionality that the users are exposed to (e.g., image catalog) and internal management functionality that is required to manage image library efficiently. 6) >>- Regarding the Policy-Driven Local and cross-data centre optimization. Question here is that it is related to the placement concept? in which GE can we put this functional block? " Yes, the optimization is performed by the placement engine. This engine is an example of GE that is not visible to the Cloud user, but to the Cloud provider. Cheers. -- 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: Alex Glikson/Haifa/IBM at IBMIL To: "fiware-cloud at lists.fi-ware.eu" Date: 31/05/2011 10:09 AM Subject: Re: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes Sent by: fiware-cloud-bounces at lists.fi-ware.eu Fernando -- thanks for insightful comments! All, We need to start thinking about the capabilities that we provide to our users -- those who would directly consume the GEs (e.g., UC project developer, Cloud Hosting provider), rather than functional components. GEs should represent groups of requirements, exposed externally. I know it is not easy, but all of us need to do this mental switch. For example, "service management" is a component, bit it is not necessarily a GE. What a UC developer will be looking for is the capability to host his (multi-VM) services somewhere. We know that this capability is provided by the Service Management component, on top of pool management, VM resource management, hypervisors, etc. But HLDesc should focus on the users and the capabilities we provide them, rather than on internal components - at least for now. Similarly, "platform management" is a component, rather than a GE The user doesn't really need to know that it runs on top of VMs, manages those VMs in a certain way, etc. Those details are important, but not at this level. I had a similar discussion yesterday with Andy regarding internal components of VM hosting GE -- what the users (or other GEs using VM hosting) are really interested in, is to be able to host their VMs. Whether or not there is a component called "node manager" somewhere underneath -- they probably wouldn't care much. Same for monitoring -- unless we refer to some unique monitoring capabilities that we provide externally, like the Amazon's CloudWatch (which I don't know if we plan to do). So, being Agile, let's focus on the needs of the target audience of the HLDesc -- which is mainly UC projects and wider audience interested in capabilities, and not internals. Regarding auto-scaling, and whether or not it should be a separate GE.. I don't mind merging them, and specifying 'auto-scaling' as one of the (optional) functions provided by the (compound) service hosting GE. SLAs vs SLOs -- "SLA" is a business/legal term, while what we provide is the infrastructure to monitor & enforce the *objectives* derived fro those *agreements*. Object Storage -- this is analogous to Amazon S3. It is a service that is surfaced separately, not necessarily related to VM hosting. VM hosting can use Object Storage -- as anyone else, internal or external to Cloud Hosting offering (we could consider some optimization for internal access -- but I think this is far beyond the level of details that we currently need). policy-driven optimization -- I see it as a part of the VM hosting GE. Let me know if you think differently. Accounting and billing -- the business side of this should be provided by WP3. On the infrastructure side -- what functions do you envision besides resource usage metering? BTW, I assume we might want to elaborate on this further once someone from FT (who is associated with this function) joins the discussion and the HLDesc effort. As discussed in our last meeting, the inter-relationships between auto-scaling, service hosting and application container hosting should be more flexible than on my original diagram. See below an updated version of the diagram. Comments are welcome! From: FERNANDO LOPEZ AGUILAR To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" Date: 31/05/2011 02:47 AM Subject: Re: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes Dear all, I was checking the GE and the relationships between all of them. I suggest to review it with the following updates. - We prefer to change the name of "Hosting of VM-Based services" to "Service Management" due to it reflects more appropriately the functionality. * Within this GE (compound basically by Claudia assets), we can find the functionality of Autoscaling, Lifecycle Management and Image processing. * Image Processing is a VM Image Manager that will be used by the PaaS (see bellow). * The functionality of the Autoscaling is provided autoscale functionality of the VM. In case of the PaaS autoscaling, we have to define specific functionality (see bellow). * Other functionality, that we need to put here, is the Federation & Interoperability part. - PaaS, is something more complex to be managed. It creates the Virtual Appliance and manages the different products that the services will need * PaaS needs also autoscaling, but we can see it compounded by 2 different parts. The first one manages the configuration of the platforms (DB, Web Server, etc...) that it is needed in a Platform. Meanwhile, the autoscaling part of the Service Management will be the functional block that realizes the real autoscale of the VM, based on this configuration information. * The name of Hosting of Application Containers is not very appropriate in this case due to PaaS is not a Platform Container itself. It tries to manage automatically the virtualization of the different components needed by an application, for example DB or Web Server. We see more appropriate the term "Platform Management (PaaS)" here. * The scalability is applied both PaaS level and Service Management level, cue to we need to reconfigure the different platforms in which our services will be scaled furthermore. * The same have to be applied to the monitoring in which we have to take into consideration both the services KPIs in the Service Management and the PaaS KPIs in the Platform part. - Regarding the SLO Mgmt, I am not sure why you put the name of this GE to SLO and not to SLA, we consider it would the more general view if we consider SLA and not the part of it. What was the reason to adopt it? * We have to considerer the different rules defined by the users through the Elasticity Rules, QoS and/or Business Criteria. If we consider this elasticity rules like SLA or related to the SLA then we need to put a relationship between the SLA and the autoscaling functionality. - Object Storage, in this case we do not see directly what is the reason that we have to put direct connection between Self-Service Interface and it, maybe due to you have to put here protocols like CDMI? Anything else? Continue with this GE we see that it is needed a connection between Object Storage and the Hosting of VM in order to access to the data objects. - Regarding the Policy-Driven Local and cross-data centre optimization. Question here is that it is related to the placement concept? in which GE can we put this functional block? - Finally, accounting and billing, we see it like a transversal component not specified here but related to all piece of the Cloud Hosting. 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 26/05/2011, a las 18:35, Alex Glikson escribi?: Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome. Also, see attached the latest version of the HLDesc template. As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them. Regards, Alex Attendees: IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT Agenda: Generic Enablers HLDesc progress Minutes: List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS) Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template Action Items: For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30. 3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge. Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 18223 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 250731 bytes Desc: not available URL: From fla at tid.es Tue May 31 11:01:23 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 31 May 2011 11:01:23 +0200 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes In-Reply-To: References: <311A9AD2-4C23-41ED-87F5-4C608FC46427@tid.es> Message-ID: <54909EE1-71B8-43B3-891E-EBEA6574FFC4@tid.es> Dear Alex, Thank you very much for your answer, I think that I can now understand your point of view in a better way. My comments inline. 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/05/2011, a las 09:09, Alex Glikson escribi?: Fernando -- thanks for insightful comments! All, We need to start thinking about the capabilities that we provide to our users -- those who would directly consume the GEs (e.g., UC project developer, Cloud Hosting provider), rather than functional components. GEs should represent groups of requirements, exposed externally. I know it is not easy, but all of us need to do this mental switch. For example, "service management" is a component, bit it is not necessarily a GE. What a UC developer will be looking for is the capability to host his (multi-VM) services somewhere. We know that this capability is provided by the Service Management component, on top of pool management, VM resource management, hypervisors, etc. But HLDesc should focus on the users and the capabilities we provide them, rather than on internal components - at least for now. Similarly, "platform management" is a component, rather than a GE The user doesn't really need to know that it runs on top of VMs, manages those VMs in a certain way, etc. Those details are important, but not at this level. I had a similar discussion yesterday with Andy regarding internal components of VM hosting GE -- what the users (or other GEs using VM hosting) are really interested in, is to be able to host their VMs. Whether or not there is a component called "node manager" somewhere underneath -- they probably wouldn't care much. Same for monitoring -- unless we refer to some unique monitoring capabilities that we provide externally, like the Amazon's CloudWatch (which I don't know if we plan to do). So, being Agile, let's focus on the needs of the target audience of the HLDesc -- which is mainly UC projects and wider audience interested in capabilities, and not internals. OK, I?ll try to make the mental switch.. so by now focusing on capabilities from the ?user? perspective. Regarding auto-scaling, and whether or not it should be a separate GE.. I don't mind merging them, and specifying 'auto-scaling' as one of the (optional) functions provided by the (compound) service hosting GE. SLAs vs SLOs -- "SLA" is a business/legal term, while what we provide is the infrastructure to monitor & enforce the *objectives* derived fro those *agreements*. OK, yes, I agree that we can call it SLA or SLO, it is just that calling SLA is more known out there, but I don?t have a problem here. No a strong opinion about the name. Object Storage -- this is analogous to Amazon S3. It is a service that is surfaced separately, not necessarily related to VM hosting. VM hosting can use Object Storage -- as anyone else, internal or external to Cloud Hosting offering (we could consider some optimization for internal access -- but I think this is far beyond the level of details that we currently need). OK, I see. policy-driven optimization -- I see it as a part of the VM hosting GE. Let me know if you think differently. In my view is more part of the Hosting of compound services, a layer up that is able to decide which concrete VM hosting to use. But we can go more into the capabilities specification and then decide where it fits better. Accounting and billing -- the business side of this should be provided by WP3. On the infrastructure side -- what functions do you envision besides resource usage metering? BTW, I assume we might want to elaborate on this further once someone from FT (who is associated with this function) joins the discussion and the HLDesc effort. Yes, probably will be the reporting of usage metering, anyway it is something that we need to elaborate more, and as you say see the interactions with the WP3 and their needs. And of course, I am completely agree with you that it is part of the FT interest within the Hosting Cloud WP. We hope that someone from them could give us more details about it. As discussed in our last meeting, the inter-relationships between auto-scaling, service hosting and application container hosting should be more flexible than on my original diagram. See below an updated version of the diagram. Comments are welcome! Just the only comment now is that we do not understand very well the position of the Hosting of Compund Services and the Hosting of Application Containers. We see it change in the order shown in the figure. From: FERNANDO LOPEZ AGUILAR > To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-cloud at lists.fi-ware.eu" > Date: 31/05/2011 02:47 AM Subject: Re: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes ________________________________ Dear all, I was checking the GE and the relationships between all of them. I suggest to review it with the following updates. - We prefer to change the name of "Hosting of VM-Based services" to "Service Management" due to it reflects more appropriately the functionality. * Within this GE (compound basically by Claudia assets), we can find the functionality of Autoscaling, Lifecycle Management and Image processing. * Image Processing is a VM Image Manager that will be used by the PaaS (see bellow). * The functionality of the Autoscaling is provided autoscale functionality of the VM. In case of the PaaS autoscaling, we have to define specific functionality (see bellow). * Other functionality, that we need to put here, is the Federation & Interoperability part. - PaaS, is something more complex to be managed. It creates the Virtual Appliance and manages the different products that the services will need * PaaS needs also autoscaling, but we can see it compounded by 2 different parts. The first one manages the configuration of the platforms (DB, Web Server, etc...) that it is needed in a Platform. Meanwhile, the autoscaling part of the Service Management will be the functional block that realizes the real autoscale of the VM, based on this configuration information. * The name of Hosting of Application Containers is not very appropriate in this case due to PaaS is not a Platform Container itself. It tries to manage automatically the virtualization of the different components needed by an application, for example DB or Web Server. We see more appropriate the term "Platform Management (PaaS)" here. * The scalability is applied both PaaS level and Service Management level, cue to we need to reconfigure the different platforms in which our services will be scaled furthermore. * The same have to be applied to the monitoring in which we have to take into consideration both the services KPIs in the Service Management and the PaaS KPIs in the Platform part. - Regarding the SLO Mgmt, I am not sure why you put the name of this GE to SLO and not to SLA, we consider it would the more general view if we consider SLA and not the part of it. What was the reason to adopt it? * We have to considerer the different rules defined by the users through the Elasticity Rules, QoS and/or Business Criteria. If we consider this elasticity rules like SLA or related to the SLA then we need to put a relationship between the SLA and the autoscaling functionality. - Object Storage, in this case we do not see directly what is the reason that we have to put direct connection between Self-Service Interface and it, maybe due to you have to put here protocols like CDMI? Anything else? Continue with this GE we see that it is needed a connection between Object Storage and the Hosting of VM in order to access to the data objects. - Regarding the Policy-Driven Local and cross-data centre optimization. Question here is that it is related to the placement concept? in which GE can we put this functional block? - Finally, accounting and billing, we see it like a transversal component not specified here but related to all piece of the Cloud Hosting. 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 26/05/2011, a las 18:35, Alex Glikson escribi?: Please, see below the summary of the conf call we had this Tuesday. Your comments are welcome. Also, see attached the latest version of the HLDesc template. As discussed, I haven't integrated your contributions -- please, send them in the new HLDesc format by next Monday, and I will then integrate them. Regards, Alex Attendees: * IBM (Alex, David, Marina), TID (Fernando), Intel (Andy), TRDF (Serge), UPM (Juaquin et al). Missing: INRIA, FT Agenda: * Generic Enablers * HLDesc progress Minutes: * List of GEs was reviewed. Relationships between the GEs might need to be adjusted (e.g., between PaaS and SM. also, auto-scaling might be used generically on top of PaaS or IaaS) * Each partner sent their updates to the document. Next steps is to align it with the GEs structure, as well as with the HLDesc template Action Items: * For each of the Generic Enablers, the corresponding partners will send an updated draft of the corresponding section of the HLDesc (3.1.2.x), according to the guidelines provided within the template (document attached below). They will also include a list of terms relevant for their GE, as well as open questions that would need to be addressed. The materials will be sent to the mailing list, by EOD Monday, May 30. * 3.1.2.1 (Hosting of VMs) -- Alex & Andy, 3.1.2.2 (Hosting of VM-based Services) -- Fernando, 3.1.2.3 (Auto-Scaling) -- Fernando, 3.1.2.4 (SLO management) - David, 3.1.2.5 (Object Storage) - Andy, 3.1.2.6 (PaaS) - Fernando, 3.1.2.7 (Cloud Edge) - Serge. * Alex and Andy to meet separately to discuss the collaboration on the HLDesc section describing "Hosting of VMs" GE ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 66394 bytes Desc: PastedGraphic-1.tiff URL: From GLIKSON at il.ibm.com Tue May 31 12:28:35 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 31 May 2011 13:28:35 +0300 Subject: [Fiware-cloud] 31-May-2011 weekly conf call -- minutes Message-ID: Thanks to everyone who attended the call. Please, see below a brief summary -- please, let me know if there is anything wrong or missing. Thanks, Alex Meeting details: 31/5, 11:00-12:00 CET, conf call Attendees: IBM, Telefonica, Intel, Technicolor, UPM Agenda: HLDesc progress Update on interlock with Juanjo Minutes: The latest set of (functional) GEs was reviewed. It was discussed what should be the goal of grouping functions and capabilities into GEs (requirements management, user-oriented), granularity, etc. The monitoring function was mentioned as important for several GEs and capabilities (provider credibility, SLOs, metering & billing). Need to elaborate on it more. It was identified that there are many important cross-GE functions and capabilities -- such as interfaces, monitoring, SLOs, security, etc. Some of which also have some exposure to the end-user. We will need to make sure that these areas are properly (and consistently) covered by the individual GE sections, and have a brief overview of these areas separately in the document (in a section parallel to GEs). Juanjo has asked for an integrated draft of the HLDesc for an initial review Juanjo promised to follow-up with FT to identify their representative for Cloud WP. This will also have implications on the corresponding HLDesc content, in the areas related to metering, accounting, billing, etc. The role of INRIA was discussed with Juanjo. It was mentioned that as a scientific partner, INRIA will be expected to contribute to the state of the art and technology blogs, as well as the corresponding reports. Regarding the particular asset that was presented during the kickoff (ProActive) -- we will need to see whether it bridges any particular gap that will be identify during the requirements gathering phase. Action Items: Alex will mark in the HLDesc the owners of the individual sub-sections (note that additional partners may contribute) Alex -- Overview, IaaS Fernando -- PaaS, Compound Services, Interfaces & Interoperability Andy -- Storage, contribution to IaaS, Monitoring Juaquin -- Interfaces (portal) Serge -- Cloud Proxy David -- SLOs TBD (need a volunteer) -- security other cross-GE aspects? Everyone will send their HLDesc contributions by the end of the day (31/5). Then Alex will merge them and will send to Juanjo for review. We will be in touch by email to discuss next stage of contributions to the HLDesc -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewx.edmonds at intel.com Tue May 31 16:18:24 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 31 May 2011 15:18:24 +0100 Subject: [Fiware-cloud] SLO's, SLA's: SLA@SOI Architecture... Message-ID: Hi all, During the today's confcall, I made references to the SLA at SOI architecture (Section 3.4 is a good place to start). If you want more information, then you will find much information here [1]. If you have any questions, let me know and will help as best as is possible. There is also more information here [2]. HTH, Andy [1] http://sourceforge.net/apps/trac/sla-at-soi/export/1941/platform/trunk/doc/S LA%40SOI-Reference_Architecture.pdf [2] http://sourceforge.net/apps/trac/sla-at-soi/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From andrewx.edmonds at intel.com Tue May 31 16:21:49 2011 From: andrewx.edmonds at intel.com (Edmonds, AndrewX) Date: Tue, 31 May 2011 15:21:49 +0100 Subject: [Fiware-cloud] Virtualised Networking, Open vSwitch Message-ID: Fernado was asking me about pointers on information related to Open vSwitch, virtualized networking etc. If you have a similar interest these links [1] [2] [3] [4] [5] [6] [7] below might be of interest/help to you. Andy [1] http://www.openvswitch.org [2] @article{Pfaff:tu, author = {Pfaff, B and Pettit, J and Koponen, T and Amidon, K}, title = {{Extending networking into the virtualization layer}}, journal = {Proc. HotNets ( {\ldots}}, rating = {0}, date-added = {2011-05-01T20:18:58GMT+00:00}, date-modified = {2011-05-31T10:39:34GMT+00:00}, abstract = {ABSTRACT The move to virtualization has created a new network access layer residing on hosts that connects the various VMs. Virtualized deployment environments impose re- quirements on networking for which traditional models are not well suited. They also provide ...}, url = \url{http://conferences.sigcomm.org/hotnets/2009/papers/hotnets2009-final143 .pdf} } [3] http://www.xen.org/products/cloudxen.html [4] http://www.opennetworkingfoundation.org/?p=44 [5] http://blog.vcider.com/2011/05/sd-forums-virutal-network-presentation/ [6] @article{Rumble:uf, author = {Rumble, SM and Ongaro, D and Stutsman, R and Rosenblum, M}, title = {{It's Time for Low Latency}}, journal = {usenix.org}, rating = {0}, date-added = {2011-05-31T10:48:06GMT+00:00}, date-modified = {2011-05-31T10:48:55GMT+00:00}, abstract = {Abstract The operating systems community has ignored network latency for too long. In the past, speed-of-light delays in wide area networks and unoptimized network hard- ware have made sub-100is round-trip times impossible. However, in the next few years datacenters ...}, url = \url{https://www.usenix.org/events/hotos11/tech/final_files/Rumble.pdf} } [7] http://wiki.openstack.org/Quantum -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From fla at tid.es Tue May 31 23:41:11 2011 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Tue, 31 May 2011 23:41:11 +0200 Subject: [Fiware-cloud] 24-May-2011 weekly conf call -- minutes In-Reply-To: References: Message-ID: <5730275D-7A95-44DD-8897-EF1E2F3A9DBE@tid.es> Dear Alex et all, You can find in the attachment the version of TID based on the current versions of the document. ________________________________ 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: FIWARE HLDesc Cloud v0.2-TID.doc Type: application/msword Size: 882688 bytes Desc: FIWARE HLDesc Cloud v0.2-TID.doc 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: