Is it possible to have foreman integrate with Git repository so that
version control can be applied to the configurations?
Hello Michael,
this is the standard (and recommented) deployment.
Foreman basically does not "care" about where do you store your
configuration. It just need a smart-proxy with puppet feature to be
available, so it can import puppet classes.
How you manage your configuration manifests is up to you.
LZ
···
On Wed, Aug 07, 2013 at 02:50:55PM +0100, Michael.OBrien wrote: > Is it possible to have foreman integrate with Git repository so that > version control can be applied to the configurations? > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/groups/opt_out. > >–
Later,
Lukas “lzap” Zapletal
irc: lzap #theforeman
We keep our modules directory in Git and our environments are branches. We
try to use Puppetforge to find a matching module then copy that to a
development branch once we have cleaned it up and made any modifications,
we push them through our usual testing processes to live.
Jim
···
On 7 August 2013 14:50, Michael.OBrien wrote:Is it possible to have foreman integrate with Git repository so that
version control can be applied to the configurations?****–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
I suspect the original question is also to do with storing items such as
parameters and node configurations that are defined in Foreman - e.g. if I
were to shift a bunch of nodes to a new hostgroup I would have no simple
rollback or history of that, or if I were to change the value of a
parameter etc. in the Foreman gui.
···
On Fri, Aug 9, 2013 at 1:10 AM, James Bailey wrote:We keep our modules directory in Git and our environments are branches.
We try to use Puppetforge to find a matching module then copy that to a
development branch once we have cleaned it up and made any modifications,
we push them through our usual testing processes to live.Jim
On 7 August 2013 14:50, Michael.OBrien Michael.OBrien@ul.ie wrote:
Is it possible to have foreman integrate with Git repository so that
version control can be applied to the configurations?****–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
This is something I'd like to see, too. Maybe not full Git integration,
but at least a file-based storage back-end for some data. Namely, I'd like
to see the provisioning templates stored as real files. Even without Git
integration, storing them as real files would let me access them from the
shell, edit them in my favorite editor and wrap them in a VCS repo. I know
Foreman has a decent rollback feature for templates, for which I've been
thankfull, but it's a child's toy compared to a real VCS.
If Hiera integration is in the works I'd like to see a file-based back-end
there, too. I really like the idea of keeping my organization's entire
configuration state in a central repository, and, in-turn, keeping a
central change log for the whole thing-- code and data combined. I've been
migrating my data into Foreman and this now just seems logical-- and
entirely possible!
The template editor should be replaced with CodeMirror, too, but that's
another issue entirely.
···
On Thursday, August 8, 2013 3:59:33 PM UTC-4, Xav Paice wrote: > > I suspect the original question is also to do with storing items such as > parameters and node configurations that are defined in Foreman - e.g. if I > were to shift a bunch of nodes to a new hostgroup I would have no simple > rollback or history of that, or if I were to change the value of a > parameter etc. in the Foreman gui. > > > On Fri, Aug 9, 2013 at 1:10 AM, James Bailey <parado...@gmail.com > > wrote: > >> We keep our modules directory in Git and our environments are branches. >> We try to use Puppetforge to find a matching module then copy that to a >> development branch once we have cleaned it up and made any modifications, >> we push them through our usual testing processes to live. >> >> Jim >> >> >> On 7 August 2013 14:50, Michael.OBrien <Michael...@ul.ie >wrote: >> >>> Is it possible to have foreman integrate with Git repository so that >>> version control can be applied to the configurations?**** >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Foreman users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-user...@googlegroups.com . >>> To post to this group, send email to forema...@googlegroups.com >>> . >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >s/into Foreman/into Hiera/
···
On 08/08/2013 05:51 PM, Lucas Yamanishi wrote: > > If Hiera integration is in the works I'd like to see a file-based > back-end there, too. I really like the idea of keeping my > organization's entire configuration state in a central repository, > and, in-turn, keeping a central change log for the whole thing-- code > and data combined. I've been migrating my data into Foreman and this > now just seems logical-- and entirely possible!Something like Gepetto for Eclipse could be useful for those with more of a
liking for text editors but as Xav said its about having as much config as
possible managed in Git and a history that foreman can access and append to