Cisco Elastic Service Controller 1.0 REST API Guide

Size: px
Start display at page:

Download "Cisco Elastic Service Controller 1.0 REST API Guide"

Transcription

1 Cisco Elastic Service Controller 1.0 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.0 REST API Guide 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 ) 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 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

4 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 Resources managed by ESC: Tenants, Networks, Subnets, Users, ServiceCatalog, Deployments o GET operations are synchronous the request/response parameters are described with an example of a request/response o 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. o 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 o 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 It is recommended that the ESC north bound client generate internal ids within the scope of the ESC. 5

6 o 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 create tenant/user/network/subnet with Openstack matching name will fail, with callback POST 409 conflict delete tenant/user/network/subnet in delete of tenant/user/network/subnet, Openstack 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 internal_tenant_id Body String NB Client tenant ID name Body String Tenant name 7

8 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 client used for debugging and logging internal_tenant_id Template String Yes Internal 8

9 1..64 Tenant ID provided by ESC NB client Name Body String Yes Tenant name 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 esc-request-status Header String A message describing the status of the request Response(synchronous)Parameters Example 9

10 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 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 10

11 <?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: 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 11

12 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: 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> 12

13 13

14 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 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 14

15 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 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 16

17 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): 200 Error Response Codes: 400 Bad Request, 500 Internal Server Error 17

18 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> <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> 18

19 <network_id>5661d66b-6ac4-49ae-b744-a5593f4aafbb</network_id> <shared>false</shared> <tenant_id>4f384dfc667a4776bc3169da27d09db5</tenant_id> </network> </networks> Create Network for Tenant 19

20 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 network is shared across all tenants. By default, only administrativ e users can change this value. provider:network_type Body String No Provider 20

21 provider:physical_networ k network type for instance vlan 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 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 21

22 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 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:

23 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> 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 23

24 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 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 24

25 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 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 Response (synchronous) 26

27 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 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: 27

28 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 Name Style Type Description 29

30 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> <subnet_id>0ff5c75c-69fa-450f c1d1a4842f4</subnet_id> </subnet> <subnet> 30

31 <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 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. ip_version Body String No IP version. cidr Body String No IP range for this subnet, 32

33 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 request Response(synchronous)Parameters Example 33

34 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. 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. 34

35 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> 35

36 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 Client-Transaction-Id: Response 36

37 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> <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> 37

38 <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. callback Header String Yes URL to be used for callback Request Example: 38

39 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) 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 39

40 esctransaction-id esc-statuscode esc-statusmessage Header 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 4) Service-Catalog 40

41 List all services in ServiceCatalog Verb URI Description GET /v0/servicecatalog Lists registered services. 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/servicecatalog 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): Bad Request (400), Internal Server Error (500) Response Parameters Name Style Type Description esc-transaction-id Header String A unique internal transaction ID generated by ESC for every request Response Example: HTTP/ OK Content-Type: application/xml; charset=utf-8 41

42 Content-Length: 200 Date: Sun, 1 Jan :00:00 GMT ESC-Transaction-Id: <?xml version="1.0" encoding="utf-8"?> <services> <service_registration> <flavor> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>a54750af-2bbb-4d30-b da37366e0</external_flavor_id> <name>sample-service-definition-group_0-sample_vm1</name> <internal_flavor_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-flavor-00-00</internal_flavor_id> <memory_mb>4096</memory_mb> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>2</vcpus> </flavor> <flavor> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>33e495bd-23c6-486f-8e78-0b1877a6bd7d</external_flavor_id> <name>sample-service-definition-group_0-sample_vm2</name> <internal_flavor_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-flavor-00-01</internal_flavor_id> <memory_mb>4096</memory_mb> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>4</vcpus> </flavor> <disk> <cloud_init_support>true</cloud_init_support> <container_format>bare</container_format> <disk_bus>ide</disk_bus> <disk_format>qcow2</disk_format> <disk_prefix>sd</disk_prefix> <e1000_net>true</e1000_net> <external_image_id>9a cd-42fc-9faf- 7a0a1ae09435</external_image_id> <imageisenabled>false</imageisenabled> <name>sample-service-definition-group_0-sample_vm1</name> <internal_image_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-image-00-00</internal_image_id> <serial_console>true</serial_console> <src> </disk> <disk> <cloud_init_support>true</cloud_init_support> <container_format>bare</container_format> <disk_bus>ide</disk_bus> <disk_format>qcow2</disk_format> <disk_prefix>sd</disk_prefix> <e1000_net>true</e1000_net> <external_image_id>b2505bb c03-84b1-486d88ee644d</external_image_id> 42

