Hello,

I am glad that things about opencontrail community are moving forward..

I am mostly interested in packaging (as a Debian Maintainer) so I guess
I can help here a little.
Some thoughts about what should such document describe (according to
some "missing pieces" that people are asking about):

- components and their individual testing (eg. unit tests of vrouter,
  controller, python tests, etc.)

- infrastructural, cross-component testing (using Fabric tooling)

- build process and cross-component dependencies (as it's kind-of
  spaghetti, scons, generation of python code, etc.)
  - it also includes way how to get all the source code, eg.
    contrail-vnc or maybe better tooling that we are using [1]

- packages build (Debian + RHEL), contrail-packages vs.
  contrail-packaging
  - build and maintanence of 3rd party dependencies (we know this is and
    always was a mess) - eg. kafka, some python- modules, etc.
    - this is something that needs to get better, resp. we already did it
      at tcpcloud/Mirantis so we can help here [2] by providing
      pipelines and flow to build and maintain these packages

  - bundled 3rd party dependencies (bind, etc.) with extra patches which
    is very dirty and should not exist at all - these extra dependencies
    should be also maintained as separate distribution packages

- branching and releasing - this was always a mess, not communicated at
  all, almost no one knows what branch is stable, development, which one
  to use for production and how they are maintained

That are my initial inputs, I think we can gather more.

Filip

---
[1] https://github.com/Mirantis/contrail-pipeline
[2] https://github.com/tcpcloud?utf8=%E2%9C%93&q=debian-&type=&language=

On 2017/07/06 01:30, Gregory Elkinbard wrote:
> Hi folks,
> Looking to put together a requirements doc for the community CI.
> Volunteers to own the doc?
> 
> Please provide requirements inputs to the list, while the docs repo is being 
> created.
> 
> Thanks
> Greg
> 

> _______________________________________________
> Dev mailing list
> Dev@lists.opencontrail.org
> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Reply via email to