August 2016 - server - Fedora mailing-lists

Proposal: Changes to Fedora Server default partitioning scheme
by Stephen Gallagher 13 Dec '24

13 Dec '24

The following proposal comes out of the discussion at this weeks Server SIG meeting[1] Fedora Server will have: * / (root) will be a minimum of 2 GiB and a maximum of 15 GiB * SWAP will continue to be calculated automatically based on available RAM on the system * All unused space will be assigned to a volume group and available to be assigned to new partitions or extend existing partitions. * Anaconda will continue to handle the appropriate EFI and /boot settings We also discussed during the meeting whether we should have a separate /var partition by default, but the general sense was that we might be better served by developing a mechanism to allow partitions to be split from existing mount points, which would be more flexible going forward. As we did not have quorum in the meeting by the point we got to this proposal, I'm taking it to the list for discussion and votes. For the record, the current behavior of the partitioning scheme is for / to be given up to 50 GiB of space and then any remaining space after that is assigned to a separate /home partition. [1] https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-15/serversig.201…

4 8

Working group members: express your continued interest
by Kevin Fenzi 12 Sep '16

12 Sep '16

Greetings. At flock recently and at todays meeting we discussed plans moving forward. https://meetbot.fedoraproject.org/fedora-meeting-2/2016-08-09/server_workin… The first of those is to check our membership and make sure everyone is still wanting to be involved. We have currently 1 open seat, but others may wish to bow out now if they don't have time or desire. So, could all existing Server working group members chime in on list if they are interested in staying in the group or giving up their seat? We will give two weeks (until the 2016-08-23 meeting) and then look to fill empty seats with interested parties. Once the seats are filled we will look at setting a new meeting time. Sgallagh is going to try and clean up and present on list a new PRD for us to review over the next week. Members can use that discussion to see if they are still wishing to participate. kevin

14 19

PRD Discussion: Kellogg Logic Model (Phase 1: Impact)
by Stephen Gallagher 06 Sep '16

06 Sep '16