43 <imageisenabled>false</imageisenabled> <name>sample-service-definition-group_0-sample_vm2</name> <internal_image_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-image-00-01</internal_image_id> <serial_console>true</serial_console> <src> </disk> <internal_service_registration_id>regsample</internal_service_registration_id> <external_service_registration_id>2dee7003-8f9d-4a1c-b2ebf2de1d3daafb</external_service_registration_id> </service_registration> </services> 43

44 Create/Register Service in ServiceCatalog Verb URI Description POST /v0/servicecatalog/{internal_service_reg istration_id} Registers a service to the ServiceCatal og Request Request Parameters: Name Style Type Requi Description red clienttransaction-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 internal_servi ce_registratio n_id Temaplate String reg.xml Body XML data model Yes Yes callback Internal Service Registration ID provided by ESC NB client. The service reg.xml data model Request Example: POST /v0/servicecatalog/123 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/registerservicecallback <datamodel> <version>1.0</version> <service_definition>... </service_definition> </datamodel> Response (synchronous) 44

45 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 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: Created (200) Error Response Code(s): Bad Request (400), 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-status- Header String Code representing Http status code esc-statusmessage code Header String A message describing the response could be a success or error message reg.xml Body XML data model The service reg.xml data model Response Example: 45

46 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"?> <services> <service_registration> <flavor> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>a54750af-2bbb-4d30-b da37366e0</external_flavor_id> <name>sample-service-definition-group_0-sample_vm1</name> <internal_flavor_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-flavor-00-00</internal_flavor_id> <memory_mb>4096</memory_mb> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>2</vcpus> </flavor> <flavor> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>33e495bd-23c6-486f-8e78-0b1877a6bd7d</external_flavor_id> <name>sample-service-definition-group_0-sample_vm2</name> <internal_flavor_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-flavor-00-01</internal_flavor_id> <memory_mb>4096</memory_mb> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>4</vcpus> </flavor> <disk> <cloud_init_support>true</cloud_init_support> <container_format>bare</container_format> <disk_bus>ide</disk_bus> <disk_format>qcow2</disk_format> <disk_prefix>sd</disk_prefix> <e1000_net>true</e1000_net> <external_image_id>9a cd-42fc-9faf- 7a0a1ae09435</external_image_id> <imageisenabled>false</imageisenabled> <name>sample-service-definition-group_0-sample_vm1</name> <internal_image_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-image-00-00</internal_image_id> <serial_console>true</serial_console> <src> </disk> <disk> <cloud_init_support>true</cloud_init_support> <container_format>bare</container_format> <disk_bus>ide</disk_bus> 46

47 <disk_format>qcow2</disk_format> <disk_prefix>sd</disk_prefix> <e1000_net>true</e1000_net> <external_image_id>b2505bb c03-84b1-486d88ee644d</external_image_id> <imageisenabled>false</imageisenabled> <name>sample-service-definition-group_0-sample_vm2</name> <internal_image_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-image-00-01</internal_image_id> <serial_console>true</serial_console> <src> </disk> <internal_service_registration_id>regsample</internal_service_registration_id> <external_service_registration_id>2dee7003-8f9d-4a1c-b2ebf2de1d3daafb</external_service_registration_id> </service_registration> </services> 47

48 Get a specific registered Service in Service Catalog Ver URI b GET /v0/servicecatalog/{internal_service_registration _id} Description Get info for a specific registered service in the ServiceCatalo g 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 internal_servi ce_registratio n_id Temaplat e String Yes Internal Service Registration ID provided by ESC NB client. Request Example: GET /v0/servicecatalog/567 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Response Response Codes Normal Response Code: 200 Error Response Code(s): 400 Bad Request, 500 Internal Server Error, 404 Resource Not found Response Parameters Name Style Type Description 48

