TOSCA Template Model Sample Clauses

TOSCA Template Model. Figure 1 shows a generic template that uses a graph to map application components and their relationships. TOSCA provides a description language to define a service template (ST), which in turn includes a topology template (TT), and a set of Plans (P) to orchestrate the execution of the application. The language is essentially based on the creation of a scheme, where components are placed along with their connections with other components. From this perspective, the language resembles the Block Diagram schemes which can be used to describe a generic algorithm. The TT is represented by a set of nodes. Nodes allow to hierarchically describe each component up to the lowest level (i.e., the VM or container that host the component), while edges provide the relationships among the components (each edge has a type describing the specific relationship, e.g., hosted on, etc.). Nodes expose capabilities (essentially features that can be used by other nodes to match with their requirements), interface (a set of functions that can be used to interact with the node, e.g., a create function that allow to create a database, etc.), and requirements (a set of features that must be satisfied in order to correctly work). Each node has its own type, as well as the relationships among the nodes (also relationships have their types). Actually, each node can be an installable package and/or an image (e.g., a VM image, a container image, etc.). Each node exposes a set of capabilities (C) representing the set of functionalities offered by the node, and a set of requirements (R) representing the specific needs (e.g., a Web Application may require an application server in order to be run). Nodes have also properties and interfaces: the former provide a description of the functionalities offered by the node-service, the latter generally concern with scripts that are used to manage the node operations. Similarly, relationships may expose properties and interfaces. A relationship indicates which nodes can satisfy the requirements of another node, by means of its capability. From this viewpoint a TT defines a mapping between the C of a node and the R of another. A plan specifies how the nodes interact each other in order to provide the whole service represented by the ST. All these elements are packaged together in a single entity called Cloud Service ARchive (CSAR). Requirements for a type can be satisfied also by the underlying hardware infrastructure that can be considered as a speci...
Sample 1
AutoNDA by SimpleDocs

Related to TOSCA Template Model

  • Template That certain three well drilling template acquired, inter alia, by Seller for use in connection with the drilling of the OCS-G 7049 #5 Well.

  • Templates The Applicant shall use Templates provided by Alberta Innovates to comply with its Required Reporting Metrics, Reports obligations, and with the Survey requirements. Because the Reports may contain technical or proprietary information about the Project or the Applicant, the Templates will specify when a section will be considered non-confidential. The content of sections that are marked as non-confidential can be disclosed in the public domain. All other sections will be considered confidential, and thus can only be disclosed to the Government of Alberta and to Funding Partners, if any, in confidence, but to no other party.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Project Implementation 2. The Borrower shall:

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Marketing Plan The MCP shall submit an annual marketing plan to ODM that includes all planned activities for promoting membership in or increasing awareness of the MCP. The marketing plan submission shall include an attestation by the MCP that the plan is accurate is not intended to mislead, confuse or defraud the eligible individuals or ODM.

  • Project Website The State will develop and maintain a website that will be made available in advance of the first public meeting for this project. The Engineer shall provide project information for the project website to the State including documents related to project background, study area limits, study objectives, project photos, study area maps, material presented at public meetings, and contact information for requesting additional information. The project website will be updated with the documents and other information provided by the Engineer to the State after each set of public meetings and the final report in PDF format provided by the Engineer will be posted by the State to give the general public access to the document.

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