15:00:54 #startmeeting Server SIG Weekly Meeting (2015-04-07) 15:00:54 Meeting started Tue Apr 7 15:00:54 2015 UTC. The chair is sgallagh. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:54 #chair sgallagh mizmo nirik stefw adamw simo tuanta mitr danofsatx 15:00:54 Current chairs: adamw danofsatx mitr mizmo nirik sgallagh simo stefw tuanta 15:00:54 #topic roll call 15:01:16 morning 15:01:21 .hello sgallagh 15:01:21 .hello junland 15:01:22 sgallagh: sgallagh 'Stephen Gallagher' 15:01:25 .hello stefw 15:01:26 junland: junland 'John Unland' 15:01:29 stefw: stefw 'Stef Walter' 15:03:00 Hell 15:03:03 Hello 15:03:10 (sorry) 15:03:12 .hello simo 15:03:16 simo: simo 'Simo Sorce' 15:03:27 mitr: a bad day today? :) 15:03:43 Luckily just a typo 15:04:41 #topic Agenda 15:04:46 #info Agenda Item: F22 Beta Testing 15:04:46 #info Agenda Item: F22 Talking Points 15:04:46 #info Agenda Item: NTP 15:04:51 ahoy 15:05:31 Any other agenda topics? 15:05:59 OK, let's get started then 15:06:03 #info Agenda Item: F22 Beta Testing 15:06:06 #undo 15:06:06 Removing item from minutes: INFO by sgallagh at 15:06:03 : Agenda Item: F22 Beta Testing 15:06:12 #topic F22 Beta Testing 15:06:37 adamw: Any progress on the test cases for the DB role? 15:06:57 nope. always seems to be that something else comes up first. 15:07:05 hopefully it's not too hard to test it without instructions... 15:07:49 Shouldn't be :-p 15:07:50 It's hard to get a sense of what specifically has to be working 15:08:11 anyone want to volunteer to help turn the core and functional requirements pages into actual test plans? 15:08:11 what's written in the criteria 15:08:20 er, requirements. :P 15:08:31 if no-one else volunteers i will get to it some damn time, honest 15:08:52 adamw: I'm just a little concerned about "some damn time" not being before Go/No-Go ;) 15:08:53 I'll be busy with a group project for my class but I will try to leave some input...if I can... 15:09:54 #info Help needed to convert Database Server Role requirements into a test plan 15:10:10 OK, I'll see what I can squeeze into my schedule this afternoon. 15:10:35 adamw: Is there a howto document on the proper wiki magic? 15:10:52 sgallagh: http://fedoraproject.org/wiki/QA:SOP_test_case_creation 15:11:00 #link http://fedoraproject.org/wiki/QA:SOP_test_case_creation 15:11:01 Thanks 15:11:03 for a basic test case little magic is required, just using the test case template (which the SOP talks about) 15:11:27 i quite often use extra templates just to share things like setup steps that are the same between multiple test cases. 15:11:57 hi guys sorry i have to skip the meeting today, im onboarding a new intern 15:12:00 So once those test plans exist (or at least start existing) later today, I need some volunteers to run through them and add karma. 15:12:08 mizmo: No worries! 15:12:17 oh, one thing, do make sure you stick with the convention that the name starts with "QA:Testcase" 15:12:28 * nirik nods. wiki namespace is important. 15:12:39 nirik: also wikitcms relies on it for finding test cases. 15:12:53 (it handles some old variants too, but QA:Testcase is the New Normal.) 15:12:56 adamw: That says to me "This belongs in the SOP" :) 15:13:01 it's in the Wikitcms SOP 15:13:13 k 15:13:13 but yeah, should probably be there too, if it isn't. i'll check 15:13:21 ah yes, it is. 15:13:26 great 15:13:46 So... volunteers to run the tests if I (and others) create them? 15:14:14 Related: I need to make a decision *today* on whether rolekit 0.3.1 goes to stable. 15:14:20 * adamw will try to do that also 15:14:34 Because if things go *well*, we'll have a release candidate tonight 15:14:39 we should be able to automate the db tests somehow or other, really. 15:14:55 adamw: Yeah, should be relatively straightforward. 15:15:03 Easily scriptable, at any rate 15:15:28 s/have a release candidate tonight/will be building a release candidate tonight/ 15:16:11 I've tested it myself reasonably well, but given that the DB Role is kind of our Big Feature this release, I'd like to have someone else sign off on it. 15:16:31 So I'm going to try to get this test plan written ASAP (I'll bump my other stuff, I guess). 15:16:49 #action sgallagh to write up a Database Role test plan today 15:18:02 thanks 15:18:04 OK, I think we've beaten that particular deceased equine sufficiently 15:18:11 i can already see the crap that's gonna eat the rest of my day. 15:18:25 #info Agenda Item: F22 Talking Points 15:19:06 tuanta has volunteered to gather and write these up, but we should probably offer a few suggestions. 15:19:38 #info Talking Point: Database Server Role 15:19:54 #info Talking Point: Default to XFS filesystem 15:20:05 (most of you are chaired, so jump right in) 15:20:07 these are short sentences/statements for a brochure or the like? 15:20:18 nirik: Right now, these are just ideas. 15:20:57 The talking points will be narrowed down by marketing/ambassadors (probably by tuanta in our case) and then turned into a training exercise for ambassadors. 15:20:57 From Fedora 22, Cockpit now has a backward compatibility guarantee ... you can add Fedora Servers to the dashboard as long as they're all Fedora 22+ 15:21:02 is that worth mentioning? 15:21:07 So they're not just short blurbs 15:21:13 stefw: Yes, absolutely 15:21:36 ok 15:21:49 do we have cockpit role deployment yet? 15:21:51 #info Talking Point: From Fedora 22 onwards, Cockpit will be compatible between OS releases 15:22:00 adamw: No, that was deferred to F23 15:22:03 k. 15:22:15 I've probably got a GSoC student to work on it, which is great. 15:24:02 I suspect we also want these to be primarily user-focused talking points. So things like pbrobinson's excellent work slimming down dependencies is probably not worth including (though it's a great addition) 15:24:28 Ooh, Docker support on ARMv7hl is probably worth mentioning, yes? 15:25:52 #info Talking Point: Fedora Server supports Docker containers on the armv7hl architecture 15:26:16 Other high-visibility changes? 15:26:23 worth mentioning yum->dnf? but that might be in other places already 15:26:31 yeah, doesn't seem flavor-specific. 15:27:38 Let's call it out anyway 15:27:46 Worst case, it ends on the cutting-room floor 15:27:47 ipsilon might be interesting to server folks... 15:28:06 #info Talking Point: DNF as the default package manager 15:28:57 #info Talking Point: Ipsilon - new multiple-protocol identity provider service 15:29:38 I hope we can land 1.0 w/o too many bugs :) 15:29:41 (of Ipsilon) 15:30:19 simo: (slightly OT) Is there documentation on how to stand up Ipsilon with FreeIPA somewhere? 15:30:51 almost :) 15:31:11 * nirik is looking forward to it being deployed in infra. ;) 15:31:19 /me mutters something about horseshoes 15:31:30 OK, anything else on this topic? 15:32:24 OK, on to NTP then 15:32:31 #topic NTP 15:32:39 sgallagh: well al lyou need to do is setup with --ipa=yes iirc: ) 15:33:06 sgallagh: should we open bugs to make the domain controller role configure cronyd as ntp server ? 15:33:09 So, as noted on the list, I tweaked comps.xml so that TC9/RC1 should install chrony by default 15:33:19 simo: I'm honestly surprised it doesn't already. 15:33:27 what was it installing before? 15:33:30 Chrony has been the default in Fedora for, what four releases now? 15:33:44 adamw: Somewhere between F21 and F22, it stopped installing CHrony 15:33:47 ah. 15:34:12 I couldn't actually figure out how it got installed in F21. Seemed a lucky accident 15:34:48 Might have been pulled in by an obscure dependency chain that we broke 15:34:59 domain controller needs a ntp server ? 15:35:15 nirik: so that clients stay in sync 15:35:17 if so, then yeah, if we can make chrony do it that seems better to me than going back to ntp. 15:35:30 it is optional 15:35:36 but we install it by default 15:35:58 * nirik nods. 15:36:34 I need to test, but I think freeipa-server-install disables chrony if it's running in favor of ntp 15:36:43 (I think I remember that from two or three years ago) 15:36:48 I think this would be good to poke at after beta... ;) 15:37:13 nirik: Actually, I need to verify that statement. 15:37:34 Because if it *breaks* if chrony is installed, we have a problem :) 15:37:51 sgallagh: it doesn't break afaik 15:37:59 yeah. Hope not 15:38:13 * nirik wonders again about comps gating during freeze. ;) 15:38:33 Well, installing chrony on an F22 server running FreeIPA right now results in NTP being stopped and chrony started 15:38:41 oh it *did* break when chrony was first introduced in fedora, so we fixed it to turn chronyd off instead of breaking :) 15:38:58 ok 15:39:17 So for now, let's agree that no (further) changes will be made for Beta? 15:39:19 sgallagh: as long as chronyd serves client sit is fine if it doesn;t listen on the network though then it is bad 15:39:53 simo: Can you have the FreeIPA guys look into a full chrony solution and see if it's feasible for Final? If not, we'll defer to F23. 15:40:42 not now 15:40:50 Has mlichvar actually said that chrony is a better server than ntpd? 15:40:53 they are way too busy 15:41:21 (It has been kind of implied, but still) 15:41:31 better how? exactly ? 15:41:59 better overall all things considered 15:42:53 Anyway, that’s post-F22 15:43:04 well, fewer security issues, but younger. ;) 15:44:30 #info We'll stick with chrony by default in F22, with the Server Role replacing it with NTP if deployed. 15:44:55 +1 15:45:06 #info Plans for F23 include doing an analysis of the relative benefits of chrony, ntp and timesyncd and switching everything to the one that makes the most sense. 15:45:17 sure. 15:45:31 ack 15:45:53 Anything further on this topic? 15:46:40 Nope. 15:46:51 #topic Open Floor 15:46:56 Anything for Open Floor? 15:48:01 * nirik has nothing to bring up 15:49:21 OK, thanks for coming folks. I'll get those test plans up soon. 15:49:30 #endmeeting