49 esctransaction-id Header reg.xml Body XML data model external_servi ce_registratio n_id Body String A unique internal transaction ID generated by ESC for every request The service reg.xml data model String Service Registration ID generated by ESC 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"?> <services> <service_registration> <flavor> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>a54750af-2bbb-4d30-b da37366e0</external_flavor_id> <name>sample-service-definition-group_0-sample_vm1</name> <internal_flavor_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-flavor-00-00</internal_flavor_id> <memory_mb>4096</memory_mb> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>2</vcpus> </flavor> <flavor> <ephemeral_disk_mb>0</ephemeral_disk_mb> <external_flavor_id>33e495bd-23c6-486f-8e78-0b1877a6bd7d</external_flavor_id> <name>sample-service-definition-group_0-sample_vm2</name> <internal_flavor_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-flavor-00-01</internal_flavor_id> <memory_mb>4096</memory_mb> <root_disk_mb>0</root_disk_mb> <swap_disk_mb>0</swap_disk_mb> <vcpus>4</vcpus> </flavor> <disk> <cloud_init_support>true</cloud_init_support> <container_format>bare</container_format> <disk_bus>ide</disk_bus> <disk_format>qcow2</disk_format> <disk_prefix>sd</disk_prefix> <e1000_net>true</e1000_net> 49

50 <external_image_id>9a cd-42fc-9faf- 7a0a1ae09435</external_image_id> <imageisenabled>false</imageisenabled> <name>sample-service-definition-group_0-sample_vm1</name> <internal_image_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-image-00-00</internal_image_id> <serial_console>true</serial_console> <src> </disk> <disk> <cloud_init_support>true</cloud_init_support> <container_format>bare</container_format> <disk_bus>ide</disk_bus> <disk_format>qcow2</disk_format> <disk_prefix>sd</disk_prefix> <e1000_net>true</e1000_net> <external_image_id>b2505bb c03-84b1-486d88ee644d</external_image_id> <imageisenabled>false</imageisenabled> <name>sample-service-definition-group_0-sample_vm2</name> <internal_image_id>d5258a0d-9f4f-4b60-a545-0f2882c07d67-image-00-01</internal_image_id> <serial_console>true</serial_console> <src> </disk> <internal_service_registration_id>regsample</internal_service_registration_id> <external_service_registration_id>2dee7003-8f9d-4a1c-b2ebf2de1d3daafb</external_service_registration_id> </service_registration> </services> 50

51 Delete/Unregister Service in ServiceCatalog Verb URI Description DELETE /v0/servicecatalog/{ internal_service_registration _id } Deletes/Unregiste rs a registered service in the ServiceCatalog Request Request Parameters: Name Style Type Require d Description clienttransaction-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 internal_servi ce_registratio n_id Temaplat e String Yes callback Internal Service Registration ID provided by ESC NB client. Request Example: DELETE /v0/servicecatalog/567 HTTP/1.1 Host: client.host.com Content-Type: application/xml Accept: application/xml Client-Transaction-Id: Callback:/unregisterservicecallback Response (synchronous) Normal Response Code(s): 200 Error Response Code(s): Bad Request (400), Resource Not Found (404), Internal Server Error (500) Response(synchronous)Parameters Name Style Type Description esc-transaction-id Header String A unique internal 51

52 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: 204 Error Response Code(s): Bad Request (400), 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 52

53 53

54 5) Deployments Get All Deployments Verb URI Descri ption GET /v0/deployments Lists deploye d service s. 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/deployments/ 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): Bad Request (400), Internal Server Error (500) Response Parameters Name Style Type Description 54

