Distributing APP from the deployment server to the index server

[masakazu]

I'm trying to distribute an app from the deployment server to the index server via the cluster manager.

In the cluster manager's deploymentclient.conf,
it uses serverRepositoryLocationPolicy and repositoryLocation to receive the app in $SPLUNK_HOME$/etc/manager-apps
and pushes it to peer-apps on the index server for distribution.

Distribution to the index server was successful, but an install error message appears in the deployment server's internal log.
Is there a setting to prevent items distributed to manager-apps from being installed?

[masakazu]

Hi, Tom-san!

Thank you for the advice.
It seems the problem was that the "stateOnClient" setting was also in the app specification.
When I removed that setting the error went away.

[serverClass:<serverClassName>:app:<AppName>]
stateOnClient = noop　　　←★
restartSplunkWeb = 0
restartsplunkd = 1

[serverClass:<serverClassName>]
stateOnClient = noop
whitelist.0 = server1

For reference, I would like to know if there is any other setting.
As mentioned above, the DS server specifies serverRepositoryLocationPolicy and repositoryLocation for the cluster manager, so the DS-app is saved in manager-app.
Is it possible to deploy the APP to the manager?

[Tom_Lundie]

If you want to dynamically deploy the app to either the manager-apps or apps directory, you can use serverclass.conf on the deployment server to do this.

Note that this is quite a complex deployment structure, make sure you keep your serverclass.conf well documented.

Firstly, restore the CM's deploymentclient.conf's repository settings to default to enable the serverClass to control the target repository:

[deployment-client]
repositoryLocation = $SPLUNK_HOME/etc/apps
serverRepositoryLocationPolicy = acceptSplunkHome

Then on the DS you can then dynamically set the repositoryLocation using the targetRepositoryLocation  directive within serverclass.conf  at the serverClass level:

For example you could have something like this:

[serverClass:CM_Deploy_to_Apps]
whitelist.0 = cm.yourcompany.com
targetRepositoryLocation = $SPLUNK_HOME/etc/apps
stateOnClient = enabled

[serverClass:CM_Deploy_to_Apps:app:example_app_1]
restartSplunkd = true

[serverClass:CM_Deploy_to_Apps:app:example_app_2]
issueReload=true
restartIfNeeded=true

[serverClass:CM_Deploy_to_Manager_Apps]
whitelist.0 = cm.yourcompany.com
targetRepositoryLocation = $SPLUNK_HOME/etc/manager-apps
stateOnClient = noop

[serverClass:CM_Deploy_to_Apps:app:example_manager_app_1]

[serverClass:CM_Deploy_to_Apps:app:example_manager_app_2]

[Tom_Lundie]

Hi,

Have a look at these docs.

On the DS make sure you've included noop for the CM serverclass.conf entry:

[serverClass:<serverClassName>]
stateOnClient = noop

Also, ensure you're not overriding it on the app-level too.

If you've already got this covered, can you share the error message please?