After a round of bug reports and bug fixing I have a new pkgdb up in the
staging environment for testing. I do not know of any problems with this
version at the moment so I'd appreciate people who use the pkgdb to change
acls frequently or query it for data give it a try and see that everything
is working for them. If there's no reports of problems I'll be pushing this
to production soon. If I'm available for part of the weekend I'll push it
Friday. If not, I'll push it out on Monday.
A new python-fedora based on 0.3.16.90 which works with the new pkgdb will
be built and pushed into updates-testing at that time as well::
The first beta of the new PackageDB is running in our staging environment
All the features for 0.5.x should be present but there's definitely bugs to
be found in the implementation. When you across one, feel free to find me
on IRC to report it (abadger1999) or send email to me
toshio(a)fedoraproject.org. If it's not something that I feel will be fixed
for 0.5.0, I'll open a ticket on the fedorahosted trac instance for it.
URLs should no longer change position but a few minor changes in query
parameters may still occur. Many scripts may need to be updated for use
with the new version of the packagedb. I'd recommend taking this
opportunity to port to the python-fedora client library if at all possible
as I'll be maintaining the clientside API there for a while even if the
serverside changes. If you need additional serverside URLs wrapped in
python-fedora, let me know (code snippets welcomed) and I'll get them into
python-fedora for you.
The current python-fedora package, 0.3.16 works with what's currently in
production. I'm currently testing python-fedora-0.3.16.90 which works with
the version in staging. Depending on how many bugs are found and how
quickly they're squashed, I'll push python-fedora-0.3.17 or 0.3.18 with the
python-fedora-0.3.16.90 packages for F-11, F12, F-13, and EL-5 are available
They're signed with my personal gpg key.
So I'm just going to throw this out there. Anyone else think zabbix isn't
quite working out?
I ask because it seems like
A) we've been using zabbix for over a year and still haven't turned nagios
B) Even after using it this whole time, I often run into issues adding new
Am I alone in this? Anyone out there super happy with our zabbix install?
I love the results we get from it, but it feels like it's turning into a
I'm working on Zikula sysadminery for Fedora Insight. I'm trying to:
* Make sure stg.fedoraproject.org is updated with all the Zikula
* Update the How-to document to reflect;
* Create a [[Zikula Infrastructure SOP]] for handing Zikula instances;
** Or should this be an SOP per site? I.e., [[Insight Infrastructure
SOP]] and [[News Infrastructure SOP]] are different or all in a
We have some bits to make work in staging once we have the install
updated and running.
Right now stg.fedoraproject.org/insight is showing the install.php,
isn't working beyond a few steps, and ... shouldn't we just be
snapping live with data from the database?
And then there is the database dump and import from publictest6 ...
... and then we want to finish the last staging bits and go live in
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
Currently logs are 'shipped' to log01 which uses some syntactic magic
to put various logs into hostname appropriate directories.. eg logs
from xen10 go into /var/log/hosts/xen10/. However sometimes this does
not work correctly. hostnames are found via reverse lookups and if no
hostname is found then the IP address is found. So anytime there is a
DNS outage or problem, logs get shoved into directories like
In order to clean up the various spazes, I have moved all the files
into appropriate hostnames and made symbolic links so that IP address
points to hostname.
10.5.126.110 -> xen10
This fixes most of the problems except for some odd directories left
over: exiting, last, gconfd, Mailman, scratch, ServeRAID, syslogd, and
my favorite Rootkit
These are from malformed syslog packets where the ip address got
mangled. I am hoping by moving the boxes to tcp logging these will go
The final directory that is filled with various 'junk' is
/var/log/hosts/unused. Red Hat used a hosting convention that every
reverse IP address not set up is called unused. This means that if DNS
was not set up correctly for a host, it and every other server that
isn't set correctly is called unused. Depending on the month this
might have been 1-4 hosts. I think we are down to 2. After the freeze,
I am going to change the reverse names on 'unused' hosts to better
track this down in the future.
Other things left to do. We need a puppet scriptlet that links forward
and reverse DNS directories and keeps up with them somehow so that
various 1-10 minute poops don't spew logs everywhere again. Second.. I
start concatenating logs but found that htis was error prone as the
logs need to be date sorted as you might have logs going to xen10
direcotires, then 10.5.126.110, then xen10 and back again as whatever
problem fixed itself.
Stephen J Smoogen.
Ah, but a man's reach should exceed his grasp. Or what's a heaven for?
-- Robert Browning
I'd like to push out a new bodhi release everywhere as soon as possible.
This release contains a bunch of critpath/no frozen rawhide fixes,
enhancements (like a /critpath grid, JSON API, and `bodhi --critpath`
cli flag), along with fixes to a few annoying bugs. I've added over 30
unit tests since the last release, and have been hammering on this code
for a while now, so it should be quite stable.