Technology update, QML2, architecture changes, Ubuntu needs..

Discuss HA for OpenStack components (RabbitMQ, MySQL, Keystone, Glance) based on the discussion at the OpenStack Design Summit.

Discuss current state of the Juju charms for deploying Openstack on Ubuntu and define what is needed to cover new Openstack components being added during Folsom/Quantal.

Promote and run a successful series of online app developer events, including at least: - The Ubuntu App Developer Week - The Ubuntu App Developer Contest

A round table discussion around MySQL in Ubuntu.

A round table discussion around MySQL in Ubuntu.

GlusterFS 3.3 brings significant improvements in the cloud area, with better support for VM image storage, as well as object storage and an HDFS compatibility library. We think this release will be useful for OpenStack deployments, and we'd like to create an integrated stack that utilizes GlusterFS - both for object storage (Swift interface) and VM image storage.

Mozilla SUMO is the product that powers support.mozilla.org and we are aiming to transition help.ubuntu.com in its entirety to SUMO in the Q-Cycle or at the very least get excellent work done towards that goal.

Continuation of Monday's session. Solving design problems together.

This blueprint is just a placeholder for scheduling purporses. For the description please go to: https://blueprints.launchpad.net/certify-planning/+spec/cert-q-external-testing

mdadm currently has a gaggle of open bugs, and every cycle the RAID ISO tests produce new and interesting bugs. It seems like we're doing something a bit wrong with Software RAID. There are some valid solutions here: https://wiki.ubuntu.com/ReliableRaid which should be discussed and either refuted or implemented.

Fedora has decided that they are going to merge {/bin,/lib,/sbin} into /usr. https://fedoraproject.org/wiki/Features/UsrMove This means that upstream support for distinguishing between / and /usr for early boot services will atrophy more than it already has, and there will be extra work involved for Ubuntu to maintain this capability. Furthermore, if we can rely on /usr to be mounted when upstart starts, we can simplify a number of system jobs. Explore whether we should change initramfs-tools in Ubuntu as well for 12.10 to provide this guarantee.

Review the buildd resources available for the distro builds and various test builds, discuss buildd uses outside the core distro team (like daily Go builds, and unity test builds).

Identify and engage targetted upstreams to submit their apps to the Ubuntu Software Centre

Part two of: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database

Hands on help with Launchpad bugs and getting involved in contributing to Launchpad

Provide support and mentoring resources for upstream app developers who want to port or integrate their application with Ubuntu and Unity

Continuation of Push to the Clouds 1. Publishing image meta-data via Glance Servers: Hardware is till pending on the production servers. Glance.ubuntu.com has been provisioned with a staging host. Discussion: 1. What images do we want to publish? 2. Do we need to produce -disk1.img (KVM compataible boot images) for pre-Precise images? 3. Are the disk image formats provided on cloud-images.ubuntu.com adiquate? Do we need to produce other disk image types? 2. Publishing of official Ubuntu images on other cloud vendors .

Easy docs and stuff for people

Integration with a hardware database. Pig or Hive (Hadoop) support. Backporting the reporting client (whoopsie) to previous Ubuntu versions. Discuss the state of Upstart's inotify event support. Further changes to the statistics website. API requirements. Sort out our story on mean time between failures (http://paste.ubuntu.com/957235/, http://instagr.am/p/KDe4WPhRxl). Additional problem types (desktop application hangs, package installation failures, debconf dialogs during package installation, ...) Providing an apport API for applications handling recoverable errors. Surfacing architecture (and other data points) only when relevant Should we continue to process and retrace crashes from derivatives? Can we set /proc/sys/fs/suid/dumpable to 2? (programs not normally dumped are dumped, but only readable by root). We need some way of ensuring we never ever send cores from ssh-agent, among others. ... Other crash database blueprints: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database-2 https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-metrics https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-updates-from-crash-reports https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-fix-ddebs https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-bucketing-improvements https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-phased-updates Additional background information: http://paste.ubuntu.com/958213/ Specification (read this first): http://wiki.ubuntu.com/ErrorTracker

System management and service orchestration for ARM Server, including MAAS and juju enablement.

The x32 ABI (http://sites.google.com/site/x32abi/) provides a compromise between IA32 and x86-64: it has a 32-bit pointer size, which is more memory-efficient and may often be faster, but has 64-bit registers and a larger register file. Support for it is gradually trickling into various relevant upstreams (kernel, glibc, gcc, etc.). Although the pieces are unlikely to be in place in time for 12.10, we should think ahead for how we might deploy this in Ubuntu.

Review the current process and identify which parts of the documentation need to be improved. Also figure out what specifically we expect from upstreams and which help the ARB can provide.

== Degraded Hardware Notifications == There are multiple ways hardware can degrade on the machine you are using. * degraded RAID * 100% disk space usage * 100% inode usage * S.M.A.R.T. - failing hardware * etc (?!) == Current notifications == * are sometimes annoying (endless popups on desktop for SMART) * non-existent AFAIK (inodes) * not configured out the box (degraded RAID http://pad.lv/535417) == Proposed notifications == Sometimes a user may not have the permissions to rectify the problem. The notification should stay persistent, until fixed. These notifications are important across all installation types. This notifications should not replicate Nagios/Check_Mk monitoring. * system indicators (Ubuntu Desktop) * byobu plugin (Ubuntu Server) * MOTD (Ubuntu Core) * landscape notifications * others ?! (Virtual Machines, cloud instance, etc) == UDS session == * Discuss what notifications we would like to implement * How/where/who will implement them

The Ubuntu Youth team has been dead for a few years. It was a place where youth people can find others from their ages, and discuss about Ubuntu and what can they do about it. My intention with this session would be to find ways to revive this group, and also to define this group purpose and main vision for now on. Also, discussing how to promote it, how its leadership is going to be taken (Point for Philip Ballew, current Team leader) and how to give it an useful position in the community are points that are important to be taken care of during this session.

From the specification (https://wiki.ubuntu.com/ErrorTracker): "If a software update is known to fix the problem, replace the primary alert with the software update alert (or progress window, depending on the update policy), with customized primary text. Or point them at a web page (not a wiki page!) with details if a workaround exists, but no fix is available yet." Should we show the crashes the user has received that are now fixed by a software update in the description of that update? Should we provide a flag to automatically install updates that fix problems which left the system in an unusable state?