HP OneView REST API Reference

connection-templates
connection-templates.html[10/17/2013 10:35:35 AM]
Updated: October 16, 2013 4:30
MDT
API Specifications Create Read Update Delete
/rest/connection-templates GET
/rest/connection-templates/defaultConnectionTemplate GET
/rest/connection-templates/schema GET
/rest/connection-templates/{id} GET PUT
Resource Model
ConnectionTemplate
ConnectionTemplateCollection
HP OneView REST API Reference
connection-templates
The connection templates resource provides APIs to manage connection templates. A connection template is associated
with one network. Each connection template describes the legal bandwidth range available to all connections utilizing the
network. A connection may specify bandwidth which is less than or equal to (but never greater than) the bandwidth range of
the connection template. The REST API (GET, UPDATE) supports an 'accept-language' in the request header and defaults
to 'en_US'. An 'auth:{token}' in the request header is required. The {token} may be retrieved from https://{appl}/rest/login-
sessions.
URI: /rest/connection-templates
Method API
GET Gets a list of connection templates.
Parameter Attributes Description
start Optional The 0-based index of the first resource to return
(start=0 starts with the first available resource). If the
specified count does not return all resources within the
maximum allowed time (see count), use the start
parameter to view additional resource pages. The default
value for start is 0 (first available resource).
count Optional Optional parameter that specifies the number of resources
to return from each API invocation. The number of
resources returned on each call is referred to as a page.
If you specify a count, the API attempts to return the
specified number of resources, however this may be
limited due to response time constraints and/or actual
number of resources available to return. The results
include the total number of resources that match the
filter or query, the actual count returned, and the
URIs to go to the next page, previous page, or both. If
necessary, you can make several requests using the URI
for the next or previous page (or different start
parameters) to get the desired
count
.