I am hoping to find some tutorials for two features I'd like to experiment
with. I've just recently been exposed to Foreman and found it's existence a
gawd send.
What I'd like to find is a tutorial on a basic puppet configuration down to
a host. Using something like network that will configure the hosts
interface/aliases/etc. I've experience doing this the old fashion way (a
node file for the host with the parameters filled in there like this.
netif::interface { 'eth2':
ifaddr => '10.20.3.23/24',
ifaddr6 => '2001:413:3ff:1::zz/64',
routes => [
{
address => '0.0.0.0/0',
gateway => '10.20.3.1',
}
],
routes6 => [
{
address => '::/0',
gateway => '2001:413:3ff:1::1'
},
],
}
Where does this part of a puppet module get configured into foreman puppet
controls? I'd be happy to run through a video and/or webpage walkthru if
someone can point me to it.
The other question relates to vmware and Foreman. I've seen some videos
where folks were able to configure the parts of a VM directly and Foreman
seemed to be able to generate the VM side and also manage the kickstart
parts as well. So far I've just been manually creating the empty VM in
vSphere and configuring Foreman to kickit as a bare metal host. I'd love to
find a tutorial/walk thru for this as well.
I have been digging through the Foreman.org website but not found anything
that I could "walkthru" just yet. Maybe I just missed it.
Thanks for any advice you might have.
> I am hoping to find some tutorials for two features I'd like to experiment
> with. I've just recently been exposed to Foreman and found it's existence a
> gawd send.
>
Welcome, glad you like it 
> What I'd like to find is a tutorial on a basic puppet configuration down
> to a host. Using something like network that will configure the hosts
> interface/aliases/etc. I've experience doing this the old fashion way (a
> node file for the host with the parameters filled in there like this. <snip>
>
> Where does this part of a puppet module get configured into foreman puppet
> controls? I'd be happy to run through a video and/or webpage walkthru if
> someone can point me to it.
>
It strongly depends on your puppet modules. It looks like your puppet
module has uses a "define" for "netif::interface", and due to how Puppet
works, ENCs (which Foreman is) cannot directly declare defines, only
classes. You'll want to look at
http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources
for the common patterns used to work around this. In short, the usual way
is to use a wrapper class and a hash of data declared in Foreman.
The other question relates to vmware and Foreman. I've seen some videos
> where folks were able to configure the parts of a VM directly and Foreman
> seemed to be able to generate the VM side and also manage the kickstart
> parts as well. So far I've just been manually creating the empty VM in
> vSphere and configuring Foreman to kickit as a bare metal host. I'd love to
> find a tutorial/walk thru for this as well.
>
These are Compute Resources - see
Foreman :: Manual. In your
case, you'll want to install foreman-vmware and then head over to the
Compute Resources section of the UI to add a new resource. Once configured,
you'll be able to select that resource when creating new hosts.
Hope that helps! Ask away if you're still unclear
Greg
···
On 20 August 2016 at 03:34, Mike Wilson wrote:
>
>
>> I am hoping to find some tutorials for two features I'd like to
>> experiment with. I've just recently been exposed to Foreman and found it's
>> existence a gawd send.
>>
>
> Welcome, glad you like it
>
>
>> What I'd like to find is a tutorial on a basic puppet configuration down
>> to a host. Using something like network that will configure the hosts
>> interface/aliases/etc. I've experience doing this the old fashion way (a
>> node file for the host with the parameters filled in there like this. <snip>
>>
>> Where does this part of a puppet module get configured into foreman
>> puppet controls? I'd be happy to run through a video and/or webpage
>> walkthru if someone can point me to it.
>>
>
> It strongly depends on your puppet modules. It looks like your puppet
> module has uses a "define" for "netif::interface", and due to how Puppet
> works, ENCs (which Foreman is) cannot directly declare defines, only
> classes. You'll want to look at
> Instantiate Puppet resources - Foreman
> for the common patterns used to work around this. In short, the usual way
> is to use a wrapper class and a hash of data declared in Foreman.
>
This was very helpful thanks! I grabbed the puppetlabs/accounts from puppet
forge and installed and then wrote a wrapper and pushed yaml data to it and
it worked. (unrelated to foreman, now I need to see if I can do what
foreman does but in puppet and make the class.users() accept a yaml file
somehow.
> The other question relates to vmware and Foreman. I've seen some videos
>> where folks were able to configure the parts of a VM directly and Foreman
>> seemed to be able to generate the VM side and also manage the kickstart
>> parts as well. So far I've just been manually creating the empty VM in
>> vSphere and configuring Foreman to kickit as a bare metal host. I'd love to
>> find a tutorial/walk thru for this as well.
>>
>
> These are Compute Resources - see
> Foreman :: Manual. In
> your case, you'll want to install foreman-vmware and then head over to the
> Compute Resources section of the UI to add a new resource. Once configured,
> you'll be able to select that resource when creating new hosts.
>
That was exactly what I needed. I was able to get it connected to vsphere
and it'll build up a vm and then kick it. Once again thanks for the link.
>
> Hope that helps! Ask away if you're still unclear
> Greg
>
Do you have any suggestions for reading material on setting up a
distributed setup? Something like a "master" foreman host and then
satellite foreman hosts? We have pops spread across the US/EU and Asia and
we'd like to have "local" foreman hosts manage locally but those foreman
hosts should somehow share the groups/templates/etc from the "master"
foreman host.
Thank you very much for your assistance.
···
On Monday, August 22, 2016 at 4:54:31 AM UTC-5, Greg Sutcliffe wrote:
> On 20 August 2016 at 03:34, Mike Wilson <uce....@gmail.com > > wrote:
So I've actually found a few things on the multiple foreman configuration
but having issues making them talk to each other. It's not very clear what
the whole cert setup is suppose to be (at least not for me).
I tried using the same cert files from the "master" on the remote foreman
hosts but doesn't seem to like that… well the remote foreman was able to
talk to smart proxy of the master but it then couldn't talk to it's own
proxy.
So many parts to the puzzle makes the head spin at times.
So, had some better luck after reading
"Foreman :: Manual"
but still not getting where I want. I think I'll start another thread. IT's
pretty complex and probably not entirely related to this post.
Still looking for decent walkthrus for current release if you can direct me
tho.
