[dev.icinga.com #8346] Additional database-creation

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8346

Created by JannikZed on 2015-02-03 12:41:52 +00:00

Assignee: vkhatri
Status: Closed (closed on 2015-02-06 17:15:53 +00:00)
Target Version: (none)
Last Update: 2015-02-06 17:15:53 +00:00 (in Redmine)

---

The current state of the cookbook assumes that there exists an pre-configured database-server. I forked the icinga2 repository and added a new cookbook and dependencies to automatically install and configure postgres-/mysql-server. I depends on the official postgres and mysql cookbooks from the chef supermarket.
I can add a new pull request in github, if you are interested in that feature.

[icinga-migration]

Updated by vkhatri on 2015-02-05 21:38:35 +00:00

• Status changed from New to Assigned
• Assigned to set to vkhatri

[icinga-migration]

Updated by vkhatri on 2015-02-05 22:14:37 +00:00

JannikZed wrote:

The current state of the cookbook assumes that there exists an pre-configured database-server. I forked the icinga2 repository and added a new cookbook and dependencies to automatically install and configure postgres-/mysql-server. I depends on the official postgres and mysql cookbooks from the chef supermarket.
I can add a new pull request in github, if you are interested in that feature.

db configuration is better off managed separately as a wrapper recipe. currently this cookbook enforces usage of cookbook - pnp4nagios which is likely to be removed in the next release, like nrpe setup/configuration was removed in earlier release.

IMHO, configuring db/pnp4nagios is out of the scope of this cookbook and up to the user to configure.

[icinga-migration]

Updated by JannikZed on 2015-02-06 09:11:42 +00:00

Alright, I created the wrapper cookbook in my github-repository. Thanks for the good work

[icinga-migration]

Updated by vkhatri on 2015-02-06 17:15:53 +00:00

• Status changed from Assigned to Closed