Browse files

Tag version 1.0.0 !

  • Loading branch information...
1 parent 038def8 commit 17de51257c1a312ab293b042ff1df0d7f9d298ae @tobami committed Sep 21, 2011
Showing with 30 additions and 25 deletions.
  1. +9 −4 CHANGELOG
  2. +13 −8 README.md
  3. +1 −1 littlechef/version.py
  4. +7 −12 setup.py
View
13 CHANGELOG
@@ -2,7 +2,7 @@
LittleChef Changelog
====================
-Unreleased
+Version 1.0.0 September 21, 2011
----------------------------------------
* NEW #46: Markus implemented node synching using rsync instead of data upload,
substantially speeding up node configuration runs. All cookbooks are now
@@ -11,14 +11,19 @@ Unreleased
* NEW #16: Automatically add a "node" data bag, which allows for node search.
It contains everything defined in each nodes/mynode.json file, plus "recipes"
(expanded recipe list), "role" (roles in the run_list),
- "roles" (expanded role list) and merged attributes (from cookbook, node and roles)
+ "roles" (expanded role list), merged attributes (from cookbook, node and roles)
+ and some Chef automatic attributes
+* NEW: Add ipaddress attribute to a node after a configuration run. That way the IP
+ of that node will be available in the node data bag and thus in the node search
* NEW #53: tow added a patch that allows to override distro detection when installing
Chef Solo
* NEW #55: Markus added a library file that allows to set "chef_environment" in a
role or node attribute
+* NEW: Changed "cook" command to "fix", so that we don't collide with the executable
+ name of an existing package. This was done so that LittleChef can be distro-packaged
* NEW #54: Multi-node execution: a list of nodes to be configured can now be given.
- Order will be preserved
-* NEW: Removed "configure" command. It will be assumed to be the default action if
+ The nodes will be configured preserving order
+* NEW: Removed "configure" command. It will be assumed to be the desired action if
no other command is given. Just typing "fix node:X" will configure node X
View
21 README.md
@@ -6,7 +6,7 @@ With LittleChef you will be able to get started more quickly cooking with [Chef]
You may think of this like a pocket Chef that doesn't need a Chef Server. Just your
local kitchen with all your cookbooks, roles data bags and nodes, which will get rsynced
-to a node each time you start a Chef Solo configuration run with the bundled 'fix'
+to a node each time you start a Chef Solo configuration run with the bundled `fix`
command.
It also adds features to Chef Solo that are currently only available for Chef Server users: data bag search, and node search.
@@ -16,17 +16,22 @@ It also adds features to Chef Solo that are currently only available for Chef Se
It all starts in the **kitchen**, which you should keep under version control:
* `auth.cfg`: Authentication information needed to be able to connect to the nodes
-* `nodes/`: After recipes are run on [Nodes][], their configuration is stored here. You
-can manually edit them or even add new ones. The name of a node should be its fqdn
+* `nodes/`: After recipes are run on [Nodes][], their configuration is stored here in
+JSON format. You can manually edit them or even add new ones. The name of a node
+should be its FQDN
* `cookbooks/`: This will be your [Cookbooks][] repository
* `site-cookbooks/`: Here you can override upstream cookbooks (Opscode's, for example)
-* `roles/`: Where Chef [Roles][] are defined
+* `roles/`: Where Chef [Roles][] are defined in JSON
* `data_bags/`: Chef [Data Bags][]. JSON databag items. Search is supported
-Whenever you apply a recipe to a node, all cookbooks, roles and databags are rsynced to that node, to the `/tmp/chef-solo/` directory. A node.json file gets created on the fly and uploaded, and Chef Solo gets executed at the remote node, using node.json as the node configuration and the pre-installed solo.rb for Chef Solo configuration.
+Whenever you start a Chef Solo configuration run with the local `fix` command, all
+cookbooks, roles and databags are rsynced to the `/tmp/chef-solo/` directory, together
+with the `/etc/chef/node.json` and `/etc/chef/solo.rb` files, and chef-solo is executed
+at the remote node.
-The result is that you can then configure your nodes exactly when and how you want by
-using the `fix` command, all without needing a Chef Server. And all your infrastructure, including your nodes, will be in code, revision controlled.
+The result is that you can configure your nodes exactly when and how you want, all
+without needing a Chef Server. And all your infrastructure, including your nodes, will
+be in code, revision controlled.
#### Data bag Search ####
@@ -38,7 +43,7 @@ following example: `search(:users, "married:true AND age:35")`
#### Environments ####
-Chef Solo does not support Environments, but, similarly as in the search case, LittleChef will automatically add a cookbook library that will let you define `chef_environment`
+Chef Solo does not support Environments, but, similarly to the search case, LittleChef will automatically add a cookbook library that will let you define `chef_environment`
in a role or node.
#### Node Search ####
View
2 littlechef/version.py
@@ -1,2 +1,2 @@
-VERSION = (1, 0, '0beta')
+VERSION = (1, 0, 0)
version = ".".join([str(x) for x in VERSION])
View
19 setup.py
@@ -28,28 +28,23 @@
test_suite='nose.collector',
classifiers=[
"Programming Language :: Python",
- "Development Status :: 4 - Beta",
+ "Development Status :: 5 - Production/Stable ",
"Environment :: Console",
"Intended Audience :: Developers",
"License :: OSI Approved :: Apache Software License",
"Operating System :: OS Independent",
'Topic :: System :: Systems Administration',
],
long_description="""\
-Cook with Chef without Chef Server
+Cook with Chef without a Chef Server
-------------------------------------
-With LittleChef you will get all you need to start cooking with Chef_.
+With LittleChef you will be able to get started more quickly cooking with Chef_, the excellent Configuration Management System.
-It works as follows: Whenever you apply a recipe to a node, all needed
-cookbooks and its dependencies are gzipped and uploaded to that node. A
-node.json file gets created on the fly and uploaded, and Chef Solo gets
-executed at the remote node, using node.json as the node configuration and the
-pre-installed solo.rb for Chef Solo configuration. Cookbooks, data bags and roles
-are configured to be found at (/tmp/chef-solo/).
+You will just need your local (preferably version controled) kitchen with all your
+cookbooks, roles data bags and nodes, which will get rsynced to a node each time
+you start a Chef Solo configuration run with the bundled 'fix' command.
-The result is that you can play as often with your recipes and nodes as you
-want, without having to worry about a central Chef repository, Chef server nor
-anything else. You are immediately ready to cook.
+It also adds features to Chef Solo that are currently only available for Chef Server users: data bag search, and node search.
.. _Chef: http://wiki.opscode.com/display/chef/Home
"""

0 comments on commit 17de512

Please sign in to comment.