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

add chainer to the website. #200

Merged
merged 5 commits into from
Sep 12, 2018
Merged

Conversation

everpeace
Copy link
Contributor

@everpeace everpeace commented Sep 2, 2018

fixes kubeflow/chainer-operator#23


This change is Reviewable

@everpeace
Copy link
Contributor Author

/assign @jlewi
/cc @jlewi @abhi-g

@everpeace everpeace changed the title add chainer job guide to the website. add chainer to the website. Sep 2, 2018
parent = "components"
weight = 30
+++

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest adding an explanation of what Chainer is.

ks apply ${ENVIRONMENT} -c chainer-operator
```

## Creating an Chainer Job
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Creating a Chainer Job

You can create an Chainer Job by defining an ChainerJob config file. See [examples/chainerjob-reference.yaml](https://github.com/kubeflow/chainer-operator/blob/master/examples/chainerjob-reference.yaml) config file. You may change the config file based on your requirements. By default, the example job is distributed learning with 3 nodes (1 master, 2 workers).

```shell
cat examples/chainerjob-reference.yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This command doesn't seem very helpful because people won't have checked out the chainer repository.

I'd suggest just telling people to download/copy paste the link you provided above.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could also just past the YAML spec into the markdown doc and tell people to copy paste it.

@abhi-g abhi-g assigned everpeace and unassigned jlewi Sep 10, 2018
@abhi-g
Copy link
Member

abhi-g commented Sep 10, 2018

@everpeace please address jlewi's comments.

@everpeace
Copy link
Contributor Author

@abhi-g sorry, I'll fix this PR today (I'm in tokyo).

@everpeace
Copy link
Contributor Author

everpeace commented Sep 11, 2018

@jlewi Hi, I fixed chainer document according to your comments. PTAL again. Thanks in advance.

Please see my comments about the ordering of chainer document on the sidebar: #200 (comment)

@abhi-g
Copy link
Member

abhi-g commented Sep 12, 2018

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhi-g

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:

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

@k8s-ci-robot k8s-ci-robot merged commit 0771142 into kubeflow:v0.2-branch Sep 12, 2018
@abhi-g
Copy link
Member

abhi-g commented Sep 12, 2018

@everpeace I just noticed that the PR merges the chainer docs to v0.2-branch. Since this is going to be available only 0.3.0 onwards, can you please instead merge this into master. I don't think it makes sense to have the Chainer component doc in 0.2 site if the component itself is not available with that release.

@everpeace
Copy link
Contributor Author

@abhi-g oh, ok. I will open another PR to master branch.

@everpeace
Copy link
Contributor Author

@abhi-g should I revert this PR??

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

Successfully merging this pull request may close these issues.

4 participants