Thanks for the response, Rob, and for taking action to clarify the
documentation. (And thanks also to Joseph, although he must have not
noticed in my OP that I'm already running Vagrant.) Sorry I took so long to
get back to working on this - I was pulled away to other things for a while.
I think I figured out something (perhaps obvious to everyone but me). In
the VM that PuPHPet made for me, there indeed is a Puppet Master - it's on
the VM itself! Apparently Vagrant installs Puppet there as part of its
provisioning. There is apparently very little "agent", because as far as I
am aware, it did not install a Puppet agent on Windows - I don't think it
even knows what host OS I have. To me that seems like a good thing, because
naturally the future home of the Puppet configuration built on a Vagrant VM
is a production server, which won't involve Vagrant and a host OS.
I'm sure it's obvious that I don't yet understand the interplay between
Vagrant and Puppet, and between the Puppet master and whatever agent piece
runs on the host. I'd like to understand how PuPHPet managed to provision a
VM without having me install anything Puppet-related, but I must be looking
in the wrong files for clues - I've tried Vagrantfile, config.yaml, and
Puppetfile, but I don't see anything about an agent or anything with a
local path. In config.yaml, there is this section under
vagrantfile-local/vm:
provision:
puppet:
manifests_path: puphpet/puppet
manifest_file: site.pp
module_path: puphpet/puppet/modules
options:
- '--verbose'
- '--hiera_config /vagrant/puphpet/puppet/hiera.yaml'
- '--parser future'
There are no executables in the .../puphpet/puppet directory. In
.../Ruby193/bin there is a file called puppet (and a bat file that calls
it), which was probably added during the "gem install puppet" that never
completed. But the whole Ruby193 directory was created two months after I
first used PuPHPet - I think it coincided with when I started using Sass,
which is also Ruby based. So PuPHPet apparently doesn't need Ruby on the
host machine at all (naturally it's on the VM). Where else should I look
for clues?
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/a3422e64-37d9-499e-b0f9-ab540e245820%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
