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 <r...@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@redhat.com;
> *Van:* Lupin Deterd <lupindet...@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
> <prmari...@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 <lupindet...@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@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
