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

Fission support #61

Open
2 tasks
mcopik opened this issue Jul 16, 2020 · 4 comments
Open
2 tasks

Fission support #61

mcopik opened this issue Jul 16, 2020 · 4 comments

Comments

@mcopik
Copy link
Collaborator

mcopik commented Jul 16, 2020

PR #56 brings basic support for deployment to Fission. Further development is needed.

  • Review the data generated in Prometheus instance
  • Change container type to gather microarchitectural features.
@mcopik
Copy link
Collaborator Author

mcopik commented May 10, 2022

There is a pending pull request with support for running our benchmark functions on Fission. We need to test if the following features are supported:

  • Creating a new function in Fission.
  • Invocation with the Fission driver.
  • Invocations with HTTP trigger.
  • Node.js functions.
  • Python functions.
  • Functions using storage.
  • Updating existing function after code change.
  • Updating existing function on a deployment with no cache.

The second part would be to update the code to the recent changes in SeBS:

  • Independent deployment of Minio storage (see OpenWhisk)
  • System, function, and trigger interfaces.

@mcopik
Copy link
Collaborator Author

mcopik commented Jul 26, 2024

@prajinkhadka You can use this issue to tick off things that already work :-)

@prajinkhadka
Copy link
Collaborator

Supported features as of now,

  • Creating a new function in Fission.
  • Invocation with the Fission driver.
  • Invocations with HTTP trigger.
  • Node.js functions.
  • Python functions.
  • Fission Builder Image to build and install dependencies.
  • Fission Runtime to run the functions.
  • Functions using storage.
  • Updating existing function after code change.
  • Updating existing function on a deployment with no cache.

The second part would be to update the code to the recent changes in SeBS:

  • Independent deployment of Minio storage (see OpenWhisk)
  • System, function, and trigger interfaces.

@mcopik
Copy link
Collaborator Author

mcopik commented Aug 26, 2024

@prajinkhadka Did you manage to solve the issue with numpy installation for the ML inference benchmark?

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

No branches or pull requests

2 participants