Rudder

Rudder agent 4.2.2.release (CFEngine Core 3.10.2)

Nicolas CHARLES wrote:

Proposing a workaround in the PR, for branch 4.2
It has two parts:

1. on the node side, at first installation, there is the script set_proxy.sh that defines the proxy for the node, and sends the inventory
2. on the server side, it's a patch in techniques, which, when the node property 'inventory_proxy' is defined, will set the proxy for the node

Nicolas, just a question. Does it mean that the set_proxy.sh exists ? If it does I don't understand how to get it.. Ready to test. Many thanx in advance. Impressed by your reactivity. Paul

Paul,

Code for workaround is submitted in the attached pull request.

The script set_proxy.sh can be downloaded at https://raw.githubusercontent.com/ncharles/rudder-techniques/2b105439a7046c676a8ae42d5989390f4f18b836/tools/set_proxy.sh - you can download it on the nodes, and use it to set the proxy for the initial promises (so when the node hasn't yet sent its inventory to the server)
To check its usage, you can run the command set_proxy.sh usage

You also have a patch to apply on the Rudder server, for continuous operations. It will ensure that the nodes will be able to send their inventory once they are managed by Rudder, with the proxy correctly defined.
The easiest way to apply this patch is to replace the file /var/rudder/configuration-repository/techniques/system/inventory/1.0/fusionAgent.st by the file https://raw.githubusercontent.com/ncharles/rudder-techniques/2b105439a7046c676a8ae42d5989390f4f18b836/techniques/system/inventory/1.0/fusionAgent.st , and then to commit this file into rudder git repository. The procedure is:

cd /var/rudder/configuration-repository/techniques/system/inventory/1.0/
git add fusionAgent.st
git commit -m "Updating inventory code to be able to set a proxy" 
rudder server reload-techniques

It should regenerate policies for all nodes, and you'll be able to set the proxy for each node by setting a node property (in the node details /properties tab) with the name inventory_proxy and the value being proxyname:proxyport
Note that you can also automate the definition of this node property using the rudder API, as described in http://www.rudder-project.org/rudder-api-doc/#api-Nodes-updateNode

Finally, this is a workaround, the actual implementation might be slightly different.

Don't hesitate to ask if you need more details on this, or help applying these patches

Dear Ruuder team,
Only one word. FANTASTIC !
We applied the patch on the server and we integrated the workaround in our automation engine.
All inventories have been sent.
Our Big picture is now BIGGER !!
Thanx again for you support and reactivity.
Let us run the meetup now !!
Pau