On Thu, 2019-05-02 at 10:15 -0400, Dusty Mabe wrote:
On 5/2/19 12:08 AM, Neal Gompa wrote:
> On Wed, May 1, 2019 at 10:48 PM Dusty Mabe <dusty(a)dustymabe.com> wrote:
> > We plan to have testing at various stages of the CoreOS build and delivery
> > pipeline. We definitely plan to have FCOS taken care of using the existing
> > kola testing utility  that was in use previously for container linux.
> > With that said, one thing that has previously been out of scope for kola is
> > testing instances that aren't provisioned with ignition (i.e. they use
> > instead). Today the Fedora Cloud base images are not provisioned using ignition
> > we'll either need to consider adding ignition as an option there OR
> > automated tests against the Fedora Cloud base images in OpenQA (if that's
> It's all possible with OpenQA, the tests just have to be written. :)
I don't know a whole lot about OpenQA but I'm interested to know:
Is it easy to start a VM and attach metadata to it (i.e. support cloud-init)?
I'd have to look into it, but it shouldn't be hard. Starting VMs is
what it *does*, and if it can't support cloud-init already, I can add
it. I'm on vacation till the 19th, will follow up on this later.
It would be a good idea if the actual tests can be shared between test
systems as much as possible. I know the tests Autocloud ran were
basically just bash scripts - openQA could easily use those. What do
the tests run in kola look like?
There's also the question of whether we still want to ship/support the
Cloud Base images. For now they are still release-blocking
deliverables, but their status feels a little vague to me. It would be
good to figure out for sure whether we still consider them important,
if so why, and if so who is in charge of them.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora