[Pdns-users] Project back-end admin for powerdns

[Kenneth Kalmer]

On Wed, Apr 22, 2009 at 5:12 PM, Julian Pawlowski <lists at propenguin.net>wrote:

>
> > Now I'd like to:
> > - Migrate a live pdns DB to adapt its structure so that it has the
> > fields/tables needed by powerdns-on-rails.
> >
> > ...
> >
> > I thought it might be just something like
> >     rake db:migrate RAILS_ENV="production"
> > but that tries to create tables, not update them.
>
> I'm currently also facing these thoughts and I just asked a ruby-guru
> friend to give me some input here :-)
> I will let you know as soon as there are any news to this.
>

Great you guys!

My apologies for only replying now, my DSL at home is busted, so this is
from the office.

There is a migration tool built into PowerDNS on Rails. It is very rough,
but I've used it on our production servers initially to import about 15,000
zones. Below is the steps to get it going, I'd appreciate any feedback you
guys have on this.

Requirements for migration:

1. Empty (new) database for powerdns-on-rails to use.
2. Correctly configured database.yml file for the "target database"
3. Fully migrate the target database using "rake db:migrate"
4. Seed the fresh database, to get an admin user: "rake db:seed"

When this is done and ready, you'll run the following:

$ rake migrate:powerdns

It will prompt you for the details of the source database, which you can
enter and then let the script run. I've had some feedback before on possible
PostgreSQL issues (in Lighthouse). I've done my best to resolve them.

Please let the feedback stream in, and thanks for trying it!

Best

-- 
Kenneth Kalmer
kenneth.kalmer at gmail.com
http://opensourcery.co.za
@kennethkalmer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20090422/263e189e/attachment-0001.html>