icontrol package Submodules icontrol Sample Clauses

icontrol package Submodules icontrol session module‌‌‌‌‌ A BigIP-RESTServer URI handler. REST-APIs use it on the requests library. Use this module to make calls to a BigIP-REST server. It will handle:
AutoNDA by SimpleDocs
icontrol package Submodules icontrol authtoken module‌‌‌‌‌ A requests-compatible system for BIG-IP token-based authentication. BIG-IP only allows users with the Administrator role to authenticate to iControl using HTTP Basic auth. Non- Administrator users can use the token-based authentication scheme described at: xxxxx://xxxxxxxxxx.x0.xxx/wiki/xxxxxxxx.xxxxxxxxxxxxxx_with_the_f5_rest_api.ashx Use this module with requests to automatically get a new token, and attach requests.Session object, so that it is used to authenticate future requests. Instead of using this module directly, it is easiest to enable it by passing a token=True argument when creating the iControlRESTSession: >>> iCRS = iControlRESTSession('bob', 'secret', token=True) class icontrol.authtoken.iControlRESTTokenAuth(username, password, lo- gin_provider_name=’tmos’) Bases: requests.auth.AuthBase Acquire and renew BigIP iControl REST authentication tokens. Parameters • username (str) – The username on BigIP • password (str) – The password for username on BigIP • login_provider_name (str) – The name of the login provider that BigIP should consult when creating the token. If username is configured locally on the BigIP, login_provider_name should be "tmos" (default). Otherwise (for example, username is configured on LDAP that BigIP consults), consult BigIP documentation or your system administrator for the value of login_provider_name. get_new_token(netloc) Get a new token from BIG-IP and store it internally. Throws relevant exception if it fails to get a new token. This method will be called automatically if a request is attempted but there is no authentication token, or the authentication token is expired. It is usually not necessary for users to call it, but it can be called if it is known that the authentication token has been invalidated by other means.

Related to icontrol package Submodules icontrol

  • Quality Control Program The Contractor shall describe the Quality Control Program in a written document which shall be reviewed by the Engineer prior to the start of any production, construction, or off-site fabrication. The written Quality Control Program shall be submitted to the Engineer for review at least ten (10) calendar days before the start of construction. The Quality Control Program shall be organized to address, as a minimum, the following items:

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • CONTRACTING BODY SATISFACTION MONITORING 18.1 The Authority may from time to time undertake (or procure the undertaking of) a Contracting Body satisfaction survey ("Contracting Body Satisfaction Survey") the purpose of which shall include:

  • CONTRACTOR TO PACKAGE DELIVERABLES The Contractor will package deliverables in accordance with good commercial practice and shall include a packing list showing the description of each item, the quantity and unit price unless otherwise provided in the Specifications or Supplemental Terms and Conditions, each shipping container shall be clearly and permanently marked as follows: (a) The Contractor's name and address, (b) the City’s name, address and purchase order or purchase release number and the price agreement number if applicable, (c) Container number and total number of containers, e.g. box 1 of 4 boxes, and (d) the number of the container bearing the packing list. The Contractor shall bear cost of packaging. Deliverables shall be suitably packed to secure lowest transportation costs and to conform to all the requirements of common carriers and any applicable specification. The City's count or weight shall be final and conclusive on shipments not accompanied by packing lists.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Documentation control Specify how documentation will be identified with an alpha numeric which indicates source, recipient, communication number etc. Provide details of any particular format or other constraints; for example that all contractual communications will be in the form of properly compiled letters or forms attached to e mails and not as a message in the e mail itself. State any particular routing requirements but note from TSC3 who issues what to whom.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • CONTRACTOR CUSTOMER SERVICE REPRESENTATIVE Contractor shall designate a customer service representative (and inform Enterprise Services of the same) who shall be responsible for addressing Purchaser issues pertaining to this Master Contract.

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