Central configuration storage
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm looking for a solution to store configuration files in a central location. My first guess was to look at LDAP, and see if you can use that for keeping track of configuration. The intended setup is a farm of webservers, database servers and the like, on Debian and Windows machines. The point is to keep the configuration in a central location, so we can easily keep track of it and keep it seperated from the servers themselves. The final goal is to be able to more easily add new servers to the farm, that all serve the same data via loadbalancing.

Is LDAP a suitable solution for the above problem? I started with looking for a LDAP configuration storage method for Apache 2, but didn't find anything. Can anyone point me in the right direction, or maybe give me a starting point.

Kind regards,

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkyrOGMACgkQkPq5zKsAFihwsgCeNx2FzpiTfK ZW5lQAmbFwXDKA
aAMAn1FY4VSmdjjdtxmxXYX04JqsemSt
=fnev
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20101005143827.GA24572@beastmaster.douma.cyso.net" >http://lists.debian.org/20101005143827.GA24572@beastmaster.douma.cyso.net

Central configuration storage
 

Hi!



On Tue, 2010-10-05 at 16:38 +0200, Nick Douma wrote:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm looking for a solution to store configuration files in a central
location. My first guess was to look at LDAP, and see if you can use
that for keeping track of configuration. The intended setup is a farm
of webservers, database servers and the like, on Debian and Windows
machines. The point is to keep the configuration in a central
location, so we can easily keep track of it and keep it seperated from
the servers themselves. The final goal is to be able to more easily
add new servers to the farm, that all serve the same data via
loadbalancing.

Is LDAP a suitable solution for the above problem? I started with
looking for a LDAP configuration storage method for Apache 2, but
didn't find anything. Can anyone point me in the right direction, or
maybe give me a starting point.


Depends on what configuration you want to store....








--

Karl E. Jørgensen

Geek

Central configuration storage
 

On 10/05/2010 09:38 AM, Nick Douma wrote:

Hi,

I'm looking for a solution to store configuration files in a central location. My first guess was to look at LDAP, and see if you can use that for keeping track of configuration. The intended setup is a farm of webservers, database servers and the like, on Debian and Windows machines. The point is to keep the configuration in a central location, so we can easily keep track of it and keep it seperated from the servers themselves. The final goal is to be able to more easily add new servers to the farm, that all serve the same data via loadbalancing.

Is LDAP a suitable solution for the above problem? I started with looking for a LDAP configuration storage method for Apache 2, but didn't find anything. Can anyone point me in the right direction, or maybe give me a starting point.



What about a sccs?

--
Seek truth from facts.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4CAB6028.3090800@cox.net">http://lists.debian.org/4CAB6028.3090800@cox.net

Central configuration storage
 

On Oct 5, 2010, at 10:38 AM, Nick Douma wrote:

> I'm looking for a solution to store configuration files in a central location. My first guess was to look at LDAP, and see if you can use that for keeping track of configuration.

Have a look at Puppet. I use LDAP to store information about systems, and then based on that information, Puppet pushes out (or modifies) configuration files, among other things. (LDAP support is built-in, so long as you add an objectClass and a couple of attributes to your schema.)

http://www.puppetlabs.com/

--
Rob McBroom
<http://www.skurfer.com/>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 579739DD-986B-4080-BF39-F349BF4CF59E@skurfer.com">http://lists.debian.org/579739DD-986B-4080-BF39-F349BF4CF59E@skurfer.com

Central configuration storage
 

Le mardi 05 octobre, Rob McBroom écrivit :

> On Oct 5, 2010, at 10:38 AM, Nick Douma wrote:
>
> > I'm looking for a solution to store configuration files in a central location. My first guess was to look at LDAP, and see if you can use that for keeping track of configuration.
>
> Have a look at Puppet. I use LDAP to store information about systems, and then based on that information, Puppet pushes out (or modifies) configuration files, among other things. (LDAP support is built-in, so long as you add an objectClass and a couple of attributes to your schema.)

Yes, I suggest also puppet.
It is far secure to have files on each servers, and have a something
keeping them updated.
Imagine if your LDAP server stops, even with slaves, I won't bet...

I see one problem, you speak about Windows...and there, puppet does not
support it (yet ?).
I think cfengine can support somewhat Windows.

Central configuration storage
 

Hi, Nick:

