Issue #9471 has been updated by Nigel Kersten. Assignee changed from Nigel Kersten to Jason McKerr
This feels like QA/Testing need to do a cost/benefit analysis of: * Build AMIs for everything we support, and deal with the guaranteed drift from "vanilla" installs as well as the implications that has for testing coverage * Use Cloud Provisioner/manifests to take vanilla AMIs and set them up for testing. There are quite a few pros and cons here, but given we're not talking about producing these as product for consumers, I don't think it's my decision /me passes buck. ---------------------------------------- Feature #9471: Need to create AMIs for testing https://projects.puppetlabs.com/issues/9471 Author: Dan Bode Status: Needs Decision Priority: High Assignee: Jason McKerr Category: Target version: Patch: None Keywords: Branch: Before we can really start testing in the cloud, we should start building AMIs that can be used by the test harness. I just tried to use the base centos ami that is hard coded into the pe-builder and in its current state it will not work with the test harness. We need to ensure that the AMIS that we build have the following installed: * ntp should be installed * tar should be installed * ssh should be installed and sshd should be enabled We should also build out (or identify existing) AMIs that can be used to test on all of the supported platforms, this includes: * SLES 11 * Solaris (SPARC and Intel) * RHEL 4,5,6 * CentOS 4,5,6 * Debian 5 * Ubuntu 10.04 LTS -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
