User Tools

Site Tools


project_proposals:domino

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
project_proposals:domino [2016/03/09 09:43]
Ulas Kozat [Project description:]
project_proposals:domino [2016/03/22 14:26] (current)
Prakash Ramchandran [Committers :]
Line 1: Line 1:
 ==== Project Name: ==== ==== Project Name: ====
  
-  * Proposed name for the project: ​Domino ​Template Distribution Service+  * Proposed name for the project: Template Distribution Service ​(Domino)
   * Proposed name for the repository: Domino   * Proposed name for the repository: Domino
 ==== Project description:​ ==== ==== Project description:​ ====
Line 75: Line 75:
 ==== Documentation:​ ==== ==== Documentation:​ ====
  
 +  * Presentations:​
 +    * {{:​project_proposals:​opnfv_technical_discussion_-_domino_proposal.pptx|}}
   * API Docs (TBD)   * API Docs (TBD)
   * Functional block description (TBD)   * Functional block description (TBD)
Line 82: Line 84:
   * Project has dependencies on Parser, OpenStack Heat, ONOSFW. Project has also dependency on SFC solutions (e.g., OpenStack neutron extensions, ODL SFC, ONOS SFC, etc.) at the API level.   * Project has dependencies on Parser, OpenStack Heat, ONOSFW. Project has also dependency on SFC solutions (e.g., OpenStack neutron extensions, ODL SFC, ONOS SFC, etc.) at the API level.
   * Although it does not have any particular dependency on OpenStack Tacker, the project has overlaps in the context of multi-site resource orchestration and parsing/​translating/​mapping TOSCA templates. Project has also potential overlaps with multi-site project.   * Although it does not have any particular dependency on OpenStack Tacker, the project has overlaps in the context of multi-site resource orchestration and parsing/​translating/​mapping TOSCA templates. Project has also potential overlaps with multi-site project.
-  * Open-O and Tacker are the main upstreams ​+  * Open-O and Tacker are the main upstreams
  
-==== Committers ​and Contributors: ====+(See [[:​project_proposals/​domino/​dependencies|Dependency Analysis]] for more detailed analysis) 
 + 
 + 
 +==== Committers : ====
  
   * Ulas Kozat (ulas.kozat@huawei.com)   * Ulas Kozat (ulas.kozat@huawei.com)
   * Prakash Ramchandran (prakash.ramchandran@huawei.com)   * Prakash Ramchandran (prakash.ramchandran@huawei.com)
 +  * someone@hp.com (Vinayak Ram of Parser project to assign HP committer)
  
 +==== Contributors : ====
  
 +  * Artur Tyloch (artur.tyloc@canonical.com)
 ==== Planned deliverables:​ ==== ==== Planned deliverables:​ ====
  
Line 99: Line 107:
     * OPNFV requirements:​ lifecycle management artifacts for VNF and service scaling     * OPNFV requirements:​ lifecycle management artifacts for VNF and service scaling
   * Dependencies   * Dependencies
-    * Parser project: policy2tosca module ​and template distributor modules are to be implemented in Parser. Also tosca2heat and yang2tosca modules implemented in Parser projects will be utilized. ​+    * Parser project: policy2tosca module ​is to be implemented in Parser. Also tosca2heat and yang2tosca modules implemented in Parser projects will be utilized. ​
     * OpenStack Heat: project will use Heat as one of the template consumers     * OpenStack Heat: project will use Heat as one of the template consumers
     * SDN Controllers:​ project will add SDN (e.g., ONOS and ODL) applications to act as template consumers     * SDN Controllers:​ project will add SDN (e.g., ONOS and ODL) applications to act as template consumers
Line 107: Line 115:
  
 Release C plans: Release C plans:
-  * Implement policy2tosca module 
   * Specification for example service policy for VNF auto-scaling and service model    * Specification for example service policy for VNF auto-scaling and service model 
   * Specification for example service policy for VNFFG auto-scaling and service model   * Specification for example service policy for VNFFG auto-scaling and service model
   * Implement template distribution to a single OpenStack Heat instance   * Implement template distribution to a single OpenStack Heat instance
 +  * Implement template distribution to two OpenStack Heat instances
   * Implement template distribution to a Heat instance and an ONOS instance   * Implement template distribution to a Heat instance and an ONOS instance
   * Implement use case 1 (orchestration templating) and use case 2 (API templating)   * Implement use case 1 (orchestration templating) and use case 2 (API templating)
project_proposals/domino.1457516591.txt.gz · Last modified: 2016/03/09 09:43 by Ulas Kozat