Cisco Elastic Service Controller 1.1 REST API Guide
|
|
- Ezra Kelley
- 5 years ago
- Views:
Transcription
1 Cisco Elastic Service Controller 1.1 REST API Guide Cisco Systems, Inc. Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at
2 Cisco Elastic Service Controller 1.1 REST API Guide 2015 Cisco Systems, Inc. All rights reserved.
3 Contents PART 1 ESC REST API FOR NB CLIENTS... 5 Introduction ) Tenants... 7 List Tenants... 7 Create a Tenant... 8 Get a Tenant Delete a Tenant ) Networks List Networks for Tenant Create Network for Tenant Get Network for Tenant Delete Network for Tenant ) Subnets List Subnets for Tenant Create Subnet for Tenant Get Subnet for Tenant Delete Subnet for Tenant ) Images List Images Create an Image Get an Image Delete an Image ) Flavors List Flavors Create a Flavor Get a Flavor Delete a Flavor ) Service-Catalog List all services in ServiceCatalog Create/Register Service in ServiceCatalog Get a specific registered Service in Service Catalog Delete/Unregister Service in ServiceCatalog ) Deployments Get All Deployments
4 Create/Deploy Get a Specific Deployment Delete/Undeploy ESC Callback Event ) VM Operations Stop a specified VM Start a specified VM Reboot a specified VM Disable VM Monitoring on a specified VM Enable VM Monitoring on a specified VM ) VNF Operations Stop Service Start Service Reboot Service Disable Monitoring for VNF Enable Monitoring for VNF
5 PART 1 ESC REST API for NB Clients Introduction o o o o o Resources managed by ESC: Tenants, Networks, Subnets, Users, ServiceCatalog, Deployments GET operations are synchronous the request/response parameters are described with an example of a request/response POST, DELETE, PUT operations are asynchronous. The asynchronous design use the web hooks approach using two independent "one-way" invocations - one to start a long-running operation (Client to ESC) and the other one to notify a requester that it is completed (ESC to client) o The inbound representation of the operation request will contain a callback field, whose value is a URI where the client expects a callback. If this field is not present, no callback will be performed. o When the operation has completed (either successfully or unsuccessfully), ESC will perform a POST request to the callback URI, with an entity body containing the final status resource for this operation. o Client can match a completion report back to the original request by comparing the internal transaction ID field value to the one returned in the initial status response o ESC Clients are expected to provide a REST implementation for all the callbacks. All POST,DELETE,PUT operations that require request and/or response body must provide a header parameter for media type. Note, that ESC is currently tested to accept and return XML. For example: Content-Type: application/xml Accept: application/xml Some string parameters, such as id, name, are restricted by the underlying cloud provider, such as Openstack. The allowable range for these parameters is included in the Create section for each resource, in this notation: String minimum-length.. maximum length, for example, for Tenant name: String Generally, names are either (for Tenant/User) or (Network/Subnet/Flavor/Image/VM) Id (such as uuid) are restricted to 64 characters, such internal_id 1..64, external_id o ESC imposes this limitation / restriction concerning internal ids: internal id naming must conform the standards stated in RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. See sections related to URI encoding, sections 2.2 Reserved Characters and 2.3 Unreserved Characters. ESC will accept an internal id specified in the request URL form the unreserved character set: unreserved = ALPHA / DIGIT / "-" / "." / "_ NOTE: the tilde ~ is not supported in the internal id character set the internal id received in a request must be unique within the scope of all the domain resources (tenant, network, subnet, service catalog, deployment ) For example, you cannot create 2 networks with the same internal_network_id, even if the networks are created in different tenants 5
6 o It is recommended that the ESC north bound client generate internal ids within the scope of the ESC. NOTE: Reusing ( recycling ) of internal ids is not recommended. This practice can lead to confusion in trouble shooting. ESC does not support Use Cases where Resources managed by ESC are modified directly in Openstack, that is, created/delete/updated out-of-band of ESC. The behavior for out-of-band modifications to Openstack of resources tenant/user/network/subnet/vm is as follows: Out-of-Band Action Result of ESC API call create tenant/user/network/subnet in Openstack delete tenant/user/network/subnet in Openstack create tenant/user/network/subnet with matching name will fail, with callback POST 409 conflict delete of tenant/user/network/subnet, previously created through ESC will fail, with callback POST 404 not found get of tenant/user/network/subnet will return details stored in esc_database create of tenant/user/network/subnet will fail, with callback POST 409 conflict update resource in Openstack tenant/user/network/subnet in esc database remains unmodified. The result is a mismatch between esc and Openstack delete vm in Openstack this will trigger ESC statemachine to perform recovery a new VM will be deploy reboot or shutdown vm in Openstack this will trigger ESC statemachine to perform recovery VM hard reboot will be attempted, followed by undeploy/deploy (if required) 6
7 1) Tenants List Tenants Note: All URIs listed in this document needs to be preceded by assuming is ESC IP and the REST interface is running with http and not https. For more info about running ESC REST interface over https please refer to ESC installation guide. Verb URI Description GET /v0/tenants List tenants Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging Request Example: GET /v0/tenants HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error Response Parameters Name Style Type Description external_tenant_id Body String Generated Openstack tenant ID 7
8 internal_tenant_id Body String NB Client tenant ID name Body String Tenant name enabled Body Boolean Indicates if tenant is enabled description Body String Description about the tenant Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT <?xml version="1.0" encoding="utf-8"?> <tenants> <tenant> <internal_tenant_id> </internal_tenant_id> <external_tenant_id> </external_tenant_id> <name>elie</name> <enabled>true</enabled> <description>a description...</description> </tenant> <tenant> <internal_tenant_id> </internal_tenant_id> <external_tenant_id> </external_tenant_id> <name>michael</name> <enabled>true</enabled> <description>a description...</description> </tenant> </tenants> Create a Tenant Verb URI Description POST /v0/tenants/{internal_tenant_id} Creates a tenant Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB 8
9 internal_tenant_id Template String Yes client used for debugging and logging Internal Tenant ID provided by ESC NB client Tenant name Name Body String Yes Enabled Body Boolean Yes Indicates if tenant is enabled description Body String No Description about the tenant callback Header String Yes URL to be used for callback Request Example: POST /v0/tenants/123 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/createtenantcallback <?xml version="1.0" encoding="utf-8"?> <tenant xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <name>elie</name> <enabled>true</enabled> <description>a description...</description> </tenant> Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Internal Server Error (500) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request 9
10 esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: ESC is processing the request Response (callback) Response Codes Normal Response Code(s): 200 Error Response Code(s): Conflict 409, Internal Server Error 500 Response(callback)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-status-code Header String Code representing Http status code esc-status-message Header String A message describing the response could be a success or error message external_tenant_id Body String Generated Openstack tenant ID name Body String Tenant name internal_tenant_id Body String Generated Openstack tenant ID enabled Body Boolean Indicates if tenant is enabled description Body String Description about the tenant 10
11 Response Example (Success): HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Success <?xml version="1.0" encoding="utf-8"?> <tenant> <external_tenant_id> </external_tenant_id> <internal_tenant_id> </internal_tenant_id> <name>elie</name> <enabled>true</enabled> <description>a description...</description> </tenant> Response Example (Failure): HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 500 ESC-Status-Message: Internal Server Error <?xml version="1.0" encoding="utf-8"?> <tenant> </tenant> Get a Tenant Verb URI Description GET /v0/tenants/{internal_tenant_id} Get tenant information by ID Request Request Parameters: 11
12 Name Style Type Required Description Header String No Transaction ID supplied by ESC NB client used for debugging and logging clienttransaction-id internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client Request Example: GET /v0/tenants/123 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error, 404 Resource Not found Response Parameters Name Style Type Description esc-transaction-id Body String A unique internal transaction ID generated by ESC for every request external_tenant_id Body String Generated Openstack tenant ID name Body String Tenant name enabled Body Boolean Indicates if tenant is enabled description Body String Description about the tenant Response Example: 12
13 HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <tenant> <external_tenant_id> </external_tenant_id> <name>elie</name> <enabled>true</enabled> <description>a description...</description> </tenant> Delete a Tenant Verb URI Description DELETE /v0/tenants/{internal_tenant_id} Deletes a tenant Request Request Parameters Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client callback Header String Yes URL to be used for callback Request Example: DELETE /v0/tenants/123 HTTP/1.1 13
14 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/deletetenantcallback Response (synchronous) Normal Response Code(s): 204 Error Response Code(s): Bad Request (400), Internal Server Error (500), 400 Resource Not Found Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: ESC is processing the request Response(callback) Response Codes Normal Response Code(s): 200 Error Response Code(s): Internal Server Error 500 Response(callback)Parameters Name Style Type Description 14
15 esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-status-code Header String Code representing Http status code esc-status-message Header String A message describing the response could be a success or error message Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Success 15
16 2) Networks List Networks for Tenant Verb URI Description GET /v0/{internal_tenant_id}/networks Lists networks to which the specified tenant has access. NOTE: a List request will return all shared networks. So networks that were created with a different internal_tenant_id that are shared will be returned. Request Request Parameters: Name Style Type Required Description Header String No Transaction ID supplied by ESC NB client used for debugging and logging clienttransaction-id internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client Request Example: GET /v0/123/networks HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s):
17 Error Response Codes: 400 Bad Request, 500 Internal Server Error Response Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request status Body String The network status. subnets Body List The associated subnets. name Body String The network name. admin_state_up Body Boolean A Boolean value that indicates the administrative status of the network. external_tenant_id Body String OpenStack tenant ID. external_network_id Body String OpenStack network ID. shared Body Boolean Indicates whether this network is shared across all tenants. By default, only administrative users can change this value. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <networks> <network> <admin_state_up>true</admin_state_up> <external_network_id>9ad32b6f-bb65-4a09-b a7dfd00</external_network_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <internal_network_id>sample-network-01</internal_network_id> <name>sample-network-01</name> <network_id>9ad32b6f-bb65-4a09-b a7dfd00</network_id> <shared>false</shared> <tenant_id>4f384dfc667a4776bc3169da27d09db5</tenant_id> </network> <network> <admin_state_up>true</admin_state_up> 17
18 <external_network_id>5661d66b-6ac4-49ae-b744- a5593f4aafbb</external_network_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <internal_network_id>sample-network-02</internal_network_id> <name>sample-network-02</name> <network_id>5661d66b-6ac4-49ae-b744-a5593f4aafbb</network_id> <shared>false</shared> <tenant_id>4f384dfc667a4776bc3169da27d09db5</tenant_id> </network> </networks> 18
19 Create Network for Tenant Verb URI Description POST /v0/{internal_tenant_id}/networks/{ Creates a internal_network_id} network for tenant Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging callback Header String Yes URL to be used for callback internal_tenant_id internal_network_id Template String Template String Yes Yes Internal Tenant ID provided by ESC NB client Internal Network ID provided by ESC NB client name Body String Yes Network name admin_state_up Body Boolean No Description about the tenant shared Body Boolean No Indicates whether this 19
20 network is shared across all tenants. By default, only administrativ e users can change this value. provider:network_type Body String No Provider network type for instance vlan provider:physical_networ k Body String No Provider physical network provider:segmentation_id Body String No Vlan ID Request Example: POST /v0/123/networks/567 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/createnetworkcallback <?xml version="1.0" encoding="utf-8"?> <network xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <name>sample-network-01</name> <admin_state_up>true</admin_state_up> <shared>false</shared> </network> Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Internal Server Error (500), Conflict (409) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request 20
21 esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: ESC is processing the request Response(callback) Response Codes Normal Response Code(s): 200 Error Response Code(s): Internal Server Error 500 Response(callback) Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-status-code Header String Code representing Http status code esc-status-message Header String A message describing the response could be a success or error message status Body String The network status. name Body String The network name. admin_state_up Body Boolean A Boolean value that indicates the administrative status of the network. external_tenant_id Body String OpenStack tenant ID of network owner external_network_id Body String Openstack network ID. shared Body Boolean Indicates whether this 21
22 network is shared across all tenants. By default, only administrative users can change this value. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Success <?xml version="1.0" encoding="utf-8"?> <network> <admin_state_up>true</admin_state_up> <external_network_id>9ad32b6f-bb65-4a09-b a7dfd00</external_network_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <internal_network_id>sample-network-01</internal_network_id> <name>sample-network-01</name> <shared>false</shared> </network> 22
23 Get Network for Tenant Verb URI Description GET /v0/{internal_tenant_id}/networks/{inter nal_network_id} Shows information for the specified network NOTE: The GET request will return successfully only if the network was created under the tenant or if the network is shared. So it is valid to get a network created under a different tenant id, as long as the network was created as shared. Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client internal_network_id Template String Yes Internal Network ID provided by ESC NB client Request Example: GET /v0/123/networks/567 HTTP/1.1 23
24 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error, 404 Resource Not found Response Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request status Body String The network status. subnets Body List The associated subnets. name Body String The network name. admin_state_up Body Boolean A Boolean value that indicates the administrative status of the network. external_tenant_id Body String OpenStack tenant ID of network owner external_network_id Body String Openstack network ID. shared Body Boolean Indicates whether this network is shared across all tenants. By default, only administrative users can change this value. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT 24
25 ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <network> <admin_state_up>true</admin_state_up> <external_network_id>9ad32b6f-bb65-4a09-b a7dfd00</external_network_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <internal_network_id>sample-network-01</internal_network_id> <name>sample-network-01</name> <network_id>9ad32b6f-bb65-4a09-b a7dfd00</network_id> <shared>false</shared> <tenant_id>4f384dfc667a4776bc3169da27d09db5</tenant_id> </network> 25
26 Delete Network for Tenant Verb URI Description DELET E /v0/{internal_tenant_id}/networks/{internal _network_id} Deletes the specified network and its associated resources. Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging callback Header String Yes URL to be used for callback internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client internal_network_id Template String Yes Internal Network ID provided by ESC NB client Request Example: DELETE /v0/123/networks/567 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/deletenetworkcallback 26
27 Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Resouce Not Found (404), Internal Server Error (500) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: ESC is processing the request Response(callback) Response Codes Normal Response Code(s): 200 Error Response Code(s): Network In Use (409), Internal Server Error (500) Response(callback) Parameters Name Style Type Description esctransaction-id Header String A unique internal transaction ID generated by ESC for every request esc-statuscode Header String Code representing Http status code esc-statusmessage Header String A message describing the response could be a success or 27
28 error message Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Success 28
29 3) Subnets List Subnets for Tenant Verb URI Description GET /v0/{internal_tenant_id}/subnets Lists subnets to which the specified tenant has access. Request Request Parameters: Name Style Type Required Description Header String No Transaction ID supplied by ESC NB client used for debugging and logging clienttransaction-id internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client Request Example: GET /v0/123/subnets HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error Response Parameters 29
30 Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request name Body String Human-readable name for this subnet (might not be unique). external_tenant_id Body String OpenStack tenant ID of network owner external_network_id Body String Openstack network ID. allocation_pools Body List List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax: <start> </start> <end> </end> gateway_ip Body String Default gateway used by devices in this subnet. ip_version Body String IP version. cidr Body String IP range for this subnet, based on the IP version. external_subnet_id Body String OpenStack subnet ID enable_dhcp Body Boolean Specifies whether DHCP is enabled for this subnet. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <subnets> <subnet> <cidr> /24</cidr> <enable_dhcp>true</enable_dhcp> <external_network_id>9ad32b6f-bb65-4a09-b a7dfd00</external_network_id> <external_subnet_id>0ff5c75c-69fa-450f c1d1a4842f4</external_subnet_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <gateway_ip> </gateway_ip> <internal_subnet_id>sample-subnet-01</internal_subnet_id> <ip_version>4</ip_version> <name>sample-subnet-01</name> <network_id>9ad32b6f-bb65-4a09-b a7dfd00</network_id> 30
31 <subnet_id>0ff5c75c-69fa-450f c1d1a4842f4</subnet_id> </subnet> <subnet> <cidr> /24</cidr> <enable_dhcp>true</enable_dhcp> <external_network_id>5661d66b-6ac4-49ae-b744- a5593f4aafbb</external_network_id> <external_subnet_id>c332ae2a eb9-ac39- cb554e0ccb63</external_subnet_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <gateway_ip> </gateway_ip> <internal_subnet_id>sample-subnet-02</internal_subnet_id> <ip_version>4</ip_version> <name>sample-subnet-02</name> <network_id>5661d66b-6ac4-49ae-b744-a5593f4aafbb</network_id> <subnet_id>c332ae2a eb9-ac39-cb554e0ccb63</subnet_id> </subnet> </subnets> 31
32 32
33 Create Subnet for Tenant Verb URI Description POST /v0/{internal_tenant_id}/subnets/{interna l_subnet_id} Creates a subnet on a specified network. NOTE: a List request will return all subnets that are created in a shared network. So subnets that were created with a different internal_tenant_id that are in a shared network will be returned. Request Request Parameters: Name Style Type Requir ed clienttransaction-id name Body String internal_subnet_id internal_tenant_id internal_network_id Body Description Header String No Transaction ID supplied by ESC NB client used for debugging and logging Template String Template String String No Yes Yes Yes Human-readable name for this subnet (might not be unique). Internal Subnet ID provided by ESC NB client Internal Tenant ID provided by ESC NB client. Should be owner of the network Internal Network ID provided by ESC NB Client. Should be the Network ID with which this subnet is associated. allocation_pools Body List No List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax: <start> </start> <end> </end> gateway_ip Body String No Default gateway used by devices in this subnet. 33
34 ip_version Body String No IP version. cidr Body String No IP range for this subnet, based on the IP version. enable_dhcp Body Boolea n No Specifies whether DHCP is enabled for this subnet. callback Body Header No URL to be used for callback Request Example: POST /v0/123/subnets/567 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/createsubnetcallback <?xml version="1.0" encoding="utf-8"?> <subnet xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <name>sample-subnet-01</name> <internal_network_id>sample-network-01</internal_network_id> <enable_dhcp>true</enable_dhcp> <ip_version>4</ip_version> <cidr> /24</cidr> <gateway_ip> </gateway_ip> <allocation_pools> <start> </start> <end> </end> </allocation_pools> </subnet> Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Internal Server Error (500) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-request-status Header String A message describing the status of the 34
35 request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: ESC is processing the request Response(callback) Response Codes Normal Response Code: Created 200 Error Response Codes: Conflict 409, Internal Server Error 500 Response(callback) Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-status-code Header String Code representing Http status code esc-status-message Header String A message describing the response could be a success or error message name Body String Human-readable name for this subnet (might not be unique). external_tenant_id Body String OpenStack tenant ID of network owner external_network_id Body String Openstack network ID. allocation_pools Body List List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax: <start> </start> <end> </end> gateway_ip Body String Default gateway used by devices in this subnet. ip_version Body String IP version. 35
36 cidr Body String IP range for this subnet, based on the IP version. external_subnet_id Body String Openstack subnet ID. enable_dhcp Body Boolean Specifies whether DHCP is enabled for this subnet. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Success <?xml version="1.0" encoding="utf-8"?> <subnet> <cidr> /24</cidr> <enable_dhcp>true</enable_dhcp> <external_network_id>9ad32b6f-bb65-4a09-b a7dfd00</external_network_id> <external_subnet_id>0ff5c75c-69fa-450f c1d1a4842f4</external_subnet_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <gateway_ip> </gateway_ip> <internal_network_id>sample-network-01</internal_network_id> <internal_subnet_id>sample-subnet-01</internal_subnet_id> <ip_version>4</ip_version> <name>sample-subnet-01</name> <allocation_pools> <start> </start> <end> </end> </allocation_pools> </subnet> 36
37 37
38 Get Subnet for Tenant Ver b GET URI /v0/{internal_tenant_id}/subnets/{internal_sub net_id} Description Shows information for a specified subnet. NOTE: The GET request will return successfully only if the subnet was created under the tenant or if the subnet is in a network that is shared. So it is valid to get a subnet created under a different tenant id, as long as the subnet is under a network created as shared. Request Request Parameters: Name Style Type Required Description Header String No Transaction ID supplied by ESC NB client used for debugging and logging clienttransaction-id internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client internal_subnet_id Template String Yes Internal Subnet ID provided by ESC NB client. Request Example: GET /v0/123/subnets/789 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml 38
39 Client-Transaction-Id: Response Response Codes Normal Response Code: 200 Error Response Codes: 400 Bad Request, 500 Internal Server Error, 404 Resource Not found Response Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request name Body String Human-readable name for this subnet (might not be unique). external_tenant_id Body String OpenStack tenant ID of network owner external_network_id Body String Openstack network ID. allocation_pools Body List List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax: <start> </start> <end> </end> gateway_ip Body String Default gateway used by devices in this subnet. ip_version Body String IP version. cidr Body String IP range for this subnet, based on the IP version. external_subnet_id Body String Openstack subnet ID. enable_dhcp Body Boolean Specifies whether DHCP is enabled for this subnet. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <subnet> <cidr> /24</cidr> 39
40 <enable_dhcp>true</enable_dhcp> <external_network_id>5661d66b-6ac4-49ae-b744- a5593f4aafbb</external_network_id> <external_subnet_id>c332ae2a eb9-ac39- cb554e0ccb63</external_subnet_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <gateway_ip> </gateway_ip> <internal_subnet_id>sample-subnet-02</internal_subnet_id> <ip_version>4</ip_version> <name>sample-subnet-02</name> <network_id>5661d66b-6ac4-49ae-b744-a5593f4aafbb</network_id> <subnet_id>c332ae2a eb9-ac39-cb554e0ccb63</subnet_id> </subnet> Delete Subnet for Tenant Verb URI Description DELET E /v0/{internal_tenant_id}/subnets/{internal_su bnet_id} Deletes a specified subnet. Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging internal_tenant_id Template String Yes Internal Tenant ID provided by ESC NB client internal_subnet_id Template String Yes Internal Subnet ID provided by ESC NB client. 40
41 callback Header String Yes URL to be used for callback Request Example: DELETE /v0/123/subnets/789 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/deletesubnetcallback Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Internal Server Error (500) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: ESC is processing the request Response(callback) 41
42 Response Codes Normal Response Code: 200 Error Response Codes: Unauthorized (401), Not Found (404), Conflict (409), Internal Server Error (500) Response(callback) Parameters Name Style Type Description Header esctransaction-id esc-statuscode esc-statusmessage Header Header String A unique internal transaction ID generated by ESC for every request String Code representing Http status code String A message describing the response could be a success or error message Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Success 42
43 43
44 4) Images List Images Verb URI Description GET /v0/images Lists all images. NOTE: a List request will return all root images (i.e images not created by service registration). Request Request Parameters: Name Style Type Required Description clienttransaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging Request Example: GET /v0/images HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Codes: 400 Bad Request, 500 Internal Server Error Response Parameters Name Style Type Description name Body String The image name. external_tenant_id Body String OpenStack tenant ID of image owner. 44
45 external_image_id Body String Openstack image ID. internal_tenant_id Body String ESC tenant ID of image owner. internal_image_id Body String Internal image ID. cloud_init_support** Body String container_format Body String Format of the container disk_bus Body String Root disk bus. disk_format Body String Format of the disk. imagechecksum Body String Hash of the image data used. imageisenabled** Body Boolean public Body Boolean Image visibility. Public or private. Default is public. serial_console** Body Boolean src Body String Image location as supplied in the request. ** These fields display default values and are not actually implemented. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jul :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <images> <image xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <cloud_init_support></cloud_init_support> <container_format>bare</container_format> <disk_bus>virtio</disk_bus> <disk_format>qcow2</disk_format> <e1000_net>false</e1000_net> <external_image_id>aa a-4d1e-a58a- 458c07d71268</external_image_id> <external_tenant_id>32c d744ff8781c9ea169aee97</external_tenant_id> <imagechecksum>133eae9fb1c98f45894a4e60d </imagechecksum> <imageisenabled>true</imageisenabled> <name>cirros-image-indep</name> <internal_image_id>cirros-image-indep</internal_image_id> <internal_tenant_id>systemadmintenantid</internal_tenant_id> <public>true</public> <serial_console>true</serial_console> 45
46 <src> x86_64-disk.img</src> <virtio_net>true</virtio_net> </image> </images> Create an Image Verb URI Description POST /v0/images/{internal_image_id} Creates an image Request Request Parameters: Name Style Type Requ Description ired client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging callback Header String Yes URL to be used for callback internal_image_id Template String Yes Internal Image ID provided by ESC NB client name Body String Yes Image name src Body String Yes Image location. disk_format Body String Yes Format of the disk. A valid value is vmdk, raw or qcow2. container_format Body String No Format of the container serial_console** Body Boolean No size* Body Integer No Size of the image sizeunit* Body String No Size unit e1000_net Body Boolean No True if image has 46
47 e1000 drivers virtio_net Body Boolean No True if image has VIRTIO drivers disk_bus Body String Yes Root disk bus. A valid value is ide, scsi or virtio. * Not suggested to use. ** These fields are not implemented. Request Example: POST /v0/images/cirros-image-indep HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/createimagecallback <?xml version="1.0" encoding="utf-8"?> <esc_datamodel xmlns=" <images> <image> <name>cirros-image-indep</name> <src>file://cisco/images/cirros x86_64-disk.img</src> <disk_format>qcow2</disk_format> <container_format>bare</container_format> <serial_console>true</serial_console> <disk_bus>virtio</disk_bus> </image> </images> </esc_datamodel> Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Internal Server Error (500), Conflict (409), User Not Found (404) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-request-status Header String A message describing the status of the 47
48 request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jul :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: Request submitted for create images.results will be sent to Response(callback) Response Codes Normal Response Code(s): 200 Error Response Code(s): Internal Server Error 500 Response(callback) Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-status-code Header String Code representing Http status code esc-status-message Header String A message describing the response could be a success or error message name Body String The image name. external_tenant_id Body String OpenStack tenant ID of image owner. external_image_id Body String Openstack image ID. internal_tenant_id Body String ESC tenant ID of image owner. internal_image_id Body String Internal image ID. cloud_init_support** Body String container_format Body String Format of the container disk_bus Body String Root disk bus. disk_format Body String Format of the disk. imagechecksum Body String Hash of the image data 48
49 used. imageisenabled** Body Boolean size Body String The size of the image data, in bytes. public Body Boolean Image visibility. Public or private. Default is public. serial_console** Body Boolean src Body String Image location as supplied in the request. ** These fields just display default values and are not actually implemented. Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Image creation completed successfully. <?xml version="1.0" encoding="utf-8" standalone="yes"?> <image xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <cloud_init_support/> <container_format>bare</container_format> <disk_bus>virtio</disk_bus> <disk_format>qcow2</disk_format> <event_type>create_image</event_type> <external_image_id>bce8770b-bc4a-4be9-bc00-697fcc160201</external_image_id> <external_tenant_id>32c d744ff8781c9ea169aee97</external_tenant_id> <imagechecksum>133eae9fb1c98f45894a4e60d </imagechecksum> <imageisenabled>true</imageisenabled> <name>cirros-image-indep</name> <size> </size> <internal_image_id>cirros-image-indep</internal_image_id> <internal_tenant_id>systemadmintenantid</internal_tenant_id> <public>true</public> <serial_console>true</serial_console> <src>file://cisco/images/cirros x86_64-disk.img</src> </image> Get an Image Verb URI Description GET /v0/images/{internal_image_id} Shows information 49
50 for the specified image Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging internal_image_id Template String Yes Internal Image ID provided by ESC NB client Request Example: GET /v0/images/cirros-image-indep HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error, 404 Resource Not found Response Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for 50
51 every request name Body String The image name external_tenant_id Body String OpenStack tenant ID of image owner external_image_id Body String Openstack image ID internal_tenant_id Body String ESC tenant ID of image owner internal_image_id Body String Internal image ID cloud_init_support Body String Not supported** container_format Body String Format of the container disk_bus Body String Root disk bus disk_format Body String Format of the disk imagechecksum Body String Hash of the image data used imageisenabled Body Boolean Not supported** public Body Boolean Image visibility. Public or private. Default is public. serial_console Body Boolean Not implemented*** src Body String Image location as supplied in the request Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <image xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <cloud_init_support></cloud_init_support> <container_format>bare</container_format> <disk_bus>virtio</disk_bus> <disk_format>qcow2</disk_format> <external_image_id>9b65523e-a31d c20-48eae40368fc</external_image_id> <external_tenant_id>32c d744ff8781c9ea169aee97</external_tenant_id> <imagechecksum>133eae9fb1c98f45894a4e60d </imagechecksum> <imageisenabled>true</imageisenabled> <name>cirros-image-indep</name> <internal_image_id>cirros-image-indep</internal_image_id> <internal_tenant_id>systemadmintenantid</internal_tenant_id> <public>true</public> <serial_console>true</serial_console> 51
52 <src>file://cisco/images/cirros x86_64-disk.img</src> </image> Delete an Image Verb URI Description DELETE /v0/images/{internal_image_id} Deletes the specified image Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging callback Header String Yes URL to be used for callback internal_image_id Template String Yes Internal Image ID provided by ESC NB client Request Example: DELETE /v0/images/cirros-image-indep HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/deleteimagecallback Response (synchronous) Normal Response Code(s):
53 Error Response Code(s): Bad Request (400), Resouce Not Found (404), Internal Server Error (500) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jul :00:00 GMT ESC-Transaction-Id: ESC-Request-Status: Request submitted for delete images.results will be sent to Response(callback) Response Codes Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Not Found (404), Internal Server Error (500), Not Acceptable (406) Response(callback) Parameters Name Style Type Description Header esctransaction-id esc-statuscode esc-statusmessage Header Header String A unique internal transaction ID generated by ESC for every request String Code representing Http status code String A message describing the response. Could be a success or error message 53
54 Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jul :00:00 GMT ESC-Transaction-Id: ESC-Status-Code: 200 ESC-Status-Message: Image deletion completed successfully. 54
55 5) Flavors List Flavors Verb URI Description GET /v0/flavors List flavors NOTE: a List request will return all root flavors (i.e flavors not created by service registration). Request Request Parameters: Name Style Type Required Description client-transaction-id Header String No Transaction ID supplied by ESC NB client used for debugging and logging Request Example: GET /v0/flavors HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code(s): 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error Response Parameters Name Style Type Description name Body String Flavor name ephemeral_disk_mb Body String Specifies the size of a secondary ephemeral 55
56 data disk external_flavor_id Body String Openstack image ID internal_flavor_id Body String Internal flavor ID memory_mb Body String Amount of memory in Mega Bytes per VM instance public Body Boolean Flavor access root_disk_mb Body String Virtual root disk size swap_disk_mb Body String Optional swap space allocation for the instance vcpus Body String Number of virtual CPUs per VM instance Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 Content-Length: 200 Date: Sun, 1 Jul :00:00 GMT <?xml version="1.0" encoding="utf-8"?> <flavors> <flavor xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>db0209a5-cf8a-4eaa-89a a</external_flavor_id> <name>myflavor1</name> <internal_flavor_id>myflavor1</internal_flavor_id> <memory_mb>512</memory_mb> <public>true</public> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>1</vcpus> </flavor> <flavor xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>e31f517d-e0bf-44d2-8e3dcf70d22f809c</external_flavor_id> <name>myflavor2</name> <internal_flavor_id>myflavor2</internal_flavor_id> <memory_mb>512</memory_mb> <public>true</public> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>1</vcpus> </flavor> </flavors> 56
Cisco Elastic Service Controller 1.0 REST API Guide
Cisco Elastic Service Controller 1.0 REST API Guide Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website
More informationGET operations are synchronous the request/response parameters are described with an example of a request/response
ESC REST API ESC REST Northbound API Documentation Table of Contents Resources managed by ESC REST Behavior of ESC REST operations ESC REST API Headers/Path/Body Callbacks Media Internal IDs Body String
More informationThe following sections below list the deployment scenarios and also list all the requirement XML files.
Cisco Elastic Services Controller (ESC) is a Virtual Network Functions Manager (VNFM), performing life cycle management of Virtual Network Functions (VNFs). ESC provides agentless and multi-vendor VNF
More informationThe following sections below list the deployment scenarios and also list all the requirement XML files.
Cisco Elastic Services Controller (ESC) is a Virtual Network Functions Manager (VNFM), performing life cycle management of Virtual Network Functions (VNFs). ESC provides agentless and multi-vendor VNF
More informationVirtual Network Functions Life Cycle Management
Virtual Network Functions Life Cycle Management Cisco Elastic Services Controller (ESC) provides a single point of control to manage all aspects of VNF lifecycle for generic virtual network functions (VNFs)
More informationVirtual Network Functions Life Cycle Management
Virtual Network Functions Life Cycle Management Cisco Elastic Services Controller (ESC) provides a single point of control to manage all aspects of VNF lifecycle for generic virtual network functions (VNFs)
More informationCisco Elastic Service Controller 1.1 NETCONF API Guide
Cisco Elastic Service Controller 1.1 NETCONF API Guide Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website
More informationDeploying Virtual Network Functions
You can orchestrate VNFs within a virtual infrastructure domain either on OpenStack or VMware vcenter. A VNF deployment is initiated as a service request through northbound interface or the ESC portal.
More informationVM Lifecycle Management APIs
VM Image Registration APIs, page 1 Custom Flavor Creation APIs, page 4 VM Deployment APIs, page 8 VM Action APIs, page 21 VM Backup APIs, page 23 VM Network APIs, page 24 Network File System APIs, page
More informationCisco Elastic Service Controller 1.0 NETCONF API Guide
Cisco Elastic Service Controller 1.0 NETCONF API Guide Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website
More informationAPI reference (Network)
FUJITSU Cloud Service K5 IaaS API reference (Network) Version 1.5 FUJITSU LIMITED All Rights Reserved, Copyright Fujitsu Limited 2015-2016 K5IA-DC-M-001-001E Preface Structure of the manuals Manual Title
More informationCisco Elastic Service Controller 3.0 Netconf API Guide
Cisco Elastic Service Controller 3.0 Netconf API Guide Updated: July, 2017 Contents 1 INTRODUCTION... 5 1.1 Using NETCONF API... 5 1.1.1 Get configuration... 5 1.1.2 Get non-configurable data... 5 1.1.3
More informationHealing Virtual Network Functions
Healing Overview, page 1 Healing a VM, page 1 Recovery and Redeployment Policies, page 5 Enabling and Disabling the Host, page 9 Notifications and Events, page 11 Healing Overview As part of life cycle
More informationUsing the vrealize Orchestrator OpenStack Plug-In 2.0. Modified on 19 SEP 2017 vrealize Orchestrator 7.0
Using the vrealize Orchestrator OpenStack Plug-In 2.0 Modified on 19 SEP 2017 vrealize Orchestrator 7.0 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/
More informationMulti-Tenant Accounting in OpenStack
Jorge L Williams Ziad N Sawalha Khaled Hussein Abstract As a cloud computing platform, OpenStack must support the concept
More informationUser Workspace Management
Access the Interface, page 1 User Management Workspace User Types, page 4 Projects (Admin User), page 5 Users (Admin User), page 9 CML Server (Admin User), page 11 Connectivity, page 30 Using the VM Control
More informationGR Installation - OpenStack
, page 1 Arbiter Installation on OpenStack, page 5 Configuration Parameters - GR System, page 8 The examples given in the steps is for your reference only. You need to modify them based on your GR deployments.
More informationVirtual Infrastructure Manager Installation Automation
Virtual Infrastructure Manager Installation Automation Feature Summary and Revision History, page 1 Feature Description, page 2 VIM Installation Automation Overview, page 2 Sample Configuration Files,
More informationVM Life Cycle Management
VM life cycle management refers to the entire process of registering, deploying, updating, monitoring VMs, and getting them service chained as per your requirements. You can perform these tasks and more
More informationTenant Onboarding. Tenant Onboarding Overview. Tenant Onboarding with Virtual Data Centers
Overview, page 1 with Virtual Data Centers, page 1 with Resource Groups, page 5 Overview In Cisco UCS Director, tenants enable you to securely control and allocate the virtual and physical infrastructure
More informationVirtual Private Cloud. User Guide. Issue 03 Date
Issue 03 Date 2016-10-19 Change History Change History Release Date What's New 2016-10-19 This issue is the third official release. Modified the following content: Help Center URL 2016-07-15 This issue
More informationCreating Application Containers
This chapter contains the following sections: General Application Container Creation Process, page 1 Creating Application Container Policies, page 2 About Application Container Templates, page 5 Creating
More informationAPI-based VNFM Upgrade Process
Feature Summary and Revision History, on page 1 Feature Description, on page 2 VNFM Upgrade Workflow, on page 2 Initiating the VNFM Upgrade, on page 4 Limitations, on page 7 Feature Summary and Revision
More informationIaaS Integration for Multi- Machine Services. vrealize Automation 6.2
IaaS Integration for Multi- Machine Services vrealize Automation 6.2 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about
More informationDigital Imaging and Communications in Medicine (DICOM) Supplement 194: RESTful Services for Non-Patient Instances
1/20/2016 3:37 PM Supplement XXX: Non-Patient Instances RESTful Service Page 1 5 10 Digital Imaging and Communications in Medicine (DICOM) Supplement 194: RESTful Services for Non-Patient Instances 15
More informationService Portal User Guide
FUJITSU Cloud Service K5 IaaS Service Portal User Guide Version 1.4 FUJITSU LIMITED All Rights Reserved, Copyright FUJITSU LIMITED 2015-2016 K5IA-DC-M-005-001E Preface Purpose of This Manual This manual
More informationMediant Cloud Edition (CE)
Installation Manual AudioCodes Mediant Family of Session Border Controllers (SBC) Mediant Cloud Edition (CE) Session Border Controller Version 7.2 Installation Manual Contents Table of Contents 1 Introduction...
More informationVM Image Packaging. VM Image Packaging Utility. Contents
is a tool for converting qcow2 and img images into a tar.gz format with additional properties and profiles. VM image packaging can be done in two ways: Utility: This is an enhanced packaging process that
More informationVMware Integrated OpenStack User Guide. VMware Integrated OpenStack 4.1
VMware Integrated OpenStack User Guide VMware Integrated OpenStack 4.1 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about
More informationWeb Cloud Solution. User Guide. Issue 01. Date
Issue 01 Date 2017-05-30 Contents Contents 1 Overview... 3 1.1 What Is Web (CCE+RDS)?... 3 1.2 Why You Should Choose Web (CCE+RDS)... 3 1.3 Concept and Principle... 4... 5 2.1 Required Services... 5 2.2
More informationConfiguring Virtual Networks Using OpenStack
This chapter contains the following sections: Information About Virtual Networks, page 1 Guidelines and Limitations for the OpenStack Dashboard, page 1 Creating a Virtual Network Workflow, page 2 Creating
More informationStorageGRID Webscale 10.3 Software Installation Guide for OpenStack Deployments
StorageGRID Webscale 10.3 Software Installation Guide for OpenStack Deployments September 2016 215-10818_A0 doccomments@netapp.com Table of Contents 3 Contents Deployment planning and preparation... 5
More informationVMware Integrated OpenStack User Guide
VMware Integrated OpenStack User Guide VMware Integrated OpenStack 3.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a
More informationManaging VMware vcenter Site Recovery Manager
Managing VMware vcenter Site Recovery Manager This chapter contains the following sections: About VMware vcenter Site Recovery Manager, page 1 Overview of SRM Configuration, page 2 Integrating SRM with
More informationCreating Application Containers
This chapter contains the following sections: General Application Container Creation Process, page 1 Creating Application Container Policies, page 3 About Application Container Templates, page 5 Creating
More informationInstalling the Cisco IOS XRv 9000 Router in KVM Environments
Installing the Cisco IOS XRv 9000 Router in KVM Environments These file types are needed to install Cisco IOS XRv 9000 Router on the KVM hypervisor:.qcow2 Used for booting the software image in KVM OpenStack
More informationIsn't it Ironic? Managing a bare metal cloud. devananda.github.io/talks/isnt-it-ironic.html. Devananda van der Veen
Isn't it Ironic? Managing a bare metal cloud Devananda van der Veen twitter: @devananda devananda.github.io/talks/isnt-it-ironic.html Who am I Master Engineer at HP OpenStack Ironic PTL OpenStack Technical
More informationReviewing the API Documentation
About the Cisco APIC-EM API Documentation, page 1 Testing the Cisco APIC-EM APIs, page 6 About the Cisco APIC-EM API Documentation Cisco APIC-EM controller provides interactive, northbound Representational
More informationLibelium Cloud Hive. Technical Guide
Libelium Cloud Hive Technical Guide Index Document version: v7.0-12/2018 Libelium Comunicaciones Distribuidas S.L. INDEX 1. General and information... 4 1.1. Introduction...4 1.1.1. Overview...4 1.2. Data
More informationIaaS Integration for Multi-Machine Services
IaaS Integration for Multi-Machine Services vcloud Automation Center 6.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by
More informationInformation About SIP Compliance with RFC 3261
APPENDIX A Information About SIP Compliance with RFC 3261 This appendix describes how the Cisco SIP IP phone complies with the IETF definition of SIP as described in RFC 3261. It has compliance information
More informationSilver Peak Systems. Installing EdgeConnect on Cisco ENCS
Silver Peak Systems Installing EdgeConnect on Cisco ENCS Contents Installing EdgeConnect on Cisco ENCS Overview... 1 Assumptions and Prerequisites... 2 Procedure... 2 Upload the EdgeConnect KVM image to
More informationCreate a pfsense router for your private lab network template
Create a pfsense router for your private lab network template Some labs will require a private network where you can deploy services like DHCP. Here are instructions for setting up an uplink router for
More informationCisco Prime Service Catalog Virtual Appliance Quick Start Guide 2
Cisco Prime Service Catalog 11.1.1 Virtual Appliance Quick Start Guide Cisco Prime Service Catalog 11.1.1 Virtual Appliance Quick Start Guide 2 Introduction 2 Before You Begin 2 Preparing the Virtual Appliance
More informationRESTCONF Programmable Interface
This chapter describes how to set-up and configure an HTTP-based protocol-representational State Transfer Configuration Protocol (RESTCONF). RESTCONF provides a programmatic interface based on standard
More informationSecuring Containers Using a PNSC and a Cisco VSG
Securing Containers Using a PNSC and a Cisco VSG This chapter contains the following sections: About Prime Network Service Controllers, page 1 Integrating a VSG into an Application Container, page 4 About
More informationSecuring Containers Using a PNSC and a Cisco VSG
Securing Containers Using a PNSC and a Cisco VSG This chapter contains the following sections: About Prime Network Service Controllers, page 1 Integrating a VSG into an Application Container, page 3 About
More informationWhat s New with VMware vcloud Director 8.0
Feature Overview TECHNICAL WHITE PAPER Table of Contents What s New with VMware....3 Support for vsphere 6.0 and NSX 6.1.4....4 VMware vsphere 6.0 Support...4 VMware NSX 6.1.4 Support....4 Organization
More informationVer Enterprise Cloud. User s Guide for. API Function. ver1.03
Enterprise Cloud User s Guide for API Function ver1.03 1 Index Index... 2 1 Use of this document... 4 2 Common Information... 5 API use flow...5 Preparation...5 API Workflow...5 API Endpoint...6 3 API
More informationSequel SMRT Link Web Services API v4.0.0 Guide. Pacific Biosciences
Sequel SMRT Link Web Services API v4.0.0 Guide Pacific Biosciences CONTENTS Chapter 1- Introduction... 5 1.1 Authentication... 5 Chapter 2 - SMRT Link Service API... 6 2.1 Run Design Service... 6 2.1.1
More informationPost Installation Tasks
This chapter contains the following sections: Changing the ESC Password, page 1 Configuring Pluggable Authentication Module (PAM) Support for Cisco Elastic Services Controller, page 3 Authenticating REST
More informationDevelop Mobile Front Ends Using Mobile Application Framework A - 2
Develop Mobile Front Ends Using Mobile Application Framework A - 2 Develop Mobile Front Ends Using Mobile Application Framework A - 3 Develop Mobile Front Ends Using Mobile Application Framework A - 4
More informationQuick Start Guide to Compute Canada Cloud Service
Quick Start Guide to Compute Canada Cloud Service Launching your first instance (VM) Login to the East or West cloud Dashboard SSH key pair Importing an existing key pair Creating a new key pair Launching
More informationNDEV Mobile HTTP Services for NDEV Mobile Clients
NDEV Mobile HTTP Services for NDEV Mobile Clients Notice NDEV Mobile HTTP Services for NDEV Mobile Clients Copyright 2011-2012 Nuance Communications, Inc. All rights reserved. Published by Nuance Communications,
More informationREST Web Services Objektumorientált szoftvertervezés Object-oriented software design
REST Web Services Objektumorientált szoftvertervezés Object-oriented software design Dr. Balázs Simon BME, IIT Outline HTTP REST REST principles Criticism of REST CRUD operations with REST RPC operations
More informationDetermine the DN of an Object Within the APIC GUI
Determine the DN of an Object Within the APIC GUI Document ID: 119419 Contributed by Shae Eastman and Gabriel Monroy, Cisco TAC Engineers. Jan 04, 2016 Contents Introduction Determine the DN of an Object
More informationLB Cache Quick Start Guide v1.0
LB Cache Quick Start Guide v1.0 Rev. 1.1.0 Copyright 2002 2017 Loadbalancer.org, Inc Table of Contents Introduction...3 About LBCache...3 Amazon Terminology...3 Getting Started...3 Deployment Concepts...4
More informationInstalling and Configuring Devstack Newton for Infoblox Integration
DEPLOYMENT GUIDE Installing and Configuring Devstack Newton for Infoblox Integration 2017 Infoblox Inc. All rights reserved. Installing and Configuring Devstack Newton for Infoblox Integration Page 1 of
More informationCisco Nexus 1000V InterCloud
Deployment Guide Cisco Nexus 1000V InterCloud Deployment Guide (Draft) June 2013 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 49 Contents
More information04 Webservices. Web APIs REST Coulouris. Roy Fielding, Aphrodite, chp.9. Chp 5/6
04 Webservices Web APIs REST Coulouris chp.9 Roy Fielding, 2000 Chp 5/6 Aphrodite, 2002 http://www.xml.com/pub/a/2004/12/01/restful-web.html http://www.restapitutorial.com Webservice "A Web service is
More informationIntroduction to RESTful Web Services. Presented by Steve Ives
1 Introduction to RESTful Web Services Presented by Steve Ives Introduction to RESTful Web Services What are web services? How are web services implemented? Why are web services used? Categories of web
More informationCisco Virtual Application Cloud Segmentation Services REST API Guide, Release 6.0STV First Published: Last Updated:
Cisco Virtual Application Cloud Segmentation Services REST API Guide, Release 6.0STV3.1.1 First Published: 2016-10-12 Last Updated: 2016-10-12 Cisco Systems, Inc. www.cisco.com 1 Overview Contents Overview...
More informationReuse Floating IP Address
Feature Summary and Revision History, page 1 Feature Description, page 2 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Ultra M Solution Ultra Automation Services
More informationCitrix CloudPlatform (powered by Apache CloudStack) Version 4.5 Concepts Guide
Citrix CloudPlatform (powered by Apache CloudStack) Version 4.5 Concepts Guide Revised January 30, 2015 06:00 pm IST Citrix CloudPlatform Citrix CloudPlatform (powered by Apache CloudStack) Version 4.5
More informationConfiguring Layer 4 to Layer 7 Resource Pools
Configuring Layer 4 to Layer 7 Resource Pools About Layer 4 to Layer 7 Resource Pools, page 1 About External IP Address Pools, page 2 About External Layer 3 Routed Domains and the Associated VLAN Pools,
More informationCloudStack Administration Guide
CloudStack Administration Guide For CloudStack Version 3.0.0 3.0.2 Revised August 16, 2012 4:41 PM 2011, 2012 Citrix Systems, Inc. All rights reserved. Specifications are subject to change without notice.
More informationAPI-based AutoDeploy, AutoIT and AutoVNF Upgrade Process
API-based AutoDeploy, AutoIT and AutoVNF Upgrade Process Feature Summary and Revision History, page 1 Feature Description (AutoDeploy and AutoIT), page 2 AutoDeploy and AutoIT Upgrade Workflow, page 2
More information2 Apache Wink Building Blocks
2 Apache Wink Building Blocks Apache Wink Building Block Basics In order to take full advantage of Apache Wink, a basic understanding of the building blocks that comprise it and their functional integration
More informationVMware vfabric Data Director Programming Guide
VMware vfabric Data Director Programming Guide vfabric Data Director 2.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by
More informationCompliance with RFC 3261
APPENDIX A Compliance with RFC 3261 This appendix describes how the Cisco Unified IP Phone 7960G and 7940G complies with the IETF definition of SIP as described in RFC 3261. It contains compliance information
More informationReST 2000 Roy Fielding W3C
Outline What is ReST? Constraints in ReST REST Architecture Components Features of ReST applications Example of requests in REST & SOAP Complex REST request REST Server response Real REST examples REST
More informationCPM. Quick Start Guide V2.4.0
CPM Quick Start Guide V2.4.0 1 Content 1 Introduction... 3 Launching the instance... 3 CloudFormation... 3 CPM Server Instance Connectivity... 3 2 CPM Server Instance Configuration... 4 CPM Server Configuration...
More informationFile Resource Operations Summary
CHAPTER 10 This chapter describes the Cisco WebEx Social API File resource operations. These operations let you upload to Cisco WebEx Social server a text or binary file (which you can later embed in or
More informationSaaSaMe Transport Workload Snapshot Export for. Alibaba Cloud
SaaSaMe Transport Workload Snapshot Export for Alibaba Cloud Contents About This Document... 3 Revision History... 3 Workload Snapshot Export for Alibaba Cloud... 4 Workload Snapshot Export Feature...
More informationvcloud Director User's Guide 04 OCT 2018 vcloud Director 9.5
vcloud Director User's Guide 04 OCT 2018 vcloud Director 9.5 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this
More informationTroubleshoot PCRF OAM VM Recovery- Openstack
Troubleshoot PCRF OAM VM Recovery- Openstack Contents Introduction Prerequisites Requirements Components Used Background Information CPS VNF Instance Recovery Procedures Troubleshoot Power on Any Instance
More informationMultiple Disk VM Provisioning
This chapter contains the following sections: About, page 1 Overview of the Procedure for, page 2 About Templates with Multiple Disks, page 2 Assigning Disk Categories, page 2 Defining Storage Policies,
More informationIntroduction to Cisco TV CDS Software APIs
CHAPTER 1 Cisco TV Content Delivery System (CDS) software provides two sets of application program interfaces (APIs): Monitoring Real Time Streaming Protocol (RTSP) Stream Diagnostics The Monitoring APIs
More informationCisco ACI Simulator VM Installation Guide
Cisco ACI Simulator VM Installation Guide New and Changed Information 2 About the Application Policy Infrastructure Controller 2 About the ACI Simulator Virtual Machine 2 Simulator VM Topology and Connections
More informationWeb Services Week 10
Web Services Week 10 Emrullah SONUÇ Department of Computer Engineering Karabuk University Fall 2017 1 Recap BPEL Process in Netbeans RESTful Web Services Introduction to Rest Api 2 Contents RESTful Web
More informationDeploying the Cisco ASA 1000V
CHAPTER 2 This chapter includes the following sections: Information About the ASA 1000V Deployment, page 2-1 Downloading the ASA 1000V OVA File, page 2-7 Deploying the ASA 1000V Using the VMware vsphere
More informationApache Wink Developer Guide. Draft Version. (This document is still under construction)
Apache Wink Developer Guide Software Version: 1.0 Draft Version (This document is still under construction) Document Release Date: [August 2009] Software Release Date: [August 2009] Apache Wink Developer
More informationVMware vfabric Data Director Installation Guide
VMware vfabric Data Director Installation Guide vfabric Data Director 1.0.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced
More informationZENworks for Desktops Preboot Services
3.2 Novell ZENworks for Desktops Preboot Services DEPLOYMENT www.novell.com Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation,
More informationInstalling the Cisco CSR 1000v in KVM Environments
Installing the Cisco CSR 1000v in KVM Environments Kernel Virtual Machine Support Information, page 1 KVM Support on OpenStack, page 2 Installation Requirements for KVM Cisco IOS XE Fuji 16.7, page 2 Creating
More informationPart2: Let s pick one cloud IaaS middleware: OpenStack. Sergio Maffioletti
S3IT: Service and Support for Science IT Cloud middleware Part2: Let s pick one cloud IaaS middleware: OpenStack Sergio Maffioletti S3IT: Service and Support for Science IT, University of Zurich http://www.s3it.uzh.ch/
More informationSAP Business One. User Guide. Issue 04 Date HUAWEI TECHNOLOGIES CO., LTD.
Issue 04 Date 2018-12-31 HUAWEI TECHNOLOGIES CO., LTD. Copyright Huawei Technologies Co., Ltd. 2019. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any
More informationPost Installation Tasks
This chapter contains the following sections: Changing the ESC Password, on page 1 Configuring Pluggable Authentication Module (PAM) Support for Cisco Elastic Services Controller, on page 3 Authenticating
More informationSUSE Cloud Admin Appliance Walk Through. You may download the SUSE Cloud Admin Appliance the following ways.
SUSE Cloud Admin Appliance Walk Through First before you proceed with deploying the Admin Appliance you must go through and answer the questionnaire to ensure you have an idea of the scope of the project
More informationIBM Single Sign On for Bluemix Version December Identity Bridge Configuration topics
IBM Single Sign On for Bluemix Version 2.0 28 December 2014 Identity Bridge Configuration topics IBM Single Sign On for Bluemix Version 2.0 28 December 2014 Identity Bridge Configuration topics ii IBM
More informationManaging the VM Lifecycle
This chapter contains the following sections:, page 1 Managing VM Power, page 2 Resizing a VM, page 3 Resizing a VM Disk, page 4 Managing VM Snapshots, page 5 Managing Other VM Actions, page 7 You can
More informationREST Easy with Infrared360
REST Easy with Infrared360 A discussion on HTTP-based RESTful Web Services and how to use them in Infrared360 What is REST? REST stands for Representational State Transfer, which is an architectural style
More informationServices and Networking
This chapter contains the following topics: Load Balancing Kubernetes Services using NGINX, on page 1 Network Policies, on page 6 Load Balancer Services, on page 7 Load Balancing Kubernetes Services using
More informationvshield API Programming Guide
vshield API Programming Guide vshield Manager 4.1.0 Update 1 vshield Zones 4.1.0 Update 1 vshield App 1.0.0 Update 1 vshield Edge 1.0.0 Update 1 vshield Endpoint 1.0.0 Update 1 This document supports the
More informationOpen Archives Initiative Object Reuse & Exchange. Resource Map Discovery
Open Archives Initiative Object Reuse & Exchange Resource Map Discovery Michael L. Nelson * Carl Lagoze, Herbert Van de Sompel, Pete Johnston, Robert Sanderson, Simeon Warner OAI-ORE Specification Roll-Out
More informationOracle 1Z Oracle Cloud Solutions Infrastructure Architect Associate.
Oracle 1Z0-932 Oracle Cloud Solutions Infrastructure Architect Associate https://killexams.com/pass4sure/exam-detail/1z0-932 QUESTION: 76 Which two resources are available by default when your Oracle Cloud
More informationManaging System Administration Settings
This chapter contains the following sections: Setting up the Outgoing Mail Server, page 2 Working with Email Templates, page 2 Configuring System Parameters (Optional), page 5 Updating the License, page
More informationNasuni Data API Nasuni Corporation Boston, MA
Nasuni Corporation Boston, MA Introduction The Nasuni API has been available in the Nasuni Filer since September 2012 (version 4.0.1) and is in use by hundreds of mobile clients worldwide. Previously,
More informationDEEP DIVE: OPENSTACK COMPUTE
DEEP DIVE: OPENSTACK COMPUTE Stephen Gordon Technical Product Manager, Red Hat @xsgordon AGENDA OpenStack architecture refresher Compute architecture Instance life cycle Scaling compute
More informationInstalling and Configuring vcloud Connector
Installing and Configuring vcloud Connector vcloud Connector 2.6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new
More information