Ubuntu Server Bug Triage Process

Hi Team

Post discussion on this ML and at UDS-Q I've written up what I think
is the bug triage process we should be following for server bugs:

  https://wiki.ubuntu.com/ServerTeam/KnowledgeBase/BugTriage

I tested this during my triage session yesterday and it covered all of
the bugs that I triaged.

This is v1.0 - please review - happy to discuss changes and make
updates if people think that it needs improvement.

Cheers

James

--

-- 
James Page
Ubuntu Core Developer

Byobu autostart from cron

precise LIO target with iscsi support

Re: Ubuntu 12.04 / kvm / libvirt / problem with network bridge br0

MAAS Install issue

resolv.conf

Ubuntu 12.04 / kvm / libvirt / problem with network bridge br0

Ubuntu server 12.04 locate problems

Server-Installation 12.04 / automatic seciruty updates

Hi,

when installing ubuntu server 12.04 I was asked, of I want to active the 
automatic security update (service). I said "no". How can I install it 
now? Is it a specific apt-package?

Thanks for any hint
-Thorsten-

Use of Blueprints + Blueprint Template

Hi Team

I've spent some time with various members of the Ubuntu Server Team
over the last few weeks reviewing how we use blueprints to track
progress during the development cycle.

This was really with the objective of trying to resolve a few
challenges that we have with current usage:

1) It's often hard to evaluate exactly when a blueprint has been
completed.

2) We sometimes have challenges with understanding the use cases for
work.

3) What the overall goal is for a blueprint is not always clear.

4) Endeavouring to bake QA into all work we do.

When I first started contributing to Ubuntu we did try to write
specifications associated with each blueprint (see [0] for the
template).

I think that this approach did not work that well - often the spec did
not get updated throughout the cycle as the primary focus is normally
on work item tracking in the blueprint - so they age and become pretty
useless very quickly.

That said there are a few concepts in the specification template that
I think would still benefit our use of blueprints.  So I'd like to
propose bringing in some of the concepts we had in specs to the
blueprint summary and whiteboard.

1) Blueprint Summary

Rationale:

One or two paragraph statement about why we are doing this blueprint.

Goal:

Overall goal for the blueprint.

2) Blueprint Whiteboard

User Stories:

User stories really help thrash our what the requirements are and why
we are actually doing the work.  They should try and encompass how you
think the output of the blueprint will be used by real people.

There may of course be multiple stories for more complicated work.

Assumptions:

What assumptions are being made about the delivery of the blueprint.

Test Plans:

This is really about validating user stories; I find its helpful to
think about these as high level processes - then they can either be
hand cranked by people who want to try stuff out or do manual QA OR
they can be automated.

..or they might even be covered by existing automated test cases.

Release Note:

One or more suitable statements that could be included in the release
note for the release associated with the blueprint.

I've worked this into one of the blueprints that I will be driving
this release which is a) simple and b) already well defined - see [1].

So a few comments about the above:

1) Its not going to fit every blueprint we write - but I think it
should cover most of them!

2) I think that having everything in the blueprint will help with
keeping it up-to-date as its the place we all go to see what needs to
be done.

3) Interested people only have to subscribe in one place and they can
then see when stuff is updated.  Has anyone ever subscribed to a spec
in the wiki?

4) The original Specification template also included a section for
'Design' - I personally think that Design should really live past the
 lifetime of a single blueprint and should be delivered as
documentation  - probably in the wiki - and referenced from the blueprint.

I will be doing this for my blueprints this cycle - it would be great
if other people could try this out as well as they write up their
blueprints from sessions at UDS.

One feature that is currently lacking in the whiteboard is the ability
to track changes over time (although you could do this through
diligent monitoring of blueprint email spam).  Its possible that we
might start managing the whiteboard content in a bzr branch and
updating the blueprint periodically - but that's still work in progress.

Cheers

James

[0] https://wiki.ubuntu.com/SpecSpec
[1] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-tomcat7
--

-- 
James Page
Ubuntu Core Developer

fsck of LVM snapshot - different behaviour in 12.04

Hi list,

[I sent this a few days ago but it doesn't seem to have come through; 
apologies if you're reading it for a second time.]

I'd like to (ab)use LVM snapshots for a periodic online fsck in the 
background.  The essence of the script is something like this:

lvcreate -s -L $snapsize vg0/srv
e2fsck -p /dev/vg0/lvol0 # discard orphaned inodes
e2fsck -fy /dev/vg0/lvol0
lvremove -f vg0/lvol0

On Lucid, this seems to work well.  On Precise, I get some false 
positives almost every time I run it: wrong free blocks/inodes count, 
and/or bitmap differences.  The filesystem is actually OK; none of these 
minor inconsistencies show up during a boot-time fsck.

My understanding is that ext4 is wired up with LVM to do a sync and 
clean up these inconsistencies at the time a snapshot is made, and 
certainly on Lucid it seems OK.  Can anyone tell me if the behaviour has 
changed, or if I'm doing something wrong?

So far I've reproduced this on my workstation and laptop (one SATA drive 
each) and on one scratch server (Dell CERC RAID, five SATA drives).  All 
of this is on bare metal and local storage.

I searched around a bit but the only thread I found is [1] which doesn't 
seem relevant -- I can't reproduce his error.

[1] https://lkml.org/lkml/2012/1/5/76

--

-- 
Ryan Tandy - Programmer/Analyst           rtandy <at> sd63.bc.ca
School District 63 (Saanich)                +1 250 652 7385