Hi to all,
I’m new to SuseManager, so maybe my question sounds dumb…
It is stated that one can manage SLES and Redhat (RHEL?) with
SuseManager. But what’s about CentOS?
Tom
Since CentOS is basically rebranded RHEL I’d expect it to work. With that
said, Novell/SUSE have typically only tested with RHEL since that’s the
distribution from which most customers have migrated to SLES, on which
most customers have requested support. Will CentOS be supported at this
point? Probably not, so if you have a problem be sure you can reproduce
it on RHEL as well, or petition SUSE to support CentOS as well via an
enhancement request ( http://www.novell.com/rms/ ).
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
Am 14.10.2013 14:08, schrieb ab:[color=blue]
Since CentOS is basically rebranded RHEL I’d expect it to work. With that[/color]
Me too…
[color=blue]
said, Novell/SUSE have typically only tested with RHEL since that’s the
distribution from which most customers have migrated to SLES, on which
most customers have requested support. Will CentOS be supported at this[/color]
I was afraid of that answer…
[color=blue]
point? Probably not, so if you have a problem be sure you can reproduce
it on RHEL as well[/color]
Good point
[color=blue]
or petition SUSE to support CentOS as well via an
enhancement request ( http://www.novell.com/rms/ )[/color]
At this early moment I’m just thinking (not really evaluating)
management tools and suites.
Thank you AB
Tom
K, well if you get into it SUSE Manager (and SMT, which is free currently)
is supposed to be pretty neat. I’ve seen demos of SMT which let you do
obvious things like cache channels at your site (better performance, less
data usage for the enterprise, etc.) to do staging of patches, so you can
create channels on your server, all pulling the patches from Novell/SUSE,
which are made for the production servers, the QA servers, the dev
servers, etc. Point each type of server to its own appropriate channel
(test servers to test channels, prod servers to prod channels, etc.) and
then apply the appropriate patches to those servers.
This means you can configure all of your servers to do auto updates of
whatever they can see, and then you can control what they see. Push out
everything you need to test servers. If they are okay, push out to QA
servers by just choosing where the patches show up (in which channels) and
then the QA servers update. Next prod, etc. Pretty fun since otherwise
you’re going to each server, choosing updates yourself, getting everything
from the main server which may be receiving newer (untested by you)
patches as you go through this process, which means greater risk. SMT
resolves that problem pretty nicely, and I’ve heard SUSE Manager can do a
bit more by letting you have a bit more definition to group servers by
roles (an Oracle database-hosting system gets these patches, while an
Apache httpd box gets those, etc.).
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…