[15:59] <lynxman> o/
[16:00] <jamespage> o/
[16:00] <hallyn> \o
[16:00] <smb>  /o\
[16:00] <roaksoax> o/
[16:00] <jamespage> smb: that bad?
[16:00] <utlemming> o/
[16:01] <smb> jamespage, maybe not. just trying to cope with multiple streams of input :)
[16:01] <zul> heylo
[16:02] <jamespage> ok - lets get started
[16:02] <jamespage> #startmeeting Ubuntu Server Team Meeting
[16:02] <meetingology> Meeting started Tue Apr  3 16:02:27 2012 UTC.  The chair is jamespage. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:02] <adam_g> o/
[16:02] <jamespage> #topic Review ACTION points from previous meeting
[16:03] <jamespage> SpamapS: invite aquette to next server team meeting to discuss servercloud-p-cloud-power-management
[16:03] <smoser> o/
[16:03] <jamespage> hmm - guess that either did not happen or aquette could not make it
[16:04] <jamespage> moving on
[16:04] <jamespage> #topic Precise Development
[16:04] <jamespage> #topic Release Bugs - http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:04] <jamespage> OK  - lets do the list...
[16:05] <jamespage> bug 960276
[16:05] <jamespage> zul - has the new patch for console logging landed yet?
[16:06] <zul> jamespage: landed in our packaging hasnt landed upstream yet
[16:06] <jamespage> zul: ack
[16:07] <jamespage> bug 883988
[16:07] <adam_g> jamespage: fixed upstream finally, will trickle into ubuntu with our next glance upload
[16:07] <adam_g> or Essex final
[16:07] <jamespage> +1
[16:07] <zul> or rc3
[16:07] <jamespage> lol
[16:07] <jamespage> bug 924739
[16:08] <jamespage> adam_g, I said I would help out with that last week - my bad - catchup later
[16:08] <jamespage> bug 928990
[16:08] <adam_g> k
[16:08] <lynxman> o/
[16:09] <jamespage> utlemming, found any time to look at that yet?
[16:10] <utlemming> I started, but got distracted on other things. I hope to get that done this week.
[16:10] <jamespage> utlemming, ack - I'm going to assign you the bug (had to think hard back to last week)
[16:10] <jamespage> bug 930916
[16:10] <jamespage> assigned to SpamapS
[16:10] <jamespage> who is not here....
[16:11] <jamespage> I'll poke him about that and some php5 stuff as well later
[16:11] <jamespage> adam_g: bug 966115
[16:11] <adam_g> jamespage: on my TODO today
[16:11] <jamespage> \o/
[16:11] <jamespage> great
[16:11] <jamespage> bug 880339 appears to be blocked on lack of information from the reported ATM
[16:12] <jamespage> bug 907197
[16:12] <jamespage> zul: still pending a response? have you seen this issue yourself?
[16:12] <zul> no i havent, i think we should take it off our list
[16:13] <jamespage> zul: as we don't have confirmation at this point I think that makes sense
[16:13] <jamespage> bug 916065
[16:14] <jamespage> I need to catch SpamapS about
[16:14] <jamespage> bug 966069
[16:14] <jamespage> looks like that is pending upload?
[16:15] <jamespage> yes it is...
[16:15] <adam_g> jamespage: waiting for the horizon rc
[16:15] <jamespage> bug 967430
[16:16]  * ttx is waiting for the horizon rc too
[16:16] <ttx> damn californians
[16:16] <ttx> adam_g: note that Glance RC3 will include your db fix
[16:16] <adam_g> ttx: saw that one, thanks
[16:17] <jamespage> marvellous
[16:17] <ttx> should be out today or early tomorrow
[16:17] <jamespage> roaksoax, are you going to have time to pickup bug 967430?
[16:17] <roaksoax> jamespage: i sure hope so
[16:17] <roaksoax> by the end of the week
[16:18] <jamespage> great
[16:18] <roaksoax> assigning it to myself
[16:18] <jamespage> roaksoax, one step ahead of you...
[16:18] <jamespage> bug 901881
[16:19] <adam_g> jamespage: still waiting on the keystone MIR to create the direct Depends
[16:19] <zul> jamespage: im hoping next week for that one
[16:19] <jamespage> zul: ack
[16:20] <jamespage> scans the rest of the list....
[16:20] <jamespage> there are a few FTBFS that need dealing with - genshi is already on the report
[16:21] <jamespage> but I also saw pacemaker and heartbeat in the latest rebuild test....
[16:21] <jamespage> I'll get bugs raised and them added to the list...
[16:21] <jamespage> #action jamespage to raise bugs for FTBFS for server related packages from latest rebuild test.
[16:21] <meetingology> ACTION: jamespage to raise bugs for FTBFS for server related packages from latest rebuild test.
[16:21] <adam_g> i fixed the cluster-glue build last night, that should resolve the pacemaker + heartbeat builds. is there a way to re-trigger those without a new upload to each, now that the dependency is fixed?
[16:22] <roaksoax> uhmm I though I had fixed pacemaker's FTBFS
[16:22] <jamespage> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120328-precise.html
[16:22] <jamespage> roaksoax, looks like there is a new one :-)
[16:22] <roaksoax> adam_g: yes, with a no change upload. I'll take care of it
[16:23] <adam_g> thanks
[16:23] <jamespage> those two packages both have the same issue - glibc headers have changed structure...
[16:23] <jamespage> memcached is also failing tests on i386 - I'm looking at that
[16:23] <adam_g> the issue was in the cluster-glue library they build against, which is fixed now. they should both build okay
[16:24] <jamespage> MIR's - zul: sounds like keystone should be complete in the next week or so?
[16:24] <zul> hopefully
[16:24] <zul> i think most of the issues have been resolved, horizon is next on the list i think
[16:24] <roaksoax> adam_g: awesome!
[16:24] <jamespage> roaksoax, how about the cobbler MIR?
[16:26] <roaksoax> jamespage: looking at it now
[16:26] <roaksoax> jamespage: jdstrand has it assigned so I guess he's conducting his review work on it, or he will soon
[16:26] <jamespage> great
[16:26] <roaksoax> MAAS is also queued
[16:27] <jamespage> Final Freeze kicks in on the 12th of April which is only 9 days away
[16:27] <jamespage> busy busy busy!
[16:27] <roaksoax> s/queued/waiting for final review after commends/
[16:27] <jamespage> next
[16:27] <jamespage> #topic Blueprints - http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html
[16:28] <jamespage> I did have a quick scan through these before the meeting
[16:28] <jamespage> I could not see anything I though needed specific dicussion but please can you all start to review any outstanding work items you have
[16:28] <jamespage> and POSTPONE anything that won't make this release.
[16:29] <jamespage> anything that needs to make this release but is in trouble - start shouting loud!
[16:29] <jamespage> Anything else anyone wants to mention about precise development?
[16:30] <jamespage> great
[16:30] <jamespage> #topic Ubuntu Server Team Events
[16:30] <jamespage> Openstack Developer Summit in two weeks time
[16:31] <jamespage> a fair few people are attending summit and/or conference
[16:31] <jamespage> any other events people want to mention?
[16:32] <jamespage> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:32] <jamespage> hggdh - around?
[16:32] <jamespage> all yours
[16:33] <jamespage> or maybe not
[16:34] <jamespage> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:34] <smb> Hi. I think I found another thing where libvirt does not exactly do the right things with xen. Affecting HVM guests. Luckily it is not fatal-
[16:34] <smb> Need to dig a bit more there.
[16:34] <smb> Beside that...
[16:34] <smb> Daviey, iscsitarget?
[16:34] <zul> iscsitarget?
[16:34] <jamespage> smb: iscsitarget?
[16:34] <smb> zul, A fix I backported to the package, but I cannot upload
[16:35] <smb> bug 962332
[16:36] <Daviey> smb: So, sorry
[16:36] <Daviey> smb: I will make sure it is uploaded *today* without fail.
[16:36] <smb> Daviey, Thank you master. :)
[16:36] <jamespage> smb: any other kernel related matters to raise
[16:36] <jamespage> ?
[16:36] <jamespage> or does anyone have anything they want to raise with smb?
[16:36] <smb> I don't think so
[16:37] <jamespage> OK
[16:37] <jamespage> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:37] <rbasak> Nothing to report. Any questions for me?
[16:37] <jamespage> ARM server all looking sweet for precise then?
[16:38] <rbasak> It looks good
[16:38] <jamespage> #topic Open Discussion
[16:38] <jamespage> I have one item to raise
[16:39] <jamespage> Ursinha has now fixed the Triage Report - http://reports.qa.ubuntu.com/reports/ubuntu-server/triage-report.html
[16:39] <Ursinha> \o/
[16:39] <jamespage> we have alot of 'New' bugs - bugs which have been assigned a priority but triaged no further than that.
[16:39] <jamespage> about 260 of them
[16:40] <jamespage> (thanks Ursinha)
[16:40] <hallyn> tnachen: \o
[16:40] <zul> jamespage: keeping you busy i see :)
[16:40] <jamespage> it would be great if people can ensure that these get some focus of the next week or so - specifically anything that might be an issue in precise
[16:41] <jamespage> I found at least three this morning
[16:41] <hallyn> tnachen is looking at getting involved with ubuntu server, and managed to sit through this whole meeting.  just wanted to introduce him
[16:41] <jamespage> hi tnachen: welcome!
[16:41] <tnachen> hi all, I emailed to ubuntu-server about the mentor program I saw on the wiki
[16:42] <tnachen> and hallyn gladly to volunteer to lead the newbie (me)
[16:42] <tnachen> I'll be working with him to learn more about libvirt and hopefully contribute!
[16:42] <jamespage> \o/
[16:42] <hallyn> i second that exuberance
[16:42] <rbasak> I'm waiting on bug 968753 to be sponsored - it looks like an issue with ssh on precise but on i386 only. I presume it'll be picked up in time.
[16:43] <rbasak> (it got reported over the weekend with a pile of dupes)
[16:43] <jamespage> rbasak, poke someone if it does not get picked up before the weekend
[16:43] <rbasak> jamespage: will do, thanks
[16:43] <jamespage> anything else?
[16:44] <jamespage> ......
[16:44] <jamespage> .....
[16:44] <jamespage> ....
[16:44] <jamespage> ...
[16:44] <jamespage> ..
[16:44] <jamespage> .
[16:44] <Daviey> o/
[16:44] <Daviey> Comgrats jamespage :)
[16:45] <Daviey> Congrats*
[16:46] <jamespage> #topic Announce next meeting date and time
[16:46] <jamespage> Tues 10th April 1600 UTC - back here again!
[16:46] <jamespage> see you all then!
[16:46] <jamespage> #endmeeting
[16:46] <meetingology> Meeting ended Tue Apr  3 16:46:59 2012 UTC.
[16:46] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-03-16.02.moin.txt
[16:46] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-03-16.02.html
[16:48] <jamespage> thanks Daviey!
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Apr  3 17:00:57 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:01] <jsalisbury> # Meeting Etiquette
[17:01] <jsalisbury> #
[17:01] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:01] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:01] <tgardner> o/
[17:01] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:01] <cking> o/
[17:01] <apw> o/
[17:01] <henrix> o/
[17:01] <sforshee> o/
[17:01] <ppisati> o/
[17:01] <ogasawara> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> P/omap4: mainly config changes trying to mimic master/generic config as much as possible. The dss/video issue (lp963512) found in the previous rebase is still unresolved (waiting for a new panda board since my own broke down exactly the day after the issue came up) - for the time being (kernel freeze) we are gonna stay with 3.2.0-1411.14 as it is good and no one complained about it, but as soon as i get the new board, it'll be a 
[17:01] <ppisati> lp971091 ("Pandaboard ES freezes with the default CPU scaling governor ondemand"): i'm investigating this one with the reporter (sending debug kernels&c).
[17:01] <ppisati> ..
[17:02] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:02] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:02] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-ubuntu-12.04.html
[17:02] <ogasawara> || apw       || hardware-p-kernel-delta-review         || 1 work item  ||
[17:02] <ogasawara> || ogasawara || hardware-p-kernel-config-review        || 1 work item  ||
[17:02] <ogasawara> ||           || hardware-p-kernel-versions-and-flavors || 2 work items ||
[17:02] <ogasawara> apw and I are aware of our work items, we'll get them closed before final.
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Blueprint: hardware-p-kernel-power-management (cking)
[17:02] <cking> Power management:
[17:02] <cking>  * Unity 2D vs 3D on Precise Beta 2 measurements
[17:02] <cking>    http://zinc.canonical.com/~cking/power-benchmarking/unity-beta2-results
[17:02] <cking>    And that wraps up these Blueprint items for Precise.
[17:02] <cking> ..
[17:03] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:03] <ogasawara> Kernel Freeze is this Thurs Apr 5.  I've already began prepping our
[17:03] <ogasawara> final upload prior to freeze and plan to upload after the meeting.  If
[17:03] <ogasawara> they are any patches which need to land, let us know immediately.  After
[17:03] <ogasawara> Kernel Freeze, all patches are subject to our SRU policy and uploads
[17:03] <ogasawara> will only be granted at the discression of the release team.
[17:03] <ogasawara> https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara>  * Thurs Apr 5 - Kernel Freeze (~2 days)
[17:03] <ogasawara>  * Thurs Apr 12 - Final Freeze (~1 week)
[17:03] <ogasawara>  * Thurs Apr 19 - Release Candidate (~2 weeks)
[17:03] <ogasawara>  * Thurs Apr 26 - Final Release (~3 weeks)
[17:03] <ogasawara> ..
[17:04] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:04] <apw> Currently we have 72 CVEs on our radar, with one new CVE added this week.
[17:04] <apw> See the CVE matrix for the current list:
[17:04] <apw>  
[17:04] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:04] <apw>  
[17:04] <apw> Overall the backlog has increased by one CVE this week:
[17:04] <apw>  
[17:04] <apw> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:04] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:04] <apw>  
[17:04] <apw> ..
[17:04] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:04] <bjf> Here is the status for the main kernels, until today (Apr. 03):
[17:04] <bjf>  
[17:04] <bjf>  * Hardy    - 2.6.24-31.101 - Nothing this cycle
[17:04] <bjf>  * Lucid    - 2.6.32-41.88  - Verification; 52 commits in total.
[17:04] <bjf>  * Maverick - 2.6.35-32.68  - Verification; 9 commits in total. NOTE: THIS IS THE LAST MAVERICK KERNEL!
[17:04] <bjf>  * Natty    - 2.6.38-14.58  - Verification; 12 commits in total. Mostly eCryptfs and KVM.
[17:04] <bjf>  * Oneiric  - 3.0.0-17.30   - Verification; 4 stable upstream releases (194 commits).
[17:04] <bjf>  
[17:04] <bjf> Current opened tracking bugs details:
[17:04] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <bjf>  
[17:04] <bjf> For SRUs, SRU report is a good source of information:
[17:04] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <bjf>  
[17:04] <bjf> Future stable cadence cycles:
[17:04] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:04] <bjf> Note: We are seeing some issues being reported for the Oneiric kernel. We
[17:04] <bjf>       are hitting these as we become aware of them.
[17:04] <bjf> ..
[17:05] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Apr  3 17:05:40 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-03-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-03-17.00.html
[20:02] <czajkowski> ogra_: highvoltage stgraber drubin ping
[20:02] <highvoltage> pong
[20:02] <czajkowski> EMEA
[20:03]  * highvoltage is ready to vote
[20:03] <highvoltage> :p
[20:03]  * stgraber waves
[20:03] <ogra_> oops, i'm late
[20:03] <czajkowski> need someone else
[20:03] <czajkowski> huzah
[20:03] <czajkowski> we have 4
[20:03] <highvoltage> ogra_: you're actually early! I was just joking
[20:03] <ogra_> do we have utlemming ?
[20:04] <stgraber> oh right, utlemming, I'm ready to vote ;)
[20:04]  * ogra_ too :)
[20:04] <iulian> 'ey!
[20:04] <czajkowski> utlemming: ping
[20:05] <stgraber> czajkowski: I'm poking him
[20:08] <stgraber> let's see if that helped
[20:10] <stgraber> apparantly not
[20:11] <czajkowski> came home for nothing :(
[20:11]  * iulian sighs.
[20:11] <highvoltage> well, look at it this way. you have a free hour now :)
[20:13] <czajkowski> aye get back into car and drive back to family meet up
[20:13] <czajkowski> toodles
[20:13] <highvoltage> czajkowski: unless we take it to email?
[20:13] <highvoltage> ok, sounds fine. meeting adjourned then?
[20:13] <ogra_> why would we ? the applicant didnt show up
[20:13]  * iulian nods.
[20:13] <ogra_> yeah, adjourned i'd say
[20:14]  * ogra_ vanishes off into the night 
[20:14] <iulian> I personally don't think we should take it to email. But it's up to you guys.
[20:14] <highvoltage> nah
[20:15] <highvoltage> (nah as in, "yes, indeed")