From john.m.kennedy at intel.com Wed Jul 4 16:17:42 2012 From: john.m.kennedy at intel.com (Kennedy, John M) Date: Wed, 4 Jul 2012 14:17:42 +0000 Subject: [Fiware-cloud] Deliverable content now public for DCRM and OS GEs Message-ID: <70851B256BA35449A5ADF81F0FADF88115CF01DD@IRSMSX101.ger.corp.intel.com> Dear all, The deliverable content for the DCRM and OS GEs has now been ported from the private wiki to the following location on the public wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE The private wiki now just contains pointers to the public pages. If I made some mistake please let me know. Best, - John. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Mon Jul 9 08:02:44 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 9 Jul 2012 09:02:44 +0300 Subject: [Fiware-cloud] Fw: Fw: today's meeting Message-ID: Please, see below minutes from last week's meeting (4/7). Attendees: IBM, Intel, Technicolor, TID Guidelines to publish GEs in the catalogue have been published by WP9. Action Item [all]: review, raise questions if there is anything unclear There are new guidelines to upload binaries Action Item [Henk, Fernando]: upload binaries to 'PPP Restricted' SVN Status of deliverables: CP: all the deliverables (code, user & programmer guide, install & admin guide, test plan) are ready (I2ND section of the public wiki, SVN) Object Storage: guides are ready. other deliverables require interlock with the developer who implemented CDMI for Swift Action Item [John/Thijs]: follow-up with the developer who implemented CDMI for Swift, expedite readiness of code and test plan deliverables SM: programmer guide will be ready in 1 week. the rest of the deliverables are ready DCRM: all the deliverables are ready Action Item: need to move the guides to the public wiki DCRM/SM user guide -- status unknown Action Item [Alex]: follow-up with UPM Regards, Alex ----- Forwarded by Alex Glikson/Haifa/IBM on 04/07/2012 04:02 PM ----- From: Alex Glikson/Haifa/IBM at IBMIL To: "fiware-cloud at lists.fi-ware.eu" , Date: 27/06/2012 06:38 PM Subject: [Fiware-cloud] Fw: today's meeting Sent by: fiware-cloud-bounces at lists.fi-ware.eu Att: IBM, Intel, UPM, TID, INRIA Minutes: We welcome Thijs who joined the Intel team (replacing Andy) Some insights from last week's review Next review will be after month 18, in Seville (testbed). We will need to show things working. However, it is not clear what exactly can we demonstrate without use-cases. It is very important to meet the deadline of having testbed running with all the GEs by end of July No special comments regarding Cloud chapter were made Status of June deliverables was reviewed Action Item [Alex]: follow-up with Technicolor on Cloud Edge deliverables Action Item [all]: make sure all the deliverables are ready on time (at least drafts) Action Item [Alex]: check where the deliverables other than the test plan should be located. In particular, those which are not supposed to be publically available (unit testing plan and report is one of them, BTW) We should refer to existing materials whenever possible User guide for DCRM/SM will refer to WebUI ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 ----- Forwarded by Alex Glikson/Haifa/IBM on 27/06/2012 04:26 PM ----- From: Alex Glikson/Haifa/IBM at IBMIL To: "fiware-cloud at lists.fi-ware.eu" , Date: 27/06/2012 09:58 AM Subject: [Fiware-cloud] today's meeting Sent by: fiware-cloud-bounces at lists.fi-ware.eu Reminder -- please, complete the action items below. On today's agenda: - project review impressions - deliverables due end of June -- test plan, user & programmer guide, install & admin guide ( https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables ) Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 ----- Forwarded by Alex Glikson/Haifa/IBM on 27/06/2012 08:21 AM ----- From: Alex Glikson/Haifa/IBM at IBMIL To: "fiware-cloud at lists.fi-ware.eu" , Date: 13/06/2012 05:15 PM Subject: [Fiware-cloud] minutes Sent by: fiware-cloud-bounces at lists.fi-ware.eu Summary of today's meeting: Date: 13/6/2012 Attendees: IBM, TID, UPM, Technicolor, INRIA Minutes: The education sessions with the use-cases were very interesting and insightful. Based on the feedback received from the use-cases, it is being considered to precede the delivery of Object Storage GE from August to July. Moreover, following the 'popularity' of the cloud proxy concept, we are considering an Open Call topic that would ease the usage of CP resources by UC applications FI-WARE project review is going to take place in Brussels next week. Only 20 minutes are allocated to present the entire year of work in each chapter, so don't expect to go into much detail. We need to make sure that our tracker properly represents the progress of our work, so that it can be verified if requested. Action Item [All, by Tue next week, 19/6]: review & update tracker, make sure all the features and stories are in place, and are properly assigned to releases and sprints (past and current). We need to finish our work on all the 'month 12' deliverables by the end of June -- including GEs first implementation (naturally), as well as deliverables associated with each GE -- installation & admin guide, user & programmer guide, test plan. Please, notice that in some cases this might require some packaging work if you need to install components on top of baseline assets. Regarding the test-plan -- there are detailed guidelines sent by Juanjo earlier today. We need to add epics and features to the backlog in the wiki that cover the main functionality of the 'baseline' assets -- so that by the end of the month our backlog will cover all the functions that need to be tested once GEs are deployed in the testbed. Then for each feature we need to document the test cases, in the wiki too. Action Item [All, by Tue the following week, 26/6]: add to the wiki the necessary epics and features to cover all the testable functions of each GE, as well as test cases for each feature. We will review the results during our meeting on 27/6. The testbed is supposed to be ready in the beginning of July. We will need to complete the installation and integration of our GEs in the testbed by the end of July, when we will need to have fully-functional cloud environment, with all the GEs (planned for July). We will discuss the details at our meeting on July 4th. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Alex Glikson/Haifa/IBM at IBMIL To: "fiware-cloud at lists.fi-ware.eu" , Date: 13/06/2012 03:53 PM Subject: [Fiware-cloud] agenda Sent by: fiware-cloud-bounces at lists.fi-ware.eu The main topic on the agenda for today's weekly call (in few minutes) is the June deliverables, as well as summary of FI-PPP education sessions. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Tue Jul 17 07:41:59 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 17 Jul 2012 08:41:59 +0300 Subject: [Fiware-cloud] Measures to enforce timely delivery Message-ID: FYI, PCC has approved the following measures to enforce timely delivery of June deliverables. Partners involved in development of a given FI-WARE GE that is not delivered by July 23rd will not be allowed to justify any PM in WP3-WP8 until they deliver. Once they deliver, it will be assumed that the PMs consumed had been those that were reported until month 12, so that no additional PMs will be accepted. Planning of PMs for the remaining of the project will be adjusted accordingly. Delivery of software that doesn?t work or proves to be rather unstable in the FI-WARE Testbed will not be considered as actually delivered. This intends to prevent that some partner delivers software which doesn?t meet enough quality by July 23rd ust to avoid costs rejections. Partners that deliver by July 23rd will be allowed to justify the PMs planned until July 23rd (provided that the software they have delivered is not rejected as stated in the previous point). This means they would not suffer any impact. It seems that all the Cloud deliverables are ready, so we are not affected (per the 3rd bullet). Of course, similar measures might be applied in the future if needed. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Wed Jul 18 14:12:14 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 18 Jul 2012 15:12:14 +0300 Subject: [Fiware-cloud] meeting today Message-ID: Let's cancel today's meeting -- no urgent topics to discuss, and some of the partners are on vacations anyway. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Wed Jul 25 16:32:31 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 25 Jul 2012 17:32:31 +0300 Subject: [Fiware-cloud] weekly Message-ID: Dear all, I apologize for not being able to dial in to the weekly call today -- something popped up unexpectedly, which prevented me from attending or being online. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri Jul 27 09:31:42 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jul 2012 09:31:42 +0200 Subject: [Fiware-cloud] Installation on the Testbed and procedures Message-ID: <501243DE.3010807@tid.es> Dear all, As leader of the task D10.2 "FI-WARE Integration" and also from the coordination I'd like to make some clarifications of general interest. As you know, WP10 (Experimentation Support, Integrated Testing and Validation) has as main task the set-up and running of the FI-WARE Testbed. Given the importance of this goal, WP10 has a representative of each partner. This representative (not the WPL) should make sure that all people within his/her company are well informed of the situation and what we expect from them in the Testbed and the experimentation stage. Several partners are not doing this work (in same cases never attended the WP10 phc) and the project coordination is receiving complaints as many people don't seem to be well informed. We sometimes resort to the WPL to help here, but this is not the "official" channel. I will try to recap to give all the consortium an overview of the situation and what we need from you. GENERAL INFO * The Testbed Team is starting to send the details on how to install the testbed to the GE owners who declared that they are going to install their GE in July * Theoretically you should install your GE yourselves but we can give a hand deploying a KVM image for those who prefer this method (other hypervisors are not supported) * The GE owner is the one who administrates and maintains the GE, not the testbed team. If something goes wrong, he/she has to put it up and running again, the WP10 will only monitor the situation and will prompt about abnormal behaviour of the GE . * We have two tools to follow this up: * Implementation cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit * Integration Tracker : https://forge.fi-ware.eu/tracker/?atid=224&group_id=18&func=browse * Each release of each GE is represented by a ticket * The use of this is explained here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Integration_Plan#Integration_Process * If you do not have access to the testbed project and cannot reach this wiki and the tracker, request access following the standard procedure REQUESTS FOR GE OWNERS * We have an installation calendar. Please fill in the responsible person per GE and state the dates when you could install * http://www.doodle.com/bymgm9h9gnbfms8k * Fill the GE template in the Testbed Cockpit (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit ) declaring if the GE is multi-tenant or not (this deeply affects the GE usage by different Use case projects at the same time) * The access to the Testbed is limited per IP. Make sure that the IPs from which you are going to access the Testbed are listed here (if not, you will not be able to enter the testbed): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit (click on your enabler and see the wiki page with the details per enabler) * Alternatively, there is also a page that has company wide IPs (not particular to an enabler): https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Operations_Cockpit * Make sure that when you install your GE, you update the corresponding ticket on the Integration tracker and also the Implementation cockpit. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 Sun Jul 29 08:55:01 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 29 Jul 2012 09:55:01 +0300 Subject: [Fiware-cloud] Fw: Comments on Features linked to GEs in the Cloud Chapter Message-ID: All, Please, see below comments by Juanjo. I've already applied some of the changes. Few more things which still need to be fixed: Features related to Placement -- IBM [Oshrit] Self-service interfaces -- UPM Other suggested changes -- all Going forward, we may consider reorganizing the backlog a bit (e.g., align the level of granularity of features and stories across GEs, make it more friendly for people outside of the project). But I think we can do this after we are done with the 1st year deliverables. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 ----- Forwarded by Alex Glikson/Haifa/IBM on 29/07/2012 09:47 AM ----- From: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL, Cc: Miguel Carrillo , "jhierro >> \"Juan J. Hierro\"" Date: 24/07/2012 10:34 PM Subject: Comments on Features linked to GEs in the Cloud Chapter Dear Alex, Please find my comments regarding revision/addition of Features linked to GEs in the Cloud Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. 2. Comments on Features linked to the IaaS Data Center Resource Management GE Several Features are not Features but Work Items (therefore shouldn't be part of the backlog that is visible on the Wiki): FIWARE.Feature.Cloud.ResourceManager.Setup.IBM.BasicProvisioning FIWARE.Feature.Cloud.ResourceManager.Setup.Intel.BasicProvisioning Some Features are too vague, while several of the descendant User Stories would be rather helpful to describe what the GE provides. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4): FIWARE.Feature.Cloud.ResourceManager.APIs.EssentialManagement The following Features seems to be linked to development of a prototype application whose deployment using the GE capabilities was tested. This should correspond to a Feature but a Work Item or should lead to definition of a separate backlog dealing with development of the prototype: FIWARE.Feature.Cloud.ResourceManager.Capacity.SimpleDaytraderOvercommitStandalone The following Features are poorly described, or the description is missing: FIWARE.Feature.Cloud.ResourceManager.Capacity.MultiVmWithConstraintsOvercommitStandalone Regarding Feature FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler, it is not clear what it means ... Are you simply declaring that you are using the OpenStack existing service ? Please improve Goal and description making this more clear. The scope and differentiation between FIWARE.Feature.Cloud.ResourceManager.Placement.BasicDeployOptimization and FIWARE.Feature.Cloud.ResourceManager.Placement.PlacementEngine is unclear. Note the similarity of the descriptions: Integrate an advanced placement engine in Openstack based environment to support multi-policy provisioning constrains. The placement component would be integrated in the run_instance path, to indicate the best-fit hosts to place the instances on, without effecting the other running instances Integrate an advanced placement engine in Openstack based environment to support multi-policy provisioning constrains. The placement component would be integrated in several paths, such as evacuation, deployment, etc. to indicate the best-fit hosts for the instances to run on Please enhance descriptions to highlight the differences. Last but not least, we would like to highlight that the Feature FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration is a rather good reference example. 3. IaaS Service Management The list of Features describing the IaaS SM GE could be considered complete and at the right level of granularity. However, all of them suffer of the same issue: the Description is a copy of the goal. It would be relevant to elaborate the Description a bit so that someone gets a better view of what functionality will be supported. Note that this exercise should would only need to be made regarding Features. 4. Object Storage There is a Feature that seems not to be a Feature but a Work Item (therefore shouldn't be part of the backlog that is visible on the Wiki): FIWARE.Feature.Cloud.ObjectStorage.Setup.Intel.BasicObjectStorage The two other remaining Features are too vague, while several of the descendant User Stories would be rather helpful to describe what the GE provides. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4): 5. Self-service interface Some of the Features rely on concepts that may not be well known by a potential reader and belong to the "conceptual model" behind the OpenStack Dashboard product (Instances, Images, Flavors). It would be nice that the Descriptions hold a short description of those concepts and even include a link to some OpenStack Dashboard documentation/web page resource where those concepts are described: FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Instances FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Images FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Flavors It would be nice to enrich a bit the description giving some examples of commands that would be supported by CLIs: FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI FIWARE.Feature.Cloud.SelfServiceInterfaces.AdminInterface.AdminCLI 6. Cloud Proxy I hope that we agree that having just one single Feature sounds like rather uncomplete. But taking a look at the User Stories derived from the single defined Feature, we would get an enough complete overview of the functionality that the GE supports. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. 7. Monitoring Features are overall Ok. It might be nice to provide some examples of metrics. Just consider to do so. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla at tid.es Sun Jul 29 11:39:02 2012 From: fla at tid.es (FERNANDO LOPEZ AGUILAR) Date: Sun, 29 Jul 2012 11:39:02 +0200 Subject: [Fiware-cloud] Fw: Comments on Features linked to GEs in the Cloud Chapter In-Reply-To: References: Message-ID: <8EE61BA0CAEDBD4E9DA928D1206463D2F87204E091@EXCLU2K7.hi.inet> I have changed the topics related to Service Manager. Regards, Fernando ________________________________________ De: fiware-cloud-bounces at lists.fi-ware.eu [fiware-cloud-bounces at lists.fi-ware.eu] En nombre de Alex Glikson [GLIKSON at il.ibm.com] Enviado el: domingo, 29 de julio de 2012 8:55 Para: fiware-cloud at lists.fi-ware.eu Asunto: [Fiware-cloud] Fw: Comments on Features linked to GEs in the Cloud Chapter All, Please, see below comments by Juanjo. I've already applied some of the changes. Few more things which still need to be fixed: 1. Features related to Placement -- IBM [Oshrit] 2. Self-service interfaces -- UPM 3. Other suggested changes -- all Going forward, we may consider reorganizing the backlog a bit (e.g., align the level of granularity of features and stories across GEs, make it more friendly for people outside of the project). But I think we can do this after we are done with the 1st year deliverables. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 ----- Forwarded by Alex Glikson/Haifa/IBM on 29/07/2012 09:47 AM ----- From: Juanjo Hierro To: Alex Glikson/Haifa/IBM at IBMIL, Cc: Miguel Carrillo , "jhierro >> \"Juan J. Hierro\"" Date: 24/07/2012 10:34 PM Subject: Comments on Features linked to GEs in the Cloud Chapter ________________________________ Dear Alex, Please find my comments regarding revision/addition of Features linked to GEs in the Cloud Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. 2. Comments on Features linked to the IaaS Data Center Resource Management GE Several Features are not Features but Work Items (therefore shouldn't be part of the backlog that is visible on the Wiki): * FIWARE.Feature.Cloud.ResourceManager.Setup.IBM.BasicProvisioning * FIWARE.Feature.Cloud.ResourceManager.Setup.Intel.BasicProvisioning Some Features are too vague, while several of the descendant User Stories would be rather helpful to describe what the GE provides. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4): * FIWARE.Feature.Cloud.ResourceManager.APIs.EssentialManagement The following Features seems to be linked to development of a prototype application whose deployment using the GE capabilities was tested. This should correspond to a Feature but a Work Item or should lead to definition of a separate backlog dealing with development of the prototype: * FIWARE.Feature.Cloud.ResourceManager.Capacity.SimpleDaytraderOvercommitStandalone The following Features are poorly described, or the description is missing: * FIWARE.Feature.Cloud.ResourceManager.Capacity.MultiVmWithConstraintsOvercommitStandalone Regarding Feature FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler, it is not clear what it means ... Are you simply declaring that you are using the OpenStack existing service ? Please improve Goal and description making this more clear. The scope and differentiation between FIWARE.Feature.Cloud.ResourceManager.Placement.BasicDeployOptimization and FIWARE.Feature.Cloud.ResourceManager.Placement.PlacementEngine is unclear. Note the similarity of the descriptions: * Integrate an advanced placement engine in Openstack based environment to support multi-policy provisioning constrains. The placement component would be integrated in the run_instance path, to indicate the best-fit hosts to place the instances on, without effecting the other running instances * Integrate an advanced placement engine in Openstack based environment to support multi-policy provisioning constrains. The placement component would be integrated in several paths, such as evacuation, deployment, etc. to indicate the best-fit hosts for the instances to run on Please enhance descriptions to highlight the differences. Last but not least, we would like to highlight that the Feature FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration is a rather good reference example. 3. IaaS Service Management The list of Features describing the IaaS SM GE could be considered complete and at the right level of granularity. However, all of them suffer of the same issue: the Description is a copy of the goal. It would be relevant to elaborate the Description a bit so that someone gets a better view of what functionality will be supported. Note that this exercise should would only need to be made regarding Features. 4. Object Storage There is a Feature that seems not to be a Feature but a Work Item (therefore shouldn't be part of the backlog that is visible on the Wiki): * FIWARE.Feature.Cloud.ObjectStorage.Setup.Intel.BasicObjectStorage The two other remaining Features are too vague, while several of the descendant User Stories would be rather helpful to describe what the GE provides. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4): 5. Self-service interface Some of the Features rely on concepts that may not be well known by a potential reader and belong to the "conceptual model" behind the OpenStack Dashboard product (Instances, Images, Flavors). It would be nice that the Descriptions hold a short description of those concepts and even include a link to some OpenStack Dashboard documentation/web page resource where those concepts are described: * FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Instances * FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Images * FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Flavors It would be nice to enrich a bit the description giving some examples of commands that would be supported by CLIs: * FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI * FIWARE.Feature.Cloud.SelfServiceInterfaces.AdminInterface.AdminCLI 6. Cloud Proxy I hope that we agree that having just one single Feature sounds like rather uncomplete. But taking a look at the User Stories derived from the single defined Feature, we would get an enough complete overview of the functionality that the GE supports. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. 7. Monitoring Features are overall Ok. It might be nice to provide some examples of metrics. Just consider to do so. ________________________________ 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