<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebAccess v7.0.1-28479">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: [Spacewalk-list] Channel clonning and patching strategy</title>
<style type="text/css">
body
{
font-family: Arial, Verdana, Sans-Serif ! important;
font-size: 12px;
padding: 5px 5px 5px 5px;
margin: 0px;
border-style: none;
background-color: #ffffff;
}
p, ul, li
{
margin-top: 0px;
margin-bottom: 0px;
}
</style>
</head>
<body>
<p>Hi Lupin,</p><p> </p><p>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.</p><p> </p><p>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.</p><p> </p><p> </p><p>Rick<br /> </p><blockquote style="border-left: #325fba 2px solid; padding-left: 5px; margin-left: 5px">-----Oorspronkelijk bericht-----<br /><strong>Aan:</strong> spacewalk-list@redhat.com; Lupin Deterd <lupindeterd@gmail.com>; <br /><strong>Van:</strong> Rick van der Linde <rick@rilp.nl><br /><strong>Verzonden:</strong> do 12-12-2013 10:59<br /><strong>Onderwerp:</strong> Re: [Spacewalk-list] Channel clonning and patching strategy<br /><strong>Bijlage:</strong> inline.txt<br /><style type="text/css">body { font-family: monospace; }</style><style type="text/css"> .bodyclass { font-family: Arial, Verdana, Sans-Serif ! important; font-size: 12px; padding: 5px 5px 5px 5px; margin: 0px; border-style: none; background-color: #ffffff; } p, ul, li { margin-top: 0px; margin-bottom: 0px; } </style><div><p>Hi Lupin,</p><p> </p><p>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.</p><p> </p><p>Rick<br /> </p><blockquote style="border-left: #325fba 2px solid; padding-left: 5px; margin-left: 5px">-----Oorspronkelijk bericht-----<br /><strong>Aan:</strong> Rick van der Linde <rick@rilp.nl>; spacewalk-list@redhat.com; <br /><strong>Van:</strong> Lupin Deterd <lupindeterd@gmail.com><br /><strong>Verzonden:</strong> wo 11-12-2013 20:17<br /><strong>Onderwerp:</strong> Re: [Spacewalk-list] Channel clonning and patching strategy<br /><style type="text/css">.bodyclass { font-family: monospace; }</style><div dir="ltr"><div><div>Hi Rick,<br /><br />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.<br /><br /> </div>Thanks,<br /> </div>Lupin<br /> </div><div><br /><br /><div>On Wed, Dec 11, 2013 at 5:06 PM, Rick van der Linde <span dir="ltr"><<a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=rick@rilp.nl'); return false;" href="mailto:rick@rilp.nl">rick@rilp.nl</a>></span> wrote:<br /><blockquote style="border-left: #ccc 1px solid; margin: 0px 0px 0px 0.8ex; padding-left: 1ex"><div><p>Hi Jupin,</p><p> </p><p>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.</p><p> </p><p>Rick<br /> </p><blockquote style="border-left: #325fba 2px solid; padding-left: 5px; margin-left: 5px">-----Oorspronkelijk bericht-----<br /><strong>Aan:</strong> <a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=spacewalk-list@redhat.com'); return false;" href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>; <br /><strong>Van:</strong> Lupin Deterd <<a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=lupindeterd@gmail.com'); return false;" href="mailto:lupindeterd@gmail.com">lupindeterd@gmail.com</a>><br /><strong>Verzonden:</strong> wo 11-12-2013 04:00<br /><strong>Onderwerp:</strong> Re: [Spacewalk-list] Channel clonning and patching strategy<br /><strong>Bijlage:</strong> inline.txt<div><div><br /><div dir="ltr">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.</div><div><br /><br /><div>On Wed, Dec 11, 2013 at 12:28 PM, Paul Robert Marino <span dir="ltr"><<a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=prmarino1@gmail.com'); return false;" href="mailto:prmarino1@gmail.com">prmarino1@gmail.com</a>></span> wrote:<br /><blockquote style="border-left: #ccc 1px solid; margin: 0px 0px 0px 0.8ex; padding-left: 1ex">Well I have an idea I've been toying with for that but I haven't tested it yet.<br /><br /><br />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.<br />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.<br />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. <br /><br />I've been thinking of doing this for things like EPEL where I have multiple copies for CentOS, Scientific Linux, etc..<br /><span style="font-family: Prelude, Verdana, san-serif"><br /><br /><br /></span><div style="font-family: arial, sans-serif; color: #999999; font-size: 12px">-- Sent from my HP Pre3</div><br /><span style="font-family: Prelude, Verdana, san-serif; color: navy"><hr align="left" style="width: 75%" /><div><div>On Dec 10, 2013 13:56, Lupin Deterd <<a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=lupindeterd@gmail.com'); return false;" href="mailto:lupindeterd@gmail.com">lupindeterd@gmail.com</a>> wrote: <br /><br /> </div></div></span><div><div><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>Hi list,<br /><br />I'm exploring the following setup.<br /><br /> </div>- Multi-org setup<br /> </div> sub-org1<br /> </div> sub-org2<br /> </div><div> sub-org3<br /> </div><div><br /> </div><div>-Patching schedule policy<br /> </div><div> sub-org1 - monthly<br /> </div><div> sub-org2 - quaterly<br /> </div><div> sub-org3 - monthly<br /> </div><div><br /> </div>Based on the organization and schedule, I want then to clone my channels as such.<br /><br /> </div>Source Base Channel Centos6(Default Org)<br /> </div> - monthly-dev-clone-Centos6<br /> </div> - monthly-qa-clone-Centos6<br /> </div> - monthly-prod-clone-Centos6<br /> <br /> </div> -qtrly-dev-clone-Centos6<br /> </div> -qtrly-qa-clone-Centos6<br /> </div> -qtrly-prod-clone-Centos6<br /><br /> </div>Then I will share the monthly clones channel to sub-org{1,3} and quaterly clones to sub-org2.<br /><br /> </div>I would like to ask for feedback on this setup or any other ways to accomplish my requirements.<br /><br /> </div>Thanks,<br /> </div>lupin<br /> </div></div></div><br />_______________________________________________<br />Spacewalk-list mailing list<br /><a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=Spacewalk-list@redhat.com'); return false;" href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br /><a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" href="https://www.redhat.com/mailman/listinfo/spacewalk-list">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br /></blockquote></div><br /> </div></div></div></blockquote></div><br />_______________________________________________<br />Spacewalk-list mailing list<br /><a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" onclick="parent.webclient.openWindow(this, 'createmail', 'index.php?load=dialog&task=createmail_standard&to=Spacewalk-list@redhat.com'); return false;" href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br /><a title="Deze link naar een extern object zal in een nieuw venster worden geopend" target="_blank" href="https://www.redhat.com/mailman/listinfo/spacewalk-list">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br /></blockquote></div><br /> </div></blockquote></div></blockquote>
</body>
</html>