DECICE Framework Sample Clauses

DECICE Framework. ‌ The DECICE framework favors a component based composition for its architectural approach, which enables switching between different implementations of the same component. Therefore, the plat- form can be specified and implemented as a set of interfaces that reflect the organizational structure of the project. Additionally, components interacting with external interfaces can be swapped out or updated if the external interfaces change without affecting the internal components. 1) it is still missing an elicitation and specification of requirements for the software architecture itself that is part of a future deliverable and will be published as soon as they have been defined. For the time being Figure 1 serves as a basis for understanding the minimal set of components that are required for the DECICE framework and what interfaces to other components they need to provide. Starting with the heart of the framework, the DECICE Control Manager is responsible for dealing with the majority of the business logic and is central to almost all control flows in the framework. In order to store settings, configuration and data relevant for the DECICE framework, the control manager has its own database, the DECICE Config Store. Another component the control manager might send requests to or receive from is the Platform Specific Glue Code for the wrapper as well as the scheduler. These interfaces serve as an integration of the control manager with the underlying platform. Here the compute plane is managed by Kubernetes but by swapping them out, they could also support another orchestration platform such as Hashicorp Nomad or Apache Mesos. The wrapper glue code serves as an abstraction for controlling the KubeAPI without having to internally adhere to its expected syntax and having the wrapper glue code translate requests from the internal representation to the format expected by the KubeAPI. The scheduler glue code serves as an entry point for the underlying platform to request scheduling decisions from the DECICE framework. The DECICE API exposes two components for interactions with the underlying platform, the end user API (job and telemetry) and the admin API (control and security). The end user API provides interfaces to submit jobs, deployments and workloads. These submissions are processed by the control manager and then stored to be considered during future scheduling decisions. Furthermore, it can also be used to send queries to the metrics storage, while conside...

Related to DECICE Framework

  • Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.

  • Legal Framework 1. This programme agreement shall be read in conjunction with the following documents which, together with this programme agreement, constitute the legal framework of the EEA Financial Mechanism 2014-2021: (a) Protocol 38c to the EEA Agreement on the EEA Financial Mechanism 2014-2021; (b) the Regulation on the implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “Regulation”) issued by the Donor States in accordance with Article 10(5) of Protocol 38c; (c) the Memorandum of Understanding on the Implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “MoU”), entered into between the Donor States and the Beneficiary State; and (d) any guidelines adopted by the FMC in accordance with the Regulation. 2. In case of an inconsistency between this programme agreement and the Regulation, the Regulation shall prevail. 3. The legal framework is binding for the Parties. An act or omission by a Party to this programme agreement that is incompatible with the legal framework constitutes a breach of this programme agreement by that Party.

  • NIST Cybersecurity Framework The U.S. Department of Commerce National Institute for Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity Version 1.1.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Residence Life or the Director’s designee.

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

  • Strategic procurement Aim of strategic procurement: No strategic procurement

  • Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.

  • Staffing Plan The Board and the Association agree that optimum class size is an important aspect of the effective educational program. The Polk County School Staffing Plan shall be constructed each year according to the procedures set forth in Board Policy and, upon adoption, shall become Board Policy.

  • TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order. (b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation. (c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled. (d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA. (b) If the HSP is not subject to the procurement provisions of the BPSAA, the HSP will have a procurement policy in place that requires the acquisition of supplies, equipment or services valued at over $25,000 through a competitive process that ensures the best value for funds expended. If the HSP acquires supplies, equipment or services with the Funding it will do so through a process that is consistent with this policy.