[Spacewalk-list] Channel clonning and patching strategy

Thu Dec 12 10:09:15 UTC 2013

Hi Lupin,

tested the organisation sharing granularity in de "Default Organisation" (orgid=1) and found this allows one to configure which suborg may see the channel and which not. I think that will solve your problem. I manage to provide these channel through suborgs, but found this does not allow me to share (child) channels with granularity. Options are: all trusted suborgs see these channels or none of them.

By building the "repository" in the default org will indeed allow you to do I suggested (share channels to specified suborgs) and allow you to clone channels. Cloning channels in suborg does work if the suborg is the one that assembled the channel. It can clone its own channels, not shared from oither suborgs.

Rick

-----Oorspronkelijk bericht-----
Aan: spacewalk-list at redhat.com; Lupin Deterd <lupindeterd at gmail.com>; 
Van: Rick van der Linde <rick at rilp.nl>
Verzonden: do 12-12-2013 10:59
Onderwerp: Re: [Spacewalk-list] Channel clonning and patching strategy
Bijlage: inline.txt
Hi Lupin,

Something comes up to my mind. The trust relationships aren't granular (enough) to be able to say, share this (child) channel to just these suborgs. According to me it's now rudimentary share to all suborgs or none of them. Please first find out how to address this.I'm trying to figure out this now.

Rick

-----Oorspronkelijk bericht-----
Aan: Rick van der Linde <rick at rilp.nl>; spacewalk-list at redhat.com; 
Van: Lupin Deterd <lupindeterd at gmail.com>
Verzonden: wo 11-12-2013 20:17
Onderwerp: Re: [Spacewalk-list] Channel clonning and patching strategy
Hi Rick,

Yes, I think that's what I envisioned above. I will create all clone channels on the Default-Org and then only share those clones to sub-orgs. From my test I cannot clone a channel within the sub-org if it was a shared channel.

 Thanks,
 Lupin

On Wed, Dec 11, 2013 at 5:06 PM, Rick van der Linde <rick at rilp.nl> wrote:
Hi Jupin,

You may want to solve this by "building" the channel within one suborg and share them to your mentioned suborgs by trust relationship between these organisation. The (child) channels can then easily be cloned within the suborg and provided to the suborg when needed by configuring the share channel to trusted orgs. You can for example add another suborg that contains all packages or use one of your already defined suborgs to provide these (child) channels.

Rick

-----Oorspronkelijk bericht-----
Aan: spacewalk-list at redhat.com; 
Van: Lupin Deterd <lupindeterd at gmail.com>
Verzonden: wo 11-12-2013 04:00
Onderwerp: Re: [Spacewalk-list] Channel clonning and patching strategy
Bijlage: inline.txt

Yes, the point being of using Spacewalk instead of plain cobbler/repo sync is that you can have a lock channel and with spacewalk-clone-by-date you can have complete control on when do you have your clone channel get updated.

On Wed, Dec 11, 2013 at 12:28 PM, Paul Robert Marino <prmarino1 at gmail.com> wrote:
Well I have an idea I've been toying with for that but I haven't tested it yet.

Since cobbler does contain a usable yum repo under the hood you could theoretically point repo sync to one of the other repos in cobbler.
Figuring out the URL is simple just view one of the kickstarts that uses the source channel and you can copy the URL it uses for the channel.
The only problem I can see in doing that is I don't think the errata syncing wouldn't work because I don't think cobblers repos get the erratas synced. 

I've been thinking of doing this for things like EPEL where I have multiple copies for CentOS, Scientific Linux, etc..

-- Sent from my HP Pre3

--------------------------------
On Dec 10, 2013 13:56, Lupin Deterd <lupindeterd at gmail.com> wrote: 

 Hi list,

I'm exploring the following setup.

 - Multi-org setup
   sub-org1
   sub-org2
   sub-org3

 -Patching schedule policy
   sub-org1 - monthly
   sub-org2 - quaterly
   sub-org3 - monthly

 Based on the organization and schedule, I want then to clone my channels as such.

 Source Base Channel Centos6(Default Org)
  - monthly-dev-clone-Centos6
  - monthly-qa-clone-Centos6
  - monthly-prod-clone-Centos6

  -qtrly-dev-clone-Centos6
  -qtrly-qa-clone-Centos6
  -qtrly-prod-clone-Centos6

 Then I will share the monthly clones channel to sub-org{1,3} and quaterly clones to sub-org2.

 I would like to ask for feedback on this setup or any other ways to accomplish my requirements.

 Thanks,
 lupin

_______________________________________________
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/20131212/bee60749/attachment.htm>