You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date


Attendees


NameProjectEmail
Greg HillBurrow

greg.hill@monax.io

Silas DavisBurrowsilas@monax.io
Richard BergSawtoothrberg@bitwise.io
Ryan Beck-BuysseSawtoothrbuysse@bitwise.io
Shawn AmundsonSawtoothamundson@bitwise.io
Srinivasan K

mail@srinivasank.net

Mike LodderIndy, Ursamike@sovrin.org
Morgan BauerFabricmbauer@us.ibm.com
Pankaj GoyalSawtoothpankaj.goyal@intel.com
Qinghui HouFabrichouqinghui2@huawei.com
Artyom BakhtinIrohabakhtin@soramitsu.co.jp
Matt SykesFabricsykesmat@us.ibm.com
Brett LoganFabricbrett.t.logan@ibm.com
Dipti
diptivs@gmail.com
Ry JonesHLrjones@linuxfoundation.org
Dave HusebyHL, Ursadhuseby@linuxfoundation.org

Agenda

Minutes

  • Mark: Tekton
    • Kubernetes native CI/CD pipeline tool.
    • Red Hat tests container stuff using VMs using Minikube.
  • Matt
    • Fabric requirements
      • need to bring up containers under Docker compose to run through example tests.
      • moving to kubernetes is possible however Fabric node requires access to the docker daemon to run chain code.
        • new solution is to build chain code as an executable that runs in a process rather than docker image.
      • testing environment has peers and orderers running in VMs and they require bringing up docker containers for running chain code.
      • there are places in fabric test that are relying on compose to run everything. so running those in a kube pod there are issues but on a vm they don't.
      • if LF went to kubernetes without a VM option, it will be a non-started for the Fabric team because they don't have the bandwidth to make the necessary changes to bring their pipeline over. 
      • Make vm-based node pool in kubernetes as part of the solution.
      • How do we want to handle packer images?
        • Is there anything that can be done to get help with problems with the packer images in the ci-management repo?
        • We have a huge issue with an packer image related to maven that has been hard to diagnose and LFIT has refused to help investigate since it isn't using an ansible-based packer system.

Action items

  • Matthew Sykes  modify maintainers file to remove Ramesh and add yourselves and add user-b2fb8 as a reviewer.
  • No labels