#11

Author: fabriziopandini

CHANGELOG.md

@@ -40,8 +40,9 @@ ansible_group_vars_path and ansible_host_vars_path are not supported anymore
 
 * Minor fix
 
-# 0.8.0 (November 16, 2016)
+# 0.7.2 (November 16, 2016)
 
 * issues #11 Allow management of Ansible vars for all hosts
 * issues #9 Create group_vars and host_vars directory only if necessary
 
+* breacking change: custom group of groups all_groups:children removed. Insteal use all (automatically created by ansible)

doc/declarative.md

@@ -308,13 +308,13 @@ Group vars can be set to literal value or to Jinja2 value generators, that will
 - **context_vars** see below
 - **nodes**, list of nodes in the ansible_group to which the group_vars belong
 
-Additionally it is possible to set variables for all groups/all hosts, by setting vars for the pre-defined `all_groups:children` group of groups:
+Additionally it is possible to set variables for all groups/all hosts, by setting vars for the pre-defined `all` group of groups:
 
 ```yaml
 kubernetes:
   ...
   ansible_group_vars:
-    all_groups:children:
+    all:
       var1: ...
   ...
 ```
@@ -397,7 +397,7 @@ Context vars can be set to literal value or to Jinja2 value generators, that wil
 
 > Context_vars generator are always executed before group_vars and host_vars generators; the resulting context, is given in input to group_vars and host_vars generators.
 
-> In addition to context vars for groups, it is possible to create context_vars for all groups/all hosts, by setting vars for the pre-defined `all_groups:children` group of groups; in this case, intuitively, the list of nodes whitin the context contains all the nodes.
+> In addition to context vars for groups, it is possible to create context_vars for all groups/all hosts, by setting vars for the pre-defined `all` group of groups; in this case, intuitively, the list of nodes whitin the context contains all the nodes.
 
 Then, you can use the above context var when generating group_vars for host vars.
 
@@ -414,13 +414,13 @@ kubernetes:
       - kb8-minions
 
   ansible_context_vars:
-    all_groups:children:
+    all:
       var0: "{{ nodes | count }}"
     kb8-master:
       var1: "{{ nodes | count }}"
 
   ansible_group_vars:
-    all_groups:children:
+    all:
       var0_from_context: "{{ context['var0'] }}"
     kb8-master:
       var1_from_context: "{{ context['var1'] }}"
@@ -430,9 +430,7 @@ kubernetes:
 
 A useful ansible inventory feature is [group of groups](http://docs.ansible.com/ansible/intro_inventory.html#hosts-and-groups).
 
-By default vagrant-compose will generate a group named `[all_groups:children]` with all the ansible_groups defined in cluster configuration; however:
-- you cannot rename all_groups
-- you cannot exclude any ansible group from all_groups.
+By default ansible has a group named `[all]` with all nodes in the cluster.
 
 If you need higher control on groups of groups you can simply add a new item to the variable `config.cluster.ansible_groups` before creating nodes.
 

doc/programmatic.md

@@ -329,12 +329,12 @@ config.cluster.compose('test') do |c|
 end
 ```
 
-Additionally, it is possible to set variables for all groups/all hosts, by setting vars for the pre-defined `all_groups:children` group of groups:
+Additionally, it is possible to set variables for all groups/all hosts, by setting vars for the pre-defined `all` group of groups:
 
 ``` ruby
 config.cluster.compose('test') do |c|
   ...
-  c.ansible_group_vars['all_groups:childrenr'] = lambda { |context, nodes|
+  c.ansible_group_vars['all'] = lambda { |context, nodes|
     return { 'var0' => nodes.length }
   }
   ...
@@ -391,7 +391,7 @@ end
 
 > Context_vars generator are always executed before group_vars and host_vars generators; the resulting context, is given in input to group_vars and host_vars generators.
 
-> In addition to context vars for groups, it is possible to create context_vars for all groups/all hosts, by setting vars for the pre-defined `all_groups:children` group of groups; in this case, intuitively, the list of nodes whitin the context contains all the nodes.
+> In addition to context vars for groups, it is possible to create context_vars for all groups/all hosts, by setting vars for the pre-defined `all` group of groups; in this case, intuitively, the list of nodes whitin the context contains all the nodes.
 
 Then, you can use the above context var when generating group_vars for nodes in the `consul-agent` group.
 
@@ -411,9 +411,7 @@ end
 ### Group of groups
 A useful ansible inventory feature is [group of groups](http://docs.ansible.com/ansible/intro_inventory.html#hosts-and-groups).
 
-By default vagrant-compose will generate a group named `[all_groups:children]` with all the ansible_groups defined in cluster configuration; however:
-- you cannot rename all_groups
-- you cannot exclude any ansible group from all_groups.
+By default ansible has a group named `[all]` with all the nodes defined in cluster configuration.
 
 If you need higher control on groups of groups you can simply add a new item to the variable `config.cluster.ansible_groups` before creating nodes.
 

lib/vagrant/compose/config.rb

@@ -62,8 +62,6 @@ def filterInventory(inventory)
           end
         end
 
-        ansible_groups['all_groups:children'] = ansible_groups.keys
-
         return ansible_groups
       end
 

lib/vagrant/compose/programmatic/cluster.rb

@@ -94,7 +94,7 @@ def compose
               ansible_groups[ansible_group] << node
             end
           end
-          extended_ansible_groups = ansible_groups.merge({'all_groups:children' => nodes})
+          extended_ansible_groups = ansible_groups.merge({'all' => nodes})
 
           ## Fase2: Configurazione provisioning del cluster via Ansible
           # Ogni nodo diventerà una vm su cui sarà fatto il provisioning, ovvero un host nell'inventory di ansible

lib/vagrant/compose/version.rb

@@ -1,5 +1,5 @@
 module Vagrant
   module Compose
-    VERSION = "0.8.0"
+    VERSION = "0.7.2"
   end
 end