Hi all,
I was thinking today that for Fedora 23 it would really cool to deliver a NAS
version of Fedora 23. I could see it being delivered in 2 formats.
1 an atomic based disk image. it could be preinstalled, you dd the image onto
a disk or a usb stick plug it in and boot, you could use initial-setup to set
a root password, set timezone etc, then use cockpit to manage and configure.
my thought here is that you could use a mirco-atx system with 4 or 6 sata
ports and you use all the disks for data and boot and run the system from a
small piece of media, 16 or 32G usb stick for instance. or even a beaglebone
black or similar arm based device with a attached usb disk
2 as a option you can select on a regular install.
The roles would be iscsi( or some other block device), nfs, smb/cifs. all
managed and configured using cockpit, a user could carve up the attached disk,
be able to alloacte nfs or smb/cifs or export some raw space as a block
device, for use in vms etc.
I know it is a pretty rough outline but figured I would get something out and
some discussion to see if what others thought. I think especially the atomic
version could be really useful. a very simple way to get some storage up and
running and use and keep it updated. especially long term, since going from
Fedora 23 to 24 should be a simple atomic update.
Regards
Dennis

So, given the discussion on the list about a NAS role, I think we have
a topic to discuss today as we plan the F23 release. Additionally, we
should follow up on the earlier topics of deciding on stable APIs and
gathering documentation.
Focus today should be on deciding our course and selecting a captain
for each major effort.
Agenda Topics:
* File-sharing Role
* Stable API Documentation
* Dependency Chain Reduction (if we have time)

Hi Server WG,
As part of the on-going Council updates, I'm organizing a Fedora
Engineering update. This includes the various WGs, rel-eng,
infrastructure, and a few others. The idea behind this is to give a
brief update of the work your group is doing towards the F23 and F24
releases. Think of this as a 5-10 minute "lightning talk" of the
highlights you want to see in those releases.
The meeting is July 7th. It would be excellent if you could have a
volunteer present the update for your group and stay around to answer
any questions. Worst case, please gather the information and send it
to me and I can do the overview, but representation from the group is
clearly preferred.
If you have questions, please let me know. The idea and format are
somewhat new, so we'll work through this as best we can.
josh

I noticed recently that the size of the Fedora Server DVD grew quite a
bit between F21 and F22, despite not really changing the requested
content. I've been trying to do a bit of analysis to see what packages
are pulling in huge numbers of dependencies.
For a first pass, I wrote a simple Python script to analyze the dep
chains of every package on the Fedora Server standard install and also
on the "full" install (clicking every optional component checkbox in
Anaconda). Right now, the output only shows which packages have the
largest *count* of dependencies (it doesn't dabble in installed size at
all), but it can give us an idea of which packages are pulling in the
most stuff and start focusing our efforts on breaking the dependencies.
So, for each of the output files, what you will see is the recursive
(non-repeating) count of the number of packages necessary to satisfy
the dependencies for every package on the system.
It's certainly worth mentioning that the "winner" is freeipa
(specifically, freeipa-server-trust-ad, which pulls in pretty much
everything else in the freeipa stack). With a little quick examination
though, one can also see that pki-ca (a dependency of FreeIPA) is sixth
from the top, so it's worth looking at whether any part of its chain
can be broken.
Anyway, enjoy this (mostly) raw data. I'll continue to process it and
see what else turns up.
Side-note: the two lists do not always have the same count for all
packages; I suspect that this is due to having multiple possibilities
to satisfy the same dependency, where one may be pulled in explicitly
during the maximal install where the despsolver might have chosen
another during the standard install.

We should have a release candidate for Fedora 22 sometime today.
Instead of having a meeting today, let's just all focus on running
through release validation if we can. We have a Go/No-Go meeting on
Thursday and I'd very much like to see us ship on time if at all
possible.
Reminder: Adam Williamson is on vacation this week, so it's up to all
of us to pick up the testing slack. I'll be doing my part. Please do
yours.

Hey all,
Have put up the page for talking points for this release:
https://fedoraproject.org/wiki/Fedora_22_talking_points
What we want to get to is a coherent story for Fedora 22 so marketing
can weave that into the beta and final announcements, plus Ambassadors
can use the talking points when they're at events (etc.), and for
anybody who's talking to press about the F22 release.
Cross-posting to working group lists to get feedback on the Cloud,
Server, and Workstation editions.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/

Hello Friends,
My name is Ramesh Basukala. I am currently employed at Dartmouth College,
Hanover, NH as a Linux Systems administrator. I have been using Fedora from
its initial release on my workstation, laptop and servers I manage. I
started using Linux from 2002. I use perl/python/bash for daily system
administration job and develop tools. I worked on various web development
projects using various tools/programming languages like php, jsp, html,
css, javascript to name few. I am always looking forward on contributing
open source community. I am excited to be part of fedora server community.
Thanks,
-Ramesh