FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 04-06-2012, 11:35 AM
Anthony Messina
 
Default Regular Koji cleanup

It was mentioned in
http://lists.fedoraproject.org/pipermail/buildsys/2012-April/003838.html
that some manual DB cleanup is in order from time to time.

I also run a private Koji instance and am wondering if there are other
regular maintenance activities that should be run other than those
provided by koji-gc and removing old scratch and work directories?

Are there other DB commands that should be run to keep things pruned down?

Thanks. -A

--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 04-09-2012, 05:17 PM
Mike McLean
 
Default Regular Koji cleanup

On 04/06/2012 07:35 AM, Anthony Messina wrote:

It was mentioned in
http://lists.fedoraproject.org/pipermail/buildsys/2012-April/003838.html
that some manual DB cleanup is in order from time to time.

I also run a private Koji instance and am wondering if there are other
regular maintenance activities that should be run other than those
provided by koji-gc and removing old scratch and work directories?

Are there other DB commands that should be run to keep things pruned down?


The sessions one is the only raw db command that I run regularly. I
really should automate that properly within Koji.


Apart from the things you listed, I believe the only other general
maintenance action I have is running the
prune-signed-copies subcommand nightly. Of course that only matters if
you are regularly generating signed copies.

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 04-09-2012, 05:26 PM
Anthony Messina
 
Default Regular Koji cleanup

On 04/09/2012 12:17 PM, Mike McLean wrote:
> On 04/06/2012 07:35 AM, Anthony Messina wrote:
>> It was mentioned in
>> http://lists.fedoraproject.org/pipermail/buildsys/2012-April/003838.html
>> that some manual DB cleanup is in order from time to time.
>>
>> I also run a private Koji instance and am wondering if there are other
>> regular maintenance activities that should be run other than those
>> provided by koji-gc and removing old scratch and work directories?
>>
>> Are there other DB commands that should be run to keep things pruned
>> down?
>
> The sessions one is the only raw db command that I run regularly. I
> really should automate that properly within Koji.
>
> Apart from the things you listed, I believe the only other general
> maintenance action I have is running the
> prune-signed-copies subcommand nightly. Of course that only matters if
> you are regularly generating signed copies.

Thanks, Mike. I've cobbled a 'koji-maint' Bash script together that
keeps things generally tidy and creates new repos using mash, etc. to
automate the Koji buildsys -> usable yum repo for a private Koji
instance: http://messinet.com/trac/browser/koji-maint/koji-maint

I'll probably add the db session cleanup to that as well.

Any recommendations for lookaside cache cleanup? I'm thinking that I'd
like to remove items from the lookaside cache once theyre removed from
Koji via kogi-gc.


Thanks. -A

--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 04-11-2012, 03:27 PM
Mike McLean
 
Default Regular Koji cleanup

On 04/09/2012 01:26 PM, Anthony Messina wrote:

Any recommendations for lookaside cache cleanup? I'm thinking that I'd
like to remove items from the lookaside cache once theyre removed from
Koji via kogi-gc.


You mean a dist-git lookaside cache? That would be a bit of a messy
problem since multiple builds might use the same source file and we
don't track that in the database.


If you want to do it as you've described, you'd need to maintain an
index and keep reference counts.


Otoh, if you're going to prune your lookaside cache at all, you might
just use a simpler test (perhaps a combination of timestamp and
latest-by-package-name). If this happens to delete a source file for a
non-deleted build in koji, then you can still recover that from the srpm
in koji if it becomes as issue.

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 07:15 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org