[Fiware-cloud] Fw: Comments on Features linked to GEs in the Cloud Chapter

[Alex Glikson]

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 <jhierro at tid.es>
To:     Alex Glikson/Haifa/IBM at IBMIL, 
Cc:     Miguel Carrillo <mcp at tid.es>, "jhierro >> \"Juan J. Hierro\"" 
<jhierro at tid.es>
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: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20120729/b248c056/attachment.html>