55 esc-transaction-id Header String A unique internal transaction generated by ESC for every re external_service_deployment_id Body String Deployment ID generated by ES deployments_details Body XML See example below 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"?> <deployments> <deployment> <deployment_stage>vm_deployed</deployment_ stage> <deployment_details> <vm_uuid>26ebf6a5-812e a50-588c6579f70a</vm_uuid> <host_uuid>rereea5-812e a50-588c6579f70a</host_uuid> <interfaces> <network_uuid>0e89b2ed-5e79-47b2-9ff fc417ef</network_uuid> <ip_address> </ip_address> <port_uuid>c806c915-d5af-4269-bb6b-b76b66c720e1</port_uuid> <subnet_uuid>fd96c915-d5af-4269-bb6b-b76b66c720e1</subnet_uuid> <mac_address>fa:16:3e:01:ed:13</mac_address> </interface> </interfaces> <management_ip_address> </management_ip_address> <vm_name>sample-service-definition sample-tenant-01 dep-sample- 01 Group_0 sample_vm1 0</vm_name> </deployment_details> <external_deployment_id> f-a4e0-4d29-9ce2- ef90b94a65e8</external_deployment_id> <external_service_registration_id>2dee7003-8f9d-4a1c-b2ebf2de1d3daafb</external_service_registration_id> <external_tenant_id>4f384dfc667a4776bc3169da27d09db5</external_tenant_id> <internal_deployment_id>dep-sample-01</internal_deployment_id> <internal_service_registration_id>regsample</internal_service_registration_id> <internal_tenant_id>sample-tenant-01</internal_tenant_id> </deployment> </deployments> 55

Cisco Elastic Service Controller 1.1 REST API Guide

Cisco Elastic Service Controller 1.1 REST API Guide Cisco Elastic Service Controller 1.1 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 information

GET operations are synchronous the request/response parameters are described with an example of a request/response

GET 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 information

Cisco Elastic Service Controller 1.1 NETCONF API Guide

Cisco 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 information

Deploying Virtual Network Functions

Deploying 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 information

Cisco Elastic Service Controller 1.0 NETCONF API Guide

Cisco 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 information

Virtual Network Functions Life Cycle Management

Virtual 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 information

Virtual Network Functions Life Cycle Management

Virtual 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 information

API reference (Network)

API 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 information

VM Lifecycle Management APIs

VM 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 information

Cisco Elastic Service Controller 3.0 Netconf API Guide

Cisco 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 information

Healing Virtual Network Functions

Healing 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 information

The following sections below list the deployment scenarios and also list all the requirement XML files.

The 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 information

Multi-Tenant Accounting in OpenStack

Multi-Tenant Accounting in OpenStack Jorge L Williams Ziad N Sawalha Khaled Hussein Abstract As a cloud computing platform, OpenStack must support the concept

More information

The following sections below list the deployment scenarios and also list all the requirement XML files.

The 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 information

GR Installation - OpenStack

GR 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 information

Digital Imaging and Communications in Medicine (DICOM) Supplement 194: RESTful Services for Non-Patient Instances

Digital 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 information

Configuring Virtual Networks Using OpenStack

Configuring 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 information

Information About SIP Compliance with RFC 3261

Information 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 information

Virtual Infrastructure Manager Installation Automation

Virtual 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 information

VM Life Cycle Management

VM 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 information

API-based VNFM Upgrade Process

API-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 information

Compliance with RFC 3261

Compliance 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 information

ZN-DN312XE-M Quick User Guide

ZN-DN312XE-M Quick User Guide ZN-DN312XE-M Quick User Guide This manual provides instructions for quick installation and basic configuration of your IP device. Step1. Connect cables to IP device Connect required cables to the device

More information

Create a pfsense router for your private lab network template

Create 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 information

Virtual Private Cloud. User Guide. Issue 03 Date

Virtual 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 information

Tenant Onboarding. Tenant Onboarding Overview. Tenant Onboarding with Virtual Data Centers

Tenant 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 information

CIS-331 Spring 2016 Exam 1 Name: Total of 109 Points Version 1

CIS-331 Spring 2016 Exam 1 Name: Total of 109 Points Version 1 Version 1 Instructions Write your name on the exam paper. Write your name and version number on the top of the yellow paper. Answer Question 1 on the exam paper. Answer Questions 2-4 on the yellow paper.

More information

Monitoring Virtual Network Functions

