This comment probably deserves its own thead, but let's start talking about it here.
I think that there should be a debian-virtual team as well as debian-cloud. This would separate and clearly define software in each realm.
An example is the debian images. The virtual team would create virtual machine images that may be specific to hypervisors but not contain any cloud or specific cloud elements. The cloud team can take that image and add on or modify it for specific clouds.
At the moment it seems like virtual and cloud is melded together.On Oct 22, 2013 7:26 AM, "Jimmy Kaplowitz" <email@example.com> wrote:Hi,At DebConf13, we had a great rollicking discussion about public clouds and official Debian image status, prompted by a few slides by me but the discussion was the best part. Here are some notes from the discussion.- Zack: might need a cloud release team to decide what goes into cloudimages and bridge release cycle differences- folks linked to Amazon/OpenStack/Google:- Cloud is just a new “architecture” for Debian to support- Maybe put tools for all clouds in a unified cloud image- Security lockdowns are important for cloud, or possibly everyone- Some people like “Official Debian” trust- Lucas: official images should use Debian practices e.g. Alioth notGithub, packages in main, and may not be necessary for Google- Zack and me: 'main' might not have to mean stable, and could includee.g. backports from unstable- almost everyone: “Debian Inspired” images with proprietary code, etca “slippery slope", don't do thisThanks to my colleague David for writing this up a day or two later -I've adapted these from his. They weren't written during the talk soI'm sure things got left out.There's also full video online from the video team. Here's one version:http://meetings-archive.debian.net/pub/debian-meetings/2013/debconf13/high/1004_Public_clouds_and_official_Debian_image_status.ogvLucas gave me some thoughts privately when I sent this to him a while back, but I'll leave it to him to repost his thoughts publicly.I just published the slides to Penta, but since Penta's attachment export for the anonymous view is broken and they're only ~120K, I'm attaching them to this email as well. If you redistribute the slides, it would make Google happiest if you include a link to the video so that everyone reading then has all the context easily available to them. Please pardon the few visual glitches that occurred during export to PDF format.- Jimmy