diff options
author | 2015-03-13 15:56:21 +0000 | |
---|---|---|
committer | 2015-03-13 15:56:21 +0000 | |
commit | 85f3132c7fd8f8f7aaf2c54237ac24f41b8d6456 (patch) | |
tree | d138460068fefd558a96a41ead4ce973b0d44293 /src/README | |
parent | b893be5cbd9447b38691ade709f75f0e28c7443d (diff) | |
parent | b4b06d27b062a65ef98753d7f1d9d340fa773329 (diff) |
Merge "added mechanism to pull upstream packages and provided single top-level make"
Diffstat (limited to 'src/README')
-rw-r--r-- | src/README | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/src/README b/src/README new file mode 100644 index 00000000..ff1a1b8e --- /dev/null +++ b/src/README @@ -0,0 +1,28 @@ +### Purpose of this folder - Quickview + +1. contains place holders for upstream source code package. +2. manages the package dependency +3. provides simple one-button build for test developers + +### Motivation Explained + +There are multiple goals for the project vswitch performance characterization. +First, it is a generic test framework that can be used to characterize any vswitch solution. +Second, it is to be as CI tool to validate any change during development. + +For the first goal, it would be nice to get all the relevant upstream source package and +to provide a easy build environment for a given test developer. Obviously we don't want to +rewrite the makefile system from upstream project. However we need to add a wrapper to the +individual packages to manage package dependecy. For example, to test ovs-dpdk vswitch solution, +the build of ovs would depend on the build result of dpdk. +This dependency is never explicitly specified in the individual package. + +For the second goal as a CI tool, it may not be needed to pull the upstream package. +So this whole folder can be ignored. + +### Files and subfolders + +* package-list: contains list of packages and their associated tags +* mk: contains top level makefiles +* dpdk: place holder for dpdk package +* ovs: place holder for ovs package. |