Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 5 Current »

Date

 

Attendees

  • Greg Hill
  • Silas Davis
  • Richard Berg
  • Ryan Beck-Buysse
  • Shawn Amundson
  • Srinivasan K
  • Mike Lodder
  • Morgan Bauer
  • Pankaj Goyal
  • Qinghui Hou
  • Artyom Bakhtin
  • Matt Sykes
  • Brett Logan
  • Dipti
  • Mark Wagner
  • Ry Jones
  • Dave Huseby

Agenda

  • Do we want to pursue moving Fabric minions to external hosting in the short term?
  • Building raw resources on AWS or IBM cloud.
    • What does this look like?

Minutes

  • Recap of the conversation so far up to last week.
  • Looking at Cloudbees
    • They don't offer a managed solutions, they only have a support contract available.
    • They have third parties they work with that can do managed services and pricing is on a per-user model.
      • A user is every committer.
      • Any special pricing for open source projects? We would have to get a quote and then negotiate with them.
      • Tested Cloudbees with Fabric and it doesn't really give us any advantage.
        • It's very similar to Jenkins and at the end of the day, it's not really something we want to pay for.
  • Looked at CircleCI
    • It does what Fabric wants to do but it doesn't integrate with Gerrit.
  • The two problems:
    • CI is one problem and is more concerned 
  • Moving forward ideas
    • CircleCI
      • Supports running both on VM's and container hosts.
      • Supports AWS and other cloud platforms so it would support Sawtooth long-running tests.
      • Does declarative pipelines that Fabric team wants.
      • We already have a CircleCI account and we can run some tests on there.
    • Bare AWS with teams doing what they want
    • Kubernetes
      • Tekton UI was unable to get it running.
        • Couldn't find support for VM nodes.
      • Kubevert can support VMs but we'd have to use rsync to get files onto the machine for testing. 
  • Producing the GB report
    • Three sections
      • Introduction that describes the current state and the set of problems.
      • Describe the potential solutions for solving the CI problem and also for solving the soak/test net problem.
      • Itemize the most likely solution to solve the most problems for the most teams.

Action items

  • David Huseby investigating Prow and Kubernetes 
  • Fabric team to narrow solutions for the report.
  • Mark Wagner (Deactivated)  to look into Kubernetes with VM (kubevert)
  • No labels