Rudder tools

As we don't have a migration path from 2.11 to 3.2, we took the decision to make an incompatible change in inventory file format from Rudder 2.11 to Rudder 3.2.
This is OK, since if someone upgrade from 2.11 to 3.0 or 3.1, and then to 3.2 (which are the only supported path), the file format evolution is compatible.

But in certain case, an user may want to upload inventory file produced by a Rudde 2.11 agent into a Rudder 3.2 server.

That won't work with the following kind of errors:

[2016-02-11 19:00:26] ERROR com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Error when trying to parse inventory 
<- Can't parse the input inventory, aborting 
<- Error when post processing report with 'post_process_inventory:check_consistency', abort 
<- Missing hostname tags (RUDDER∕HOSTNAME and OPERATINGSYSTEM/FQDN) in report. Having at least one of Those tags is mandatory.

So we need to have some script to transform 2.11 inventory file into 3.2. It may not work in certain case, but for the majority of them, it is quite easy to do.