Skip to content

[UX] Run Firecracker without API #1165

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

Closed
andreeaflorescu opened this issue Jul 9, 2019 · 0 comments · Fixed by #1273
Closed

[UX] Run Firecracker without API #1165

andreeaflorescu opened this issue Jul 9, 2019 · 0 comments · Fixed by #1273
Labels
Roadmap: Tracked Items tracked on the roadmap project.

Comments

@andreeaflorescu
Copy link
Member

Once we have the possibility to configure Firecracker via a configuration file (#923) we can also look into the possibility to disable/compile out the API server.

As of now, there are two available options:

  • use conditional compilation to compile out the api_server
  • soft disable of the API (aka do not create the API thread or initialize the API server)

Each of these options come with trade-offs and before decided which way to go, we should get more input from people wanting to use Firecracker without the API.

For additional information you can check the initial issue: #923

@alexandruag alexandruag added the Priority: Medium Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled label Jul 15, 2019
@raduweiss raduweiss added the Roadmap: Tracked Items tracked on the roadmap project. label Jul 15, 2019
@raduweiss raduweiss changed the title Run Firecracker without API [UX] Run Firecracker without API Sep 18, 2020
@raduweiss raduweiss removed the Priority: Medium Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled label Sep 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Roadmap: Tracked Items tracked on the roadmap project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants