Feature #5131
improve management of the cluster and database instances from build.xml
0%
Related issues
History
#1 Updated by Greg Shah over 5 years ago
We should automate the following processes:
- creation of the cluster
- installing the custom locale/handling the locale issues
- commands to create the cluster
- add users, grant permissions
- ...
- make a master database backup
I haven't reviewed our database setup docs, but the core idea here is to automate processes that are manual today. We will have to consider Windows support as well as Linux.
The best location for this (at this time) is probably in the Apache ant build scripting that we use (which is outside of FWD today).
#2 Updated by Greg Shah over 1 year ago
- Project changed from Database to Deployment
The best location for this (at this time) is probably in the Apache
antbuild scripting that we use (which is outside of FWD today).
The requirements from #5131-1 are all still critical except for this idea. We will not implement this improvement outside of FWD. Instead, we will create tools in Java code that is part of FWD, to improve the deployment of database support. We can consider non-Java scripting as a fallback when Java code is not a good match. Java code will be the first choice.
#3 Updated by Roger Borrello 8 months ago
- Related to Feature #10491: Tool to standardize PG cluster creation added
#4 Updated by Roger Borrello 8 months ago
I'm not sure that the use of build.xml is good from the perspective of deployment. When I think of deployment, wouldn't this be a set of files already built and away from any build environment, perhaps packaged in an archive? Perhaps I'm missing something about how build tools like ant can be used.