search

rhtconsulting / rhc-ose

OpenShift Automation and Utilities by Red Hat Consulting
42 stars 34 forks source link

DNS instance should not provision volume #225

Closed oybed closed 8 years ago

oybed commented 8 years ago

With the latest ansible based tools, the DNS instance is also getting assigned an additional volume for storage. This isn't necessary and is wasting resources. Should be at least made optional and disabled by default.

sabre1041 commented 8 years ago

@oybed the openstack-create node has logic to only create volumes when sizes are specified

https://github.com/rhtconsulting/rhc-ose/blob/openshift-enterprise-3/rhc-ose-ansible/roles/openstack-create/tasks/main.yml#L90-L97

Could be reuse of previously defined variables?

oybed commented 8 years ago

@sabre1041 agreed. This issue was opened just to track the default behavior that seemed to have changed in the later versions of the tools - i.e.: it used to not assign a volume to the dns instance by default.

sabre1041 commented 8 years ago

@oybed what version of ansible are you running? My latest run 2 weeks ago with ansible 2.1.0.0 did not attach a volume

oybed commented 8 years ago

@sabre1041 NVM - appears I need to learn how to count. It was an oversight from my side. :-) Closing it out.