server November 2015

server@lists.fedoraproject.org

26 participants
16 discussions

Server SIG Weekly Meeting Minutes (2015-11-10)
by Stephen Gallagher 10 Nov '15

10 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================= #fedora-meeting-1: Server SIG Weekly Meeting (2015-11-10) ========================================================= Meeting started by sgallagh at 16:02:25 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-10/serversig.2015… . Meeting summary - --------------- * roll call (sgallagh, 16:02:25) * Agenda (sgallagh, 16:04:27) * Agenda Item: Cockpit Release Criteria (sgallagh, 16:04:28) * Agenda Item: Server/Cloud Interaction (sgallagh, 16:04:28) * Agenda Item: Minimal Installation (sgallagh, 16:04:28) * Cockpit Release Criteria (sgallagh, 16:05:53) * LINK: https://lists.fedoraproject.org/pipermail/server/2015-November/002114.html (sgallagh, 16:07:41) * LINK: http://fpaste.org/288885/ (mizmo, 16:19:18) * AGREED: New cockpit release criteria are accepted. (+7, 0, -0) (sgallagh, 16:22:36) * Server/Cloud Interaction (sgallagh, 16:22:42) * ACTION: mhayden and jds2001 will be the primary contacts with the Cloud SIG to discuss Server positioning in public clouds (sgallagh, 16:27:20) * Minimal Installation (sgallagh, 16:32:23) * AGREED: Proposal: Assert that Fedora Server is meant to be a defined platform and not necessarily the most minimal platform possible. (+5, 0, -0) (sgallagh, 16:57:17) * Open Floor (sgallagh, 17:00:09) Meeting ended at 17:01:57 UTC. Action Items - ------------ * mhayden and jds2001 will be the primary contacts with the Cloud SIG to discuss Server positioning in public clouds Action Items, by person - ----------------------- * jds2001 * mhayden and jds2001 will be the primary contacts with the Cloud SIG to discuss Server positioning in public clouds * mhayden * mhayden and jds2001 will be the primary contacts with the Cloud SIG to discuss Server positioning in public clouds * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * sgallagh (127) * mizmo (58) * jds2001 (33) * mhayden (30) * adamw (26) * nirik (14) * zodbot (14) * stefw (6) * linuxmodder (1) * danofsatx (0) * simo (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZCIyYACgkQeiVVYja6o6O1MwCgly2eTT9auXOUgkL1W3oH8tHr aXEAnRNJ4rMa2LqqZoSkgzI5Oy3Jhtx5 =t5cS -----END PGP SIGNATURE-----

1 0

Rolekit Weekly Meeting Minutes (2015-11-10)
by Stephen Gallagher 10 Nov '15

10 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ==================================== #fedora-server: rolekit (2015-11-10) ==================================== Meeting started by sgallagh at 14:30:03 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-server/2015-11-10/rolekitweekly.201… . Meeting summary - --------------- * init process (sgallagh, 14:30:04) * Agenda (sgallagh, 14:30:30) * Agenda Item: Issue Triage (sgallagh, 14:30:59) * Agenda Item: Status Report (sgallagh, 14:31:07) * Issue Triage (sgallagh, 14:32:42) * https://github.com/libre-server/rolekit/issues/54 - The Domain Controller role should support setting up the Vault (sgallagh, 14:33:59) * Assigned to nilsph for Fedora 24 nice-to-have enhancement (sgallagh, 14:48:53) * https://github.com/libre-server/rolekit/issues/55 - Ensure static IP for domain controller (sgallagh, 14:48:58) * Making this a documentation bug, assigned to sgallagh for Fedora 24 (sgallagh, 14:54:33) * https://github.com/libre-server/rolekit/issues/57 - Support redeploy() for Domain Controller (sgallagh, 14:54:58) * Domain Controller redeploy() is deferred to the Future milestone for now (sgallagh, 15:05:23) * Status Report (sgallagh, 15:06:57) * LINK: https://github.com/systemd/systemd/issues/1797 (sgallagh, 15:08:02) * Lots of discussion on the redesign of the unit file creation and monitoring. See full logs for details (sgallagh, 15:25:36) Meeting ended at 15:44:27 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * sgallagh (145) * nilsph (69) * twoerner (53) * zodbot (8) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZCEQUACgkQeiVVYja6o6N3VwCgkJROjek7IiYLTeQXt43Bf3tM itsAniBwxEKOFfwz9LFMZqdHtSYeomdi =ND0O -----END PGP SIGNATURE-----

1 0

Soliciting Agenda for Weekly Server SIG Agenda (2015-11-10)
by Stephen Gallagher 10 Nov '15

10 Nov '15

