You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MLStacks framework notionally supports feature stores but lacks an explicit deployment option for Feast, a popular feature store for machine learning. This task involves integrating Feast as a ComponentFlavorEnum within MLStacks and implementing its deployment via Terraform.
Task Description
To enhance MLStacks' feature store capabilities, this task aims to add Feast as a deployable feature store option. This requires updating enums and constants to recognize Feast as a component flavor and creating a Terraform module for deploying Feast on Kubernetes clusters, guided by the Feast repository's Terraform configuration.
Expected Outcome
The ComponentFlavorEnum in src/mlstacks/enums.py includes Feast as an option for feature store components.
src/mlstacks/constants.py is updated to support feature_store as a stack component type, with feast as a permitted flavor.
A Terraform module for deploying Feast on cloud providers (AWS, Azure, and GCP) is developed and integrated into MLStacks.
The deployment process is tested on the implemented cloud providers to ensure Feast operates correctly within the MLStacks framework.
Steps to Implement
Update src/mlstacks/enums.py to add feast to the ComponentFlavorEnum for feature stores.
Modify src/mlstacks/constants.py to recognize feature_store as a stack component and include feast as an available flavor.
Develop a Terraform module for deploying Feast on Kubernetes, referencing the Feast Terraform guide for best practices and configurations.
Ensure the Terraform module supports deployment across AWS, Azure, and GCP, with configurations and resources appropriately tailored for each cloud provider.
Conduct comprehensive testing on each cloud provider to verify that the Feast deployment functions as expected and integrates smoothly with MLStacks.
Document the deployment process, configuration options, and any provider-specific considerations for users looking to deploy Feast as part of their MLStacks setup.
Additional Context
By incorporating Feast as a feature store deployment option, MLStacks will significantly enhance its data management capabilities, offering users a robust and scalable solution for managing features in machine learning workflows.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@strickvl Updates on the implementation:
Made changes to the constants and enums file to recognize feature_store as a stack component and include feast as an available flavor.
Currently working on developing the Terraform module.
MLStacks framework notionally supports feature stores but lacks an explicit deployment option for Feast, a popular feature store for machine learning. This task involves integrating Feast as a
ComponentFlavorEnum
within MLStacks and implementing its deployment via Terraform.Task Description
To enhance MLStacks' feature store capabilities, this task aims to add Feast as a deployable feature store option. This requires updating enums and constants to recognize Feast as a component flavor and creating a Terraform module for deploying Feast on Kubernetes clusters, guided by the Feast repository's Terraform configuration.
Expected Outcome
ComponentFlavorEnum
insrc/mlstacks/enums.py
includes Feast as an option for feature store components.src/mlstacks/constants.py
is updated to supportfeature_store
as a stack component type, withfeast
as a permitted flavor.Steps to Implement
src/mlstacks/enums.py
to addfeast
to theComponentFlavorEnum
for feature stores.src/mlstacks/constants.py
to recognizefeature_store
as a stack component and includefeast
as an available flavor.Additional Context
By incorporating Feast as a feature store deployment option, MLStacks will significantly enhance its data management capabilities, offering users a robust and scalable solution for managing features in machine learning workflows.
Code of Conduct
The text was updated successfully, but these errors were encountered: