So now you have used Puppet to manage your application schema in the database. But you notice that the application also has some settings stored in tables inside of the database. Settings for external services like the URL of a WebService or the UNC of a server you have to connect to. Settings that contain different values in the production environment than in the test or development environment. This situation is a perfect match for Puppet. But how do we get Puppet to do this? This post will show you how the ora_config module, makes this possible.

Puppet already has a name when it comes to managing the configuration of IT infrastructure. But when it comes to managing applications, others tools are better known. In this blog post, we are going to show you how the ora_config module allows you manage your database schemas with Puppet. The ora_config module allows you to seamlessly integrate management of infrastructure and application deployment.

The size of a database is one of the more important items you can and must configure when managing a database. Oracle has several different mechanisms for doing this. In this article, we will show you how you can use Puppet and the Enterprise Modules ora_config module to do this. At the end of this article, you’ll be able to choose the best way to manage your database size with Puppet.

Russ looked at his screen. He started to get a bit weary. How in heavens name would he be able to manage this. He was looking at the requests he had for twenty applications that all had specific Oracle database needs. All different with regards to tablespaces, users, rights and services. And if that wasn’t bad enough in itself, all of the project teams building those applications, had up to 5 specific environments with different sizes and sometimes other settings. Russ definitely could use some help with this.