{"action":"created","issue":{"url":"https://api.github.com/repos/jorritfolmer/puppet-splunk/issues/3","repository_url":"https://api.github.com/repos/jorritfolmer/puppet-splunk","labels_url":"https://api.github.com/repos/jorritfolmer/puppet-splunk/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/jorritfolmer/puppet-splunk/issues/3/comments","events_url":"https://api.github.com/repos/jorritfolmer/puppet-splunk/issues/3/events","html_url":"https://github.com/jorritfolmer/puppet-splunk/issues/3","id":146736213,"number":3,"title":"Search Head Clustering","user":{"login":"cbowlesut","id":8246957,"avatar_url":"https://avatars.githubusercontent.com/u/8246957?v=3","gravatar_id":"","url":"https://api.github.com/users/cbowlesut","html_url":"https://github.com/cbowlesut","followers_url":"https://api.github.com/users/cbowlesut/followers","following_url":"https://api.github.com/users/cbowlesut/following{/other_user}","gists_url":"https://api.github.com/users/cbowlesut/gists{/gist_id}","starred_url":"https://api.github.com/users/cbowlesut/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cbowlesut/subscriptions","organizations_url":"https://api.github.com/users/cbowlesut/orgs","repos_url":"https://api.github.com/users/cbowlesut/repos","events_url":"https://api.github.com/users/cbowlesut/events{/privacy}","received_events_url":"https://api.github.com/users/cbowlesut/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-07T20:40:53Z","updated_at":"2016-04-08T05:30:40Z","closed_at":null,"body":"Very nice job with this module, I am currently using it to bootstrap our new Splunk environment.  Having some issues with our search head cluster, which is your example 7.  \r\n\r\nI have sucessfully appled the SHC node configurations to a staging server and captured the puppet_* apps.\r\nI have configured a deployer.\r\nHowever, I am not clear on the best way to bootstrap new SHC nodes, since there is a chicken/egg problem with configuring them to join the cluster before pushing configurations.\r\n\r\nCould you clarify the steps to take on the SHC nodes/slaves? \r\n\r\nThanks!\r\n"},"comment":{"url":"https://api.github.com/repos/jorritfolmer/puppet-splunk/issues/comments/207222793","html_url":"https://github.com/jorritfolmer/puppet-splunk/issues/3#issuecomment-207222793","issue_url":"https://api.github.com/repos/jorritfolmer/puppet-splunk/issues/3","id":207222793,"user":{"login":"jorritfolmer","id":11555154,"avatar_url":"https://avatars.githubusercontent.com/u/11555154?v=3","gravatar_id":"","url":"https://api.github.com/users/jorritfolmer","html_url":"https://github.com/jorritfolmer","followers_url":"https://api.github.com/users/jorritfolmer/followers","following_url":"https://api.github.com/users/jorritfolmer/following{/other_user}","gists_url":"https://api.github.com/users/jorritfolmer/gists{/gist_id}","starred_url":"https://api.github.com/users/jorritfolmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jorritfolmer/subscriptions","organizations_url":"https://api.github.com/users/jorritfolmer/orgs","repos_url":"https://api.github.com/users/jorritfolmer/repos","events_url":"https://api.github.com/users/jorritfolmer/events{/privacy}","received_events_url":"https://api.github.com/users/jorritfolmer/received_events","type":"User","site_admin":false},"created_at":"2016-04-08T05:30:40Z","updated_at":"2016-04-08T05:30:40Z","body":"Something like this should work:\r\n\r\n1. stop Splunk on SHC nodes\r\n1. manually put captured puppet_* apps in /opt/splunk/etc/apps on each SHC node\r\n1. manually put captured puppet_* apps in /opt/splunk/etc/shcluster/apps on SH Deployer\r\n1. make sure /opt/splunk/etc/system/local is empty on each SHC node\r\n1. start SHC node\r\n1. splunk init shcluster-config on each SHC node\r\n1. splunk bootstrap shcluster-captain on one of the SHC nodes\r\n\r\nThe splunk init shcluster-config will create its configuration in /opt/splunk/etc/system/local individually for each node. So make sure to clean that between iterations of the steps above.\r\n\r\nI've since discovered that it is possible to create 1 single configuration for SHC nodes that can copied to each SHC node and the SH Deployer. It involves pre-creating a `server_list = ` line with the GUID and fqdns of the SHC nodes. This belongs in the `[shcluster]` stanza of server.conf. It's basically the splunk init shcluster-config step in a more portable form. You can get the GUID from /opt/splunk/etc/instance.cfg on each SHC node.\r\n\r\nThis could be Puppetized, I think, however it will need custom facts, node dependencies and other Puppet wizardry."}}