Monitoring Virtual Network Functions Monitoring the VNFs, page 1 Monitoring Methods, page 7 Monitoring a VM, page 8 Monitoring Operations, page 9 Monitoring the VNFs After deploying VNFs, they are monitored periodically to check their health

More information

Mediant Cloud Edition (CE)

Mediant 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 information

Develop 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 - 2 Develop Mobile Front Ends Using Mobile Application Framework A - 3 Develop Mobile Front Ends Using Mobile Application Framework A - 4

More information

CIS-331 Final Exam Spring 2015 Total of 115 Points. Version 1

CIS-331 Final Exam Spring 2015 Total of 115 Points. Version 1 Version 1 1. (25 Points) Given that a frame is formatted as follows: And given that a datagram is formatted as follows: And given that a TCP segment is formatted as follows: Assuming no options are present

More information

Cisco Prime Service Catalog Virtual Appliance Quick Start Guide 2

Cisco 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 information

Using 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 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 information

IaaS Integration for Multi- Machine Services. vrealize Automation 6.2

IaaS 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 information

Please note: This is a working document and is subject to change. Please check back periodically to ensure you have the latest version of this spec.

Please note: This is a working document and is subject to change. Please check back periodically to ensure you have the latest version of this spec. Customs Declaration Service Full Declaration API v0.4 Document Version Please note: This is a working document and is subject to change. Please check back periodically to ensure you have the latest version

More information

CIS-331 Final Exam Spring 2018 Total of 120 Points. Version 1

CIS-331 Final Exam Spring 2018 Total of 120 Points. Version 1 Version 1 Instructions 1. Write your name and version number on the top of the yellow paper and the routing tables sheet. 2. Answer Question 2 on the routing tables sheet. 3. Answer Questions 1, 3, 4,

More information

CPM. Quick Start Guide V2.4.0

CPM. 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 information

Determine the DN of an Object Within the APIC GUI

Determine 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 information

Troubleshoot PCRF OAM VM Recovery- Openstack

Troubleshoot 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 information

Sequel SMRT Link Web Services API v4.0.0 Guide. Pacific Biosciences

Sequel 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 information

Service Portal User Guide

Service 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 information

REST Easy with Infrared360

REST 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 information

Internet Engineering Task Force (IETF) Obsoletes: 7302 September 2016 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Obsoletes: 7302 September 2016 Category: Informational ISSN: Internet Engineering Task Force (IETF) P. Lemieux Request for Comments: 7972 Sandflow Consulting LLC Obsoletes: 7302 September 2016 Category: Informational ISSN: 2070-1721 Entertainment Identifier Registry

More information

CIS-331 Exam 2 Fall 2014 Total of 105 Points. Version 1

