In regard to: [Puppet Users] Puppet & Oracle Database config management,...:
My next challenge is maintaining Oracle database specific configuration on the relevant hosts. This contains various elements, such as /etc/oratab, /etc/oranfstab (as we're using dNFS), various NFS mounts required for a given database, and a few other bits and pieces... Ideally, it would be a 1-to-1 relationship between a given host and a given DB. However that's unlikely in our env - We're more likely to have 1 or multiple databases on a given host, which all need to be maintained. My initial thoughts are to use something like hiera to maintain this configuration data. Is this my best approach? Any other suggestions? Anyone doing this for real?
We're doing it, but not particularly well. We mostly configure the prereqs for Oracle -- packages, user & group, limits.d entries, profile.d shell settings, sysctl, paths, etc. We use puppet's file shipping for tnsnames.ora. I don't think we're actually managing /etc/oratab; the first run of puppetizing our db servers left some content that we allow the DBA to change directly. I am using hiera for the sysctl settings, along with a bit of logic in the manifest for whether AMM is in use or hugepages. We too have multiple databases per host, which complicates things somewhat. If you come up with something you feel is even moderately elegant, consider sharing it on the forge. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
