Deployment Architecture

Deployment Server

rupeshn
Explorer

Hi,

In production environment ,I've deployment server with several serverclasses(having multiple Apps and clients). I've deployed few apps to clients in some serverclass through DS. Now, I want to disable my deployment server permanently. Here are few questions that come to my mind when i think of disabling DS.

  1. How to disable DS?
  2. If I disbale DS. Will the Apps pushed through DS earlier will be deleted from deployment clients?
  3. If Yes, How to avoid deletion of Apps deployed through DS from deployment clients?

Please Help.

Thank You!

0 Karma
1 Solution

burwell
SplunkTrust
SplunkTrust

I believe if there's no serverclass.conf then the server that was the deployment server won't act as a deployment server.

The clients will attempt to connect but will fail but the existing apps should not get deleted.

Alternatively

1) on the client, you could add

 [deployment-client]
 disabled = true

See https://docs.splunk.com/Documentation/Splunk/7.3.0/Admin/Deploymentclientconf

2) You could point to a non existent deployment server

[target-broker:deploymentServer]
targetUri = nonexistent_server.mycompany.com

View solution in original post

0 Karma

morethanyell
Builder

How to disable DS?
-- uninstall the Splunk Enterprise from the host that is serving as the DS
-- if the Splunk Enterprise is working not only as a DS but other Splunky purpose and so you don't want to uninstall the Splunk in it, then delete all serverclasses, deployment-apps, and go to each client and delete the deploymentclient.conf

If I disbale DS. Will the Apps pushed through DS earlier will be deleted from deployment clients?
-- nope. apps in the clients will just stay as though they're installed there manually

If Yes, How to avoid deletion of Apps deployed through DS from deployment clients?
-- ...

0 Karma

burwell
SplunkTrust
SplunkTrust

I believe if there's no serverclass.conf then the server that was the deployment server won't act as a deployment server.

The clients will attempt to connect but will fail but the existing apps should not get deleted.

Alternatively

1) on the client, you could add

 [deployment-client]
 disabled = true

See https://docs.splunk.com/Documentation/Splunk/7.3.0/Admin/Deploymentclientconf

2) You could point to a non existent deployment server

[target-broker:deploymentServer]
targetUri = nonexistent_server.mycompany.com
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Why do you want to disable the DS? You'll need to update the deployed apps.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...