New user questions:
I can't find a clear method in the documentation for allowing Foreman
to see our external nodes configuration. I'm actually not sure WHO
manages the external nodes once you start use Foreman. Since Foreman
doesn't provide any revision control of our external node files, I
want to keep using our old external nodes script, and just have
Foreman as a pretty front end GUI. How can I do that?
The new host screen has a lot of drop downs with no data in them.
Where does the data come from? I noticed that the Environment drop
down defaults to 'production', but our environments are called
something else. Not sure why this is.
Doug.
As for the environments, that is determined from system facts. To
load those into foreman there are a couple different ways explained
at: Puppet Facts - Foreman … some
other things may also get filled out after doing this. I don't
currently use foreman for builds (yet) so I don't have much more info
regarding that.
Also, there is a bug where the environment is set only once when the
host is created … if its changed it doesn't currently get updated to
the new environment.
I'm not sure I understand the whole ENC issue … so I'll just point
you to more documentation. 
http://theforeman.org/projects/foreman/wiki/External_Nodes#Import-your-external-node-setup-from-an-older-external-node-setup
http://theforeman.org/projects/foreman/wiki/External_Nodes
Regards,
Jake
···
On May 26, 12:26 pm, Douglas wrote:
> New user questions:
>
> I can't find a clear method in the documentation for allowing Foreman
> to see our external nodes configuration. I'm actually not sure WHO
> manages the external nodes once you start use Foreman. Since Foreman
> doesn't provide any revision control of our external node files, I
> want to keep using our old external nodes script, and just have
> Foreman as a pretty front end GUI. How can I do that?
>
> The new host screen has a lot of drop downs with no data in them.
> Where does the data come from? I noticed that the Environment drop
> down defaults to 'production', but our environments are called
> something else. Not sure why this is.
>
> Doug.
Issue = I don't want Foreman to manage my nodes.
Doug.
···
On Thu, May 26, 2011 at 2:01 PM, Jake - USPS wrote:
As for the environments, that is determined from system facts. To
load those into foreman there are a couple different ways explained
at: Puppet Facts - Foreman … some
other things may also get filled out after doing this. I don’t
currently use foreman for builds (yet) so I don’t have much more info
regarding that.
Also, there is a bug where the environment is set only once when the
host is created … if its changed it doesn’t currently get updated to
the new environment.
I’m not sure I understand the whole ENC issue … so I’ll just point
you to more documentation.
It doesn't have to. I use it pretty much just for reporting right
now. I plan on next using it for limited classifying (assigning
modules to systems through it). Lastly I plan to build from it.
Regards,
Jake
···
On May 26, 4:05 pm, Douglas Garstang wrote:
> On Thu, May 26, 2011 at 2:01 PM, Jake - USPS wrote:
>
> > As for the environments, that is determined from system facts. To
> > load those into foreman there are a couple different ways explained
> > at:http://theforeman.org/projects/foreman/wiki/Puppet_Facts... some
> > other things may also get filled out after doing this. I don't
> > currently use foreman for builds (yet) so I don't have much more info
> > regarding that.
>
> > Also, there is a bug where the environment is set only once when the
> > host is created ... if its changed it doesn't currently get updated to
> > the new environment.
>
> > I'm not sure I understand the whole ENC issue ... so I'll just point
> > you to more documentation. :P
>
> Issue = I don't want Foreman to manage my nodes.
>
> Doug.
>
>> As for the environments, that is determined from system facts. To
>> load those into foreman there are a couple different ways explained
>> at: Puppet Facts - Foreman … some
>> other things may also get filled out after doing this. I don't
>> currently use foreman for builds (yet) so I don't have much more info
>> regarding that.
>>
>> Also, there is a bug where the environment is set only once when the
>> host is created … if its changed it doesn't currently get updated to
>> the new environment.
>>
>> I'm not sure I understand the whole ENC issue … so I'll just point
>> you to more documentation.
>>
>>
> Issue = I don't want Foreman to manage my nodes.
>
Thats not an issue… Foreman was design that you can use the parts you
need…
if you don't plan on using provisioning, you might want to look at disabling
that, so you wont see all of the dropdowns etc.
btw: if your dropdowns are empty, it probably means you didn't import your
puppet data… see the FAQ's.
Ohad
···
On Fri, May 27, 2011 at 12:05 AM, Douglas Garstang wrote:
> On Thu, May 26, 2011 at 2:01 PM, Jake - USPS wrote:
Doug.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
