Bases: object
Client side of the central RPC API.
API version history:
1.0 - Initial version 1.1 - Add new finder methods 1.2 - Add get_tenant and get_tenants 1.3 - Add get_absolute_limits 2.0 - Renamed most get_resources to find_resources 2.1 - Add quota methods 3.0 - RecordSet Changes 3.1 - Add floating ip ptr methods 3.2 - TLD Api changes 3.3 - Add methods for blacklisted domains 4.0 - Create methods now accept designate objects 4.1 - Add methods for server pools 4.2 - Add methods for pool manager integration 4.3 - Added Zone Transfer Methods 5.0 - Remove dead server code 5.1 - Add xfr_zone 5.2 - Add Zone Import methods 5.3 - Add Zone Export method 5.4 - Add asynchronous Zone Export methods 5.5 - Add deleted zone purging task 5.6 - Changed ‘purge_zones’ function args 6.0 - Renamed domains to zones 6.1 - Add ServiceStatus methods 6.2 - Changed ‘find_recordsets’ method args 6.3 - Changed ‘update_status’ method args 6.4 - Removed unused record and diagnostic methods 6.5 - Removed additional unused methods
Bases: RPCService
Delete or abandon a zone On abandon, delete the zone from the DB immediately. Otherwise, set action to DELETE and status to PENDING and poke Pool Manager’s “delete_zone” to update the resolvers. PM will then poke back to set action to NONE and status to DELETED
List service statuses.
List existing zones including the ones flagged for deletion.
List Floating IPs PTR
token pr Neutron in the SC
We lookup FIPs using the configured values for this deployment.
Purge deleted zones. :returns: number of purged zones
Stop a service.
graceful – indicates whether to wait for all threads to finish or terminate them instantly
We strictly see if values[‘ptrdname’] is str or None and set / unset the requested FloatingIP’s PTR record based on that.
context – Security context information.
zone_id – The ID of the designate zone.
status – The status, ‘SUCCESS’ or ‘ERROR’.
serial – The consensus serial number for the zone.
action – The action, ‘CREATE’, ‘UPDATE’, ‘DELETE’ or ‘NONE’.
updated zone
Update zone. Perform checks and then call _update_zone()
updated zone
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.