DebConf20 Cloud Images BoF (Thu 2020-08-27 20:00 UTC)

Items on the agenda for the BoF:

1/ Quick retrospective on last year
- Accounts moved under the Debian org?!?

    - working on new accounts being associated w/SPI

    - cloud team doesn't have anything setup w/SPI owned account

    - azure has been fixed since before buster release

    - no funding for cloud-team stuff though

- First large cloud-init update in Buster and post-mortem about the failures

Q: Define/Formalize the tests needed to get cloud-init (also other packages) ready for a stable release would not make stable release managers accept it more easily?

2/ Our TODO for Bullseye
- writting an equivalent of https://salsa.debiages-team/live-setup/blob/master/bin/check-openstack-updates

    - This should read the .json manifest containing all package version numbers

- Use systemd-networkd? cloud-init does not support it directly

    - can we replicate all of the existing use-cases?

    - ipv4 always, ipv6 optional - with no way to know ahead of time

    - cloud-init expects ifupdown

    - WNPP says ifupdown is O since 2020-06-28: https://bugs.debian.org/963891

    - what happens to things that use the dhclient hooks?  would we be forced to adopt e.g. timesyncd?


3/ Cloud team inside Debian
- Exclusive (just strict cloud, aka VM) or inclusive (everything from hardware to container)?
- How to handle offers for access to clouds
   -- We have some teams within Debian using public cloud resources today. How can we make it easy for others to access similar resources, and when is it appropriate to do so?

4/ Questions and feedback from users

 - Is there scope for talking to other distros eg Ubuntu to get common viewpoints on systemd-networkd and so on?