Hi Chris,
On Tue, 19.12.2006 at 03:00:04 -0700, Clint Pachl [EMAIL PROTECTED] wrote:
I am working on an automation system that will commence from OS
installation. For instance, all the questions asked during OS
installation can be placed in a config file on the central repos. To
I've also
Something else you might want to consider (this is what I ended up
doing, since I didn't want to use NFS) is creating installer LiveCD
along the lines of http://www.alti.at/knowhow/obsdlivecd/index.php. I
wrote a dialog based installer to allow techs to do easy OS installs.
The LiveCD approach
Hi Matthew,
On Tue, 06.03.2007 at 09:18:28 -0600, Matthew Franz [EMAIL PROTECTED] wrote:
Something else you might want to consider (this is what I ended up
doing, since I didn't want to use NFS) is creating installer LiveCD
along the lines of http://www.alti.at/knowhow/obsdlivecd/index.php. I
Toni Mueller wrote:
OTOH, in my own network, I want fully automatic unattended installs.
Have you looked at siteXYtools?
http://mongers.org/openbsd/siteXYtools/
---
Lars Hansson
Toni Mueller wrote:
If Qemu runs OpenBSD, that'd answer another long-standing question I
had in my pipe because I'm currently lacking such a thing.
VMware Server is now cost-free as well, if the rest of the license is
acceptable.
On Wed, Dec 20, 2006 at 08:53:41AM -0600, Will Maier wrote:
On Wed, Dec 20, 2006 at 02:31:09PM +, Brian Candler wrote:
That makes a lot of sense. But enforcing that policy might be
difficult. This is important if you're relying on your gold server
for disaster recovery purposes - if the
On Tue, Dec 19, 2006 at 06:23:16AM -0700, Clint Pachl wrote:
A pull-only system assumes that the clients actually pull. What if
they don't? How do you know when their last successful pull was?
If you implement a push system, how do you know if something was
actually pushed? What if
On Wed, Dec 20, 2006 at 02:31:09PM +, Brian Candler wrote:
That makes a lot of sense. But enforcing that policy might be
difficult. This is important if you're relying on your gold server
for disaster recovery purposes - if the target machines had some
change made which nobody remembers
Brian Candler wrote:
That makes a lot of sense. But enforcing that policy might be difficult.
This is important if you're relying on your gold server for disaster
recovery purposes - if the target machines had some change made which nobody
remembers and weren't reflected in the gold server, then
Hello,
Not directly OpenBSD related but I thought I'd ask. I'd like to use
a revision control system to manage files on 25-30
servers but I'm not sure whether I'd use a centralized repository or
have a separate revision control system on each box. It would also be
good
to know how much
On 12/18/06, atstake atstake [EMAIL PROTECTED] wrote:
Not directly OpenBSD related but I thought I'd ask. I'd like to use
a revision control system to manage files on 25-30
servers but I'm not sure whether I'd use a centralized repository or
have a separate revision control system on each
atstake atstake wrote:
Not directly OpenBSD related but I thought I'd ask. I'd like to use
a revision control system to manage files on 25-30
servers but I'm not sure whether I'd use a centralized repository or
have a separate revision control system on each box. It would also be
good
to know
Hello
To the OP, I would keep everything centralized and in a repository.
Then dedicate a test machine, or two, that you will use to deploy your
updates and test the integrity of your automation system. If all goes
well with the test, push the tested updates over to the production
repos.
On Tue, Dec 19, 2006 at 03:00:04AM -0700, Clint Pachl wrote:
I would use a dedicated, highly secure and always backed-up box to
store/manage a central repository (CVS/SVN). This repos will hold
all the necessary bytes (binaries, config files, ports, etc.) to
re-image any machine from scratch.
I'm just going to mention rdist, since it's in base. While certainly not as
complex and feature rich as as cfengine it does get the job done just fine
for most tasks.
---
Lars Hansson
Francois Visconte wrote:
Hello
To the OP, I would keep everything centralized and in a repository.
Then dedicate a test machine, or two, that you will use to deploy
your updates and test the integrity of your automation system. If all
goes well with the test, push the tested updates over
Will Maier wrote:
On Tue, Dec 19, 2006 at 03:00:04AM -0700, Clint Pachl wrote:
I would use a dedicated, highly secure and always backed-up box to
store/manage a central repository (CVS/SVN). This repos will hold
all the necessary bytes (binaries, config files, ports, etc.) to
re-image any
Francois Visconte wrote:
Hello
To the OP, I would keep everything centralized and in a repository.
Then dedicate a test machine, or two, that you will use to deploy
your updates and test the integrity of your automation system. If all
goes well with the test, push the tested updates over
On Tue, Dec 19, 2006 at 05:44:45AM -0700, Clint Pachl wrote:
So your're saying cfengine would need to be included in an install
set, such as base40.tgz or some custom install set in order to be
used in a base install (an obvious yes)? So how do we automate to
that point? I would like to
I'm not so convinced it is that complex on a homogeneous OpenBSD
network. OpenBSD is a very manageable system, such as the entire OS
contained in compressed tarballs for easy extraction and the flexible
ports system. Both of these entities are easily scriptable. Then all
there is to worry about
On Tue, Dec 19, 2006 at 06:23:16AM -0700, Clint Pachl wrote:
I'm not so convinced it is that complex on a homogeneous OpenBSD
network. OpenBSD is a very manageable system, such as the entire
OS contained in compressed tarballs for easy extraction and the
flexible ports system. Both of these
On Tue, Dec 19, 2006 at 05:58:08PM +1100, atstake atstake wrote:
Not directly OpenBSD related but I thought I'd ask. I'd like to use a
revision control system to manage files on 25-30 servers but I'm not
sure whether I'd use a centralized repository or have a separate
revision control system
Not directly OpenBSD related but I thought I'd ask. I'd like to use
a revision control system to manage files on 25-30
servers but I'm not sure whether I'd use a centralized repository or
have a separate revision control system on each box. It would also be good
to know how much leverage can a
23 matches
Mail list logo
