The Cloud SIG test day for Fedora 15 is will be this Thursday . The
focus will be on using BoxGrinder  and Amazon Elastic Compute Cloud
(EC2)  with Fedora 15.
BoxGrinder is "a set of projects that help you grind out appliances for
multiple virtualization and Cloud providers." Another way to put it is
that BoxGrinder makes it easy to create and deploy custom installations
of Fedora, Red Hat Enterprise Linux or CentOS to your favorite KVM, Xen
or VMWare based clouds. This includes private clouds and EC2.
Live images, prebuilt EC2 amis and meta-appliances  will be available
on the test day if you don't already have Fedora 15 installed. Detailed
instructions for how to test are available on the wiki .
There are test cases for BoxGrinder that can be run without an AWS
account for EC2 but testing on Amazon's infrastructure and other cloud
providers (BoxGrinder also supports ElaticHosts, SKALI Cloud, Open
Hosting and Serverlove) would be very much appreciated.
Get ready for some cloudy good-ness and please help test if you have the
test-announce mailing list
I'm looking for someone to take ownership of the getmail package.
It's a small but very stable python application with barely any need for
Nevertheless I can't find the time for it anymore, and if nobody is
interested to take over, it will be orphaned.
For many years Fedora infrastructure has been running a
talk.fedoraproject.org asterisk server. This allows contributors to
talk to each other, or send voice mails, etc.
However, it gets very very little usage and also has no one really
maintaining it or fixing issues with it. In the last 130days there have
been a total of 95 calls using the server. There are a number of
outstanding infrastructure tickets on the service that no one has dealt
with. The server running it is running an outdated OS version and
So, we are going to retire the service on 2011-05-05.
Now, some of you might say: “But I want to use it! what can I do to
save it?” First, as it is now, it’s a waste of a server instance to run
something 24×7 that only processes 1 call every few days. Any plan to
continue the service would HAVE to include some way to increase usage
of the service to make it worth doing. There would also need to be a
group of folks who would help fix issues, enhance the service, help
with updates and so on. A single interested person would be a single
point of failure. If such a group forms and has a plan, please bring it
to the infrastructure list/meetings.
Recently, I noticed that my system does not want to shutdown properly.
I suspect that this has something to do with systemd v25. Anyone
noticed this problem? The last message that appears on shutdown is
"Stopped SYSV: PostgreSQL database server..".