Deployment Models Sample Clauses

Deployment Models. Contractor may provide cloud based services through the following deployment methods: • Private cloud. The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Deployment Models. Three main deployment models can be considered when designing an SDN-based control plane: • A fully centralized model, with a logically single SDN controller with the whole view of the entire DCN • A hierarchical model, with a first layer of “child” SDN controllers responsible for disjoined portion of the DCN and a “parent” SDN controller which handle a more abstracted view of the whole DCN, obtained through the cooperation with the “child” controllers. This model could be adopted to handle very different technology domains through specialized “child” SDN controllers and requires only a north-south interaction between each child controller and its parent controller. Of course, this interaction can be recursive and involve several layers in the SDN controller hierarchy. • A distributed east-west model, with a set of peer SDN controllers, each of them responsible for a portion of the DCN and cooperating together with horizontal communications to achieve the whole control and management of the entire DCN. In general, the third model is very complex and particularly suitable to large scenarios characterized by a variety of trust domains where each network domain is controlled through proprietary protocols and a very limited amount of information can be exchanged outside the domain boundaries. The inter- controller communication can be regulated using protocols like BGP (Border Gateway Protocol) [RFC4271] or PCEP (Path Computation Element communication Protocol) [RFC5440]. However, this model is scarcely applicable to the intra-DC scenario, where a single DC provider is responsible for the whole DCN. The hierarchical model may be of interest due to the heterogeneous nature of the COSIGN DCN. However, the complexity and the time delays required by the inter-controller synchronization and communication (also in this case the PCEP is a reasonable candidate, with the extensions for the stateful and active mode [PCESTAT], [PCEINIT]) can be considered as strong limitation in highly dynamic scenarios like DCN environment. For this reasons, the COSIGN DCN Control Plane solution is based on the centralized deployment model, with a single SDN controller that maintains the overall view and control of the overall DCN. The specific characteristics of the different technologies available at the data plane are handled through dedicated plugins and abstracted with a powerful information model that allows for the application of unified functions and procedures in the SDN contro...
Sample 1Sample 2
Deployment Models. The Order will state the number of and, if applicable, type of User and the type of deployment model through which Customer will receive access to and rights in the Software. Other than as stated in this Agreement or in an Order, Viewpoint reserves all other right, title, and interest in the Software. (a) On Premises. Subject to Customer’s compliance with this Agreement, Viewpoint grants Customer a limited, worldwide, nonexclusive, nontransferable license, without sublicense rights, to (i) install one production copy of the Software on one server owned or leased by Customer, or the number of servers listed in the Order if a different number of servers is stated in the Order, for Customer’s own business purposes and (ii) allow the number of and, if applicable, type of Users stated in the Order to access and use the Software concurrently (“License”) in accordance with the Documentation. Customer may make up to three nonproduction copies of the Software under an on premises License for backup, archival, or testing purposes. Customer is responsible for procuring, installing, configuring, and maintaining all hardware, software, and operating systems required to run the Software, as set forth in the Documentation. If applicable, Viewpoint will use commercially reasonable efforts to install the Software on a mutually agreed upon schedule. As used in this Agreement installation means when a copy of the Software has been installed on a server owned or leased by Customer and at least one User workstation. (b) Software-as-a-Service. Subject to Customer’s compliance with this Agreement, Viewpoint will make the Software available to Customer to (i) access and use the Software for Customer’s own business purposes and (ii) allow the number of and, if applicable, type of Users stated in the Order to access and use the Software (“SaaS Subscription”) in accordance with the Documentation. The Software is located on servers that are controlled by Viewpoint. Customer has no right to receive a copy of the object code or source code to the Software.
Sample 1Sample 2
Deployment Models. The Order will state the number of and, if applicable, type of User and the type of deployment model through which Customer will receive access to and rights in the Software. (a) On Premises. Subject to Customer’s compliance with this Agreement, Viewpoint grants Customer a limited, worldwide, nonexclusive, nontransferable license, without sublicense rights, to (i) install one production copy of the Software on one server owned or leased by Customer for Customer’s own business purposes and (ii) allow the number of and, if applicable, type of Users stated in the Order to access and use the Software (“License”) in accordance with the Documentation. Customer may make up to three nonproduction copies of the Software under an on premises License for backup, archival, or testing purposes. Customer is responsible for procuring, installing, configuring, and maintaining all hardware, software, and operating systems required to run the Software, as set forth in the Documentation. If applicable, Viewpoint will use commercially reasonable efforts to install the Software on a mutually agreed upon schedule. As used in this Agreement installation means when a copy of the Software has been installed on a server owned or leased by Customer and at least one User workstation. (b) Software-as-a-Service. Subject to Customer’s compliance with this Agreement, Viewpoint will make the Software available to Customer for the Term (as defined in Section 14.1, below) to (i) access and use the Software for Customer’s own business purposes and (ii) allow the number of and, if applicable, type of Users stated in the Order to access and use the Software (“Subscription”) in accordance with the Documentation. The Software is located on servers that are controlled by Viewpoint. Customer has no right to receive a copy of the object code or source code to the Software.
Sample 1Sample 2
Deployment Models. Private cloud ‐ The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises. Community cloud ‐ The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises. Public cloud ‐ The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider. Hybrid cloud ‐ The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).
Sample 1
Deployment Models. Public and private cloud services in a UK government context: G-Cloud phase 2 definitions: Public Cloud means Utility Computing that is available to individuals, public and private sector organisations. Public Cloud is often non-geographically specific and can be accessed wherever there is an Internet connection.
Sample 1

Related to Deployment Models

  • Deployment If the Tenant is deployed with a military unit for a period of not less than 90 days.

  • Training Programs All employees shall successfully complete all necessary training prior to being assigned work (e.g., all employees will complete health and safety training prior to being assigned to task). Nothing in this Article or provision shall constitute a waiver of either party’s bargaining obligations or defenses. The Employer still has an obligation to notify and bargain changes in terms and conditions of employment with the exclusive representative.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Training Program It is agreed that there shall be an Apprenticeship Training Program, the provisions of which are set forth in Exhibit "D", which is attached hereto and forms part of this Agreement.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate Ymax’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. Ymax shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!