I have a handful of CentOS servers running various bits and pieces for a
small WISP. These servers are spread across bare metal, esxi virtual
machines and a couple kvm guests. In due time, I expect the esxi host to
be removed and it's machines migrated/moved to kvm.
Each server does one thing, a
I use spacewalk and puppet for even just my home ecosystem. Wouldn't go
back. It makes management of updates etc so much easier.
-Blake
On Feb 18, 2014 11:11 AM, "Jon Moore" wrote:
> I have a handful of CentOS servers running various bits and pieces for a
> small WISP. These servers are spread
What features of spacewalk are you using? I'm in this area where the whole
idea looks cool and seems impressive, but I do wonder how much profit I'll
get out of all the setup and additional maintenance.
Thanks,
Jon M
On Tue, Feb 18, 2014 at 12:00 PM, Blake Dunlap wrote:
> I use spacewalk and
Package/channel management and pxe deployment. Puppet works better for
config management.
The main use is so I can control package upgrades across my cloud VERY
easily. The box is also very low maintenance once set up, almost 0.
There is also an errata import script that will build all the errata
Jon,
If you are taking care of a lot of RHEL or CentOS boxes, the answer is
Yes! I use it to kickstart my servers, both physical and virtual. I
use it to maintance and patch my servers. You can also use it to
monitor them as well. Can use it as a low level cvs for conifig files,
though I think pu
So you understand, it only takes about 10 minutes to set up on a new vm.
Just have a postgres server somewhere for the database. The only slow part
is waiting for the channels to sync.
Just make sure you have a locally usable FQDN already configured on the box
forward and back and your life will
I've attempted a setup in the past, maybe 2 years ago now. The
installation was pretty quick. Just added their repo, and did some yum
installs. However, once I was "up and running" and I never could quite
figure out how to get from I have a new spacewalk server up to actually
having the channels
Happy to help if you have questions.
Suggest making a master channel with no packages for the major version, and
using child channels even for the base channel. It makes it much easier to
do point upgrades later.
-Blake
On Tue, Feb 18, 2014 at 1:15 PM, Jon Moore wrote:
> I've attempted a setu
Thanks for the comments. I am managing mostly CentOS servers. Based on
other recommendations, I'm going to try and lab some of this up and see how
it goes. Sounds like I will benefit from this.
On Tue, Feb 18, 2014 at 1:05 PM, Chuck Payne wrote:
> Jon,
>
> If you are taking care of a lot of
Jon,
I created a script that can help you put down the repo, you are
welcome to use. You will need to adjust to your changes. I use it as a
cron job to make sure I am update today, and a way to pull files once
I got a box created.
Chuck
On Tue, Feb 18, 2014 at 2:17 PM, Blake Dunlap wrote:
> Hap
I would like to agree about the ease of pxe deployment, errata/bug fixes,
and general systems management. I have been attempting to deploy Spacewalk
for over a week now, and I am no further along than the database setup. The
lead systems admin has given a list protocols for packages allowable
(
11 matches
Mail list logo
