Skip to content
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

ignore Retain field #565

Closed
hougangliu opened this issue May 20, 2019 · 8 comments
Closed

ignore Retain field #565

hougangliu opened this issue May 20, 2019 · 8 comments
Assignees

Comments

@hougangliu
Copy link
Member

in experiment.spec.trialTemplate and experiment.spec.metricsCollectorSpec, Retain filed is defined, which is used to delete worker job and metricCollecoter job when trial completed, but now we ignore the field when create new trial( Trial struct has no counterpart field of the two kind of Retain)

should we drop Retain in experiment and always delete worker job and metricCollecoter job when trial completed? or add two new field in trial.spec?

/cc @richardsliu @gaocegege @johnugeorge @YujiOshima which one do you prefer?

@gaocegege
Copy link
Member

I have a question may not be related to the issue. How to support the case that the users want to create new trials for the completed experiment? Do we plan to support it? Ref #346

@johnugeorge
Copy link
Member

johnugeorge commented May 21, 2019

We can add support for Retain in trial if needed. It should not be a big change.

@hougangliu
Copy link
Member Author

I have a question may not be related to the issue. How to support the case that the users want to create new trials for the completed experiment? Do we plan to support it? Ref #346

We need discuss it more in next meeting or in #346. Anyway, I think the feature may be not included in release 0.6

@hougangliu
Copy link
Member Author

/assign

@johnugeorge
Copy link
Member

I have a question may not be related to the issue. How to support the case that the users want to create new trials for the completed experiment? Do we plan to support it? Ref #346

Other k8s objects follow the same convention right? eg: K8s Job

@hougangliu
Copy link
Member Author

/close since #572 merged

@hougangliu
Copy link
Member Author

/close

@k8s-ci-robot
Copy link

@hougangliu: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants