-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BREAKING: Ability to download from download.splunk.com #150
Changes from all commits
e21b53c
f1d8ca1
af3c081
e3d9b6e
a933014
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -103,6 +103,21 @@ | |
tag => 'splunk_server', | ||
} | ||
|
||
if $facts['virtual'] == 'docker' { | ||
ini_setting { 'OPTIMISTIC_ABOUT_FILE_LOCKING': | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you know if this is always needed in any Docker container? Or is it just required for the acceptance tests to work in Travis? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Both. I don't know the exact details but if you google splunk docker unusable filesystem This is pretty much the solution everyone provides. Even the chef-splunk repo did this but this was for their acceptance test. I Also could not find exact details on why/how this actually works. If you want to try this out locally under docker remove that line and watch it fail with the above error message. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, I saw the comment before. Just wondering whether it's best to do this in the module or in the acceptance test; I think a case could possibly be made either way, but seems kind of magical, esp. since there's no parameter to control it. It sounds like if you setup the volumes correctly, it may not be necessary to set this?
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @wyardley I saw that but that isn't "Applicable" i believe in our case. When running docker acceptance tests we are not taking a folder on the host and mapping it to a folder in the docker container. Make sense? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, yeah, I thought this change was in the manifest itself, not in the test. I agree that this is a reasonable workaround in the acceptance test itself. |
||
ensure => present, | ||
section => '', | ||
setting => 'OPTIMISTIC_ABOUT_FILE_LOCKING', | ||
value => '1', | ||
path => '/opt/splunk/etc/splunk-launch.conf', | ||
} | ||
|
||
Package[$package_name] | ||
-> Ini_setting['OPTIMISTIC_ABOUT_FILE_LOCKING'] | ||
-> Exec <| tag == 'splunk_server' |> | ||
} | ||
|
||
|
||
splunk_input { 'default_host': | ||
section => 'default', | ||
setting => 'host', | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you split the new nodesets at least into an own commit? Or a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing!