[CentralOH] Kokki, or, Server Management

[Morgan Goose]

Issac, 

Interestingly enough, that project was started in the #fabric room on freenode
and has a room a few months ago IIRC.  It's utalizing fabric as it's underlying
communication library, and ends up being a loose set of functions to "organize"
some fabric stuff into good bits for package management.

I've not used it, and most likely wont, as I feel a one time start script like
that can be implemented with a good use of a cloud api provider, and some
simple lines of bash for the apt-gets.

If you pop into either channel I think bitprophet (the main fabric dev) uses
some cloud'y stuff. And the kokki dev may be lurking in there, or at lease in
the #kokki room.

goose


On Fri, Nov 12, 2010 at 09:43:30AM -0500, Issac Kelly wrote:
>    I finally got all of my new projects switched over to fabric + git for
>    deployment. �The big missing piece now is actually setting up the box.
>    There seem to be a few big projects in the FOSS world (Puppet and Chef are
>    quite popular in ruby) and then there's this outlier that, even from my
>    Python friends I've heard noting about ([1]http://samuelks.com/kokki/)
>    have any of you used this? �What do you use for deployment management or
>    server management in general?
> 
>    My needs are generally very very basic:
> 
>    ) Fire up an instance of Ubuntu (Latest LTS) on [Rackspace|AWS|Slicehost]
>    ) Add general dev tools (build-essential, git-core, svn, mercurial
>    ) Add my Python toolchain (python, virtualenv, virtualenvwrapper, pil)
>    ) Add Postgres [sometimes GDAL, PostGIS ...]
>    ) Add�psycopg2
>    ) Add nginx // supervisord
>    ) (And now, run fab locally to deploy something)
>    I would like to automate everything except the last step
> 
> References
> 
>    Visible links
>    1. http://samuelks.com/kokki/

> _______________________________________________
> CentralOH mailing list
> CentralOH at python.org
> http://mail.python.org/mailman/listinfo/centraloh

---end quoted text---