CHANGELOG.md in cluster_chef-knife-3.0.10 vs CHANGELOG.md in cluster_chef-knife-3.0.11

@@ -1,4 +1,18 @@
+## v3.0.11: We Raid at Dawn
+
+* You can now assemble raid groups in the cluster definition:
+  - node metadata instructing the volumes recipe to build the raid volume
+  - marks the component volumes as non-mountable, in the appropriate raid group, etc
+* Changed the order of `cluster_role` and `facet_role` in the run list. It now goes:
+  - `:first`  roles (cluster then facet)
+  - `:normal` roles (cluster then facet)
+  - special roles: `cluster_role` then `facet_role`
+  - `:last` roles (cluster then facet)
+* knife cluster launch uses ClusterBootstrap, not knife's vanilla bootstrap.
+* can now do group('group_that_wants').authorized_by_group('group_that_grants') so that in cluster A I can request access to cluster B without gaining its group myself.
+* push the organization (if set) into the node metadata
+
 ## v3.0.10: Cloud fixes
 
 * security groups are now created/updated in knife cluster sync. This can't help you apply then to a node afer launch though -- nothing can, the API doesn't allow it.
 * clusters now all refer to an AMI named `cluster_chef-natty` by default, and to customizable roles `org_base`, `org_final` and `org_users` (where `org_base` has a role_implication for membership in the systemwide `org_base` security group)
 * default facet instances is now 1 who knows why it wasn't always 1.