Fwd: Re: Fedora Server PRD Draft and call for participation
by Joe Brockmeier
FYI - we had a bit of interaction on the cloud/server responsibilities,
etc. yesterday, it might be worthwhile for the cloud WG folks to take a
minute and look this over and make sure we also understand what the
server WG has here.
-------- Original Message --------
Subject: Re: Fedora Server PRD Draft and call for participation
Date: Wed, 15 Jan 2014 08:21:07 -0500
From: Stephen Gallagher <sgallagh(a)redhat.com>
Reply-To: server(a)lists.fedoraproject.org
On 01/10/2014 03:05 PM, Stephen Gallagher wrote:
> The first deliverable that the Fedora Server Working Group was
> tasked with was the production of a Product Requirements Document.
> This document is intended to provide a high-level view of the goals
> and primary deliverables of the Fedora Server distribution. A great
> deal of discussion has gone on during the weekly Working Group
> meetings as well as on the mailing list.
>
> At this time, the deadline for the delivery of the PRD is rapidly
> approaching. Originally it was due to be delivered for ratification
> on Monday, January 13th, but at the FESCo meeting on Wednesday, it
> was agreed to delay this deadline by a single week. The primary
> reason for this delay was so that the Fedora Cloud and Fedora
> Server groups could have some last discussions about overlap and
> respective areas of responsibility.
>
> This past Tuesday, we had an all-day PRD hackfest in IRC and have
> come up with a fairly strong draft[1]. It is not yet complete
> (notably, there remains a FIXME under "Misc. Concerns" and some
> ambiguity around the Use Cases), but I believe that it is close
> enough to its final form (as envisioned by those people that have
> contributed to it), that we should expose this document to the
> wider world and ask for input before submitting it to the Fedora
> Engineering Steering Committee and Fedora Advisory Board a week
> from Monday.
>
> Please read through the PRD draft and provide feedback of any sort.
> If you see that we have missed or misrepresented any of our
> statements, we would very much like to hear this soon.
>
> [1]
> https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_D...
The
>
draft document has been updated with all changes proposed at the
Working Group meeting yesterday and is now presumed to be effectively
complete.
I respectfully request that all members of the Server Working Group
(CCed) respond with an approval vote, or if they feel something
requires changing, please describe it in detail.
Given that we must submit this to FESCo and the Board by Monday, I am
setting a hard deadline on Friday at 1600 UTC for votes.
_______________________________________________
server mailing list
server(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/server
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
10 years, 3 months
Reminder + agenda for tomorrow's (1/15/2014) meeting
by Sam Kottler
Following is the list of topics that will be discussed in the cloud WG meeting Wednesday at 17:00 UTC in #fedora-meeting-1 on irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2014-1-15 17:00 UTC'
= New business =
* Determine items that need cross-WG coordination from the PRD and assign people to lead discussions
* Talk about release engineering work needed over the next few months to get F21 cloud deliverables completed
Anything else we want to cover from the PRD that will need attention ASAP for F21?
= Followups =
* PRD recap and discuss any remaining work
If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/cloud, or bring it up at the end of the meeting during the open floor.
-Sam
10 years, 3 months
F20 Kernel recompile for Google Cloud
by Michael Hall
Hi I hope this is the appropriate forum for my question.
I am recompiling a F20 kernel as part of preparing a custom image for use
on Google Cloud.
I wish to build a minimal nginx+node.js+mondodb server image.
I am attempting to compile an image in accordance with Google's
recommendations here:
https://developers.google.com/compute/docs/building-image#providedkernel
Apart from Google's recommendations, there seem to be a large number of
other features that could/should be disabled.
Is there an existing guide anywhere as to how much useless stuff can be
safely disabled in the kernel in this use case?
Thanks
Mike
10 years, 3 months
Vagrant in Fedora
by Alex Drahon
Hi all,
I wanted to give an update on the status of Vagrant in Fedora 20, I just realised it's my first post to the list so I'll take this opportunity to introduce myself. I'm Alex, I work at Red Hat as a Solution Architect (ie. nothing engineering related), I wrote the vagrant-kvm plugin on my spare time to make it work on my Fedora laptop, though there's now a (much more qualified) second maintainer who is also providing support for Ubuntu through a PPA. Matthew asked me if I wanted to work on packaging Vagrant and the KVM plugin for Fedora 20, and I foolishly accepted ;)
It's quite exhilarating having the opportunity to contribute to Fedora, and at the same time I feel totally lost. I don't mean this as a criticism, it's just this "first week at school" feeling, it will take me some time to get an idea of how things work. That said, here's the Vagrant situation:
1. I have a vagrant RPM that installs and works as expected, there's some minimal patching involved which has to do with the fact that Vagrant expect to be running in it's own Ruby 1.9.3 environment in /opt
2. There was also some patching involved to make the plugin system work, although I haven't tested plugins extensively (some stuff breaks like rubygems loading path) and providing common plugins as RPMs looks like the better way in Fedora.
3. I had to build my own rubygems-childprocess (current Fedora package is very old) and rubygems-log4r (not provided in Fedora) RPMs, but I don't know how I should submit them (package review ticket?). There's a existing ticket for log4r https://bugzilla.redhat.com/show_bug.cgi?id=905240 , I added it as a dependency to the Vagrant ticket.
4. I've packaged vagrant-kvm as a RPM and it installs, but I'm running into serious issues with Policykit. I don't think I'll be able to solve that without help, I'm not even sure what's the right way to do it.
So, as a summary:
- yum install vagrant should work, at which point you need to install VirtualBox and it will run as expected
- vagrant-kvm installs but I don't know how to add the right polkit rules (I need help)
Looks pretty good, right?
Alex
10 years, 3 months
Cloud SIG discussion on centos-devel
by Rich Bowen
There's a conversation going on on the centos-devel mailing list
http://lists.centos.org/mailman/listinfo/centos-devel regarding the
creation of a Cloud SIG. I wanted to mention it here because I know that
there are folks here that 1) would have opinions about how this might be
accomplished and 2) have a lot of experience with doing this already at
Fedora, and might help us avoid pitfalls, and also help us move faster
to things that you've already solved.
I'd appreciate anyone jumping in over there who is interested in this
effort. Thanks.
--Rich
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 3 months
PRD to-do list
by Matthew Miller
Okay, so, we've got some more to do here. :)
I think we're pretty good down to section 3, User Profiles. We put a lot of
work into that last week and they're looking good too but we need some
finish work. Going over those and adding polish would be great. And if
anyone feels like formatting them to match
http://fedoraproject.org/wiki/Server/Personas.... :)
The primary use case list is also starting to look good, but each could be
fleshed out. Also, it is kind of a grab bag, and we have to decide if
_these_ are the ones we want. A couple of these are rather specific in
technology but don't actually describe use (Docker and OpenShift) and maybe
those are actually better later on.
And then as we get further down the document, it all kind of falls apart.
There's a whole blank "Features" section, for example.
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
10 years, 3 months
PRD Hackfest on 8 January 2014
by Joe Brockmeier
The following meeting has been modified:
Subject: PRD Hackfest on 8 January 2014
Organizer: "Joe Brockmeier" <jzb(a)redhat.com>
Time: Wednesday, January 8, 2014, 8:00:00 AM - 12:00:00 PM GMT -06:00 US/Canada Central [MODIFIED]
Invitees: server(a)lists.fedoraproject.org; cloud(a)lists.fedoraproject.org
*~*~*~*~*~*~*~*~*~*
Argh. Resending with appropriate date. Sorry folks!
Per previous discussion, posting a calendar invite for anyone that wants to join in the "hackfest" on Wednesday, from 14:00 UTC to 18:00 UTC.
Best,
jzb
10 years, 3 months
PRD Hackfest on 8 January 2014
by Joe Brockmeier
The following is a new meeting request:
Subject: PRD Hackfest on 8 January 2014
Organizer: "Joe Brockmeier" <jzb(a)redhat.com>
Time: Monday, January 6, 2014, 2:00:00 PM - 6:00:00 PM GMT/UTC Coordinated Universal Time
Invitees: server(a)lists.fedoraproject.org; cloud(a)lists.fedoraproject.org
*~*~*~*~*~*~*~*~*~*
Per previous discussion, posting a calendar invite for anyone that wants to join in the "hackfest" on Wednesday, from 14:00 UTC to 18:00 UTC.
Best,
jzb
10 years, 3 months
ANNOUNCE: Oz 0.12.0 release
by Chris Lalancette
All,
I'm pleased to announce release 0.12.0 of Oz. Oz is a program for
doing automated installation of guest operating systems with limited
input from the user. Release 0.12.0 is a bugfix and feature release
for Oz. Some of the highlights between Oz 0.11.0 and 0.12.0 are:
* Fixes to concurrent oz-install invocations
* Python 3 compatibility in the test suites
* Support for Ubuntu 12.04.3
* Support for Mageia
* Allow a MAC address to be passed in (instead of auto-generated)
* Support for RHEL5.10
* Support for Ubuntu 13.10
* Use lxml instead of libxml2 for XML document processing (it has much
better error messages)
* Remove the unused "tunnels" functionality
* Support FreeBSD 10.0
* Remove deprecated functions from the Guest class
* Speed up guest customization on guests that support NetworkManager
* Follow subprocess commands as they are executed (makes debugging easier)
* Ensure that any paths from the user are absolute, otherwise things
don't work properly
* Add support for OpenSUSE 13.1
* Add support for Fedora 20
* Add support for RHEL-7
A tarball and zipfile of this release is available on the Github
releases page: https://github.com/clalancette/oz/releases . Packages
for Fedora-19, Fedora-20, and EPEL-6 have been built in Koji and will
eventually make their way to stable. Instructions on how to get and
use Oz are available at http://github.com/clalancette/oz/wiki .
If you have questions or comments about Oz, please feel free to
contact me at clalancette at gmail.com, or open up an issue on the
github page: http://github.com/clalancette/oz/issues .
Thanks to everyone who contributed to this release through bug
reports, patches, and suggestions for improvement.
Chris Lalancette
10 years, 3 months
