Server SIG Weekly Meeting Minutes (2015-04-28)
by Stephen Gallagher
=========================================================
#fedora-meeting-1: Server SIG Weekly Meeting (2015-04-28)
=========================================================
Meeting started by sgallagh at 15:00:08 UTC. The full logs are
available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-04-28/fedora
-meeting-1.2015-04-28-15.00.log.html
.
Meeting summary
---------------
* roll call (sgallagh, 15:00:08)
* Agenda (sgallagh, 15:06:15)
* Agenda Item: F23 Planning (sgallagh, 15:06:21)
* F23 Planning (sgallagh, 15:09:19)
* LINK:
https://lists.fedoraproject.org/pipermail/server/2015-April/001842.html
(sgallagh, 15:10:02)
* libabigail includes an abidiff tool which is pretty handy and could
be plugged into a taskotron test (sgallagh, 15:20:14)
* Formulate concrete plans at next week's Server SIG meeting
(sgallagh, 15:40:50)
* ACTION: stefw to start a conversation about package/security
updates
on the mailing list (sgallagh, 16:02:16)
Meeting ended at 16:13:00 UTC.
Action Items
------------
* stefw to start a conversation about package/security updates on the
mailing list
Action Items, by person
-----------------------
* stefw
* stefw to start a conversation about package/security updates on the
mailing list
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* sgallagh (120)
* simo (105)
* stefw (78)
* nirik (47)
* adamw (23)
* zodbot (9)
* randomuser (7)
* jonmasters_ (4)
* bochecha (2)
* mitr (0)
* danofsatx (0)
* tuanta (0)
* mizmo (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 5 months
Call for agenda for Server SIG Weekly Meeting (2015-04-28)
by Stephen Gallagher
This week, I think we need to discuss plans for Fedora 23.
Many people continue to ask if Fedora Server plans to have a long-term
maintenance release in the future. Thus far, we've all been pretty
much in agreement that we aren't ready for that.
The problem with a long-term release is, of course, personnel. It's
not terribly exciting to provide support on older (sometimes outdated)
packages, so no one really wants to do it without a really compelling
reason (in Ubuntu, this is usually - but not always - a paycheck from
Canonical).
However, a long-term maintenance release is a potential _solution_,
not a description of the problem. Looking at the real problem behind
it, the issue is actually "I need a guarantee that software I run atop
this is expected to continue working for X months/years." What this
really means is that the supported APIs and ABIs on the system
continue to behave the same way for an extended period of time. This
is orthogonal to the problem of packages.
So my proposal for Fedora 23 is that we de-emphasize the user-visible
engineering for a release in favor of working on tools to enable us to
better maintain API and ABI across releases. For example, I think we
need to be developing a taskotron tool to monitor for C/C++ ABI
changes in any /usr/lib[64] library that we ship in the default Fedora
Server install. Such a tool should disable auto-pushing to stable if
the ABI changes in an incompatible way.
The other thing we should be doing is gathering API documentation into
a common place where we can decide which of the default packages we
install should be considered "stable" API (possibly defined as "stuff
we agree must work for 2-4 releases, even if this means maintaining a
compat package for a while").
So in short, my proposal is for us to research what we are shipping in
terms of libraries and APIs (such as D-BUS), gather their
documentation in one place and use this as a basis to build tools to
help us ensure that they stay functional for multiple releases.
Let's discuss this at the meeting today.
8 years, 5 months
Agenda Request for 2015-04-21 Server SIG Meeting
by Stephen Gallagher
What is on this week's agenda, folks?
I think we probably need to figure out what our top priorities are for
Final release. I suspect we need to do some work with the marketing,
websites and ambassador teams to ready them for the release.
8 years, 5 months
Beta blocker/FE update karma requests
by Adam Williamson
Hi folks! As some of you know, part of the release validation process is
to make sure the fixes for blocker and freeze exception bugs are tested
and confirmed, and give karma to the updates so they can be pushed to
stable.
For F22 Beta, the following updates for blocker/FE bugs have been
included in Beta RC2, and we need to confirm the fixes and provide
karma. It would be great if folks could help with this. Of course not
everyone will have the necessary configuration or Cloud accounts or
whatever to test every fix, don't worry! Just do whatever you can if you
have some time to help out.
* https://admin.fedoraproject.org/updates/FEDORA-2015-4820/cloud-utils-0.27...
This one fixes https://bugzilla.redhat.com/show_bug.cgi?id=1197894 . You
can give it +1 karma if you test a 22 Beta RC2 Cloud image - see the
test cases at
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Beta_RC2_Cloud -
and find that it boots successfully and the root partition is resized to
fit the space available.
* https://admin.fedoraproject.org/updates/util-linux-2.26.1-1.fc22
This one fixes https://bugzilla.redhat.com/show_bug.cgi?id=1210428 .
It's another Cloud issue: to test this one, you need to deploy a cloud
instance and then reboot it. If that works (and the resize still
happens), you can +1 the update.
* https://admin.fedoraproject.org/updates/FEDORA-2015-5751/gnome-boxes-3.16...
This one fixes https://bugzilla.redhat.com/show_bug.cgi?id=1164492 . You
can give it +1 karma if you boot the 22 Beta RC2 Workstation live image
(any arch) and confirm that the libvirt default NAT network
configuration is *not* set up: that is, there's no virbr0 interface, and
the package libvirt-daemon-config-network is not installed.
* https://admin.fedoraproject.org/updates/FEDORA-2015-5960/realmd-0.15.2-2....
This one fixes https://bugzilla.redhat.com/show_bug.cgi?id=1210483 .
Testing the blocker fix requires you to have an Active Directory domain
controller available (you'd have to install Fedora 22 Beta RC2 Server
and then enrol the newly installed system in the AD domain using realmd
- test cases at
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Beta_RC2_Server#Dom... - but if you have a FreeIPA domain you could at least check this realmd build works OK for enrolling in that domain.
* https://admin.fedoraproject.org/updates/FEDORA-2015-4922/rolekit-0.3.2-1....
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1209602 and also
https://bugzilla.redhat.com/show_bug.cgi?id=1207872 (an FE bug), both
related to deployment of the database 'Server Role'. To test it, install
Fedora 22 Beta RC2 Server (DVD, or if you use the netinst, ensure you
get that version of rolekit from updates-testing) and then try to deploy
the database server role...which I can't find any instructions for ATM,
but sgallagh might be able to provide some. Then check you can log into
the deployed pgsql instance with the password from the role config.
* https://admin.fedoraproject.org/updates/FEDORA-2015-5686/kwin-5.2.2-2.fc22
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1210861 , an FE
issue. You can +1 it so long as the F22 Beta RC2 KDE live image seems to
be basically working fine and this update doesn't seem to cause any
issues - kwin is involved in just about anything you do in KDE,
obviously, so as long as the KDE validation tests are good we can be
pretty confident this is fine.
* https://admin.fedoraproject.org/updates/FEDORA-2015-4553/libzip-0.11.2-5....
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1204677 , an FE
security issue. I don't know the details of how to verify the security
fix is good, but you can give it a general +1 if zip file manipulation
in dependent packages seems to be working. "sudo repoquery
--whatrequires libzip" will list packages with a direct dep on libzip.
* https://admin.fedoraproject.org/updates/FEDORA-2015-5161/plasma-workspace...
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1207079 , another
FE issue. Test for this one is pretty simple: make sure you get a
screenshot when you press the 'Print Screen' key in 22 Beta RC2 KDE.
* https://admin.fedoraproject.org/updates/FEDORA-2015-4727/qt5-qtwebkit-5.4...
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1204796 , another
FE security issue, also in KDE. Going by the bug description, to verify
the fix you'd need to check what was logged in the file
'WebpageIcons.db' somehow (I'm assuming it's a simple DB mapping URLs to
favicons), but you can give it a general +1 if web browsing with
Konqueror works OK in 22 Beta RC2 KDE.
Again, whatever help folks can provide on testing these would be great -
thanks! And of course, we need all the help we can get filling out the
Beta RC2 test matrices, see
https://lists.fedoraproject.org/pipermail/test-announce/2015-April/001040... for all the details on that.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
8 years, 5 months
Fedora Server lifecycle
by Carlos Raúl Laguna
Hello to everyone,
I have a question about lifecycle, i read the draft proposal
https://fedoraproject.org/wiki/Server/Proposals/Server_Lifecycle , but that
is 2013 old ? Any actual news on this, i am about to deploy a freeipa
environment in one hand i have centos 7 ipa 4.1.0 and Fedora 21 server
4.1.2 with several bugs corrected in the other can anyone point me some
more recent direction in this topic. Regard
8 years, 5 months
Server SIG Weekly Meeting Minutes (2015-04-07)
by Stephen Gallagher
=========================================================
#fedora-meeting-1: Server SIG Weekly Meeting (2015-04-07)
=========================================================
Meeting started by sgallagh at 15:00:54 UTC. The full logs are
available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-04-07/fedora-meeti...
.
Meeting summary
---------------
* roll call (sgallagh, 15:00:54)
* Agenda (sgallagh, 15:04:41)
* Agenda Item: F22 Beta Testing (sgallagh, 15:04:46)
* Agenda Item: F22 Talking Points (sgallagh, 15:04:46)
* Agenda Item: NTP (sgallagh, 15:04:46)
* F22 Beta Testing (sgallagh, 15:06:12)
* Help needed to convert Database Server Role requirements into a
test
plan (sgallagh, 15:09:54)
* LINK: http://fedoraproject.org/wiki/QA:SOP_test_case_creation
(sgallagh, 15:11:00)
* ACTION: sgallagh to write up a Database Role test plan today
(sgallagh, 15:16:49)
* Agenda Item: F22 Talking Points (sgallagh, 15:18:25)
* Talking Point: Database Server Role (sgallagh, 15:19:38)
* Talking Point: Default to XFS filesystem (sgallagh, 15:19:54)
* Talking Point: From Fedora 22 onwards, Cockpit will be compatible
between OS releases (sgallagh, 15:21:51)
* Talking Point: Fedora Server supports Docker containers on the
armv7hl architecture (sgallagh, 15:25:52)
* Talking Point: DNF as the default package manager (sgallagh,
15:28:06)
* Talking Point: Ipsilon - new multiple-protocol identity provider
service (sgallagh, 15:28:57)
* NTP (sgallagh, 15:32:31)
* We'll stick with chrony by default in F22, with the Server Role
replacing it with NTP if deployed. (sgallagh, 15:44:30)
* 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. (sgallagh, 15:45:06)
* Open Floor (sgallagh, 15:46:51)
Meeting ended at 15:49:30 UTC.
Action Items
------------
* sgallagh to write up a Database Role test plan today
Action Items, by person
-----------------------
* sgallagh
* sgallagh to write up a Database Role test plan today
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* sgallagh (83)
* adamw (24)
* simo (17)
* nirik (16)
* mitr (9)
* zodbot (8)
* junland (3)
* stefw (3)
* jsmith (1)
* mizmo (1)
* danofsatx (0)
* tuanta (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 5 months
chrony, ntp, timesyncd?
by Chris Murphy
I have Fedora 22 Server Beta TC4 (I realize TC6 is current0 installed,
and just today realized the date+time is wrong by 20 hours. I don't
know why it would be this wrong absent something to keep it accurate,
however chrony is was not installed by default. It is installed by
default with Fedora 21 Server. So? Is this inadvertent? I think
something needs to keep the time correct.
--
Chris Murphy
8 years, 5 months
