[etch-users] Etch 3.17.0 released

[Jason H. <jh...@ap...>]

Client
------

ticket:8 Add support for an /etc/etch.conf config file to the client. This
allows users to set the etch server, the directory to use for local
configuration (if desired instead of using a server), and the SSH key
permanently. These were previously only configurable on the command line. The
config file also allows the user to set a PATH that will be in force for any
commands etch runs. The PATH was previously hard-coded in the client.

Change the worker_processes setting from 20 to 8 in the unicorn.rb config file
included with the server. 20 workers was proving too much for our dedicated
etch servers with 8 GB of RAM and thus seemed an inappropriate default for
general usage. We've changed our servers to 16.

Increase the sqlite timeout in the production section of the server's
database.yml config file from 5s to 20s. Users reported sqlite timeouts under
heavy load at the 5s setting. Since usage is primarily not interactive a
higher timeout allows more clients to be served from a given server.

Update the example nodetagger and nodegrouper scripts in the
etchserver-samples/nventory/ directory to include a number of enhancements.

Enhance etch_to_trunk script with additional options including the ability to
specify the username and timezone.

Set the postinstall/postremove scripts to be executable when building
the Solaris packages.

Update dependencies for Debian package.  These were copied from the tpkg 
Debian package which is more widely used, and seem appropriate for etch 
as well.

Server
------

NOTE:  The server now requires the searchlogic gem and rails 2.3.10

Add searchlogic searching to the controllers in the server that didn't have
search functionality. The clients and results controllers still have their
homegrown search functionality that will need to be migrated to searchlogic at
some point.

Update to rails 2.3.10.  Apparently 2.3.8 is incompatible with newer
versions of the i18n gem and I started running into that
incompatibility.  That incompatibility was fixed in 2.3.9.

Added basic views in the server for the models that didn't have any views.

ticket:10 Fix the etch home link in the upper left of the web UI so that it
obeys RAILS_RELATIVE_URL_ROOT.