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

Compare with Current View Page History

« Previous Version 11 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

Completed Work

  • David Huseby  move the initial CI/CD document from the TSC space to CI/CD space.
  • Gregory Hill  add details, including costs, of the Burrow CI/CD pipeline in the existing setups page.
  • user-b2fb8  get the actual cost of the current Jenkins and Gerrit CI/CD setup used by Fabric.
  • David Huseby  initial requirements gathering document set up.

Discussion

  • Talk about how we want to do requirements gathering.
    • Should we break up along teams and report back?
    • Should we assign one or two people to study each team's solution and report back?

Minutes

  • Dave space set up and requirements docs are up.
  • Ry: we're budgeted to spend about ~$120k/year and we're currently spending about $60k this year so we do have some money to spend for some exploration with a parallel system.
  • Dave: talking about requirements.
    • Kubernetes concerns:
      • Sawtooth
        • assumes a docker runtime under the docker building process.
        • also docker compose.
      • are any projects using Docker swarm or any other competing technologies that they would have to move away from?
    • Other platforms to look at.
      • CNCF is using Prow. What is Prow?

Action items

  • Ryan Beck-Buysse look into Sawtooth's existing pipeline and identify any pain points for moving existing infra to a kube cluster.
  • Srinivasan K  figure out if any of our teams are using Docker swarm or any competing products.
  • David Huseby  investigate kube cpu credits, memory limits, cpu limits, and load balancing across namespaces.
  • No labels