Hi,

Here are the minutes of the meeting. They can also be found online with
the irc logs here: https://wiki.ubuntu.com/MeetingLogs/Server/20100622.        

==== Review ACTION points from previous meeting ====

* ttx to coordinate testing for Alpha 2?
* ttx  was to start Alpha 2 testing coordination during the meeting, so that
was not yet done - carry over.

* smoser to train someone on the release team on the cloud image release?
* an account on build machine is in the works for cjwatson
* "training" is mostly written up at
https://wiki.ubuntu.com/UEC/Images/Publishing

* jjohansen to review atop patchset for Alpha3 planning purposes?
* handed over to kamal
* kamal hoped to be done same day
* Daviey to update #588861, if needed against alpha1
* passed to ccheney and jjohansen, who are finding the first bad kernel
* jiboumans_ notes this blocks eucalyptus for alpha2
* ttx notes this is higher priority than atop patchset
* zul to move the sru tracker code to it's own project?
* https://edge.launchpad.net/server-sru-tracker

==== TOPIC] Maverick development (ttx) ====
ttx pointed to http://people.canonical.com/~pitti/workitems/maverick
/canonical-server-maverick-alpha-2.html, and pointed out specs should be
around 75%.  Regarding
milestones, he shared
https://bugs.launchpad.net/ubuntu/maverick/+bugs?field.milestone=27560 of
which a few apply to us:

* bug 588861 in linux (Ubuntu Maverick) ""pad block corrupted" error when
trying to register an image with 2.6.34 kernel" [High,Triaged]
https://launchpad.net/bugs/588861
* bug 595421 in eucalyptus (Ubuntu Maverick) "Eucalyptus doesn't start with
latest stable version of "Groovy"" [High,Triaged]
https://launchpad.net/bugs/595421
* bug 588410 in eucalyptus (Ubuntu Maverick) "dynamic block storage should use
virtio" [High,Triaged] https://launchpad.net/bugs/588410
* bug 594372 in tgt (Ubuntu Maverick) "MIR: tgt" [Medium,Confirmed]
https://launchpad.net/bugs/594372
* bug 574554 in tgt (Ubuntu Maverick) "tgtd needs init script or upstart job"
[Medium,Triaged] https://launchpad.net/bugs/574554
* zul says the upstart script needs to be reiveiwed by the foundations team
* bug 594509 in irqbalance (Ubuntu Maverick) "irqbalance main process ended,
respawning" [High,Confirmed] https://launchpad.net/bugs/594509

Finally, Alpha2 ISO testing is coming up, and ttx asked us to subscribe
to tests we'd like to run:

* http://iso.qa.ubuntu.com/qatracker/build/ubuntuserver/all

====  Weekly Updates & Questions for the QA Team (hggdh) ====

hggdh has installed the latest euca on their test rig, and a test was
running.

==== Weekly Updates & Questions for the Kernel Team (jjohansen) ====

jjohansen reports the EC2 kernel is being problematic, and if a kernel
isn't working by friday then alpha2 may have to use a Lucid based kernel.

==== Papercuts status (ttx) ====

Alpha2 iteration status can be seen at
https://launchpad.net/server-papercuts/+milestone/maverick-alpha-2.  If
you lack time to complete these bugs, you are asked to unassign yourself
so they can be reassigned.

For Alpha3, we are short on nominations.  ttx blogged about it in the
hopes of provoking more:

* http://fnords.wordpress.com/2010/06/21/did-we-fix-all-small-usability-
issues-in-ubuntu-server/

==== Weekly SRU review:
https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (zul)
====

Zul says that at UDS in Brussels, there was a session about involving more
people in nominating SRUs by using the mailing list, rather than the team
meeting.  He'd like to start that next week, by sending an email to
ubuntu-server m-l.

==== Weekly Updates & Questions for the Documentation Team (sommer) ====

Nothing to discuss

==== Open Discussion ====

ttx begs or badgers for papercut nominations.

==== Agree on next meeting date and time ====

Next meeting will be on Tuesday, June 29th at 15:00 UTC in #ubuntu-meeting.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Review ACTION points from last meeting

* ttx to coordinate testing for Alpha 2 – carry over * smoser to train someone on the release team on the cloud image release – carry over

Maverick development (jib)

Most specs should be around 50% completion right now. If you’re off that mark, you may want to review work items and see if any can be postponed or dropped, or ask for some support some are well ahead of that curve so we should have some slack in that area.

ttx confirmed we are going reasonably well, adding that the UEC specs are slightly late but we’ve been addressing that.

mathiaz has been experimenting with a new format/template for the status section of BP and stated that we should be seeing the output of this in the coming days.

ttx noted that: * UEC testing was rescoped to concentrate on fixing the current issues to get to a stable situation, and engage in training new people. * qa workflow was moved to A3 to give priority to uec-testing. * cloud-init was trimmed down to move prio-3 things as targets of opportunity * cloud-utils first work items were reassigned to clint * uec-ec2-kernel-updates work items were clarified

ttx feels that everyone now has a stable and clear view on what’s expected from everyone and that if someone thinks he cannot make it, please raise the red flag !

Feature Definition Freeze this week (ttx)

ttx drew attention to http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html and stated it gives a clear commonly shared view on what’s expected.

