[GSoC] Provide a PyTorch MNIST Example for Push-based Metrics Collection

[Electronic-Waste]

What this PR does / why we need it:

Provide a Pytorch MNIST example for push-based metrics collection.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Checklist:

• Docs included if any changes are user facing

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andreyvelich for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[tenzen-y]

@Electronic-Waste Could we implement CI powered by papermill first in a separate PR?

[Electronic-Waste]

It seems that #2417 mentioned it and has already been taken by someone. I'll ask the assignee about the progess. And if he doesn't have time, I would be glad to take it :)

Please let me know your thoughts. cc @tenzen-y @andreyvelich

[tenzen-y]

It seems that #2417 mentioned it and has already been taken by someone. I'll ask the assignee about the progess. And if he doesn't have time, I would be glad to take it :)

Please let me know your thoughts. cc @tenzen-y @andreyvelich

As Andrey mentioned in the issue, we are working on it at the traininig-operator, first.
So, let us come back here after the papermill implementation is completed in the training operator.

[Electronic-Waste]

Yeah, I see! I'm looking forward to enhance my understanding of Training-Operator through this issue :)

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[google-oss-prow]

@Electronic-Waste: The label(s) /remove-label lifecycle/statle cannot be applied. These labels are supported: tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, lifecycle/needs-triage. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/remove-label lifecycle/statle

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.

[google-oss-prow]

@Electronic-Waste: The label(s) /remove-label lifecycle/stale cannot be applied. These labels are supported: tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, lifecycle/needs-triage. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/remove-label lifecycle/stale

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.

[Electronic-Waste]

/remove-lifecycle stale