when you click on Provision button on a discovered host, Foreman
actually renders Edit Host page and the Discovery plugin makes some
tricks to use this complex form. This is error prone and there are
multiple issues with this approach (the form renders twice,
organization/location cannot be changed, random bugs).
Since I assume that most of you use Hostgroups provisioning, I was
thinking about complete redesign of the Provision discovered host page
into much simpler form showing the following fields:
Would this be a limitation for you? Do you use some fields found on the
provisioning screen when doing discovery nodes? Opinions?
If this shows to be a wrong path, I need to redesign how we re-use the
form. The New Host form could be enhanced in Foreman Core in a way it
would accept some external input via HTTP request like name, taxonomy
and NICs configuration.
We could even combine both workflows as "Provision" and "Provision via
Hostgroup" buttons so both simple and extended forms are supported. This
would make sense mainly for API (new host form is quite complex).
> Hey,
>
> when you click on Provision button on a discovered host, Foreman
> actually renders Edit Host page and the Discovery plugin makes some
> tricks to use this complex form. This is error prone and there are
> multiple issues with this approach (the form renders twice,
> organization/location cannot be changed, random bugs).
Can you move a Host::Discovered to a different org? If that were the
prerequisite to provisioning in a different org that seems fine to me.
> Since I assume that most of you use Hostgroups provisioning, I was
> thinking about complete redesign of the Provision discovered host page
> into much simpler form showing the following fields:
>
> Name: _____
> Organization: ____
> Location: _____
> Hostgroup: ____
>
> Would this be a limitation for you? Do you use some fields found on the
> provisioning screen when doing discovery nodes? Opinions?
Off hand I see it a problem if users want to configure multiple
interfaces or anything else specific to the host but not host group.
There's not many of those but enough to be a pretty big limitation.
···
On Tue, Aug 25, 2015 at 04:37:34PM +0200, Lukas Zapletal wrote:
If this shows to be a wrong path, I need to redesign how we re-use the
form. The New Host form could be enhanced in Foreman Core in a way it
would accept some external input via HTTP request like name, taxonomy
and NICs configuration.
We could even combine both workflows as “Provision” and “Provision via
Hostgroup” buttons so both simple and extended forms are supported. This
would make sense mainly for API (new host form is quite complex).
