Correct internal behaviour per method Sample Clauses

Correct internal behaviour per method. In this paragraph, we summarise the internal workflow per method from an high-level point of view. It is impor- tant to note that the (M)RO has a strong relationship with the other components in terms of the exchanged mes- sages. All these messages are printed in the log-file of the process (i.e. modules/resource/orchestrator/log/resource- orchestrator.log) in a pretty XML format. In the GetVersion method, the (M)RO fills the XML-RPC structure with the proper values. In the ListResources method, the (M)RO first verifies the user credentials and then reads from the MongoDB [8] database the information on the nodes and links for the C, SDN, SE and TN resources. At the end, the adver- tisement RSpec is composed and returned to the client. In the Describe method, the (M)RO verifies the user credentials and retrieves the information of the slice composition from the database. Then, it sends the describe command to each involved RMs or ROs. When the responses are correctly received, it creates the manifest RSpec and the list of slivers merging the output of the corresponding message. This information is then returned to the client. The Renew, Status and PerformOperationalAction methods are quite similar and we use the same template for the implementation. In these methods, the (M)RO starts verifying the user credentials and reading the slice composition from the database. AGer that, it sends the proper command (i.e. Renew, Status or PerformOpera- tionalAction) and, when it receives the responses, only the list of slivers is produced and returned to the caller. The Allocate method is the most complex implementation we currently have in the code. AGer the verification of the user credentials and the validation of the incoming request RSpec, the (M)RO tries to extend the request adding the Stitching Entity information. Here, we use a dedicated pathFinder module that simply lookup the database in order to fetch the missing resources description. When the request is completely reformatted, the (M)RO analyses the schema extracting the C, SDN, SE, TN sections. Each section is then introduced in the allocate command to the proper RM or RO. At the end, the (M)RO composes the manifest RSpec as sum of the received responses and fills the list of slivers structure. The Provision and Delete methods are also used to update the Monitoring System with the information related to the slice. As usual, the user credentials are verified and the slice composition retrieved from the database. ...
Sample 1
AutoNDA by SimpleDocs
Correct internal behaviour per method. We have massively used the log file to validate the correct behaviour per each method of the interface. Using the OMNI tool, each method of the API was called and the log file deeply analysed. In case of errors, the problem was reported to the development team. In order to facilitate this procedure, the colorlog module has been introduced, producing different colours for the different levels, e.g green for debug, blue for info, red for error, etc. Moreover, we have added the timestamps and a proper handler for the dumping of the messages. As result, we have no errors in the normal test conditions.
Sample 1
Correct internal behaviour per method. The second item seeks to verify the correctness of the internal workflow of requests. That is done by testing incoming requests that arrive to the manager and traverse all way down until arriving at the driver. It also takes into account the returned information coming from the manager and going down to the driver. For that matter, tests have been automated to ensure a proper internal workflow. Unit tests for the involved methods can be found in the XXXXX repository, located under the corresponding folder [10] within the ocf branch. Looking into detail, the unit tests in CRM look for a proper behaviour/output on the following: • Management of unique identifiers (URN, HRN) for resources: ensure correct retrieval of the identifiers, appropriate parsing of authority, slice and sliver entities, and correct translation of URNs into HRNs and vice-versa. • Management of reservations: validate that reservations are assigned the default expiration time (1 hour) and ensure proper type handling during the management of the projects and slices. • Advertising resources: return (un)available servers, return slivers per slice, etc. • Management of slivers: correctly starting, stopping, rebooting, deleting and renewing resources. • Internal management: ensure credentials are verified correctly, handlers are set up as expected, and re- source specifications are accurately translated into an internal representation (model) used within internal components. The previous tests cover pretty much the full experimenter life cycle, yet further manual tests have been performed during the integration phase with the Resource Orchestrator (RO). These manual tests have been carried out both manually (using a third-party client, such as jFed or OMNI) and also by using the RO to proxy requests to its managed RMs.
Sample 1
Correct internal behaviour per method. During the tests the log file had been used to validate the correct behaviour per each method of the interface. Using the OMNI tool, each method of the API was called and the log file deeply analysed. In case of errors, the problem was fixed by the SERM developers. The correctness of the VLAN translation rules installation on the switching device had been confirmed by using the Ryu REST API and the method that displays all the OpenFlow rules. In first phase of the tests the soGware Open VSwitch has been used as a Stitching Entity. In the next phase the proper VLAN translations on the Juniper MX80 with the OpenFlow support was also tested. As result, no errors in the normal test conditions occurred.
Sample 1

