With many Proof of Concepts (PoCs) going on for SUSE Cloud, the development team has observed that we have no clear path on how Sales Engineers (SEs) and sometimes dedicated support engineers (xSE) can receive technical support to successfully complete the projects, often leading to escalation calls and even firefighting on-site visits by developers. Goal of that project is to come up with a best practice guide and to eventually set expectations on what's possible from a development point of view. Results should be documented in a central internal location and announced to all relevant parties.
This project is part of:
Hack Week 11
Activity
Comments
Be the first to comment!
Similar Projects
Introducing "Bottles": A Proof of Concept for Multi-Version CRD Management in Kubernetes by aruiz
Description
As we delve deeper into the complexities of managing multiple CRD versions within a single Kubernetes cluster, I want to introduce "Bottles" - a proof of concept that aims to address these challenges.
Bottles propose a novel approach to isolating and deploying different CRD versions in a self-contained environment. This would allow for greater flexibility and efficiency in managing diverse workloads.
Goals
- Evaluate Feasibility: determine if this approach is technically viable, as well as identifying possible obstacles and limitations.
- Reuse existing technology: leverage existing products whenever possible, e.g. build on top of Kubewarden as admission controller.
- Focus on Rancher's use case: the ultimate goal is to be able to use this approach to solve Rancher users' needs.
Resources
Core concepts:
- ConfigMaps: Bottles could be defined and configured using ConfigMaps.
- Admission Controller: An admission controller will detect "bootled" CRDs being installed and replace the resource name used to store them.
- Aggregated API Server: By analyzing the author of a request, the aggregated API server will determine the correct bottle and route the request accordingly, making it transparent for the user.
Mortgage Plan Analyzer by RMestre
Project Description
Many people face challenges when trying to renegotiate their mortgages with different banks. They receive offers from multiple lenders and struggle to compare them effectively. Each proposal may have slightly different terms and data presentation, making it hard to make informed decisions. Additionally, understanding the impact of various taxes and variables can be complex. The Mortgage Plan Analyzer project aims to address these issues.
Project Overview:
The Mortgage Plan Analyzer is a web-based tool built using PHP, Laravel, Livewire, and AdminLTE/bootstrap. It provides a user-friendly platform for individuals to input basic specifications about their mortgage, adjust taxes and variables, and obtain short-term projections for each proposal. Users can also compare multiple mortgage offers side by side, enabling them to make informed decisions about their mortgage renegotiation.
Why Start This Project:
I found myself in this position and most tools I found around are either for marketing/selling purposes or not flexible enough. As i was starting getting lost in a jungle of spreadsheets i thought I could just create a tool to help me and others that may be experiencing the same struggles to provide clarity and transparency in the decision-making process.
Goals for Hackweek 24
- Improve the general behaviour of the forms:
- * Delay calculations after input change;
- * Allow to copy from a specific simulation;
- Improve the comparison graphs: Instead of having 4 graphs, maybe have it all in one.
- Support multi languages
Result of Hackweek 23
- Developed a base site that:
- * Allows adding up to 3 simulations;
- * Create financial plans;
- * Simulations comparison graph for the first 4 years;
- Created Github project @ https://github.com/rjpmestre/mortgage-plan-analyzer
- Launched a demo instance using Oracle Cloud Free Tier currently @ http://138.3.251.182/
Goal for Hackweek 23
By the end of the week, I'm planning to have a basic web application with the following features:
- User-friendly interface for inputting mortgage specifications like the loan amount, term, fixed and variable terms taxes.
- Display of financial plan
- Ability to adjust taxes and variables to see their impact on financial plan.
- Aesthetically pleasing output using AdminLTE/bootstrap for a pleasant and intuitive user experience.
Resources
- Banco de Portugal: Main simulator all portuguese banks have to follow ( https://clientebancario.bportugal.pt/credito-habitacao )
- Laravel: A PHP web application framework for building robust and scalable applications. ( https://laravel.com/ )
- Livewire: A Laravel library for building dynamic interfaces without writing JavaScript. ( https://livewire.laravel.com/ )
- AdminLTE: A responsive admin dashboard template for creating a visually appealing interface. ( https://adminlte.io/ )
- GitHub: We will host the project on GitHub for version control and collaboration. ( bet you didn't know this one, https://github.com/ )
- Vercel ( https://vercel.com/ ) or Oracle Cloud ( https://www.oracle.com/cloud/free/ ): Consideration will be given to hosting a running instance of the application using Vercel or Oracle Cloud's free tier, ensuring accessibility and availability.
This will be my first collaborative project in github. I'm pretty confident about setting up the bases of the project and financial math around it but i'll probably need some help:
- supporting multi language ( if i have to pick only one language, probably will choose Portuguese as this will for sure fit their needs and i'm more comfortable with Portuguese financial slang)
- setting up the running instance (as i'm not familiar neither with vercel nor oracle cloud services)
Save pytorch models in OCI registries by jguilhermevanz
Description
A prerequisite for running applications in a cloud environment is the presence of a container registry. Another common scenario is users performing machine learning workloads in such environments. However, these types of workloads require dedicated infrastructure to run properly. We can leverage these two facts to help users save resources by storing their machine learning models in OCI registries, similar to how we handle some WebAssembly modules. This approach will save users the resources typically required for a machine learning model repository for the applications they need to run.
Goals
Allow PyTorch users to save and load machine learning models in OCI registries.
Resources
Impove Tracking Milestone Quality by rtsvetkov
Description
We need to track better the milestone quality.
Goals
Propose a transparent process for managing the Milestone-relevant bugs in Bugzilla. - Transparency on the delivery - Clear current Responsibility - Clear TPM responsibility - Clear current assignee
Resources
No special resources Bugzilla,
Questions to answer:
What is the best way to track the responsibilities on the tickets, including those of the technical project managers, developers, and subject matter experts?
ghostwrAIter - a local AI assisted tool for helping with support cases by paolodepa
Description
This project is meant to fight the loneliness of the support team members, providing them an AI assistant (hopefully) capable of scraping supportconfigs in a RAG fashion, trying to answer specific questions.
Goals
- Setup an Ollama backend, spinning one (or more??) code-focused LLMs selected by license, performance and quality of the results between:
- deepseek-coder-v2
- dolphin-mistral
- starcoder2
- (...others??)
- Setup a Web UI for it, choosing an easily extensible and customizable option between:
- Extend the solution in order to be able to:
- Add ZIU/Concord shared folders to its RAG context
- Add BZ cases, splitted in comments to its RAG context
- A plus would be to login using the IDP portal to ghostwrAIter itself and use the same credentials to query BZ
- Add specific packages picking them from IBS repos
- A plus would be to login using the IDP portal to ghostwrAIter itself and use the same credentials to query IBS
- A plus would be to desume the packages of interest and the right channel and version to be picked from the added BZ cases