> From: "Tim Flink" <[email protected]> > I'm still leaning towards the no-cloud option, mostly because I really > don't want to get into openstack deployment management. Yes, there is a > fedora infra managed instance of openstack but I also think assuming we > would never have to help fix/improve that deployment is a bit on the > naive side. The other big advantages in my mind are that the no-cloud > approach makes the local execution much closer to the production > execution model and we'd be much closer to enabling stuff like gnome's > test suite. > > I'd appreciate thoughts from other folks on which route they think is a > better approach.
From the Beaker side, one of the big reasons we went down the path of providing the "virt/image-install" task is because we don't yet have an ETA on when we'll drop the "experimental" tag from our OpenStack integration. So unless you have a particularly compelling need to do multi-host test orchestration, sticking with virt guests on a single host sounds like a good option to me. The other thing that may potentially let you do is IPv6-only testing of your guests, even if nothing else on your network supports IPv6-only operation. Cheers, Nick. -- Nick Coghlan Red Hat Hosted & Shared Services Software Engineering & Development, Brisbane HSS Provisioning Architect _______________________________________________ qa-devel mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/qa-devel
