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

src/cmd-buildextend-vultr: prepare a Vultr raw image #1083

Merged
merged 2 commits into from
Jan 31, 2020
Merged

src/cmd-buildextend-vultr: prepare a Vultr raw image #1083

merged 2 commits into from
Jan 31, 2020

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Jan 29, 2020

With this, I was able to build a new coreos-assembler and use it to build a fedora-coreos-31.20200128.dev.0-vultr.x86_64.raw that claims to have the vultr platform id set. No change to Ignition yet, so its not of practical use yet, but its something.

cosa build
cosa buildextend-vultr

@dghubble dghubble changed the title Add cmd-buildextend-vultr to prepare a Vultr raw image src/cmd-buildextend-vultr: prepare a Vultr raw image Jan 29, 2020
Copy link
Member

@cgwalters cgwalters left a comment

Choose a reason for hiding this comment

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

Seems sane to me as a start. Let's at least link to coreos/fedora-coreos-tracker#355 in the commit message?

* Build a raw image with the Ignition provider set to vultr
to correspond with coreos/ignition#918
* coreos/fedora-coreos-tracker#355
@darkmuggle
Copy link
Contributor

LGTM, this follows the new model :)

Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

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

One comment, LGTM otherwise!

src/cosalib/vultr.py Outdated Show resolved Hide resolved
@jlebon jlebon merged commit 3f31774 into coreos:master Jan 31, 2020
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.

None yet

4 participants