-
Notifications
You must be signed in to change notification settings - Fork 24
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
Comments
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. :) |
+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. |
@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. |
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. |
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. |
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. |
Neat! If there's no email output, where can one see the results? |
@mattdm, a fedmsg pops out onto the bus. Topic is |
@mattdm This is also something we can display on |
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. |
+1 on just emailing on failure. |
Adding an idea from @mattdm:
After cloud image is uploaded:
The text was updated successfully, but these errors were encountered: