[Spacewalk-list] Guide for Channel Management on Multi-Org Setup

[Lupin Deterd]

Hi Michael,

Thank you, exactly did what I envsioned. By the way, this my first time to
handle/setup multi-org and this dry-run will be implemented on RHN
Sattelite 5.6 but testing it now on Spacewalk, do I need to be wary of
differences? On my list right now is only about erratas but rest of
functionality would be the same?

Thanks,
Lupin


On Fri, Oct 11, 2013 at 12:56 AM, Michael Mraka <michael.mraka at redhat.com>wrote:

> Lupin Deterd wrote:
> % Hi,
> %
> % I created two org under the default spacewalk org, now do I need to
> create
> % a sperate software channel for each org?
> %
> % i,e.
> %  org-1
> %    -> centos6
> %       ->centos6-updates
> %    ->centos5
> %        ->centos5-updates
> % org-2
> %   -> centos6
> %       ->centos6-updates
> %    ->centos5
> %        ->centos5-updates
>
> Hi Lupin,
>
> You can achieve this via Channel sharing.
>
> On the bottom of Channel > Manage Software Channel > _your_channel_ page
> there's Channel Access Control section where you can setup the channel to
> meet your sharing needs.
>
> So, no need for separate software channels, conversely channel name are
> unique
> across whole Spacewalk server thus there can't be two centos6 channels in
> different orgs,
>
> % *) Can't be the common channel, i,e centos6 be created on default-org and
> % share to org underneath it?
>
> That's the preferred way how to do it.
>
> % *) If I need to create each software channel to each org, does it mean
> the
> % disk space will double as well?
>
> It would because disk storage is organized per org.
>
>
> Regards,
>
> --
> Michael Mráka
> Satellite Engineering, Red Hat
>
> _______________________________________________
> 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/20131011/e1ea0df1/attachment.htm>