-
Notifications
You must be signed in to change notification settings - Fork 24
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
Scottx611x/docker puppet install #1664
Changes from 5 commits
0c001e7
dde2154
aeacd84
d160d8c
3b2953e
76e96ba
c23057d
3095a51
f0bac99
fb90605
645365b
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 |
---|---|---|
@@ -0,0 +1,5 @@ | ||
class refinery::docker_ { | ||
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. Why not 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. Because there is already a class |
||
class { 'docker': | ||
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. This should be 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. Okay, should this be changed throughout our manifests? I was just following the syntax that we had used throughout 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. Also this answer is from 2012, is it still relevant? 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. Yes, it's the reason you got the naming error when trying to use 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. And yes, this should be changed in the rest of the manifests but in a separate branch. |
||
docker_users => [$app_user] | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,9 +3,6 @@ | |
# for better performance | ||
sysctl { 'vm.swappiness': value => '10' } | ||
|
||
# to avoid empty ident name not allowed error when using git | ||
user { $app_user: comment => $app_user } | ||
|
||
file { "/home/${app_user}/.ssh/config": | ||
ensure => file, | ||
source => "${deployment_root}/ssh-config", | ||
|
@@ -229,6 +226,7 @@ | |
Class["ui"], | ||
Class["solr"], | ||
Class["neo4j"], | ||
Class["docker"], | ||
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. Why does supervisor require docker? 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. I don't think supervisor explicitly needs docker, but i don't think we want to start up everything without it since our app will depend on docker working. 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. I'd remove that since there is no explicit dependency and docker installation will still happen by the time the Refinery manifest is applied. |
||
Class["::rabbitmq"], | ||
Service["memcached"], | ||
], | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
class refinery::selenium { | ||
$geckodriver_version = 'v0.15.0' | ||
$filename = "geckodriver-${geckodriver_version}-linux32.tar.gz" | ||
$filename = "geckodriver-${geckodriver_version}-linux64.tar.gz" | ||
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. Why is this necessary? 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. Because Geckodriver is not providing 32 bit builds in its newer releases anymore |
||
$install_path = "/opt/geckodriver" | ||
|
||
package { "firefox":} | ||
|
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.
Why not use the puppetlabs/docker_platform?
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.
Not sure, it looks exactly the same as:
garethr-docker
Actually it depends on it: https://forge.puppet.com/puppetlabs/docker_platform/dependencies
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.
The benefit of the puppetlabs modules is that they are provided by the Puppet team. Also, garethr-docker was last updated about a year ago and it supports only up to Ubuntu 14.04. The puppetlabs version was last updated a week ago and supports Ubuntu 16.04. Basically, it looks like it is probably going to replace garethr-docker.