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
While supporting OpenedX installations in Kubernetes, the OpenedX providers created different tooling to provide the best performance possible for the platform users. One of the key components of this tooling is a Tutor plugin (or a set of tutor plugins) that extends the Tutor capabilities for Kubernetes to get the best out of this technology when it comes to installing and maintaining a Large instance. Specific cases of this fact are:
It would be interesting to analyze the features these plugins have to offer and assess if it's worth moving features in common to the tutor-harmony plugin. I think this could ease the maintainability of such Tutor plugin features and leverage the community to run their initiatives with the best practices and tooling available. For sure, it will most likely be an opinionated layer to run instances for every provider, however, we could collaborate in the common ground we share.
The first point from the Edunext side will be listing the features offered by Drydock. We kindly invite you to share your ideas as well.
The text was updated successfully, but these errors were encountered:
While supporting OpenedX installations in Kubernetes, the OpenedX providers created different tooling to provide the best performance possible for the platform users. One of the key components of this tooling is a Tutor plugin (or a set of tutor plugins) that extends the Tutor capabilities for Kubernetes to get the best out of this technology when it comes to installing and maintaining a Large instance. Specific cases of this fact are:
It would be interesting to analyze the features these plugins have to offer and assess if it's worth moving features in common to the tutor-harmony plugin. I think this could ease the maintainability of such Tutor plugin features and leverage the community to run their initiatives with the best practices and tooling available. For sure, it will most likely be an opinionated layer to run instances for every provider, however, we could collaborate in the common ground we share.
The first point from the Edunext side will be listing the features offered by Drydock. We kindly invite you to share your ideas as well.
The text was updated successfully, but these errors were encountered: