|
| 1 | +--- |
| 2 | +title: Week 13 |
| 3 | +author: Muhammad Salman |
| 4 | +author_url: https://github.com/SalmanDeveloperz |
| 5 | +tags: [gsoc25, scheduler, infrastructure, devops] |
| 6 | +--- |
| 7 | + |
| 8 | +<!-- |
| 9 | +SPDX-License-Identifier: CC-BY-SA-4.0 |
| 10 | +
|
| 11 | +SPDX-FileCopyright Text: 2025 Muhammad Salman <[email protected]> |
| 12 | +--> |
| 13 | + |
| 14 | +# Week 13 |
| 15 | + |
| 16 | +*(August 26, 2025 – September 01, 2025)* |
| 17 | + |
| 18 | +## Work Done |
| 19 | +- Reviewed **Scheduler functionality** in both setups: |
| 20 | + - Rebased and partially ran the Scheduler from **Omar’s previous setup**. |
| 21 | + - Started testing the Scheduler in the **new setup** with the latest branch as per decided with [Avinal](https://github.com/avinal). |
| 22 | +- Analyzed the **services, logs, and configuration flows** from the old setup and attempted to configure them similarly in the new setup. |
| 23 | +- Discovered that the **latest master branch** introduced changes: |
| 24 | + - Database migration issues. |
| 25 | + - Agent-related errors. |
| 26 | + - These prevent the Scheduler from running properly. |
| 27 | +- Continued working on the **Final Evaluation Documentation**, writing down: |
| 28 | + - Steps we tried. |
| 29 | + - Issues discovered. |
| 30 | + - Comparisons between setups. |
| 31 | + |
| 32 | +All changes are pushed to Omar’s forked repository under the following branch: |
| 33 | + |
| 34 | +* https://github.com/SalmanDeveloperz/fossology/tree/OmarAbdelSamea/GSoC/Microservices |
| 35 | + |
| 36 | +The associated commit can be viewed here: |
| 37 | + |
| 38 | +* https://github.com/SalmanDeveloperz/fossology/commit/4fd4787936081c0c8db7df8e40d57e76e123a51a |
| 39 | +--- |
| 40 | + |
| 41 | +## Meeting 1: |
| 42 | + |
| 43 | +*(August 27, 2025)* |
| 44 | + |
| 45 | +Meeting was missed because [Avinal](https://github.com/avinal) was unavailable (he was away from home). He asked me to prepare a document outlining the issues we have discovered so far and send it to them for feedback. |
| 46 | + |
| 47 | +## Meeting 2: |
| 48 | + |
| 49 | +*(August 28, 2025)* |
| 50 | + |
| 51 | +I presented my progress (detailed above) and explained the challenges with Scheduler, database migrations and agents in current state of infrastructure. |
| 52 | + |
| 53 | + |
| 54 | +## Challenges |
| 55 | +- Major differences between **previous setup vs. latest branch** made Scheduler migration harder. |
| 56 | +- **Database and agent issues** are blockers preventing smooth execution. |
| 57 | +- Need more time to design and implement a stable solution. |
| 58 | + |
| 59 | +## Next Steps |
| 60 | +Although the GSoC timeline has ended, I plan to: |
| 61 | +- Continue contributing to **FOSSology Microservices Infrastructure**. |
| 62 | +- Focus on solving the **Scheduler migration challenges**. |
| 63 | +- Work on **database migration and agent issues**. |
| 64 | +- Improve and refine **documentation** for new contributors. |
| 65 | +- Collaborate with the community to **design and implement** the pending parts of the project after critical evaluation. |
| 66 | + |
| 67 | +--- |
| 68 | +## Final Note |
| 69 | +While this report concludes my **official GSoC period**, it does not conclude my journey with **FOSSology**. |
| 70 | +The Microservices Infrastructure project is critical and still has a long way to go. I am fully determined to **keep contributing**, **improving** and **finishing what was started**. |
| 71 | + |
| 72 | +This is just the **end of GSoC**, not the end of my contributions 🚀. |
0 commit comments