[Spacewalk-list] Spacewalk on SuSE?

Bernd Helber bernd at helber-it-services.com
Wed Jul 22 16:27:34 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Daryl.

The subscription ID was meant, you may verify it with  webbrowser if
you cann access the Repo.

If not check if the Subscription is still valid.

Hope that helps.

Kind regards.

Bernd



Am 22.07.15 um 15:33 schrieb Daryl Rose:
> Bernd, I have a follow up question. You're examples show
> "https://whatever:youraccountis@nu.novell.com/repo/$RCE/SLES11-SP1-Poo
l/sle-11-x86_64".
> I'm not sure what goes in "whatever:youraccountis".  I don't know
> if that is our subscription number, the user ID that I log into SCC
> with, or the credential that registered server was registered
> with? I've tried all of the above, and I still get an error telling
> me that SW can not retrieve the repository metadata (respomd.xml). 
> Suggestions? Thank you Daryl
> 
>> Date: Fri, 17 Jul 2015 23:07:09 +0200 From:
>> bernd at helber-it-services.com To: spacewalk-list at redhat.com 
>> Subject: Re: [Spacewalk-list] Spacewalk on SuSE?
>> 
>> Dear Daryl
>> 
>> If you make use of  the nu.novell.com REPO's
>> 
>> It should look like this.
>> 
>> 
>> https://whatever:youraccountis@nu.novell.com/repo/$RCE/SLES11-SP1-Poo
l/sle-11-x86_64
>>
>>
>> 
If you make Use of SuSE Customer Center and make use of  new generated
>> URL's from your registered Systems in SuSE CUstomer Center you
>> dont need the nu.novell stuff anymore.
>> 
>> https://updates.suse.com/SUSE/Products/SLE-SERVER/12/x86_64/product?V
ERYLONGTOKEN
>>
>>
>> 
If you want to do yourself an favor, install spacecmd Shell
>> Creating Channels and Repos works very quick and is very
>> comfortable.
>> 
>> Few month ago i've written a blog post about this task,
>> unfortunately its in german but it might give you an impression
>> how it works.
>> 
>> http://unixhaus.de/index.php?/archives/2502-Spacewalk-Channels-auf-de
r-Shell-konfigurieren.html
>>
>>
>> 
Hope that helps to accomplish your needs.
>> 
>> kind regards.
>> 
>> Bernd Helber
>> 
>> On 17.07.2015 21:46, Daryl Rose wrote:
>>> Bernd, Thanks for the information. I looked at doing exactly
>>> what you described, however, there is a variable in the URL,
>>> $RCE,  that I have no idea what to populate it with.  Also, it
>>> appears to me that they also pass the login credentials in the
>>> URL, ?credentials=NCCcredentials. Do you know how to resolve
>>> those two items? Thanks Daryl
>>> 
>>>> Date: Fri, 17 Jul 2015 20:16:05 +0200 From:
>>>> bernd at helber-it-services.com To: spacewalk-list at redhat.com 
>>>> Subject: Re: [Spacewalk-list] Spacewalk on SuSE?
>>>> 
>>>> One of my Customers, is using Spacewalk for exactly the same
>>>> purpose. Patching and Installing CentOS and SLES 11/12
>>>> 
>>>> What they do ist.. registering an Client to SuSE Customer
>>>> Center scc.suse.com
>>>> 
>>>> If the client is registered.. they activate the repository in
>>>> SLES12 After the Activation the pull the newly generated REPO
>>>> URls out the SLES Instance
>>>> 
>>>> Create a Software Channel in Spacewalk Create a repository in
>>>> Spacewalk  add the Repository to the desired Spacewalk
>>>> Software Channel.
>>>> 
>>>> And install the Spacewalk  Agent to the SLES Machine.
>>>> 
>>>> In the past it was possible to get all Packages from
>>>> nu.novell.com
>>>> 
>>>> SLES in Spacewalk have been a topic on this list you may
>>>> check out those links
>>>> 
>>>> https://www.redhat.com/archives/spacewalk-list/2014-December/msg001
33.html
>>>>
>>>>
>>>> 
https://www.redhat.com/archives/spacewalk-list/2015-February/msg00057.ht
ml
>>>> 
>>>> Kind regards and happy weekend.
>>>> 
>>>> 
>>>> Am 17.07.15 um 18:20 schrieb Daryl Rose:
>>>>> Steven, Yes, my ultimate goal is to manage both my RHEL and
>>>>> SLES servers with a single package management solution. I
>>>>> have a large number of both RHEL and SLES servers.  I am
>>>>> looking at a server/package management system that I can
>>>>> manage both environments.  I have experience with previous
>>>>> versions of RH Satellite, and knowing that SW was the
>>>>> upstream source I stood up a SW server as a
>>>>> Proof-of-Concept.  I was able to successfully sync both
>>>>> CentoOS and OpenSuSE repository's and patch demo servers. 
>>>>> In the past couple of months, I've had RH and SuSE
>>>>> demonstrations to see if either one their products would
>>>>> fit with what we're looking for in a package management
>>>>> system. I was not impressed with RH Satellite 6 demo.  The
>>>>> biggest thing that I need is to be able to patch my
>>>>> servers.  The person doing the demonstration couldn't show
>>>>> me how to patch a system with Satellite 6.  I don't
>>>>> remember for sure, either he wasn't setup for it, or was
>>>>> prepared.  I do remember that I was not happy with the
>>>>> person doing the demonstration.  And.....l specifically
>>>>> requested patch management when I setup the demo.  One
>>>>> thing that I do remember about the demo was; I can only
>>>>> manage RHEL servers with Satellite.  I can't manage my SLES
>>>>> servers.  I would need a separate system to manage my  SLES
>>>>> servers. I had no prior experience with SuSE Manager prior
>>>>> to the demonstration, but I was really impressed with the
>>>>> product.  I learned during the demo that SW is also the
>>>>> upstream source and SuSE Manager looks and acts just like
>>>>> SW, only a different theme.   The person doing the
>>>>> demonstration was prepared and showed me exactly want I
>>>>> wanted to see, how to patch systems using SuSE Manger.
>>>>> Also I can manage both RHEL and SLES with SuSE Manger.  In
>>>>> order to get the RHEL packages, I would need a Pulp server
>>>>> registered with RH, then sync RHEL packages to the SuSE
>>>>> Manger.  I successfully setup a Pulp server, and synced the
>>>>> packages to my current CentOS SW server. Now that I have
>>>>> functioning Pulp and SW servers I got to thinking "how
>>>>> would I get the packages from SuSE?"  I don't know if I can
>>>>> point my SW server to SuSE without it being registered.
>>>>> My guess is that you can't. SuSE Manager is a SLES server
>>>>> and would be registered with SuSE.  I thought that I would
>>>>> try putting SW on a SLES server, register it to SuSE to get
>>>>> the SLES packages.  I may not be able to access ALL of the
>>>>> SLES repositories, but that's okay, this is just a PoC
>>>>> server, not an actual production server.  I would then use
>>>>> the Pulp server to pull down RHEL packages and sync them
>>>>> over to the SW server. <snip>.....but it is possible to use
>>>>> spacewalk running on Centos to manage/deploy SLES, opensuse
>>>>> etc. </snip> If this is actually possible, how would a
>>>>> person access the SuSE repositories via SW on a CentOS
>>>>> server?   If this is possible, I would like to try that.
>>>>> I would be much easier than trying to compile SW from
>>>>> scratch on a SLES server. Thanks Daryl
>>>>> 
>>>>> From: Steven.Reed at transport.nsw.gov.au To:
>>>>> spacewalk-list at redhat.com Date: Fri, 17 Jul 2015 10:56:34
>>>>> +1000 Subject: Re: [Spacewalk-list] Spacewalk on SuSE?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> Have not stood it up on SLES but it is possible to use
>>>>> spacewalk running on Centos to manage/deploy SLES, opensuse
>>>>> etc.  Assuming that’s your end goal.
>>>>> 
>>>>> There is a bit of messing round with the kickstart/autoyast
>>>>> files to get them to work and you need to modify some parts
>>>>> of cobbler.
>>>>> 
>>>>> Obviously this is unsupported and if you want to run it in
>>>>> production it may be better to use Suse’s supported
>>>>> product.  Unless you know what you are doing and can deal
>>>>> with unexpected issues J
>>>>> 
>>>>> 
>>>>> 
>>>>> From: spacewalk-list-bounces at redhat.com
>>>>> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of
>>>>> Daryl Rose
>>>>> 
>>>>> Sent: Friday, 17 July 2015 4:32 AM
>>>>> 
>>>>> To: spacewalk-list at redhat.com
>>>>> 
>>>>> Subject: Re: [Spacewalk-list] Spacewalk on SuSE?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Yes, I know that SuSE is using Spacewalk as their upstream
>>>>> source.  I had them do a demo for me awhile back.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> How difficult is it to compile SW from source?  All of the
>>>>> documentation is for Red Hat, CentOS and Fedora.  Has
>>>>> anyone else compiled it from source?  What kind of
>>>>> documentation is available?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Daryl
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Date: Thu, 16 Jul 2015 12:15:03 -0400
>>>>> 
>>>>> From: prmarino1 at gmail.com
>>>>> 
>>>>> To: spacewalk-list at redhat.com; spacewalk-list at redhat.com
>>>>> 
>>>>> Subject: Re: [Spacewalk-list] Spacewalk on SuSE?
>>>>> 
>>>>> Yes the guys at SuSE lol.
>>>>> 
>>>>> 
>>>>> Seriously it the upstream project for SuSE manager so yes
>>>>> it can be done and you shouldn't expect to see any SuSE
>>>>> specific issues; the one piece of bad news is you should
>>>>> not expect the Red Hat rpms to work on SuSE so unless
>>>>> someone know a SuSE specific RPM  repo you may have to
>>>>> compile the server components your self.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> From: Daryl Rose
>>>>> 
>>>>> 
>>>>> Sent: Thursday, July 16, 2015 09:55
>>>>> 
>>>>> 
>>>>> To: spacewalk-list at redhat.com
>>>>> 
>>>>> 
>>>>> Reply To: spacewalk-list at redhat.com
>>>>> 
>>>>> 
>>>>> Subject: [Spacewalk-list] Spacewalk on SuSE?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Has anyone stood up Spacewalk on SuSE?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Daryl
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Spacewalk-list mailing list Spacewalk-list at redhat.com 
>>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> This email (including any attachments) may contain
>>>>> confidential and/or legally privileged information and is
>>>>> intended only to be read or used by the addressee(s). If
>>>>> you have received this email in error, please notify the
>>>>> sender by return email, delete this email and destroy any
>>>>> copy. Any use, distribution, disclosure or copying of this
>>>>> email by a person who is not the intended recipient is not
>>>>> authorised.
>>>>> 
>>>>> 
>>>>> 
>>>>> Views expressed in this email are those of the individual
>>>>> sender, and are not necessarily the views of Transport for
>>>>> NSW, Department of Transport or any other NSW government
>>>>> agency. Transport for NSW and the Department of Transport
>>>>> assume no liability for any loss, damage or other
>>>>> consequence which may arise from opening or using an email
>>>>> or attachment.
>>>>> 
>>>>> Please visit us at http://www.transport.nsw.gov.au or
>>>>> http://www.transportnsw.info
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________ 
>>>>> Spacewalk-list mailing list Spacewalk-list at redhat.com 
>>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________ 
>>>>> Spacewalk-list mailing list Spacewalk-list at redhat.com 
>>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>>> 
>>>> 
>>>> 
>>>> -- with kind regards
>>>> 
>>>> 
>>>> _______________________________________________ 
>>>> Spacewalk-list mailing list Spacewalk-list at redhat.com 
>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________ Spacewalk-list
>>> mailing list Spacewalk-list at redhat.com 
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>> 
>> 
>> _______________________________________________ Spacewalk-list
>> mailing list Spacewalk-list at redhat.com 
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 
> 
> 
> 
> _______________________________________________ Spacewalk-list
> mailing list Spacewalk-list at redhat.com 
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 


- -
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVr8R2AAoJEHxIkeoL34IfXGMH/A58Lzoxn/PTxzsuKMS6nPMh
/mS4bAxcflA0vQUCdZcQixXcangJtBwrMowpTeeJA/QJosEtw8/b+5MSBH3ooiJm
CjyLMWIVljex/zA1BKguukwm2Q8Od/9xxWNl9q9ycVkQjvs27JpQ2UPsYlqFtPwS
B28N5BbJzNZ3GSP+dmuOVf6pNGjDSjgJQ3JH52KehF5bFv6iru/PVJzuqhZFqScF
VnjF5rTSS8BwSOHM8qpaQ+F9egzKnBckN713eAieC2vDZ5vLEPXn15k1lCffJHR2
tAkhxRULRrBGi4v2fbTksp+O5pNCPcwcQeFcCshamv4p1mL0uJj4gadwXDNvmkE=
=057k
-----END PGP SIGNATURE-----




More information about the Spacewalk-list mailing list