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

Spin up an instance and run a simple test after cloud image upload #7

Closed
6 tasks done
dtgay opened this issue Jun 7, 2014 · 11 comments
Closed
6 tasks done

Spin up an instance and run a simple test after cloud image upload #7

dtgay opened this issue Jun 7, 2014 · 11 comments
Milestone

Comments

@dtgay
Copy link
Contributor

dtgay commented Jun 7, 2014

Adding an idea from @mattdm:

After cloud image is uploaded:

  • a test instance is booted in any one of our available environments (EC2, Fedora cloud, whatever is easiest)
  • a simple test is run against that instance
    • connect via ssh and run /bin/true
    • it should be easy to sub in any other "test command" (more complicated tests can come later)
  • results of that test are reported on fedmsg (and possibly by email to cloud-sig list)
  • make sure test instance has been terminated and its resources released
@mattdm
Copy link

mattdm commented Jun 7, 2014

Also, I left this unsaid, but of course the last step is "terminate test instance and make sure its resources are released". Just for the record. :)

@dtgay
Copy link
Contributor Author

dtgay commented Jun 7, 2014

+1, added to the list. As I start programmatically doing EC2 things, I'll be keeping a close eye on the AWS control panel to ensure that our resources aren't wasted.

@dtgay dtgay added this to the 4th of July milestone Jun 7, 2014
@dtgay
Copy link
Contributor Author

dtgay commented Jun 19, 2014

@mattdm, we just want the image to be tested by any provider? So we don't need a test run for an image by every provider? We can just use say a spun-up EC2 test instance to test an image once? Just making sure we don't want each provider to spin up its own test instance to test each image build, if that makes sense.

@mattdm
Copy link

mattdm commented Jun 19, 2014

We'll need to some tests for every provider -- especially the "does it boot" one, but also metadata services and probably some of the other basic "does it work" tests.

On the other hand, things like "are the dependencies correct", "is the image size not crazy", and other tests which aren't environment-sensitive can and probably should only be done one place.

@mattdm
Copy link

mattdm commented Jun 19, 2014

Possibly, we do the complete tests on our own openstack, and then only once that has succeeded do we bother uploading to the other services and running those tests.

@dtgay
Copy link
Contributor Author

dtgay commented Jul 8, 2014

Alright, this is done. There are some improvements to be made, but it works. Fedimg currently does not send test results to any email list, but that could be added later if deemed not-too-spammy.

@dtgay dtgay closed this as completed Jul 8, 2014
@mattdm
Copy link

mattdm commented Jul 8, 2014

Neat! If there's no email output, where can one see the results?

@dtgay
Copy link
Contributor Author

dtgay commented Jul 8, 2014

@mattdm, a fedmsg pops out onto the bus. Topic is image.test instead of image.upload. So we have two fedmsg topics in Fedimg now. I'm unfamiliar with how things work on that mailing list, so if you think it appropriate to shoot out an email with every test success or failure, or perhaps a condensed newsletter of sorts, I can do that, too.

@dtgay
Copy link
Contributor Author

dtgay commented Jul 8, 2014

@mattdm This is also something we can display on fedora-releng-dash

@mattdm
Copy link

mattdm commented Jul 9, 2014

A lot of the mailing lists do have automated messages like that. Maybe ask if people would like to see it there? Maybe after it's going for a while, we could have it only send failures? I know I'd like this, but maybe others won't.

@dtgay
Copy link
Contributor Author

dtgay commented Jul 9, 2014

+1 on just emailing on failure.

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

No branches or pull requests

2 participants