New goodies in the 1.0.x series

15 views
Skip to first unread message

Miquel Torres

unread,
Nov 14, 2011, 11:50:42 AM11/14/11
to littl...@googlegroups.com
Hi all,

there have been already 3 minor releases in the 1.0.x series, the
latest one (1.0.4) was uploaded to PyPI today.

The most important changes have been:

deploy_chef:
* Eivind added deploy_chef support for Arch Linux
* Cristi fixed rpm installation by using the FrameOS RBEL repository
* cleonte contributed deploy_chef support for CentOS/RHEL v6

Chef Solo configuration runs:
* Markus added operation "nodes_with_role", which configures all nodes
with the given role
* Markus refactored command line options: use "fix -h" instead of "fix -l"
* New command line option "--env"
* Markus added Chef Solo logs (found on /var/log/chef/solo.log)
* Automatic metadata.json regeneration from metadata.rb by using the
"knife metadata" command


There are several take aways:
* We can now use metadata.rb for our cookbooks (and directly use the
opscode repo), which is much more compact than the json version, and
LittleChef will automatically generate the metadata.json file if it
thinks you edited metadata.rb
* We can start using LittleChef more semantically. For example, let's
say we have a production deployment with several nodes with the roles
"shopping_frontend", "shopping_db", "shopping_lb". You can now
reconfigure all of them by typing
"fix --env=production nodes_with_role:shopping*"
which is pretty cool. No need to type a long list of node names.
* Chef Solo output for the last two runs is saved to the node's
/var/log/chef/solo.log and .../solo.log.1
* Command line options do not longer have the fabric syntax and are
now more standard looking. It felt out of place to type "fix debug
node:X". Now it is "fix --debug node:X"


So what are the next steps?
Using LittleChef semantically is something I would like to expand on,
so hearing from you how you are using it would be very helpful.
Another thing that is on the radar is parallel configuration of nodes,
which is now possible with the latest version of fabric. More on that
in another post.

Cheers!


Full Changelog:

Version 1.0.4 November 14, 2011
----------------------------------------
* NEW: Make "list_nodes" respect the --env option
* FIX: Accept --env=ENV in addition to --env ENV


Version 1.0.3 November 11, 2011
----------------------------------------

* NEW #15 (partly): Automatic metadata.json regeneration from metadata.rb
* NEW #63: cleonte contributed deploy_chef support for CentOS/RHEL v6
* NEW #70: Markus added Chef Solo logs (found on /var/log/chef/solo.log)
* NEW: Made debug and env proper command line options instead of fake
fabric tasks
* FIX #67: Andrew fixed `get_ips` for OSX by adding a regex to parse IPs
* FIX #66: Remove sensible data from a node after a configuration run


Version 1.0.2 October 11, 2011
----------------------------------------
* NEW #61: Added the command option "env"
* NEW #60: Don't force to define a password if ssh-config is used
* FIX #62: Cristi fixed rpm installation by using the FrameOS RBEL repository
* FIX: Automatic node data bag created items with the hostname as the name.
That can lead to name collitions. Now FQDN with underscores is used instead


Version 1.0.1 September 28, 2011
----------------------------------------
* NEW #58: Markus added operation "nodes_with_role", which configures
all nodes with
the given role
* FIX #57: Eivind added deploy_chef support for Arch Linux
* FIX: Transform "true" and "false" strings from into real True and False values
happens with default values from metadata.json attributes

Reply all
Reply to author
Forward
0 new messages