CIS-331 Exam 2 Fall 2014 Total of 105 Points. Version 1 Version 1 1. (20 Points) Given the class A network address 119.0.0.0 will be divided into a maximum of 15,900 subnets. a. (5 Points) How many bits will be necessary to address the 15,900 subnets? b. (5

More information

Introduction to Cisco TV CDS Software APIs

Introduction 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 information

CIS-331 Fall 2014 Exam 1 Name: Total of 109 Points Version 1

CIS-331 Fall 2014 Exam 1 Name: Total of 109 Points Version 1 Version 1 1. (24 Points) Show the routing tables for routers A, B, C, and D. Make sure you account for traffic to the Internet. Router A Router B Router C Router D Network Next Hop Next Hop Next Hop Next

More information

ReST 2000 Roy Fielding W3C

ReST 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 information

Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim Wort. This paper assumes the installation and system configuration are complete.

Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim Wort. This paper assumes the installation and system configuration are complete. Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim Wort This paper is a cookbook for configuring the Oracle Solaris 11.2 OpenStack Unified Archive. The Solaris 11.2 OpenStack Unified Archive is no

More information

Simple Object Access Protocol (SOAP) Reference: 1. Web Services, Gustavo Alonso et. al., Springer

Simple Object Access Protocol (SOAP) Reference: 1. Web Services, Gustavo Alonso et. al., Springer Simple Object Access Protocol (SOAP) Reference: 1. Web Services, Gustavo Alonso et. al., Springer Minimal List Common Syntax is provided by XML To allow remote sites to interact with each other: 1. A common

More information

What s New with VMware vcloud Director 8.0

What 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 information

Post Installation Tasks

Post 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 information

IPv6 in Avi Vantage for OpenStack

IPv6 in Avi Vantage for OpenStack Page 1 of 11 view online Overview Starting with release 18.1.1, OpenStack integration with Avi Vantage is IPv6 capable. The integration discussed in this article has been tested for OpenStack Ocata which

More information

Understanding RESTful APIs and documenting them with Swagger. Presented by: Tanya Perelmuter Date: 06/18/2018

Understanding RESTful APIs and documenting them with Swagger. Presented by: Tanya Perelmuter Date: 06/18/2018 Understanding RESTful APIs and documenting them with Swagger Presented by: Tanya Perelmuter Date: 06/18/2018 1 Part 1 Understanding RESTful APIs API types and definitions REST architecture and RESTful

More information

vcloud Director User's Guide 04 OCT 2018 vcloud Director 9.5

vcloud 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 information

CIS-331 Exam 2 Fall 2015 Total of 105 Points Version 1

CIS-331 Exam 2 Fall 2015 Total of 105 Points Version 1 Version 1 1. (20 Points) Given the class A network address 117.0.0.0 will be divided into multiple subnets. a. (5 Points) How many bits will be necessary to address 4,000 subnets? b. (5 Points) What is

More information

ZENworks for Desktops Preboot Services

ZENworks 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 information

4. Specifications and Additional Information

4. Specifications and Additional Information 4. Specifications and Additional Information AGX52004-1.0 8B/10B Code This section provides information about the data and control codes for Arria GX devices. Code Notation The 8B/10B data and control

More information

Libelium Cloud Hive. Technical Guide

Libelium 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 information

CONFIGURING WEBAPP SECURE TO PROTECT AGAINST CREDENTIAL ATTACKS

CONFIGURING WEBAPP SECURE TO PROTECT AGAINST CREDENTIAL ATTACKS APPLICATION NOTE CONFIGURING WEBAPP SECURE TO PROTECT AGAINST CREDENTIAL ATTACKS Protect your Web Applications from Brute Force Credential Attacks Using WebApp Secure and Intrusion Deception Technology

More information

Post Installation Tasks

Post 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 information

Cisco ACI Terminology ACI Terminology 2

Cisco ACI Terminology ACI Terminology 2 inology ACI Terminology 2 Revised: May 24, 2018, ACI Terminology Cisco ACI Term Alias API Inspector App Center Application Policy Infrastructure Controller (APIC) Application Profile Atomic Counters Alias

More information

NDEV Mobile HTTP Services for NDEV Mobile Clients

NDEV 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 information

CIS-331 Fall 2013 Exam 1 Name: Total of 120 Points Version 1

CIS-331 Fall 2013 Exam 1 Name: Total of 120 Points Version 1 Version 1 1. (24 Points) Show the routing tables for routers A, B, C, and D. Make sure you account for traffic to the Internet. NOTE: Router E should only be used for Internet traffic. Router A Router

More information

Session 8. Reading and Reference. en.wikipedia.org/wiki/list_of_http_headers. en.wikipedia.org/wiki/http_status_codes

Session 8. Reading and Reference. en.wikipedia.org/wiki/list_of_http_headers. en.wikipedia.org/wiki/http_status_codes Session 8 Deployment Descriptor 1 Reading Reading and Reference en.wikipedia.org/wiki/http Reference http headers en.wikipedia.org/wiki/list_of_http_headers http status codes en.wikipedia.org/wiki/_status_codes

More information

Ver Enterprise Cloud. User s Guide for. API Function. ver1.03

Ver 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 information

RESTful Services. Distributed Enabling Platform

RESTful Services. Distributed Enabling Platform RESTful Services 1 https://dev.twitter.com/docs/api 2 http://developer.linkedin.com/apis 3 http://docs.aws.amazon.com/amazons3/latest/api/apirest.html 4 Web Architectural Components 1. Identification:

More information

Installing the Cisco Nexus 1000V Software Using ISO or OVA Files

Installing the Cisco Nexus 1000V Software Using ISO or OVA Files Installing the Cisco Nexus 1000V Software Using ISO or OVA Files This chapter contains the following sections: Installing the VSM Software, page 1 Installing the VSM Software Installing the Software from

More information

2 Apache Wink Building Blocks

2 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 information

IaaS Integration for Multi-Machine Services

IaaS 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 information

RESTful Network API for Notification Channel

RESTful Network API for Notification Channel RESTful Network API for Notification Channel Candidate Version 1.0 17 Jan 2012 Open Mobile Alliance OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20120117-C OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20120117-C

More information

API-based AutoDeploy, AutoIT and AutoVNF Upgrade Process

API-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 information

Cisco CCIE Data Center Written Exam v2.0. Version Demo

Cisco CCIE Data Center Written Exam v2.0. Version Demo Cisco 400-151 CCIE Data Center Written Exam v2.0 Version Demo QUESTION 1 Which IETF standard is the most efficient messaging protocol used in an lot network? A. SNMP B. HTTP C. CoAP D. MQTI Correct Answer:

More information

SOA Software API Gateway Appliance 6.3 Administration Guide

SOA Software API Gateway Appliance 6.3 Administration Guide SOA Software API Gateway Appliance 6.3 Administration Guide Trademarks SOA Software and the SOA Software logo are either trademarks or registered trademarks of SOA Software, Inc. Other product names, logos,

More information

REST Web Services Objektumorientált szoftvertervezés Object-oriented software design

REST 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 information

CIS-331 Final Exam Spring 2016 Total of 120 Points. Version 1

CIS-331 Final Exam Spring 2016 Total of 120 Points. Version 1 Version 1 1. (25 Points) Given that a frame is formatted as follows: And given that a datagram is formatted as follows: And given that a TCP segment is formatted as follows: Assuming no options are present

More information

Deploying the Cisco ASA 1000V

Deploying 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 information

OVERVIEW OF ETSI M2M RELEASE 1 STAGE 3 API AND RESOURCE USAGE

OVERVIEW OF ETSI M2M RELEASE 1 STAGE 3 API AND RESOURCE USAGE OVERVIEW OF ETSI M2M RELEASE 1 STAGE 3 API AND RESOURCE USAGE Presented by Guang Lu, WG3 Rapporteur, InterDigital Outline TS 102 921 overview ETSI M2M reference points ETSI M2M resource tree ETSI M2M API

More information

Infoblox Installation Guide. vnios for Microsoft Azure

Infoblox Installation Guide. vnios for Microsoft Azure Infoblox Installation Guide vnios for Microsoft Azure Copyright Statements 2017, Infoblox Inc. All rights reserved. The contents of this document may not be copied or duplicated in any form, in whole or

More information

Layer-4 to Layer-7 Services

Layer-4 to Layer-7 Services Overview, page 1 Tenant Edge-Firewall, page 1 LBaaS, page 2 FWaaS, page 4 Firewall Configuration, page 6 Overview Layer-4 through Layer-7 services support(s) end-to-end communication between a source and

More information

Apache Wink Developer Guide. Draft Version. (This document is still under construction)

Apache 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 information

Cisco 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.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 information

Configuring Hyper-V Network Virtualization

Configuring Hyper-V Network Virtualization This chapter contains the following sections: Prerequisites for HNV, page 1 Default Settings for HNV, page 2 Steps for Creating an HNV Network, page 2 Configuring NSM for HNV on the VSM, page 3 Creating

More information

Cisco ACI Simulator VM Installation Guide

Cisco 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 information

Cisco Meeting Server. Cisco Meeting Server Release 2.0+ Multi-tenancy considerations. December 20, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.0+ Multi-tenancy considerations. December 20, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.0+ Multi-tenancy considerations December 20, 2017 Cisco Systems, Inc. www.cisco.com Contents Change History 3 1 Introduction 4 1.1 How to use this Document

More information

OpenStack Havana On IPv6

OpenStack Havana On IPv6 OpenStack Havana On IPv6 Shixiong Shang Randy Tuttle Ciprian Popoviciu! Version 1.9.3 Agenda Introduction IPv6 and Cloud IPv6 Refreshment Proof of Concept Proposed Blueprint Next Steps 2 Introduction Nephos6!

More information

Open Archives Initiative Object Reuse & Exchange. Resource Map Discovery

Open 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 information

Introduction to RESTful Web Services. Presented by Steve Ives

Introduction 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 information

[MS-OAUTH2EX]: OAuth 2.0 Authentication Protocol Extensions. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-OAUTH2EX]: OAuth 2.0 Authentication Protocol Extensions. Intellectual Property Rights Notice for Open Specifications Documentation [MS-OAUTH2EX]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,

