Exposed interfaces Sample Clauses

Exposed interfaces. The RO module exposes a GENIv3 [9] compliant interface which can be used by the user applications (e.g. the XXXXX-GUI) to allocate, configure, describe or release resources into the federated test-bed. It also provides a custom API used for configuration purposes. GENIv3 API Each incoming GENIv3 request is received by the GENIv3 Handler and then forwarded to the GENIv3 Dele- gate. This component performs all the authentication and authorization checks and then validates the received RSpec with a proper schema. Depending on the input parameters, the delegate chooses the correct plug-in (or plug-ins) that should serve the request and translates the context to be executed into the underlying layer. In addition, the delegate can store data into the Resource DB simply calling a dedicated DB Manager object which can be considered as a DB abstraction layer. We have several plug-ins to interact with different Resource Managers. Basically, there is a 1:1 mapping between the RM and the corresponding plug-in. This mechanism allows us to isolate the specific RM management logic inside the plug-in and to offer a common and generalized interface to the upper layer. The methods offered by this API are as follows: • GetVersion: return basic information of the RO, such as the format of the supported RSpecs. • ListResources: retrieve description of the available resources that are managed by the RO.
Sample 1
AutoNDA by SimpleDocs
Exposed interfaces. The SDN-RM inherits its base from the XXXXXX OFAM, which exposes the GENIv2 interface. Now, as any other XXXXX Resource Managers, this module also offers the GENIv3 API; which enables a programmatic, abstracted and standardized use of any resource in the testbed. This -as the previous standard interfaces- were designed initially by SFA and have been since revisited, standardized and widely adopted by other infrastructures. The main benefit of using such interfaces is to allow easier federation between testbeds; that is, the sharing of resources of different kinds and offered by different providers; but also serve for exposing a standard interface that can help automation and abstraction when it comes to reserve, provision or scheduler resources. GENIv2 API The GENIv2 API is the previously accepted interface and is still supported nowadays by several infrastructures. Through a simple workflow, the more important methods and their functionality can be observed: • GetVersion: learn basic information about the SDN-RM, such as the format of the supported RSpecs. • ListResources: retrieve description of the topology (switches and their interconnections). • CreateSliver: provision and initialize a set of datapath IDs and conditions (called FlowSpace), according to an RSpec. • SliverStatus: check status of the FlowSpace (sliver). • RenewSliver: extend expiration time for the FlowSpace. • DeleteSliver: when done, delete the FlowSpace. GENIv3 API This is the latest interface adopted by the GENI and other testbeds community. Compared to the previous interface, this allows new operations such as the Allocation (a reservation, prior to the effective provisioning of the resource), or the PerformOperationalAction that allows extending operations on a resource to include any extra functionality. The main methods are as follow: • GetVersion: learn basic information about the SDN-RM, such as the format of the supported RSpecs. • ListResources: retrieve description of the topology (switches and their interconnections). • Allocate: request reservation of a subset of resources (VMs), according to an RSpec. In contrast with C-RM, this is not incremental: a new allocation does not extend previous reservations. • Provision: effectively provision and get ownership of a subset of previously allocated FlowSpaces. • Status: check status of the reservation or the FlowSpace.
Sample 1
Exposed interfaces. As documented in the Building blocks section, the MS exposes 2 APIs to other modules. The structure of the URIs is previously agreed and know between the participant modules in the communication. The detailed structure of the URIs is shown in Figure 3.2.
Sample 1

Related to Exposed interfaces

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Integrated Digital Loop Carriers The feeder portion of some loops may be provide by means of Integrated Digital Loop Carrier (IDLC). IDLC provides a fiber optic cable transmission path that travels directly into BellSouth’s central office local switch. Where BellSouth uses IDLC ,if technically feasible and capacity does exist, BST will provide Al-Call with a Designed DS0 UVL by using alternative provisioning techniques including but not limited to such as “hairpinning” and DAC grooming. Alternative provisioning techniques will be provided at no additional cost to Al-Call . Hairpinning involves providing a DS0 signal from an IDLC-served loop to Al-Call ’s collocation equipment by using a dedicated pathway that traverses BellSouth’s central office switch. BellSouth will provide such DS0 signal to Al-Call by establishing a copper cross connect between the BellSouth switch and Al-Call ’s collocation equipment.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • ROAD TOLERANCES Purchaser shall perform road work within the tolerances listed below. The tolerance class for each road is listed on the TYPICAL SECTION SHEET. Tolerance Class A B C Road and Subgrade Width (feet) +1.5 +1.5 +2.0 Subgrade Elevation (feet +/-) 0.5 1.0 2.0 Centerline alignment (feet lt./rt.) 1.0 1.5 3.0 1-6 ORDER OF PRECEDENCE Any conflict or inconsistency in the road plan will be resolved by giving the documents precedence in the following order:

Time is Money Join Law Insider Premium to draft better contracts faster.