server October 2014

server@lists.fedoraproject.org

20 participants
32 discussions

[Fedocal] Reminder meeting : Fedora Server Working Group
by Pierre-YvesChibon 27 Oct '14

27 Oct '14

Dear all, You are kindly invited to the meeting: Fedora Server Working Group on 2014-10-28 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly meeting to discuss issues and planning for the Fedora Server Product and SIG. More information available at: [http://fedoraproject.org/wiki/Server](http://fedoraproject.org/wiki/Server) Source: https://apps.fedoraproject.org/calendar//meeting/283/

1 0

[Fwd: [Fwd: [Test-Announce] Fedora 21 Beta Release Candidate 1 (RC1) Available Now!]]
by Stephen Gallagher 24 Oct '14

24 Oct '14

We've got a few issues, so this is likely to end up slipping by a week. I'd like anyone in the Server SIG who is willing to run as many of the validation tests as possible today, so we have the maximum time available to fix any discovered issues before Thursday's Go/No-Go meeting.

1 0

Server WG Quick Vote: Firewall status API for rolekit
by Stephen Gallagher 22 Oct '14

22 Oct '14

The Beta release criteria for rolekit were largely copied from the PRD and Technical Specification. One of these bits was this: "Release-blocking roles must be able to report their status in regard to the system firewall as described in the technical specification." The tech spec reads: "Roles will be required to support the following API: ... A query interface providing metadata information about the role (not all roles must implement all parts of this, bold lines are mandatory): ... A list of the ports that the role operates on, as well as data about whether those ports are currently firewalled." Unfortunately, rolekit does not currently have this capability. Thomas and I decided during development to defer that (because this information is available through the firewalld API and firewall-cmd as well), but we forgot to communicate it to the rest of the Server SIG. As a result, we (the Server WG) need to make a decision: Do we believe that this firewall status API is important enough to slip Beta. Because there's no chance we will be able to implement this in time for tonight's compose. Proposal: The requirement to be able to list the role's related firewall state is deferred to Fedora 22 and should be removed from the release criteria. I am +1. Please vote immediately, as we do not have much time.

8 7

2014-10-22 @ 1600 UTC ** Fedora 21 Blocker Review Meeting
by Mike Ruckman 22 Oct '14

22 Oct '14

# F21 Blocker Review meeting # Date: 2014-10-22 # Time: 16:00 UTC (12:00 EDT, 09:00 PDT) # Location: #fedora-blocker-review on irc.freenode.net We've already had one blocker review meeting this week (which is likely why I forgot to send this email until now), but it's time for another! With Go/No-Go being decided tomorrow we have plenty to do in order to be ready. So far we've got 9 proposed blockers and and 4 proposed freeze exceptions to look through for this meeting. If you want to take a look at the accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist We'll be evaluating these bugs to see if they violate the Beta Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F21 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you in a couple hours! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

Server WG Weekly Meeting Minutes (2014-10-21)
by Stephen Gallagher 22 Oct '14

22 Oct '14

=================================================================== #fedora-meeting-1: Server Working Group Weekly Meeting (2014-10-21) =================================================================== Meeting started by sgallagh at 15:00:33 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-10-21/fedora-meeting… . Meeting summary --------------- * roll call (sgallagh, 15:00:33) * Agenda (sgallagh, 15:06:12) * Agenda Item: Fedora 21 Install Media (sgallagh, 15:06:33) * Agenda Item: Fedora 21 Beta Status (sgallagh, 15:06:33) * Fedora 21 Install Media (sgallagh, 15:08:37) * AGREED: Server WG finds it acceptable that all netinstalls be universal and select Server as the default installation environment in interactive Anaconda. (+8, 0, -0) (sgallagh, 15:21:43) * Fedora 21 Beta Status (sgallagh, 15:22:26) * LINK: https://www.happyassassin.net/testcase_stats/21/Server.html (adamw, 15:25:26) * danofsatx has been running tests against the Domain Controller Role. Is encountering an issue with named. (sgallagh, 15:26:50) * ACTION: junland to jump right in with TC testing (sgallagh, 15:27:40) * ACTION: danofsatx to file a bug against FreeIPA for the named start failure (sgallagh, 15:28:43) * we really need to run those tests against Beta TC4/RC1 (sgallagh, 15:29:23) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_21_Beta_TC4_Server (sgallagh, 15:29:35) * LINK: https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria#Server_Produ… (sgallagh, 15:30:19) * for anyone who doesn't know, you can nominate blocker bugs at https://qa.fedoraproject.org/blockerbugs/propose_bug , or just mark them as blocking the bug 'BetaBlocker' and explain why in a comment. (sgallagh, 15:32:01) * Go/No-Go Meeting is Thursday, which means we hopefully don't have any blockers but if there are any we need to know *today* to have any chance of avoiding slippage. (sgallagh, 15:35:25) * It would be appreciated if anyone with spare cycles spends some time testing Beta TC4 today. (sgallagh, 15:36:03) * Open Floor (sgallagh, 15:40:57) * Product GUI install media still doesn't have the Product Logo (sgallagh, 15:46:34) * No risk to Beta release due to branding/logo (sgallagh, 15:48:28) * Server WG Test Day (sgallagh, 15:50:06) * ACTION: junland to look into scheduling a Fedora Server Test Day (sgallagh, 15:57:26) Meeting ended at 16:02:18 UTC. Action Items ------------ * junland to jump right in with TC testing * danofsatx to file a bug against FreeIPA for the named start failure * junland to look into scheduling a Fedora Server Test Day Action Items, by person ----------------------- * danofsatx * danofsatx to file a bug against FreeIPA for the named start failure * junland * junland to jump right in with TC testing * junland to look into scheduling a Fedora Server Test Day * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * sgallagh (108) * adamw (37) * simo (35) * junland (26) * nirik (13) * danofsatx (13) * zodbot (9) * tuanta (5) * mitr (3) * davidstrauss (2) * stefw (0) * mizmo (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

2 1

Server release validation updates
by Adam Williamson 22 Oct '14

22 Oct '14

Today I did some server validation testing - and, unfortunately, filed multiple blocker bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1155301 https://bugzilla.redhat.com/show_bug.cgi?id=1155304 https://bugzilla.redhat.com/show_bug.cgi?id=1155329 https://bugzilla.redhat.com/show_bug.cgi?id=1155334 I also wrote a couple of new test cases and modified the Server release validation matrix somewhat: * https://fedoraproject.org/wiki/QA:Testcase_Server_role_deploy is a generic 'test basic role functionality' test * https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_basic covers the Cockpit functionality that's meant to be present at Beta I added new tables to the matrix - https://fedoraproject.org/wiki/Template:Server_test_matrix - which apply the generic role functionality test to 'Release-blocking roles' and 'Non-release-blocking roles' - at present we only have one of each, but the idea is that the test will be listed once for each role we ship, in the appropriate table. I added the new Cockpit test directly to the 'general tests' section (where the tests we previously had live). I've applied all these changes to https://fedoraproject.org/wiki/Test_Results:Fedora_21_Beta_TC4_Server , and they'll show up 'automagically' for all future composes. We still need test cases for the specific FreeIPA functionality covered in the criteria, and a couple other bits and pieces we specified for Beta; I'll look at adding those ASAP. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

Decision on Fedora Product branding: Fedora $PRODUCT 21 vs Fedora 21 $PRODUCT
by Stephen Gallagher 21 Oct '14

21 Oct '14

Hello folks, I raised a question with the Board a couple weeks ago[1] as to how we should be branding the different releases. It's been clear that different groups have different opinions on whether we should call something Fedora Server 21 vs. Fedora 21 Server (and Workstation and Cloud, of course). I was asked by the Board to get input from each of the working groups as well as marketing and branding folks. I'm sending this to each of these lists, but PLEASE keep all replies on the devel(a)lists.fedoraproject.org list or it will be impossible to keep track of the replies. (I've set the reply-to header on this email; please try not to lose it). A few specific comments that have been made on the Board ticket (to avoid rehashing them). * "Fedora Server 21" sounds like we've had 21 releases of Fedora Server and we certainly haven't. * Should we start all of the Products at version 1 and say "built on the Fedora 21 platform"? Anyway, we need to have a consistent branding decision made for the release (and for the Ambassadors). So please come prepared to find a consensus (not to win a fight). [1] https://fedorahosted.org/board/ticket/11

2 1

Soliciting Agenda for 2014-10-21 meeting
by Stephen Gallagher 20 Oct '14

20 Oct '14

What do we need to discuss on Tuesday? I think at minimum we need to make sure we're in shape for Beta release (there should be a release candidate compose by then)

3 4

New in beta to highlight?
by Joe Brockmeier 20 Oct '14

20 Oct '14

Hi all, Any big new features/changes in the beta we should be highlighting in the beta announcement? Please let me know ASAP and I'll incorporate them. Or - edit boldly! https://fedoraproject.org/wiki/F21_Beta_release_announcement Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

3 2

[Fedocal] Reminder meeting : Fedora Server Working Group
by Pierre-YvesChibon 20 Oct '14

20 Oct '14

Dear all, You are kindly invited to the meeting: Fedora Server Working Group on 2014-10-21 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly meeting to discuss issues and planning for the Fedora Server Product and SIG. More information available at: [http://fedoraproject.org/wiki/Server](http://fedoraproject.org/wiki/Server) Source: https://apps.fedoraproject.org/calendar//meeting/283/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server October 2014