Now that EC2 functionality is a release requirement, I've written up a draft test case for EC2 AMIs. I tried to keep it straight forward without writing a "how to use EC2" guide.
https://fedoraproject.org/wiki/User:Tflink/QA:Testcase_EC2_AMI_Validation_%2...
I'd appreciate any suggestions or comments before moving it from a draft page and adding it to the release validation matrices.
Tim
On Mon, Jan 09, 2012 at 08:10:42AM -0700, Tim Flink wrote:
Now that EC2 functionality is a release requirement, I've written up a draft test case for EC2 AMIs. I tried to keep it straight forward without writing a "how to use EC2" guide.
https://fedoraproject.org/wiki/User:Tflink/QA:Testcase_EC2_AMI_Validation_%2...
I'd appreciate any suggestions or comments before moving it from a draft page and adding it to the release validation matrices.
Looks good to me.. thought as a first time user of AWS, the process of creating an account and the verification was a bit slow.
Also, when finally creating an account I've had no idea what to actually select. I saw something about free Amazon Micro EC2 but no idea how to use it. Finally figured out that I am suppose to use the "Classic" workflow.
Perhaps adding in a comment saying: "As setting up a first-time AWS account can take sometimes a few hours, it is recommended that the user create this in advance."
Also perhaps a link to do when nothing shows up. For example I just created an ami-5f16d836 and all lights are green but I can't connect to it. Perhaps some link to "how to get debug/bootup logs" from the instance?
Or how to add 'debug loglevel=8' to the kernel bootup? IF that is is possible?
On Mon, 9 Jan 2012 11:39:52 -0500 Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
Looks good to me.. thought as a first time user of AWS, the process of creating an account and the verification was a bit slow.
Also, when finally creating an account I've had no idea what to actually select. I saw something about free Amazon Micro EC2 but no idea how to use it. Finally figured out that I am suppose to use the "Classic" workflow.
I see what you mean but I'm a little hesitant to add those kind of details to the test case. It might be better to have a separate wiki page for "getting started with EC2" instructions. I'll look around to see if there is already a page like that.
Perhaps adding in a comment saying: "As setting up a first-time AWS account can take sometimes a few hours, it is recommended that the user create this in advance."
It's been a while since I first created my account, so I had forgotten about that.
Also perhaps a link to do when nothing shows up. For example I just created an ami-5f16d836 and all lights are green but I can't connect to it. Perhaps some link to "how to get debug/bootup logs" from the instance?
I wonder if your security group is set up to allow SSH. By default, no traffic is allowed from outside EC2.
Or how to add 'debug loglevel=8' to the kernel bootup? IF that is is possible?
I'm honestly not sure how to do that, will look into whether or not it's possible, though.
Thanks,
Tim
On Mon, Jan 9, 2012 at 1:47 PM, Tim Flink tflink@redhat.com wrote:
I see what you mean but I'm a little hesitant to add those kind of details to the test case. It might be better to have a separate wiki page for "getting started with EC2" instructions. I'll look around to see if there is already a page like that.
It's the only section of the Cloud Guide that has actually been fully fleshed out, but it does exist! See section 2.1 of http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Clou...
Props to Garrett Holmstrom (I hope I spelled his name correctly) for writing those instructions for the Cloud Guide.
-- Jared Smith Fedora Project Leader
On Mon, 9 Jan 2012 14:14:15 -0500 "Jared K. Smith" jsmith@fedoraproject.org wrote:
On Mon, Jan 9, 2012 at 1:47 PM, Tim Flink tflink@redhat.com wrote:
I see what you mean but I'm a little hesitant to add those kind of details to the test case. It might be better to have a separate wiki page for "getting started with EC2" instructions. I'll look around to see if there is already a page like that.
It's the only section of the Cloud Guide that has actually been fully fleshed out, but it does exist! See section 2.1 of http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Clou...
Props to Garrett Holmstrom (I hope I spelled his name correctly) for writing those instructions for the Cloud Guide.
Awesome, that's exactly what I was looking for. Thanks for the link, I updated the wiki page so that it is using that instead of the AWS guide.
Tim
On Mon, Jan 09, 2012 at 08:10:42AM -0700, Tim Flink wrote:
Now that EC2 functionality is a release requirement, I've written up a draft test case for EC2 AMIs. I tried to keep it straight forward without writing a "how to use EC2" guide.
https://fedoraproject.org/wiki/User:Tflink/QA:Testcase_EC2_AMI_Validation_%2...
I'd appreciate any suggestions or comments before moving it from a draft page and adding it to the release validation matrices.
Tim
I would say it is good, and fairly straight forward. The only change I might suggest is adding "The instance is capable of installing from the default yum repository" to expected results. We are shipping very bare bones instances here. There are really 4 key requirements:
1. The system will boot 2. You can ssh into the host as ec2-user with sudo access 3. You can install packages from the yum repository 4. The system is stable in all of these tasks.
Justin
On Mon, 9 Jan 2012 11:48:12 -0600 "Justin M. Forbes" jmforbes@linuxtx.org wrote:
I would say it is good, and fairly straight forward. The only change I might suggest is adding "The instance is capable of installing from the default yum repository" to expected results. We are shipping very bare bones instances here. There are really 4 key requirements:
- The system will boot
- You can ssh into the host as ec2-user with sudo access
- You can install packages from the yum repository
- The system is stable in all of these tasks.
Thanks for the feedback, I added expected results for SSH and installation using yum.
Tim
-
Jared K. Smith -
Justin Forbes -
Konrad Rzeszutek Wilk -
Tim Flink