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

Improve doc for gcp components. #1049

Merged
merged 12 commits into from
Apr 4, 2019
Merged

Conversation

hongye-sun
Copy link
Contributor

@hongye-sun hongye-sun commented Mar 26, 2019

The change includes improvements on all GCP OOB component docs.


This change is Reviewable

@hongye-sun hongye-sun changed the title [WIP] Improve doc for gcp components. Improve doc for gcp components. Mar 29, 2019
@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 30, 2019

/test kubeflow-pipeline-e2e-test

# Required Parameters
PROJECT_ID = '<Please put your project ID here>'
GCS_WORKING_DIR = 'gs://<Please put your GCS path here>' # No ending slash
%%capture
Copy link
Contributor

Choose a reason for hiding this comment

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

What is %%capture command?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is used to hide the outputs from the cell. It's usually not quite useful to show pip install logs here.

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we still need errors to be output.
https://ipython.readthedocs.io/en/stable/interactive/magics.html#cellmagic-capture shows a way to not capture stderr.
however, when I tried it in my notebook with !pip install, it does not work.

Copy link
Contributor

@Ark-kun Ark-kun Apr 4, 2019

Choose a reason for hiding this comment

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

BTW, pip has the --quiet option.

@@ -33,20 +34,23 @@ inputs:
default: ''
type: String
- name: output_gcs_path
description: 'The GCS blob path to dump the query results to.'
description: 'The path to the Cloud Storage bucket to store the query output.'
Copy link
Contributor

Choose a reason for hiding this comment

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

To be honest, the word "bucket" is confusing here. You've probably meant "The path of GCS directory" or "The path of GCS file".

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a suggested change from tech writer. I'd like to follow their suggestion to make it consistent with other AIHub docs.

Copy link
Contributor

Choose a reason for hiding this comment

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

OK.
We should probably still tell them that technically, a bucket is my-bucket while gs://my-bucket/some/dir/ is a GCS directory path, not a bucket.

!pip3 install $KFP_PACKAGE --upgrade
```

2. Load the component by DSL
Copy link
Contributor

Choose a reason for hiding this comment

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

"Load the component using KFP SDK"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

"EXPERIMENT_NAME = 'Dataflow - Launch Template'\n",
"COMPONENT_SPEC_URI = 'https://raw.githubusercontent.com/kubeflow/pipelines/d2f5cc92a46012b9927209e2aaccab70961582dc/components/gcp/dataflow/launch_template/component.yaml'"
"COMPONENT_SPEC_URI = 'https://raw.githubusercontent.com/kubeflow/pipelines/d2f5cc92a46012b9927209e2aaccab70961582dc/components/gcp/dataflow/launch_template/component.yaml'\n",
"dataflow_template_op = comp.load_component_from_url(COMPONENT_SPEC_URI)\n",
Copy link
Contributor

@Ark-kun Ark-kun Apr 3, 2019

Choose a reason for hiding this comment

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

Do we really need two lines to load component? Having a single line will make it much easier to copy/paste to a multi-component pipeline (otherwise, the COMPONENT_SPEC_URI variable name will be duplicated).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@Ark-kun
Copy link
Contributor

Ark-kun commented Apr 3, 2019

Such a big PR =)
I've left some minor comments.

@Ark-kun
Copy link
Contributor

Ark-kun commented Apr 4, 2019

/lgtm

@gaoning777
Copy link
Contributor

/lgtm

@hongye-sun
Copy link
Contributor Author

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongye-sun

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

1 similar comment
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongye-sun

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 8e2ea39 into kubeflow:master Apr 4, 2019
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this pull request Oct 22, 2023
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this pull request Mar 11, 2024
* update tekton to 0.38.4

* update tekton to 0.38.4
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