Use the console to create new node groups for each spoke or group of spokes in your infrastructure.

1. In the console, click Classification, and then click Add group. 
2. Specify options for the new node group, and then click Add.
   For example, create a group that represents a Sydney datacenter.

   Option	Value
   Parent name	PE MCollective
   Group name	Sydney_datacenter
   Environment	Select the environment agents are in.
   Environment group	Do not select this option.

3. Click the link to Add membership rules, classes, and variables.
4. On the Rules tab, create a rule to add agents to this group, then click Add rule and commit changes.

   For example, create a rule that matches nodes in the Sydney datacenter.

   Option	Value
   Fact	data_center
   Operator	=
   Value	syd

5. On the Configuration tab in the Add new class field, enter puppet_enterprise::profile::mcollective::agent and click Add class.
6. In the puppet_enterprise::profile::mcollective agent class, specify parameters and then commit changes.

   Parameter	Value
   activemq_brokers	Names of the spokes you want to classify. Hubs must be entered as an array.

7. Run Puppet on the ActiveMQ hub and spokes, including the master or master of masters, and on any agents.

If you do not want to use the console to create new node groups for each spoke or groups of spokes in your infrastructure, you can use Hiera with automatic data binding instead.

1. On the master, edit your Hiera config file (/etc/puppetlabs/puppet/hiera.yaml) so that it contains, as part of the hierarchy, the custom fact you're using to classify spokes.
   For example, add the custom data_center fact to the hierarchy.

   #hiera.yaml
      ---
       :backends:
            - eyaml
            - yaml
       :hierarchy:
            - "%{clientcert}"
            - "%{data_center}"
            - global
   
   
        :yaml:
        :datadir: "/etc/puppetlabs/code/environments/%{environment}/hieradata"

2. On the master, add Hiera data files to map ActiveMQ spokes to custom facts.
   For example, map spokes to Sydney and Portland datacenters using the custom data_center fact.

   1. Navigate to /etc/puppetlabs/code/environments/production/hieradata/, and create a file called syd.yaml that contains the content:

      ---
      puppet_enterprise::profile::mcollective::agent::activemq_brokers:
         - 'SPOKE.SYD.EXAMPLE.COM'
      

   2. Still in the hieradata directory, create a file called pdx.yaml that contains the content:

      ---
      puppet_enterprise::profile::mcollective::agent::activemq_brokers:
          - 'SPOKE.PDX.EXAMPLE.COM'

3. Verify the custom fact on the end node.

   For example, running facter data_center on a node classified in the Sydney datacenter returns the value syd. 

4. Verify that Hiera picks up the expected value for the ActiveMQ spoke given the appropriate parameters.
   For example, on the master, running this command returns the value of the Sydney broker hostname.

   hiera puppet_enterprise::profile::mcollective::agent::activemq_brokers data_center=syd environment=production

5. On the master, reload the pe-puppetserver service: sudo service pe-puppetserver reload.
6. Run Puppet on the ActiveMQ hub and spokes, including the master or master of masters, and on any agents.