Skip to content
This repository has been archived by the owner on May 7, 2021. It is now read-only.

kola/qemu: Add a swtpm by default #1120

Merged
merged 1 commit into from
Nov 21, 2019
Merged

Conversation

cgwalters
Copy link
Member

The duplication in qemu code between cosa and kola needs
to end - this is the start of moving some bits into kola.
Eventually we'll have cosa run be a wrapper for something
like kola qemuexec.

This bit is the equivalent of
coreos/coreos-assembler@55c9b65

We want to strongly emphasize use of TPM devices in CoreOS, so let's provision
one by default.

They can be used for disk encryption, secure secret storage, etc.

The duplication in qemu code between cosa and kola needs
to end - this is the start of moving some bits into kola.
Eventually we'll have `cosa run` be a wrapper for something
like `kola qemuexec`.

This bit is the equivalent of
coreos/coreos-assembler@55c9b65

We want to strongly emphasize use of TPM devices in CoreOS, so let's provision
one by default.

They can be used for disk encryption, secure secret storage, etc.
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.

Looks sane to me. No reason not to also do this for the qemu platform, right? (Though I think there's a higher-level issue there of needing to dedupe more things.)

@cgwalters
Copy link
Member Author

We don't actually use qemu anymore do we? I am increasingly thinking that that path should really be libvirt.

@cgwalters
Copy link
Member Author

Does anyone mind if I do a PR to make qemu-unpriv an alias for qemu?

@cgwalters
Copy link
Member Author

No reason not to also do this for the qemu platform, right?

Is this considered a blocker?

@jlebon
Copy link
Member

jlebon commented Nov 20, 2019

Is this considered a blocker?

It's not, though I'd like at least @ajeddeloh or @arithx to have a look too.

Copy link
Contributor

@arithx arithx left a comment

Choose a reason for hiding this comment

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

Does anyone mind if I do a PR to make qemu-unpriv an alias for qemu?

Most of the features added in the qemu platform aren't being utilized for either *COS distribution set so I'd be okay making qemu-unpriv the default and providing the current qemu platform under a different handle.


No reason not to also do this for the qemu platform, right?

Is this considered a blocker?

I'm fine not having it in this PR

@cgwalters
Copy link
Member Author

I don't have merge access btw (should I?)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants