Expected outcomes & behaviour Sample Clauses

Expected outcomes & behaviour. The Identity Management module will be responsible for handling authentication and authorization control whether it concerns internal request made by HEROES’ services or external request from a user using the published APIs. The following workflows schemas will present the expected behaviour of the module when confronted to a user’s request to log in onto the HEROES platform and then proceed to call upon one of the published API.
Sample 1
AutoNDA by SimpleDocs
Expected outcomes & behaviour. The Deployment & Integration Module main objective is to implement / execute tasks that will be sent from the Workflow Management module to ensure that the resources are available for receiving ML/HPC jobs. The following types of incoming tasks are expected: • Deploy / undeploy cloud compute resources • Check if HPC Centre HEROES resources and services are active and correctly configured The Deployment & Integration Module will also contain a library of Ansible [13] playbooks that will be used to install and configure the HEROES Runtime both in the cloud platforms and in the HPC Centres. 4.2.5.1 Deployment workflows Figure 10 - Cloud Platform Deployment workflow & HPC Centre Compliance Check workflow The Cloud Platform Deployment workflow will take care of: • Start / Stop compute nodes on existing Private Cloud Clusters within an Organization scope • Deploy / undeploy temporary compute nodes for single users and organizations without an existing Private Cloud Cluster. (Please note that this will cover all types of different compute nodes, including but not limited to CPU nodes, GPU nodes, Remote Visualization nodes.) • The above tasks will be accomplished using the Cloud Platform CLI and APIs, mainly through scripts. The scripts will be exposed to the Workflow module either directly or via APIs. The HPC Centre Compliance Check workflow will take care of: • Check that the HEROES Runtime is active on the HPC Centre Headnode (see section 4.2.1) • Check that the HEROES Runtime is configured as expected • The above tasks will be accomplished using Ansible roles, containerized applications and services, scripts. The Ansible roles will be exposed to the Workflow module either directly or via APIs.
Sample 1
Expected outcomes & behaviour. As stated before, the expected outcome for this module is: • Dynamic and transparent energy optimization for running jobs. EAR will dynamically analyse running jobs and will select the optimal frequency. HEROES will apply a default policy for non-expert users and will give the opportunity to select a specific energy optimization policy to energy-aware users. Anyway, system specific settings will be considered. Energy optimization policies will be applied when supported by system limitations. • Automatic job accounting: Metrics gathered by EAR will be reported to HEROES DB. Not all the data will be reported, only data needed for HEROES job accounting and for the decision module. Given a job could generate lots of signatures at runtime, we will select relevant data such as 1 signature per application phase and phase duration. • System monitoring: EAR will report system status and relevant metrics / events to the decision module to characterize our ecosystem.
Sample 1
Expected outcomes & behaviour. The Data Management Module will be the core of the following workflows.
Sample 1
Expected outcomes & behaviour. The Application and Container Management & Orchestration Module main objective is to allow the creation, management, and orchestration of application. The following types of incoming tasks are expected: • Create / Delete application • Update application • Publish / Unpublish application The application packager (organization application administrator or Application Provider) can create an application within the HEROES platform using a container. The application creation includes: • The application information will be stored in a database within the Application and Container Management & Orchestration module. • The storage of the application’s container will be managed by the Data Management module After its creation, application will become visible for modifications or publication for its owner. The owner of an application must make functional tests within the HEROES platform with its application before each new application publishment. After publishment, the cost and license of the published application will be available for the Cost Management module.
Sample 1
Expected outcomes & behaviour. The Workflow & Job Management Module main objective is to allow the creation, management, and orchestration of custom workflows, both for engineering and architecture management. The following types of tasks are expected: • Create / Delete architecture / engineering / scientific workflows • Run a specific workflow interacting with the rest of the HEROES architecture • Log all the states and changes of the workflow • Give proper metadata about the workflows state and execution The Workflow & Job Management main tool (Ryax) can easily create workflows for the HEROES platform using their own GUI or importing it as code from an external repository. The workflows creation and later execution include some interaction with other modules that are part of the HEROES infrastructure, where: • The execution of the workflow could be triggered by the user directly using the User Interface via a web browser. • The user can define the data used by the workflow through HEROES web interface or APIs. Then, the Workflow & Job Management module interacts indirectly with the Data Management module to transfer data to the target infrastructures and used by the different workflow tasks. • All the workflow submission parameters are forwarded by the Service Gateway to the Workflow Management Module. It then uses them through the Decision Module to get some information about placement strategy for the workflow. • The user chooses if he continues or not with the workflow execution via web browser using the User Interface. • When the target infrastructure is selected, the Deployment and Integration Module deploys the required resources if needed. • The toolset is selected from an available Singularity container on the Application and Container Management and orchestration module. • The job is submitted to the Resource Providers using the Submission / Transfer module. • The job is monitored using the Submission / Transfer Module and the obtained metrics are placed in the Telemetry / Accounting Module. • The metadata retrieved from the execution and workflow status is saved in the General Logging Module.
Sample 1
Expected outcomes & behaviour. The decision module will operate in four successive steps:
Sample 1
AutoNDA by SimpleDocs
Expected outcomes & behaviour. 4.8.5.1 Log events / messages and store in central repository Figure 32 - Logging & storing workflow Thanks to the many source plugins available for FluentD, a component of the HEROES platform will be able to log using native libraries (python, java, etc.) interacting directly with the FluentD td-agent (TreasureData Agent) [11] process. In case of system services, the rsyslog [34] source plugin will be used to forward any event / message that will normally be sent just to the OS (Operating System) logging facilities. The td-agent process will then forward the logs to the central repository, where Elasticsearch will be able to tag, analyse and index the received data, that will then be ready for consultation, search, and further analysis with Xxxxxx.
Sample 1
Expected outcomes & behaviour. The Costs Module main objective is to: • Provide means to manage business models for the applications / workflows and resources. The history of each business model will be kept for auditing. • Provide a centralized accounting information for billing purposes (keep track of all consumed resources and associated prices).
Sample 1

