Jump to: navigation, search

Difference between revisions of "Designate/Blueprints/ReverseFixedIP"

(API Details: GET / POST / DELETE)
(List the Fixed IP PTR Records (GET))
 
(19 intermediate revisions by the same user not shown)
Line 12: Line 12:
 
This blueprint proposes to provide an interface for a VM instance's PTR record based on the allocated Fixed IP.
 
This blueprint proposes to provide an interface for a VM instance's PTR record based on the allocated Fixed IP.
  
This blueprint is based on the blueprint done for floating IPs:
+
This blueprint is based on the blueprint for floating IP PTR records:
  
 
     [[Designate/Blueprints/Reverse]]
 
     [[Designate/Blueprints/Reverse]]
Line 25: Line 25:
 
! Verb !! Resource !! Description
 
! Verb !! Resource !! Description
 
|-
 
|-
| GET || /reverse/fixedips/{IP address} || Return the PTR record for the given IP address.
+
| GET || /reverse/fixedips || Return the list of PTR records for all fixed IP addresses.
 
|-
 
|-
| PATCH || /reverse/fixedips/{IP address} || Set or unset the PTR record for the given IP address.
+
| GET || /reverse/fixedips/{region}:{IP address} || Return the PTR record for the given fixed IP address.
 +
|-
 +
| PATCH || /reverse/fixedips/{region}:{IP address} || Create or delete the PTR record for the given fixed IP address.
 
|}
 
|}
  
==== Get the PTR Record (GET) ====
+
==== List the Fixed IP PTR Records (GET) ====
 +
 
 +
Return the list of PTR record for all fixed IP addresses.
 +
 
 +
There is no request message body.
 +
 
 +
'''Response'''
 +
    {
 +
        “fixedips”: [
 +
            {
 +
                "ptrdname": "server.mydomain.com.",
 +
                "address": "<region>:<ipv4 or ipv6 compliant address>",
 +
                "ttl": 3600,
 +
                "description": null,
 +
                "links": {
 +
                    "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
 +
                }
 +
            },
 +
            {
 +
                "ptrdname": "server2.mydomain.com.",
 +
                "address": "<region>:<ipv4 or ipv6 compliant address>",
 +
                "ttl": 3600,
 +
                "description": null,
 +
                "links": {
 +
                    "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
 +
                }
 +
            }
 +
        ],
 +
        "links": {
 +
            "self": "http://endpoint/v2/reverse/fixedips"
 +
        }
 +
    }
 +
 
 +
==== Get the Fixed IP PTR Record (GET) ====
  
Return the PTR record for the given instance ID.
+
Return the PTR record for the given fixed IP address.
  
 
There is no request message body.
 
There is no request message body.
Line 39: Line 74:
 
     {
 
     {
 
         “fixedip”: {
 
         “fixedip”: {
            "id": "<uuid>",
 
 
             "ptrdname": "server.mydomain.com.",
 
             "ptrdname": "server.mydomain.com.",
             "address": "<ipv4 or ipv6 compliant address>",
+
             "address": "<region>:<ipv4 or ipv6 compliant address>",
 
             "ttl": 3600,
 
             "ttl": 3600,
            "created_at": "2014-03-04T11:00:01.000000",
 
            "update_at": null,
 
 
             "description": null,
 
             "description": null,
 
             "links": {
 
             "links": {
                 "self": "http://endpoint/v2/reverse/fixedips/<ip address>"
+
                 "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
 
             }
 
             }
 
         }
 
         }
 
     }
 
     }
  
==== Set the PTR Record (PATCH) ====
+
==== Create the Fixed IP PTR Record (PATCH) ====
  
Set the PTR record for the given IP address.
+
Create the PTR record for the given fixed IP address.
  
 
'''Request'''
 
'''Request'''
Line 67: Line 99:
 
     {
 
     {
 
         “fixedip”: {
 
         “fixedip”: {
            "id": "<uuid>",
 
 
             "ptrdname": "server.mydomain.com.",
 
             "ptrdname": "server.mydomain.com.",
             "address": "<ipv4 or ipv6 compliant address>",
+
             "address": "<region>:<ipv4 or ipv6 compliant address>",
 
             "ttl": 3600,
 
             "ttl": 3600,
            "created_at": "2014-03-04T11:00:01.000000",
 
            "update_at": null,
 
 
             "description": null,
 
             "description": null,
 
             "links": {
 
             "links": {
                 "self": "http://endpoint/v2/reverse/fixedips/<ip address>"
+
                 "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
 
             }
 
             }
 
         }
 
         }
 
     }
 
     }
  
==== Unset the PTR Record (PATCH) ====
+
==== Delete the Fixed IP PTR Record (PATCH) ====
  
Unset the PTR record for the given IP address.
+
Delete the PTR record for the given fixed IP address.
  
 
'''Request'''
 
'''Request'''

Latest revision as of 15:28, 13 March 2014

Overview

Gerrit Patch []
Launchpad Blueprint [1]

Summary

This blueprint proposes to provide an interface for a VM instance's PTR record based on the allocated Fixed IP.

This blueprint is based on the blueprint for floating IP PTR records:

   Designate/Blueprints/Reverse

API Resource - Private / Fixed IPs

Using the general endpoint call "/reverse" add the fixed IP resource called "fixedips".

API Details

Verb Resource Description
GET /reverse/fixedips Return the list of PTR records for all fixed IP addresses.
GET /reverse/fixedips/{region}:{IP address} Return the PTR record for the given fixed IP address.
PATCH /reverse/fixedips/{region}:{IP address} Create or delete the PTR record for the given fixed IP address.

List the Fixed IP PTR Records (GET)

Return the list of PTR record for all fixed IP addresses.

There is no request message body.

Response

   {
       “fixedips”: [
           {
               "ptrdname": "server.mydomain.com.",
               "address": "<region>:<ipv4 or ipv6 compliant address>",
               "ttl": 3600,
               "description": null,
               "links": {
                   "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
               }
           },
           {
               "ptrdname": "server2.mydomain.com.",
               "address": "<region>:<ipv4 or ipv6 compliant address>",
               "ttl": 3600,
               "description": null,
               "links": {
                   "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
               }
           }
       ],
       "links": {
           "self": "http://endpoint/v2/reverse/fixedips"
       }
   }

Get the Fixed IP PTR Record (GET)

Return the PTR record for the given fixed IP address.

There is no request message body.

Response

   {
       “fixedip”: {
           "ptrdname": "server.mydomain.com.",
           "address": "<region>:<ipv4 or ipv6 compliant address>",
           "ttl": 3600,
           "description": null,
           "links": {
               "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
           }
       }
   }

Create the Fixed IP PTR Record (PATCH)

Create the PTR record for the given fixed IP address.

Request

   {
       "fixedip": {
           "ptrdname": "server.mydomain.com.",
           "ttl": 3600
       }
   }

Response

   {
       “fixedip”: {
           "ptrdname": "server.mydomain.com.",
           "address": "<region>:<ipv4 or ipv6 compliant address>",
           "ttl": 3600,
           "description": null,
           "links": {
               "self": "http://endpoint/v2/reverse/fixedips/<region>:<ipv4 or ipv6 compliant address>"
           }
       }
   }

Delete the Fixed IP PTR Record (PATCH)

Delete the PTR record for the given fixed IP address.

Request

   {
       "fixedip": {
           "ptrdname": null
       }
   }

The return body is empty.

Database Changes

There are no changes to the database schema.