User Tools

Site Tools


requirements_projects:resource_management

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
requirements_projects:resource_management [2014/12/04 14:31]
Gerald Kunzmann [Committers and Contributors:]
requirements_projects:resource_management [2014/12/17 06:22] (current)
Murali Birru [Committers and Contributors:]
Line 50: Line 50:
  
   * Describe how the project is extensible in future   * Describe how the project is extensible in future
-    * Resource Management ​can be extended to +    * It can be extended to resource management ​based on policy 
-      * Node mapping ​based on requested criteria ​ +        * e.g. VNF mapping based on DPDK support, affinity rules etc. 
-        * DPDK support, affinity rules etc.+          * this project focuses on realizing the reservation/​capacity management feature, not on determining policy for such features ​
  
  
Line 64: Line 64:
  
   * Identify similar projects is underway or being proposed in OPNFV or upstream project   * Identify similar projects is underway or being proposed in OPNFV or upstream project
-    * N/A+    * Copper ([[requirements_projects:​Virtual Infrastructure Deployment Policies]])
   * Identify any open source upstream projects and release timeline.  ​   * Identify any open source upstream projects and release timeline.  ​
     * StormForge - https://​github.com/​stormstack/​stormforge ​     * StormForge - https://​github.com/​stormstack/​stormforge ​
Line 83: Line 83:
   * Names and affiliations of the committers:   * Names and affiliations of the committers:
     * Ashiq Khan (DOCOMO: khan@nttdocomo.com)  ​     * Ashiq Khan (DOCOMO: khan@nttdocomo.com)  ​
-    * Peter Lee (ClearPath: plee@clearpath.com)+    * Peter Lee (ClearPath: plee@clearpathnet.com)
     * Ryota Mibu (NEC: r-mibu@cq.jp.nec.com)     * Ryota Mibu (NEC: r-mibu@cq.jp.nec.com)
     * Ravi Chunduru (ClearPath: rchunduru@clearpathnet.com)     * Ravi Chunduru (ClearPath: rchunduru@clearpathnet.com)
     * Carlos Goncalves (NEC: Carlos.Goncalves@neclab.eu)     * Carlos Goncalves (NEC: Carlos.Goncalves@neclab.eu)
-    * Serge Manning (Sprint)+    * Serge Manning (Sprint: Serge.Manning@sprint.com)
     * Dirk Kutscher (NEC: dirk.kutscher@neclab.eu)     * Dirk Kutscher (NEC: dirk.kutscher@neclab.eu)
-    * Siva Busa (ClearPath) +    * Siva Busa (ClearPath: SBusa@clearpathnet.com
-    * Hironobu Maeda (ClearPath)+    * Hironobu Maeda (ClearPath: HMaeda@clearpathnet.com)
     * Arturo Martin De Nicolas (Ericsson: arturo.martin-de-nicolas@ericsson.com)     * Arturo Martin De Nicolas (Ericsson: arturo.martin-de-nicolas@ericsson.com)
 +    * Murali Birru (murali.yadav@calsoftlabs.com)
 +
   * Any other contributors:​ TBD   * Any other contributors:​ TBD
  
Line 104: Line 106:
       * ''​pkgcloud''​ open source software will be integrated to provide library abstraction to OpenStack APIs       * ''​pkgcloud''​ open source software will be integrated to provide library abstraction to OpenStack APIs
       * The reference implementation will be designed to operate as a //plug-in// to OpenStack that can run independently from the underlying OpenStack deployment. ​ Current primary target OpenStack compatibility is Juno but may also be compatible to older OpenStack releases (compatibility report will be provided along with the code contribution).       * The reference implementation will be designed to operate as a //plug-in// to OpenStack that can run independently from the underlying OpenStack deployment. ​ Current primary target OpenStack compatibility is Juno but may also be compatible to older OpenStack releases (compatibility report will be provided along with the code contribution).
-    * Description of potential use cases+    * Description of potential use cases (i.e. different ways of realizing resource reservation/​capacity management)
   * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.   * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.
     * N/A     * N/A
requirements_projects/resource_management.1417703470.txt.gz · Last modified: 2014/12/04 14:31 by Gerald Kunzmann