When you rebuild your dev-container, there is currently no way to keep the existing storage data directories. This is inconsistent with the relational db where you can rebuild your server while keeping the relational db intact. There is a validation to check in the storage installer to fail the installation if the specified data directories are non-empty. I think this makes sense, particularly for production scenarios; however, we do want to be able to keep our storage db intact in the dev-container like we do with postgres. I was thinking about adding an option to the storage installer that could turn off that validation check. The option wouldn't even have to be included in the help/usage. It could remain undocumented since it is really intended for dev use. What do people think?
+1
Would it be a system property? If so for dev environments we could set up a RHQ_STORAGE_ADDITIONAL_JAVA_OPTS variable.
Le 10/07/2013 05:02, John Sanda a écrit :
rebuild your dev-container, there is currently no way to keep the existing storage data directories. This is inconsistent with the relational db where you can rebuild your server while keeping the relational db intact. There is a validation to check in the storage installer to fail the installation if the specified data directories are non-empty. I think this makes sense, particularly for production scenarios; however, we do want to be able to keep our storage db intact in the dev-container like we do with postgres. I was thinking about adding an option to the storage installer that could turn off that validation check. The option wouldn't even have to be included in the help/usage. It could remain undocumented since it is really intended for dev use. What do people think?
The easiest thing would be to add another command line option that would be set in rhq-storage.properties. We only generate rhq-storage.properties for dev builds, and that provides dev-container defaults.
On Jul 10, 2013, at 4:20 AM, Thomas Segismont tsegismo@redhat.com wrote:
+1
Would it be a system property? If so for dev environments we could set up a RHQ_STORAGE_ADDITIONAL_JAVA_OPTS variable.
Le 10/07/2013 05:02, John Sanda a écrit :
rebuild your dev-container, there is currently no way to keep the existing storage data directories. This is inconsistent with the relational db where you can rebuild your server while keeping the relational db intact. There is a validation to check in the storage installer to fail the installation if the specified data directories are non-empty. I think this makes sense, particularly for production scenarios; however, we do want to be able to keep our storage db intact in the dev-container like we do with postgres. I was thinking about adding an option to the storage installer that could turn off that validation check. The option wouldn't even have to be included in the help/usage. It could remain undocumented since it is really intended for dev use. What do people think?
rhq-devel mailing list rhq-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
rhq-devel@lists.fedorahosted.org