Hi, Michael already made a great set of roles to install and configure Oracle databases. See https://github.com/oravirt/ansible-oracle. It works but I wonder if this is the way to go or not. Considering the fact that there will be many Oracle installations and upgrades, I can imagine that the simplest declarative form would make an overview a lot easier that the way it is built now.
I imagine something like - install the stuff orainst src=pp:/hh/ff ORACLE_HOME=/some/loc ORACLE_BASE=/some ORA_INVENTORY=/also/somewhere type=rdbms/wls edition=EE/SE/.... options=partitioning,rac etc. I think this would mean writing an orainst module that does al the work, including defining the facts. When writing such a module, there will be a lot of code that is already written, like copy and shell/command. It would be a pity to have to write that same functionality again. How should we tackle such a thing? Maybe ansible-oracle is already when we should dream about? The biggest goal of writing such a module would be to improve the declarative description of what it does. The actions will be the same as ansible-oracle already does. It works. Would it be OK to re-use the modules that are already proven to build a new module? Ideally an oracle installation would be written as smooth as it goes with yum. Ronald - who is interested to hear about the way to go. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/09fa32ef-931e-4a36-9a97-14e5fff97c50%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
