server July 2014

server@lists.fedoraproject.org

20 participants
26 discussions

Agenda for Server WG Meeting (2014-07-08)
by Stephen Gallagher 07 Jul '14

07 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There is only one agenda item for this week: * Release Media Status and Tasks As Adam Williamson noted in another thread, we need to have TC1 trees available this week. We need to divvy up the work and get this together immediately (if not sooner). I'm inviting Dennis Gilmore and Jon Disnard to join us for this meeting to help us sort out exactly what we need to get to them. Dennis, Jon: The meeting is at 1600 UTC tomorrow in #fedora-meeting-1. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO6kzAACgkQeiVVYja6o6N80gCfQKhoQoPtbWnK3e7/NOUHiMZE sxIAn0x69bV3bvpecOyg7Y81KBasGJYc =6auw -----END PGP SIGNATURE-----

1 0

Alpha TC1: this week, folks
by Adam Williamson 07 Jul '14

07 Jul '14

So, just to inject a valuable note of panic into proceedings, I thought I'd note in case anyone's unaware that Alpha TC1 is scheduled for Tuesday. My informal evaluation is that, to all intents and purposes, we do not have a product yet. Right? There's no server kickstart. We haven't written any of the code backing server roles, or any of the roles. There's no fedora-release-server package (I don't think). There's no variant build of anaconda with our planned changes in place. I have been rather behind on devel@ discussion and following FESCo and stuff lately, so I may be missing some existing consideration of this sort of thing, but it felt worth pointing out, at least. Anyone have any thoughts on this situation? (I just checked briefly, and it looks like as of last FESCo meeting, we're on schedule). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

3 2

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

07 Jul '14

Dear all, You are kindly invited to the meeting: Fedora Server Working Group on 2014-07-08 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

Multiple 'role' instances?
by Stef Walter 03 Jul '14

03 Jul '14

So this may be way out there ... I'm looking ahead to how Cockpit would implement roles, and combine them with other concepts such as containerized server applications... Is there (will there be) any concept in rolekit of mulitple instances of a role on a server? I know that this certainly doesn't apply to some services like IPA Domain Controller. But for others, such as databases it may be a limitation later on. For example MongoDB has one database. If you want more than one, you run more than one MongoDB on more than one port. These run as seperate systemd instances etc... Another example is PostgresQL. Although it supports multiple databases, it only supports one authentication scheme. If you want distinct authentication domains in postgres, you run it more than once. A general example is containerized services. If at some point we do implement a role using containers, having multiple containers filling the same "role" (eg: EAP node) is common. Anyway, I'm not saying that this is a *must have* aspect of rolekit. I wanted to raise the issue. It's certainly something we have to consider at the Cockpit level. Cheers, Stef

3 5

Remote access url and fingerprint in /etc/issue
by Stef Walter 03 Jul '14

03 Jul '14

I'd like to work [0] on adding a remote access URL to /etc/issue for Fedora Server 21 and Atomic. This puts useful information on the VT, especially for virtual machines, and also servers with monitors attached. It would look something like: Fedora Release 21 (xxx) Kernel 3.14.8-200.fc20.x86_64 on an x86_64 (tty1) Remote access: https://192.168.11.10:4444 SHA1: 80:81:46:45:0E:FF:75:AD:C5:40:7A:C2:38:74:57:46:BF:B1:DD:1C localhost login: Some notes or questions. * Including the certificate fingerprint makes it possible for more users to securely connect even when using self-signed certificate. * Should we include the appropriate ssh command? * Implementing the http URL is easy given agetty's support for \4 [1] * When Cockpit generates a self-signed certificate, it could either put the fingerprint directly in /etc/issue or alternatively we could work on a solution revolving around \S{VARIABLE} and /etc/os-release There's also the case of headless servers. I would like some way to have users be able to see the above info too. Perhaps via /etc/motd, or perhaps some other way. Cheers, Stef [0] https://bugzilla.redhat.com/show_bug.cgi?id=1110763 [1] man 8 agetty

3 3

Server WG Meeting (cancel?) (2014-07-01)
by Stephen Gallagher 01 Jul '14

01 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry folks, I forgot to send out an agenda this week. Unless there are any urgent topics that need the WG, I think we should be okay with continuing on the lists. A couple things to note and follow: 1) Thomas Woerner and I are hacking on rolekit and will be doing so in #fedora-server for the foreseeable futute. 2) I started a thread on the fedora-devel list about how to handle fedora-release-* and per-package configuration. Please review and chime in, this is important to all Products. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOyu0sACgkQeiVVYja6o6OKTACdGUMD1786rdwI29l0+9GhqNfP CkUAoIGYg5zSYdLPCvtHJWWlmGgQW0TV =3IOT -----END PGP SIGNATURE-----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server July 2014