Looks like that Foreman doesn't support subclasses. You can configure it
via GUI, but on puppet run it will not be applied to the node.
Please confirm that it is by-design behavior or not. If yes, can you please
add this to documentation and block it at GUI level.
Thanks in advance!
Subclasses as in module:classnameA:classnameB?
If so, Foreman absolutely supports this. You should see Foreman pass this
in the ENC output.
Josh
···
On Wed, Sep 18, 2013 at 5:34 PM, Alexey Savva wrote:Looks like that Foreman doesn’t support subclasses. You can configure it
via GUI, but on puppet run it will not be applied to the node.
Please confirm that it is by-design behavior or not. If yes, can you
please add this to documentation and block it at GUI level.
Thanks in advance!–
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/groups/opt_out.
I'm probably doing it all wrong, but in my experience I have not been able
to define parameters for subclasses in the gui. I tend to define subclass
params in a wrapper class. Is there a better way to do this within the gui?
Also, for a long time, I was confused on the difference between a defined
resource and a subclass. Foreman seems to have no mechanism to define a
resource for a host. A wrapper class is needed for these.
···
On Wed, Sep 18, 2013 at 6:01 PM, Josh Baird wrote:Subclasses as in module:classnameA:classnameB?
If so, Foreman absolutely supports this. You should see Foreman pass this
in the ENC output.Josh
On Wed, Sep 18, 2013 at 5:34 PM, Alexey Savva alex.savva@gmail.comwrote:
Looks like that Foreman doesn’t support subclasses. You can configure it
via GUI, but on puppet run it will not be applied to the node.
Please confirm that it is by-design behavior or not. If yes, can you
please add this to documentation and block it at GUI level.
Thanks in advance!–
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/groups/opt_out.–
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/groups/opt_out.
–
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
300 College Park
Dayton, Ohio 45469-1530
(937) 229-5088
salderman1@udayton.edu
“We are not some casual and meaningless product of evolution. Each of us
is the result of a thought of God. Each of us is willed. Each of us is
loved. Each of us is necessary.” - BXVI
> I'm probably doing it all wrong, but in my experience I have not been able
> to define parameters for subclasses in the gui. I tend to define subclass
> params in a wrapper class. Is there a better way to do this within the gui?
>
Thats very dependant on how your modules are structured. If you have "class
foo::bar ($quux=false) {}" then obviously assigning "foo::bar" to your Host
in Foreman will allow you to control the value of "quux", but if the
top-level class "foo" doesn't pass it through, then you've no way to
control it from Foreman by just adding foo. This snippet should work for
you as an example:
class foo ($quxx=false) {
include foo::bar
}
class foo::bar {
notify { "quux is ${foo::quux}": }
}
When a module correctly inherits it's parameters from the topclass, you
should have no issues passing variables in from the ENC. Check our
installer modules for more complex examples, they all do this.
Also, for a long time, I was confused on the difference between a defined
> resource and a subclass. Foreman seems to have no mechanism to define a
> resource for a host. A wrapper class is needed for these.
>
That's not a Foreman limitation, it's a Puppet one - no ENC can declare
defines.
Greg