Revision as of 07:56, 13 May 2011

Quantum API Specification

<<TableOfContents()>>

Introduction

This document constitutes a first attempt in defining an API for the Quantum service. The operation list cannot be deemed complete, and formats for request and response messages have not yet been defined. Moreover, authentication, authorization, and extension mechanisms, as well as the URL structure, are not defined in this document.

Since Quantum provides “network connectivity as a service”, this API defines Layer-2 operations only. This document also proposes operations for bridging Quantum networks with external networks, such as a customer-managed network in an on-premise data centre; however, use cases in this area (bridging and federation) should be explored better.

We first introduce the operation list, and then discuss how these operations can be used to accomplish some common use cases.

Glossary

Operation List

For each operation, both XML and JSON representation should be assumed. List of error response codes:

<<Anchor(GetNetworks)>>

List networks

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

This operation returns the list of all networks currently defined in Quantum; returned list includes at least the network’s unique identifier.

Response Codes:

~+~-Normal Response code: 200

Error response code(s): 500 Service Unavailable, 401 Unauthorized -~ +~

<<Anchor(GetNetworkDetails)>>

List network details

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

This operation provides detailed output for a specific network configured in Quantum.'

Response Codes:

~+~-Normal Response code: 200

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized -~+~

<<Anchor(PostNetwork)>>

Create Network

~+~-

-~+~

Request Body:

The body for this network should contain a symbolic name for the network.

Description:

~+~-This operation asynchronously creates a Layer-2 network in Quantum based on the information provided in the request body.

Quantum validates the request, creates the network object, dispatches it to the plugin, and then returns the unique identifier of the network to the caller, who can check the progress of the operation performing a GET on networks/id.

Resources for the new network can be either provided at create time or when virtual interfaces are plugged into this network depending on the particular plugin implementation.

If the validation phase fails, the network object is not created at all, and a 400 error is returned to the caller. -~+~

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 413 Over Limit -~ <<Anchor(PutNetwork)>> +~

Update Network

~+~-

-~+~

Request Body:

The request body for this operation will possibly contain the new symbolic name for the network.

Description: This operation asynchronously updates a network in Quantum according to the information provided in the request body.

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 510 PluginFault -~ <<Anchor(DeleteNetwork)>> +~

Delete Network

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

~+~-This operation removes the network specified in the URI. It will fail if an attachment is plugged into anyone of the network’s ports (error code 511). It will not fail instead if logical ports are configured for the network, as long as nothing is plugged into them.

Logical ports will be destroyed together with the network. The operation is asynchronous.

Quantum forwards the request to the plugin, and upon success removes the network object. Callers can check the current status of the operation by performing a GET on networks/id. This operation is not recoverable. -~+~

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 510 PluginFault, 511 AttachmentsPlugged -~ <<Anchor(GetPorts)>> +~

List logical ports for network

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

This operation lists all the ports currently configured for a network. Response should include, for each port, at least its unique identifier (might just be a port number) and the identifier of the attachment plugged into it, if any.

Response Codes:

~+~-Normal Response code: 200

Error response code(s): 500 Service Unavailable, 401 Unauthorized -~ <<Anchor(GetPortDetails)>> +~

List port details

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

~+~-This operation provides detailed output for a specific port configured for a given network.

This operation will return all the attributes of the port, including plugin-specific attributes. -~+~

Response Codes:

~+~-Normal Response code: 200

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized -~ <<Anchor(PostPort)>> +~

Create Port

~+~-

-~+~

Request Body:

The request body is not mandatory.

Description:

~+~-This operation asynchronously creates a port on a Quantum network based on the information provided in the request body. Quantum validates the request, creates the port object and attaches it to the appropriate network object. The request is then dispatched to the plugin.

Resources for the new port can be either provided at create time or when virtual interfaces are plugged into this port depending on the particular plugin implementation. Also, this operation could not be implemented for some plugins as the number of ports available might be fixed when the network is created. If the validation phase fails, the port object is not created at all, and a 400 error is returned to the caller. -~+~

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 413 Over Limit -~

