COSI Calls

Wednesday open source calls

To Edit/Contribute

  1. Go to https://hackmd.io/IXcDy0prSgia4lOH_e1xSA
  2. Log in (github, etc)
  3. Click either the pencil or split screen icon at the top

02 June 2021 (06/02/2021)

Attending

Agenda

  • [andrewrynhard] move schedule to bi-weekly
  • [andrewrynhard] COSI rename due to conflict
  • [smira] Demo

26 May 2021 (05/19/2021)

Attending

Agenda

  • [andrewrynhard] Creating our first official plugins
  • [nova] cosi.dev repo permissions
  • [nova] demo demo demo

19 May 2021 (05/19/2021)

Attending

Agenda

  • [smira] Engineering deep-dive into COSI runtime
  • [invidian] KOSS - Kubernetes OS Server - PoC for using Kubernetes API server for managing host resources == managing sysctl using kubectl

12 May 2021 (05/12/2021)

Attending

Agenda

  • [andrewrynhard] Networking with other projects
  • [andrewrynhard] cosi.dev
  • Kubecon recap:
    • Other OS vendors looking at COSI
    • Flatcar Linux Monthly Meetings
  • [rsmitty] Kubecon US!
    • CFP closing May 23 2021
      • Deep Dive session
  • [saiyam] thought on this? -> https://devopsish.com/217/
    • We need new names:
      • ADIOS: API-driven Interface for Operating Systems
  • [andrewrynhard] KCP

5 May 2021 (05/05/2021)

CANCELED

28 April 2021 (04/28/2021)

Attending

Agenda

21 April 2021 (04/21/2021)

Attending

Agenda

  • [andrewrynhard] Should an implementation live in the COSI org?
    • We feel that having a reference implementation is good.
    • We should design such that multiple implementations is easy.
    • We should get clear about the name of the spaces (e.g. engine).
    • names should be inclusive of new tools and old tools
      • EG: the launcher/bootstrap component should include:
        • systemd
        • init
        • engine
        • windows init
        • osx launcher
        • freebsd init
  • [andrewrynhard] Branding.
    • Create cosi.dev repo.
    • andrew give nóva access to repo
    • we need a youtube channel?
    • nóva to set up hello world
  • [andrewrynhard] Git LFS?
    • yes
  • [andrewrynhard] Equinix Metal stream.
    • We need to get onto meetups, steams, etc. to start evangelizing COSI.
  • [nóva] First draft at charter
  • [invidian] Initial spec compatibility between different OSes

14 April 2021 (04/14/2021)

Attending

Agenda

–

07 April 2021 (04/04/2021)

Attending

Agenda

  • Questions/Answers

  • [nóva] Intros

  • [nóva] can we collect problem statements?
    • distributed operating system void
    • [andrew] is anyone willing to share today?
      • [stefan] everyone is solving the underlying OS problem in different ways
        • drivers, specs, storage
        • if we are able to achieve a spec, that would be a good thing
        • this is very ambitious, but we should start
      • [mateusz] kubelet
        • having a clearly defined way of kubernetes interfacing with the operating systems
        • having a clear API should make everyones lives easier
      • [christian]
        • we are running rook/ceph ("bad things")
        • running flatcar
        • we do an update here -> trouble over there
        • hopefully COSI will help with standardizing this
        • CNI seems like an anti pattern (installing after)
      • [stefan] standard CNI
        • See cilium, BGP networking
        • Why is there so many choices to achieve the same goal
        • There might be some work around the kubelet
      • [nóva] kubelet
        • drop in, replace, alternative to kubelet
        • maybe something there
        • kubelet seems like "main interface"
        • maybe we just have kubelet features?
        • [stefan] where does kubernetes end?
          • where does kubelet start?
          • where does cluster API end
        • [andrew] there seems to be overlap between kubelet/cosi - we need to define these things
          • kubelet is critical part of cosi
        • [nóva] cni, cri, csi
          • all took a top down approach to solving compute, storage, networking
        • [seán] API
          • really the API is the value here
          • having a standardized interface
          • the exercise is abstracting or "presenting" the operating system (kernel) to the commonly used configuration
        • [stefan] dat systemd tho
          • [seán] systemd and kubernetes dont really conflict
            • systemd and kubernetes are the same thing but at different layers
          • [nóva] systemd and kubernetes might be the same thing just with a different scope
          • [andrew] does systemd share the goal of kubernetes
          • talos is a reimaginement of distributed OS
        • [andrew] there is a COSI spec
          • systemd can have a shim
          • system can implement COSI spec
          • talos also has it
          • assumption that you can SSH into box and mutate system via systemd and package managers
            • ain't nobody got time for that
      • [christian]
        • Q: is cosi k8s centric?
        • A: the interface is for all distributed systems
      • [steven]
        • post kubernetes world where "nodes" can communicate with each other
        • see below "history of COSI"
      • [nóva] should we agree on "the interface"?
        • distributed vs non-distributed
        • a "set" can go 0:1:N
      • [seán] this is an interface to a kernel?
        • [nóva] we could just add a new syscall as a thought experiment
        • sounds like we agree on the implementation
        • distributed interface from 0:N
    • History of COSI:
  • [@andrewrynhard] Project home
  • [@andrewrynhard] White paper

Action Items

  • andrew:
    • set up cosi-spec org
    • invite invitees of above
    • nova add issues
      • communications
      • github issues
    • andrew to give us a place to start on white paper
    • people to suggest what COSI is solving
Select a repo