We need to discuss our new plans going forward for the Fedora Server Edition. Fedora has started adopting the Kellogg Logic Model[1] for planning purposes. At this year's Flock in Kraków, Poland, we started this process with the people who were present. I put together a Kanban board[2] as an imperfect visualization of this discussion so we can use that. In a proper visualization of the model, all of the cards would have arrows pointing to the column to their right to indicate which card they were implementing. I'd like to continue this exercise with the larger Server SIG audience on this mailing list. We will go through five unique phases, each corresponding to the five columns in the Kellogg Logic Model from right to left (so we will start at the rightmost column, "Impact" and then proceed through "Outcomes", "Outputs", "Activities", and "Resources in order). This thread will begin with "Impact". In the Kellogg Logic Model, this is the high-level change we want to effect in the world. An analogue to this in our original PRD would be our Mission and Vision statements. At Flock, we summarized (and shortened) the Vision and Mission as follows: * Vision: Admins default to choosing Fedora Server as a deployment platform for apps and services * Mission: Produce common base and server roles (best practices in a can) So let's start by discussing these. Do we like these as our long-term end goals? Should they be more specific or more vague? [1] https://www.wkkf.org/resource-directory/resource/2006/02/wk-kellogg-foundat… [2] https://taiga.fedorainfracloud.org/project/sgallagh-fedora-server-planning-…

3 5

Server SIG Weekly Meeting Minutes (2016-08-30)
by Stephen Gallagher 30 Aug '16

30 Aug '16

=================================================================== #fedora-meeting-1: Server Working Group Weekly Meeting (2016-08-30) =================================================================== Meeting started by sgallagh at 20:00:55 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-30/serversig.201… . Meeting summary --------------- * Roll Call (sgallagh, 20:00:55) * Agenda (sgallagh, 20:09:52) * Agenda Item: Server SIG PRD (sgallagh, 20:09:52) * Agenda Item: Server Edition cloud image (sgallagh, 20:11:26) * Server SIG PRD (sgallagh, 20:12:21) * LINK: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… (sgallagh, 20:13:50) * LINK: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… (sgallagh, 20:16:24) * LINK: https://taiga.fedorainfracloud.org/project/sgallagh-fedora-server-planning-… (sgallagh, 20:19:39) * Current Vision Statement: Fedora Server is the preferred [community] platform for system administrators and developers seeking to deploy applications and services that use the latest technology on a stable foundation with effective resource utilization. (sgallagh, 20:27:45) * Flock abridged Vision Statement: Admins default to choosing Fedora Server as a deployment platform for apps and services (sgallagh, 20:28:45) * LINK: https://taiga.fedorainfracloud.org/project/sgallagh-fedora-server-planning-… (jds2001, 20:30:39) * LINK: https://taiga.fedorainfracloud.org/project/sgallagh-fedora-server-planning-… (sgallagh, 20:30:42) * Lots of discussion on this topic, will continue on the list (sgallagh, 21:34:52) Meeting ended at 21:35:26 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mizmo (181) * sgallagh (158) * langdon (46) * vvaldez (37) * jds2001 (36) * nirik (26) * smooge (20) * rbergeron (19) * zodbot (18) * mhayden (14) * mjwolf (7) * adamw (3) * geppetto (1) * dperpeet (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Kellogg Logic Model Discussion
by Stephen Gallagher 30 Aug '16

30 Aug '16

Stephen Smoogen asked me to go over the logic model with him a bit today, which we did in #fedora-server. Since it may be useful to others, here's a log of our conversation. I hope it helps disambiguate things. (12:01:08 PM) sgallagh: OK, so let me start from a fairly high-level view. (12:01:45 PM) sgallagh: We originally developed the Server PRD shortly after Flock Charleston with a bunch of ideas we had for what the Server Edition should look like. (12:02:23 PM) sgallagh: It's been a couple years since then and the world has changed, so instead of the small tweaks we made to the PRD last year, we decided it might be time to take the design back to brass tacks (12:02:50 PM) smooge: that is good. I am looking at using this process on EPEL also (since it doesn't even have a PRD) (12:03:03 PM) sgallagh: As part of that effort, I latched on to the Kellogg Logic Model as a means to accomplish two things: (12:03:18 PM) sgallagh: 1) Provide a structured brainstorming model for what we want to get done (12:03:30 PM) sgallagh: 2) Provide an organized, step-by-step guide for how to get there. (12:04:12 PM) sgallagh: Essentially, we will use this model to provide a high-level view of what we want to achieve over the next couple years (12:04:44 PM) sgallagh: The KLM is broken up into five main categories: three that we can affect directly and two that are results or consequences from those. 12:05 (12:05:32 PM) sgallagh: Normally, planning is done from right to left; in essence we start by describing what we want the end-state to look like and then work backwards from there, ensuring that every step along the way ties itself directly to those goals (12:06:04 PM) sgallagh: Execution goes left to right. (12:07:17 PM) sgallagh: I should mention the five categories (from left to right): "Inputs", "Activities", "Outputs" and then "Outcomes" and "Impact" (12:07:55 PM) sgallagh: So planning begins with "Impact". In other words, what is the grand change that we want to see in the world/industry as a result of our actions. (12:08:32 PM) sgallagh: smooge: With me so far? (12:09:01 PM) smooge: trying (12:09:32 PM) sgallagh: smooge: OK, what can I do to make it clearer? 12:10 (12:10:08 PM) smooge: I don't understand how we can plan for stuff we don't have affect over. (12:10:46 PM) smooge: So if we can work on Impacts, Activities and Outputs but Outcomes and Impact are not ours to actually say about.. why do we start with those 2? (12:11:02 PM) smooge: does that make sense? (12:11:11 PM) sgallagh: I didn't say we had no affect over them (12:11:22 PM) sgallagh: I said that we don't have *direct* affect. (12:11:45 PM) sgallagh: For a simple example: I want my employees to be healthier. (12:11:59 PM) sgallagh: So I build a gymnasium in the office. (12:12:13 PM) sgallagh: I can't *directly* make my employees healthy, but I can provide a path to it. (12:13:03 PM) sgallagh: Actually, let's take that as an example to work through (12:13:19 PM) smooge: ok sounds good (12:13:58 PM) sgallagh: The Impact I want to have is "Improved employee retention" (12:14:19 PM) sgallagh: An Outcome that I might seek is "Employees spend their PTO on vacation instead of sick leave" 12:15 (12:15:04 PM) sgallagh: So one of many Outputs I might include would be building a gym for them to exercise before/after work. (12:15:24 PM) sgallagh: smooge: Is that a little easier to follow? (12:15:37 PM) smooge: yes (12:16:18 PM) smooge: though my pedantic brain tries to rebel at connecting the two :) (12:16:24 PM) sgallagh: So then we'd go down to Activities which would be things like "Purchase gym equipment" and then futher to Inputs which would be capital and personnell (12:16:40 PM) sgallagh: Well, that's actually the most important part (12:16:48 PM) sgallagh: And yes, this is a contrived example (12:17:20 PM) sgallagh: The most important aspect of this is that nothing appears to the left in the model without directly serving at least one element to the right (except Impact, of course) (12:18:06 PM) sgallagh: Among other things, this helps trim down on work that doesn't directly advance the mission (12:19:30 PM) sgallagh: So my first goal for this process is to get everyone in the WG on the same page wrt our "mission" (12:19:47 PM) sgallagh: *How* do we want to change the world 12:20 (12:20:13 PM) sgallagh: And then break it down until we have a path there (12:20:56 PM) ***sgallagh leaves room for comments (12:21:18 PM) smooge: ok that makes a lot more sense than the web pages I was going through (12:22:03 PM) sgallagh: Oh, good (12:22:56 PM) sgallagh: It's really not anything that there aren't a hundred other frameworks for, but since we weren't using *any* of them, going with the one that other parts of the Fedora Project latched on to seemed sensible (12:23:01 PM) smooge: so when I looked at the taiga board I felt the impacts were too large to be achievable. I see "Improved employee retention" as something that is achievable because it can be measured against (12:23:58 PM) sgallagh: Well, this model differentiates between "capable of being measured" and "we have a way to measure it". (12:24:19 PM) smooge: I am trying to figure out how much of that inability to see due to inbuilt blinders (12:24:21 PM) sgallagh: But when we get to that phase, we may indeed change what's there to make it more possible (12:24:48 PM) smooge: since I have a ton of inbuilt blinders :) 12:25 (12:25:38 PM) sgallagh: Please also be aware that the Taiga board is the result of 20 minutes of brainstorming at Flock. They're a guidepost (12:25:39 PM) smooge: the other part that didn't come up in the articles I read was how we move left to right in the KLM. (12:25:49 PM) sgallagh: I expect them to change markedly once the whole WG is hacking at it (12:26:41 PM) sgallagh: smooge: Sorry, could you rephrase that? I'm not sure what statement you are making. (12:26:58 PM) smooge: as in if the Impact was "End World Hunger" but all the items on the left were unable to make that happen.. how do you go with "Ok I have N inputs, what can I do with that to and how do I change End World Hunger to End Hunger on my street" (12:27:39 PM) sgallagh: I'm still not quite following. (12:27:49 PM) sgallagh: Inputs isn't "what I have". It's "what I need" (12:28:51 PM) smooge: ok. so I normally deal with "what I have" because I never have "what I need" (12:28:52 PM) sgallagh: If you don't have what you need when you get down to that point, then it's time to consider new Outputs, probably. (12:29:28 PM) sgallagh: Right, and that's probably the easiest place to get confused. 12:30 (12:30:12 PM) sgallagh: in this model, planning always moves right to left. If you get to the end and discover that "what I need" doesn't match "what I have", you either need to acquire what you don't have, reconsider what you need, or change what you plan to deliver. (12:30:22 PM) sgallagh: The model will iterate in that case (12:32:37 PM) sgallagh: smooge: Do you understand, or am I being obtuse? (12:32:53 PM) smooge: no I believe I understand. (12:33:32 PM) smooge: I am mostly writing and then rewriting responses because my brain is picking apart the framework for not covering all the counterpoints it keeps coming up with (12:33:48 PM) smooge: and I am telling myself that a response isn't needed to do that (12:34:18 PM) smooge: it is just a framework to get discussion going not a framework like ruby on rails that I am depending my website on (12:34:45 PM) sgallagh: yes, exactly. 12:35 (12:35:02 PM) sgallagh: It's something we can point to later every time someone says "What if we did X?" (12:35:18 PM) smooge: so my silence is me typing stuff and then going and saying that sentence was not going to be helpful.. retype, retype (12:35:56 PM) smooge: versus me not paying attention. (12:36:26 PM) sgallagh: I wasn't making any accusations. I was mostly just hoping I wasn't talking over you :) (12:36:54 PM) smooge: soryr I didn't feel like you were... I was being quiet a lot when you were waiting for things (12:37:10 PM) sgallagh: What responses were you thinking, though? (12:37:34 PM) menantea is now known as menantea_away (12:37:42 PM) sgallagh: I mean, your last point is correct; it's meant for framing the discussion, not for deciding specific technical actions. (12:38:13 PM) sgallagh: smooge: For another example, mattdm used this one at Flock: https://mattdm.fedorapeople.org/treklogicmodel.png (12:39:01 PM) smooge: well most of problems with it are the lack of feeding stuff you find from the left back into the right. You waterfall into the top and work down to the bottom over and over again 12:40 (12:40:11 PM) sgallagh: Right, but that's very intentional. (12:40:30 PM) sgallagh: If the stuff you find in the left doesn't already match something that you're trying to achieve, it's *probably* noise (12:40:57 PM) sgallagh: And if it's revealing something you *should* be trying to achieve, then it makes sense to go through the revision process to include it (12:41:00 PM) sgallagh: (IMHO) (12:43:47 PM) smooge: school calling. i am on phone (12:44:47 PM) sgallagh: smooge: Unless you have other questions, I think we're done for now. 12:45 (12:45:00 PM) sgallagh: Do you mind if I post this discussion to the server@ list for anyone else who is interested? (12:45:19 PM) smooge: no problems on my part (12:45:35 PM) sgallagh: OK, thanks

1 0

Agenda for 2016-08-30 Meeting
by Stephen Gallagher 29 Aug '16

29 Aug '16

I was hoping we'd have more movement on the PRD/KLM discussion here on the list, but since it hasn't happened, I think we should move the Logic Model discussion over to the meeting tomorrow. Any other topics for this week's meeting? Reminder: the meeting time has moved five hours later in the day, to 4pm US/Eastern.

2 1

Updated Invitation: Fedora Server Working Group Meeting @ Tue Aug 30, 2016 4pm - 5pm (EDT) (sgallagh@redhat.com)
by Stephen Gallagher 29 Aug '16

29 Aug '16

This event has been changed. Title: Fedora Server Working Group Meeting New meeting time starting 2016-08-30 (changed) When: Tue Aug 30, 2016 4pm – 5pm Eastern Time (changed) Where: #fedora-meeting-1 Calendar: sgallagh(a)redhat.com Who: * Stephen Gallagher - organizer * server(a)lists.fedoraproject.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=X2M0cmowcDlqNzBwamViY… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account server(a)lists.fedoraproject.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Proposal: for F26, move Cloud Base Image to Server WG
by Matthew Miller 28 Aug '16

28 Aug '16

We've talked about this for a while, but let's make it formal. The plan is to transition from Cloud as a Fedora Edition to Something Container Clustery (see https://fedoraproject.org/wiki/Objectives/ProjectFAO) But, we still need cloud as a _deploy target_. The FAO-container-thing will continue to have cloud image deploy targets (as well as bare metal). I think it makes sense to _also_ have Fedora Server as a cloud deploy target. This could possibly be both a Fedora Server Minimal Cloud Image and Fedora Server Batteries Included Image — but that'd be up to Server WG, I think. Overall, I'm proposing: 1. Dissolve Cloud WG (See below; don't panic) 2. Form new Atomic WG or FAO WG (name to be bikeshedded) (a lot of overlap in membership with current Cloud WG, of course!) 3. _Keep_ Cloud SIG as a gathering point around cloud technology and covering shared underlying technology (fedimg, koji cloud image production, autocloud). Think of this as analogous in some ways to something like the ARM SIG. 4. Change https://getfedora.org/cloud/ to https://getfedora.org/atomic/ or https://getfedora.org/fao/ 5. Create new http://cloud.fedoraproject.org/ in the same style as https://arm.fedoraproject.org/ 6. New Atomic/FAO WG produces Whatever New Deliverable (starting with Two Week Atomic) 7. Cloud Base Image becomes base (uh, see what I did there?) for new Fedora Server cloud image (or images). 8. Vagrant image _probably_ the same — or maybe becomes its own thing? 9. ??? 10. Profit! -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

7 15

Server SIG Weekly Meeting Minutes (2016-08-23)
by Stephen Gallagher 23 Aug '16

23 Aug '16

=================================================================== #fedora-meeting-1: Server Working Group Weekly Meeting (2016-08-23) =================================================================== Meeting started by sgallagh at 15:00:55 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-23/serversig.201… . Meeting summary --------------- * Roll Call (sgallagh, 15:01:15) * Agenda (sgallagh, 15:05:12) * Agenda Item: Open Seats (sgallagh, 15:05:12) * Agenda Item: New Meeting Time (sgallagh, 15:05:12) * Agenda Item: Fedora 25 Talking Points (sgallagh, 15:05:12) * Agenda Item: Server SIG PRD (sgallagh, 15:05:12) * Open Seats (sgallagh, 15:06:36) * danofsatx and hanthana did not respond to queries to retain their seat on the Server Working Group (sgallagh, 15:07:26) * AGREED: smooge (Stephen Smoogen) is elected to serve on the Server Working Group (+5, 0, -0) (sgallagh, 15:16:48) * LINK: https://fedorahosted.org/dell-config-cluster/ and https://fedorahosted.org/dell-satellite-sync/ though Dell has now taken them both over (vvaldez, 15:21:02) * LINK: https://github.com/vvaldez (vvaldez, 15:22:22) * AGREED: vvaldez (Vinnie Valdez) is elected to serve on the Server Working Group (+5, 0, -0) (sgallagh, 15:27:54) * New Meeting Time (sgallagh, 15:28:04) * Proposal: Server SIG meeting time moves to Tuesdays at 4pm US/Eastern (following US DST) (sgallagh, 15:31:53) * AGREED: Server SIG meeting time moves to Tuesdays at 4pm US/Eastern (following US DST) (+6, 0, -0) (sgallagh, 15:36:27) * This meeting time goes into effect on 2016-08-30 (sgallagh, 15:36:50) * Fedora 25 Talking Points (sgallagh, 15:37:14) * Talking Point: Fedora Server 25 now ships Node.js 6.x (sgallagh, 15:42:02) * LINK: https://fedoraproject.org/wiki/Fedora_24_talking_points#Fedora_Server says no (sgallagh, 15:43:25) * Cockpit in Fedora 25 now has an SELinux Troubleshooter module (sgallagh, 15:44:29) * Cockpit in Fedora 25 can display host SSH keys in the system dashboard (sgallagh, 15:44:54) * Cockpit in Fedora 25 will include support for network teaming, docker volume and storage management as well as the creation of systemd timer units (sgallagh, 15:46:35) * DOCKAH DOCKAH DOCKAH (adamw, 15:46:38) * Cockpit will also support multi-step (incl. 2FA) authentication in Fedora 25 (sgallagh, 15:47:05) * LINK: http://dockah.dockah.dockah.com/ (mhayden, 15:47:14) * Fedora 25 will ship with Docker 1.12 (sgallagh, 15:49:59) * Non-server-specific: Fedora 25 will remove support for weaker (1024-bit) certificate authorities (sgallagh, 15:50:42) * FreeIPA may or may not deliver version 4.4 in Fedora 25. Needs discussion as it missed Alpha. (sgallagh, 15:51:25) * Server SIG PRD (sgallagh, 15:56:47) * Out of time in the meeting, will be discussed on the server(a)lists.fp.o mailing list (sgallagh, 15:57:02) * Open Floor (sgallagh, 15:57:06) Meeting ended at 16:00:28 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * sgallagh (102) * zodbot (19) * vvaldez (19) * mhayden (15) * adamw (14) * mjwolf (9) * nirik (8) * bconoboy_ (3) * smooge (0) * dperpeet (0) * jds2001 (0) * danofsatx (0) * hanthana (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Requests for Server SIG agenda (2016-08-23)
by Stephen Gallagher 23 Aug '16

23 Aug '16

First order of business will be addressing the open seats; as of right now, neither Dan Mossor (danofsatx) nor Danishka Navin (hanthana) have replied to the "continued interest" thread, so it is likely that both of their seats will be up for consideration. At present, we have at least one self-nomination for an open seat: Stephen Smoogen (smooge). It was unclear to me whether any of the other respondents to the WhenIsGood were self-nominating. Once the seats are decided, we will pick our new meeting time. Right now, the optimum time would appear to be 1500 US/Eastern (1900 UTC) on either Tuesdays or Thursdays which would accommodate everyone who replied except for linuxmodder (sorry, Corey). I'll express a slight preference to taking the Tuesday slot, as it gives us a last chance to discuss things before Go/No-Go meetings at the various Fedora milestones. If anyone else would like to raise an agenda item for tomorrow's meeting, please speak up.

7 8

Invitation: Fedora Release Tools Demo (Live Broadcast) @ Tue Aug 23, 2016 12pm - 1pm (EDT) (acarter@redhat.com)
by Amanda Carter 19 Aug '16

19 Aug '16

You have been invited to the following event. Title: Fedora Release Tools Demo (Live Broadcast) Hangout: https://plus.google.com/events/c01barsqi2mg2bb7qsihbntbj5c The hangout will be broadcast live & posted: http://www.youtube.com/watch?v=3lM9E9WBmU4 Q&A - fedora-meeting-1(a)irc.freenode.net -- Purpose: The purpose of a demo is to show our stakeholders what we completed this iteration, get feedback from them about the changes & set some context and expectation with them about our direction. Demo agenda & previous demos can be viewed here: http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tool… Highlights today: https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-too… When: Tue Aug 23, 2016 12pm – 1pm Eastern Time Where: Hangout on Air / YouTube live stream Calendar: acarter(a)redhat.com Who: (Guest list is too large to display) Event details: https://www.google.com/calendar/event?action=VIEW&eid=bzE5MWs3OWtzNWc0NjFkY… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account server(a)lists.fedoraproject.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Server WG self-nomination
by Stephen John Smoogen 16 Aug '16

16 Aug '16

I read Stephen J Gallagher's self-nomination for one of the 2 open seats and I would like to nominate myself for one of the seats. My name is Stephen Smoogen and I work in Fedora Infrastructure. I have worked for Red Hat now for 11 years and have supported various Unix and Linux servers for 24 years. My focus is on how Small/Medium Site system administrator runs systems versus a Large Installation System Administrator. -- Stephen J Smoogen.

2 2

Minutes from Server SIG meeting 8/16/2016
by Jon Stanley 16 Aug '16

16 Aug '16

Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-16/serversig.201… ====================================================== #fedora-meeting-1: Server Working Group Weekly Meeting ====================================================== Meeting started by jds2001 at 15:09:48 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-16/serversig.201… . Meeting summary --------------- * Roll Call (jds2001, 15:09:49) * sgallagh nomination to WG (jds2001, 15:18:22) * dperpeet nomination to WG (sgallagh, 15:26:24) * AGREED: dperpeet appointed to WG (jds2001, 15:33:35) * meeting time (jds2001, 15:34:37) * Please respond to the WhenIsGood request so we can find a new meeting time (sgallagh, 15:42:44) * WG Interest Recertification (sgallagh, 15:47:51) * ACTION: sgallagh to send a reminder email about WG interest and CC members directly. (sgallagh, 15:52:20) Meeting ended at 15:59:45 UTC. Action Items ------------ * sgallagh to send a reminder email about WG interest and CC members directly. Action Items, by person ----------------------- * sgallagh * sgallagh to send a reminder email about WG interest and CC members directly. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jds2001 (53) * sgallagh (47) * zodbot (15) * mhayden (12) * adamw (8) * nirik (7) * dperpeet (6) * mizmo (5) * bconoboy (4) * vvaldez (3) * jkurik (2) * mjwolf (1) * danofsatx (0) * hanthana (0) * ]mhayden (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Server SIG Meeting Time
by Stephen Gallagher 16 Aug '16

16 Aug '16

A number of the sitting WG members have a conflict at the current meeting time, so I think now is probably a good time to run a WhenIsGood to find a new weekly meeting time. I've set one up, so please chime in. http://whenisgood.net/8bc83ek

1 0

unsubscribe
by Vikram Goyal 16 Aug '16

16 Aug '16

unsubscribe

2 1

Server WG self-nomination
by Stephen Gallagher 15 Aug '16

15 Aug '16

Currently, there are at least two open seats on the Server Working Group (formerly filled by Simo Sorce and Stef Walter). I would like to self-nominate to rejoin the Server WG and take one of those open seats. I left the Working Group several months ago due largely to a change in my job responsibilities at Red Hat. However, I am now making another internal move and will again have a large slice of time to allocate to the Fedora Server Edition. In particular, my day job will now be working as part of the Modularity and Base Runtime groups at Red Hat, and as such I would like to focus my efforts in Fedora Server towards delivering a fully modular Fedora Server Edition functioning as the reference implementation of this technology for the rest of the Fedora Project. Thank you for considering my application.

2 2

Future of the server WG
by Jon Stanley 12 Aug '16

12 Aug '16

I’m quite concerned about the status of the Fedora Server Working group after the departure of Stephen - he provided excellent leadership and is definitely missed from the working group. However, things seem to have fallen by the wayside since his departure. Perhaps the members that are at Flock can meet and hammer out what the future of the working group should be. From my perspective, there are a few things: We need to be a viable upstream for some of our downstream derivatives, and be a thought leader for what folks want to see there. I know that this can be a little controversial among some people, but we cannot ignore the fact that we are the upstream of one of the major Linux server vendors in the world. It would be foolish of us to do so. More than that, we need to be a fountain of innovation in the server ecosystem - regardless of what our downstream constituents want or are paying for. I think that RoleKit is a good example of this. It started as something that our downstream wanted and funded. They then changed their mind on that for reasons that I’m not privy to, but the work has continued, albeit slower. We need to decide what our deliverables are going to be. The cloud working group has shifted towards a minimal OS and containers as the solution. Is this something that we should adopt, and deliver the best containers that there are for various server roles? Is the deliverable something else entirely? Do we stay the course that we have been of producing a general purpose OS with some tweaking? I’d like to see the server product be differentiated from a “choose your own adventure” system that anyone can build today, but be something with some thought behind the integration of various components and making sure that things work well together. Is there room for the “choose your own adventure” course? Of course - some people will choose that. We need to go back to the initial PRD (https://fedoraproject.org/wiki/Server/Product_Requirements_Document) that the working group was formed with and see if it’s still valid and viable, or if we need to change it, and if so in what way? What does that lead to in terms of deliverables? I’m willing to help with some of this work, but I cannot lead it since I’m busy with $DAYJOB, but I’ll help in absolutely any way that I’m able to.

14 36

Cockpit 0.117
by Stef Walter 11 Aug '16

11 Aug '16

A summary of the Cockpit weekly release. There’s a new release every week, although it's been a month since the release notes were posted. Here are the highlights from this weeks 0.114 through 0.117 releases. Configure volumes and environment for a Docker container -------------------------------------------------------- Vanlos Wang implemented support for configuring volumes and environment variables when running a container in the Cockpit UI. This allows you see what environment variables and volumes an image is pre-configured to have. It then allows the user to define additional environment variables and volumes for the new container, and then commit those changes to a new image if desired. Video: https://youtu.be/l9E78Uevg00 Change: https://github.com/cockpit-project/cockpit/issues/4506 Setup container and image storage --------------------------------- Marius worked with Dan Walsh and and others to implement a UI for configuring the Docker container and image storage pool. It's now easy to add additional disks or storage to that pool, or reset it to a clean state. On some operating systems like Atomic Host, this storage pool is present by default, and elsewhere this container storage pool can be set up. Relatedly on the command line, checkout the new "atomic storage" sub-command which does the same configuration tasks, that previously had to be configured with arcane configuration files. Video: https://youtu.be/l9fmMa5WJMk Change: https://github.com/cockpit-project/cockpit/pull/4350 Change: https://github.com/projectatomic/atomic/pull/373 Change: https://github.com/projectatomic/docker-storage-setup/pull/135 ... Support for Network Teaming ---------------------------- Marius also added support for configuring network teaming to Cockpit. Network teams are similar to network bonds, in that they combine two network interfaces into one, and involve failover or load balancing modes. But teams have more robust terminology and implementation. Since teams are a server side feature, this will replace the functionality for defining teams in Linux Desktop control center applications. Support for configuring bonds in Cockpit will remain for the time being until the team support can be relied upon to completely replace that functionality. Both NetworkManager and Cockpit are involved in this. Here's a video demoing the changes: Video: https://youtu.be/-sob1W33Xus Change: https://github.com/cockpit-project/cockpit/pull/4571 Pulling images without authentication from the Openshift Registry ----------------------------------------------------------------- The Openshift image registry now supports pulling images without first logging in. It can be configured to allow this on a per-project basis. This allows images to be shared from the registry with a broader audience of developers or image consumers, such as scripts. Aaron Weitekamp worked on adding support the Registry console to configure projects to allow pulling images without authentication. Here's a video of those changes: Video: https://youtu.be/fpsvtq5hENk Change: https://github.com/cockpit-project/cockpit/pull/4791 Don't allow formatting extended partitions ------------------------------------------ Cockpit no longer erroneously allows formatting certain partitions, such as extended partitions containing other logical partitions. Change: https://github.com/cockpit-project/cockpit/pull/4823 Test every change on CentOS --------------------------- Cockpit runs all its tests suites against code before that code is merged, much less becomes part of a release. This isn't just unit tests, but integration booting of RHEL, Debian, Fedora and Atomic machines. We now added CentOS to that list. We now boot CentOS 7.x instances many hundreds of times a day to test aspects of the system, and how Cockpit and a given pull request interact with it. Change: https://github.com/cockpit-project/cockpit/pull/4689 Show SSH host keys and machine ID --------------------------------- Peter changed the main system info page to shows the local machine ID for easy access. You can also see the fingerprints of all the SSH host keys. These are the fingerprints that you would be expected to recognize and/or add to the "known_hosts" file when accessing the machine over SSH. Screenshot: http://cockpit-project.org/blog/images/cockpit-ssh-host-keys.png Change: https://github.com/cockpit-project/cockpit/pull/4310 Red Hat subscription registration options ----------------------------------------- Dominik worked on the Red Hat subscriptions functionality. You can now specify an activation key when registering the system. This key is generated in your organization in such a way that it uniquely identifies when kind of software should be available on the system. You can now also specify an organization when registering the system. Change: https://github.com/cockpit-project/cockpit/pull/4722 Change: https://github.com/cockpit-project/cockpit/pull/4697 Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 0.117 is available in Fedora 24: https://bodhi.fedoraproject.org/updates/cockpit-0.117-1.fc24 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/0.117 Take care, Stef

1 0

Tomorrow's regularly scheduled WG meeting
by Jon Stanley 09 Aug '16

09 Aug '16

Unfortunately, I'm in Ansible training for $DAYJOB tomorrow - so I'll not be able to attend the meeting. I didn't mean to sound alarmist in my previous email, but rather to jumpstart a discussion that sorely needs to be had. Let's discuss that on the list at the very least, and if someone wants to head up a meeting and talk about it, I'll read the logs later :). -Jon

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server August 2016