December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: 1The Services The Services are defined by the following properties: Technical Monitoring (XXX) is distributed system supporting EGI/NGI operations. It provides remote monitoring of services, visualization of the service status, dashboard interfacing, notification system and generation of availability and reliability reports. The central monitoring services are needed to ensure the aggregation of all EGI metric results and the access to the data at a EGI-wide scope through the central ARGO user interface. These results are exposed through the central ARGO web service and its programmatic interface (XML & JSON supported). On top of that, the ARGO Reporting System generates monthly availability reports about sites and operational tools for use of the service owners. In addition to the central services described above, the activity provides also: Monitoring of XXX.xx technical services: a centralised XXX installation is currently running in production to monitor the performance of XXX.xx operations tools and user community support tools. A central Nagios service is provided to support specific operations activities like User DN publishing in accounting records, GLUE information validation and monitoring of deployed software versions. New specific monitoring needs will emerge depending on the operations technical activities, and the central monitoring Nagios will be configured to address them. The Nagios infrastructure needs to be scaled accordingly. When the monitoring infrastructure of EGI will move to a full central deployment, the Monitoring service will include a high availability deployment of Nagios services to monitor the entire EGI Federation (more than 5000 services). The deployment must support the size of the infrastructure. Development of nagios probes: Maintenance of existing operations probes Development of new probes as required to support operations activities Requirements gathering Coordination This activity is responsible for the coordination of the system operations and upgrade activities with those partners that are in charge of operating other systems that depend on it. Operation Daily running of the system Provisioning of a high availability configuration Min. three Nagios boxes for the monitoring of the services. The Nagios’es cannot be deployed all in the...
December 2017. The LESSEE may, by August of each year, make a further offer to the LESSOR to lease the PROPERTY during a subsequent year, subject to the condition that his/her academic achievements and disciplinary record may be taken into account by the LESSOR in the consideration of the offer. However, if the LESSEE commits a breach of contract, amongst others, by not obeying the annexed Nooitgedacht C House Rules (Addendum “B”), Housekeeping Rules (Addendum “C”) or the University of Stellenbosch’s Code for Student Discipline as contained in part 1 of the General Year Book for the relevant year, or if the LESSEE does not qualify for registration as a student at the University of Stellenbosch for the following year, he/she will have no right to make a further offer.
December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Lever Agreement1 with following information: 1The Services The Services are defined by the following properties: Technical The GGUS system is divided into three environments: development, test and production environment. Every environment includes three layers: Presentation - web frontend to provide the entry point for the graphical user interface; Logic - AR Server which executes the workflow rules and performs the main tasks. AR Server is providing the communication interface between external systems and is accompanied by the email-engine to provide the additional mail-based interface into the helpdesk system; Backend - Oracle DBMS Human components This activity is responsible for the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it. Coordination with user communities, technology providers and operators is provided by dedicated Advisory Board meetings.
December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: 1The Services The Services are defined by the following properties: IT components The software provisioning infrastructure is composed by the following components: Integration with RT, a new product release (the tuple Product, Platform, Architecture) is associated with a RT ticket, which tracks the status of the product in the software provisioning process. Submission of new products with XML. Repository Back-end: responsible unit for handling the movement of packages between repositories, validating the individual product releases submissions, building accumulative as well as per-product YUM/APT repositories (multiple per OS/Arch case) and the other automations needed to perform the UMD operations. It also provide a RESTful API for external integrations (e.g. with the UMD portal/frontend) Composer: a web-based interface for bundling versioned software products that have successfully passed the UMD verification process, into a robust UMD release ready to be deployed either to the production or the candidate repositories. ReleaseXML editor: a web interface to create a new entry in the UMD release process., it is connected with the RT and the bouncer Repositories: the following repositories must be maintained for every operating system and major release supported: Untested: contains the packages to be installed during the verification Testing: contains the packages to be installed during staged rollout Base: contains the packages released in the first major release Update: contains the packages released in the update releases Release Candidate: it is generated before a UMD release, to simulate the production repositories after the UMD release under preparation. This is used to test the installability of the newly released components, as well as the products already in production. The processes to move products between repositories and to create releases must be as automated as possible. The task must provide statistics about the repository usage in terms of downloads, aggregated by packages and time. Front-end, the information about UMD releases (release notes, list of components, configuration) must be available in a web frontend. Note: the architecture of the internal components is not mandatory, but the services provided must be equivalent. The software provisioning infrast...
December 2017. All Queensland services will be expected to be compliant with the NQS staffing ratios from 1 January 2018.
December 2017. The agreement makes a number of references to provisions of the Code and, although clause 2.4 contains a standard provision that references to the Code are as it is amended from time to time, care should be taken to check that the Code references are up-to-date. 7 If the Grantor is the tenant under the Lease, the definitions of “Lease”, “Premises”, “Tenant” and “Tenant’s Guarantor” should be deleted. If the Grantor is a leaseholder, it would be good practice to give short details of the Lease in Schedule 1 in describing the “Property”.
December 2017. The Agreement was discussed and approved by the Customer and the Provider 17/03/2016. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: 1 The Services The Services are defined by the following properties: Technical The Operations Portal provides different capabilities: The detection and the follow-up of incidents on the different resource centre of the EGI infrastructure The repository for the static information related to Virtual Organizations The broadcast tool A visualisation (charts) and notification (emails or rss) system related to the downtimes impacting the services, the sites, the NGIs or the VO A reporting and computing system giving the availabilities and reliabilities of the NGI Core services, of the sites and of the services of a VO A user tracking tool Metrics and charts The architecture is composed of three modules: A database – to store information related to the users or the VO - namely MySQL A web module – graphical user interface – which is currently integrated into the Symfony and bootstrap frameworks A Data Aggregation and Unification Service named Lavoisier Both MySQL and the web module are clustered to provide High Availability. Different instances of the services must be deployed to ensure HA. This service includes the following components. 1 xxxxx://xxxxxxxxx.xxx.xx/document/2752 Coordination This activity is responsible for the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it. Coordination with the EGI Operations is necessary to support the production of reports and to provide data views not available in the portal standard interfaces. Operation Daily running of the system Provisioning of a high availability configuration A test infrastructure to verify interoperability and the impact of software upgrades on depending systems Deployment in the testing infrastructure and in production of the developments produced by EGI-Engage Maintenance This activity includes: bug fixing, proactive maintenance, improvement of the system coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the Operations Portal. Maintenance of probes to test the functionality of the service Requirements gathering D...
December 2017. The Agreement was discussed and approved by the Customer and the Provider on 29 April 2016 The Agreement extends the Corporate-level EGI Operational Lever Agreement1 with following information: The Services The Services are defined by the following properties: Technical The Accounting repositories store compute (serial and parallel jobs), storage, and cloud resources accounting data collected from Resource Centres of the EGI Federation. Accounting information is gathered from distributed sensors into a central accounting repository where it is processed to generate summaries that are available through the EGI Accounting Portal. The Accounting Repository, based on the XXXX software, has a MySQL database backend, and needs to ensure the exchange of accounting information with peer e-Infrastructures. The Accounting Portal receives and stores the site, user, and VO level summaries generated by the Accounting Repository and provide views via a web portal, for example, by aggregating sites in a country on custom time intervals. The databases are organized into a CPU record database, a User record database, and a topology database. Coordination This activity is responsible for: The coordination of the XXXX database operations and upgrade activities with those partners that are in charge of operating systems that depend on the central XXXX accounting databases and portal, or on which the accounting infrastructures depends. The Coordination with the EGI Operations to support accounting clients upgrade campaigns and other operational activities aiming at improving the accuracy and completeness of the accounting information gathered. Requirements gathering from service providers and end-users. Operation Daily running of the system including the repositories and the portal Provisioning of a high availability configuration A test infrastructure to verify interoperability and the impact of software upgrades on depending systems Deployment of new releases in production Maintenance This activity includes: Bug fixing, proactive maintenance, improvement of the system Coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the central EGI components of the system. Maintenance of probes to test the functionality of the service Requirements gathering Documentation Service hours and exceptions As defined in Corpor...
December 2017. The Agreement was discussed and approved by the Customer and the Provider. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: The Services The Services are defined by the following properties: Technical All the products released in UMD must be verified against the relevant acceptance criteria. Products must be deployed in a controlled environment. Every product in UMD must have a verification report associated, with the results of the verification process. The verifiers must be familiar with the core products used in EGI, the most common site configurations and third parties components such as DBMS and LRMS. The software to be verified involves user facing services, HTC services, storage services, cloud services, and all the products that are critical for EGI communities and are part of UMD. This task will also test the release candidates to check the dependencies and installability of the packages before the official release. UMD releases are expected to be 6-10 minor releases per year, distributed in two major releases, and supporting three operating system platforms. Staged Rollout is performed by Early Adopter (EA) sites who volunteer to deploy products fulfilling the acceptance criteria in the production infrastructure, exposing them to real users and real use cases. Coordination The task must coordinate the verifications when the process is outsourced to developers or user communities, this means: overview to advancements in the process and collect the reports produced during verification, making sure that the relevant information (GGUS tickets opened, known issues) are properly propagated to the UMD release. During staged rollout this task is responsible for the coordination of the Early Adopters activity, namely assign and monitor the progress of each individual product and corresponding EA teams, collect and analyze the reports provided by the EA team and in case of issues found make sure that relevant information is properly handled. Operation This task will operate a cloud infrastructure to be used as a testbed for the verification of the UMD products. The size of the infrastructure should allow the deployment of several VM in parallel to test also for service interoperability. Verification of products should be outsourced only when the effort required would be too high (for example for lack of expertise), or for technical limitations that prevent to deploy the service in the testbed. UMD Relea...
December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Lever Agreement1 with following information: 1The Services The Services are defined by the following properties: Technical This activity will run the processes that are implementing the resource allocation and the long tail of science platform. The processes are: Resource Allocation from a EGI centrally managed resource pool of resources, and Service Level management via the support of the e-GRANT tool User management for the long tail of science platform: validation of the user affiliation and user suspension when service quotas are exceeded. Human components This activity is responsible for requirements gathering from user communities and EGI Participants and for the coordination of the provisioning of services and community tools by virtual research communities and EGI participants. Operation Operation of the e-grant tool 2Service hours and exceptions As defined in Corporate-level EGI Operational Lever Agreement. 3Support As defined in Corporate-level EGI Operational Lever Agreement. Support is provided via EGI Service Desk2 Support Unit: <specify> Support is available between: Monday and Friday 9:00 and 17:00 CET/CEST time This excludes public holidays at the same time in all organizations providing the service.
