/srv/irclogs.ubuntu.com/2008/10/14/#ubuntu-meeting.txt

=== Rafik_ is now known as Rafik
=== asac_ is now known as asac
* persia prepares11:54
amachupersia: elkbuntu: TheMuso: lifeless: Hi every body!11:55
TheMusoHey amachu.11:55
TheMusoIt appears we have nobody on the agenda.11:55
amachuHi TheMuso :-)11:56
amachubelutz had mailed that he might join!11:56
persiaNobody on the agenda might mean a short meeting.  Did we get more thoughts on timing/composition that I missed?11:57
amachunext week is the right time we take what we discussed last week on time and additional members on board to the CC!11:57
persiaIndeed.11:58
amachupersia: not much to those what we discussed, may be TheMuso, lifeless can add their thoughts12:00
amachufor yourself, me and elkbuntu three were discussing on that much!12:00
TheMusoI have nothing to add. I can do earlier in the evening, but not later. However I know this affects others, so really don't know.12:00
persiaOr belutz or zakame12:00
TheMusoAll I can say is name a time, and I'll say yes or no as to whether I can do it.12:01
persiaTheMuso, The proposal was for 9:00 and 15:00 UTC.  Would the former work for you (on Tuesdays)?12:01
TheMusopersia: 9:00UTC would suit me very nicely.12:02
persiaTheMuso, That's what was thought, that it would be better for those in +10 or greater, whereas 15 would be better for those in +7 or less.  Those in +8 or +9 probably find the current time very convenient.12:03
amachupersia: 15.00 would suit Indian time, 9.00 might suit others better..12:03
amachupersia: yes.. We need to check with belutz and zakame12:03
amachulet me check for the participant for the day :-)12:04
amachuamireldor?12:04
amachusvaksha?12:04
amachustefanlsd?12:04
amachuit appears none of them is here!12:04
TheMusoI thought we had stefanlsd? approach us already...12:05
TheMusogah cut and paste12:05
amachushould I go ahead and take names of svaksha and amireldor from the agenda for they aren't turning up for a long time? they can add themselves again when they wish to take part..12:06
TheMusoamachu: I say yes.12:06
persiaI'd agree with that.12:06
amachufine, I will do that..12:06
amachuelkbuntu: silent today?12:06
amachuand lifeless: show some life ;-)12:07
elkbuntuamachu, nearly forgot12:08
amachuelkbuntu: hmm...12:08
persialifeless was nearly 23 hours early to the meeting, so may have become distracted.12:08
amachuelkbuntu: any comments on discussions so far?12:08
elkbuntunot quite caught up yet12:09
elkbuntusvaksha is online12:10
elkbuntujust not in here12:10
elkbuntuamachu ^^12:11
amachusvaksha online where?12:12
elkbuntuin #ubuntu-women12:13
amachugot her12:13
elkbuntuamachu, you might need to be blunt12:14
amachuelkbuntu: asking her!12:16
amachugood! I need to mail the list asking for opinions..12:17
amachufrom belutz, zakame and lifeless12:17
amachuif belutz and zakame can turn out to meetings regularly then we new members to the board can be re-considered..12:19
amachubut I will mail first..12:19
elkbuntui'd still like to see more on the board12:19
amachuOk!12:20
persiaI'm happy with the current board number if we don't have two meetings.  If we have two meetings, I want 9 comprised of 3 from the east, 3 from the west, and 3 from the middle.12:21
elkbuntubecause even if belutz and zakame can turn out more reguarly, we've still got a high chance of not having the quorum12:21
elkbuntuwhich i believe is the same as what persia believes12:22
persiaYes.12:22
elkbuntuhi svaksha_, good to see you active.12:23
amachupersia: that sounds good to me too...12:24
svaksha_elkbuntu: i was never inactive, silent yes12:24
elkbuntusvaksha_, the word 'see' is the key12:24
svaksha_amachu asked if i was applying so for the record, i am not applying for reactivating the expired membership12:25
persiasvaksha_, You're applying for new membership, or not applying at all?12:26
svaksha_persia: my membership expired in Aug, and i was thinking of reapplying (or whatever you call it) but i think i can volunteer  without  it too right?12:28
elkbuntuof course. else nobody would even *get* to membership ;)12:29
amachusvaksha_: you can.12:29
persiasvaksha_, Certainly.  You're welcome to help without membership.  As a member, you get an email address, the right to carry business cards, and other benefits.12:30
amachusvaksha_: as said,  we were discussing removing your entry and amireldor's from the agenda for they were present for quite some time! and if you wish you can add yourself later..12:30
svaksha_persia: :)12:31
svaksha_amachu: sure12:31
amachuand We would be glad to see you back, if you aren't taking it up today..12:31
svaksha_:)12:31
amachuare you or not?12:32
svaksha_amachu: 13:28 < svaksha_> persia: my membership expired in Aug, and i was thinking of reapplying (or whatever you call it) but i think i can volunteer  without  it  too right?12:32
svaksha_amachu: not today12:33
persiasvaksha_, Indeed.  So, we're going to remove you from the agenda, and you can add it back if you want to reapply at a later time.12:33
* svaksha_ nods12:33
persiaamachu, Do we have any other agenda items?12:33
=== leonel_ is now known as leonel
amachusvaksha_: Ok. Keep contributing :-)12:34
amachupersia: No12:34
amachuelkbuntu: TheMuso: any other thing which you would like to discuss?12:35
TheMusoNot from me.12:35
TheMusoI've actually gotta run I'm affraid.12:35
elkbuntucan i discuss sleep? :Þ12:35
Hobbseeelkbuntu: no.  Sleep is forbidden.12:36
elkbuntu:(12:36
TheMusoso till later folks, and thanks/12:36
persiadiscussing sleep is pointless.  Good night :)12:36
elkbuntucyas12:36
lifelesserg12:42
lifelesshai12:42
Hobbseelifeless: and you missed it again.  But you were closer this time!12:42
lifelessHobbsee: :(12:42
persialifeless, What's your opinion on splitting the meeting and adding more members?12:44
lifelesspersia: do you mean committee members?12:49
persiaYes.12:49
persia3/3/3 and 9:00/15:0012:49
lifelessI think its a bit hard to service france and argentina at the moment :P12:50
persiaYeah, well, there is that :)12:50
lifelessbut we rarely have so many applicants that we have to defer some12:51
lifelessso, other than being nice times for me, I don't see much motivation to change12:51
lifelessperhaps west asia is a little under-available time slot wise though12:51
persiaWell, being nice times for all the other people in places like India, East Australia, and New Zealand.12:52
lifelessyah12:52
persiaPersonally, I think picking nice times for us (within the prescription of "evening") is the best way to service the region.12:53
lifelessasia is so damn wide12:53
lifelessits a bad way to assess time zone availability IMNSHO.12:54
persiaI suppose.  I don't think of "Asia" as wide, but I don't think of Australia as part of "Asia".12:55
persiaThat makes it similar in width to London <-> Petersberg or Sao Paulo <-> Mountain View12:55
lifelessanyhow +1 on better times for the committee; if that makes it unavilable reasonably to folk in the nominated zone, then a separate committee to cover that region is needed IMO12:55
lifelesswhat tz is turkey?12:55
persia+3 or +4 I think.12:56
persia+312:56
persia(but DST may apply)12:56
persiaI'd claim that we're only responsible for +5 to +13 or so, but that's my personal opinon.12:57
persia(hrm, does NZ have a +13:15 at certain times of year, or does it only go up to +12:45?)12:58
=== nxvl_ is now known as nxvl
=== Rinchen` is now known as Rinchen
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Server Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 14 Oct 17:00: Kernel Team | 15 Oct 12:30: ubuntu-us-pa LoCo Team | 15 Oct 17:00: QA Team | 15 Oct 22:00: Platform Team | 16 Oct 12:00: Ubuntu Mobile Team
* kirkland waves o/15:59
* mathiaz waves o//15:59
zulhello16:00
nealmcbo/16:00
Koono--16:00
mathiazwelcome to the 33919023th edition of the Ubuntu Server Team meeting !16:01
nxvl\o\ /o/ \o\ /o/16:01
mathiazlet's get the show started16:01
mathiaz#startmeeting16:01
MootBotMeeting started at 10:01. The chair is mathiaz.16:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:01
persiaIt's not that.  It's about the 40th.  I may have lost count along the way, but not by that much.16:01
mathiazToday's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting16:02
mathiazLast week's minutes: https://wiki.ubuntu.com/MeetingLogs/Server/2008100716:03
mathiaz[TOPIC] Bacula SRU16:03
MootBotNew Topic:  Bacula SRU16:03
mathiazzul: ^?16:03
nxvlpersia: don't make us lose the joy16:03
mathiazzul: I think it has been published?16:03
zulmathiaz: uploaded not accepted afaik yet16:04
zulill bug pitti about it16:04
mathiazzul: ok.16:05
mathiaz[TOPIC] Review ServerGuide for Intrepid16:05
MootBotNew Topic:  Review ServerGuide for Intrepid16:05
mathiazsommer: anything new?16:05
mathiazok - noone is there - moving on16:07
mathiaz[TOPIC] KVM16:07
MootBotNew Topic:  KVM16:07
mathiazkirkland: what's the update on virtio bugs?16:07
kirklandmathiaz: i'm chasing down the virtio disk bug16:07
mathiazkirkland: there were two bugs: one related to network and one related to block device16:07
kirklandmathiaz: looks to be grub geometry16:07
mathiazkirkland: IIRC the network virtio bug is fixed16:08
kirklandmathiaz: the disk geometry for virtio disks is wrong in grub16:08
kirklandmathiaz: i'm checking if any of the other distros have solved that yet16:08
mathiazkirkland: ok - that may point to an issue with kvm on the host16:09
sommermathiaz: sorry, nothing new :)16:09
mathiazkirkland: or an issue with the kernel guest16:09
mathiazsommer: ok - I'll try to send an update to the support section16:09
kirklandmathiaz: i was concentrating on the guest16:09
mathiazkirkland: if this is an issue with the guest kernel we may be hit by the kernel freeze16:10
nealmcbthis one? https://bugs.launchpad.net/bugs/28149216:10
ubottuLaunchpad bug 281492 in grub "grub does not install properly to a virtio disk in kvm (/dev/vda)" [Undecided,Confirmed]16:10
mathiazkirkland: that is scheduled for this thursday16:10
mathiaznealmcb: yes16:10
kirklandmathiaz: i may need to employ some additional expertise on this16:11
mathiazkirkland: let's assume we are not able to fix grub in time16:11
mathiazkirkland: what are the options?16:11
mathiazkirkland: should we emit a warning? add some code to check if /boot is on a vd* device?16:12
kirklandmathiaz: tell people to install using a plain disk, and after installation is done, use a virtio disk16:12
mathiazkirkland: that means some more work to be done in the installer16:13
mathiazkirkland: or in grub-install?16:13
kirklandmathiaz: i'm trying to fix it in grub, as i said16:14
kirklandmathiaz: grub-install writes a borked bootloader to the disk16:14
kirklandmathiaz: if we get a good bootloader on the disk, it boots fine16:14
mathiazkirkland: right - I think it's the right to try to solve the issue16:15
kirklandmathiaz: but when the grub writes the bootloader to a /dev/vd* disk, it hoses the disk for booting16:15
kirklandmathiaz: that's in the installer, and in runtime16:15
mathiazkirkland: However I'm wondering about contigency plan if we don't fix it in time for intrepid16:15
mathiazkirkland: right - so grub-install would be the correct place to emit a warning if it tries to write on a vd* device16:16
nijabao/16:16
mathiazkirkland: you said you'd ask for help16:16
kirklandmathiaz: sure16:16
jdstrandkirkland: I'm somewhat confused-- if the backup plan is to install to /dev/hda, then change to firtio *after* install, won't the next invocation of grub (eg through a kernel update), mess up the mbr (or whatever is borked)?16:16
mathiazkirkland: what kind of expertise would you require?16:16
mathiazjdstrand: I don't think so16:17
mathiazjdstrand: the next invocation of grub will just update menu.lst16:17
kirklandmathiaz: i was going to ask cjwatson and aliguori, unless you can point me to someone else16:17
jdstrandmathiaz: good point16:17
mathiazjdstrand: however it would break the boot loader if grub itself was updated16:17
jdstrandmathiaz: or if the user played with grub-install manually16:18
mathiazkirkland: I don't think of anyone else - it seems to be kernel related somehow16:18
mathiazjdstrand: correct.16:19
mathiazkirkland: ok - it seems you've some ressource to get things moving16:20
mathiazkirkland: however keep in mind the kernel freeze on thursday16:20
kirklandmathiaz: I'm trying16:20
mathiazkirkland: on thursday we may need to see if we should try to keep fixing grub or go with a contigency plan since it will be hard to fix the kernel if necessary16:21
mathiazkirkland: other than this bug, is there anything else on kvm?16:22
kirklandmathiaz: have you verified the virtio networking fix?16:22
mathiazkirkland: yes - it's working from me in a hardy host16:22
mathiazkirkland: and on your side?16:23
kirklandmathiaz: i would like to mirror your test16:23
mathiazkirkland: on a intrepid host?16:23
kirklandmathiaz: i could not get it working on Friday, but i think my invocation or setup might have been wrong16:23
mathiazkirkland: ok - I'll outline my test after the meeting16:23
kirklandmathiaz: thanks16:23
=== txwikinger2 is now known as txwikinger
mathiaz[ACTION] mathiaz to explain his virtio network test to kirkland16:24
MootBotACTION received:  mathiaz to explain his virtio network test to kirkland16:24
mathiazkirkland: anything on the virt-manager front?16:24
kirklandmathiaz: no16:25
mathiazkirkland: ok - thanks for the update on the virtualization front16:25
kirklandmathiaz: sure16:25
mathiaz[TOPIC] JeOS16:25
MootBotNew Topic:  JeOS16:25
mathiaznijaba: so I've got all things sorted out16:26
nijabayes, that's great.  I guess we need some testing now..16:26
mathiaznijaba: the -virtual kernels are on the -server cd and the F4 option to install a minimal virtual machine has been added to the installer16:26
mathiaznijaba: I'm going to test today's -server isos as they're the first ones shipping with the -virtual kernels16:27
nijabaso we have a full intergartion of the jeos installer in the server cd, coolio16:27
mathiaznijaba: yop - however JeOS is not mentionned anywhere16:27
nijabayes, and the first time we have a 64bit kernel for -virtual16:27
mathiaznijaba: technically -virtual is just a -server kernel with a lot of modules not included16:28
nijabaJeOS has never been mentionned elswhere than in the docs, so that's ok16:28
mathiaznijaba: well - JeOS was part of the iso name16:28
mathiaznijaba: and part of the product name too16:28
nealmcbnijaba: ahh - 64bit kernel - nice16:29
nijabamathiaz: yes, but better safe than sorry, right ;)16:29
mathiaznijaba: I was wondering if it should be added to the F4 option some how16:29
nijabawell, do not worry too much about this, I'll put plenty of explanation on the web, wiki, etc...16:29
nijabamathiaz: I think the wording you proposed is more self explanatory16:30
mathiaznijaba: "Install a minimal virtual machine"16:30
nijabaJeOS seems to be confusing for some, they were often trying to install it on real hw16:30
nijabamathiaz: yes, that's really clear16:31
* nealmcb nods16:31
nijabamathiaz I have added a couple test cases on the server test for qa, how can I get the tests added to qa.u.c?16:31
mathiaznijaba: great - so we've got JeOS fully integrated in intrepid -server iso16:32
mathiaznijaba: they should be added by tomorrow16:32
mathiaznijaba: do we have access to ESX somewhere?16:32
nijabaI tried to ping heno but did not get a reply16:32
nijabamathiaz: IS has one up and running16:32
nijabayou can request access to it, I guess16:33
mathiaznijaba: hm - I don't know how16:33
mathiaznijaba: I'll ask heno or cr3 about it16:33
nijabaok, I'll email heno tonight16:33
mathiaznijaba: does JeOS support xen also?16:34
nijabanope16:34
mathiaznijaba: only ESX and kvm are supported?16:34
nijabathe -virtual kernel is not a paravirt kernel16:34
nijabamathiaz: officially, yes, but it could work elsewhere16:34
mathiaznijaba: well -virtual is the -server kernel16:34
zulnijaba: umm what?16:35
nijabajust need a full virtualization env, not paravirt16:35
mathiaznijaba: the -virtual kernel is not a different kernel build AFAIUI16:35
mathiaznijaba: is just a sub-selection of the -server build16:36
nijabamathiaz: right, and this is the issue, AFAIK, to run it in a paravirt env, no?16:36
nijabazul: do you agree that we need a -xen kernel to run ubuntu as a paravirtualizatin guest?16:37
mathiaznijaba: I'm not sure - I'm running intrepid -server kernel as kvm guests.16:37
nijabamathiaz: kvm == full virtualization, as vmware and virtualbox16:37
zulnijaba: no, you can run xen paravirt stuff with the server kernel16:37
mathiaznijaba: hm - ok16:37
nijabazul: ah, ok, so the paraviort extension made it in the plain kernel16:38
zulnijaba: yep16:38
nijabacoolio16:38
nijabaI did not know that16:38
mathiazzul: do you have access to a xen host ?16:38
mathiazzul: in order to test JeOS in xen?16:38
zulmathiaz: I can quickly16:39
mathiaznijaba: or we don't need to test on xen?16:39
zulxen is in universe though16:39
nijabathat would be nice if we could support it as well with -virtual16:39
zulI dont think it will work with virtual though it hasnt been tested though16:40
nijabazul: xen host is, but we decided to officially support xen as a guest option for ubuntu16:40
zulnijaba: interesting..16:40
nijabazul: dom0 ->  community, domU -> full maintenance16:40
mathiaznijaba: which version of xen host should we test on then?16:41
zulnijaba: ok then, I just want to add the -virutal kernel needs to add the xen modules then16:41
nijabazul: I am lost, do you need extension to the kernel or not to run in a xen env as a DomU?16:42
zulthe extensions to the kernel, the way that it works is that it takes a list of modules from the server kernel and repackages them, afaik right now the xen block devices and network devices are not packaged with the -virtual kernel16:43
zulIll send a patch to the kernel team mailing list today to get this fixed16:43
mathiazzul: ok - so keep in mind the kernel freeze on thursday16:43
nijabazul: ah, ok, we do not have the *modules*16:43
nijabazul: so let's think about it for Jaunty16:44
zulmathiaz: I can submit the patch after I go vote ;)16:44
nijabazul: too late, too risky, IMHO16:44
mathiazzul: nijaba: ok - so we don't try to support xen guest in intrepid?16:44
nijabazul: not with the virtual kernel16:45
mathiaznijaba: zul: ok - let's  move on16:45
mathiaznijaba: we can discuss that later16:45
nijabasure16:45
mathiaz[TOPIC] python-vm-builder16:45
MootBotNew Topic:  python-vm-builder16:45
mathiaznijaba: you - again?16:45
nijabamathiaz, actually to ask you to take a look at the current trunk16:46
nijabaask you to review it and upload it if you think it is fit16:46
mathiaznijaba: I thought kees uploaded it yesterday16:46
nijabaonce uploaded, i need for somemone to test it a bit on xen + libvirt16:46
nijabamathiaz: nope, that was a fix kirkland did for ubuntu-virt-mgmt16:47
mathiaznijaba: ah ok then16:47
mathiaz[ACTION] mathiaz to look at sponsoring python-vm-builder16:47
MootBotACTION received:  mathiaz to look at sponsoring python-vm-builder16:47
mathiaznijaba: what's the url?16:48
* ivoks hi16:48
zulnijaba: we should get poppy's fix in there as well16:48
nijabamathiaz: https://code.launchpad.net/~ubuntu-virt/vmbuilder/trunk16:48
mathiaznijaba: thnks.16:48
nijabanope, thank you16:48
mathiaznijaba: anything else on vm-builder?16:48
nijabanope, apart from testing required...16:49
nijabaI implemented some missing function to support xen, but do not have a xen host16:49
nijabazul validated that the fstab was ok, but nobody tested with libvirt16:50
mathiazok - so it seems we'd need access to ESX and xen environment to test both JeOS and vm-builder16:50
nijabawould be nice16:50
mathiazok - let's move on16:51
mathiaz[TOPIC] Open Discussion16:51
MootBotNew Topic:  Open Discussion16:51
mathiazivoks: so what's on your plate this week?16:51
ivoksmathiaz: i've finished testing of drbd and rhcs, all fine (except one minor bug in drbd)16:51
ivoksmathiaz: i plan testing bacula during this week16:52
mathiazivoks: bacula in intrepid?16:52
ivoksmathiaz: right16:52
ivoksmathiaz: and if there is anything anyone needs help with, i would be glad to help16:52
mathiazivoks: ebox testing is still on my TODO list16:53
ivoksi guess squashing bugs :D16:53
ivoksmathiaz: i could do that...16:53
zulivoks: if you need anything from me just poke me with a stick just not in the eye :)16:53
mathiazivoks: and preparing a FFe request for the motu release team16:53
ivokszul: i'll poke you with a drbd patch16:53
nijaba:D16:53
zulivoks: im expecting it :)16:53
ivoksmathiaz: FFE for motu?16:54
mathiazivoks: yes16:54
ivoksmathiaz: for ebox?16:54
mathiazivoks: it's a new upstream revision16:54
ivoksok16:54
ivoksput me in for ebox testing16:54
mathiazivoks: so a FFe needs to be written and motu-release subscribed16:54
ivoksor.. sign me in16:54
ivoksmathiaz: i know16:54
ivoksmathiaz: could i squeez ipmitool update into that? :)16:55
mathiazivoks: https://launchpad.net/~ebox/+archive <- that's what needs to be reviewd and sponsored16:55
mathiazivoks: of course :D16:55
ivoksok16:55
ivoksall right... lots of packages :)16:56
mathiazivoks: but only the modules that are already in hardy need to be looked at16:56
ivoksk16:56
mathiazivoks: that's about 2/3 of the listed packages IIRC16:56
zulmathiaz: are they still using courier-imap for their mail module?16:57
mathiazzul: I don't know16:57
pgraner\16:57
mathiazpgraner: is the kernel team meeting now?16:57
mathiazpgraner: or in one hour?16:57
ivoksin an hour, imho16:58
ivoksiirc16:58
pgranermathiaz: one hour,16:58
mathiazok16:58
mathiazanything else to add?16:58
pgranermathiaz: I typed in the wrong window :-(16:58
mathiazpgraner: I thought you were making signs... ;)16:58
ivoksoh...16:59
ivoksif anyone needs virtual machine for testing, let me know - i have one just for that16:59
pgranermathiaz: nope just stupidity on my part...16:59
* nijaba needs to part.... catching a flight... thanks all16:59
ivoksnijaba: have a good trip16:59
mathiaz[TOPIC] Agree on next meeting date and time.17:00
nijabathanks ivoks17:00
MootBotNew Topic:  Agree on next meeting date and time.17:00
mathiazsame time, same place, next week?17:00
sommersure17:00
ivoksok17:01
ivoks(i might be late again :/)17:01
mathiazexcellent then. See you all next week, same place same time17:01
mathiazthanks for attending and happy testing!17:02
mathiaz#endmeeting17:02
MootBotMeeting finished at 11:02.17:02
mathiazivoks: as long as you show up for the Open Discussion topic it's all good ;)17:02
sommerthanks mathiaz, later all17:02
ivoksmathiaz: :D17:03
ivoksmathiaz: sorry... you know, there's that nice girl and all... :)17:03
=== cjwatson_ is now known as cjwatson
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 14 Oct 17:00: Kernel Team | 15 Oct 12:30: ubuntu-us-pa LoCo Team | 15 Oct 17:00: QA Team | 15 Oct 22:00: Platform Team | 16 Oct 12:00: Ubuntu Mobile Team | 16 Oct 13:00: Desktop Team
=== Rafik_ is now known as Rafik
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Kernel Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 15 Oct 12:30: ubuntu-us-pa LoCo Team | 15 Oct 17:00: QA Team | 15 Oct 22:00: Platform Team | 16 Oct 12:00: Ubuntu Mobile Team | 16 Oct 13:00: Desktop Team
rtgBenC: vesafb looks good so far.17:59
pgranerHello Everyone its about time for the Kernel Team Meeting....18:00
pgranerLooks like we have everyone from the Canonical side so I guess we can get started18:00
pgraner#startmeeting18:00
MootBotMeeting started at 12:00. The chair is pgraner.18:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:00
pgraner[TOPIC] Welcome Jim18:01
pgranerI'd like to Welcome Jim to the kernel team as the newest Canonical hire!18:01
MootBotNew Topic:  Welcome Jim18:01
liebhi all18:01
smb_tpHi jim18:01
rtglieb: dood18:01
ckingHi Jim, welcome!18:01
amitkwelcome Jim18:01
ogasawarahi Jim :)18:01
pgranerlieb: Glad to have you onboard!18:02
pgraner[TOPIC] Intrepid Status18:02
MootBotNew Topic:  Intrepid Status18:02
pgranerLP #254923 HPA18:02
pgraner[LINK] http://lwn.net/Articles/301862/18:02
MootBotLINK received:  http://lwn.net/Articles/301862/18:02
ubottuLaunchpad bug 254923 in dmraid "dmraid doesnt work right with nforce570" [Undecided,Incomplete] https://launchpad.net/bugs/25492318:02
pgranerThis bug is showing up and has folks concerned.18:02
BenCpgraner: Already fixed18:02
pgranerI've asked cjwatson to join and talk about what we need to do?18:02
pgranerBenC: What was the fix?18:03
BenCpgraner: I uploaded a new module-init-tools that sets ignore_hpa=118:03
BenCwhich gives us the previous behavior18:03
pgranerBenC: How much grief are we going to get from upstream on that one?18:03
BenCcjwatson, Keybuk and I discussed this for some time18:03
BenCpgraner: no more than before, but I've agreed we need to discuss an upgrade path for ignore_hpa=0 for jaunty18:03
pgranerBenC: Make sure you add that to the UDS planning page pls.18:04
cjwatsonso I definitely think we need to worry about it for jaunty18:04
BenCBasically upgrading systems, or multi-boot systems with a kernel that has ignore_hpa=1 need to be taken care of18:04
cjwatsonbut a lot of the work needs to be in userspace18:04
pgraner[ACTION] BenC to add HPA handling to UDS planning page18:04
MootBotACTION received:  BenC to add HPA handling to UDS planning page18:04
cjwatsonwe can't fiddle about with the contents of disks in nearly the same way in the kernel18:04
BenCpgraner: ACK18:04
pgranerAnything else on this one?18:05
pgranerOk, moving on then....18:05
pgranerLP #261318 toshiba acpi18:05
pgranerAre we doing the right thing in shipping tlsup instead of toshiba_acpi? If so, what do we need to do in order to get it working properly?18:05
BenCpgraner: I will note that Keybuk disagrees with my solution being in modprobe.d instead of changing the source code in libata-core.c, but that's not relevant, IMO18:05
ubottuLaunchpad bug 261318 in xorg "Regression: new Toshiba Laptop Support (tlsup) driver breaks Toshiba hotkeys; input device does not support 'kbd' input handler" [Undecided,New] https://launchpad.net/bugs/26131818:05
rtgBenC: I got similar hassles from him this morning18:06
pgranerBenC: ack, noted just add to the planning page18:06
pgranerSo whats up with this one?18:06
BenCpgraner: first I've heard of it18:06
* BenC reads the bug quickly...18:06
pgranerBenC: Looks like users are seeing various levels of support with the new code18:07
pgranerBenC: I'll keep moving and give you the action to handle it18:08
pgraner[ACTION] BenC to look into  LP #261318 toshiba acpi18:08
ubottuLaunchpad bug 261318 in xorg "Regression: new Toshiba Laptop Support (tlsup) driver breaks Toshiba hotkeys; input device does not support 'kbd' input handler" [Undecided,New] https://launchpad.net/bugs/26131818:08
MootBotACTION received:  BenC to look into  LP #261318 toshiba acpi18:08
BenCpgraner: ACK18:08
pgranerLP #282700, 263782, 277795 Usplash Screen Corruuption18:08
ubottuLaunchpad bug 282700 in linux "[Intrepid] occasional hangs with screen corruption while booting" [Undecided,Confirmed] https://launchpad.net/bugs/28270018:08
ubottuLaunchpad bug 263782 in linux "intrepid hang with screen corruption during boot with 2.6.27-2-generic on x61" [High,Triaged] https://launchpad.net/bugs/26378218:08
ubottuBug 277795 on http://launchpad.net/bugs/277795 is private18:09
pgranerI understand we are reverting to vesafb instead uvisafb, has anyone had a chance to test it yet?18:09
pgranerrtg: ???18:09
BenCpgraner: fix committed, rtg testing18:09
rtgpgraner: its looking OK on 2 x86-64 laptops18:09
* Keybuk sniggers at the idea of visafb18:09
Keybukdrawing on money!18:09
BenCor immigration papers :)18:09
pgranerrtg: can you follow up in the bug with the testing results pls?18:10
rtgpgraner: can do18:10
pgraner[ACTION] rtg to follow up on  LP #282700, 263782, 277795 Usplash Screen Corruuption in the bug18:10
MootBotACTION received:  rtg to follow up on  LP #282700, 263782, 277795 Usplash Screen Corruuption in the bug18:10
ubottuLaunchpad bug 282700 in linux "[Intrepid] occasional hangs with screen corruption while booting" [Undecided,Confirmed] https://launchpad.net/bugs/28270018:10
pgranerLP #267875 rf_kill switch18:10
ubottuLaunchpad bug 263782 in linux "intrepid hang with screen corruption during boot with 2.6.27-2-generic on x61" [High,Triaged] https://launchpad.net/bugs/26378218:11
ubottuBug 277795 on http://launchpad.net/bugs/277795 is private18:11
ubottuBug 277795 on http://launchpad.net/bugs/277795 is private18:11
ubottuLaunchpad bug 267875 in linux "rf_kill interface not available for iwl3945, iwl4965 in 2.6.27" [Medium,Confirmed] https://launchpad.net/bugs/26787518:11
pgranerrtg: how we doing on this one?18:11
rtgpgraner: no progress.18:11
pgranerrtg: will it make kernel freeze?18:11
rtgslangasek thiks its an app space issue18:11
rtgs/thiks/thinks/18:11
pgranerrtg: is he working it?18:11
rtghe uploaded something, though I can't recall what. pm-utils?18:12
slangasekwell, that wasn't my /thought/, that's what I was told18:12
slangasekI uploaded the acpi-support part18:12
pgranerslangasek: you have doubts?18:12
rtgI'd go look at the bug but my POS fire-fox won't start.18:12
slangasek*if* /sys/class/rfkill/rfkill<n>/state is the right interface, then a hal fix is still needed18:12
slangasekpgraner: I always have doubts where anything under /sys is concerned :P18:13
* pgraner nods18:13
slangasekif there were some documentation that I could beat upstream developers with later if it were changed, I'd be much happier :-)18:13
pgranerslangasek: so what do we need to do to close this one out?18:13
rtgI don't think rf-kill has settled down to being a stable feature yet.18:13
slangasekwell, in the absence of that documentation, I was going to ask pitti to look into it18:14
slangasekor if he doesn't have time, tackle the hal patching myself18:14
pgranerslangasek: ok I'll give you that action then?18:14
slangaseksure18:14
rtgslangasek: so what is HAL gonna do? unload/reload driver modules?18:14
slangasekrtg: hal has to notify n-m when the rfkill has been switched18:14
slangasekit did this for the old iwl interface18:15
pgraner[ACTION] slangasek to look into rf_kill issue LP# 26787518:15
MootBotACTION received:  slangasek to look into rf_kill issue LP# 26787518:15
rtgsends a D-BUS message?18:15
slangasekyes18:15
pgranerLP #220917 iwl4965 firmware18:15
pgranerHave we sorted this one out yet?18:15
ubottuLaunchpad bug 220917 in linux-ubuntu-modules-2.6.24 "iwl4965 firmware missing in alternate installer" [Undecided,Confirmed] https://launchpad.net/bugs/22091718:15
pgranerBenC: ???18:15
rtgI think it should just unload the module 'cause most of the drivers aren't smart enough to power down.18:15
BenCpgraner: Fixed partially18:16
BenCpgraner: I need to split into a linux-firmware image to have a proper fix for upgrades18:16
BenCpgraner: which is in-progress18:16
BenCpgraner: will update bug18:16
pgranerBenC: ack18:16
pgraner[ACTION] BenC to update bug LP# 220917 with current status18:17
MootBotACTION received:  BenC to update bug LP# 220917 with current status18:17
pgranerMoving on.... Status of wireless backport18:17
pgranerrtg: What say you?18:17
rtgpgraner: initial implementation is done, now I'm waiting for upstream bug fixes.18:17
rtgIt doesn't play well with NM18:18
slangasekrtg: "just unload the module" - is that in reference to 267875?  I think that's pretty out-of-scope for this bug, which is about fixing the regression that n-m no longer knows the interface is down18:18
pgranerrtg: asking the obvious, will it make kernel freeze?18:18
rtgslangasek: when the modules gets unloaded, NM seems to notice.18:18
rtgpgraner: likely not. the empty package is in the archive18:18
pgranerrtg: thats gonna leave us with some pretty big bugs hanging18:19
rtgpgraner: besides, LBM is really subject to SRU policy.18:19
pgranerslangasek: you agree ^^^^^^^^^^^^^?18:19
slangasekrtg: that's fine, but I'm not writing code to figure out when to re-load the modules...18:20
rtgslangasek: it was just a suggestion :)18:20
slangasekpgraner: I think it's fair to say that SRUs are the primary reason for LBM's existence, sure18:20
slangasekand that anything that's fair to fix in LBM at all is fair to fix via SRU18:21
rtgslangasek: that doesn't make sense to me.18:21
pgranerrtg: when do think upstream will settle?18:21
slangasekrtg: sorry, why not?18:21
* BenC thinks rtg and slangasek are intertwining two conversations :)18:21
rtgLBM is a vehicle for porting upstream versions, which do not necessarily address SRU issues.18:22
slangasekwell, ok18:22
rtgpgraner: upstream wireless will not converge until someone imposes some discipline on the development process.18:22
slangaseklet's put it this way, then: I'm not likely to feel the need to meddle with anything you tell me should go into LBM, as long as it doesn't collide with the final freeze :)18:22
rtgslangasek: agreed18:23
pgranerrtg: I was looking for for you gut feel, than a "state of upstream devel process".... jeeez18:23
pgraners/for//18:23
pgraners/you/your/18:23
rtgpgraner: I don't have a gut feel, 'cause I think things are out of control.18:24
* pgraner needs to lay off the caffeine 18:24
pgranerrtg: then I'll keep this on the tracking list for now18:24
pgraner[ACTION] pgraner to follow up with rtg on state of wireless backport18:25
MootBotACTION received:  pgraner to follow up with rtg on state of wireless backport18:25
rtgthe out-of-box experience will mostly be ok if you're using a mainstream wireless adapter, and don't try to do anything funny.18:25
pgranerrtg: ack18:25
pgranerLP #262564 Wrong Copyright file in pkg18:25
ubottuLaunchpad bug 262564 in linux-restricted-modules "copyright file is incorrect" [High,Fix released] https://launchpad.net/bugs/26256418:25
pgranerBenC: you squash this one yet?18:25
BenCpgraner: fixed and uploaded18:25
BenC"Fix released"18:25
pgranerBenC: nice18:25
pgranerAnyone have any other pet bugs they would like to add here?18:26
pgranerGoing once.....18:26
pgranerGoing twice...18:26
pgranerGoing three times.....18:27
pgranerMoving on....18:27
pgraner[TOPIC] QA Bugs18:27
MootBotNew Topic:  QA Bugs18:27
pgraner[LINK] http://people.ubuntu.com/~ogasawara/intrepid-buglist.html18:27
MootBotLINK received:  http://people.ubuntu.com/~ogasawara/intrepid-buglist.html18:27
ogasawaraI've frozen the buglist for now18:27
ogasawaraall bugs which I feel need to be addressed I'll ping the team directly18:27
ogasawaraor bring them up here in the meeting18:27
pgranerogasawara: can you make sure all bugs are assigned to an individual rather than the kernel-team?18:28
ogasawarapgraner: sure18:28
pgraner[ACTION] ogasawara to make sure  all bugs are assigned to an individual18:28
MootBotACTION received:  ogasawara to make sure  all bugs are assigned to an individual18:28
pgranerogasawara: anything you want to say about individual bugs now? or can we move on?18:28
ogasawaraI think we're good, move on18:29
pgranerogasawara: ack18:29
pgraner[TOPIC] Open Discussion18:29
MootBotNew Topic:  Open Discussion18:29
pgranerWe got a question from mnuckfish on the Future of the linux-ports kernels18:29
pgranerCan we keep ports in sync with the official Ubuntu kernel in Jaunty? Like lpia does now?18:29
pgranerIs there anyone that cares about ia64 (currently FTBFS), sparc, hppa?18:29
munckfishHi folks18:29
munckfishI just wanted to get an idea what the intention was for the future of the ports kernels18:30
pgranerBenC: thoughts?18:30
BenCpgraner: In jaunty I hope to be able to devote some time to those ports18:30
munckfishthey use the 2.6.25 source right now18:30
smb_tpI looked at the ia64 FTBA and since it is only ABI stuff would care about that18:30
BenCpgraner: part of the reason for doing it this way in intrepid is that we knew we were going to be hard pressed to handle just x86 and x86-6418:30
munckfishBenC: how come things will be easier in Jaunty?18:31
BenCmunckfish: we have more people on the canonical kernel team, and more experience, so I might have free time :)18:31
amitkpgraner: It is kinda hard to support these without necessary hardware to test with - who has a hppa, ia64 machine?18:31
munckfishBenC: sounds good18:31
liebI do18:31
pgranerBenC: I wouldn't go that far18:31
BenCamitk: I do18:32
BenCI have one of everything18:32
liebalthough the power bill has been half since the 'tanic has been off...18:32
BenCpgraner: well, there's a better chance in jaunty than there was in intrepid18:32
pgranerBenC: possibly, however we have assumed other workloads as well.18:32
munckfishwell this is positive I really wasn't sure whether the general feeling towards ports was to let them die18:32
BenClieb: sounds good, maybe we can both give it a little love18:32
BenCmunckfish: as pgraner is pointing out, there's no guarantee though18:33
pgranerBenC: we can discuss at UDS when we are all together, I'm not opposed but we need to see what the cost is vs. everything else on the plate along with Jaunty features18:33
munckfishBenC: well that's ok, I'm happy to do any leg work I can - as I've done for Intrepid18:33
amitkso let me play devils advocated here: how many people use the ia64 and hppa ports?18:33
BenCamitk: probably 5-10 people18:33
BenCif that many18:34
amitk*advocate18:34
munckfishWhat about powerpc?18:34
BenCppc is pretty well used by the community, just not very well supported by it18:34
persiaia64 is interesting to keep because it helps resolve a number of 64-bit code issues (it does 64-bit differently than amd64)18:34
BenCI would say ppc is lead only by x86/x86-6418:34
BenCpersia: so does sparc18:35
persiaBenC, Hrm.  Good point.  I should look there instead.18:35
BenCbut then it isn't 64-bit userspace18:35
BenCexcept for a few bits18:35
pgranerBenC: IBM has been asking the server team for official support, we need to check with them to see if we can get IBM to help out for power18:35
* amitk agrees with ppc, considering that PS3 will be available for the next 5-7 years18:35
BenCpgraner: IBM bought me a power5 box, so I feel somewhat obligated to help out18:36
BenCeven if it is in my own time18:36
munckfishWow, so there's a chance it may become official again?18:36
pgraner[ACTION] pgraner to set up talk with server team on PPC support18:36
MootBotACTION received:  pgraner to set up talk with server team on PPC support18:36
BenCbut an officially supported power (or even better CBE) port would be nice18:36
munckfishvery nice18:37
pgranermunckfish: we need to see internally if its something thats worth while or not18:37
pgranermunckfish: are you did this answer your questons?18:37
pgraners/questons/questions/18:37
munckfishYes, second question was about staying in sync18:38
BenCmunckfish: up for discussion at UDS18:38
munckfishamitk's LPIA tree18:38
BenCmaybe we can look into putting some of the more stable ports back into the main kernel tree18:38
munckfishis that likely a good way to do things for ports/18:38
munckfish?18:38
munckfishBenC: ok understood18:38
BenCIMO, ia64 and hppa should be left external to our tree18:38
munckfishbtw folks Intrepid is running nicely on PS3 now bar one install bug - so thx for all the help, advice, and patience you've all offered in these last months18:39
BenCmunckfish: excellent...guess it's time to upgrade mine :)18:39
pgranerAny other open topics ?????18:39
rtgslangasek: is there anything holding up the transition to -updates of the Hardy kernel in -proposed ?18:39
slangasekI haven't been tracking it, sorry; pitti would be better able to answer18:40
smb_tpI have to get back on him on that18:40
slangasekI know we had one purported regression, which I believe I saw was ironed out18:40
rtgslangasek: ok. kees is hot to publish CVEs18:40
pgraner[ACTION] smb_tp to get with pitti on Hardy -updates18:41
MootBotACTION received:  smb_tp to get with pitti on Hardy -updates18:41
smb_tpIn case hardy doesn't get into updates, there might be a split release but getting hardy as well would be preferred18:41
smb_tppgraner, ack18:41
pgranerAnything else?18:41
pgranerOk moving on then...18:42
pgraner[TOPIC] Lightening Round18:42
MootBotNew Topic:  Lightening Round18:42
pgranerI'll go first...18:42
pgranerI'll be in London for release week.18:42
pgranerWorking with the other teams on late breaking kernel issues. So if I ping you or ask status, please be kind. thats about it.18:42
pgranertimg: ???18:43
rtgheads down, boss.18:43
pgranerrtg: just what I like to hear :-)18:43
pgranerrtg: I think we covered most of your stuff above...18:44
rtgyep - I've no other topics18:44
pgranerBenC: how about you?18:44
BenCpretty much the same...finishing up the stuff we discussed on the bug list, and starting on some of the new action items from this meeting18:44
pgranerBenC: by my box score you walked away with most of the actions... anything else in the queue ?18:44
pgranerBenC: any concerns for kernel freeze?18:45
BenCpgraner: none of the moment18:45
BenC/sof/at/18:45
pgranerBenC: ack18:45
pgraneramitk: what say you?18:45
amitkBeen busy keeping the lpia kernel up-to-date. Next week will be spent improving out-of-box support for some of the mobile devices we care about.18:46
amitksamsung q1 and jax10 being the main ones18:46
pgraneramitk: any concerns ?18:46
amitkno.. looking good.18:47
pgranersmb_tp: you're turn...18:47
smb_tpWork towards CVE release, fix ports ia64 FTBS, expect to get buried by Leann in bug reports...18:47
pgranersmb_tp: at least ogasawara is kind, she could really be mean about it18:48
rtgBenC: I think we should roll a kernel today and get the vesafb change propagated.18:48
smb_tppgraner, I don't dare to say something else ;) She's too close18:48
* ogasawara moves smb_tp to the top of her list :)18:48
pgranersmb_tp: I know!18:48
pgranercking: how goes it?18:49
ckingSupporting OEM team - plenty of BIOS and embedded controller issues to resolve18:49
pgranercking: your getting pretty good what that DSDT stuff?18:49
ckingwell - I'm very comfortable at seeing bugs in DSTD / AML code now :-)18:50
pgranercking: we can give you a bag of chicken bones and some magic dust if it would help?18:50
cking- yeah - I think voodoo + magic is required18:50
pgranerlieb: I would guess you don't have much other than new guy tasks... ?18:50
smb_tpEspecially if it comes to interpret 4 letter variables...18:51
liebyup18:51
BenCrtg: agreed18:51
liebthat too18:51
pgraner[ACTION] BenC to roll new kernel with vesafb changes18:51
MootBotACTION received:  BenC to roll new kernel with vesafb changes18:51
rtgBenC: lemme redo a wireless patch for ipw220, then I can upload it (unless you have something?)18:51
BenCrtg: have at it18:51
pgraner[ACTION] rtg to roll new kernel with vesafb changes and other "stuff"18:52
MootBotACTION received:  rtg to roll new kernel with vesafb changes and other "stuff"18:52
rtgon it...18:52
pgranerOk folks our time is about up, anything else?18:52
smb_tpno18:52
persiaI'm curious if anyone was able to review the -rt kernel, and if it needed work.18:53
pgranerAnyone?18:53
rtgpersia: it now builds ok, but I haven't run it.18:53
BenCI tried a couple weeks ago to port the -rt patchset to 2.6.27 and gave up after manually merging > 100 patches of some 4-50018:53
BenCis it based on 2.6.27?18:53
persiaBenC, abogani completed the porting.18:54
persiaYes.18:54
BenCmore power to him then18:54
rtgit actually build depends on 2.6.27.18:54
rtguses quilt to apply the patches18:54
persiaI've been told that's what upstream for -rt is doing.18:54
BenCthat's what I was working on when it was based on .2618:55
BenCeasy to work with18:55
rtgyeah - I thought it was an elegant way to do it.18:55
persiaabogani was wondering if there was a chance of a l-r-m-source package to do the same for l-r-m, or whether he'd have to copy the l-r-m source to do it as well.18:55
pgranerAnything else?18:55
BenCpersia: > #ubuntu-kernel18:56
pgranerOk, we are need to get outta here. I'll call it end of meeting.18:57
pgraner#endmeeting18:57
MootBotMeeting finished at 12:57.18:57
pgranerThanks everyone18:57
amitkbye all18:57
BenCbye18:57
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 15 Oct 12:30: ubuntu-us-pa LoCo Team | 15 Oct 17:00: QA Team | 15 Oct 22:00: Platform Team | 16 Oct 12:00: Ubuntu Mobile Team | 16 Oct 13:00: Desktop Team | 16 Oct 14:00: Ubuntu Java
ubunupam i right in this chat when i use to talk ubuntu caus i just installed it 2 ohours ago20:51
cjwatsonubunup: this channel is for meetings (as in organised meetings) among Ubuntu teams; #ubuntu, please20:53
ubunupo sry thx20:54
=== cjwatson_ is now known as cjwatson
=== Toadstoo1 is now known as Toadstool
=== txwikinger2 is now known as txwikinger

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!