can someone please provide me a way to set up three deployment servers? I want the first one to send to two deployment servers and once app is deployed it goes to the deployment server folder of those two servers instead of app, so it can also push those apps to respective clients. I did this before but very long time and can't seem to figure out how I did it.
Thanks
You need the targetRepositoryLocation in serverclass.conf to tell your main DS to push apps to your secondary DSes in the deployment-apps folder:
targetRepositoryLocation = <path>
* The location on the deployment client where to install the apps defined
for this Deployment Server.
* If this value is unset, or set to empty, the repositoryLocation path is used.
* Useful only with complex (for example, tiered) deployment strategies.
* Defaults to $SPLUNK_HOME/etc/apps, the live
configuration directory for a Splunk instance.
So you'd have a serverclass to deploy the deployment-apps to the other DSes in deployment-apps
, and another serverclass to deploy the serverclass.conf to the DSes in etc/apps
.
This recent answers post has additional details. The accepted answer says targetRepositoryLocation is buggy, but an answer below shows it in practice. We did this exact thing in Splunk training today, and it is valid and supported.
You need the targetRepositoryLocation in serverclass.conf to tell your main DS to push apps to your secondary DSes in the deployment-apps folder:
targetRepositoryLocation = <path>
* The location on the deployment client where to install the apps defined
for this Deployment Server.
* If this value is unset, or set to empty, the repositoryLocation path is used.
* Useful only with complex (for example, tiered) deployment strategies.
* Defaults to $SPLUNK_HOME/etc/apps, the live
configuration directory for a Splunk instance.
So you'd have a serverclass to deploy the deployment-apps to the other DSes in deployment-apps
, and another serverclass to deploy the serverclass.conf to the DSes in etc/apps
.
This recent answers post has additional details. The accepted answer says targetRepositoryLocation is buggy, but an answer below shows it in practice. We did this exact thing in Splunk training today, and it is valid and supported.
Thank You @micahkemp will give this a try