Page Comparison

...

1. Best-Practice: Have a separate docker folder in a suitable location within the project's directory structure.

   1. For VinePerf it is: tools/docker

2. Best-Practice: Within this docker folder, have a dedicate folder for each and every container that you plan to publish. 
   1. In VinePerf for Prox container, the path is: tools/docker/test-containers/trafficgen-pods/proxprox
3. In each container folder, ensure you have:
   1. Dockerfile, that is well tested.
   2. Source files that are referred in the Dockerfile, which is present in this folder' with ADD/COPY commands

...

1. Download releng repo in order to submit a patch. git clone https://gerrit.opnfv.org/gerrit/releng
2. Best Practice: Create a separate branch: cd releng; git checkout -b vineperfcontainers
3. Open and Edit this file: https://github.com/opnfv/releng/blob/master/jjb/releng/opnfv-docker.yaml
   1. Setup receiver under existing receivers. See Change-1 below.
   2. Add  your container description under dockerrepo. Please prefix the name of the container with the project name. Seel See Change-2 below for example
4. git add; git commit (Add description); git review.
5. Add reviewers - Trevor Bramwell, ....

Change-1:

vineperf-receivers: &vineperf-receivers
     receivers: >
         sridhar.rao@spirent.com

Change-2:

- 'vineperf-prox':
    project: 'vineperf'
    dockerdir: 'tools/docker/test-containers/trafficgen-pods/prox'
    <<: *master
    <<: *vineperf-receivers