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

Augment DockerRunner to support running from a fondant Pipeline #651

Merged
merged 7 commits into from
Nov 27, 2023

Conversation

GeorgesLorre
Copy link
Collaborator

No description provided.

@GeorgesLorre
Copy link
Collaborator Author

  E   TypeError: unsupported operand type(s) for |: 'type' and 'type'

Thanks python 3.8...

Copy link
Member

@RobbeSneyders RobbeSneyders left a comment

Choose a reason for hiding this comment

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

Thanks @GeorgesLorre! The general approach looks good!

extra_volumes=extra_volumes,
build_args=build_args,
)
self.run(output_path)
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this be _run?

self,
input: t.Union[Pipeline, str],
*,
output_path: str = "docker-compose.yml",
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to expose this? I would move this to a temp file or hidden directory.

Copy link
Contributor

Choose a reason for hiding this comment

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

Wouldn't this make it more difficult to run the pipeline again from the same component spec to follow the "compile once, run many" approach (well in this case it would be "run once, run many")?

Unless this is temporary until we introduce a general compiler that we can start from as proposed here https://github.com/orgs/ml6team/projects/1/views/8?filterQuery=&pane=issue&itemId=44594106

Copy link
Member

Choose a reason for hiding this comment

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

I would only hide this in the Runner. Users can still explicitly compile using the compile command or Compiler class.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

With expose you mean the file and not the argument ?

Copy link
Member

Choose a reason for hiding this comment

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

Both

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

updated

self,
input: t.Union[Pipeline, str],
*,
output_path: str = "docker-compose.yml",
Copy link
Contributor

Choose a reason for hiding this comment

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

I know super picky, but can we use a common yaml file extension within Fondant. Either yml or yaml?
btw: accordingly to the docker compose docs the new preferred default file for docker compose is called compose.yaml

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fair point ( can we add this to precommit ?). I will make the changes

@PhilippeMoussalli
Copy link
Contributor

_ No description provided. _

Are we planning on doing the same for kfp and Vertex?

@GeorgesLorre
Copy link
Collaborator Author

_ No description provided. _

Are we planning on doing the same for kfp and Vertex?

Yes the idea is to make the Runner classes prime user interfaces (next to the cli). Now you need to import a compiler and runner and and compile first before running. The idea here is that the user would only need 1 class that is easy to use.

@GeorgesLorre GeorgesLorre merged commit 130fb25 into main Nov 27, 2023
6 checks passed
@GeorgesLorre GeorgesLorre deleted the feature/docker-compile-and-run branch November 27, 2023 10:54
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