More information

04 Webservices. Web APIs REST Coulouris. Roy Fielding, Aphrodite, chp.9. Chp 5/6

04 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 information

Services and Networking

Services 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 information

API Reference for Cisco Enterprise Network Function Virtualization Infrastructure Software

API Reference for Cisco Enterprise Network Function Virtualization Infrastructure Software API Reference for Cisco Enterprise Network Function Virtualization Infrastructure Software First Published: 2017-03-31 Last Modified: 2018-04-20 Americas Headquarters Cisco Systems, Inc. 170 West Tasman

More information

Cisco Nexus 1000V for KVM OpenStack REST API Configuration Guide, Release 5.x

Cisco Nexus 1000V for KVM OpenStack REST API Configuration Guide, Release 5.x Cisco Nexus 1000V for KVM OpenStack REST API Configuration Guide, Release 5.x First Published: August 01, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA

More information

LB Cache Quick Start Guide v1.0

LB 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 information

Request for Comments: 5437 Category: Standards Track Isode Limited January 2009

Request for Comments: 5437 Category: Standards Track Isode Limited January 2009 Network Working Group Request for Comments: 5437 Category: Standards Track P. Saint-Andre Cisco A. Melnikov Isode Limited January 2009 Status of This Memo Sieve Notification Mechanism: Extensible Messaging