<<Anchor(DeletePort)>> +~

Delete Port

~+~-

-~+~

Request Body: This operation does not require a request body.

Description:

~+~-This operation removes a logical port from a Quantum network. This operation might not be available for plugins in which the number of ports is fixed at network creation; in this case ports should not be deleted, just as they cannot be created.

The operation is not recoverable and will fail if an attachment is plugged into the port. -~+~

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 510 PluginFault, 511 AttachmentsPlugged. -~ <<Anchor(GetPortAttachment)>> +~

List attachment details for port

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

~+~-This operation returns configuration details for the attachment plugged into the port specified in the request URI.

This information might include:

• Type of the attachment (e.g.: virtual network interface, bridge device);
• A reference to the resource being attached (If managed by Quantum);
• A reference to an external resource being attached (If not managed by Quantum); -~+~

Response Codes:

~+~-Normal Response code: 200

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorize -~ <<Anchor(PutPortAttachment)>> +~

Attach resource to port

~+~-

-~+~

Request Body:

The request body for this network should contain a reference to the resource to plug into the logical port. Plugged resources can either be managed by or external to Quantum. In both cases, the request body will contain an identifier for that resource.

Description:

~+~-This operation asynchronously plugs a resource, or attachment, into the logical port specified in the request URL. A resource can be either a virtual network interface belonging to a VM instance, or any kind of device or service which can be plugged into the Quantum network in order to provide different services, such as IP addressing management. Different kinds of resources can be defined in the future.

The request will be first validated by Quantum and then dispatched to the plugin. As the request is asynchronous, control is immediately returned to the caller. Progress of the operation can then be checked by querying the attachment (or the logical port) with a GET request.

The validation can fail if:

• The attachment is already plugged somewhere else;
• There is already another attachment plugged into the specified logical port.

If the validation phase fails, the attachment object is not created at all, and a 400 error is returned to the caller. -~+~

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 413 Over Limit, 423 AlreadyAttached, 423 PortInUse, 510 PluginFault -~ <<Anchor(DeletePortAttachment)>> +~

Remove attachment from port

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

This operation asynchronously removes an attachment from a logical port. This operation cannot be undone.

Response Codes:

~+~-Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 413 Over Limit, 510 PluginFault -~ <<Anchor(GetNetworkAttachments)>> +~

Retrieve resources attached to network

~+~-

-~+~

Request Body:

This operation does not require a request body.

Description:

This operation return a list of resource currently attached to the virtual network specified in the URI. For each resource, the returned list should specify at least the identifier of the resource and the identifier of the port in which the resource is currently plugged.

Response codes:

~+~-Normal Response code: 200

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized -~ <<Anchor(PostNetworkAttachment)>> +~

Attach resource to network

~+~-

-~+~

Request Body:

The request body for this network should contain a reference to the resource to plug into the logical port. Plugged resources can either be managed by or external to Quantum. In both cases, the request body will contain an identifier for that resource.

Description:

~+~-This operation asynchronously plugs a resource, or attachment, into the logical port specified in the request URL. A resource can be either a virtual network interface belonging to a VM instance, or any kind of device or service which can be plugged into the Quantum network in order to provide different services, such as IP addressing management. Different kinds of resources can be defined in the future.

This operation is very similar to “attach resource to port”, with the only exception that a logical port is not specified in this case. Quantum plugins can either use a free port on the network, or create a new logical port, and then plug the resource into it.

The identifier of the logical port where the resource has been plugged should be returned to the caller. -~+~

~+~-Response Codes: Normal Response code: 202

Error response code(s): 500 Service Unavailable, 400 Bad Request, 401 Unauthorized, 413 Over Limit, 423 AlreadyAttached, 424 PortInUse, 510 PluginFault -~ +~