zones created via zone import don't have pool attributes

Bug #1690184 reported by Tim Simmons
This bug affects 4 people
Affects Status Importance Assigned to Milestone
In Progress
Dmitry Galkin

Bug Description

Any zone that is created via zone import will be created with an empty
pool attributes dictionary.

This means that any zone import zone will fall through to whatever default pool
is configured via the pool scheduler.

It would be nice to have some way to specify pool attributes with a zone import,
however, this is difficult as it can't be in the HTTP body, as that's of type text/dns,
and it's the zone data itself.

Perhaps an HTTP header? The api-wg would die, but we can't think of anything better at first glance.

Tim Simmons (timsim)
Changed in designate:
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (master)

Fix proposed to branch: master

Changed in designate:
assignee: nobody → Dmitry Galkin (galkindmitrii)
status: Confirmed → In Progress
Revision history for this message
Dmitry Galkin (galkindmitrii) wrote :

Hi all,

I've submitted a fix for that as Tim suggests. The header to specify the pool id during zone import is 'X-Designate-Pool-ID'.

Feel free to review:)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on designate (master)

Change abandoned by "Erik Olof Gunnar Andersson <email address hidden>" on branch: master

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.