ttx reminded that Final Definition Freeze is this week, and warned the need to freeze the design on all specs that affect main packages and present those to the release team .

Weekly Updates & Questions for the QA Team (hggdh)

(ttx checks that the awesome Daviey is scribe)

hggdh shares that he has been testing the metadata issue fix, and preparing to get to Lexington next week for a sprint. He notes that the current fix seems to be insufficient, and is still producing issues.

hggdh confirms that the latest lucid SRU for eucalyptus has been moved from -proposed to -updates.

Weekly Updates & Questions for the Kernel Team (jjohansen)

jjohansen shares the pv-ops kernel for EC2 hasn’t been working out so we are shelving it for at least alpha2 and will update the Xen patches, and comments that zul seems to want to volunteer to work on it. zul clarifies that he wasn’t.

jjohansen confirms the kernel has some known performance regressions, that will probably be in alpha2, freeing time to work on some Amazon EC2 issues, and the performance issues are known upstream and a fix should be in a later RC release.

jjohansen states the kernel team has would like to know some more about Bug #588861. The awesome Daviey confirms that triaging has been somewhat blocked at the moment, as it seems there are other foundation related issues stopping us from even getting as far as that to reproduce the issue. Since, the latest kernel, we haven’t had an enviroment where we can reproduce that. Therefore, i’ve been unable to provide further information OR confirm if the issue is still ongoing in the latest kernel. jjohansen confirms we know its kernel related, and not an update to something else. jjohansen requests that he is kept posted and will recommend adding it to the top 50 bugs for the kernel team.

[ACTION] jjohansen to review atop patchset for Alpha3 planning purposes [ACTION] Daviey to update #588861, if needed against alpha1

Weekly Updates & Questions for the Documentation Team (sommer)

sommer confirms he added some items to the blueprint: https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-serverguide-updates , but feels he will need the most help with is the UEC section. kirkland points at Daviey, who tries to point it back to kirkland.

sommer mentions he’ll request help on the clustering section from RoAkSoAx / ivoks, and that he has some updates from ttx regarding tomcat.

Priase is given to sommer for his awesome work. Hugs also seem to be unanimous to Bryce for unclutterring the launchpad whiteboard.

Papercuts Alpha2 subcycle status (ttx)

ttx shares https://launchpad.net/server-papercuts/+milestone/maverick-alpha-2 , and notes that all are assigned and 65% are already fixed, and that there are a shortage of nominations for the next cycle.

New SRU Tracker (zul)

zul introduces that at maverick uds we agreed to change the way we do nominations for SRU. we are taking it to the ubuntu-server list to get more feedback, the email will be starting shortly after some introduction. States that we are also monitoring the status of the SRU nominated bugs (work in progress) at http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html

zul explains that it is a cron job that sucks in launchpad into a sql database and displays the results. Only running daily, the information might be out of date sometimes.

[ACTION] zul to move the sru tracker code to it’s own project

Open Discussion

(Nothing to discuss)

Agree on next meeting date and time

Next meeting will be on Tuesday, 22nd June at 1800 UTC in #ubuntu-meeting.

Greetings! If you’re going to be at Velocity 2010 next week, we hope you’ll join us at the Ubuntu Server Users and Developers BoF, Tuesday June 22 @ 8:30pm.

We’re going to cover a number of topics:

• UEC – We’ll do our best to build a fully functioning “private cloud” with just a couple of USB keys.
• Ubuntu Server 10.10 – The release is just around the corner in October, we’ll talk about some of the things planned.
• Feedback – The BoF will be attended by members of the Ubuntu Server development team, so bring your questions and feedback!

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Action points from the last meeting

• sommer to try to move server doc spec to Ubuntu specs: DONE
• ttx to document (or delegate documentation of ) package stack names: DONE

Alpha1 milestone

The Alpha1 milestone will be released Thursday. Please participate to Server ISO testing to get as much coverage as we can. Current known issues include an oversized CD, due to bug 587893. smoser will publish cloud images soon. Between now and Alpha1 we are in soft freeze and should not upload major changes that could impact negatively the milestone.

ACTION: all to run ISO testing coverage on alpha1

ACTION: smoser to ensure cloud images make it to the alpha1 iso tracker

Alpha2 subcycle status

The Canonical team tracks progress on their specs here. Please remember to keep your work items and Status: line updated in the blueprints, at least once per week before Monday EOB. See the WorkItemsHowto for more info. ttx will reset the trends line tomorrow to something more useful to track progress.

server-maverick-cloud-kernel-upgrades needs some attention since there is some work separation between smoser and jjohansen, and a more detailed work items plan is desired.

On the community side, Mail & cluster stack look in great shape. jib asked to seperate items out for before & after feature freeze to help track things. The doc spec is also in good shape.

ACTION: smoser to coordinate with jjohansen and ttx to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades

Weekly Updates & Questions for the QA Team

hggdh verified bug 565101, which should go to -updates as soon as possible. Additionally, he also did a quick test of bug 586134, and seems to work with 512 loop devices configured. There might be a delay in the Eucalyptus SRU due to a potential regression on bug 566793.

Weekly Updates & Questions for the Kernel Team

jjohansen is in vacation, so no progress yet on pv-ops. SpamapS mentioned that the proposed PTRACE changes would also affect negatively the ops population, and will chime in on the thread to make that concern known.

