Skip to content

Conversation

@cgwalters
Copy link
Member

@cgwalters cgwalters commented Mar 11, 2020

Today kola testiso is pretty hardcoded. I think it was @arithx
suggested making things more generic, and this implements
that. The core mantle platform/ bits have an API to start
a PXE install, and the precise Ignition that gets passed in
is provided by a higher level test.

I also cleaned things up a bit in preparation for supporting
ISO testing and not just the PXE path. (Though the code
is still messy in this respect, but this is a preparatory step)

A possible next step here is to actually implement the Machine
interface instead of having a custom InstalledMachine, that'd
make it even easier to have something like:

kola run --pxe basic

@cgwalters
Copy link
Member Author

Depends on #1228

@jlebon
Copy link
Member

jlebon commented Mar 11, 2020

Hmm, I thought maybe adding the needs-rebase label would trigger the OpenShift bot to say that this PR needs a rebase too.

@cgwalters
Copy link
Member Author

🏄‍♂️ Rebased

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.

Didn't read in depth, but looks reasonable at a high-level.
Will let @arithx have a look.

/approve

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.

Apologies if there's comments on code that already existed. The diff isn't very useful for me.

@Prashanth684
Copy link
Contributor

Not related to this change but i noticed that when I tested the Fedora CoreOS live image, the CoreOS installer failed complaining about finding a signature file. Should we add coreos.inst.insecure to the cmdline or should the signature file be generated by default ?

@cgwalters
Copy link
Member Author

Should we add coreos.inst.insecure to the cmdline or should the signature file be generated by default ?

use kola testiso -S

@Prashanth684
Copy link
Contributor

Prashanth684 commented Mar 12, 2020

Should we add coreos.inst.insecure to the cmdline or should the signature file be generated by default ?

use kola testiso -S

i was doing a cosa kola testiso -h and I couldn't view the usage doc. Just did a kola testiso -h and that helped

@cgwalters
Copy link
Member Author

Updated to address comments!

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.

/approve

Today `kola testiso` is pretty hardcoded.  I think it was @slowrie
suggested making things more generic, and this implements
that.  The core mantle `platform/` bits have an API to start
a PXE install, and the precise Ignition that gets passed in
is provided by a higher level test.

I also cleaned things up a bit in preparation for supporting
ISO testing and not just the PXE path.  (Though the code
is still messy in this respect, but this is a preparatory step)

A possible next step here is to actually implement the `Machine`
interface instead of having a custom `InstalledMachine`, that'd
make it even easier to have something like:

`kola run --pxe basic`
@jlebon
Copy link
Member

jlebon commented Mar 13, 2020

/lgtm

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arithx, cgwalters, jlebon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [arithx,cgwalters,jlebon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants