>> Newb questions warning!
> No problem, welcome to the community!
>> 1- Trying to understand how foreman creates or even can see puppet modules
>> if there are no manifest files anywhere. I am taking it the is because of a
>> database backend in foreman and you make your puppet server use the same
>> database? How do you create a class or module with no manifest?
> A couple of points here. Firstly, I generally recommend against the db
> sharing - give Foreman it's own database, and in the long run, you'll
> be glad you did.
> Foreman doesn't create any puppet code at all - it simply reads it.
> So, you have to go and write some puppet code, and you have to write
> it as modules - Foreman won't read site.pp or similar files.
> Once you have some modules, you can ask Foreman to import your class
> definitions (More -> Puppet Classes -> Import From <proxy name>).
> You'll need an appropriately configured Foreman-Proxy for this. Once
> your classes are imported from your puppetmaster, you'll be able to
> assign the classes to nodes in the Foreman interface.
>> 2- Also I am running an ESXi test box and want puppet (once configured) to
>> manage a test vm on it. How can you add a vm on an ESXi server if ESXi is
>> not a supported compute resource? I do not need foreman to provision just
>> pxe boot, kickstart, puppet takes over. Is there clear steps for this in
> If I recall correctly, ESXi is supported by the libvirt libraries? If
> so, try setting that up, and use a Libvirt Compute Resource. I'm no
> VMware expert, so other community members might chime in here.
VMWare support is no longer done through libvirt, as there is now a
native VMWare compute resource type. (via a vmware fog provider)
However it is currently still considered experimental and has some
restrictions that we are working on improving. I think we are a couple
weeks away from improving the support enough to remove the
experimental tag. Today it's useable to a a large degree in the
development branch, but if you are looking for VMWare support in a
stable release, I'd wait for the upcoming 1.1 release. (It's coming
> If all else fails, create VMs by hand and treat them as Bare Metal
> machines in Foreman.
This works great, and you get the benefits of using Foreman as a
Puppet ENC, Puppet reports processor, and systems inventory database
without the provisioning. This is ok because Foreman is really the
best option for an ENC/reports-processor today. (My company started
using foreman for these features, and are only justnow getting around
to using it for provisioning.)
Please understand compute resources are an optional piece in foreman,
and are strictly related to provisioning.
>> documenting this process and cotrib to the wiki or where ever you would
> There's a new site with new docs coming soon, but in the meantime, we
> always love more contributions! Please feel free to contribute to the
> wiki, if that's something you want to do.
Feel free to subscribe to the foreman-dev mailing list, and/or swing
by and visit on irc #theforeman (freenode) or #theforeman-dev and say
hello!!. I'm guessing once you get a basic foreman install up, you
would be a good candidate to help out with the vmware efforts?
As for the vmware setup instructions… I believe the process today
requires you connect via a vcenter management host. Guessing if you
have a single test box, you don't have that? (It's a rapidly moving
target in the develop branch, so the docs will prolly follow once it
is released in a stable point release, which again should be fairly
On Fri, Nov 30, 2012 at 9:01 AM, Greg Sutcliffe wrote:
> On 30 November 2012 13:49, Dominic Kaiser wrote:
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.