Weekly Updates & Questions for the Documentation Team

Lucid serverguide PDF is available on h.u.c. For next week’s meeting, sommer will present new sections for which the doc team will need input from the server team.

ACTION: sommer to present list of sections that need input from server team

Papercuts selection for Alpha2 subcycle

We currently have 14 bugs nominated for a desired total of 16 targets, so choosing between them should be easy. Last-minute nominations can still occur since ttx will proceed with formal selection tomorrow morning. You can also start assigning yourself to those you’re interested in.

Weekly SRU review

SRU nominations were reviewed. The tracker for the new SRU process is under work, with an early view accessible here.

Open Discussion

server-maverick-openldap-dit was reviewed and approved. EtienneG brought up the question of which iSCSI target is being chosen for main/UEC: tgt is the answer, and ccheney will work on the MIR, and zul on the upstartification.

Agree on next meeting date and time

Next meeting will be on Tuesday, June 8th at 18:00 UTC in #ubuntu-meeting.

Apologies for this delayed post, I had some confusion in setting up my access to the blog. -clint

Here are the minutes of the meeting. They can also be found online with
the irc logs here:

https://wiki.ubuntu.com/MeetingLogs/Server/20100525

==== Review ACTION points from previous meeting (ttx) ====

* ttx to confirm spec submission deadlines with Jos: DONE
* ttx to walk SpamapS through the spec proces: DONE

==== Maverick Alpha2 subcycle and specs ====

* specs need to be set to review by EOB May 26 (Extends deadline by 1
day)
* design mandatory, implementation (work items) should have a full
rough plan, user stories can be filled in later.

==== Weekly Updates & Questions for the QA Team (hggdh) ====

* zul needs help getting back ability to nominate bugs for lucid
* QA workflow spec to remain as server team's responsibility
(jiboumans)

==== Weekly Updates & Questions for the Kernel Team (jjohansen) ====

* status update on ec2/uec kernel upgrades
* built many, none have booted, will check vmlinuz stripping/xen
settings (jjohansen)
* CEPH will be enabled in next upload to maverick

==== Weekly status for Server documentation (sommer) ====

* Server guide for lucid had a broken PDF, fix committed and awaiting
upload to "h.u.c" (sommer)
* documentation specs to be moved under Ubuntu launchpad project to
allow usage of work items tracker (sommer)
* [ACTION] sommer to try to move server doc spec to Ubuntu specs

==== Maverick Papercuts: Start of the alpha-2 round (ttx) ====

* All should blog/announce papercuts (ttx)
* Minor features / wishlist are included because not LTS cycle (ttx)
* nominate by marking bugs as affecting 'server-papercuts' project
* nominations will be reviewed next week, sub cycle begins Jun 2nd,
ends week before Alpha2 release

==== Weekly SRU review:
https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review
(mathiaz) ====

