
=====
Usage
=====

Reclass is an external node classifier (ENC) as can be used with automation
tools, such as Puppet, Salt, and Ansible. It is also a stand-alone tool for
merging data sources recursively.

Sample Metadata
===============

Install sources from [repository, git, pip]:

.. code-block:: yaml

    salt:
      source:
        engine: pkg
    ...
      source:
        engine: git
        repo: git+https://github.com/salt-formulas/reclass
        branch: master
    ...
      source:
        engine: pip
    ...

If reclass is pre-installed, set the engine to None to avoid updates:

.. code-block:: yaml

    salt:
      source:
        engine: None

Reclass storage with data fetched from git:

.. code-block:: yaml

   See tests/pillar/storage_git.sls

Reclass storage with local data source:

.. code-block:: yaml

   See tests/pillar/storage_local.sls

Reclass storage with archive data source:

.. code-block:: yaml

   See tests/pillar/storage_archive.sls

Reclass storage with archive data source with content hash check:

.. code-block:: yaml

   See tests/pillar/storage_archive_public.sls

Reclass model with single node definition:

.. code-block:: yaml

   See tests/pillar/generate_single.sls

Reclass model with multiple node defined:

.. code-block:: yaml

   See tests/pillar/generate_multi.sls

Reclass model with multiple node defined and interpolation enabled:

.. code-block:: yaml

   See tests/pillar/generate_multi_interpolate.sls

Reclass storage with simple class mappings:

.. code-block:: yaml

   See tests/pillar/class_mapping.sls

Reclass models with dynamic node classification

.. code-block:: yaml

   See tests/pillar/node_classify.sls

Classify node after creation and unclassify on node deletion:

.. code-block:: yaml

    salt:
      master:
        reactor:
          reclass/minion/classify:
          - salt://reclass/reactor/node_register.sls
          reclass/minion/declassify:
          - salt://reclass/reactor/node_unregister.sls

Event to trigger the node classification:

.. code-block:: bash

    salt-call event.send 'reclass/minion/classify' "{'node_master_ip': '$config_host', 'node_ip': '${node_ip}', 'node_domain': '$node_domain', 'node_cluster': '$node_cluster', 'node_hostname': '$node_hostname', 'node_os': '$node_os'}"

.. note::

    You can send any parameters in the event payload, all will be checked
    against dynamic node classification conditions.

    Both actions will use the minion ID as the node_name to be updated.

Confirmation of node classification

Currently, Salt does not allow getting confirmation on minion upon successful
reactor execution on event. However, there can be issues with reactor in Salt
2017.7 (https://github.com/saltstack/salt/issues/47539) or reactor register
state can fail if pillar failed to render, so node registration confirmation
may be needed. To enable this functionality, add the
``node_confirm_registration`` parameter to event data with value ``true``:

.. code-block:: bash

   salt-call event.send 'reclass/minion/classify' "{'node_master_ip': '$config_host', 'node_ip': '${node_ip}', 'node_domain': '$node_domain', 'node_cluster': '$node_cluster', 'node_hostname': '$node_hostname', 'node_os': '$node_os', node_confirm_registration: true}"

Then on minion side execute:

.. code-block:: bash

   salt-call mine.get 'salt:master' ${minion_id}_classified pillar

If ``true`` is returned, then registration has passed successfully.


Event to trigger the node declassification:

.. code-block:: bash

   salt-call event.send 'reclass/minion/declassify'

Nodes definitions generator
===========================

Generate nodes definitions by running:

.. code-block:: bash

    salt-call state.sls reclass.storage -l debug

Remove unnecessary files from nodes/_generated:

.. code-block:: yaml

    reclass:
      storage:
        reclass_nodes_cleanup: true

Static node definition:

.. code-block:: yaml

    reclass:
      storage:
        enabled: true
        node:
          openstack_benchmark_node01:
            classes:
            - cluster.example.openstack.benchmark
            domain: example.com
            name: bmk01
            params:
              linux_system_codename: xenial
              salt_master_host: 192.168.0.253
              single_address: 192.168.2.95

Multiple nodes definitions (using generator):

.. code-block:: yaml

    reclass:
      storage:
        enabled: true
        node:
          openstack_compute_rack01:
            classes:
            - cluster.example.openstack.compute
            domain: example.com
            name: cmp<<count>>
            params:
              linux_system_codename: xenial
              salt_master_host: 192.168.0.253
            repeat:
              start: 1
              count: 50
              digits: 3
              params:
                single_address:
                  start: 101
                  value: 192.168.2.<<count>>

Multiple nodes definitions (using generator) with IP address comprehension.
Ranges are named and formatting symbol of the same name is replaced by IP
address from the corresponding range.
Some extra references supported, as:
  COLON_SYMBOL_FOR_FUTURE_REFERENCE = ':'
Which will be replaced during reclass process

.. code-block:: yaml

    reclass:
      storage:
        enabled: true
        node:
          openstack_compute_rack01:
            classes:
            - cluster.example.openstack.compute
            domain: example.com
            name: cmp<<count>>
            params:
              linux_system_codename: xenial
              salt_master_host: 192.168.0.253
            repeat:
              ip_ranges:
                single_address: '172.16.10.97-172.16.10.98'
                tenant_address: '172.16.20.97-172.16.20.98'
              network_ranges:
                sriov_address: '10.10.0.1/24-10.10.50.1/24'
              start: 1
              count: 50
              digits: 3
              params:
                single_address:
                  start: 101
                  value: 192.168.2.<<single_address>>
                tenant_address:
                  start: 101
                  value: 192.168.2.<<tenant_address>>
                somevalue:
                  start: 101
                  value: 192.168.2.<<tenant_address>>COLON_SYMBOL_FOR_FUTURE_REFERENCEtestme

Read more
=========

* http://reclass.pantsfullofunix.net/index.html
* http://reclass.pantsfullofunix.net/operations.html