Le mardi 15 décembre 2015 à 19:57 +0530, Kaushal M a écrit : > On Tue, Dec 15, 2015 at 6:06 PM, Michael Scherer <[email protected]> wrote: > > Le mardi 15 décembre 2015 à 05:39 +0000, [email protected] a écrit : > >> https://bugzilla.redhat.com/show_bug.cgi?id=1291537 > >> > >> Bug ID: 1291537 > >> Summary: [RFE] Provide mechanism to spin up reproducible test > >> environment for all developers > >> Product: GlusterFS > >> Version: mainline > >> Component: project-infrastructure > >> Assignee: [email protected] > >> Reporter: > >> CC: [email protected], [email protected] > >> > >> > >> > >> Description of problem: > >> > >> There should be a way for developers to obtain/spin up a test environment > >> which > >> is identical to our upstream test infrastructure. > > > > I suspect that having a different code base for the Vagrant VM and the > > regular one will just cause trouble. > > > > Why did people decide to rewrite the jenkins slave installation in > > ansible when we published the salt based stuff, and if there was any > > issues no one did ever post anything on the gluster-infra list ? > > > > Micheal, I'm still working on fixing salt state for the jenkins slave. > I'm nearly done with it, I need to just fix ~5 tests each on el7 and f23. > I hope that this will become the standard base for any gluster regression > test. > > Raghavendra had started this particular effort by himself before the > salt states were published. > He probably chose Ansible, as it's much easier to use Ansible with Vagrant. > > I'll work with him to see that we can converge on a solution.
Well, salt is also getting on my nerves on a regular basis, so if we start to have people who know ansible in the community, we could reevalute the tools. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
