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
As per this existing Flame workflow below for steps between #3 and #4 ( https://github.com/cisco-open/flame/blob/main/docs/01-introduction.md) , is there a way an End user (AI_ML engineer persona) can define an "SLA attribute or SLA construct" declaratively for the Controller taking the input requests and then creating the Flame cluster's worker creation process (using a pre-defined SLA). This would help federated edge cloud architectures very well where there is a $cost associated to the time it takes for #worker creation process (it could even be an Init container as well). Please find the reference architecture for such a Fed_Cloud with IP SLA parameter. Does it make sense to such a capability as a New feature in FLAME for roadmap planning ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As per this existing Flame workflow below for steps between #3 and #4 (
https://github.com/cisco-open/flame/blob/main/docs/01-introduction.md) , is there a way an End user (AI_ML engineer persona) can define an "SLA attribute or SLA construct" declaratively for the Controller taking the input requests and then creating the Flame cluster's worker creation process (using a pre-defined SLA). This would help federated edge cloud architectures very well where there is a $cost associated to the time it takes for #worker creation process (it could even be an Init container as well). Please find the reference architecture for such a Fed_Cloud with IP SLA parameter. Does it make sense to such a capability as a New feature in FLAME for roadmap planning ?
Beta Was this translation helpful? Give feedback.
All reactions