poweradmin cookbook

This cookbook is used to install poweradmin - web-based console to manage PowerDNS.

Requirements

You should have already installed PowerDNS and pdns-backend-mysql to use it without errors.

Depends on cookbooks:

• apt
• yum-epel
• apache2
• tar
• database
• chef-pdns (this one used for tests)

Supported Platforms

Tested and runs on:

• Ubuntu 12.04
• Ubuntu 14.04
• CentOS 6.5
• Debian 7.6
• CentOS 7
• Debian 6.0.10

Should also work with other RHEL and Debian based distos, but not tested yet.

Attributes

node["poweradmin"]["remote_install"] - whenever to install poweradmin from remote or local source. Default - true

node["poweradmin"]["version"] - version to download. used in node["poweradmin"]["remote_url"]. Default - 2.1.7

node["poweradmin"]["remote_url"] - download URL for poweradmin. Default - https://github.com/poweradmin/poweradmin/archive/v#{node["poweradmin"]["version"]}.tar.gz

node["poweradmin"]["package_name"] - name for local package located in files/default. Default - poweradmin-2.1.7.tgz

node["poweradmin"]["install_dir"] - Docroot for apache2 where poweradmin will be located. Default - /var/www/poweradmin
node["poweradmin"]["http_port"] - port where Poweradmin web panel could be found. Default - '80'

Here is a block of mysql connection settings - it should be easy to understand what value stands for.

Should be the same, previously used to configure pdns-backend-mysql.

node["poweradmin"]["hostname"] = 'localhost'

node["poweradmin"]["port"] = 3306

node["poweradmin"]["username"] = 'powerdns'

node["poweradmin"]["password"] = 'p4ssw0rd'

node["poweradmin"]["dbname"] = 'powerdns'

node["poweradmin"]["type"] = 'mysql'

Usage

poweradmin::default

Use recipe[poweradmin::default] to deploy Poweradmin web panel on your working copy of PowerDNS with mysql-backend.

poweradmin::test

Use recipe[poweradmin::test] to deploy Poweradmin web panel alongside with test deployment of PowerDNS+mysql-backend used in this chef-pdns test cookbook.

But it's not recomended to use it in such way. At least right now.

Contributing

Your contributions is highly appreciated.
Here is standart instruction how to do so:

1. Fork the repository on Github
2. Create a named feature branch (i.e. add-new-recipe)
3. Write your change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request

License and Authors

• Author:: SiruS (https://github.com/podwhitehawk) ```text Copyright (C) 2014 SiruS (https://github.com/podwhitehawk)

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
```