SoftFIRE Middleware Architecture and supporting services Sample Clauses

SoftFIRE Middleware Architecture and supporting services. The SoftFIRE middleware architecture is going through a deep restructuring and consolidation in order to provide better services to experimenters. With reference to Figure 1, several “managers” will be designed, implemented and provided to experimenters in order to support the experiment lifecycle. The identified managers are NFV Manager, for virtualized resources, SDN Manager for the allocation of the SoftFIRE provided SDN functionalities, a Security Manager that will support the allocation of security functions made available by SoftFIRE and usable by the experimenters, the Monitoring Manager for some related monitoring functionalities. The NFV Manager and the SDN Manager are under development and will be provided in time for the second wave. The other managers will be progressively introduced in order to be used in the following wave of experimentations or Hackathons/Challenge. it is important to clarify that access to the individual OpenStack instances will be granted only via the SoftFIRE Experiment Manager (i.e., the SoftFIRE Middleware), and in most of the cases OpenStack APIs won’t be available to be directly consumed by experimenters. Nevertheless, the testbed will be aligned with industry-oriented standardisation efforts: TOSCA is going to be exposed to experimenters for deploying and provisioning resources on the federated infrastructure. This implies also to deprecate the usage of jFED and FITeagle in favour of a TOSCA approach. This means that SoftFIRE generic resources will be described as TOSCA nodes and the SoftFIRE Experimenter Manager will support the “translation” and allocation of the requested resource onto the SoftFIRE available resources. Experimenters could already start to get familiar with the TOSCA APIs and functionalities offered by the Open Baton framework [3]. Although the final ones which will be exposed by the SoftFIRE middleware will be slightly different, the SoftFIRE consortium will try to maintain compatibility with the functionalities provided by the Open Baton APIs. SoftFIRE will make use of the Open Baton 4th release which will be launched by the end of April. The Open Baton installation in SoftFIRE will provide the following components: NFVO, Generic VNFM, Auto-scaling Engine, Zabbix Plugin, and OpenStack driver. Experimenters could also consider to extend the set of components provided by the Open Baton framework. For this they could make use of the Open Baton SDK and build either a new VIM driver, Monitoring driver...
Sample 1
AutoNDA by SimpleDocs

Related to SoftFIRE Middleware Architecture and supporting services

  • Software and Services Upon execution of this Contract, a notice of award for RFO DIR-SDD-TMP-232 shall be posted by DIR on the Electronic State Business Daily.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Software Services If elected by Customer, the following Software Services will be made available for Customer’s use.

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.

  • Hardware and Software In order to use the Services, you must obtain and maintain, at your expense, compatible mobile hardware and software as specified by Credit Union from time to time. Credit Union is not responsible for any third party software you may need to use the Services. Any such software is accepted by you as is and is subject to the terms and conditions of the software agreement you enter into directly with the third party software provider at time of download and installation.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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