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 component.yaml to every ibm-components #984

Merged
merged 3 commits into from
Mar 20, 2019

Conversation

Tomcli
Copy link
Member

@Tomcli Tomcli commented Mar 18, 2019

Add component.yaml to every ibm-components, so users can have a better idea about each component and able to load components with kfp.components.


This change is Reviewable

@k8s-ci-robot
Copy link
Contributor

Hi @Tomcli. 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.

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

Hi @Tomcli. 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.

@Tomcli
Copy link
Member Author

Tomcli commented Mar 18, 2019

/assign @animeshsingh

inputs:
- {name: model_id, description: 'Required. Model training_id from Fabric for Deep Learning'}
- {name: deployment_name, description: 'Required. Deployment name for the seldon service'}
- {name: model_class_name, description: 'PyTorch model class name', default: 'ModelClass'}
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this specific to PyTorch models? Should we call this 'Seldon Core - Serve PyTorch Model' ? Or make it mroe generic?

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for the review. The component container itself could be more generic, but maybe this component.yaml implementation is more specific for PyTorch model. Let me rename the description.

Copy link
Member Author

Choose a reason for hiding this comment

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

done

description: |
Deploy stored model on Watson Machine Learning as a web service.
inputs:
- {name: model_uid, description: 'Required. UID for the Watson Machine Learning model'}
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this the UID for stored model?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, the Watson store component output will be passed to this field as model UID.

@animeshsingh
Copy link
Contributor

/lgtm

@animeshsingh
Copy link
Contributor

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: animeshsingh

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

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 20, 2019

/ok-to-test

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 20, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot merged commit 0fa221a into kubeflow:master Mar 20, 2019
Linchin pushed a commit to Linchin/pipelines that referenced this pull request Apr 11, 2023
@Tomcli Tomcli deleted the components branch February 28, 2024 23:04
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this pull request Mar 11, 2024
…beflow#984 (kubeflow#985)

* Add binary character check to copy-results-artifacts

* Update unit tests
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