Cloud team BoF ============== DC17, Montréal pls read IRC ;-) Status update ------------- Had a great sprint last year, and lots of plan happened Not a *huge* amount of work on that plan since... :-/ kuLa working on builds for AWS and GCP on casulana AWS: noahm and KuLa have made progress using FAI? GCE: Still using the bootstrap-vz tooling, just updated for Stretch Azure: using openstack-debian-images, updated to Stretch Openstack: Using openstack-debian-images (same as for wheezy & jessie). Now have arm64 images too \o/ Vagrant: work on porting images generation to FAI ported to the same git repo Tests ----- Still need to work on testing images using the set of tests that we made last year. Once we have that, we can agree on moving over to FAI and validating image builds for all platforms. We can also agree on FAI now? serpent has volunteered to drive the test suite work for our images. What exactly are the current cloud providers testing, and how? Steve Z listed some tests [will grab from video later...] relevant work from a startup doing clouds comparison: https://github.com/cloudscreener/debian-image-tester Azure test suite is platform: - https://github.com/Azure/azure-linux-automation GCE tests listed too, for platform integration: - Any and all metadata interaction - image configuration is correct - new infrastructure changes that may not be released yet zigo: need sponsored hardware to run an OpenStack one time deployement, and test on the image on it. Test suite and scenarios (tempest), install scripts (openstack-deploy package) are all in Debian (Stretch included). We should be building images on the d.o machines - will do that for FAI-built images casulana (the new build machine is hosted at bytemark in the UK) Do we have any way of doing bare-metal testing there alongside the image builder? Long story, but *no* Vagrant boxes should be built on the same infrastructure too, using VMs there. Want to be doing CI and automated build and uploads. Test using FAI to make images for all the platforms, and debug any problems we find. Zach tried it for GCE Stretch and got images that didn't boot. Can we debug that? :-) Once we have validated all that, we should be building all centrally and working from there. We can set up as many VMs as we need. We could be building in temporary VMs (one for each build, created on demand). We should have a set of tools to create VMs and run the build there. Do *not* want to build on the bare hardware because we don't run processes as root on the bare hardware. Also need something generic so we can run the same process (build VM, run in VM, etc.) on local machines as well as on casulana to help with development and testing. Since fai-diskimage requires root the build should take place in a VM. If we build on Casulana (England) we still should publish on debian-cd image on sweden. Network is very good so moving images between the two hosts should not be a problem. Todo: - Test the result image of the Azure patch merge inside current version of openstack-debian-images (ie: finish the merge) - Test if the OpenStack image works on AWS (no reason it wouldn't) Package updates --------------- Release team are of course happy for us to get things updated in stable, modulo sanity. We just need to do the work. cloud-init ---------- Did we make any progress on upstreaming etc.? We're not really tracking the ubuntu upstream at the moment. We were worried about lack of progress, but upstream seem to have improved. Need to check on status of the changes we were talking about. Cloud-init sprint at the end of August at Google Seattle - anybody going? Please make sure we're involved. We're worried about lack of cross-distro support! Plans ----- Next cloud sprint - suggested dates Mon 16 to Wed 18 October at Azure offices in Redmond. Not *yet* set in stone, see mail to the list for confirmation. Space for plenty of people to turn up, and we'll be online too Discussion ---------- If people need Azure accounts, just sign up for (MSDN?) account, tell zobel/Steve Zarkos/ask friendly on debian-cloud@l.d.o and that comes with $150 credit per month Credentials: Looking at exposing Debian identities to the cloud services so we can manage access as needed directly from Debian (luca) kula keen on helping with this from cloud team side