server August 2016

server@lists.fedoraproject.org

29 participants
18 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server August 2016