Skip to main content

Offline content for non-standard packages (Satellite, Repo, etc..)

EDIT:  This explains how you could have offline content of specific packages.

You could potentially do the following:
* retrieve the repo file for the files you want to retrieve
* place the repo file in /etc/yum.repos.d/ and make sure enabled=0 (otherwise your host will try to use that repo for updates)
* create an excludepkgs and includepkgs directive in your repo file
* run reposync and identify the repo you just created
* bonus: you could run createrepo (which would create the repomd.xml file and all)
* place the entire repo on some media that you can attach to your server

Repo File (I use this to ONLY grab a few asm files - not the entire repo - hence the include/exclude)
/etc/yum.repos.d/oracle.repo
~~~
[ol6_latest]
name=Oracle Linux 6 Latest (x86_64)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=0
exclude = *xen*
includepkgs = oracleasm*el6.x86_64 oracle-validated-* oracleasmlib* cvu* kmod-oracleasm*
excludepkgs = oracleasm-2.6*.ol6xen* oracleasm-2.6.*.ol6debug* oraclelinux-release* oracle-logos* oracle-rdbms*
includepkgorder = excludepkg,includepkg
~~~

~~~
SWBASE=/var/satellite/repos/
ARCH=x86_64
REPOID=ol6_latest
PKGDIR=${SWBASE}/${ARCH}/${REPOID}

reposync -q -n -a $ARCH --repoid=${REPOID} -p ${SWBASE}/${ARCH}/ # > /dev/null 2>&1
cd $PKGDIR
createrepo $PKGDIR

tree /var/satellite/repos/x86_64/ol6_latest/

/var/satellite/repos/x86_64/ol6_latest/

|-- getPackage
|   |-- kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm
|   `-- oracleasm-support-2.1.8-1.el6.x86_64.rpm
`-- repodata
    |-- filelists.xml.gz
    |-- other.xml.gz
    |-- primary.xml.gz
    `-- repomd.xml

~~~

I pulled this from a script that I use to do many things, but I think all the pieces are there.

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.