More information

CIS-331 Exam 2 Spring 2016 Total of 110 Points Version 1

CIS-331 Exam 2 Spring 2016 Total of 110 Points Version 1 Version 1 1. (20 Points) Given the class A network address 121.0.0.0 will be divided into multiple subnets. a. (5 Points) How many bits will be necessary to address 8,100 subnets? b. (5 Points) What is

More information

Networking-vpp: An OpenStack ml2 driver for VPP Jerome Tollet / Ian Wells FD.io Program July 6 th, fd.io FoundaBon 1

Networking-vpp: An OpenStack ml2 driver for VPP Jerome Tollet / Ian Wells FD.io Program July 6 th, fd.io FoundaBon 1 Networking-vpp: An OpenStack ml2 driver for VPP Jerome Tollet / Ian Wells FD.io Program July 6 th, 2017 fd.io FoundaBon 1 Agenda What is networking-vpp? Design principles Overall architecture Current feature

More information

Getting Familiar with the API Data Types

Getting Familiar with the API Data Types CHAPTER 4 This module describes the various API data types used in the SCMS SCE Subscriber API. Subscriber ID, page 4-1 Information About Network ID Mappings, page 4-2 Information About SCA BB Subscriber

More information

Cisco VDS Service Broker Software Installation Guide for UCS Platforms

Cisco VDS Service Broker Software Installation Guide for UCS Platforms Cisco VDS Service Broker 1.0.1 Software Installation Guide for UCS Platforms Revised: May 2013 This document provides detailed instructions for installing the Cisco Videoscape Distribution Suite Service

More information

Cisco UCS Director REST API Cookbook

Cisco UCS Director REST API Cookbook Cisco UCS Director REST API Cookbook Release 1.0 Published: April, 2015 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed

More information

Developing RESTful Services Using JAX-RS

Developing RESTful Services Using JAX-RS Developing RESTful Services Using JAX-RS Bibhas Bhattacharya CTO, Web Age Solutions Inc. April 2012. Many Flavors of Services Web Services come in all shapes and sizes XML-based services (SOAP, XML-RPC,

More information