-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap 0.3 #203
Comments
It seems that these APIs in Luna engine are sufficient for 0.3 yet. In addition to providing a basic implementation, it also makes sense to make this implementation more solid and practical. |
@zojw seems working on the k8s and docker stuff, any thoughts? |
yup, I'm trying to do some investigation(learning k8s- -, write rough code, and prepare design discussion) in a local branch, the mainly direction just follow last online-meeting's idea(boostrap kernel, then kernel boostrap & monitor & scale other components...) current progress is...
[ ] still under investigation, but it seems almost workable, and I will give a detailed discussion thread when the last two items are done(maybe this weekend or early next week), we need more k8s experts to help review although there are many decisions & designs we need to take care & discuss, IMO we can finish those discussions and ship a k8s rough runnable version in v0.3, this also can help us to verify Luna engine's solid distribute running ability |
@zojw could you start a discussion thread so that we can focus on implementing deployment? You can later create an issue with concrete items by "Create issue from discussion". (Here is an example) |
As mentioned in #266 (comment), the journal API is still unstable as described in #229 and #260. Also, the binary is broken now. Do you still plan to deliver a basic implementation of Luna engine at Jan 28, 2022? Will it be a memory implementation, and used as a library only? |
I think regular releases are not suitable at the current stage for two reasons:
So I suggest that we think about that bigger picture described in #245 first. We can come back to planned releases when we have a clearer path towards that goal. #252 #263 #260 #251 are some attempts to clear the path. I think I should start a new tracking issue for Engula 2022. |
@huachaohuang totally agree! Before we have a clear picture, we can release when features are ready, i.e., a basically usable luna engine with deployment supports :) Note: please update the PR description. We can still set up targets for a 0.3 release without an explicit deadline. |
Close this in favor of #270 for now. We can open a new issue for v0.3 when we have a clear estimation of the schedule. |
Planned release date: Jan 28, 2022.
I don't have a clear plan for 0.3 yet. One possible goal is to provide a basic implementation of Luna engine. Open for discussions.
The text was updated successfully, but these errors were encountered: