There are some newer technologies floating around that we may want to consider adding to the supported seed. These include: * Nginx - Has become de-facto scalable web server, and grown up as an OSS project now * Node.js - Gaining popularity fast, and *SHOULD* be a build-dep of OpenStack Horizon    - Also a direct dependency of the new Juju GUI * MongoDB (also headed for main as part of juju) -- Others? - seed prunin. Anything that can be dropped? Rationale: Goal:

An initial roundtable to help kick off this UDS.

Openstack QA workplan for Ubuntu. -- Add the following to the lab - quantum, ceph - james-page Add different deployment options on a less frequent basis - james-page Rationale: Goal:

The XCP Toolstack is an open source, server and cloud virtualization platform which provides a rich management API on top of the Xen hypervisor. The purpose of this blueprint is to discuss improvements to the Ubuntu XCP Toolstack that we wish to make during the Q-series development cycle. We would also like to discuss ideas for improving the interaction between the XCP Toolstack and other Cloud and Server managment interfaces, such as OpenStack, CloudStack, and Juju. Rationale: As a type-1 hypervisor, Xen provides various architectural benefits over KVM which make it well suited for the cloud. The XCP Toolstack is a Xen management platform which makes Xen easy to use, and integrates well with OpenStack and CloudStack. Goals: 1) To bring the XCP Toolstack in Ubuntu 13.10 on-par with XCP 1.6 and XenServer 6.1 in terms of feature parity and performance. 2) To build a development community around the XCP Toolstack and Ubuntu.

SRU process and schedule for Essex and Folsom. Rationale: Goal:

Xen is a mature, enterprise-grade, open-source type I hypervisor. This session we will give a brief project update about our recent 4.2 release and the roadmap for our upcoming 4.3 release. We will then discuss various topics about Xen integration in Ubuntu. A detailed feature list for 4.2 can be found here: http://wiki.xen.org/wiki/Xen_4.2_Feature_List There are two related features that are probably the most important from a user / integration perspective: * libxl has gone from being a "tech preview" to having an officially-supported stable interface. libxl is a library designed to allow all the basic hypervisor functionality in a consistent, stable interface which will be backwards-compatible. There are already libvirt bindings available for libxl (not sure which release this will be in). * xl is now the default toolstack, rather than xend. xl is built on top of libxl, and is meant to be a drop-in replacement for xm. It is entirely written in C (xend and xm are written in python). The main difference users see (other than performance improvements) should only be that they type "xl" instead of "xm" for their basic commands. Rationale: Goal: 1. To update other Ubuntu developers on the progress of the Xen project 2. To define what it would look like to have Xen be easy-to-use, robust, and reliable in Raring 3. To identify any changes which need to happen for #2 to take place.

Application server technologies such as Django, JavaEE or Ruby on Rails work in a similar way: an application server provides a runtime and services to a number of applications it hosts, such as access to data sources, configuration options, etc in a way that shields the applications from the underlying topology. This blueprint aims to extend the Juju subordinate service concept, provide support for a number of application server technologies in two ways: charms for some of the most common application servers and tools to enable users to create charms for their own application to be deployed on top of any compatible application server. Rationale: Goal:

Currently, virtualization infrastructure from qemu to openstack, does not fully comprehend architectures that are non-x86. While qemu has finally been built on powerpc in precise to enable a KVM enabled VM, things like libvirt and openstack do not entirely know about the existence and difference for non-x86 hosts and VMs. Enablement is needed so that these differences are apparent and so that jobs/VMs can be created as "generic" or specific to a certain architecture. == Comment == Hi Ben, Currently the session shortname (virt-powerpc) doesn't fit the convention for the tracks. Would you be able to determine where you think this best fits? -- Daviey Change to servercloud. -- BenC

We've learned a lot since the creation of charm helper. Debian packagers took 7 iterations before boiling all of debhelper's goodness into a declarative system. We can learn from them, and get there in our second iteration.

