User Tools

Site Tools


continuous_integration_ci

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
Last revision Both sides next revision
continuous_integration_ci [2014/10/29 14:41]
Ulrich Kleber [Documentation:]
continuous_integration_ci [2014/11/13 13:56]
Ulrich Kleber [Dependencies:]
Line 24: Line 24:
  
   * **Select a basic set of upstream projects to be integrated in the first step** \\ //we will start with the list from the F2F (see below) and adjust if necessary//   * **Select a basic set of upstream projects to be integrated in the first step** \\ //we will start with the list from the F2F (see below) and adjust if necessary//
-  * **Select a basic hardware definition for the build servers and for the basic verification** \\ //Linux Foundation provides the starting point// +  * **Select a basic hardware definition for the build servers and for the basic verification** \\ //Linux Foundation provides the initial environment// 
-  * **Select the tools for code repository, build processes and automation** \\ //Linux Foundation provides the starting point//+  * **Select the tools for code repository, build processes and automation** \\ //Linux Foundation provides the initial tool environment//
   * **Define the image formats for code deployment in the test environment** \\ //Start with a quick solution and later decide for a format allowing easy deployment for developers and automated verification//​   * **Define the image formats for code deployment in the test environment** \\ //Start with a quick solution and later decide for a format allowing easy deployment for developers and automated verification//​
   * **Define the branching rules for the code repositories** \\ //this will be defined by TSC in the development process and used here//   * **Define the branching rules for the code repositories** \\ //this will be defined by TSC in the development process and used here//
Line 49: Line 49:
   * Open Daylight (Support along with Neutron)   * Open Daylight (Support along with Neutron)
   * Linux Kernel ( Supported Compute nodes)   * Linux Kernel ( Supported Compute nodes)
-  * OVS (DPDK/ODP\\ //​note: ​ OVS is known to be too slow, so need to enhance and  provide alternate to  meet the SDN/DP latency & scale requirements//​ +  * OVS (accelerated version using DPDK user space patches
-  * CEPH - block, data, image… \\ //can start with Cinder and progress to Ceph as it evolves; some concerns, but use as start point and add alternate solutions later//+  * CEPH - block, data, image… \\ //can start with Cinder and progress to Ceph as it evolves//
  
 The initial set is meant to be as small as possible, so the initial environment can be provided early. The initial set is meant to be as small as possible, so the initial environment can be provided early.
Line 73: Line 73:
 ==== Dependencies:​ ==== ==== Dependencies:​ ====
  
-None, except ​on upstream ​projects. ​+The first step of integration has no dependency ​on other OPNFV projects. However it depends on decisions that will be made outside the project, like for example the selection of Linux distributions,​ which may need TSC approval.
  
-Octopus ​is the initial ​project ​others will depend ​on.+Test and verification in later project stages ​is dependent on the test objects provided by VNF deployment test cases project
 + 
 +Continuous integration in later project stages is dependent ​on the Simultaneous Release project.
  
 ==== Committers and Contributors:​ ==== ==== Committers and Contributors:​ ====
Line 81: Line 83:
 == Companies/​affiliations committed to the project and willing to provide substantial resources: == == Companies/​affiliations committed to the project and willing to provide substantial resources: ==
  
-  * Huawei ​(10), contacts: Uli Kleber (ulrich.kleber ad huawei.com),​ Prakash Ramchandran (p.ramchandran ad huawei.com)+  * Huawei, contacts: Uli Kleber (ulrich.kleber ad huawei.com),​ Prakash Ramchandran (prakash.ramchandran ad huawei.com)
   * Cisco, contact: Ian Wells (iawells ad cisco.com)   * Cisco, contact: Ian Wells (iawells ad cisco.com)
-  * RedHat+  * RedHat, contact: Dave Neary (dneary ad redhat.com 
 +  * HP, contact: Dave Lenrow (david.lenrow ad hp.com)
   * ..   * ..
  
Line 92: Line 95:
 ==== Planned deliverables:​ ==== ==== Planned deliverables:​ ====
  
-See project description +The first step will be to generate a build of all the upstream components. ​
 ==== Proposed Release Schedule: ==== ==== Proposed Release Schedule: ====
  
Line 104: Line 106:
 ==== Appendix: ==== ==== Appendix: ====
  
-The following information is preliminary and may be used during ​the project lifetime.+This project will be executed using Agile Development methodology. This Appendix provides exemplary tasks and some other details at project execution for informational purpose. Those exemplary tasks and details are living content, and subject to further evolution ​during project lifetime. Jira tool will be used to further develop the details.
  
 === Basic set of upstream projects === === Basic set of upstream projects ===
continuous_integration_ci.txt · Last modified: 2014/11/13 13:57 by Ulrich Kleber