We would add Identifications/References Monitoring The first would deal with the requirements regarding how elements are to be identified/referenced (which elements have an id? nets, images and VMs only? or also mems, disks...). Regarding 'Monitoring', we think that's an important aspect that also should be included in this specification. Regards, Luis On Wed, Apr 29, 2009 at 6:33 PM, Ignacio Martin Llorente <llorente@dacya.ucm.es> wrote:
Hi,
We are going to start with the evaluation of the submitted use cases. I am planing to create a table summarizing requirements for the different use cases with the following entries:
A. Functional Requirements VM Description VM Management Network Management Image Management
B. Non-functional Requirements Security Quality of Service Others
Any suggestion?
Ignacio -- Ignacio M. Llorente, Full Professor (Catedratico): http://dsa-research.org/doku.php?id=people:llorente DSA Research Group: web http://dsa-research.org and blog http://blog.dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- ----------------- Luis Rodero, PhD. Junior Researcher @ Telefónica I+D