[Spacewalk-list] Need help with implementation

[Matt Micene]

Have you looked into using clone-by-date to push content from your level
1 to 2?  Or you can look into the spacewalk-manage-channel-lifecycle
script.  

 

Cloning will take all content from a source channel into a target, so
you won't need to push individual packages.  For example, if you clone
the RHN public channel on the 1st of every month to dev, you can do
whatever inspection and testing you need to do on system subcribed to
the dev channel.  Say on the 15th of the month you are comfortable that
dev has the packages you need (further cloning, single errata push, what
have you) you can then clone from dev to test on that date.  Since dev
is the source here, you won't get anything from the level above (RHN
Public).  

 

The script I mentioned was written to provide a wrapper around base
channels with multiple child channels and give you a way to do naming
conventions, rollbacks, etc.  You can do multiple channels with
clone-by-date if you use config files.

 

HTH,

Matt

 

From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Choure,
Siddharth
Sent: Thursday, May 23, 2013 1:46 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Need help with implementation

 

Ok I figured out to add packages from one channel to another using the
GUI. Now my question is how do I make sure that the dependencies for
those packages get transferred as well?

Thanks,
Siddharth Choure

 

On Thu, May 23, 2013 at 12:41 PM, Choure, Siddharth
<schoure at 1worldsync.com> wrote:

Hi Alyson,
Thanks for your response. My setup is identical to yours. I have all the
packages in Level1 and created a Level 2 Private Channel that has all
the packages that one would expect in 6.4 release. Now if I want to push
packages from Level 1 to Level 2, how would I do that other than
rhn_push?

Thanks,
Siddharth Choure

 

On Thu, May 23, 2013 at 12:19 PM, Alyson Calhoun
<alyson.calhoun at gmail.com> wrote:

This is how we are currently implementing our setup:

 

 Level 1:  RHN public channel

       Level 2: Create a "private" channel (considered as dev)

             Level 3:Create another channel (considered as qa)

                  Level 4: one more channel - stable packages
(considered as prod)

 

 

Pull all your nightly packages in level 1

Then sync level2 - do not sync after that until you are ready for
updated packages and test they work on your dev builds.

 

As you go down the levels, each step is a more "stable" package release.

 

>From level 2 down, it will only sync when you manually push the
packages.

 

Hope that makes sense.

 

On Thu, May 23, 2013 at 10:32 AM, Choure, Siddharth
<schoure at 1worldsync.com> wrote:

	So I am doing a Spacewalk installation for our organization.
	
	Here is my setup -

	1. Dedicated Spacewalk server.

	2. mrepo pulls all packages from RH base channel and dumps it
into rhel-x86_64-server-6 channel.

	3. I have created a custom channel for our machines matching the
release and update we are using. eg. for RHEL6.4, I created rhel6u4
channel using the following command - 
	
	spacewalk-create-channel --user=me --server=localhost
--version=6 --update=u4 --release=Server --arch=x86_64
--destChannel=rhel6u4

	and all my test machines are subscribed to this channel.

	This channel has packages that would exist like if I had a 6.4
iso.

	 

	Now my question is, rhel-x86_64-server-6 channel gets updated
nightly by mrepo via a cronjob. Suppose RH releases a newer version of
kernel that we think we need for our machines or any other package for
that matter, how do I transfer that package from mrepo updated channel
to our release channel? I know I can do rhn_push but that will involve a
lot of work. Is there an easier way to do it?

	I am also open to suggestions on how to tweak what I am trying
to do which is basically, have a frozen channel to which all new
machines will be subscribed to as per their release and update and then
update the packages in those channels as per our organizations need.

	Thanks,

	Siddharth Choure

	 

	_______________________________________________
	Spacewalk-list mailing list
	Spacewalk-list at redhat.com
	https://www.redhat.com/mailman/listinfo/spacewalk-list

 


_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130523/0dd71b54/attachment.htm>