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 Pipeline design #21

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

Yancey1989
Copy link
Collaborator

@Yancey1989 Yancey1989 commented Mar 23, 2020

Add API design for Tekton Pipeline.

@Yancey1989 Yancey1989 changed the title [wip]Add Pipeline design Add Pipeline design Mar 23, 2020
@Yancey1989
Copy link
Collaborator Author

cc @typhoonzero

@@ -101,7 +101,7 @@ spec:
We hope Fluid users could represent it by the following line.

```python
skaffold_git = fluid.Git(
skaffold_git = fluid.git_resource(

Choose a reason for hiding this comment

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

Please also update below descriptions: Please be aware that the call to fluid.Git doesn't include the name

Choose a reason for hiding this comment

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

Why not use fluid.git for simple?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Why not use fluid.git for simple?

Just tracing the current implementation. I think we can update the API and design in another PR if need.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I remember that Tekton has a limited number of pre-defined resource types and git is one of them. I would suggest we keep it Git other than git_resource, because git_resouce is not a fullname; git_pipeline_resource is. But git_pipeline_resource is too long. It seems reasonable to use a short name Git for one of a few pre-defined types.

doc/design.md Outdated Show resolved Hide resolved
doc/design.md Outdated

``` python
@fluid.pipeline
def tutorial(source_repo:"resource,git", web_image="resource,image"):

Choose a reason for hiding this comment

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

source_repo="resource,git"

Copy link
Collaborator Author

@Yancey1989 Yancey1989 Mar 27, 2020

Choose a reason for hiding this comment

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

I think it's okay, this is the parameter annotation instead of the default value, ref: https://www.python.org/dev/peps/pep-3107/#id29

build_skaffold_web = build_docker_image_from_git_source(source_repo, web_image)

deploy_web = deploy_using_kubectl(source_repo, web_image)
deploy_web.web_image.from(build_skaffold_web)

Choose a reason for hiding this comment

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

How to define dependency by not using input/output?

Copy link
Collaborator Author

@Yancey1989 Yancey1989 Mar 27, 2020

Choose a reason for hiding this comment

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

Can use the runAfter keyword, and I added a section PiepeLine with DAG to introduce how to construct the DAG.


``` yaml
apiVersion: tekton.dev/v1beta1
kind: Pipeline
Copy link
Collaborator

Choose a reason for hiding this comment

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

What is the lifecycle of a pipeline object?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Pipeline object is like function definition in Python which includes Pipeline Tasks
A PipelineRun object would invoke the Pipeline Tasks as the dependency, can find some information from Task Status

doc/design.md Show resolved Hide resolved

This will result in the following execution graph:

``` text
Copy link
Collaborator

Choose a reason for hiding this comment

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

No whitespace between ``` and text

@@ -101,7 +101,7 @@ spec:
We hope Fluid users could represent it by the following line.

```python
skaffold_git = fluid.Git(
skaffold_git = fluid.git_resource(
Copy link
Collaborator

Choose a reason for hiding this comment

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

I remember that Tekton has a limited number of pre-defined resource types and git is one of them. I would suggest we keep it Git other than git_resource, because git_resouce is not a fullname; git_pipeline_resource is. But git_pipeline_resource is too long. It seems reasonable to use a short name Git for one of a few pre-defined types.

@@ -125,7 +125,7 @@ spec:
We hope Fluid users could represent the above YAML file by the following line.

```python
skaffold_image_leeroy_web = fluid.Image(
skaffold_image_leeroy_web = fluid.image_resource(
Copy link
Collaborator

Choose a reason for hiding this comment

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

Similarly, "image" is one of a few pre-defined resource types. How about we keep the name Image.

@@ -142,7 +142,7 @@ According to the [document](https://github.com/tektoncd/pipeline/blob/master/doc
The following example from the [Tekton tutorial](https://github.com/tektoncd/pipeline/blob/master/docs/tutorial.md#task-inputs-and-outputs) takes an input resource, an output resource, and two input parameters.

```yaml
goapiVersion: tekton.dev/v1alpha1
apiVersion: tekton.dev/v1alpha1
Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks for pointing this out!


### Pipeline

A `Pipeline` object is like function declaration, according to the [definition](https://github.com/tektoncd/pipeline/blob/master/docs/pipelines.md).
Copy link
Collaborator

Choose a reason for hiding this comment

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

In the above text, we stated that a Task is like a function. Here we state the same with Pipeline. What is the difference between these two types of "functions"?

value: "spec.template.spec.containers[0].image"
```

The above `Pipeline` is referencing a `Task` called `deploy-using-kubectl` defined as follows:
Copy link
Collaborator

Choose a reason for hiding this comment

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

is referencing => refers to

build_skaffold_web = build_docker_image_from_git_source(source_repo, web_image)

deploy_web = deploy_using_kubectl(source_repo, web_image)
deploy_web.web_image.from(build_skaffold_web)
Copy link
Collaborator

Choose a reason for hiding this comment

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

This deploy_web.web_image.from syntax looks confusing. Python programmer do not do this with function parameters.

I am afraid that this weird design might come from the fact that a Pipeline is NOT similar to a function definition.

Copy link
Collaborator

Choose a reason for hiding this comment

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

After reading more about Pipeline, I see it describes a DAG of tasks, where edges are data dependencies between tasks.

Thinking about the following example from the Tekton tutorial https://github.com/tektoncd/pipeline/blob/master/docs/pipelines.md#from:

- name: build-app
  taskRef:
    name: build-push
  resources:
    outputs:
      - name: image
        resource: my-image
- name: deploy-app
  taskRef:
    name: deploy-kubectl
  resources:
    inputs:
      - name: image
        resource: my-image
        from:
          - build-app

Using programming language idiom, it is simply function calls

deploy_kubectl(image=build_push(my_image))

It seems that what we expect users to write is

@fluid.pipeline
def build_and_deploy(image):
    deploy_kubectl(image=build_push(my_image))

where @fluid.pipeline should dry-run the function build_and_deploy to analysis the function dependencies, which is deploy_kubectl.image <- build_push, and generate the YAML definition of the Pipeline object.

I am not sure if the above suggestion is correct, or how reasonable it is. It has been a while I haven't use Tekton.

As the following example of `Pipeline spec` comes from Tekton Pipeline tutorials:

``` yaml
- name: lint-repo
Copy link
Collaborator

Choose a reason for hiding this comment

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

This doesn't look like a complete Kubernetes YAML. What is its kind?

- `from`: clauses on the PipelineResources needed by a Task.
- `runAfter`: clauses on the Pipeline Tasks.

As the following example of `Pipeline spec` comes from Tekton Pipeline tutorials:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Which tutorial? We need a URL here.

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

Successfully merging this pull request may close these issues.

4 participants