Hi experts
i am currently running puppetserver 2.7.25
with forman Version 1.5.0
i have 2 questions .
1 . I am trying to understand the Environments in puppet .
how can i implement it in real world env
common development production
why is the default client environment is always production ?
- something unexpected happen to me while working with Env
I have created a test module
i have added 1 Redhat test machine using foreman to the test module
this new test machine run the module without any problems
But i when i added a new Ubuntu machine and configured it as puppet client
.the new ubuntu tried to run the module the module although it was not
added any class in foreman (it failed since the module was written with
Redhat/Centos yum commands . I didn't expect the module to run on the new
Ubuntu machine since i didn't add this module to it in forman , it tried to
"run" it only because the Ubuntu machine was also in production Environment
.
can someone please explain the Flow ???
the Redhat and The Ubuntu were in the Same Env , but i only added classed
to the Redhat machine not to the ubuntu . i didnt expect the Ubuntu machine
to report an error
can someone please explain
thank you
Hi,
I am still struggling with environments, nevertheless…
if you set up environments with puppet on your master, you can import them
to Foreman no problem. I don't understand how you would bring up a
environment from foreman and get puppet classes in it, though.
Environments give you a way to organize your hosts and classes in yet
another way. You could keep different versions of classes in each of the
environments just for an example.
As to your problem… there are many ways a host can receive a puppet class
in foreman… Perhaps you assigned it to a host-group the new host is in.
Environments in foreman influence the classes as well…
If you edit the host you can see all the classes that are run on the host
and where they come from…
Regards, Jochen
···
Am Samstag, 1. November 2014 11:20:53 UTC+1 schrieb Yaniv Fine:
>
> Hi experts
> i am currently running puppetserver 2.7.25
> with forman Version 1.5.0
>
> i have 2 questions .
>
> 1 . I am trying to understand the Environments in puppet .
> how can i implement it in real world env
> common development production
> why is the default client environment is always production ?
>
> 2. something unexpected happen to me while working with Env
> I have created a test module
> i have added 1 Redhat test machine using foreman to the test module
> this new test machine run the module without any problems
> But i when i added a new Ubuntu machine and configured it as puppet client
> .the new ubuntu tried to run the module the module although it was not
> added any class in foreman (it failed since the module was written with
> Redhat/Centos yum commands . I didn't expect the module to run on the new
> Ubuntu machine since i didn't add this module to it in forman , it tried to
> "run" it only because the Ubuntu machine was also in production Environment
> .
> can someone please explain the Flow ???
> the Redhat and The Ubuntu were in the Same Env , but i only added classed
> to the Redhat machine not to the ubuntu . i didnt expect the Ubuntu machine
> to report an error
>
> can someone please explain
> thank you
>
Thank you for the reply.
The classes are generic that I wrote
But they use centos/RH specific commands.
That don't run well on Ubuntu 
···
On Nov 2, 2014 1:57 PM, "Garrett DeMarco" wrote:
What I mean is that since you’re using 2.7, the classes you’re importing
may be meant for 3.
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/8C0rbrTJxKw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Hello! I am also having this issue since upgrading to Foreman 1.5. I have
several environments, namely "test", "development", and "production", and
host groups configured that, when hosts are assigned to them, associate
them with those environments. What I've been noticing is that hosts in,
for instance, my "Default – Test" host group, which is configured to
associate assigned hosts with the "test" environment, are being assigned to
the "production" Puppet environment instead. This is despite verifying
that no environment is defined in the '/etc/puppet/puppet.conf' file on the
host, and confirming that, when editing the host's configuration in
Foreman, the host is assigned to the proper environment.
This was not an issue prior to the Foreman 1.5 upgrade, and I'm wondering
if the issue is Puppet 2.7. I hope to upgrade to the latest version of
Puppet 3.x from the PuppetLabs repo in the next several days, and will
report back if the Puppet upgrade resolves the issue.
Please advise if there is another known issue that those of us encountering
this issue should consider.
Thanks,
– Adam
···
______________________
*J. Adam Craig*
Linux & Windows Operating Systems Engineer
VCU Computer Center
804.828.4886
“Don’t be a phishing victim – VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details,
visit http://infosecurity.vcu.edu/phishing.html”
On Sun, Nov 2, 2014 at 8:58 AM, Yaniv Fine yanivfine@gmail.com wrote:
Thank you for the reply.
The classes are generic that I wrote
But they use centos/RH specific commands.
That don’t run well on Ubuntu
On Nov 2, 2014 1:57 PM, “Garrett DeMarco” garrett.demarco@gmail.com > wrote:
What I mean is that since you’re using 2.7, the classes you’re importing
may be meant for 3.
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/8C0rbrTJxKw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Maybe all machines in an environment. Only "test" if they can run a class
even if the were not explicitly added to a class. Maybe I need to consider
building classes with OS check inside the class???
···
On Nov 3, 2014 4:08 PM, "J. Adam Craig" wrote:
Hello! I am also having this issue since upgrading to Foreman 1.5. I
have several environments, namely “test”, “development”, and “production”,
and host groups configured that, when hosts are assigned to them, associate
them with those environments. What I’ve been noticing is that hosts in,
for instance, my “Default – Test” host group, which is configured to
associate assigned hosts with the “test” environment, are being assigned to
the “production” Puppet environment instead. This is despite verifying
that no environment is defined in the ‘/etc/puppet/puppet.conf’ file on the
host, and confirming that, when editing the host’s configuration in
Foreman, the host is assigned to the proper environment.
This was not an issue prior to the Foreman 1.5 upgrade, and I’m wondering
if the issue is Puppet 2.7. I hope to upgrade to the latest version of
Puppet 3.x from the PuppetLabs repo in the next several days, and will
report back if the Puppet upgrade resolves the issue.
Please advise if there is another known issue that those of us
encountering this issue should consider.
Thanks,
– Adam
J. Adam Craig
Linux & Windows Operating Systems Engineer
VCU Computer Center
804.828.4886
“Don’t be a phishing victim – VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details,
visit http://infosecurity.vcu.edu/phishing.html”
On Sun, Nov 2, 2014 at 8:58 AM, Yaniv Fine yanivfine@gmail.com wrote:
Thank you for the reply.
The classes are generic that I wrote
But they use centos/RH specific commands.
That don’t run well on Ubuntu
On Nov 2, 2014 1:57 PM, “Garrett DeMarco” garrett.demarco@gmail.com >> wrote:
What I mean is that since you’re using 2.7, the classes you’re importing
may be meant for 3.
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/8C0rbrTJxKw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/8C0rbrTJxKw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
