So I figured out that it only interprets the templates when you click the
build button on the host. If you change the template or add parameters to a
host/host group/environment/os, you must cancel the build and click build
again.
···
On Sep 1, 2011 12:19am, Corey Osman wrote:
Is foreman managing your tftp server? This is how foreman inserts the
initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> wrote:
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
> So I figured out that it only interprets the templates when you click
> the build button on the host. If you change the template or add
> parameters to a host/host group/environment/os, you must cancel the
> build and click build again.
Yeah, if you use tftp I dont think there is a way to trigger anything
from foreman side…
Ohad
···
On 09/01/2011 09:47 AM, lavaman@gmail.com wrote:
>
> On Sep 1, 2011 12:19am, Corey Osman wrote:
> >
> > Is foreman managing your tftp server? This is how foreman inserts
> the initrd and kernal entries.
> > On Aug 31, 2011 9:51 PM, "lavaman" lavaman@gmail.com> wrote:
> >
> >
> >
> >
> >
> > --
> >
> > 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.
> >
> >
> >
> > --
> 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.
Maybe you could trigger when dhcp grants a lease to a host in build mode?
I'm still interested in knowing more about how the templates work. It seems
that there are urls in foreman that use the name of the template that
appears on the template page, but the url for the kickstart template that
goes in the pxe template corresponds to a filename in app/view/unattended?
With the included templates, it's not clear what the relationship is between
the foreman name and the filename. It doesn't help that the wiki refers to a
template that is not included (provision), at least not in the rpm from the
yum repo.
>> So I figured out that it only interprets the templates when you click
>> the build button on the host. If you change the template or add
>> parameters to a host/host group/environment/os, you must cancel the
>> build and click build again.
> Yeah, if you use tftp I dont think there is a way to trigger anything
> from foreman side…
>
> Ohad
>>
>> >
>> > Is foreman managing your tftp server? This is how foreman inserts
>> the initrd and kernal entries.
>> >
>> >
>> >
>> >
>> >
>> > –
>> >
>> > 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.
>> >
>> >
>> >
>> > –
>> 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.
>
> –
> 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.
···
On Sep 1, 2011 1:25 AM, "Ohad Levy" wrote:
> On 09/01/2011 09:47 AM, lavaman@gmail.com wrote:
>> On Sep 1, 2011 12:19am, Corey Osman wrote:
>> > On Aug 31, 2011 9:51 PM, "lavaman" lavaman@gmail.com> wrote:
>
> Maybe you could trigger when dhcp grants a lease to a host in build mode?
>
> I'm still interested in knowing more about how the templates work. It seems
> that there are urls in foreman that use the name of the template that
> appears on the template page, but the url for the kickstart template that
> goes in the pxe template corresponds to a filename in app/view/unattended?
> With the included templates, it's not clear what the relationship is between
> the foreman name and the filename. It doesn't help that the wiki refers to a
> template that is not included (provision), at least not in the rpm from the
> yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS's that support it (debian
late command, solaris etc)
script - something that returns a script, for example to update a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration templates) to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are used to
seed the database with working examples, they should not be modified
(they are left there for legacy compatibility, but have no useful
function).
After that, you need to assign the templates to os's etc as defined
here [1] and here [2]
So I figured out that it only interprets the templates when you click
the build button on the host. If you change the template or add
parameters to a host/host group/environment/os, you must cancel the
build and click build again.
Yeah, if you use tftp I dont think there is a way to trigger anything
from foreman side…
Is foreman managing your tftp server? This is how foreman inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> wrote:
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
A little. I guess the problem i'm having is that i have a template of type
provision associated with an os. I've put a client with that os in build
mode and it will boot via pxe and run kickstart, but cannot use the ks url http://foreman/unattended/provision which is in the included pxe kickstart
default template. That url always returns an error stating that there is no
provision.erb in /app/views/unattended.
···
On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy wrote:
Maybe you could trigger when dhcp grants a lease to a host in build mode?
I’m still interested in knowing more about how the templates work. It
seems
that there are urls in foreman that use the name of the template that
appears on the template page, but the url for the kickstart template that
goes in the pxe template corresponds to a filename in
app/view/unattended?
With the included templates, it’s not clear what the relationship is
between
the foreman name and the filename. It doesn’t help that the wiki refers
to a
template that is not included (provision), at least not in the rpm from
the
yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS’s that support it (debian
late command, solaris etc)
script - something that returns a script, for example to update a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration templates) to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are used to
seed the database with working examples, they should not be modified
(they are left there for legacy compatibility, but have no useful
function).
After that, you need to assign the templates to os’s etc as defined
here [1] and here [2]
So I figured out that it only interprets the templates when you click
the build button on the host. If you change the template or add
parameters to a host/host group/environment/os, you must cancel the
build and click build again.
Yeah, if you use tftp I dont think there is a way to trigger anything
from foreman side…
Is foreman managing your tftp server? This is how foreman inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> wrote:
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
> A little. I guess the problem i'm having is that i have a template of type
> provision associated with an os. I've put a client with that os in build
> mode and it will boot via pxe and run kickstart, but cannot use the ks url
> http://foreman/unattended/provision which is in the included pxe kickstart
> default template. That url always returns an error stating that there is no
> provision.erb in /app/views/unattended.
Sounds to me you didnt configure a default OS template… Settings -->
OS --> edit …
Ohad
···
On Thu, Sep 1, 2011 at 7:59 PM, lavaman wrote:
>
> On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy wrote:
>>
>> On Thu, Sep 1, 2011 at 10:51 AM, lavaman wrote:
>> > Maybe you could trigger when dhcp grants a lease to a host in build
>> > mode?
>> >
>> > I'm still interested in knowing more about how the templates work. It
>> > seems
>> > that there are urls in foreman that use the name of the template that
>> > appears on the template page, but the url for the kickstart template
>> > that
>> > goes in the pxe template corresponds to a filename in
>> > app/view/unattended?
>> > With the included templates, it's not clear what the relationship is
>> > between
>> > the foreman name and the filename. It doesn't help that the wiki refers
>> > to a
>> > template that is not included (provision), at least not in the rpm from
>> > the
>> > yum repo.
>> let me try clear it up a bit:
>>
>> There are provisioning types/kinds:
>> PXELinux - tftp based pxebooting
>> gPXE - g/iPXE based booting
>> provision - kickstart, preseed, autoyast, jumpstart etc
>> finish - post installation scripts for OS's that support it (debian
>> late command, solaris etc)
>> script - something that returns a script, for example to update a
>> grub.conf of an existing system
>> PXEGrub - Grub base pxe booting (used only for intel solaris).
>>
>> each of on this types, generate a url, e.g.
>> http://foreman/unattended/provision
>>
>> it depends on the template (settings --> configuration templates) to
>> which type of provisioning they apply to.
>>
>> the templates which are defined in app/views/unattended, are used to
>> seed the database with working examples, they should not be modified
>> (they are left there for legacy compatibility, but have no useful
>> function).
>>
>> After that, you need to assign the templates to os's etc as defined
>> here [1] and here [2]
>>
>> Hope this clears up a bit,
>> Ohad
>>
>> [1] http://theforeman.org/projects/foreman/wiki/Unattended_installations
>> [2] http://theforeman.org/projects/foreman/wiki/TemplateWriting
>>
>>
>>
>>
>>
>> >
>> > On Sep 1, 2011 1:25 AM, "Ohad Levy" wrote:
>> >> On 09/01/2011 09:47 AM, lavaman@gmail.com wrote:
>> >>> So I figured out that it only interprets the templates when you click
>> >>> the build button on the host. If you change the template or add
>> >>> parameters to a host/host group/environment/os, you must cancel the
>> >>> build and click build again.
>> >> Yeah, if you use tftp I dont think there is a way to trigger anything
>> >> from foreman side...
>> >>
>> >> Ohad
>> >>>
>> >>> On Sep 1, 2011 12:19am, Corey Osman wrote:
>> >>> >
>> >>> > Is foreman managing your tftp server? This is how foreman inserts
>> >>> the initrd and kernal entries.
>> >>> > On Aug 31, 2011 9:51 PM, "lavaman" lavaman@gmail.com> wrote:
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> >
>> >>> > 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.
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> 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.
>> >>
>> >> --
>> >> 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.
>> >>
>> >
>> > --
>> > 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.
>> >
>>
>> --
>> 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.
>>
>
> --
> 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.
>
A little. I guess the problem i’m having is that i have a template of
type
provision associated with an os. I’ve put a client with that os in build
mode and it will boot via pxe and run kickstart, but cannot use the ks
url http://foreman/unattended/provision which is in the included pxe
kickstart
default template. That url always returns an error stating that there is
no
provision.erb in /app/views/unattended.
Sounds to me you didnt configure a default OS template… Settings -->
OS --> edit …
Maybe you could trigger when dhcp grants a lease to a host in build
mode?
I’m still interested in knowing more about how the templates work. It
seems
that there are urls in foreman that use the name of the template that
appears on the template page, but the url for the kickstart template
that
goes in the pxe template corresponds to a filename in
app/view/unattended?
With the included templates, it’s not clear what the relationship is
between
the foreman name and the filename. It doesn’t help that the wiki
refers
to a
template that is not included (provision), at least not in the rpm
from
the
yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS’s that support it (debian
late command, solaris etc)
script - something that returns a script, for example to update a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration templates) to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are used to
seed the database with working examples, they should not be modified
(they are left there for legacy compatibility, but have no useful
function).
After that, you need to assign the templates to os’s etc as defined
here [1] and here [2]
So I figured out that it only interprets the templates when you
click
the build button on the host. If you change the template or add
parameters to a host/host group/environment/os, you must cancel the
build and click build again.
Yeah, if you use tftp I dont think there is a way to trigger anything
from foreman side…
Is foreman managing your tftp server? This is how foreman inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> wrote:
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
–
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
.
A little. I guess the problem i’m having is that i have a template of
type
provision associated with an os. I’ve put a client with that os in
build
mode and it will boot via pxe and run kickstart, but cannot use the ks
url http://foreman/unattended/provision which is in the included pxe
kickstart
default template. That url always returns an error stating that there
is no
provision.erb in /app/views/unattended.
Sounds to me you didnt configure a default OS template… Settings -->
OS --> edit …
Maybe you could trigger when dhcp grants a lease to a host in build
mode?
I’m still interested in knowing more about how the templates work.
It
seems
that there are urls in foreman that use the name of the template that
appears on the template page, but the url for the kickstart template
that
goes in the pxe template corresponds to a filename in
app/view/unattended?
With the included templates, it’s not clear what the relationship is
between
the foreman name and the filename. It doesn’t help that the wiki
refers
to a
template that is not included (provision), at least not in the rpm
from
the
yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS’s that support it (debian
late command, solaris etc)
script - something that returns a script, for example to update a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration templates) to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are used to
seed the database with working examples, they should not be modified
(they are left there for legacy compatibility, but have no useful
function).
After that, you need to assign the templates to os’s etc as defined
here [1] and here [2]
So I figured out that it only interprets the templates when you
click
the build button on the host. If you change the template or add
parameters to a host/host group/environment/os, you must cancel the
build and click build again.
Yeah, if you use tftp I dont think there is a way to trigger
anything
Is foreman managing your tftp server? This is how foreman inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> wrote:
–
You received this message because you are subscribed to the
Google
–
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.
–
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
.
> Actually, it was Kickstart default PXElinux
>
>>
>> It's set to PXELinux and Kickstart PXE default…
Can you paste your foreman logs from when a host requests a kickstart?
does it work with spoof?
Ohad
···
On Thu, Sep 1, 2011 at 8:49 PM, lavaman wrote:
> On Thu, Sep 1, 2011 at 11:47 AM, lavaman wrote:
>>
>> On Thu, Sep 1, 2011 at 11:44 AM, Ohad Levy wrote:
>>>
>>> On Thu, Sep 1, 2011 at 7:59 PM, lavaman wrote:
>>> > A little. I guess the problem i'm having is that i have a template of
>>> > type
>>> > provision associated with an os. I've put a client with that os in
>>> > build
>>> > mode and it will boot via pxe and run kickstart, but cannot use the ks
>>> > url
>>> > http://foreman/unattended/provision which is in the included pxe
>>> > kickstart
>>> > default template. That url always returns an error stating that there
>>> > is no
>>> > provision.erb in /app/views/unattended.
>>>
>>> Sounds to me you didnt configure a default OS template.. Settings -->
>>> OS --> edit ...
>>>
>>> Ohad
>>> >
>>> > On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy wrote:
>>> >>
>>> >> On Thu, Sep 1, 2011 at 10:51 AM, lavaman wrote:
>>> >> > Maybe you could trigger when dhcp grants a lease to a host in build
>>> >> > mode?
>>> >> >
>>> >> > I'm still interested in knowing more about how the templates work.
>>> >> > It
>>> >> > seems
>>> >> > that there are urls in foreman that use the name of the template
>>> >> > that
>>> >> > appears on the template page, but the url for the kickstart template
>>> >> > that
>>> >> > goes in the pxe template corresponds to a filename in
>>> >> > app/view/unattended?
>>> >> > With the included templates, it's not clear what the relationship is
>>> >> > between
>>> >> > the foreman name and the filename. It doesn't help that the wiki
>>> >> > refers
>>> >> > to a
>>> >> > template that is not included (provision), at least not in the rpm
>>> >> > from
>>> >> > the
>>> >> > yum repo.
>>> >> let me try clear it up a bit:
>>> >>
>>> >> There are provisioning types/kinds:
>>> >> PXELinux - tftp based pxebooting
>>> >> gPXE - g/iPXE based booting
>>> >> provision - kickstart, preseed, autoyast, jumpstart etc
>>> >> finish - post installation scripts for OS's that support it (debian
>>> >> late command, solaris etc)
>>> >> script - something that returns a script, for example to update a
>>> >> grub.conf of an existing system
>>> >> PXEGrub - Grub base pxe booting (used only for intel solaris).
>>> >>
>>> >> each of on this types, generate a url, e.g.
>>> >> http://foreman/unattended/provision
>>> >>
>>> >> it depends on the template (settings --> configuration templates) to
>>> >> which type of provisioning they apply to.
>>> >>
>>> >> the templates which are defined in app/views/unattended, are used to
>>> >> seed the database with working examples, they should not be modified
>>> >> (they are left there for legacy compatibility, but have no useful
>>> >> function).
>>> >>
>>> >> After that, you need to assign the templates to os's etc as defined
>>> >> here [1] and here [2]
>>> >>
>>> >> Hope this clears up a bit,
>>> >> Ohad
>>> >>
>>> >> [1]
>>> >> http://theforeman.org/projects/foreman/wiki/Unattended_installations
>>> >> [2] http://theforeman.org/projects/foreman/wiki/TemplateWriting
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> >
>>> >> > On Sep 1, 2011 1:25 AM, "Ohad Levy" wrote:
>>> >> >> On 09/01/2011 09:47 AM, lavaman@gmail.com wrote:
>>> >> >>> So I figured out that it only interprets the templates when you
>>> >> >>> click
>>> >> >>> the build button on the host. If you change the template or add
>>> >> >>> parameters to a host/host group/environment/os, you must cancel
>>> >> >>> the
>>> >> >>> build and click build again.
>>> >> >> Yeah, if you use tftp I dont think there is a way to trigger
>>> >> >> anything
>>> >> >> from foreman side...
>>> >> >>
>>> >> >> Ohad
>>> >> >>>
>>> >> >>> On Sep 1, 2011 12:19am, Corey Osman wrote:
>>> >> >>> >
>>> >> >>> > Is foreman managing your tftp server? This is how foreman
>>> >> >>> > inserts
>>> >> >>> the initrd and kernal entries.
>>> >> >>> > On Aug 31, 2011 9:51 PM, "lavaman" lavaman@gmail.com> wrote:
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > --
>>> >> >>> >
>>> >> >>> > 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.
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > --
>>> >> >>> 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.
>>> >> >>
>>> >> >> --
>>> >> >> 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.
>>> >> >>
>>> >> >
>>> >> > --
>>> >> > 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.
>>> >> >
>>> >>
>>> >> --
>>> >> 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.
>>> >>
>>> >
>>> > --
>>> > 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.
>>> >
>>>
>>> --
>>> 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.
>>>
>>
>
> --
> 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.
>
Maybe you could trigger when dhcp grants a lease to a host in
build
mode?
I’m still interested in knowing more about how the templates work.
It
seems
that there are urls in foreman that use the name of the template
that
appears on the template page, but the url for the kickstart
template
that
goes in the pxe template corresponds to a filename in
app/view/unattended?
With the included templates, it’s not clear what the relationship
is
between
the foreman name and the filename. It doesn’t help that the wiki
refers
to a
template that is not included (provision), at least not in the rpm
from
the
yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS’s that support it (debian
late command, solaris etc)
script - something that returns a script, for example to update a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration templates) to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are used to
seed the database with working examples, they should not be modified
(they are left there for legacy compatibility, but have no useful
function).
After that, you need to assign the templates to os’s etc as defined
here [1] and here [2]
So I figured out that it only interprets the templates when you
click
the build button on the host. If you change the template or add
parameters to a host/host group/environment/os, you must cancel
the
build and click build again.
Yeah, if you use tftp I dont think there is a way to trigger
anything
from foreman side…
Is foreman managing your tftp server? This is how foreman
inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> wrote:
–
You received this message because you are subscribed to the
Google
Groups “Foreman users” group.
–
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.
–
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
.
without thinking too much, it sounds to me like you dont have template
assigned to the host os, if you edit the host and click on
provisioning templates, does it show the right templates?
Ohad
···
On Thu, Sep 1, 2011 at 9:19 PM, lavaman wrote:
> I get the same error with a spoof or via kickstart. Here is the log entry
> from a spoof:
>
> Processing UnattendedController#provision (for 192.168.2.4 at 2011-08-31
> 21:22:10) [GET]
> Parameters: {"spoof"=>"192.168.0.3"}
> Found client.test.com
>
> ActionView::MissingTemplate (Missing template unattended/provision.erb in
> view path app/views):
> passenger (2.2.2) lib/phusion_passenger/rack/request_handler.rb:81:in
> `process_request'
> passenger (2.2.2) lib/phusion_passenger/abstract_request_handler.rb:203:in
> `main_loop'
> passenger (2.2.2)
> lib/phusion_passenger/railz/application_spawner.rb:340:in
> `start_request_handler'
> passenger (2.2.2)
> lib/phusion_passenger/railz/application_spawner.rb:298:in
> `handle_spawn_application'
> passenger (2.2.2) lib/phusion_passenger/utils.rb:181:in `safe_fork'
> passenger (2.2.2)
> lib/phusion_passenger/railz/application_spawner.rb:296:in
> `handle_spawn_application'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
> `__send__'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
> `main_loop'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:187:in
> `start_synchronously'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:154:in `start'
> passenger (2.2.2)
> lib/phusion_passenger/railz/application_spawner.rb:192:in `start'
> passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:257:in
> `spawn_rails_application'
> passenger (2.2.2)
> lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
> passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:251:in
> `spawn_rails_application'
> passenger (2.2.2)
> lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
> passenger (2.2.2)
> lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
> passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:250:in
> `spawn_rails_application'
> passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:153:in
> `spawn_application'
> passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:282:in
> `handle_spawn_application'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
> `__send__'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
> `main_loop'
> passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:187:in
> `start_synchronously'
>
> Rendering /usr/share/foreman/public/500.html (500 Internal Server Error)
>
>
>
> On Thu, Sep 1, 2011 at 11:51 AM, Ohad Levy wrote:
>>
>> On Thu, Sep 1, 2011 at 8:49 PM, lavaman wrote:
>> > Actually, it was Kickstart default PXElinux
>> >
>> > On Thu, Sep 1, 2011 at 11:47 AM, lavaman wrote:
>> >>
>> >> It's set to PXELinux and Kickstart PXE default...
>>
>> Can you paste your foreman logs from when a host requests a kickstart?
>>
>> does it work with spoof?
>>
>> Ohad
>> >>
>> >> On Thu, Sep 1, 2011 at 11:44 AM, Ohad Levy wrote:
>> >>>
>> >>> On Thu, Sep 1, 2011 at 7:59 PM, lavaman wrote:
>> >>> > A little. I guess the problem i'm having is that i have a template
>> >>> > of
>> >>> > type
>> >>> > provision associated with an os. I've put a client with that os in
>> >>> > build
>> >>> > mode and it will boot via pxe and run kickstart, but cannot use the
>> >>> > ks
>> >>> > url
>> >>> > http://foreman/unattended/provision which is in the included pxe
>> >>> > kickstart
>> >>> > default template. That url always returns an error stating that
>> >>> > there
>> >>> > is no
>> >>> > provision.erb in /app/views/unattended.
>> >>>
>> >>> Sounds to me you didnt configure a default OS template.. Settings -->
>> >>> OS --> edit ...
>> >>>
>> >>> Ohad
>> >>> >
>> >>> > On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy >> >>> > wrote:
>> >>> >>
>> >>> >> On Thu, Sep 1, 2011 at 10:51 AM, lavaman wrote:
>> >>> >> > Maybe you could trigger when dhcp grants a lease to a host in
>> >>> >> > build
>> >>> >> > mode?
>> >>> >> >
>> >>> >> > I'm still interested in knowing more about how the templates
>> >>> >> > work.
>> >>> >> > It
>> >>> >> > seems
>> >>> >> > that there are urls in foreman that use the name of the template
>> >>> >> > that
>> >>> >> > appears on the template page, but the url for the kickstart
>> >>> >> > template
>> >>> >> > that
>> >>> >> > goes in the pxe template corresponds to a filename in
>> >>> >> > app/view/unattended?
>> >>> >> > With the included templates, it's not clear what the relationship
>> >>> >> > is
>> >>> >> > between
>> >>> >> > the foreman name and the filename. It doesn't help that the wiki
>> >>> >> > refers
>> >>> >> > to a
>> >>> >> > template that is not included (provision), at least not in the
>> >>> >> > rpm
>> >>> >> > from
>> >>> >> > the
>> >>> >> > yum repo.
>> >>> >> let me try clear it up a bit:
>> >>> >>
>> >>> >> There are provisioning types/kinds:
>> >>> >> PXELinux - tftp based pxebooting
>> >>> >> gPXE - g/iPXE based booting
>> >>> >> provision - kickstart, preseed, autoyast, jumpstart etc
>> >>> >> finish - post installation scripts for OS's that support it (debian
>> >>> >> late command, solaris etc)
>> >>> >> script - something that returns a script, for example to update a
>> >>> >> grub.conf of an existing system
>> >>> >> PXEGrub - Grub base pxe booting (used only for intel solaris).
>> >>> >>
>> >>> >> each of on this types, generate a url, e.g.
>> >>> >> http://foreman/unattended/provision
>> >>> >>
>> >>> >> it depends on the template (settings --> configuration templates)
>> >>> >> to
>> >>> >> which type of provisioning they apply to.
>> >>> >>
>> >>> >> the templates which are defined in app/views/unattended, are used
>> >>> >> to
>> >>> >> seed the database with working examples, they should not be
>> >>> >> modified
>> >>> >> (they are left there for legacy compatibility, but have no useful
>> >>> >> function).
>> >>> >>
>> >>> >> After that, you need to assign the templates to os's etc as defined
>> >>> >> here [1] and here [2]
>> >>> >>
>> >>> >> Hope this clears up a bit,
>> >>> >> Ohad
>> >>> >>
>> >>> >> [1]
>> >>> >>
>> >>> >> http://theforeman.org/projects/foreman/wiki/Unattended_installations
>> >>> >> [2] http://theforeman.org/projects/foreman/wiki/TemplateWriting
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> >
>> >>> >> > On Sep 1, 2011 1:25 AM, "Ohad Levy" wrote:
>> >>> >> >> On 09/01/2011 09:47 AM, lavaman@gmail.com wrote:
>> >>> >> >>> So I figured out that it only interprets the templates when you
>> >>> >> >>> click
>> >>> >> >>> the build button on the host. If you change the template or add
>> >>> >> >>> parameters to a host/host group/environment/os, you must cancel
>> >>> >> >>> the
>> >>> >> >>> build and click build again.
>> >>> >> >> Yeah, if you use tftp I dont think there is a way to trigger
>> >>> >> >> anything
>> >>> >> >> from foreman side...
>> >>> >> >>
>> >>> >> >> Ohad
>> >>> >> >>>
>> >>> >> >>> On Sep 1, 2011 12:19am, Corey Osman >> >>> >> >>> wrote:
>> >>> >> >>> >
>> >>> >> >>> > Is foreman managing your tftp server? This is how foreman
>> >>> >> >>> > inserts
>> >>> >> >>> the initrd and kernal entries.
>> >>> >> >>> > On Aug 31, 2011 9:51 PM, "lavaman" lavaman@gmail.com> wrote:
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> > --
>> >>> >> >>> >
>> >>> >> >>> > 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.
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> > --
>> >>> >> >>> 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.
>> >>> >> >>
>> >>> >> >> --
>> >>> >> >> 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.
>> >>> >> >>
>> >>> >> >
>> >>> >> > --
>> >>> >> > 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.
>> >>> >> >
>> >>> >>
>> >>> >> --
>> >>> >> 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.
>> >>> >>
>> >>> >
>> >>> > --
>> >>> > 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.
>> >>> >
>> >>>
>> >>> --
>> >>> 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.
>> >>>
>> >>
>> >
>> > --
>> > 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.
>> >
>>
>> --
>> 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.
>>
>
> --
> 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.
>
Yes. It shows the same templates that are assigned to the os.
···
On Thu, Sep 1, 2011 at 12:48 PM, Ohad Levy wrote:
without thinking too much, it sounds to me like you dont have template
assigned to the host os, if you edit the host and click on
provisioning templates, does it show the right templates?
A little. I guess the problem i’m having is that i have a
template
of
type
provision associated with an os. I’ve put a client with that os
in
build
mode and it will boot via pxe and run kickstart, but cannot use
the
ks
url http://foreman/unattended/provision which is in the included pxe
kickstart
default template. That url always returns an error stating that
there
is no
provision.erb in /app/views/unattended.
Sounds to me you didnt configure a default OS template… Settings
–>
OS --> edit …
Ohad
On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy ohadlevy@gmail.com > >> >>> > wrote:
Maybe you could trigger when dhcp grants a lease to a host in
build
mode?
I’m still interested in knowing more about how the templates
work.
It
seems
that there are urls in foreman that use the name of the
template
that
appears on the template page, but the url for the kickstart
template
that
goes in the pxe template corresponds to a filename in
app/view/unattended?
With the included templates, it’s not clear what the
relationship
is
between
the foreman name and the filename. It doesn’t help that the
wiki
refers
to a
template that is not included (provision), at least not in the
rpm
from
the
yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS’s that support it
(debian
late command, solaris etc)
script - something that returns a script, for example to update a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration templates)
to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are used
to
seed the database with working examples, they should not be
modified
(they are left there for legacy compatibility, but have no useful
function).
After that, you need to assign the templates to os’s etc as
defined
Is foreman managing your tftp server? This is how foreman
inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> > wrote:
–
You received this message because you are subscribed to the
Google
Groups “Foreman users” group.
–
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.
–
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
.
> Yes. It shows the same templates that are assigned to the os.
I'm just guessing, but can you try to have a simple one liner template
in your KS provisioning template?
Ohad
···
On Thu, Sep 1, 2011 at 9:51 PM, lavaman wrote:
>
> On Thu, Sep 1, 2011 at 12:48 PM, Ohad Levy wrote:
>>
>> without thinking too much, it sounds to me like you dont have template
>> assigned to the host os, if you edit the host and click on
>> provisioning templates, does it show the right templates?
>>
>> Ohad
>>
>> On Thu, Sep 1, 2011 at 9:19 PM, lavaman wrote:
>> > I get the same error with a spoof or via kickstart. Here is the log
>> > entry
>> > from a spoof:
>> >
>> > Processing UnattendedController#provision (for 192.168.2.4 at 2011-08-31
>> > 21:22:10) [GET]
>> > Parameters: {"spoof"=>"192.168.0.3"}
>> > Found client.test.com
>> >
>> > ActionView::MissingTemplate (Missing template unattended/provision.erb
>> > in
>> > view path app/views):
>> > passenger (2.2.2) lib/phusion_passenger/rack/request_handler.rb:81:in
>> > `process_request'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/abstract_request_handler.rb:203:in
>> > `main_loop'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/railz/application_spawner.rb:340:in
>> > `start_request_handler'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/railz/application_spawner.rb:298:in
>> > `handle_spawn_application'
>> > passenger (2.2.2) lib/phusion_passenger/utils.rb:181:in `safe_fork'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/railz/application_spawner.rb:296:in
>> > `handle_spawn_application'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
>> > `__send__'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
>> > `main_loop'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:187:in
>> > `start_synchronously'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:154:in
>> > `start'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/railz/application_spawner.rb:192:in `start'
>> > passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:257:in
>> > `spawn_rails_application'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/abstract_server_collection.rb:126:in
>> > `lookup_or_add'
>> > passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:251:in
>> > `spawn_rails_application'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
>> > passenger (2.2.2)
>> > lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
>> > passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:250:in
>> > `spawn_rails_application'
>> > passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:153:in
>> > `spawn_application'
>> > passenger (2.2.2) lib/phusion_passenger/spawn_manager.rb:282:in
>> > `handle_spawn_application'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
>> > `__send__'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:337:in
>> > `main_loop'
>> > passenger (2.2.2) lib/phusion_passenger/abstract_server.rb:187:in
>> > `start_synchronously'
>> >
>> > Rendering /usr/share/foreman/public/500.html (500 Internal Server Error)
>> >
>> >
>> >
>> > On Thu, Sep 1, 2011 at 11:51 AM, Ohad Levy wrote:
>> >>
>> >> On Thu, Sep 1, 2011 at 8:49 PM, lavaman wrote:
>> >> > Actually, it was Kickstart default PXElinux
>> >> >
>> >> > On Thu, Sep 1, 2011 at 11:47 AM, lavaman wrote:
>> >> >>
>> >> >> It's set to PXELinux and Kickstart PXE default...
>> >>
>> >> Can you paste your foreman logs from when a host requests a kickstart?
>> >>
>> >> does it work with spoof?
>> >>
>> >> Ohad
>> >> >>
>> >> >> On Thu, Sep 1, 2011 at 11:44 AM, Ohad Levy >> >> >> wrote:
>> >> >>>
>> >> >>> On Thu, Sep 1, 2011 at 7:59 PM, lavaman wrote:
>> >> >>> > A little. I guess the problem i'm having is that i have a
>> >> >>> > template
>> >> >>> > of
>> >> >>> > type
>> >> >>> > provision associated with an os. I've put a client with that os
>> >> >>> > in
>> >> >>> > build
>> >> >>> > mode and it will boot via pxe and run kickstart, but cannot use
>> >> >>> > the
>> >> >>> > ks
>> >> >>> > url
>> >> >>> > http://foreman/unattended/provision which is in the included pxe
>> >> >>> > kickstart
>> >> >>> > default template. That url always returns an error stating that
>> >> >>> > there
>> >> >>> > is no
>> >> >>> > provision.erb in /app/views/unattended.
>> >> >>>
>> >> >>> Sounds to me you didnt configure a default OS template.. Settings
>> >> >>> -->
>> >> >>> OS --> edit ...
>> >> >>>
>> >> >>> Ohad
>> >> >>> >
>> >> >>> > On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy >> >> >>> > wrote:
>> >> >>> >>
>> >> >>> >> On Thu, Sep 1, 2011 at 10:51 AM, lavaman >> >> >>> >> wrote:
>> >> >>> >> > Maybe you could trigger when dhcp grants a lease to a host in
>> >> >>> >> > build
>> >> >>> >> > mode?
>> >> >>> >> >
>> >> >>> >> > I'm still interested in knowing more about how the templates
>> >> >>> >> > work.
>> >> >>> >> > It
>> >> >>> >> > seems
>> >> >>> >> > that there are urls in foreman that use the name of the
>> >> >>> >> > template
>> >> >>> >> > that
>> >> >>> >> > appears on the template page, but the url for the kickstart
>> >> >>> >> > template
>> >> >>> >> > that
>> >> >>> >> > goes in the pxe template corresponds to a filename in
>> >> >>> >> > app/view/unattended?
>> >> >>> >> > With the included templates, it's not clear what the
>> >> >>> >> > relationship
>> >> >>> >> > is
>> >> >>> >> > between
>> >> >>> >> > the foreman name and the filename. It doesn't help that the
>> >> >>> >> > wiki
>> >> >>> >> > refers
>> >> >>> >> > to a
>> >> >>> >> > template that is not included (provision), at least not in the
>> >> >>> >> > rpm
>> >> >>> >> > from
>> >> >>> >> > the
>> >> >>> >> > yum repo.
>> >> >>> >> let me try clear it up a bit:
>> >> >>> >>
>> >> >>> >> There are provisioning types/kinds:
>> >> >>> >> PXELinux - tftp based pxebooting
>> >> >>> >> gPXE - g/iPXE based booting
>> >> >>> >> provision - kickstart, preseed, autoyast, jumpstart etc
>> >> >>> >> finish - post installation scripts for OS's that support it
>> >> >>> >> (debian
>> >> >>> >> late command, solaris etc)
>> >> >>> >> script - something that returns a script, for example to update
>> >> >>> >> a
>> >> >>> >> grub.conf of an existing system
>> >> >>> >> PXEGrub - Grub base pxe booting (used only for intel solaris).
>> >> >>> >>
>> >> >>> >> each of on this types, generate a url, e.g.
>> >> >>> >> http://foreman/unattended/provision
>> >> >>> >>
>> >> >>> >> it depends on the template (settings --> configuration
>> >> >>> >> templates)
>> >> >>> >> to
>> >> >>> >> which type of provisioning they apply to.
>> >> >>> >>
>> >> >>> >> the templates which are defined in app/views/unattended, are
>> >> >>> >> used
>> >> >>> >> to
>> >> >>> >> seed the database with working examples, they should not be
>> >> >>> >> modified
>> >> >>> >> (they are left there for legacy compatibility, but have no
>> >> >>> >> useful
>> >> >>> >> function).
>> >> >>> >>
>> >> >>> >> After that, you need to assign the templates to os's etc as
>> >> >>> >> defined
>> >> >>> >> here [1] and here [2]
>> >> >>> >>
>> >> >>> >> Hope this clears up a bit,
>> >> >>> >> Ohad
>> >> >>> >>
>> >> >>> >> [1]
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> http://theforeman.org/projects/foreman/wiki/Unattended_installations
>> >> >>> >> [2] http://theforeman.org/projects/foreman/wiki/TemplateWriting
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> >
>> >> >>> >> > On Sep 1, 2011 1:25 AM, "Ohad Levy" >> >> >>> >> > wrote:
>> >> >>> >> >> On 09/01/2011 09:47 AM, lavaman@gmail.com wrote:
>> >> >>> >> >>> So I figured out that it only interprets the templates when
>> >> >>> >> >>> you
>> >> >>> >> >>> click
>> >> >>> >> >>> the build button on the host. If you change the template or
>> >> >>> >> >>> add
>> >> >>> >> >>> parameters to a host/host group/environment/os, you must
>> >> >>> >> >>> cancel
>> >> >>> >> >>> the
>> >> >>> >> >>> build and click build again.
>> >> >>> >> >> Yeah, if you use tftp I dont think there is a way to trigger
>> >> >>> >> >> anything
>> >> >>> >> >> from foreman side...
>> >> >>> >> >>
>> >> >>> >> >> Ohad
>> >> >>> >> >>>
>> >> >>> >> >>> On Sep 1, 2011 12:19am, Corey Osman >> >> >>> >> >>> wrote:
>> >> >>> >> >>> >
>> >> >>> >> >>> > Is foreman managing your tftp server? This is how foreman
>> >> >>> >> >>> > inserts
>> >> >>> >> >>> the initrd and kernal entries.
>> >> >>> >> >>> > On Aug 31, 2011 9:51 PM, "lavaman" lavaman@gmail.com> >> >> >>> >> >>> > wrote:
>> >> >>> >> >>> >
>> >> >>> >> >>> >
>> >> >>> >> >>> >
>> >> >>> >> >>> >
>> >> >>> >> >>> >
>> >> >>> >> >>> > --
>> >> >>> >> >>> >
>> >> >>> >> >>> > 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.
>> >> >>> >> >>> >
>> >> >>> >> >>> >
>> >> >>> >> >>> >
>> >> >>> >> >>> > --
>> >> >>> >> >>> 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.
>> >> >>> >> >>
>> >> >>> >> >> --
>> >> >>> >> >> 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.
>> >> >>> >> >>
>> >> >>> >> >
>> >> >>> >> > --
>> >> >>> >> > 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.
>> >> >>> >> >
>> >> >>> >>
>> >> >>> >> --
>> >> >>> >> 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.
>> >> >>> >>
>> >> >>> >
>> >> >>> > --
>> >> >>> > 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.
>> >> >>> >
>> >> >>>
>> >> >>> --
>> >> >>> 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.
>> >> >>>
>> >> >>
>> >> >
>> >> > --
>> >> > 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.
>> >> >
>> >>
>> >> --
>> >> 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.
>> >>
>> >
>> > --
>> > 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.
>> >
>>
>> --
>> 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.
>>
>
> --
> 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.
>
without thinking too much, it sounds to me like you dont have template
assigned to the host os, if you edit the host and click on
provisioning templates, does it show the right templates?
A little. I guess the problem i’m having is that i have a
template
of
type
provision associated with an os. I’ve put a client with that
os
in
build
mode and it will boot via pxe and run kickstart, but cannot use
the
ks
url http://foreman/unattended/provision which is in the included
pxe
kickstart
default template. That url always returns an error stating
that
there
is no
provision.erb in /app/views/unattended.
Sounds to me you didnt configure a default OS template… Settings
–>
OS --> edit …
Ohad
On Thu, Sep 1, 2011 at 2:01 AM, Ohad Levy ohadlevy@gmail.com > >> >> >>> > wrote:
On Thu, Sep 1, 2011 at 10:51 AM, lavaman lavaman@gmail.com > >> >> >>> >> wrote:
Maybe you could trigger when dhcp grants a lease to a host
in
build
mode?
I’m still interested in knowing more about how the templates
work.
It
seems
that there are urls in foreman that use the name of the
template
that
appears on the template page, but the url for the kickstart
template
that
goes in the pxe template corresponds to a filename in
app/view/unattended?
With the included templates, it’s not clear what the
relationship
is
between
the foreman name and the filename. It doesn’t help that the
wiki
refers
to a
template that is not included (provision), at least not in
the
rpm
from
the
yum repo.
let me try clear it up a bit:
There are provisioning types/kinds:
PXELinux - tftp based pxebooting
gPXE - g/iPXE based booting
provision - kickstart, preseed, autoyast, jumpstart etc
finish - post installation scripts for OS’s that support it
(debian
late command, solaris etc)
script - something that returns a script, for example to
update
a
grub.conf of an existing system
PXEGrub - Grub base pxe booting (used only for intel solaris).
it depends on the template (settings --> configuration
templates)
to
which type of provisioning they apply to.
the templates which are defined in app/views/unattended, are
used
to
seed the database with working examples, they should not be
modified
(they are left there for legacy compatibility, but have no
useful
function).
After that, you need to assign the templates to os’s etc as
defined
here [1] and here [2]
So I figured out that it only interprets the templates
when
you
click
the build button on the host. If you change the template
or
add
parameters to a host/host group/environment/os, you must
cancel
the
build and click build again.
Yeah, if you use tftp I dont think there is a way to
trigger
anything
from foreman side…
Ohad
On Sep 1, 2011 12:19am, Corey Osman <corey@logicminds.biz > > > >> >> >>> >> >>> wrote:
Is foreman managing your tftp server? This is how
foreman
inserts
the initrd and kernal entries.
On Aug 31, 2011 9:51 PM, “lavaman” lavaman@gmail.com> > >> >> >>> >> >>> > wrote:
–
You received this message because you are subscribed to
the
Google
Groups “Foreman users” group.
–
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.