On Tuesday 05 October 2010 16:38:28 Nick Douma wrote:
> Hi,
>
> I'm looking for a solution to store configuration files in a central
> location. My first guess was to look at LDAP, and see if you can use that
> for keeping track of configuration. The intended setup is a farm of
> webservers, database servers and the like, on Debian and Windows machines.

Forget about that: Windows configuration management will need to go its own
way, and everything else will probably be able to share common procedures.

> The point is to keep the configuration in a central location, so we can
> easily keep track of it and keep it seperated from the servers themselves.
> The final goal is to be able to more easily add new servers to the farm,
> that all serve the same data via loadbalancing.

The answer is obvious then; you should use a tiered solution with the
following "bricks":
1) Automated installation (maybe FAI)
2) Configuration management (the likes of Puppet or CFengine)
3) Deployment orchestration (things like Controltier)

>
> Is LDAP a suitable solution for the above problem? I started with looking
> for a LDAP configuration storage method for Apache 2, but didn't find
> anything. Can anyone point me in the right direction, or maybe give me a
> starting point.

Make a Google search about "devops" and see documents like this one:
http://dev2ops.org/storage/downloads/FullyAutomatedProvisioning_Whitepaper.pdf

Cheers.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201010052148.15205.jesus.navarro@undominio.net">ht tp://lists.debian.org/201010052148.15205.jesus.navarro@undominio.net

Central configuration storage
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Thanks for all the great responses to my vague question :P. I think I
have a good starting point for my research on this subject.

If anyone has some more pointers, feel free to give them!

- - Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyrmuwACgkQkPq5zKsAFihI4QCeLKErjNaLjs xT3K7XNRF8SxBL
XA4AnigMKFPjq/hX1j7TP8rZrw7nKW1D
=ZMZf
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CAB9AEF.40702@nekoconeko.nl">http://lists.debian.org/4CAB9AEF.40702@nekoconeko.nl

Central configuration storage
 

Hi,
I tested puppet coupled with a version management system (git for me).
Seems pretty good for linux servers only. I don't know for windows servers.


Cheers

On 05/10/2010 15:38, Nick Douma wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm looking for a solution to store configuration files in a central location. My first guess was to look at LDAP, and see if you can use that for keeping track of configuration. The intended setup is a farm of webservers, database servers and the like, on Debian and Windows machines. The point is to keep the configuration in a central location, so we can easily keep track of it and keep it seperated from the servers themselves. The final goal is to be able to more easily add new servers to the farm, that all serve the same data via loadbalancing.

Is LDAP a suitable solution for the above problem? I started with looking for a LDAP configuration storage method for Apache 2, but didn't find anything. Can anyone point me in the right direction, or maybe give me a starting point.

Kind regards,

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkyrOGMACgkQkPq5zKsAFihwsgCeNx2FzpiTfK ZW5lQAmbFwXDKA
aAMAn1FY4VSmdjjdtxmxXYX04JqsemSt
=fnev
-----END PGP SIGNATURE-----






--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4CAC42B0.1070009@gmail.com">http://lists.debian.org/4CAC42B0.1070009@gmail.com

Central configuration storage
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

> I tested puppet coupled with a version management system (git for me).
> Seems pretty good for linux servers only. I don't know for windows servers.

I seem to notice that about puppet now too, after reading part of the
docs. The windows support is not yet mature (or present). For my
project, windows support is needed though.

- - Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkysR9sACgkQkPq5zKsAFigTVwCdEcyx28F8ux/0b1hxC4ugz2yy
COcAn3w71DkX1zgg7hHzWWSPChv5Ale9
=RMD/
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CAC47E0.5060409@nekoconeko.nl">http://lists.debian.org/4CAC47E0.5060409@nekoconeko.nl

Central configuration storage
 

On 05/10/10 15:38, Nick Douma wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm looking for a solution to store configuration files in a central location. My first guess was to look at LDAP, and see if you can use that for keeping track of configuration. The intended setup is a farm of webservers, database servers and the like, on Debian and Windows machines. The point is to keep the configuration in a central location, so we can easily keep track of it and keep it seperated from the servers themselves. The final goal is to be able to more easily add new servers to the farm, that all serve the same data via loadbalancing.

cfengine


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4CAC4DBE.5070005@sharescope.co.uk">http://lists.debian.org/4CAC4DBE.5070005@sharescope.co.uk