Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
Problem: Currently, resonance frequency-based HRV training is backed by robust scientific evidence, but it remains inaccessible to the masses due to the high costs of proprietary hardware and software tools. There is a need to bridge the gap between basic consumer wearables and professional open-source psychophysiological research. Solution: BreathState 2.0 solves this by evolving the existing mobile application into an active, multi-modal, clinical-grade biofeedback platform. This will be achieved by introducing cross-platform architecture (Mobile/Web/VR), integrating research-grade hardware (Vernier respiration belts), and porting Python-based professional analytics natively to the application. Deliverables: A multi-patient database architecture using Drift with CSV export capabilities. Cross-platform application builds supporting Android, iOS, and Web. Integration of Vernier GDX-RB respiration belts via BLE with Polar H10 synchronization. A full on-device NeuroKit2-to-Dart analytics engine (computing time-domain HRV, frequency-domain HRV, RSA, and Baevsky Stress Index). A real-time biofeedback dashboard featuring dual-axis waveforms and adaptive guided breathing. An immersive WebXR HRV visualization scene (breathing sphere) accessible via Meta Quest headsets.
<p>Currently, the ways to flash images in BeagleBone hardware are not easy especially for beginners, SD card method takes up much time and manual configuration, BBBlfs flashing tool works but is CLI based, not much reliable and works on limited platforms, TI's Uniflash tool is also old and works only under older versions of Windows and Linux with a lot of manual configuration. The project is to port the BeagleBone bootloader server BBBlfs(currently written in c) to JavaScript(node.js) and make a cross platform GUI (using electron framework) flashing tool utilising the etcher.io project. This will allow us to have single code base for a cross platform tool.</p> <p>The tool works as:</p> <ol> <li>TFTP transfer of SPL binary and u-boot.</li> <li>Utilizing the ums feature of u-boot, booting the BB hardware into USB mass storage mode.</li> <li>Flashing the BB hardware with etcher.io like tool. </li> </ol> <p>This project project will be really helpful for everybody especially newbies, who would have a nice experience with flashing images easily and faster, so that they can focus on the more important stuff be it their robotics project, kernel development or some new PRU hack.</p>
Virtio is an open standard designed to enhance I/O performance between virtual machines (VMs) and host systems in virtualized environments. VirtioFS is an extension of the Virtio standard specifically crafted for file system sharing between VMs and the host. This is particularly beneficial in scenarios where seamless access to shared files and data between VMs and the host is essential. VirtioFS has been widely adopted in virtualization technologies such as QEMU and Kata Container. Apache OpenDAL is a data access layer that allows users to easily and efficiently retrieve data from various storage services in a unified manner. In this project, our goal is to reference virtiofsd (a standard vhost-user backend, a pure Rust implementation of VirtioFS based on the local file system) and implement VirtioFS based on OpenDAL. Through this project, VMs can access numerous data services through the file system interface with the assistance of the OpenDAL service daemon deployed on the host, all without their awareness. It ensures the efficiency of file system reading and writing in VMs through VirtioFS support. This storage-system-as-a-service approach conceals the details of the distributed storage system from VMs. This ensures the security of storage services, as VMs do not need to be aware of the information, configuration and permission credentials of the accessed storage service. Additionally, it enables the utilization of a new backend storage system without reconfiguring all VMs.
<h4>Cross-language analysis of U.S.-Russian relations (Task 3)</h4> <p>Tweets from US democrats (or just anyone actively opposing Trump's presidency) and Russian conservators (or anyone supporting government) are collected and brought to a common denominator via translation-based and non-translation cross-lingual methods. Resulting corpus would be fascinating to research through several perspectives: for example get the political views through speech analysis, comparison of similarities in the vocabulary between people of similar and different political views, etc. Information can be retrieved through the Twitter API (Search or Stream, using Tweepy library).</p> <h4>Early Alzheimer syndrome detection in speech analysis (Task 9)</h4> <p>Research showed that it is possible to detect early signs of Alzheimer Syndrome in speech. I propose to train a model, which will learn to do it (and later make an app, assisting people with the high risk of Alzheimer). Data can be extracted from the Talk Bank (<a href="https://dementia.talkbank.org/" target="_blank">DementiaBank</a>) or, for example, <a href="https://dementiadiaries.org/" target="_blank">Dementia Diaries</a> website. The app could prompt their users to talk about their day and using speech recognition module could analyze the possibility of Alzheimer and changes overtime.</p>
Cartography currently does not ingest many of the AWS resource types used in popular CloudGoat attack/detection scenarios. This mentorship project will extend Cartography’s AWS plugin and schema to cover these missing resources, enabling security practitioners to visualize and query full CloudGoat labs end‑to‑end. The mentee will: i. Audit the AWS resource types used across selected CloudGoat scenarios. ii. Update Cartography’s schema to include each resource, with appropriate labels and key properties. iii. Implement ingestion functions in the AWS plugin, including relationship discovery (e.g., linking log groups to CloudWatch alarms). iv. Add Cypher sample queries and Python examples to the docs demonstrating how to explore one's infrastructure. Expected Outcome: 1) Support for the full list of AWS resources used in CloudGoat (e.g. SSM parameters, CodeBuild projects, CloudWatch metrics/alarms, SNS topics/subscriptions, ECS/EFS resources, Glue jobs, API Gateway, Cognito, Secrets Manager, etc.). a. Full list in the linked issue 2) Automated test coverage for each new resource type. 3) Updated documentation and example notebooks showing end‑to‑end CloudGoat use cases with Cartography.
This project aims to add brain imaging data structure (BIDS) provenance to a workflow engine written in Python called ‘Pydra’. The brain imaging data structure format is a widely-adopted framework for disseminating clean datasets for use in the reproducibility of neuroimaging data analyses (https://bids.neuroimaging.io/). This project would aid in this pursuit by establishing built-in support for the BIDS format within the Pydra software package. Pydra is a library that allows complete control of the command line through Python (e.g., within a Jupyter Notebook). The majority of brain imaging data is analyzed using many commands that operate in a serial manner for cleaning, aligning, and applying statistical models to the data often in batches. Rather than relying on shell scripting and manual documentation of software versions, commands used, and outputs that are generated, Pydra can do so automatically. Pydra not only allows commands to be run through Python that would normally be run within the command line, but also unlocks the ability to interface with any CLI binaries a user might have installed as third party tools. Beyond this, Pydra allows the development of ‘workflows’ or stepwise processing pipelines with traceable software and command provenance, allowing an individual to essentially run an exact analysis in a “frozen” environment that the original publisher/researcher/scientist used themselves.
<p>Enhancing the FOSSAsia Open Event Template to add new functionalities like</p> <ol> <li>Fixing app specific bugs (Random Force Close and similar errors), optimize app Performance, and Stabilization. </li> <li>Android Wear support by allowing the user to receive notification for the events he has bookmarked on his smartwatch and get the driving directions to the event. </li> <li>Enhancing the Map Activity by displaying all the sub events and allowing the user to navigate to the event from the app itself.The map will also show locations of nearby hotels and Airports. </li> <li>Adding features like ability to mark the attendance and rate the session. </li> <li>Enhancing the general UI/UX of the app by redesigning various parts of the app by following material guidelines and optimizing the UI for tablets. </li> <li>Adding an option to display recent G+/Twitter posts by the Speaker and the Organization, Session images and also the reviews given to an event by the attendees. </li> <li>Generate the apk without using Android Studio by adding an option in the app which asks for API URL, App name and icon and then generates a signed .apk. This can also be done using a web-app that uses the build-bot for generating the app.</li> </ol>
<p>The Open Event project has SIX components:</p> <ul> <li>The Open Event Format Definition</li> <li>The Open Event Server</li> <li>The Open Event Generic Android App and It's Generator</li> <li>The Open Event Web App Generator</li> <li>The Open Event Organiser App</li> <li>The Open Event Frontend</li> </ul> <p>All the components support organizers in all stages from event planning to publishing, marketing and ticket sales for all kinds of events including concerts, conferences, summits and regular meetups.. Automated web and mobile apps help organizers in creating event web pages and apps without any investment or knowledge of development. This also helps attendees to get information easily.</p> <p>This proposal focuses on the <strong>Open Event Server, the Organizer App, and the Frontend</strong> for the summer.</p> <p>For the Open Event Server, remaining important features will be added in order to make it feature complete. These features would then be implemented in the Frontend and the Organizer App.</p> <p>The Organizer App's architecture will be revamped from MVP to MVVM. And new features from the server will be implemented while using reactive programming, dependency injection, and other modern standard libraries.</p>
<p>Our objective is to determine the best architectural and parallelization options for the BLonD future C++ code base. Project includes:</p> <ul> <li>Existing simulations performance profile data and component interaction diagrams.</li> <li>Micro benchmark data selection for regional stress testing that can reveal of currently existing architectural pitfalls.</li> <li>Prototypes for potential architecture evolution that are exclusively designed for BLonD performance optimization covering wide amount of task and data parallelization technics: from local SMID optimizations and coprocessor kernels to cluster technics.</li> </ul> <p>Main project deliverable will be a report covering possible architecture directions rooted in profile data, performance tests and future possibilities. This report will include UML diagrams showing architectural blueprints for concurrency and parallelism directions, structured performance analysis of performed tests and created prototypes, a table comparing selected technologies in terms of:</p> <ul> <li>Top available simulation scale.</li> <li>Integration into current architectural model.</li> <li>Prototype testing results.</li> <li>Profiling tools.</li> <li>Publically available information and documentation.</li> <li>Hardware requirements.</li> </ul>
MoFA agents currently operate as "black boxes" in isolation—they lack shared memory, structured handoff protocols, and cross-agent coordination. When a multi-agent swarm fails, there is no single distributed trace to follow and no system-wide intelligence to explain why. This proposal transforms MoFA from a collection of individual agents into a "Cognitive Ecosystem" by implementing a symbiotic coordination-and-observability layer. Building on the OTLP+Prometheus pipeline with a 336x performance gain and the core coordination traits I designed (PR #997), this project delivers: (1) An AgentHub Coordination layer featuring InMemoryVectorStore for semantic memory and ChannelHandoffProtocol for reliable task delegation; (2) A zero-copy EventRecord Bridge using tokio::broadcast to fan out state mutations; (3) An Observatory Intelligence Engine featuring a petgraph-powered Knowledge Graph for live topology mapping and a Z-Score Statistical Anomaly Detector for identifying rogue agent behavior (token burn, latency spikes). The result is a production-grade "Nervous System" for MoFA where every agent interaction is first-class, observable, and governed. Key metrics include: Zero-drop event propagation at 4000 EPS, <50ms graph query latency, 80%+ unit test coverage, and a full W3C TraceContext implementation for cross-agent waterfall visualization.
This proposal aims to describe how to add inlay hints support to the Haskell language server. Inlay hints can provide a more fancy, intuitive, and convenient ui view of the current state of the code, such as the fixity of operators, the type of bound symbols in `let`, the type of holes, etc. Some basic work already exists in the current HLS that makes it feasible to implement inlay hints, such as the basic type library already in use: https://github.com/haskell/lsp; and the hls plugin system. Prior to submitting this proposal, I had already started working on trying to make some implementation work, and had made some progress. I submitted a draft pull request (https://github.com/haskell/haskell-language-server/pull/4131) to hls's github repository, which lists some todo's, but it should be noted that there is more to this proposal than just the pr's, and any suitable information that can be presented with the help of inlay hints will be included in the work. Since the ability to configure inlay hints is already in the todo, even if inlay hints that are too informative are implemented, they will not be a bother to the user: the user has the ability to configure the information that inlay hints will display. In the body of the proposal, I detailed the timeline and details for implementing the idea. I'll continue to build on the progress of this pull request, gradually implementing more inlay hints usages and important configuration capabilities.
Meshery is the open-source cloud native manager that empowers platform engineers to design and operate infrastructure. As infrastructure complexity grows, the need for intelligent assistance becomes critical. This project focuses on developing and enhancing a dedicated AI Adapter and AI Connections for Meshery. This adapter serves as the bridge between Meshery’s core orchestration engine and various Large Language Models (LLMs). The goal is to enable "Natural Language to Infrastructure" capabilities, allowing users to describe their architectural intent (e.g., "Deploy a highly available Kubernetes cluster on AWS with Prometheus monitoring") and have Meshery auto-generate the visual topology and configuration manifests. The intern will work on decoupling the AI logic from the core platform, allowing users to "Bring Your Own Model" (BYOM)—supporting both cloud-based providers (OpenAI, Anthropic) and local inference runners (Ollama, LocalAI). Expected Outcome: 1. A fully functional AI Adapter (or Connection) integrated into the Meshery ecosystem. 2. Demonstrable capability for users to swap between at least two different LLM providers (e.g., OpenAI vs. a local Llama 3 model). 3. Implementation of a feature where natural language queries result in a rendered design. 4. Merged pull requests (PRs) including code, tests, and documentation.
Switching to Conscrypt, simulating the security APIs becomes much more high-fidelity and it achieves the goal of Robolectric to make it similar to an Android environment. Currently, Robolectric uses BouncyCastle as the Java Cryptography Extension (JCE) security provider. Starting in Android P, Android switched to using Google Conscrypt as the security provider. To be more consistent with Android, Robolectric should update the default security provider to Conscrypt. As it is using the BouncyCastle, this means that whenever the JCA APIs are used in a Robolecetric test, BouncyCastle will be used by default. Officially, In Android the default JCE provider is Conscrypt. This is a Java wrapper over BoringSSL. The goal is to have Robolectric switch from BouncyCastle by default to Conscrypt. The Conscrypt module uses BoringSSL, a native library that is a Google fork of OpenSSL and which is used in many Google products like Google Chrome for cryptography and TLS. Conscrypt uses Java code and a native library to provide the Android TLS implementation as well as a large portion of Android cryptographic functionality such as key generators, ciphers, and message digests. Conscrypt is relatively selective and focuses on the most important and widely-used algorithms. Conscrypt also supports the curves in Elliptic Curves crypto operations and it is much faster than BouncyCastle as it is optimized native code. But BoringSSL doesn't have official releases and makes no guarantees around API or ABI stability.
The goal of this project is to make the Rust language available on the GNU/Hurd operating system. Currently, there is no official Rust support for GNU/Hurd, which limits developers' ability to build high-performance, safe, and concurrent software on this platform. The Rust language is increasingly being used in fundamental libraries such as librsvg and python-cryptography, so it is crucial to have a compiler for Rust on GNU/Hurd. The Rust compiler is portable, but its runtime library, libstd, needs to be ported to GNU/Hurd. This involves telling Rust how to call standard C library functions, which can be generated from libc C headers using the bindgen tool. The proposed solution involves creating a new Rust target for GNU/Hurd by investigating the system calls and interfaces available in GNU/Hurd and adapting Rust's code generator to generate code that uses these interfaces. The project aims to optimize Rust's performance on the GNU/Hurd platform by identifying performance bottlenecks and implementing improvements where necessary. The deliverables of the project include the Rust-GNU/Hurd toolchain, which comprises the Rust compiler and libraries, documentation, and optimized performance of Rust on the GNU/Hurd platform. The project also includes researching the GNU/Hurd system, identifying the system calls and interfaces that Rust will need to use, and creating documentation for the Rust-GNU/Hurd toolchain.
This project addresses the issue of translating complex marine biodiversity data into actionable knowledge for ecosystem management in Florida. It makes use of existing biodiversity datasets (OBIS, GBIF) and ecosystem variables (e.g., temperature) to develop a collection of reproducible Jupyter Notebooks powered by Python packages like pyOBIS, GeoPandas, and machine learning packages. These notebooks are dedicated to showcasing the top environmental inquiries in areas like the Florida Keys, Rookery Bay, Tampa Bay, and the Gulf of Mexico covering trends in Rice's Whale, birds, and seagrasses. The solution combines species occurrence records and ecosystem information to generate visualizations, spatial models, and biodiversity metrics. Interactive maps, temporal trend plots, and model-based habitat predictions are products. Constructed with reproducibility and open science principles in mind, the tools will assist resource managers, researchers, and decision-makers in conservation planning. Deliverables include: 5 modular Jupyter Notebooks (e.g., habitat models, trend predictions), Reusable data pipeline functions (data ingestion, cleaning, analysis), Public Docker-supported GitHub repository, Easy-to-read documentation and automated testing framework. The project facilitates environmental decision-making through data science and encourages collaboration through open, reproducible tools.
<p>The main goal of this year's GSoC was to develop <a href="https://github.com/fossasia/badgeyay" target="_blank"><strong>Badgeyay</strong></a> into a complete Service with services ranging from simple to complex functionalities which include :</p> <ul> <li>Modularizing the API and follow the best standards.</li> <li>Improving the Rest API and Resolving the known bugs.</li> <li>Improving current UI of Badgeyay and changing it along with GSoC Period by Using Ember JS and Semantic UI.</li> <li>Improving the Badge Layout and provide more features to the user. </li> <li>Implementing User Authentication and Integrating database management system into Badgeyay. </li> <li>Implementing a Badge Management System.</li> <li>Implementing Admin Panel.</li> </ul> <p>Tech Stack:</p> <p>The whole front end is shifted to Flask template to MVC frontend framework Ember JS. Everything in the frontend is divided into components and chaining of actions and models have been implemented. Semantic UI is used for styling purposes.</p> <p>The whole API is redesigned to follow JSON API specification using the marshmallow to make it compatible with data coming from Frontend. Firebase is also used to support admin and authentication functionalities from the backend flask server.</p>
<p>R provides two types of regular expressions in <code>base</code> package, extended regular expressions (the default) with TRE and Perl-like regular expressions used by <code>perl = TRUE</code> with PCRE.</p> <p>PCRE includes useful features, such as named capture, but it uses a backtracking algorithm, so it is easy to take exponential time or arbitrary stack depth for certain regular expressions. Using PCRE in the service backend would have left it open to easy denial of service attacks.</p> <p>TRE has a polynomial time complexity but does not include named capture.</p> <p><code>stringi</code> is a R package use the regular expression engine from the ICU library, which has an exponential time complexity. The <code>stringi</code> package does not support named capture yet because it is still considered as experimental in ICU.</p> <p>RE2 is a primarily DFA based regular expression engine from Google that is fast at matching large amounts of text with named capture. Users can build fast and scalable service backend with RE2 library.</p> <p>This project will create an R package interface to the RE2 library, providing the R community with the first regular expression package with both named capture and polynomial time complexity.</p>
The proposal aims to develop an innovative, accessible mobile application to address the specific challenges faced by visually impaired students in their learning process. The app goes beyond traditional resources by utilising sound, touch, device sensors, and interactive elements to create a multi-sensory learning experience. This approach aims to improve engagement, understanding, and retention of key mathematical concepts. The proposal highlights my strong interest in accessibility software solutions, a relevant background in Android development, and a desire to use technology to make a positive social impact. Through my research, I have demonstrated the use of existing accessibility tools and outlined a comprehensive project plan that includes: 1.)Interactive modules: Lessons on basic arithmetic, cardinal directions, trigonometry, geometry, metric systems, and more. The modules thoughtfully leverage device features like magnetometers, gyroscopes, and accelerometers. 2.)Story-based learning: A story mode with auto-generated MCQs potentially using TensorFlow Lite for comprehension and assessment. 3.)Accessibility focus: Thorough consideration of screen reader compatibility, audio and haptic feedback, and support for Braille displays and switch access. 4.)Iterative development: A detailed timeline with a community bonding period, regular milestones, testing, and a phase for incorporating user feedback. The idea of this proposal aligns closely with Zendalona's mission.
<p>The Wayback Machine Extension is a powerful tool that collects and stores information about the search queries you make and the web pages you view to provide you with information about those pages and to help the Wayback Machine archive the Web. Driven by a powerful idea and an enthusiastic team, this extension has successfully been archiving the internet since 2017. The Wayback Machine Extension plays a significant role in providing people a way to archive and preserve the publicly available web pages and mapping the evolution of the World Wide Web.</p> <h4>This Project focused on Improving the Wayback Machine Extension by:</h4> <ol> <li>Enhancing the existing Search Box feature.</li> <li>Adding 'Fact Check' feature</li> <li>Adding 'Bulk Save' feature</li> <li>Re-defining the display of existing Contexts</li> <li>More enhancements:<ul> <li>Solving the existing issues to ensure full functionality</li> <li>Code optimization and improvement</li> <li>UI improvements</li> <li>Searching, inspecting and fixing bugs</li> <li>Interacting with users about issues and opportunities to make the app better</li> <li>Writing Tests</li> <li>Adding support for Edge</li> <li>Making the Internet a BETTER place to surf.</li> </ul> </li> </ol>
Kgateway can be used as an “AI Gateway” that allows applying traditional traffic management, security, and resiliency policies when reaching out to LLM providers. It also allows sending a request to another server for processing things like prompt guards or enrichment before we send it off to the LLM providers. An important aspect in any system that has lots of moving parts is observability: the collection of metrics and other information that allow you to identify issues and troubleshoot a live system. This project aims to enable OpenTelemetry support in kgateway’s AI extensions by allowing users to configure a gRPC tracing collector. This feature enables span propagation from the AI extensions extproc server and exporting traces to an OpenTelemetry-compatible backend (e.g., OpenTelemetry Collector, Jaeger, Zipkin, or Datadog). This feature will build on Envoy’s native tracing capabilities and aligns with industry-standard observability practices. This will make it easier to debug, monitor, and optimize traffic flowing to LLM Providers through kgateway. Expected Outcome: 1. Design and implement an API to enable tracing for the kgateway’s AI extproc extension. 2. Extend the AI extensions extproc server with OpenTelemetry tracing. 3. Create end-to-end (e2e) tests to validate configuration and trace propagation. 4. Write documentation for plugin developers and end users.....
OpenTRIM is a C++ Monte Carlo simulation framework that models the interaction of ions with matter, tracking energy deposition and defect creation. Currently, it includes a fixed tallying system for recording standard outputs, such as energy lost to ionization or defects. This project aims to extend OpenTRIM's capabilities by implementing a flexible, user-customizable tally system. The new tally system will allow users to define, via JSON configuration, what simulation events to track (e.g., ion stopping, vacancy creation), how to bin data (e.g., in cylindrical or Cartesian coordinates), and what physical quantities to record (e.g., ion depth, deposited energy). It will be implemented as a new class hierarchy in C++, inheriting from the existing tally class, and will make use of the ArrayND data structure for multidimensional data storage. Deliverables include: a) A customizable tally class with support for user-defined event handling b)JSON-configurable tally setup (geometry, energy bins, spatial bins, etc.) c) Sample tally implementations (e.g., ion range profiling) d) Unit tests, documentation, and tutorials for extending the system This work will empower researchers and developers to tailor OpenTRIM output to their specific simulation needs, improving its usability and scientific value.
Currently, the Cytoscape App Store only supports plugins for the Cytoscape Desktop App. Since a web version of Cytoscape is available, web plugins and service apps can add functionality, similar to the desktop plugins. With multiple platforms, a unified app registry would be ideal in organizing plugins and extensions, with layered filtering capabilities (e.g. platform type, app type). To solve this problem, the proposal includes an implementation plan on frontend UI changes and filtering, database migrations, an updated submission and approval flow for both web apps and service apps, and health monitoring for all apps. The first 3-4 weeks will be spent discussing final changes with mentors, with database migrations to accomodate the new platform types. The frontend will also receive changes including filtering, new tags and categories. Weeks 5 and 6 will follow a similar process for web service apps. Weeks 7-10 will consist of adjusting the submission workflow, including frontend UI changes for developers and database migrations. Health checks will also be implemented, with certain criteria to determine the health status of an app. Weeks 11-12 will consist of unit testing, including health check testing, testing new uploads, latency checks and documentation.
This project addresses the critical challenge of GPU resource management in ML/AI research environments where researchers often face delays due to inefficient resource allocation. I'll develop a comprehensive CPU-based control plane that efficiently orchestrates GPU resources through four key components: an advanced job scheduler with priority management and preemption capabilities, a comprehensive observability platform with real-time dashboards, a streamlined model deployment pipeline with CI/CD integration, and robust infrastructure automation. By implementing technologies like Slurm for scheduling, Prometheus/Grafana for monitoring, Terraform/Ansible for infrastructure automation, and integrating ML-specific tools like MLflow and NVIDIA Triton, the system will deliver significant benefits to researchers: reduced wait times for GPU access, transparent visibility into resource availability, priority access for time-sensitive research, and a seamless deployment pipeline from training to serving. Deliverables include a functioning scheduler with priority queue support, a comprehensive monitoring system with custom dashboards, infrastructure-as-code modules, a model deployment pipeline with CI/CD integration, and an intelligent alerting system. The complete solution will serve as a reference implementation for academic GPU cluster management, providing reusable components and best practices for similar infrastructure requirements in the ML research community.
Currently, in OpenYurt, the core component YurtHub—which acts as a transparent proxy between edge node system components (e.g., kubelet, CNI, CoreDNS, kube-proxy) and the Kubernetes API server—is deployed as a systemd service on each edge node. The installation is performed exclusively via the community-provided tool YurtAdm during node joining. This approach imposes a significant limitation: users must use YurtAdm to onboard nodes, making it impossible to install YurtHub on existing Kubernetes nodes that were not initially provisioned with YurtAdm. To improve flexibility and user experience, the community aims to support a label-driven, declarative installation mechanism: 1. When a specific label (e.g., openyurt.io/is-edge-worker=true) is added to a node, YurtHub should be automatically installed and started on that node. 2. Conversely, when the label is removed, YurtHub should be gracefully uninstalled and its resources cleaned up. This enhancement will enable seamless integration of OpenYurt into existing Kubernetes clusters without requiring re-onboarding of nodes. Expected Outcome: 1. Design and implement a controller/operator that watches for node labels and triggers YurtHub lifecycle operations. 2. Develop an installation/uninstallation mechanism that: a. Installs YurtHub as a systemd service. b. Ensures idempotency and handles failures gracefully. c. Cleans up all YurtHub-related files, configurations, and services