-
Notifications
You must be signed in to change notification settings - Fork 107
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
Add timeout to ceph_pool resource #225
base: master
Are you sure you want to change the base?
Conversation
In a few instances, we found ceph_pool hanging. The timeout attribute would allow us to control how long we would like to wait before raising an exception.
Hi @Johanni , Error in travis is due to some changes on rubocop. |
@@ -16,6 +16,9 @@ | |||
# Optional arguments for pool creation | |||
attribute :create_options, :kind_of => String | |||
|
|||
# The number of seconds before a timeout occurs during pool creation | |||
attribute :timeout, :kind_of => Integer, :default => nil, :required => false |
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.
:default => nil, :required => false
are optional as it's the default behavior
In a few instances, we found ceph_pool hanging. The timeout attribute would allow us to control how long we would like to wait before raising an exception.
Fix rubocop version in Gemfile
In a few instances, we found ceph_pool hanging. The timeout attribute would allow us to control how long we would like to wait before raising an exception.
Took me a while to fix my rebasing, but I think I got it now :) |
Do I need to squash commits or is it good as is? |
In a few instances, we found ceph_pool hanging. The timeout attribute would allow us to control how long we would like to wait before raising an exception.
In a few instances, we found ceph_pool hanging. The timeout attribute
would allow us to control how long we would like to wait before raising
an exception.