Dominique Dumont | 1 Sep 2009 10:24
Picon
Favicon

Re: How to you manage yum and package "workflow" ?


Hello

Michael DeHaan <mdehaan <at> redhat.com> writes:
> 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.

Yes. I have developed for our needs an application to handle a workflow
of packages during their qualification. 

> For instance, seperate environments for "devel", "Q/A" (test),
> "stage", or "production" -- having at least two levels, but maybe
> more?

We have 4 levels:
- integ: barely tested but should work
- qa_ready: functional test done
- pre_release: most QA tests done, may be shipped to customer with some
  restrictions (early access)
- release (aka production).

> 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?)

Packages are tested before entering the "integ" level mostly by rpmlint
and some custom tools to enforce our policy. 

(Continue reading)

Justin Sherrill | 1 Sep 2009 14:25
Picon
Favicon

Disabling PXE support in cobbler

Is there was a way to disable cobbler from writing to /tfpboot?
Currently cobbler just blows away whatever pxe configuration is there.
I didn't see any config options to disable this, nor did my scan over
the pxe section of the code seem to show much.

Thanks,

-Justin

--

-- 
Justin Sherrill, RHCA          1801 Varsity Drive.
Software Engineer                Raleigh, NC 27603
Red Hat, Inc.
James Cape | 1 Sep 2009 15:28
Picon
Favicon
Gravatar

Re: How to you manage yum and package "workflow"

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)
Thomas S Hatch | 1 Sep 2009 15:49
Picon
Gravatar

Re: How to you manage yum and package "workflow" ?

Oh, I forgot to mention, at my previous job I set up a koji server to manage builds and did the "inheritence magic" to make a always up-to-date repo of local builds which could be taped by cobbler for development builds.  After testing was complete we moved the rpms into a main deployment repo for the company.  So just a 2 step process, but koji helped a great deal.  Hopefully I can get koji up and running at me current employment when I find the time, it just so happens that koji is a bit of a pain to set up :)

On Tue, Sep 1, 2009 at 2:24 AM, Dominique Dumont <dominique.dumont <at> hp.com> wrote:

Hello

Michael DeHaan <mdehaan <at> redhat.com> writes:
> 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.

Yes. I have developed for our needs an application to handle a workflow
of packages during their qualification.

> For instance, seperate environments for "devel", "Q/A" (test),
> "stage", or "production" -- having at least two levels, but maybe
> more?

We have 4 levels:
- integ: barely tested but should work
- qa_ready: functional test done
- pre_release: most QA tests done, may be shipped to customer with some
 restrictions (early access)
- release (aka production).

> 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?)

Packages are tested before entering the "integ" level mostly by rpmlint
and some custom tools to enforce our policy.

Integration team is responsible of creating a package set that represent
a major functionality or a product. Once these package sets are created,
they can be promoted to qa_ready is decided by integration team (all
packages will follow the promotion of a package set). Promotion to
pre_release or release is decided by QA or project manager.

A promotion can be done by a command line or by a web interface.

Notifications are sent by mail to notify people about the package and
package set evolution in the infrastructure.

I have presented this "package infrastructure" to French Perl Workshop
[1] in June. They provides some details on the workflow and
tools. Fortunately for most of you the slides [2] are in English.

> 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?

Ahem, interaction with Cobbler is not done yet, but is definitely on our
radar screen.

Feel free to send comments or questions.

Hope this helps

[1] http://conferences.mongueurs.net/fpw2009/ (French)
[2] http://journeesperl.fr/fpw2009/slides/hp_pkg_infra.pdf (English)

--
Dominique Dumont
"Delivering successful solutions requires giving people what they
need, not what they want." Kurt Bittner

irc:
 domidumont at irc.freenode.net
 ddumont at irc.debian.org
_______________________________________________
cobbler mailing list
cobbler <at> lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

_______________________________________________
cobbler mailing list
cobbler <at> lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
Dan Radez | 1 Sep 2009 19:14
Picon
Favicon
Gravatar

Re: How to you manage yum and package "workflow" ?


> 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?)
> 

We are in process of migrating to a Django based web app we've written
that in itself is a self contained repo manager. It handles package and
repo associations in a database and generates yum repos from it's data.
It also reads the package data and stores it for searching and
validating associations.

The app has functionality built into it to communicate with other
instances. So we've spun up a instance for of the app for each dev,
release-builders, qa, stage and prod to isolated versions to the
environment they're currently being tested in.

To promote a package from one env to another we just use the app. It
transfers the file and sets up the new db records and kicks off a repo
regeneration for us.

Dan

Michael Saverino | 1 Sep 2009 19:46

Downloading a Debian 5.0 repo with Cobbler

 

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 <at> ln22ms ~]$ arch=i386
[saverino <at> ln22ms ~]$ dist=lenny
[saverino <at> ln22ms ~]$ hostname=ftp.es.debian.org
[root <at> 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/images/netboot/debian-installer/i386/' /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...

_______________________________________________
cobbler mailing list
cobbler <at> lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
Michael A. Saverino | 3 Sep 2009 05:44

Downloading a Debian 5.0 repo with Cobbler

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 <at> ln22ms ~]$ arch=i386
[saverino <at> ln22ms ~]$ dist=lenny
[saverino <at> ln22ms ~]$ hostname=ftp.es.debian.org
[root <at> 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/images/netboot/debian-installer/i386/' /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...
_______________________________________________
cobbler mailing list
cobbler <at> lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
Javier Palacios | 3 Sep 2009 09:05
Picon

Re: Downloading a Debian 5.0 repo with Cobbler

On Thu, Sep 3, 2009 at 5:44 AM, Michael A. Saverino<saverino <at> hughes.net> wrote:
> 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

First of all, take into account that this feature is currently
discontinued/unsupported.

> 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:

But in any case, the wiki instructions should work if you are using a
recent enough development version of cobbler. If you are using the
latest version, that means that Michael has actually removed that code
and it is actually not available. In that case, you can try to use
version from git://github.com/javiplx/cobbler-devel.git although the
base version for that branch is many months old.

But in any case, whithout the --os-version, the import will not work,
because it is impossible to guess which debian version is being
imported.

Alternative path is to import a real media, that will allow
autodiscovery. But only boot information is used from the imported
tree, and you will need to download again all the packages to the
associated cobbler/apt repository

Javier Palacios
Bryan Schneiders | 3 Sep 2009 17:38

webui, profile, yum repos selection box, architecture filter

cobbler-1.6.6-1.fc10.i386

The yum repository selection box on the profile page in the web interface appears to automatically filter
out repositories that don't match the architecture of the current profile.  This includes hiding i386
repositories from an x86_64 profile.  I'm finding myself in a situation where I cannot select my local i386
updates repositories containing necessary updates for i386 packages I have installed on x86_64 hosts.

I will try the command line next and hope it doesn't have the same restrictions.

Is this behaviour also present in the upcoming release of Cobbler?  Is there was way to change it in the
meantime for the current stable release?

Thanks.
--

-- 

Bryan Schneiders
bschneiders <at> woti.com
301-562-1900 ext 305
Michael Saverino | 3 Sep 2009 18:42

Re: Downloading a Debian 5.0 repo with Cobbler



On Sep 1, 2009, Michael Saverino <saverino <at> hughes.net> wrote:

_______________________________________________
cobbler mailing list
cobbler <at> lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Gmane