Install and configure for Ubuntu in designate

Bug #1740510 reported by Filippo DiNoto
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [ ] This doc is inaccurate in this way: ______
- [x] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - Ask OpenStack:
 - The mailing list:
 - IRC: 'openstack' channel on Freenode

Release: on 2017-12-18 19:22
SHA: 0740dbb53d8e3d5be40f12a377c63385a3108d5d

Revision history for this message
Filippo DiNoto (fdinoto) wrote :

I've had a lot of difficulty understanding the documentation and I'd like to offer some suggestions.

The install/config documents that comprehensively explain how to get designate working using the BIND9 backend makes gratuitous use of which I assume is because it is intended to get a standalone dev/poc working asap.

Personally I would like to see the docs changed to a scenario that does not use wherever possible because it makes it difficult to grasp exactly what each part of the configuration is doing.

I realize that there are other sections in the docs that do not use everywhere but those all seem to be based on PowerDNS which causes uncertainty for anyone who is familiar with bind but trying to learn designate. It introduces a double-unknown that completely destroys my confidence in what I already know :)

Changed in designate:
status: New → Triaged
importance: Undecided → High
tags: added: docs low-hanging-fruit
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.