Skip to content

Specifying pool capacity is now optional. #11

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

Merged
merged 2 commits into from
Feb 4, 2019

Conversation

enqack
Copy link
Contributor

@enqack enqack commented Feb 2, 2019

A modified version of pool.xml.j2 will now pass parsing if capacity is omitted. Omitting capacity limits the pool's capacity to it's resident volume's capacity.

@enqack enqack closed this Feb 2, 2019
@markgoddard
Copy link

Hi, thanks for the PR. Do you not need this anymore?

@enqack
Copy link
Contributor Author

enqack commented Feb 4, 2019

I wasn't sure if I had something wrong given the CI errors I received. After closing the PR I came across a better syntax to use and will submit a PR for that version. If you have any input or other guidance I should consider please let me know. It is a simple change but thought I should ask.

@enqack enqack reopened this Feb 4, 2019
Copy link

@markgoddard markgoddard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@markgoddard markgoddard merged commit ed42550 into stackhpc:master Feb 4, 2019
@markgoddard
Copy link

CI errors were due to ansible-lint, fixed in another PR. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants