implementation of mxnet operator API v1

[wackxu]

This is an exact copy of the v1beta1 APIs and controller implementation. Future API changes will be made to the v1 sub-folders.

ref #36

/assign @suleisl2000 @gaocegege

---

This change is 

[k8s-ci-robot]

Hi @wackxu. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[gaocegege]

/ok-to-test

@wackxu
Thanks for your contribution! 🎉 👍

Can you split the commits? For example, we can put generated code (client-gen, defaulter-gen) in one commit then we can review the code that hand-written by you.

[gaocegege]

Generally LGTM
/lgtm

[gaocegege]

Well I prefer adding e2e test for mxnet operator, too.

But it is not in the scope of this PR.

/cc @richardsliu

[TravisBuddy]

Travis tests have failed

Hey @wackxu,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 6b710d00-8118-11e9-b9f1-63f75d62ea26

[wackxu]

/ok-to-test

@wackxu
Thanks for your contribution!

Can you split the commits? For example, we can put generated code (client-gen, defaulter-gen) in one commit then we can review the code that hand-written by you.

Done

[wackxu]

Well I prefer adding e2e test for mxnet operator, too.

But it is not in the scope of this PR.

/cc @richardsliu

Yes, we need add e2e test and we can do this in follow pr.

[TravisBuddy]

Travis tests have failed

Hey @wackxu,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 36fbd3f0-8124-11e9-b9f1-63f75d62ea26

[wackxu]

@gaocegege The CI is green now. I think we can merge it first. And for API changes or bug fix that cherry pick from tf-operator could be done in the follow PR.

[gaocegege]

/lgtm

[gaocegege]

@suleisl2000 Need your approval

[suleisl2000]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: suleisl2000

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [suleisl2000]

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