REST APIs Sample Clauses

REST APIs. Table 2 – List of APIs for provisioning of overlay virtual networks Operation URI Description List networks List networks Lists networks to which the specified tenant has access. Create network Create network Creates a network. Bulk create networks Bulk create networks Creates multiple networks in a single request. Show network Show network Shows information for a specified network. Update network Update network Updates a specified network. Delete network Delete network Deletes a specified network and its associated resources. Table 3 – List networks specification List networks Request parameters tenant_id UUID The tenant ID admin_state_up bool The administrative state of the network, which is up (true) or down (false) Id uuid The network ID Response Name string The network name parameters Shared bool Indicates whether this network is shared across all tenants. By default, only administrative users can change this value Status string The network status. Subnets dictionary The associated subnets Successful response codes: 200 Error response codes: unauthorized (401) Table 4 – Create network specification Create network Request parameters admin_state_up (optional) bool The administrative state of the network, which is up (true) or down (false). name (Optional) string The network name. A request body is optional: If you include it, it can specify this optional attribute. shared (Optional) bool Indicates whether this network is shared across all tenants. By default, only administrative users can change this value. tenant_id (Optional) uuid Admin-only. The UUID of the tenant that will own the network. This tenant can be different from the tenant that makes the create network request. However, only administrative users can specify a tenant ID other than their own. You cannot change this value through authorization policies. router:external (Optional) bool Indicates whether this network is externally accessible. Response parameters admin_state_up bool The administrative state of the network, which is up (true) or down (false). Id uuid The network ID. name string The network name. shared bool Indicates whether this network is shared across all tenants. By default, only administrative users can change this value. Status string The network status. subnets Dictionary The associated subnets. tenant_id UUID The tenant ID Successful response codes: 201 Error response codes: badRequest (400), unauthorized (401) Table 5 – Bulk create networks specification Bulk create net...
Sample 1
AutoNDA by SimpleDocs
REST APIs. Table 9 – List of APIs for provisioning of virtual optical slices Operation URI Description POST POST/restconf/config/virtual- infrastructure-manager:slice Creates a new virtual optical slice. GET GET/restconf/config/virtual- infrastructure- manager:slice/<TenantID>/<SliceID> Shows the information associated to the virtual optical slice. GET GET/restconf/config/virtual- infrastructure- manager:slice/<TenantID> Shows the information associated to the virtual optical slices owned by a given tenant PUT PUT/restconf/config/virtual- infrastructure- manager:slice/<TenantID>/<SliceID> Updates or modifies the configuration of the specified virtual optical slice. DELETE DELETE/restconf/config/virtual- infrastructure- manager:slice/<TenantID>/<SliceID> Removes the virtual optical slice and releases the occupied resources. Table 10 – Create virtual optical slice specification POST/restconf/config/virtual-infrastructure-manager:slice Request parameters TenantID integer Identifier of the tenant EndPoints List<Node> List of the nodes that need to be included in the slice QoS QoS object List of the parameters that set the QoS requested for the optical slice MonitoringInfo (optional) Monitoring object Object that contains the parameters that need to be monitored in the optical slice Time (optional) Time object Parameters to set the start time and the duration of the optical slice Response parameters SliceID integer Identifier given to the slice created Topology Topology object Object that contains the topology of the created optical slice (i.e. list of nodes and links) Status enum Current status of the optical slice Successful response codes: 201 CREATED Error response codes: 400 BAD REQUEST, 403 FORBIDDEN 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE Table 11 – Show virtual optical slice specification GET/restconf/config/virtual-infrastructure-manager:slice/<TenantID>/<SliceID> Request parameters TenantID Integer Identifier of the tenant of the slice SliceID Integer Identifier of the slice Response parameters Topology Topology object Object that contains the topology of the optical slice (i.e. list of nodes and links) identified by SliceID QoS QoS object List of the parameters that set the QoS requested for the optical slice identified by XxxxxXX MonitoringInfo (optional) Monitoring object Object that contains the parameters that need to be monitored in the optical slice identified by SliceID Time (optional) Time object Parameters to set the start time and the durat...
Sample 1
REST APIs. Table 15 – List of APIs for provisioning of optical connectivity Operation URI Description POST /restconf/config/optical- provisioning-manager:connection Creates a new optical connection PUT /restconf/config/optical- provisioning- manager:connection/connectionID Modifies some parameters of an established optical connection with identifier “connectionID” GET /restconf/config/optical- provisioning- Retrieves the details of an established optical manager:connection/connectionID connection with identifier “connectionID” GET /restconf/config/optical- provisioning- manager:connections Lists all the established optical connections DELETE /restconf/config/optical- provisioning- manager:connection/connectionID Tears-down and removes the optical connection with identifier “connectionID” Table 16 – POST /restconf/config/optical-provisioning-manager:connection specification POST /restconf/config/optical-provisioning-manager:connection connection_type enum The type of the connection. The following options are available: point-to-point: point-to-multipoint: anycast: src_endpoint_type enum The type of the source endpoint (e.g., an IP address) src_endpoint string Source end point for the optical connection dst_endpoint_type enum The type of the destination endpoint (e.g., an IP address) Request parameters dst_endpoint list<string> Destination end point for the optical connection. It is a single value for point-to-point connections and a list of values for point-to- multipoint and anycast connections. In the first case the connection is established between the source and all the destination endpoints, while for anycast connections a single destination is chosen from the pool. bidirectional boolean Indicates if the connection service is bidirectional recovery (optional) enum The recovery strategy to be adopted for the optical connection. The following options are available: Unprotected: in case of failures, the control plane does not apply any countermeasure. Protected: during the setup phase the control plane establishes an additional, possibly disjoint, connection where the traffic is transferred in case of failure on the primary path. Restoration: when the control plane detects a failure in a connection, it tries to establish dynamically a new working path. qos_parameters qos object Specification of the desired QoS. It includes the following optional elements: minimum_reserved_bw, max_bw, max_delay, packet_loss, class_of_service time_constraints (optional) time constrain...
Sample 1
REST APIs. Table 29 – List of APIs for the DCN information service Operation URI Description GET /restconf/config/opendaylight- inventory:nodes Retrieve all the nodes available in the network, each of them with the list of its ports. POST /restconf/operations/opendaylight- port-statistics:get-all-node- connectors-statistics Retrieve statistics about all the ports in a node POST /restconf/operations/opendaylight- port-statistics:get-node-connector- statistics Retrieve statistics about a given port in a node POST /restconf/operations/opendaylight- flow-statistics:get-all-flows- Retrieve statistics about all the flows in a node statistics-from-all-flow-tables POST /restconf/operations/opendaylight- flow-statistics:get-flow-statistics Retrieve statistics about a given flow in a node POST /restconf/operations/opendaylight- flow-table-statistics:get-flow- tables-statistics Retrieve statistics about all the tables in a node POST /restconf/operations/opendaylight- queue-statistics:get-all-queues- statistics-from-given-port Retrieve statistics about all the queues in a port Table 30 – GET /restconf/config/opendaylight-inventory:nodes specification GET /restconf/config/opendaylight-inventory:nodes Request parameters -- -- -- Response parameters Nodes List<Node object> The description of the nodes, including their NodeId and their ports. Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE Table 31 – POST /restconf/operations/opendaylight-port-statistics:get-all-node-connectors-statistics specification POST /restconf/operations/opendaylight-port-statistics:get-all-node-connectors-statistics Request parameters NodeId String The unique identifier of the node. Response parameters Ports List<Port object> The list of the ports. Each Port object includes the Port Id, the Port Type and the PortStats, as defined in the information model above. Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE Table 32 – POST /restconf/operations/opendaylight-port-statistics:get-node-connector-statistics specification POST /restconf/operations/opendaylight-port-statistics:get-node-connector-statistics Request parameters NodeId String The unique identifier of the node. PortId String The unique identifier of the port. Response parameters PortType Enum Type of the port: optical or eth. PortStatistics PortStats object Port...
Sample 1
REST APIs. Table 21 – List of APIs for CRUD operations on forwarding rules Operation URI Description POST /restconf/config/forwarding-rules- manager/connectionID Creates a new forwarding rules for optical "connection ID" over specific end points PUT /restconf/config/forwarding-rules- manager/connectionID Modifies all the forwarding rules for an established optical connection with identifier “connectionID” PUT /restconf/config/forwarding-rules- manager/connectionID/forwarding- rule-ID Modifies the forwarding rules with identifier "forwarding-rule-ID" for an established optical connection with identifier “connectionID” GET /restconf/config/forwarding-rules- Retrieves all the forwarding rules which manager/connectionID identify client flows mapped over an established optical connection with identifier “connectionID” GET /restconf/config/forwarding-rules- manager/connectionID/forwarding- rule-ID Retrieves a specific forwarding rule with identifier “forwarding-rule-ID” mapped over an established optical connection with identifier “connectionID” DELETE /restconf/config/forwarding-rules- manager/connectionID Removes all the forwarding rules associated to client flows mapped over an optical circuit with identifier “connectionID” DELETE /restconf/config/forwarding-rules- manager/connectionID/forwarding- rule-ID Removes a specific forwarding rule with identifier “forwarding-rule-ID” mapped over an established optical connection with identifier “connectionID” Table 22 – POST /restconf/config/forwarding-rules-manager/connectionID POST /restconf/config/forwarding-rules-manager/connectionID Request parameters connection_id string The unique identifier of the created connection of_classification string The requested Open-Flow classification of the flows over the connection ID Response parameters Forwarding_rule_id string The unique identifier of the created forwarding rule. Status enum Current status of the client flow Successful response codes: 201 CREATED Error response codes: 400 BAD REQUEST, 403 FORBIDDEN 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE Table 23 – PUT /restconf/config/forwarding-rules-manager /connectionID PUT /restconf/config/forwarding-rules-manager/connectionID Request parameters of_classification string The requested Open-Flow classification of the flows over the connection ID Response parameters status enum Current status of the flow modifications Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND, 405 M...
Sample 1

Related to REST APIs

  • DEVELOPMENT CHARGES The Owner agrees to pay development charges with respect to the development in accordance with the Municipality's Development Charges By-Law.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its Reliability Planning Process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Short-Term Reliability Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the STAR or Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Short-Term Reliability Process Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!