Re: [Fab-user] fabric-recipes

[Prateek Sureka]

Hi Jan,

In the original design, config.py is supposed to be user editable (kind of like fabricrc). Granted that the current design and documentation doesn't make that obvious - your call for an externalized configuration is valid in any case.

I think we can use ConfigParser instead of YAML. Its sufficient for our needs and part of the standard library and there really is no syntax to learn.

I'll push some code over the weekend (been really busy at work) once I get our test infrastructure up and running.

Please advise where we can take this discussion if this group is not the right place.

Prateek

On 18-Apr-2012, at 2:24 AM, Jan Vlčinský (TamTam Research) wrote:

Hi

I like it.

While testing it (briefly), obviously many tests failed, as IPs etc. are hardcoded and there are some assumptions done (like minimal set of service and tools already present at machines).

In past I created set of fab tools for my own use, structured it to tree of service names to care about and found, it would be practical to externalize configuration parameters from the code.

So I decided to use yaml configuration format (unfortunately this adds one more dependency, but e.g. Google App Engine did exactly the same decission and I understand, why is this well readable format preferred).

Just an idea.

Question: is this list the best place for ongoing discussion about this?

Jan

Ing. Jan Vlčinský
TamTam Research s.r.o.
Slunečnicová 338/3, 734 01 Karviná Ráj, Czech Republic
tel: +420-597 602 024; mob: +420-608 979 040
skype: janvlcinsky; GoogleTalk: address@hidden
http://cz.linkedin.com/in/vlcinsky

On 15 April 2012 22:01, Prateek Sureka <address@hidden> wrote:

Hi all,

I've been working on a small set of recipes based on fabric. I use them to manage my organization's network of debian/ubuntu hosts.

The key objectives of the project are:

* Easy to use (no installation, little to no dependencies - except Python+fabric)

* Idempotency

The recipes currently available are:

* apt - ensure a package is installed/removed on all hosts

* cups_client - ensure all hosts are pointing to a specified cups server

* hosts - ensure the hostname of each host is set correctly

* lsof - query the open ports on all hosts

* ntp_client - ensure that the clock on all hosts are sync'd to a central time server and timezone is set correctly

* service - ensure that a particular service is running/stopped/restarted on all hosts

* snmp - ensure that all hosts are set up for snmp using the same community string

* syslog_client - ensure that all hosts are reporting syslog to a centralized syslog server (works great with splunk!)

* web - ensure that an nginx based webserver is correctly proxying a set of internal sites (e.g. webmin/cups server/phpmyadmin) using sub-domains

* webmin - ensure that webmin is correctly deployed on each host

* whois - use your firewall's arp cache and iptraf mac to hostname database to resolve ip addresses and mac addresses to hostname - useful on a DHCP network.

For now it only works on Debian/Ubuntu but I plan to (with your help) support other flavors of *nix, OSX and Windows as well.

Wishlist:

* Ability to remotely run anti-virus scans and quarantine infected hosts using mac address filtering on the firewall

* Automatically configure new hosts on the ldap server (user account as well as asset record) including pam_ldap authentication.

* Automount home directories (add a folder with links to commonly used applications e.g. intranet/crm/hrm

* Automatically backup (ensure certain folders are backed up) to offsite host.

* Any more you can think of?

You can find it at:

https://github.com/surekap/fabric-recipes

--
Prateek Sureka
address@hidden

_______________________________________________
Fab-user mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fab-user