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

Upgrade firecracker to 1.4.1 #486

Merged
merged 2 commits into from
Aug 10, 2023

Conversation

fangn2
Copy link
Contributor

@fangn2 fangn2 commented Mar 16, 2023

Issue #, if available:
Upgrade firecracker from 1.0.0 to 1.4.1

Description of changes:
Upgrade firecracker to 1.4.1
firecracker-microvm/firecracker@v1.0.0...v1.4.1
PR #495 has upgraded firecracker partially to 1.4.1(only snapshot memory backend was added, not all swagger specs were in sync with v1.4.1), this PR is a followup to make sure swagger files are in sync and client were generated.

  1. Pull swagger specs from firecracker 1.4.1
  2. go generate to rebuild the client
  3. Upgrade version in the Makefile

Missing features not yet implemented at sdk side are captured in the list.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Sign-off-by: Tony Fang nhfang@amazon.com

@fangn2 fangn2 requested a review from a team as a code owner March 16, 2023 18:21
@fangn2 fangn2 force-pushed the upgrade-firecracker branch 2 times, most recently from 63ae1a7 to 5b8c168 Compare July 28, 2023 13:56
@fangn2 fangn2 changed the title Upgrade firecracker to 1.3.1 Upgrade firecracker to 1.4.0 Jul 28, 2023
@fangn2 fangn2 marked this pull request as draft July 28, 2023 14:08
@fangn2
Copy link
Contributor Author

fangn2 commented Jul 28, 2023

Waiting for #495 to merge to unblock build issue.

@bduffany
Copy link
Contributor

bduffany commented Jul 28, 2023

Waiting for #495 to merge to unblock build issue.

I think my PR (#495) is dependent on upgrading Firecracker, since MemoryBackend is not available in Firecracker v1.0.0.

I can bump firecracker_version in the Makefile in my PR, if that's all that's needed. Let me know if I need to do anything else.

@fangn2
Copy link
Contributor Author

fangn2 commented Jul 29, 2023

I can bump firecracker_version in the Makefile in my PR, if that's all that's needed. Let me know if I need to do anything else.

Thanks! From test perspetive, change that is enough to test with firecracker 1.4.0

1. Pull swagger specs from firecracker
2. `go generate` to rebuild the client
3. Upgrade version in the Makefile

Signed-off-by: Tony Fang <nhfang@amazon.com>
@fangn2 fangn2 marked this pull request as ready for review August 7, 2023 19:14
@fangn2 fangn2 requested a review from ginglis13 August 8, 2023 14:19
Makefile Outdated Show resolved Hide resolved
Signed-off-by: Tony Fang <nhfang@amazon.com>
@fangn2
Copy link
Contributor Author

fangn2 commented Aug 9, 2023

Since firecracker 1.4.1 was released, upgrade to it directly.
1.4.0 to 1.4.1 has no swagger.yaml change.

@fangn2 fangn2 changed the title Upgrade firecracker to 1.4.0 Upgrade firecracker to 1.4.1 Aug 9, 2023
Copy link
Contributor

@swagatbora90 swagatbora90 left a comment

Choose a reason for hiding this comment

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

LGTM

@fangn2 fangn2 merged commit 4299558 into firecracker-microvm:main Aug 10, 2023
5 checks passed
@fangn2 fangn2 deleted the upgrade-firecracker branch August 10, 2023 00:20
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