Puppet proposal

Eyal Edri eedri at redhat.com
Mon Aug 20 06:36:23 UTC 2012



----- Original Message -----
> From: "Robert Middleswarth" <robert at middleswarth.net>
> To: infra at ovirt.org
> Sent: Monday, August 20, 2012 12:05:53 AM
> Subject: Re: Puppet proposal
> 
> On 08/14/2012 11:41 AM, Eyal Edri wrote:
> >
> > ----- Original Message -----
> >> From: "Karsten 'quaid' Wade" <kwade at redhat.com>
> >> To: infra at ovirt.org
> >> Sent: Tuesday, August 14, 2012 5:24:09 PM
> >> Subject: Re: Puppet proposal
> >>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> On 08/14/2012 03:25 AM, Eyal Edri wrote:
> >>> i have a deamon i've written already - attached.
> >> Do we have a git repo for the Infra team yet? I know we could have
> >> Puppet manifests in its own repo, but we have other version
> >> control
> >> needs. Maybe one repo?
> > i recommend one repo for puppet classes. ('puppet')
> > we can publish it to community also, so people can contribute
> > puppet classes we well.
> >
> > i still think we need a separate 'jenkins' repo for all jenkins
> > code, for personal exp using complex jenkins code in jobs.
> >
> > but i won't object to have a single repo for starts with
> > subdirectories (/jenkins /puppet /foreman)
> I personally think we need diff repo's for Puppet and Jenkins.  I
> know
> foreman intergrates with Puppet so those might be able to share the
> same
> repo but that is call we can make when we go to intergrate foreman
> in.
> 

i agree, foreman has the option to manage the puppet repo also, via various environment iirc,
so its not a good idea to put jenkins code there as well. 

also, if jobs will listen to changes in Jenkins code, and puppet code will be in the same repo,
jobs will be triggered for a change that might not be relevant to jenkins (e.g new puppet class). 


> Thanks
> Robert
> >
> > E.
> >> - - Karsten
> >> - --
> >> Karsten 'quaid' Wade, Sr. Analyst - Community Growth
> >> http://TheOpenSourceWay.org  .^\  http://community.redhat.com
> >> @quaid (identi.ca/twitter/IRC)  \v'  gpg: AD0E0C41
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.4.12 (GNU/Linux)
> >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >>
> >> iD8DBQFQKl+J2ZIOBq0ODEERArmdAKCH4ro2WnKzyFu+TX6g8zlIdn5xWQCgxfVF
> >> 5KbY33AL3uVuGOJqQLlUdSc=
> >> =2cy5
> >> -----END PGP SIGNATURE-----
> >> _______________________________________________
> >> Infra mailing list
> >> Infra at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/infra
> >>
> > _______________________________________________
> > Infra mailing list
> > Infra at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> 
> 
> --
> Thanks
> Robert Middleswarth
> @rmiddle (twitter/Freenode IRC)
> @RobertM (OFTC IRC)
> 
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
> 



More information about the Infra mailing list