Addons Engine + Marketplace

melkodary commented 3 weeks ago

Short

Extending root-orchestrator without bloating the system and allowing users to enable features and swap out features with other ones, for instance swapping out the scheduler with a new one.

Proposal

Create a marketplace: it is responsible for hosting addons, providing a central repository where users can browse, download, and install additional features or extensions for their primary software system. This simplifies the process of extending software functionality by offering a range of third-party enhancements in a single, accessible location.

Oakestra-addons-marketplace

Addons Engine: it is designed to extend and enhance the functionality of a primary software application or ecosystem. It enables third-party developers to create and distribute additional features, tools, or services that users can install or integrate into their existing software setup. It facilitates the installation, management/monitoring of these addons. An addon engine could run on either root-orchestrator or cluster-orchestrator.

Oakestra-addons-engine

Ratio

It's necessary to have a system that is not bloated with too many features and that would make developers life hard to maintain otherwise. Also a system that is tailored more to users needs is probably a faster system, because unnecessary features are not added. Only the users needed extensions are installed. Also it provides customizability where users can swap base features with other ones, for example changing the way the scheduler works.

Impact

Depends on how it's used. If new feature will swap out another feature, then existing dependents on the new feature are affected.

Status

Implemented but needs review and further testing.

Checklist

[x] Discussed
[x] Documented
[x] Implemented
[ ] Tested

Malyuk-A commented 3 weeks ago

Is it intended that those 3 share the same name? If they are different it would be helpful to have distinct names.

melkodary commented 3 weeks ago

Is it intended that those 3 share the same name? If they are different it would be helpful to have distinct names.

Fixed! Thanks for pointing it out.

Malyuk-A commented 3 weeks ago

How are the addons_engine and addons_marketplace intended to be launched? In the code, they are separate from the root orchestrator. Is this just for now or should this be like that? For local testing should I simply build and run their dockerfiles or am I missing smth?

oakestra / oakestra