Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ngi:start [2018/12/10 14:26] – kunkel | ngi:start [2021/07/09 13:05] (current) – [Presentations] kunkel | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ====== Next Generation Interfaces ====== | ====== Next Generation Interfaces ====== | ||
| - | //This page is under construction.// | ||
| + | The efficient, convenient, and robust execution of data-driven workflows and enhanced data management are key for productivity in computer-aided Research, Development and Engineering (RD& | ||
| + | Still, the storage stack is based on low-level POSIX I/O (or objects in cloud storage). | ||
| + | The forum would bring together vendors, storage experts, and users to discuss key features of alternative APIs and aims to establish governance strategies. | ||
| - | The efficient, convenient, and robust execution of data-driven workflows and enhanced data management are key for productivity in computer-aided RD&E. Still, the storage stack is based on low-level POSIX I/O (or objects in cloud storage). | + | We are exploring to establish |
| - | We are establishing | + | The envisioned coarse-grained API aims to overcome current obstacles for highly parallel workflows but would be beneficial also in the domain of big data and even desktop PC. |
| It bears the opportunity to create a new ecosystem. | It bears the opportunity to create a new ecosystem. | ||
| Line 17: | Line 19: | ||
| The final component is how to enable vendors to do differentiating optimizations without violating the common interface. | The final component is how to enable vendors to do differentiating optimizations without violating the common interface. | ||
| - | Main features of the resulting prototype: | + | Main features of the resulting prototype |
| * Smart hardware and software components | * Smart hardware and software components | ||
| * Storage and compute are covered together | * Storage and compute are covered together | ||
| Line 29: | Line 31: | ||
| {{:: | {{:: | ||
| - | The system shall make placement decisions, partial replication of data depending on the availability and characteristics of the storage, but also considering the usage patterns particularly of the workflows. | + | The system shall make placement decisions, partial replication of data depending on the availability and characteristics of the storage, but also considering the usage patterns, particularly of the workflows. |
| Thus, all available storage shall be used concurrently, | Thus, all available storage shall be used concurrently, | ||
| In contrast, existing systems rely on data migration and policies. | In contrast, existing systems rely on data migration and policies. | ||
| + | |||
| ===== Standardization ===== | ===== Standardization ===== | ||
| - | We are building | + | We are in the process |
| - | Driven | + | The process will share the idea with the successful |
| + | The approach is sketched in the figure below; | ||
| + | members are experts from domain science, industry and data centers and form the bodies. | ||
| + | The activity is led by the elected steering board. | ||
| + | Topic-specific workgroups and committees develop the standard (data model and APIs) driven by relevant | ||
| + | Ultimately, we will support the creation of a reference implementation based on state-of-the-art technology that demonstrates the approach on the use-cases. | ||
| + | We are aware that this endeavor | ||
| + | |||
| + | We expect that vendors and researchers will embrace the open ecosystem similarly to MPI and explore and contribute to the forum and its development. | ||
| {{ : | {{ : | ||
| + | |||
| + | ===== Presentations ===== | ||
| + | |||
| + | ISC HPC 2021 -- {{ : | ||
| Line 43: | Line 58: | ||
| We welcome contributions. | We welcome contributions. | ||
| - | If you are interested in this topic, subscribe to our [[https:// | + | If you are interested in this topic, subscribe to our [[https:// |
