Internal interfaces & interactions Sample Clauses

Internal interfaces & interactions. Figure 5 - Identity Management module internal interfaces & interactions The IAM module will expose its functions via API to the other modules of the HEROES platform. Internal and external authentication and authorization will be managed by the Identity Management Module: • Internal services can interact with the IAM module and request an authorization check at any time. • External access control will be centralized by the Service Gateway (see User Interface & API module Section 4.10) that will handle the authentication and authorization requests.
Sample 1
AutoNDA by SimpleDocs
Internal interfaces & interactions. Figure 9 - Deployment Module internal interfaces & interactions The Deployment & Integration module will interact with the other HEROES platform modules via API. Identity Management: • User identification (check User’s id, role, group/project/organization) • Authorization (check if the user has access to the remote platform) • Endpoint authentication (check if the API call was initiated from a legitimate endpoint within the HEROES platform) Workflow & Job Management: • Receive tasks with detailed requirements to deploy / undeploy remote cloud instances • Send events with status of all executed task Logging & Accounting: • Send events with details about all received requests/tasks • Send events with status of all executed task
Sample 1
Internal interfaces & interactions. Interaction from cloud or HPC nodes to outside will be done though SSH to guarantee the deployment in HPC Centres with strong connectivity limitations. Figure 15 - Energy Management & Optimization internal interfaces & interactions EAR will gather 3 types of data that will be used for HEROES accounting and the Decision module: • Job accounting: Performance and energy metrics corresponding with HEROES jobs. This information is gathered at runtime, and it can be reported at application end or periodically depending on system access limitations. It will include the data for job accounting (identification and resource consumption) and processed information with the application runtime characteristics that can be useful for the decision module. Ideally, this information could be the runtime signatures of the application but, depending on the availability and the amount of data we could expect to send and store a kind of application profile and not all the signatures computed.
Sample 1
Internal interfaces & interactions. Figure 20 - Application and Container Management & Orchestration internal interfaces & interactions The Container Management & Orchestration will interact with the other HEROES platform modules via API. Identity Management: • User identification (check User’s id, role, group / project / organization) • Authorization (check if the user has access to the remote platform and to this service) • Endpoint authentication (check if the API call was initiated from a legitimate endpoint within the HEROES platform) Data Management: • Uploading container from the User to the platform • Container storage within the HEROES platform including: o Versioning of the container o Tags linked to the stored container Logging & Accounting: • Send events with details about all received requests / tasks • Send events with status of all executed tasks
Sample 1
Internal interfaces & interactions. Figure 28 - Decision Module & Performance Metadata Module internal interfaces & interactions The decision module will interact with the other HEROES platform modules via API. Energy Management and Optimization – EAR: • to get metadata about jobs power consumption Data Management: • to get accounting logs and other data useful for making predictions • to store predictions and users’ choices Workflow & Job management: • to get workflow submission request • to receive workflow placement suggestions Logging & Accounting: • Send events with details about all received requests / tasks • Send events with status of all executed task User Interface & API: • to request cost estimation of the workflow on different platforms using Cost API • to provide the performance dashboard
Sample 1

Related to Internal interfaces & interactions

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Network PHARMACY is a retail, mail order or specialty pharmacy that has a contract to accept our pharmacy allowance for prescription drugs and diabetic equipment or supplies covered under this plan. NETWORK PROVIDER is a provider that has entered into a contract with us or other Blue Cross and Blue Shield plans. For pediatric dental care services, network provider is a dentist that has entered into a contract with us or participates in the Dental Coast to Coast Network. For pediatric vision hardware services, a network provider is a provider that has entered into a contract with EyeMed, our vision care service manager.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

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