Downloading a Debian 5.0 repo with Cobbler
by Michael Saverino
Here is a resend of my post from a few days ago.. It somehow got mangled into an html document nobody could easily read on the list:
I have been trying to download and import a Debian 5.0 repository as per the instructions on this page:
https://fedorahosted.org/cobbler/wiki/DebianDeployment
I define the environment variables and execute the command as shown... First error is that cobbler states that --os-version is no longer a valid option. So I proceed by removing that option and rexecuting with the resulting following error:
[saverino@ln22ms ~]$ arch=i386
[saverino@ln22ms ~]$ dist=lenny
[saverino@ln22ms ~]$ hostname=ftp.es.debian.org
[root@ln22ms saverino]# cobbler import --name=${dist}-net --breed=debian --arch=${arch} --mirror=rsync://${hostname}/debian/dists/${dist}/main/installer-${arch}/current/images/netboot/debian-installer/${arch}
/usr/lib/python2.6/site-packages/Cheetah/CacheRegion.py:30: DeprecationWarning: the md5 module is deprecated; use hashlib instead
import md5
- rsync -a 'rsync://ftp.es.debian.org/debian/dists/lenny/main/installer-i386/current/...' /var/www/cobbler/ks_mirror/lenny-net-i386 --exclude-from=/etc/cobbler/rsync.exclude --progress
receiving incremental file list
sent 169 bytes received 529 bytes 279.20 bytes/sec
total size is 7542574 speedup is 10805.98
---------------- (adding distros)
No distro signature for kernel at /var/www/cobbler/ks_mirror
I get the same result with cobbler under Fedora 10 or Fedora 11 (all updates applied). Any advise on what may be causing the problem would be appreciated.
Many Thanks,
Mike...
14 years, 8 months
How to you manage yum and package "workflow" ?
by Michael DeHaan
I'm curious if anyone out there uses (or does not use!) a workflow where
they might have some packages or repos that are for different levels of
workflow.
For instance, seperate environments for "devel", "Q/A" (test), "stage",
or "production" -- having at least two levels, but maybe more?
In other words, is there an app that you develop that needs to be
deployed to different levels of servers as it passes various checkpoints?
(What tools and processes are involved in those checkpoints?)
If you have setups like this, how do you manage them with Cobbler and
other tools? What is your workflow, or do you have one?
Thanks!
--Michael
14 years, 8 months
Re: How to you manage yum and package "workflow"
by James Cape
Michael,
I've got the production network, and an isolated test network (cobbler
is dual-homed). The test network pulls from a different set of
packages, based on the puppet $environment variable... So puppet
manages the stuff in yum.repos.d, and adds whatever 3p-$env-$arch
evaluates to, for example.
My cobbler profiles are all pointed at prod, though there's a hole in
the testing (dear liza) where you can push a package to prod without
testing a clean install---I'm leaning towards solving that with
separate profiles for testing, which would pull in the the those repos
for the install separately.
Thanks,
--
James Cape
tel:+1-312-576-3969 (m)
14 years, 8 months
