Re: Putting Networkd on cloud Atomic and base image for F24

On Mon, 14 Dec 2015 23:30:48 +0530 Kushal Das wrote: > Hi, > > This email is to resume the discussion on putting Networkd as network > stack in Fedora Cloud Atomic and base images. During Fedora 23 release > we had some discussion on the same. I made couple of images [1], and

Re: Fedora cloud image feedback

On Wed, 16 Dec 2015 09:59:54 +0530 Deepak Shetty wrote: > On Tue, Dec 15, 2015 at 6:09 PM, Matthew Miller > wrote: > > > On Tue, Dec 15, 2015 at 08:41:30AM +, P J P wrote: > > > Today in another conversation[1], I received this feedback about

Re: Taskotron and Cloud Image tests

On Thu, 17 Apr 2014 17:35:13 +0200 Vitaly Kuznetsov vkuzn...@redhat.com wrote: snip Another possible snag is that I want to start locking down network access on most if not all of the test clients so that it's less possible for user-submitted tasks to go awry and do things they

Re: Automatic Smoketests for the Cloud Images: What to Test?

On Fri, 7 Mar 2014 18:46:49 +0900 Sandro \red\ Mathys r...@fedoraproject.org wrote: snip So we have the RedHatQE tests, Taskotron and CentOS's CI. Can anyone of the people involved (at the Red Hat side, I guess) well me why we have 3 systems for 1 task? When I took ownership of this external

Re: Automatic Smoketests for the Cloud Images: What to Test?

On Fri, 7 Mar 2014 19:46:28 +0900 Sandro \red\ Mathys r...@fedoraproject.org wrote: snip When I took ownership of this external need (for the Fedora cloud product) I was under the impression we only just (are going to) have Taskotron and everyone knows it's THE way to go. I

Re: Automatic Smoketests for the Cloud Images: What to Test?

On Wed, 5 Mar 2014 20:58:32 +0900 Sandro \red\ Mathys r...@fedoraproject.org wrote: Heads-up: I've taken ownership for the external need Automatic Smoketests on Image Build [0] Testing an image takes time and resources, and with several images, it takes several times that. Since that simply

Re: F18 AMI Testing

On Fri, 4 Jan 2013 14:33:56 -0500 Matthew Miller mat...@fedoraproject.org wrote: On Thu, Jan 03, 2013 at 04:55:59PM -0700, Tim Flink wrote: I completely forgot about this with all the other F18 stuff going on but has anyone been testing the F18 AMIs? If so, are they working

Re: EC2 AMI Test Case Review Request

On Tue, 10 Jan 2012 17:14:52 -0800 (PST) Max Spevack mspev...@fedoraproject.org wrote: To what extent is it possible to run automated tests over Fedora AMIs? Is that being done at all? What would it take to do it? As far as I know, there are no automated tests being done on Fedora AMIs. I

EC2 AMI Test Case Review Request

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_%28draft%29 I'd appreciate any suggestions or

Re: EC2 AMI Test Case Review Request

On Mon, 9 Jan 2012 11:39:52 -0500 Konrad Rzeszutek Wilk konrad.w...@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

Re: EC2 AMI Test Case Review Request

On Mon, 9 Jan 2012 11:48:12 -0600 Justin M. Forbes jmfor...@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

Cloud Test Day Today

The Fedora 16 cloud test day is going on today in #fedora-test-day. The main test day page [1] lists the details on all of the projects that are taking part in the test day. If you're interested, stop by and help test any or all of: - Aeolus [2] * Aeolus is software for running virtual

Fedora S3 Backed AMIs

As I'm learning more about EC2 and AMIs, I'm wondering what the plans are for Fedora S3 backed AMIs. If I'm understanding correctly, an S3 backed AMI has no persistent storage - once the instance is rebooted, all changes are effectively reverted. This would mean that applying updates to an S3