Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 81462 - RFE: Tool to aid in storage of kickstart RPMs on satellite servers
RFE: Tool to aid in storage of kickstart RPMs on satellite servers
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Mihai Ibanescu
Fanny Augustin
Depends On:
Blocks: 88391
  Show dependency treegraph
Reported: 2003-01-09 12:59 EST by Greg DeKoenigsberg
Modified: 2007-07-31 15:03 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-14 12:04:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Greg DeKoenigsberg 2003-01-09 12:59:16 EST
Customers want to use satellite servers as kickstart servers as well.  This is

Unfortunately, RPM duplication and disk space usage becomes a problem.  90% of
the RPMs in a given kickstart file tree will also be in the RPM repository for
the satellite.

To eliminate unnecessary duplication, we should have a de-duping copy function
for RPMs that might work something like this:

$ satcp /mnt/cdrom/filetree/*.rpm /var/www/pub/filetree/*.rpm

Before writing each RPM to disk, satcp would check the satellite repository.  If
an RPM with the same(ish) name and matching MD5sum exists, create a symlink
instead of copying the file.

We would then document the use of this satcp script in the satellite/kickstart
Comment 1 Mihai Ibanescu 2003-01-09 16:22:51 EST
Should be on my plate I guess.
Comment 2 Greg DeKoenigsberg 2003-02-03 09:52:53 EST
Bumping priority ("provisioning" implications)
Comment 3 Greg DeKoenigsberg 2003-04-11 10:53:02 EDT
RHN 3.0.0
Comment 4 Greg DeKoenigsberg 2003-04-14 12:04:43 EDT
Was apparently decided in my absence that this piece is out.  OK, then, out it
is.  And since this was a "stopgap" feature until we got "real" provisioning, we
should probably close this altogether.

Note You need to log in before you can comment on or make changes to this bug.