What do we want to discuss today, folks? I think we should have a follow-up on the Cockpit criteria discussion. Additionally, I think it would be good to select a subcommittee to work with the Cloud SIG to work on our plans in that space. Lastly, I want to open a new topic: Should the Server SIG be responsible for the "minimal" environment group in comps.xml? Technically, it is available on the Server install media, so we should decide if that makes sense for us to own in an official capacity. Many people already assume that we do, but as of right now, minimal installs report themselves as non-productized installations.

3 5

Call for topics for today's meeting - 2015-11-03
by Major Hayden 03 Nov '15

03 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hey there, I'm organizing today's meeting for Stephen and he asked me to send out an email calling for topics. If you have anything to discuss at today's IRC meeting, please let me know and I'll those topics added to the list. Thanks! - -- Major Hayden -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWOLp0AAoJEHNwUeDBAR+xYj8P/3BMzDnd3Fn2g9OwgsA7Drce 34Jii4YLqxU8+olowiFtNH8voY6Glkpo99OhnIWDp80gpNmhJU4Suo8JGaWzg1dH Pi6Ws9SAZ5xpd1/mbKDHCdTJ3F/fa7cfe5CMYuO3s67LTCAwYIYia+hsylWPn3HQ QTpjM6CD5frdApetQ1CBCgObU/3rnR0oq6CmQGC7FkGq4mPqd60kKa3RszrnN/UL bqUPfaIBzrI3txCRepRWX97zTCKxJgKpFjH3dwLY9n9MVTWAntIxPxHv8N59fUo3 M331zCI9/ZAwKQXFG0Q9MQ7q/zDTSoy69oVcRQ7OPdufr4l/zpb5DEubnwYA4ZLp nmua5otBYl4SPF3wCnqflXIYWChEIHJJnm1wta4n/USIVHydPLJW3xKSAo/yqUG1 ZzXNnqpnXEIfdEJUYKnTHAan1SCMJaa3APDiaYBz88/gVDneD7WjCLV7iwHBUBb8 jE7NAsHKSGSKFggxIjVBZBFtFo9AUjYz9WmzXECPcN4d8pv0D93uydOrpxPzmgno 27jMnCQlv9UpkSnWapyXmwXArND6QRl3AsOu+KN3Psf26gXsvkgEnnn92LSPmAqa L7kQc9lE5ObkrmDnZXMaQQZrpknLizuZrH4p6NI/WAiDlL/WxRj5u39nN0u49mFN FYyX9JOZGqOW6ZrJRlOk =nxv4 -----END PGP SIGNATURE-----

4 6

Karma request: freeipa and pki-core updates to fix FreeIPA upgrades
by Adam Williamson 02 Nov '15

02 Nov '15

Hi folks! We have a big problem with F23 at the moment, where upgrades from previous releases break FreeIPA. A couple of updates have just been sent out to try and fix this, and it'd be great if people could help test and karma them: https://bodhi.fedoraproject.org/updates/freeipa-4.2.3-1.fc23 https://bodhi.fedoraproject.org/updates/FEDORA-2015-f12c332a2f we'd recommend *not* testing on a production server for now :) The test should more or less be to deploy a FreeIPA server on F21 or F22, check it works, upgrade to F23, install both those updates, then try running the FreeIPA upgrade script - `ipa-server-upgrade` - and check whether you get a successful upgrade and a working server. If you do, you should be able to +1 karma both updates. Thanks a lot! I'd also be interested if anyone's seeing execmem denials from SELinux with FreeIPA on F23: https://bugzilla.redhat.com/show_bug.cgi?id=1277224 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 2

[F24 Criteria Change] FreeIPA Upgrades
by Stephen Gallagher 02 Nov '15

02 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Up to now, all of our release criteria for FreeIPA have been in terms of fresh installations on a newly-installed system. However, there are numerous individuals out there who are running FreeIPA on Fedora systems and who would suffer greatly if an upgrade from the previous version did not work. I propose that the following release criterion be added for Fedora 24 and onwards: Beta Criterion: * For any system with a configured and enabled FreeIPA server (or Domain Controller Role powered by the same), it must be possible to upgrade from Fedora N to Fedora N+1 and have the same set of domain controller services available after upgrade. As a secondary criterion, I'd also like to recommend that we add: Final Criterion: * For any system with a configured and enabled FreeIPA server (or Domain Controller Role powered by the same), it must be possible to upgrade from Fedora N to Fedora N+1 and have the same set of domain controller services available after upgrade without manual intervention. (Note, that secondary criterion is not currently possible; there is a manual upgrade script that must be run post-distro-upgrade). See https://fedorahosted.org/freeipa/ticket/5373 for more details. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlY3ewQACgkQeiVVYja6o6PqNgCdGQJz1NoRbonDIsAsmDvCovQY qPgAn3iuZFIbiQ+sGt6GeyeN+uDj1GHQ =KjHi -----END PGP SIGNATURE-----

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server November 2015