how to set up global deployment server

[vw5qb73]

In my existing landscape, i have 10+ deployment servers that caters to the deployments of varous Datacenter. We have configured 1 deployment server per data center.

We are finding it difficult to ensure consistent configurations of apps across various Datacenter deployment servers, especially some of the deployment servers are not under any puppet/chef control.

We need a central deployment server that can push the configurations to each of the DC's respective deployment server

Let us know how to proceed with the set up instructions, design and other factors to be considered

[javiergn · Accepted solution]

Hi,

I did have a 2-tier deployment server on my previous company mainly because of security reasons. There was a global one and then another one inside a secure VLAN. If configured properly it'll save you a lot of time but keep in mind is going to make your configuration changes a bit more complicated to perform.

Anyway, this is doable and there's an example here (see section at the bottom called "Example: How to propagate apps from Primary to Secondary Deployment Server"):

http://wiki.splunk.com/Deploy:DeploymentServer

Some more information here: https://answers.splunk.com/answers/37649/multiple-deployment-servers-configuration.html

Hope that helps,
J

[vw5qb73]

Thank you for this information. I have some follow up questions on the solution you have mentioned above and my understanding on this.

Let's assume - we have a central deployment server "A" and a local DC deployment server "B"

From what i understand for the set up,

1. First, we need to create a master app for every local DC's deploy server ( in this case B),
2. then set up serverclass.conf in the central server A to propagate the master app and is child apps to B.
3. Update deploymentclient.conf in B to point to A

Let me know if my understanding is correct

Thanks,

Sandeep

[javiergn]

Yeah that's the case on a high level.
You are basically going to deploy a customised serverclass.conf to each deployment child in order to tell them what to deploy and where. Those children are going to be clients of the master deployment server.

Something I forgot to mention is that this configuration doesn't seem to be fully supported by Splunk. At least that's what I was told 2 years ago when I implemented it for the first time. So if you raise a support case with Splunk about it, you might not get a decent support. Keep in mind I'm talking about something that happened a while back so hopefully will not be the case anymore!