Re: [Puppet Users] puppet in an appliance model?

[Nikola Petrov]

Hi,

Using puppet in standalone mode with puppet apply from a cronjob will
work without problems. The only thing that will be missing are exported
resources. But you won't need those if this is a single machine.

--
Nikola

On Fri, May 17, 2013 at 03:52:11PM -0700, Vince Taluskie wrote:
> Hey Folks,
>
> I am looking at using puppet to help manage/coordinate system integration
> among several teams collaborating on an appliance product. This is a
> little different than other environments where I've used puppet for
> managing large numbers of systems. In the appliance case, we need to
> build & manage only a single system so a puppetmaster becomes extra baggage
> that is not really needed - what features will not work without one tho?
> Will erb templates still work? Will modules also function without a
> puppet master?
>
> i'm wondering if anyone has already shared their experiences with the group
> using puppet in this kind of mode. If so, please share and I will
> summarize.
>
> Thanks,
>
> Vince
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To post to this group, send email to puppet...@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Keith Burdis]

With PuppetDB >1.1 it is now possible to use exported resources when running puppet apply [1], though of course this still means having a central PuppetDB. This is not relevant for a single machine setup though, as you say.

  - Keith

[1] http://docs.puppetlabs.com/puppetdb/1.3/connect_puppet_apply.html

[jcbollinger]

On Saturday, May 18, 2013 6:45:35 AM UTC-5, nikolavp wrote:

Hi,

Using puppet in standalone mode with puppet apply from a cronjob will
work without problems. The only thing that will be missing are exported
resources. But you won't need those if this is a single machine.

Well, I think there would be a couple more things missing than that.  Reporting and the HTTP API spring to mind.  Still, these are things that don't make much sense in a single-machine context anyway.  Certainly all the bread & butter features will still work: modules, functions, templates, relationships, classes, all native and defined-type resources, hiera.  I think even node blocks work, though they don't necessarily make sense in single-machine mode.


John

[Brian Lalor]

On May 20, 2013, at 8:59 AM, jcbollinger <John.Bo...@stJude.org> wrote:

Well, I think there would be a couple more things missing than that.  Reporting and the HTTP API spring to mind.  Still, these are things that don't make much sense in a single-machine context anyway.  Certainly all the bread & butter features will still work: modules, functions, templates, relationships, classes, all native and defined-type resources, hiera.  I think even node blocks work, though they don't necessarily make sense in single-machine mode.

You can still do reporting, just not back to the master.  I've been playing with pushing reports to Logstash…

--
Brian Lalor
bla...@bravo5.org

[Jakov Sosic]

On 05/20/2013 02:59 PM, jcbollinger wrote:
> Well, I think there would be a couple more things missing than that.
> Reporting and the HTTP API spring to mind. Still, these are things that
> don't make much sense in a single-machine context anyway. Certainly all
> the bread & butter features will still work: modules, functions,
> templates, relationships, classes, all native and defined-type
> resources, hiera. I think even node blocks work, though they don't
> necessarily make sense in single-machine mode.

And how to setup hiera in a masterless puppet?