* Two bugs nominated, 567179 & 583542, to be declined pending more
information
* New SRU review process spec revealed with shiny pictures
[[https://wiki.ubuntu.com/ServerMaverickSruProcess]]

==== Open Discussion ====

* EC2 AMI-API tools in multiverse are out of date whenever amazon adds
services/regions/etc.
* PPA vs. backports discussion results in PPA *and* backports upload
as way to get latest tools to users.

==== Announce next meeting date and time ====

* Next meeting will be Tue, Jun 1 18:00 UTC 2010

With the Maverick cycle kicking off and UDS-M just behind us, it’s time to take a look at what’s in store for the next release of Ubuntu Server. In broad strokes, these will be the likely topics:

• Better integration with Upstart
• Further improvements to Mail & Cluster stack
• Adopt Ceph & GlusterFS, MongoDB, Drizzle & Cassandra
• Ease deployments & loadbalancing in the cloud
• For UEC: enabling kernel upgrades, virtio support, new admin UI, easier developer deployment, cloud on a stick and lots more testing
• Adopt & improve the following Java stacks: Tomcat, Ehcache, Hibernate, Hadoop and Pig

Like last iteration, we’ll be reviewing and accepting blueprints proposed for Maverick on a per milestone basis. This week, we’ll review the work for Alpha2 and you’ll be able to track the progress on the work item tracker.

If you’d like to contribute to the Maverick release, please join us at our weekly IRC meetings on Tuesdays between 1800 and 1900 UTC on #ubuntu-meeting on irc.freenode.net. We could especially use your help in the papercuts project and bug triaging!

On behalf of the Ubuntu Server Team,

-Jos

Review ACTION points from previous meeting (ttx)

• No action points

Maverick Blueprints and Specs

• Please have a look at specs where you are set as drafter, and set them to “Drafting” if you started drafting. Some reassignment/balancing may occur
• Feature Definition Freeze is June 17th. specs should be considered due for approval by May 27, which means they must be submitted for review by May 25th.

• For Server Team work, the Implementation section of the SpecTemplate is largely replaced by the Work Item tracker.

• this is the merging period, so please have a look at https://wiki.ubuntu.com/UbuntuDevelopment/Merging

• [ACTION] ttx to confirm spec submission deadlines with Jos

• [ACTION] ttx to walk SpamapS through the spec process

Weekly Updates & Questions for the QA Team (hggdh)

• hggdh expects to handle the UEC Testing spec with some input from mathiaz and smoser

Weekly Updates & Questions for the Kernel Team (jjohansen)

• mathiaz asked about a bug on his x201 laptop. Very server-ish, indeed.

Weekly SRU review

• https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review

• There was a session at UDS discussing improvements to the SRU process. This will result in a blueprint and work items.

Open Discussion

• The Canonical Server Team has grown, adding
  • SpamapS (Clint Byrum): Web/Ops stack
  • Davey (Dave Walker): UEC
  • ccheney (Chris Cheney): Desktop Team on loan to server team for some UEC related work.

Agree on next meeting date and time

The next meeting will be: Tue May 25 18:00 UTC 2010

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Weekly SRU review

Lucid has been added to the list of nominations to be reviewed while intrepid was removed (being EOL). The list of bugs fixed in the last 9 days has also been fixed and can again be used in the SRU weekly review.

A session about SRU improvement has been scheduled at the next UDS.

UDS Maverick

There is a tentative schedule available on the summit website.

Agree on next meeting date and time

Due to UDS the meeting has been canceled next week.

Next meeting will be on Tuesday, May 19th at 18:00 UTC in #ubuntu-meeting.

Ubuntu Server Team weekly minutes have been published at:

https://wiki.ubuntu.com/MeetingLogs/Server/20100428

Summary:

On track for Lucid release.  Get Blueprints filed for Maverick UDS as soon as possible!

Actions:

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Review ACTION points from previous meeting

• mathiaz to fix a broken script with bug reporting link above (not done)
• ttx to follow up with ivoks/RoaKSoax on cluster stack state (done, but needs refresh)
• mathiaz to propose removal of dovecot-postfix on MLs (not done)

[ACTION] mathiaz to fix the “server fixed bugs” broken script

[ACTION] ttx to follow up with ivoks/RoaKSoax on cluster stack state

[ACTION] mathiaz to propose removal of dovecot-postfix on MLs

Lucid release status

FinalFreeze will hit us tomorrow, and then all uploads will need ReleaseTeam approval, so team members are advised to get every fix they can in by the end of the day. Here is the release-critical bugs status:

• 556343 (zul): mvo will run the test now again and once its finished, upload the syslog file

• 532733 (kirkland): forwarded upstream, haven’t made much progress on that one, not able to reproduce it easily (outside of the odd apt-get circumstance)

• 513273 (kirkland): uploaded fix was rejected, needs bug commenters to help do some testing on it against bochs

• 533029 (zul): pending on FFe

• 562261: sync approved, needs ArchiveAdmin action

Slow progress in the remaining work items in the specs. Eucalyptus merging and packaging should be complete today today, the others are assumed to still be on track.

Once those higher-priority items are taken care of, you can work on Lucid targets of opportunity. You can find a list of those on the release status page, or go directly to https://bugs.launchpad.net/ubuntu/lucid/+bugs for the complete list. The server team side of the release is appearing to be mostly in good shape, though more testing would not hurt, team members are encouraged to blog/call for that.

Weekly Updates & Questions for the QA Team

hggdh is still working on the issue preventing the UEC test rig to successfully run Topology 2 tests. mathiaz and kirkland will help him debug that. He is slowed down by a kernel issue preventing his KVM to work correctly (needs to try out the latest kernel). The ISO testcases are good since beta2 and should not change until release. hggdh also started to work on the EC2 tests, jump-starting from smoser’s work.

Weekly Updates & Questions for the Kernel Team

jjohansen reported that bug 530361 (support for DELL H200/H700/H800 SAS cards) was fixed in time for KernelFreeze. The remaining big issue is bug 546743, servers with ATI ES1000 cards don’t get anything on console. jjohansen is still investigating options but we are now past KernelFreeze, which reduces our choices. This can be rolled into a new kernel, workarounded in a kernel cmdline set at install-time, or mentioned in the release notes and shipped in a kernel SRU.

Weekly SRU review

zul conducted a quick review that didn’t end up with anything new accepted for SRU. The recently-fixed server bugs query is still broken and cannot be used. Note that zul plans to discuss SRU handling at next UDS.

Open discussion

zul mentioned he has been working on getting mysql-5.0 out of universe, and it should be ready to be removed from universe today. Some team members reported starting to have classic pre-release sleep trouble.

Announce next meeting date and time

Next meeting will be on Wednesday, April 21st at 14:00 UTC in #ubuntu-meeting.

Beta2 milestone release (ttx)

• Beta2 will be released tomorrow (Thursday 2010-04-08). Server is looking good.

• Some Beta2 tasks still remain .

• 531494 has been fixed, and we are going to give ramdisk-free UEC and EC2 images one last chance. The 20100107.1 build will not have ramdisks and testing should be done both on EC2 and UEC for that. If we run into issues that look related to lack of ramdisk we will revert to using ramdisks for beta-2 and release.

RC/Final preparation (ttx)

• Release occurs at the end of the month. Priority until then is:
  • Release-critical bugs
  • Continued specs (eucalyptus-merging, uec-testing, puppet-ec2)
  • Lucid targets of opportunity

• List of all critical bugs are available at https://wiki.ubuntu.com/ServerTeam/ReleaseStatus

• The FinalFreeze is next week. Please pay special attention during triaging to catch release-critical issues. Feel free to subscribe ttx to those bugs.

• openldap is in need of some work, regarding update from hardy, per mathiaz “sticky point is the conversion from slapd.conf cn=config”

Weekly Updates & Questions for the QA Team (hggdh)

• Test cases in iso tracker have been recently updated.

Weekly Updates & Questions for the Kernel Team (jjohansen)

• 532553 is targetted for post beta2

• jjohansen will look into some kvm oopses also (556919 , 444365 , 458201)

• FinalFreeze for kernel is next week

Weekly SRU review: (mathiaz)

• https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review

• http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html

• [ACTION] Mathiaz to fix a broken script with bug reporting link above.

Call for Maverick blueprints (ttx)

• Maverick UDS is in a bit less than a month.
• To register a blueprint, name it server-maverick-* and set Jos Boumans as the approval.

Open Discussion

• RoAkSoAx pointed out “Cluster Packages are getting into Debian. Those include ivoks changes… they should be hitting Debian unstable soon, though I’m not sure if they are going to do so in time for us to sync/merge”. In lucid, cluster-agents, cluster-glue, heartbeat are still in universe . RoaAkSoAx will be looking more into this.

• [ACTION] ttx to follow up with ivoks/RoaKSoax on cluster stack state

• Per zul, mysql-server-5.0 removal is ready to go in after freeze is lifted.

• [ACTION] mathiaz to propose removal of dovecot-postfix on MLs

• mathaiz proposal to drop the ubuntu-serverguide from the archive, was generally met with unhappyness. sommer is planning a SRU update to address the ldap changes, which is the most out of date.

• Please sponsor packages : http://qa.ubuntu.com/reports/sponsoring/

Agree on next meeting date and time

Next meeting will be on Wednesday, April 14th at 14:00 UTC in #ubuntu-meeting.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Beta2 status

ttx reminded everyone that Beta2 Freeze was around the corner.

There are a few beta2-targeted bugs:

• Bug 292971 (mathiaz). It will probably require a BetaFreezeException.

• Bug 493593 (zul)

• Bug 408402 (zul)

• Bug 532733 (kirkland)

Most of the Work Items targeted for beta2 are not impacted by the BetaFreeze, except for:

• puppet/uec-ec2: integrate upstream patches for testsuite (mathiaz). Patches are available from upstream. However mathiaz may not have time to integrate them in time for BetaFreeze.

• id-mgt-ref-env: package latest sssd (mathiaz): He may not have the time to package this bug-fix-only update before BetaFreeze.

ttx mentioned the addition of a work item covering libvirt compatibility testing. kirkland said he planned to work on libvirt with jdstrand a full day.

ScottK added that clamav reached RC2 for version 0.96. Testing is welcome and packages are available from the ubuntu-clamav PPA.

Weekly Updates & Questions for the QA Team

hggdh reported he had run the stress and scalability testing on the UEC testing network for Beta1. There are 2 topologies left for testing. Multi-network testing still requires a lot of manual steps. kirkland mentioned that he had the hardware to test multi-network but testing that topology was time consuming.

ttx asked about adding UEC topologies test cases to the QA tracker. hggdh replied he would add them today.

hggdh wondered whether the daily -server isos should be tested on a regular basis. ttx replied that pre/post milestones were the most important images to test. If the tests are fully automated and don’t require a lot of hand-holding running them on the dailies could be useful.

Weekly Updates & Questions for the Kernel Team (jjohansen)

jjohansen reported that two bugs related to EC2 had been fixed in the latest kernel upload. Soft lockups are caused by a variety of things but they shouldn’t happen near as often.

Server Papercuts status for beta2

ttx reported that 8 bugs were fixed while 2 were left open. ttx would like to discuss how successful the project was and if it should be done again, even on non-LTS cycles. He also confirmed that the project was now closed for this cycle and new nominations wouldn’t be accepted anymore.

Bug zapping status (kirkland)

kirkland reported a successful UEC bug zap from last week. mathiaz mentioned he was running a MysQL Bug zap this week.

Community participation has been rather low for both the bug zapping and server paper cut projects. A session at the next UDS should be dedicated to improve Community participation.

Information about server survey (nijaba)

nijaba reported that the result of the Server survey were available to anyone in the community that might need it.

UDS-M topics

ScottK brought up the idea of having a session at UDS on what we wanted the next LTS to look like to have an idea of longer term stuff.

Agree on next meeting date and time

Next meeting will be on Wednesday, April 7th at 14:00 UTC in #ubuntu-meeting.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Review ACTION points from previous meeting

• kirkland to publish tentative bugzapping roadmap: Done, will be updated.

Beta1 status review

ttx informed everyone that we are at the beginning of the beta1 subcycle… but not very far from the end of it. Thursday next week is Beta1Freeze, a hard freeze before the Beta1 release, so most uploads should be made before that date. For reference, the beta1-targeted blueprints are tracked at http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html

smoser reported that the EBS root support was on track, with all tools moved over to using the new api tools.

Weekly Updates & Questions for the QA Team (hggdh)

hggdh reported that the build in MySQL regression PPA was still failing, and zul confirmed that he was working on it. hggdh didn’t have the time to look into the UEC test rig yet, but will do this week (the idea being that he should be able to run the post-A3, pre-beta1 UEC tests). hggdh also reported good progress on mastering the automated ISO testing framework soren was previously working on.

Weekly Updates & Questions for the Kernel Team (jjohansen)

jjohansen reported bug 527208 outstanding, blocking boot on c1.xlarge type instances in EC2: it should hopefully be fixed this week. mathiaz brought his request for creating vlan modules for d-i (bug 530459) to the kernel team attention.

Server Papercuts (ttx)

14 bugs were targeted for the first papercuts fixing campaign, which will end on Beta1Freeze, Thursday next week. Everyone is welcome to assign themselves some of those bugs, which are usually easy to fix. ScottK offered support in helping fixing the amavisd-new bugs.

There is still some room in the second campaign (beta2), so people should keep on nominating their favorite annoyance as a bug also affecting the “Server papercuts” project. In the nomination list, bug 211915 was accepted and assigned to sommer for the beta2 campaign.

Bugzapping (kirkland)

kirkland reported good progress on the current kvm bugzapping effort, and now Lucid’s kvm package appears to be in good shape. He might not have time to get around to libvirt, where there’s a lot more open bugs, due to other pressing work. A eucalyptus bugzapping week is also already planned. Other bugzapping efforts will have to be organized by other people.

In order to encourage that, the bugzapping format will be slightly simplified to lower the barrier of entry: you should target as a group a single package and spend a minimum of 2 days on it (Triaging / Bugfixing), ideally 3 days. People interested in chairing such an effort should edit the ServerLucidBugZapping wikipage.

kirkland also mentioned that bugzapping was a great way for community members in companies that care about the shape of a particular package to get involved: you should consider asking your boss/work for 2-3 days to focus on Ubuntu XYZ package where XYZ is the key package that your company/business/IT-staff needs working better in Ubuntu.

On a related front, ScottK reported that someone should figure out why suddenly tons of people who have no idea how to configure postfix are installing it, which he traced back to some Google Chrome packages.

Update on Daily Bug triager: New,Undecided bugs (mathiaz)

mathiaz updated the daily query to be live (“New Bugs” link at https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#triager). He wanted to remind everyone to triage all bugs on the list on their Triage day: starting at the top and processing one bug after the other at least until you reach one opened on today.

Open Discussion

Daviey asked if, as part of the ArchiveReorg that is being phased in, people should think about requesting ubuntu-server upload privileges. The team details need to be sorted out first, and we didn’t feel the urgency of it since most interested people are already core-dev. However in order to lower the barrier of entry, it makes sense to set the team in place in all cases.

jmdault mentioned upcoming updates to Asterisk, due to two recent security fixes.

ACTION: mathiaz to sync up with cjwatson re: ubuntu-server upload team

Announce next meeting date and time

Next meeting will be on Wednesday, March 10th at 14:00 UTC in #ubuntu-meeting.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Specifications review for Feature Freeze

ttx conducted a review of some specifications in preparation for Feature Freeze:

• server-lucid-aws-client-libraries: smoser reported all the relevant projects had been packaged and were waiting from review.

ACTION: ttx to follow up on server-lucid-cluster-stack and server-lucid-asterisk-integration via email

• server-lucid-uec-testing: kirkland mentioned there was one topology left for testing. Everything was on track.
• server-lucid-seeds: mathiaz commented that the next step was to make sure all packages had been demoted to universe. It was also decided to move all the rhcs related items to the cluster-stack blueprint.
• server-lucid-cluster-stack: ivoks reported that all the packages were available in the ubuntu-ha PPA. The next step was to get all the MIR written before FF.
• server-lucid-asterisk-integration: jdmault mentioned that all packages were available in his PPA. He was looking for help to get them uploaded to lucid before FF. Daviey offered some help in sponsoring relevant packages.

Boto 1.9 vs Boto 1.8 for euca2ools

ttx outlined the issue with euca2ools and boto. The current version of boto in the lucid archive was 1.9 whereas euca2ools had been thoroughly tested with version 1.8. He presented 3 options:

1. Fix bugs a they come up, as its not black magic
2. Revert to 1.8, and be stuck with an old lib
3. Ship both version

After some discussion it was decided to focus on the first option.

Weekly Updates & Questions for the Kernel Team

smoser reported that both -virtual and -ec2 kernels were booting without ramdisks.

Server Papercuts

ttx conducted the review of the bugs nominated for the server-papercuts project. This was followed by a discussion about how many bugs should be worked on given the time frame. The goal was to fix 6 to 7 bugs a week given the number of bugs currently opened.

Agree on next meeting date and time

Next meeting will be on Wednesday, February 24th at 14:00 UTC in #ubuntu-meeting.

While preparing the next LTS release the Ubuntu Server team looked for packages that should be demoted to universe in order to ease the five year maintenance window that come with LTS releases. Discussion started during UDS and several requests for feedback have been sent  since then. Amongst the list of packages to be demoted to universe, the venerable nis package can be found.

The Network Information Service has been around for a long time – however its protocols are old and insecure by design for the current network environments. Better alternatives such as LDAP, Kerberos and DNS are available. That being said the package is still maintained in Debian and will be available from the universe repository in the next LTS release.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Review ACTION points from previous meeting (jib)

• ACTION: ttx to announce papercuts nominations
  • ttx: done
• ACTION: zul to do another call to action for the apport hooks involvement
  • zul: will do today
• ACTION: zul to raise php5.3 update on -server and -devel mailinglist, outline which apps are currently not working with 5.3
  • zul: done

Alpha3 progress review (ttx)

• Make sure status is updated on each of your blueprint whiteboards EOD on Tuesdays !

• Prio 1 specs < 70% completed: uec-testing, mysql-5.0, seeds

  • uec-testing (mathiaz)
    • kirkland: testing iso’s today
    • mathiaz: good shape
  • mysql-5.0 (zul)
    • zul: upload today
  • [ACTION] zul to forward issues about ctbd to jelmer to see if those can be lifted before FF
  • [ACTION] zul to do another call to action for the apport hooks involvement
  • Discussion on RHCS, whether to keep in main, move to universe; mailing list thread should reach a conclusion soon
  • daily-vcs (zul)
    • zul: been working on higher priority specs
  • puppet-etckeeper-integration (mathiaz, soren)
    • soren, mathiaz: should merge from debian unstable, not in danger

• Prio 2 specs < 50% completed: daily-vcs, puppet-etckeeper-integration, puppet-uec-ec2-integration

server-lucid-papercuts (ttx)

server-lucid-papercuts

• https://bugs.launchpad.net/server-papercuts/+bugs

• Each bug was reviewed, voted on with -1/0/+1
• ttx updated all bugs accordingly
• for details on each bug, please see the logs below

server-lucid-apport-hooks update (zul)

server-lucid-apport-hooks

• zul: all prior 1 are done except for openssh its pending a review with cjwatson

• ttx: As a general reminder, apport hooks are easy, and a great way of contributing your first patches/branches to Ubuntu

Weekly Updates & Questions for the QA Team (soren)

• smoser: new guy starts: 15th (which is a US holiday) so 16th
• soren: handed over automatic ISO testing stuff to the QA team. It’ll be running in the DC soon.

Weekly Updates & Questions for the Kernel Team (jjohansen)

• jjohansen: new EC2 kernel is checked in, has the latest updates, and updated configs

Weekly SRU review (mathiaz)

• [ACTION] kirkland to propose a karmic fix for bug 503180 in PPA
  • kirkland: to upload karmic eucalyptus iptables fix for SRU, PPA first, then -proposed
    • done

• Launchpad bug 364581 in mod-auth-mysql “Crash when logging in” [Low,Fix released] https://launchpad.net/bugs/364581

  • mathiaz: accepting

Open Discussion

• kirkland: tftpd-hpa in lucid sucks
  • stgraber: I’m still not sure about what to do here but I’m very tempted to restore the old behavior
    • done
• ttx: Ubuntu bug 508382 in bacula “bconsole does not connect to bacula-director” [Medium,Confirmed]

Agree on next meeting date and time

• ttx: That will be again same place same time, for at least one more week

Last week the Lucid Alpha3 development phase started. So in following our Alpha2 announcement below is what’s on the horizon for Alpha3. Some of these are new blueprints for Alpha3 some are continued work from Alpha2.

Alpha3 Projects

Since the upcoming release is an LTS, a lot of this cycles work is centered around stability. Currently, we’re broadly targeting the following 3 areas:

Software integration

• Eucalyptus 1.6.2
• Moving from MySQL 5.0 to 5.1
• Provide libraries in PHP/Python/Perl for AWS services

Improving our UEC & EC2 experience

• Integrating Puppet & Etckeeper
• Provide boothooks & user based configuration

QA & testing

• UEC tests
• Automated server tests
• Bug squashing
• Apport hooks
• Daily builds for server packages
• The Server Papercuts project

There are also a few community driven specs which are targeted for the Lucid release:

• Asterisk Integration
• Ubuntu Cluster Stack
• Ubuntu Server Containers (LXC, OpenVZ)
• Integration of Amavisd-new, Spamassassin, and Clamav

The full list of blueprints related to these targets and our progress can be found on the server team wiki or on our work item tracker.

Feedback & Involvement

If you have any suggestions for AWS libraries in PHP/Perl/Python or are interested in packaging/contributing a library in another language, please let us know in the RFC thread

To make the most of our Server Papercuts project, please participate in the email discussion and nominate papercuts and/or volunteer to fix them!

To help us track down bugs and crashes better, we’re adding apport hooks to several key pieces of software. If you’d like to implement any of those hooks or contribute your own, please let us know in
the blueprint.

The Ubuntu Cluster Stack spec has issued a call for testing and would love to hear about your experiences.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Review ACTION points from previous meeting

• smoser to look at getting Karmic images refreshed: bug verifiedfixed, image refresh coming up before end of week

Action: smoser to publish karmic cloud image refresh

• mathiaz to send out AWS Client lib RFC: done
• ttx to coordinate alpha ISO testing: done
• ttx for papercuts: discuss acceptance criteria, project publicity plan: mail sent, more in this meeting

• mathiaz to publish papercuts & apport efforts in our blog/community channels: done

• mathiaz to publish request for iso testing in our regular blog/community channels: done

Spec quickreview

All alpha-3 targeted specs are on track.

To avoid useless noise, blueprint assignees are asked to refresh the status of their specs by using the “Status:” section of the blueprint whiteboard. It will then automagically show up in the report (http://people.canonical.com/~pitti/workitems/canonical-server-lucid-alpha-3.html).

Action: Everyone: update status for your specs before the meeting starts

Alpha3 subcycle planning

The final planning is still being discussed, and should be officialized this week. No change is expected in the Prio 1 specs (“High” priority), some priority changes might affect Prio2/3 specs, and some late specs might be introduced as Prio2/3 specs.

server-lucid-papercuts

We discussed the papercuts acceptance criteria, as described in a recent ubuntu-server ML post. This looks fine and was approved. Final criteria should make clear that any server-related package (in main, universe or multiverse) is relevant, and that the fix should not introduce a new feature (and therefore be OK to fix after FeatureFreeze). The criteria might be further refined when we start hitting difficult nominations.

About the project publicity plan, mathiaz already posted a blog entry about the project on the ubuntuserver blog. This should be complemented by an ubuntu-devel ML post, personal blog posts (ttx, zul) and brought to the attention of the Ubuntu Weekly News team. alexm will talk about it in his loco. The message is about nominating your favorite server papercuts, so that we gather as many candidates as possible now.

Action: ttx, zul to blog about papercuts, make sure UWN gets the word

Action: ttx to send email about criteria and nomination to ubuntu-devel, ubuntu-server

server-lucid-apport-hooks

Building on the UDS Dallas discussion about how having apport hooks in server packages can help the quality of the bug reports we receive, the server apport hooks effort aims at adding as many as we can before FeatureFreeze. zul created a page at https://wiki.ubuntu.com/ServerTeam/ApportHooks with likely candidates. Anyone interested, please sign up for your favorite package, or add your own !

Weekly Updates & Questions for the QA Team

soren has been extending the ISO testing features, and can now at the click of a button run ISO tests of the cartesian product of i386/amd64,lvm/non-lvm,basic/mail/bind9/lamp/postgresql installs. Documentation on the setup is under way, and the process should be ultimately integrated with Marc Tardif’s checkbox work. soren will lead an UbuntuDeveloperWeek session about this next Tuesday at 2000 UTC.

Weekly Updates & Questions for the Kernel Team

Discussion concentrated on bug 494565, since a decision must be reached on the best option to follow. The -virtual kernel currently being a subflavour of -server and -generic-pae, building support for the block devices needed for EC2 and UEC would also affect those kernels. The options are CONFIG_SCSI_SYM53C8XX_2, CONFIG_VIRTIO_NET and CONFIG_VIRTIO_BLK. CONFIG_SCSI_SYM53C8XX_2=y, in particular, could have unexpected consequences on some rare hardware. Note that building in that SCSI support would not prevent it from being manually bypassed. Alternatives would be to make -virtual a flavour of its own (but this adds a lot of maintenance work for the kernel team), patch UEC so that it works without that SCSI support (potential performance issues, deviation from upstream), or abandon the idea of using no ramdisks for UEC. This should be further discussed on ubuntu-devel.

Action: smoser to raise thread about the no-ramdisk / -virtual config tradeoff

Assigned and to-be-assigned bugs

List at http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html still needs to be cleaned up to be more useful.

Action: zul, kirkland to unassign themselves from “maybe working on one day” bugs

Agree on next meeting date and time

Next meeting will be on Wednesday, January 27th at 14:00 UTC in #ubuntu-meeting.

At UDS Lucid in Dallas the Ubuntu Server team had a session on how to take the opportunity of the LTS release to concentrate on fixing highly-annoying, low-hanging fruit bugs. This effort lead by Thierry Carrez was named Server papercuts as a tribute to the famous One hundred papercuts project from the Desktop experience team.

The idea is to spend time during this less-featureful development cycle to fix server usability issues to make Ubuntu Server even more sysadmin-friendly. The first part of this work involves identifying such issues, and for that we need the help of the Ubuntu Server user community, which experiences those issues every day. The second part is about fixing these Server papercuts. This is a great way to start being involved in bug fixing and Ubuntu development since these low hanging fruit should all be relatively easy-to-fix bugs.

How can I help?

If you come a across a bug in a server related package that looks like a good candidate, open a task against the server papercut project. The Ubuntu Server team will then review the different nomination and accept bugs that can be considered as low-hanging fruits.

If you have a patch to fix a bug, grab it and attach it to the bug. Or better, prepare a bzr branch and submit a merge proposal: the Ubuntu Server team will review it and guide you in the process of making your fix available in the archive.

The big number of Ubuntu bugs can sometimes be overwhelming. Providing high quality bugs can help in getting the bugs triaged and fixed faster. This is where Apport comes into the game – a tool used to automatically generate crash reports for debugging. Apport can be extended via hooks to provide specific information on a per package basis. For example the Ubuntu Server team added hooks for MySQL during the Karmic release cycle. Relevant logs as well as configuration information are automatically added to every bug reported against the mysql package.

If you have ideas about adding apport hooks for other server related packages let the Ubuntu Server team know. Add it to the wiki page, look up how to write apport hooks and prepare a patch – or better a bzr branch. The Ubuntu Server team will review it and help you integrate your work into the archive.