<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> I’ve been using a given repository for multiple channels, as long as the channels are within the same organization. Repository entities appear to be private to the organization that creates them.<o:p></o:p> <o:p> </o:p> However, a channel that allows trusted organization access does seem to present all the packages to the trusted organization, even though the trusted organization does not see the underlying repository entity behind the channel. I’m still testing for all of the characteristics or quirks of this setup.<o:p></o:p> <o:p> </o:p> So, on channel creation, the linkages will look something like this:<o:p></o:p> <o:p> </o:p> + Create parent.channel<o:p></o:p> <![if !supportLists]>- <![endif]>Create parent.repo<o:p></o:p> <![if !supportLists]>- <![endif]>Link parent.repo to parent.channel <o:p></o:p> <![if !supportLists]>- <![endif]>Create child.channel<o:p></o:p> <![if !supportLists]>o <![endif]>Create child.repo<o:p></o:p> <![if !supportLists]>o <![endif]>Link child.repo to child.channel<o:p></o:p> <o:p> </o:p> + Create second_parent.channel<o:p></o:p> <![if !supportLists]>- <![endif]>Link parent.repo to second_parent.channel<o:p></o:p> <![if !supportLists]>- <![endif]>Create second_parent_child.channel<o:p></o:p> <![if !supportLists]>o <![endif]>Link child.repo to second_parent_child.channel<o:p></o:p> <o:p> </o:p> You now have two parents which can have independent attributes (software to install, filesystem sizing, Kickstart profiles) working from a common base of packages.<o:p></o:p> <o:p> </o:p> The one thing I’d like to see behave differently is that each parent/child set of channels will require spacewalk-repo-sync operations as changes propagate from upstream repositories; effectively, the sync has to be run against all channels referencing a given repo to get the channel details updated.<o:p></o:p> <o:p> </o:p> Good Luck!<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Michael Snyder | Digital River | Principal Engineer, Cloud Engineering<o:p></o:p> msnyder@digitalriver.com | digitalriver.com<o:p></o:p> p: +1 952-225-3257 | c: +1 952-491-1185 | f: +1 952-392-0972 <o:p></o:p> 10380 Bren Road West, Minnetonka, MN 55343, USA<o:p></o:p> <o:p> </o:p> From: spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] On Behalf Of Balint Szigeti<o:p></o:p> Sent: Saturday, November 30, 2013 10:28 AM<o:p></o:p> To: spacewalk-list@redhat.com<o:p></o:p> Subject: Re: [Spacewalk-list] Channels management and client registration<o:p></o:p> <o:p> </o:p> Yes.<o:p></o:p> A repository could be used for multiple channels. I think. I'm not front of my system but if I remember correctly that is the way that it works.<o:p></o:p> <o:p> </o:p> Balint<o:p></o:p> On 30/11/13 11:44, Christian Tardif wrote:<o:p></o:p> On 2013-11-30 04:45, Balint Szigeti wrote:<o:p></o:p> <o:p> </o:p> The solution is, you have 2 or more different EPEL chanels which are using the SAME repository.<o:p></o:p> So your EPEL 6.2 and EPEL 6.0, and so on, use the same repository. In that case the RPMs will be downloaded only once and they will not be duplicated.<o:p></o:p> <o:p> </o:p> OK, so I understand that a particular RPM from a particular repository will ahways be downloaded only once, no matter on which channel it is related to, right?<o:p></o:p> <o:p> </o:p> Christian...<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> _______________________________________________<o:p></o:p> Spacewalk-list mailing list<o:p></o:p> Spacewalk-list@redhat.com<o:p></o:p> https://www.redhat.com/mailman/listinfo/spacewalk-list<o:p></o:p> <o:p> </o:p> </div> </body> </html>