Openstack grizzly in Ubuntu Its big - who in the team knows which bits and where do we have gaps? -- james-page Rationale: Openstack has been in Ubuntu for 4 releases now and is established and stable. Folsom is the next release of Openstack and Ubuntu should have this release as well. Goal: Include the grizzly release in Ubuntu 13.04 and 12.04

Query2 was introduced during 12.04 as a new feature for machine read-able format. While the new JSON format describes the images, it is rather unweildy. In light of that, it is proposed to deprecate the new format and introduce a simplified format which is based on request. The new format will return results based on URL, for example: data=cloud&distro=lucid&arch=amd64&stream=server&instance_type=ebs&region=ap-southeast-1 Will return: {     "request": {         "allactive": "1",         "arch": "amd64",         "bad_asks": [],         "cloud": "EC2",         "data": "cloud",         "distro": "lucid",         "instance_type": "ebs",         "region": "ap-southeast-1",         "release_tag": "release",         "stream": "server"     },     "response": [         {             "arch": "amd64",             "build_date": "2012-09-13",             "build_id": "D87316017B9FF4490EF14CB7119E8995",             "build_serial": "20120913",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": true,             "published_date": "2012-09-13",             "published_id": "ami-903575c2",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-903575c2",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-07-26",             "build_id": "9CF68D8D8D3F9B9D529A0BA3FDE64B94",             "build_serial": "20120724",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-07-26",             "published_id": "ami-786d2c2a",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-786d2c2a",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-04-03",             "build_id": "BB64C065F8912EAC3947D7407FCC3F68",             "build_serial": "20120403",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-04-03",             "published_id": "ami-6c6f283e",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-6c6f283e",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-02-21",             "build_id": "98BD8363A17C49562E89D52DF2F05097",             "build_serial": "20120221",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-02-21",             "published_id": "ami-7089cd22",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-7089cd22",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         }     ],     "vendor": {         "name": "Canonical Group, Ltd.",         "product": "Ubuntu Cloud Images",         "product_eula": "http://www.ubuntu.com/project/about-ubuntu/licensing",         "product_url": "http://www.ubuntu.com"     },     "version": {         "epoch": 1348259881,         "uuid": "7c057ef45e1543df8d538bd55d466733"     } } Rationale: Goal:

= Rationale = As described in bug 972077, apt's on-disk format makes it difficult or impossible to update the archive without exposing a race condition to a client. While in theory potentially very small, in reality it makes 'apt' a very weak link in a automated install scenario. = Goal = Make apt hashsum mismatch errors go away permanently, and remove racey conditions when updating apt repositories.

Initially this came out as a discussion on #ubuntu-cloud (or was it #juju?) when swift CDN backed mirrors were announced for Amazon EC2 cloud. It is in a way related to servercloud-q-apt-improvements the hash based apt repositories. Debian has http://snapshot.debian.org/ repository. In essence it has every package, every version, every architecture, ever published in debian (more or less). Furthermore it also makes all of these packages available with standard apt-get, by storing and providing Releases/Packages files made by each publisher run (more or less). Currently in Ubuntu/Launchpad we do not have such facility. It is possible to retrieve individual source&binary packages from launchpadlibrarian, but the whole Ubuntu Archive is not available as of that point in time. Ideally if the Ubuntu Mirror is backed by immutable CDN, it should be relatively cheap to also store and server the repository files over the CDN to create equivalent service like snapshot.debian.org but only for the ubuntu archive. Another use case for this type of mirror would be the archive that currently holds automatically generated dbgsym packages. Currently dbgsym packages are not available for every single version of packages in the archive. And for launchpad/whoopsie/daisy retraces it has been requested to keep all versions of dbgsym packages and not remove them, otherwise retraces fail and we are loosing important information from submitted core dumps. Rationale: Goal:

Juju is subject to a rapid development pace, and will continue to do so. We should gate both trunks (python and go) on unit and functional tests passing. This should include some form of the official charm tests. This will require substantial infrastructure to test all providers such as MaaS.

Re-work packaging framework so its easier to work with and maintain. Rationale: Goal:

Now that OpenStack has matured even more, High Availability is one of the components on which more concentration is required. HA support for certain components of the infrastructure have been provided in the form of Resource Agents, however, these do not address some of the uses cases. In this session we will discuss the following: HA for RabbitMQ  - Active/Active  - Active/Passive HA for MySQL  - Active/Passive - DRBD  - Active/Active - Galera Quamtum  - quamtum-l3-agent (Active/Passive)  - quamtum-dhcp-agent (Active/Passive)  - quamtum-server (HAProxy) Nova  - nova-api (HAProxy)  - nova-scheduler (HAProxy) Cinder (HAProxy) keystone (HAProxy) Glance (Ceph)  - glance-api  - glance-registry == Other == Ceph  - Pacemaker support Qpid == Resource agents == openstack-resource-agents: - cinder-api - cinder-schedule - cinder-volume - glance-api - glance-registry - keystone - nova-api - nova-cert - nova-consoleauth - nova-network - nova-novnc - nova-scheduler - nova-volume - quantum-agent-dhcp - quantum-agent-l3 - quantum-server ceph-resource-agents

A roundtable discussion around MySQL in Ubuntu. Followup from UDS-Q and discussion of work items for this cycle. Rationale: Goal:

Query2 was introduced during 12.04 as a new feature for machine read-able format. While the new JSON format describes the images, it is rather unweildy. In light of that, it is proposed to deprecate the new format and introduce a simplified format which is based on request. The new format will return results based on URL, for example: data=cloud&distro=lucid&arch=amd64&stream=server&instance_type=ebs&region=ap-southeast-1 Will return: {     "request": {         "allactive": "1",         "arch": "amd64",         "bad_asks": [],         "cloud": "EC2",         "data": "cloud",         "distro": "lucid",         "instance_type": "ebs",         "region": "ap-southeast-1",         "release_tag": "release",         "stream": "server"     },     "response": [         {             "arch": "amd64",             "build_date": "2012-09-13",             "build_id": "D87316017B9FF4490EF14CB7119E8995",             "build_serial": "20120913",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": true,             "published_date": "2012-09-13",             "published_id": "ami-903575c2",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-903575c2",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-07-26",             "build_id": "9CF68D8D8D3F9B9D529A0BA3FDE64B94",             "build_serial": "20120724",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-07-26",             "published_id": "ami-786d2c2a",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-786d2c2a",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-04-03",             "build_id": "BB64C065F8912EAC3947D7407FCC3F68",             "build_serial": "20120403",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-04-03",             "published_id": "ami-6c6f283e",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-6c6f283e",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-02-21",             "build_id": "98BD8363A17C49562E89D52DF2F05097",             "build_serial": "20120221",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-02-21",             "published_id": "ami-7089cd22",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-7089cd22",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         }     ],     "vendor": {         "name": "Canonical Group, Ltd.",         "product": "Ubuntu Cloud Images",         "product_eula": "http://www.ubuntu.com/project/about-ubuntu/licensing",         "product_url": "http://www.ubuntu.com"     },     "version": {         "epoch": 1348259881,         "uuid": "7c057ef45e1543df8d538bd55d466733"     } } Rationale: Goal:

[RATIONALE]: Currently the Cloud Images are built and released based on upstream tests. The idea is that if the upstream tests work, that the images will just work. However, due to bugs hit this past cycle, and with the proliferation of new clouds, the need to validate that the cloud images work where they should and characterisiticly are what we say they are, is becoming apparent. Also, with the proliferation of new cloud vendors, there is a need to automate the release process. Some in the community have asked for a more frequent release cadance for the cloud images. As a result, for the R-cycle, we will implement testing and automation that will be aimed at ensuring enhanced quality of the images. [GOAL]:   1) Implement deeper testing for the Ubuntu Cloud Images   2) Improve the quality of the Ubuntu Cloud Images by pro-actively looking for regressions and stress testing.   3) Implement Automatic releases to increase the release cadance for the Cloud Images The following Tests will be implemented: * Image Characteristic Tests:   - Define attributes of a Cloud Image, i.e. prescense of certain files, file formats, and package sets. For example:         - precences of /etc/cloud and files under it         - check boot loader configruation for grub and grub2         - deeper cloud-init testing         - check SSH configuration * Bug regression tests: look over the Cloud Image bugs related to the bulding of the images. For example:     - check that /var/log/{btmp,wtmp,lastlog} exist     - In order for a cloud image bug to be "fixed released" a test should be written to prevent future regressions. * Image boot tests    - Test that QCow images boot on KVM and OpenStack    - Test that outputed files are valid    - Validate boot loader and console configurations * Image proactive bug searching in Cloud instances    - Fully excersize disk, I/O and network looking for potential bugs    - Increase Amazon instance sizes tested    - Excercise -proposed updates to check for issues which may cause problems    - Use of Juju for testing Juju/Cloud Integration    - Mock workload tests * Image performance testing    - Measure I/O performance to identify problems with kernels or userland configurations caused by updates or build process * Explore implementation of UTAH testing framework * Integration and publication of results to Jenkins Instance    - Add the daily images to iso.qa.ubuntu.com    - Automatically update test results to iso.qa.ubuntu.com For Automation: * Integrate testing into image build process.    - Daily images for the development release must pass characteristic and regression tests.    - Daily images for the stable releases must pass all tests to be published    - Milestones for the development image are subjected to all tests suites    - Introduce automatic promotion of QA'd daily images when the daily has a new kernel or boot-criticial (i.e. reboot required to use) package.        - Automate email announcement generation - Implement Twitter Announcements - RSS Feeds Feedback Requests (via the two major Ubuntu Cloud Lists) https://lists.ubuntu.com/archives/ubuntu-cloud/2012-October/000839.html https://groups.google.com/forum/?fromgroups=#!topic/ec2ubuntu/HLjoxOgOJ10

libvirt is the preferred virtualization management solution in Ubuntu.

In this session we will discuss: * New features for MAAS this cycle. * Bug fixing.

Things to fix for 13.04 in lp:charmworld, including addition of charm ratings to the UI. -Discuss adding any possible usage statistics -Discuss adding provider testing status Rationale: Goal:

Discuss state of Juju charms for deploying OpenStack. TODOs: - Quantum - SSL everywhere - HAproxy support for API server scale out and HA - HA rabbitmq and mysql - Nova compute live migration

lxc is the chosen lightweight (linux-guest-only) virtualization platform on Ubuntu.

The current Ubuntu Server Certified Hardware programme is a programme intended to ensure that a particular release of Ubuntu works, up to a certain level, with a specific hardware configuration. All tests in the Ubuntu Server Certified Hardware programme are hardware related, with no specific software stack tests. Some customers have been asking to create an extension of that programme that will specifically test a version of OpenStack, with a specific version of Ubuntu, running in a hardware configuration. This new programme will include new Open Stack tests and some hardware related ones for functionality that helps creating and managing a private cloud. These tests would be run on top of the Ubuntu Server Certified Hardware test suite and therefore, every server that is Ubuntu Cloud Infrastructure Ready will automatically appear in the list of Ubuntu Server Certified Hardware, specifying that the system is ready to be part of an Ubuntu Cloud Infrastructure deployment.

vmbuilder was once the supported method for creating virtualization images under Ubuntu. It has now been deprecated in favor of use of cloud images and other image creation tools. 'oz' is favored as a replacement as it essentially wraps the (fully supported and tested) ubuntu installer.

Discussion of the juju gui. Solicitation of feedback of current implementation and brainstorm discussion on new features and integrations for raring.

MidoNet is an advanced Software Defined Networking (SDN) solution, which provides network virtualization for public and private cloud environments. Adding MidoNet dependencies is the first step towards including MidoNet into ubuntu repositories for Ubuntu (possibly partner).

binfmt_misc (miscelaneous binary formats) is a kernel module which supports the specification of userspace interpreters for binaries executed by userspace. By specifying an invalid binfmt for ELF, it is possible for a confused chroot or package to destroy the ability of the host to execute any binaries. By introducing a namespace for binfmts, a chroot could be preventd from changing the binary formats usable on the host.

What's GOing on with Juju?

qemu-kvm is the preferred hardware emulation platform in Ubuntu. The goal of this work is to follow and help test upstream development, collaborate on bug fixing with upstream, and ensure that kvm is stable and fullfills our needs. In this cycle, we will focus on merging divergent source packages into one, and re-syncing our packaging as far as possible with Debian. This should result in increased testing for arm users, reduced duplication of effort between qemu-linaro and qemu-kvm sources, and increase collaboration with Debian. Etherpad: http://pad.ubuntu.com/uds-q-servercloud-r-qemu Blueprint: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-qemu

The kdump mechanism from the kdump-tool package is more flexible than its kexec-tool equivalent. It allows for multiple dumps to be collected, is the mechanism used in upstream Debian and has a configuration file that let the sysadmin controls some parameters. It is currently functional on Ubuntu but the documented way of gathering a kernel dump is to use the 0_kdump initscript delivered by kexec-tools which package the kernel dump file as an Apport bundle. While this solution is sufficient on Desktops, it becomes restrictive on server/cloud installs. Rationale: Current kexec-tool kernel dump capture mechanism is too limitative in a server/cloud environment Goal: Decide on the feasibility of using kdump-tool as default for server/cloud installs

Every UDS we have a Cloud Image Roundtable, Cloud Init Discussion. This UDS, we are going to consolidate the discussion of Cloud Images and the interaction with Cloud Vendors (including Cloud-Init and vendor tools). Cloud Images: * Carry over of recue images volumes from UDS-Q * Switch to UUID's instead of labels * Disk formats, or provide scripts for easy conversion between tools * Discuss usability of Cloud images in LXC and stand-alone KVM Cloud-Init: * Add short-hand for installing cloud vendor packages * Add support for IAM per-instance credentials * Customization of when Cloud-init runs? Package More tools:    - Cloud Meta-packages to install specific tools    - AWS       - Import/Export [1]       - CloudSearch [2]       - Elastic BeanStalk [3]       - MapReduce [4]       - SNS [5]       - Minor (single tools)           - CloudFront [6]           - Route 53 [7]    - HP Cloud        - Ruby Tools [8]    - Windows Azure Tools        - NodeJS CLI tool [9]        - Not packagable due to dependencies on NodeJS - Perhpas packe a helper script?    - Google Compute [10] Reformat cloud-images.ubuntu.com to use same Ubuntu.com format. [1] http://awsimportexport.s3.amazonaws.com/importexport-webservice-tool.zip [2] http://s3.amazonaws.com/amazon-cloudsearch-data/cloud-search-tools-1.0.0.1-2012.03.05.tar.gz [3] https://s3.amazonaws.com/elasticbeanstalk/cli/AWS-ElasticBeanstalk-CLI-2.1.zip [4] http://elasticmapreduce.s3.amazonaws.com/elastic-mapreduce-ruby.zip [5] http://sns-public-resources.s3.amazonaws.com/SimpleNotificationServiceCli-2010-03-31.zip [6] http://d1nqj4pxyrfw2.cloudfront.net/cfcurl.pl [7] http://awsmedia.s3.amazonaws.com/catalog/attachments/{dnscurl.pl,route53tobind.pl,bindtoroute53.pl,route53zone.pl} [8] https://docs.hpcloud.com/cli/unix [9] https://github.com/WindowsAzure/azure-sdk-for-node [10] https://developers.google.com/compute/docs/gcutil/ [RATIONALE]: To enable the use of Ubuntu regardless of the Cloud [GOAL]: Provide native packaging for all major cloud vendors.

Rationale: By improving the basic level of testing that can be applied to all packages in the server supported seeds, we decrease the amount of manual testing effort required during the development release and to support stable release updates. This reduces the risk of changes impacting basic functionality of supported packages. Goal: DEP-8 tests for all supported server packages. UTAH tests using DEP-8 tests for testing.