Related to Correct internal behaviour per method

  • DISADVANTAGED BUSINESS ENTERPRISE OR HISTORICALLY UNDERUTILIZED BUSINESS REQUIREMENTS The Engineer agrees to comply with the requirements set forth in Attachment H, Disadvantaged Business Enterprise or Historically Underutilized Business Subcontracting Plan Requirements with an assigned goal or a zero goal, as determined by the State.

  • Reasonable Suspicion Testing The Employer may, but does not have a legal duty to, request or require an employee to undergo drug and alcohol testing if the Employer or any supervisor of the employee has a reasonable suspicion (a belief based on specific facts and rational inferences drawn from those facts) related to the performance of the job that the employee:

  • FLORIDA CONVICTED/SUSPENDED/DISCRIMINATORY COMPLAINTS By submission of an offer, the respondent affirms that it is not currently listed in the Florida Department of Management Services Convicted/Suspended/Discriminatory Complaint Vendor List.

  • Convicted, Discriminatory, Antitrust Violator, and Suspended Vendor Lists In accordance with sections 287.133, 287.134, and 287.137, F.S., the Contractor is hereby informed of the provisions of sections 287.133(2)(a), 287.134(2)(a), and 287.137(2)(a), F.S. For purposes of this Contract, a person or affiliate who is on the Convicted Vendor List, the Discriminatory Vendor List, or the Antitrust Violator Vendor List may not perform work as a contractor, supplier, subcontractor, or consultant under the Contract. The Contractor must notify the Department if it or any of its suppliers, subcontractors, or consultants have been placed on the Convicted Vendor List, the Discriminatory Vendor List, or the Antitrust Violator Vendor List during the term of the Contract. In accordance with section 287.1351, F.S., a vendor placed on the Suspended Vendor List may not enter into or renew a contract to provide any goods or services to an agency after its placement on the Suspended Vendor List. A firm or individual placed on the Suspended Vendor List pursuant to section 287.1351, F.S., the Convicted Vendor List pursuant to section 287.133, F.S., the Antitrust Violator Vendor List pursuant to section 287.137, F.S., or the Discriminatory Vendor List pursuant to section 287.134, F.S., is immediately disqualified from Contract eligibility.

  • BUSINESS CONTINUITY/DISASTER RECOVERY In the event of equipment failure, work stoppage, governmental action, communication disruption or other impossibility of performance beyond State Street’s control, State Street shall take reasonable steps to minimize service interruptions. Specifically, State Street shall implement reasonable procedures to prevent the loss of data and to recover from service interruptions caused by equipment failure or other circumstances with resumption of all substantial elements of services in a timeframe sufficient to meet business requirements. State Street shall enter into and shall maintain in effect at all times during the term of this Agreement with appropriate parties one or more agreements making reasonable provision for (i) periodic back-up of the computer files and data with respect to the Trusts; and (ii) emergency use of electronic data processing equipment to provide services under this Agreement. State Street shall test the ability to recover to alternate data processing equipment in accordance with State Street program standards, and provide a high level summary of business continuity test results to the Trusts upon request. State Street will remedy any material deficiencies in accordance with State Street program standards. Upon reasonable advance notice, and at no cost to State Street, the Trusts retain the right to review State Street’s business continuity, crisis management, disaster recovery, and third-party vendor management processes and programs (including discussions with the relevant subject matter experts and an on-site review of the production facilities used) related to delivery of the service no more frequently than an annual basis. Upon reasonable request, the State Street also shall discuss with senior management of the Trusts any business continuity/disaster recovery plan of the State Street and/or provide a high-level presentation summarizing such plan.”

  • Historically Underutilized Businesses (“HUBs”). In accordance with state law, it is TFC’s policy to assist HUBs whenever possible to participate in providing goods and services to the agency. TFC encourages those parties with whom it contracts for the provision of goods and services to adhere to this same philosophy in selecting subcontractors to assist in fulfilling PSP’s obligations with TFC. If PSP subcontracts with others for some or all of the services to be performed under an Assignment to this Agreement, PSP shall comply with all HUB requirements pursuant to Chapter 2161 of the Texas Government Code. At or prior to the execution of an Assignment with a value that is anticipated to meet or exceed One Hundred Thousand and No/100 Dollars ($100,000.00), PSP must provide a completed HUB Subcontracting Plan, which shall be approved by TFC prior to execution of the Assignment. A copy of the HUB Subcontracting Form is attached hereto and incorporated herein for all purposes as Exhibit G. PSP shall provide the HUB Program of TFC with pertinent details of any participation by a HUB in fulfilling the duties and obligations arising under an Assignment, on the HUB Subcontracting Plan Progress Assessment Report (“PAR”). A copy of the PAR Form is attached hereto and incorporated herein for all purposes as Exhibit H.

  • Discriminatory Vendors An entity or affiliate who has been placed on the discriminatory vendor list may not submit a bid, proposal, or reply on a contract to provide any goods or services to a public entity; may not submit a bid, proposal, or reply on a contract with a public entity for the construction or repair of a public building or public work; may not submit bids, proposals, or replies on leases of real property to a public entity; may not be awarded or perform work as a contractor, supplier, subcontractor, or consultant under a contract with any public entity; and may not transact business with any public entity.

  • CFR PART 200 Procurement of Recovered Materials A non-Federal entity that is a state agency or agency of a political subdivision of a state and its contractors must comply with section 6002 of the Solid Waste Disposal Act, as amended by the Resource Conservation and Recovery Act. The requirements of Section 6002 include procuring only items designated in guidelines of the Environmental Protection Agency (EPA) at 40 CFR part 247 that contain the highest percentage of recovered materials practicable, consistent with maintaining a satisfactory level of competition, where the purchase price of the item exceeds $10,000 or the value of the quantity acquired during the preceding fiscal year exceeded $10,000; procuring solid waste management services in a manner that maximizes energy and resource recovery; and establishing an affirmative procurement program for procurement of recovered materials identified in the EPA guidelines. Does vendor certify that it is in compliance with the Solid Waste Disposal Act as described above? Yes

  • Presentation of Potential Target Businesses The Company shall cause each of the Initial Shareholders to agree that, in order to minimize potential conflicts of interest which may arise from multiple affiliations, the Initial Shareholders will present to the Company for its consideration, prior to presentation to any other person or company, any suitable opportunity to acquire an operating business, until the earlier of the consummation by the Company of a Business Combination or the liquidation of the Company, subject to any pre-existing fiduciary obligations the Initial Shareholders might have.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (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 EveryCall. 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 EveryCall (e.g. hairpinning):

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