You get SLES 11 updates from Novell. SLES12 from SuSE. Regards Robert Am 08.08.2016 17:58 schrieb Bernd Helber <[email protected]>: > > Dear Jinesh, > > there are no URLS, like we had it in the Past. > You have to register a System at > > SuSE Customer Center, select all Repo's you're in need of. > > SuSE Customer Center will generate URLS you have to use. > > > At example > > spacecmd {SSM:0}> repo_details sles12-sdk > Repository Label: sles12-sdk > Repository URL: > https://updates.suse.com/SUSE/Products/SLE-SDK/12/x86_64/productveryyyyyyyloooooooooooooooooooooooongtooooooooookenwithweirdsigns > > Repository Type: yum > > > Then create your Software Channels. > Create your Repos and attach the Repos to the Software Channel. > > > Kind regards. > > Am 08.08.16 um 16:11 schrieb Daryl Rose: > > Jineesh, > > > > > > This is correct. You have to have properly licensed servers to be able > > to access the repositories. > > > > > > The reason why I am using SW is because I have both RHEL and SLES > > servers in my environment. I evaluated purchasing Red Hat Satellite > > server and SuSE Package Management Server. However, I cannot afford > > purchasing both products and licenses all of my systems, so I opted for > > Spacewalk. Spacewalk is the upstream development for both platforms and > > I can have a single pain of glass for both environments. > > > > > > I could make either RH Satellite or SuSE Management Server work for > > both, but I would have to setup a PULP server to proxy the packages from > > one environment to the other. I tested that scenario, and it was a > > major pain. Going the SW direction seems to be the best option. I > > registered my SW server with Red Hat, and then a couple of servers with > > SuSE, who's sole purpose is to access the repositories. I now am able > > to manage both RHEL and SLES environments from a single SW server. Very > > easy and works great. But again, you need to license and register > > servers with SuSE to access the repositories. > > > > > > Daryl > > > > > > > > > > ------------------------------------------------------------------------ > > *From:* [email protected] > > <[email protected]> on behalf of Robert Paschedag > > <[email protected]> > > *Sent:* Sunday, August 7, 2016 11:34 PM > > *To:* [email protected] > > *Cc:* [email protected] > > *Subject:* Re: [Spacewalk-list] channels for SuSE - in spacewalk > > > > You can find the URL links within your Novell account settings. > > > > Put your credentials directly into the URL > > > > Regards > > Robert > > Am 05.08.2016 15:41 schrieb [email protected]: > >> > >> Hi Daryl, > >> > >> > >> > >> Thanks for the details. > >> > >> > >> > >> Could you please let us know what is the repository URL for SUSE11 SP3 > >> and where you put the credentials in URL link. > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Thanks & Regards, > >> > >> Jineesh K > >> > >> > >> > >> > >> > >> > >> > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Daryl Rose > >> Sent: Thursday, August 04, 2016 1:18 AM > >> To: [email protected] > >> Subject: Re: [Spacewalk-list] channels for SuSE - in spacewalk > >> > >> > >> > >> Jineesh, > >> > >> > >> > >> In order to get SLES repositories setup in Spacewalk, you need to first > >> register one server per service pack with SuSE. For example, I have > >> servers that are on both SLES 11 SP3 and SLES 11 SP4. I built two servers > >> specifically just to register to SuSE. One was registered to the SLES 11 > >> SP3 SuSE repository and the other > > was registered to the SLES 11 SP4 > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> After I built those server and registered them with SuSE, I opened yast > >> and copied the Repository URL. I used that string, along with the > >> registered credentials in the "Repository URL" of the Repository Details > >> page in Spacewalk. The credentials can be found in > >> /etc/zypp/credentials.d/NCCcredentials of the server that you > > would register with SuSE. > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> From: [email protected] > >> <[email protected]> on behalf of > >> [email protected] <[email protected]> > >> Sent: Wednesday, August 3, 2016 2:17 PM > >> To: [email protected] > >> Subject: Re: [Spacewalk-list] channels for SuSE - in spacewalk > >> > >> > >> > >> Hi Daryl, > >> > >> > >> > >> It would be helpful, if you could share the details. > >> > >> > >> > >> > >> > >> Thanks & Regards, > >> > >> Jineesh K > >> > >> > >> > >> > >> > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Daryl Rose > >> Sent: Tuesday, August 02, 2016 7:36 PM > >> To: [email protected] > >> Subject: Re: [Spacewalk-list] channels for SuSE - in spacewalk > >> > >> > >> > >> Jineesh, > >> > >> > >> > >> I was wondering if you were able to get SLES 11 channel setup? I > >> successfully setup SLES 11 and am in the process of moving all of my > >> servers from SCC to my Spacewalk environment. > >> > >> > >> > >> If you need further assistance, please let me know. > >> > >> > >> > >> Daryl > >> > >> > >> > >> ________________________________ > >> > >> From: [email protected] > >> <[email protected]> on behalf of > >> [email protected] <[email protected]> > >> Sent: Thursday, June 2, 2016 8:19 AM > >> To: [email protected] > >> Subject: Re: [Spacewalk-list] channels for SuSE - in spacewalk > >> > >> > >> > >> Hi, > >> > >> > >> > >> Anybody knows the steps to create channel for Enterprise SuSE 11 boxes > >> > >> > >> > >> > >> > >> Thanks & Regards, > >> > >> Jineesh K > >> > >> > >> > >> > >> > >> From: Kotayi, Jineesh > >> Sent: Monday, May 30, 2016 7:47 PM > >> To: '[email protected]' <[email protected]> > >> Subject: [Spacewalk-list] channels for SuSE - in spacewalk > >> > >> > >> > >> > >> > >> Hi, > >> > >> > >> > >> We have installed spacewalk setup in our environment and created channels > >> for Redhat and CentOS. > >> > >> > >> > >> We have to create channels for SuSE 11 boxes as well. Could you please > >> help us to share the documents to create the channels for SuSE as we are > >> unable to find any forum > >> > >> > >> > >> > >> > >> Thanks & Regards, > >> > >> Jineesh K > >> > >> > >> > >> ________________________________ > >> > >> > >> This message is for the designated recipient only and may contain > >> privileged, proprietary, or otherwise confidential information. If you > >> have received it in error, please notify the sender immediately and delete > >> the original. Any other use of the e-mail by you is prohibited. Where > >> allowed by local law, electronic > > communications with Accenture and its affiliates, including e-mail and > > instant messaging (including content), may be scanned by our systems for > > the purposes of information security and assessment of internal > > compliance with Accenture policy. > >> ______________________________________________________________________________________ > >> > >> > >> www.accenture.com <http://www.accenture.com> > > > > _______________________________________________ > > 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 > > > > > > _______________________________________________ > 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
