Re: Next Steps for Taskotron

2014-07-25 Thread Adam Williamson
On Wed, 2014-07-23 at 14:16 -0600, Tim Flink wrote: > The next big feature that I want to work on is support for disposable > clients in Taskotron. This is basically a requirement for doing automated installation testing, right? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter:

Re: Next Steps for Taskotron

2014-07-25 Thread Nick Coghlan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/25/2014 07:51 AM, Tim Flink wrote: > So, long story short - the biggest problem with using the fedora > openstack instance is due to technical limitations of the version > of openstack being used and how everything's wired up. They > probably ar

Re: Next Steps for Taskotron

2014-07-24 Thread Dan Callaghan
Excerpts from Tim Flink's message of 2014-07-24 06:16 +10:00: > While disposable clients may sound simple, there are many parts to > this. > - deciding whether to use something like openstack vs. libvirt Something else to consider here: if you build disposable testing that requires using virtua

Re: Next Steps for Taskotron

2014-07-24 Thread Tim Flink
On Thu, 24 Jul 2014 16:14:33 -0400 Matthew Miller wrote: > On Wed, Jul 23, 2014 at 02:16:39PM -0600, Tim Flink wrote: > > While disposable clients may sound simple, there are many parts to > > this. > > - deciding whether to use something like openstack vs. libvirt > >* The limiting issue he

Re: Next Steps for Taskotron

2014-07-24 Thread Matthew Miller
On Thu, Jul 24, 2014 at 04:14:33PM -0400, Matthew Miller wrote: > I don't think a separate openstack instance should be necessary... I'm not > sure how ours is currently configured -- and I certainly haven't kept up > with the state of the art in openstack networking -- but having a separate > vlan

Re: Next Steps for Taskotron

2014-07-24 Thread Matthew Miller
On Wed, Jul 23, 2014 at 02:16:39PM -0600, Tim Flink wrote: > While disposable clients may sound simple, there are many parts to this. > - deciding whether to use something like openstack vs. libvirt >* The limiting issue here is likely to be that clients need to be > isolated on the netwo

Re: Next Steps for Taskotron

2014-07-23 Thread Nick Coghlan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/24/2014 06:16 AM, Tim Flink wrote: > Now that we're pretty much feature-complete for replacing AutoQA > with Taskotron, it's time to start talking about what to work on > next. > > The next big feature that I want to work on is support for > dis