Related to Expected outcomes & behaviour

  • Expected Outcomes The educational goals and objectives for improving student achievement, including how much academic improvement students are expected to show each year, how student progress and performance will be evaluated and the specific results to be attained, as described in Section 5a of the application: Student Performance, Assessment and Evaluation.

  • Expected Outcome With this waiver, the school will be able to implement its program and evaluate its teachers in accordance with its Performance Appraisal System, which is designed to produce greater accountability and be consistent with the school’s goals and objectives. This will benefit staff members as well as students and the community. Non-Automatic Waivers: Statute Description and Rationale and Replacement Plan

  • Outcomes Secondary: Career pathway students will: have career goals designated on SEOP, earn concurrent college credit while in high school, achieve a state competency certificate and while completing high school graduation requirements.

  • Influenza Vaccination The parties agree that influenza vaccinations may be beneficial for patients and employees. Upon a recommendation pertaining to a facility or a specifically designated area(s) thereof from the Medical Officer of Health or in compliance with applicable provincial legislation, the following rules will apply:

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • PERFORMANCE OUTCOMES 8 A. CONTRACTOR shall achieve performance objectives, tracking and reporting Performance 9 Outcome Objective statistics in monthly programmatic reports, as appropriate. ADMINISTRATOR 10 recognizes that alterations may be necessary to the following services to meet the objectives, and,

  • Behaviour No obscene or insulting language or disorderly behaviour shall be permitted. This includes any form of entertainment that may be considered lewd or inappropriate for a public place or that may offend or cause embarrassment to others.

  • Intrusion Detection All systems involved in accessing, holding, transporting, and protecting PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY that are accessible via the Internet must be protected by a comprehensive intrusion detection and prevention solution.

  • Influenza Vaccine Upon recommendation of the Medical Officer of Health, all employees shall be required, on an annual basis to be vaccinated and or to take antiviral medication for influenza. If the costs of such medication are not covered by some other sources, the Employer will pay the cost for such medication. If the employee fails to take the required medication, she may be placed on an unpaid leave of absence during any influenza outbreak in the home until such time as the employee has been cleared by the public health or the Employer to return to the work environment. The only exception to this would be employees for whom taking the medication will result in the employee being physically ill to the extent that she cannot attend work. Upon written direction from the employee’s physician of such medical condition in consultation with the Employer’s physician, (if requested), the employee will be permitted to access their sick bank, if any, during any outbreak period. If there is a dispute between the physicians, the employee will be placed on unpaid leave. If the employee gets sick as a reaction to the drug and applies for WSIB the Employer will not oppose the application. If an employee is pregnant and her physician believes the pregnancy could be in jeopardy as a result of the influenza inoculation and/or the antiviral medication she shall be eligible for sick leave in circumstances where she is not allowed to attend at work as a result of an outbreak. This clause shall be interpreted in a manner consistent with the Ontario Human Rights Code.

  • Rating Impact on Student Learning Growth ESE will provide model contract language and guidance on rating educator impact on student learning growth based on state and district-determined measures of student learning. Upon receiving this model contract language and guidance, the parties agree to bargain with respect to this matter.

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