Added Parameter 'size_is_minsize' (true|false(default)) #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Most of the times it desired to specify minimum disk settings for your application stacks (e.g. your web server should have a /var/ww space of 10GB).
However while during operations individual servers must be manually extended (//var/log is full because of a user error on a single web server of our fleet). For this operations sometimes manually intercepts. However this makes the puppet manifest fail from that moment on.
If size_is_minsize is set to true, the size parameter is actually a minsize parameter, causing the puppet manifest not to fail, if the LV we found is actually larger then we expected.
I think this is an essential feature and is needed for opertations at larger scale, expecially with outsourced highly operation teams.
Even better would be a ensure mode of "minsize", however I was not able to implement this :L)