Also in spacewalk 2.0 and up you can add the SSL certs from subscription manager into spacewalk. Then you can take the subscription URI's from access.redhat.com and prefix them with https://cdn.redhat.com .
They are regular yum repos with the errata so there is no need to do an external errata sync any more. 

Warning using mrepo or the method I mentioned is technically a violation of your Red Hat support contract since it does not pass the subscription information to Red Hat.





-- Sent from my HP Pre3


On Sep 3, 2014 6:24 PM, Avi Miller <[email protected]> wrote:

Hi,

On 4 Sep 2014, at 7:59 am, Glen Collins <[email protected]> wrote:

> And thanks for your reply. While the option you gave will work, I don't think it'll work when you need two authenticated repositories like RHEL and Oracle.

The authentication used by the ULN update mechanism is different to the one used by RHN, so you should be able to combine both into a single install. Certainly you can mix a ULN-based Spacewalk repository with others, so I can't see why this should be any different.

Note that Spacewalk 2.2 ships with ULN integration (it was submitted upstream), so if you're running 2.2, you can use ULN right now. Essentially, just configure your CSI-enabled Oracle SSO credentials in /etc/rhn/spacewalk-repo-sync/uln.conf and use the repository URL style of uln:///<channel_id>, e.g. uln:///ol6_x86_64_latest - and yes, the three / are intentional here.

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia


_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to