Jiaxin Shan
Jiaxin Shan
We may build a top level orchestration at this moment so we can orchestrate the deployment by ourselves. This is on hold
Remove it from v0.2.0. Pending on model orchestration. Now, the easier way is to configure the S3 env in runtime container.. Do not let engine to handle it.
It only happens on lambda cloud, I can not reproduce it on any other clouds
@happyandslow what's the status of this story? 1. All above metrics in the issue description are all collected? 2. Did you make changes to the plot diagram? 3. is #667...
@happyandslow Any updates?
> I'm waiting for some free cycles to test these out before PR can be merged. @happyandslow Do you mean the changes has been included in #676 or in coming...
Great. We can close this issue, we can revisit #862 once it's ready.
em. introducing expectation definitely improve the complexity a lot. We use similar strategy in kubeflow training in the past. Th tricky thing is expectation package is not in the controller...
not technical issue. this can only be done after we public the repo, so we can use the registered domain
I think the initial version overall looks good to me. I would like to check whether that's helpful to make it part of the release manifest. @googs1025 @Xunzhuo @nurali-techie any...