can a HF be a deployment server & client ?

[Esky73]

In a scenario where we have 2 x HF's that send data to a cloud instance.

One of the HF's is a deployment server - can this also be a client ? so we can push out apps to both the remote HF and the local HF ?

deploymentclient.conf
[target-broker:deploymentServer]
targetUri = localhost:8089

doesn't seem to work.

[MuS]

Hi Esky73,

Yes, it can be done - but it is tricky and you need to plan this carefully.

Basically on the first Deployment server you change the repositoryLocation option http://docs.splunk.com/Documentation/Splunk/latest/Updating/Useserverclass.conf#Non-filtering_attrib... so apps will not be placed into etc/apps (default directory) but in the etc/deployment-apps directory.

On the second Deployment server you can mange the DS clients as usual.

Test it before put this into production!

Hope this helps and makes sense ...

cheers, MuS

[Esky73]

Cheers MuS

We only have the one DS

Just seeking clarity - in a DS > DC scenario you do want the server to push out from deployment-apps to /etc/apps.
So on the instance where it is both a DS and a DC i do config changes in the deployment-apps folder and thats pushed across to /etc/apps locally.

[MuS]

Okay, I miss understood your question!
A DS should never be its own DC - This will / can produce wormholes and Loki will unleash his army of doom over your Splunk 😉 No really, you should not do this.

Easiest way to overcome this use case would be a cronjob which copies your apps from etc/deployment-apps to etc/apps

cheers, MuS

[Esky73]

OK Cheers.

[MuS]

Thanks for the points, but if you click the ^ symbol it will upvote the answer or comment and will not take points away from you 😉

[aakwah]

Indeed 🙂