I don't see a way to schedule any tasks through RemoteExecution plug-in on
discovered hosts - is this not supported? Is it going to be and there's a
work in progress on this?
I have been hoping to use RemoteExecution on both provisioned and
discovered hosts for HW/FW management and configuration tasks - RAID
configuration, FW updates, etc.
Having this available for discovered hosts makes perfect sense for HW fleet
management as such systems are not being used and thus present themselves
as perfect candidates for such tasks, especially if some of those tasks may
require a reboot (for example after FW updates) - while FW update itself
usually possible on production systems, rebooting them to take the effect
would be disruptive for running workload/applications. And that's why I
believe discovered hosts should be targeted for such HW life-cycle tasks
because of their state.
Please let me know if this makes sense to you. Technically I don't see any
reason why that cannot be implemented in conjunction with FDI which only
needs a Foreman RemoteExec SSH public key installed on it.
> From: "'Konstantin Orekhov' via Foreman users" <foreman-users@googlegroups.com>
> To: "Foreman users" <foreman-users@googlegroups.com>
> Sent: Wednesday, May 18, 2016 3:42:50 PM
> Subject: [foreman-users] RemoteExecution not available for discovered hosts?
>
> Hello there!
>
> I don't see a way to schedule any tasks through RemoteExecution plug-in on
> discovered hosts - is this not supported?
Not currently, unfortunately
> Is it going to be and there's a work in progress on this?
We are definitely interested in doing it. It needs a little code refactoring to make
it work with discovered hosts.
I have been hoping to use RemoteExecution on both provisioned and
discovered hosts for HW/FW management and configuration tasks - RAID
configuration, FW updates, etc.
Having this available for discovered hosts makes perfect sense for HW fleet
management as such systems are not being used and thus present themselves
as perfect candidates for such tasks, especially if some of those tasks may
require a reboot (for example after FW updates) - while FW update itself
usually possible on production systems, rebooting them to take the effect
would be disruptive for running workload/applications. And that’s why I
believe discovered hosts should be targeted for such HW life-cycle tasks
because of their state.
Please let me know if this makes sense to you. Technically I don’t see any
reason why that cannot be implemented in conjunction with FDI which only
needs a Foreman RemoteExec SSH public key installed on it.
Thanks for your reply, Benjamin!
I've voted up on that feature request. I don't assume you have any idea for a timeline for this, do you?
Konstantin Orekhov
···
From: Stephen Benjamin
To: foreman-users@googlegroups.com
Sent: Wednesday, May 18, 2016 1:36 PM
Subject: Re: [foreman-users] RemoteExecution not available for discovered hosts?
Hi,
----- Original Message -----
From: “‘Konstantin Orekhov’ via Foreman users” foreman-users@googlegroups.com
To: “Foreman users” foreman-users@googlegroups.com
Sent: Wednesday, May 18, 2016 3:42:50 PM
Subject: [foreman-users] RemoteExecution not available for discovered hosts?
Hello there!
I don’t see a way to schedule any tasks through RemoteExecution plug-in on
discovered hosts - is this not supported?
Not currently, unfortunately
Is it going to be and there’s a work in progress on this?
We are definitely interested in doing it. It needs a little code refactoring to make
it work with discovered hosts.
I have been hoping to use RemoteExecution on both provisioned and
discovered hosts for HW/FW management and configuration tasks - RAID
configuration, FW updates, etc.
Having this available for discovered hosts makes perfect sense for HW fleet
management as such systems are not being used and thus present themselves
as perfect candidates for such tasks, especially if some of those tasks may
require a reboot (for example after FW updates) - while FW update itself
usually possible on production systems, rebooting them to take the effect
would be disruptive for running workload/applications. And that’s why I
believe discovered hosts should be targeted for such HW life-cycle tasks
because of their state.
Please let me know if this makes sense to you. Technically I don’t see any
reason why that cannot be implemented in conjunction with FDI which only
needs a Foreman RemoteExec SSH public key installed on it.
Are there any new developments on this topic? I'd love to have an ability
to run tasks on discovered hosts before they are provisioned - RAID
reconfiguration, BMC operations on users, BIOS
settings/verification/reconfiguration, firmware updates on HW components,
HW diagnostics and burn-in, etc.
I'm sure other folks will find more uses for this feature.
Planned feature, we were talking about this at FOSDEM 2017, but not
sure when I get to this.
File a ticket and feel free to take a look, should be pretty easy
(deploy ssh key via kernel command line, add support for discovered
hosts in REX, job done).
LZ
···
On Tue, Feb 28, 2017 at 12:03 AM, 'Konstantin Orekhov' via Foreman users wrote:
> Hello there!
>
> Are there any new developments on this topic? I'd love to have an ability to
> run tasks on discovered hosts before they are provisioned - RAID
> reconfiguration, BMC operations on users, BIOS
> settings/verification/reconfiguration, firmware updates on HW components, HW
> diagnostics and burn-in, etc.
>
> I'm sure other folks will find more uses for this feature.
>
> Thanks!
>
> --
> 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 https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
> Planned feature, we were talking about this at FOSDEM 2017, but not
> sure when I get to this.
>
> File a ticket and feel free to take a look, should be pretty easy
> (deploy ssh key via kernel command line, add support for discovered
> hosts in REX, job done).
>
Are there any new developments on this topic? I’d love to have an
ability to
run tasks on discovered hosts before they are provisioned - RAID
reconfiguration, BMC operations on users, BIOS
settings/verification/reconfiguration, firmware updates on HW
components, HW
diagnostics and burn-in, etc.
I’m sure other folks will find more uses for this feature.
> File a ticket and feel free to take a look, should be pretty easy
> (deploy ssh key via kernel command line, add support for discovered
> hosts in REX, job done).
>
As Ohad already mentioned below, there's already a feature request opened
for this for several months now. I was already told that this should be
rather easy to implement, but it seems nobody can get to it just yet.
I'd much appreciate it though.
One thing in regards to SSH key distribution - one of the other
possibilities is include it directly in the image (for those of us who
builds their own FDI), the other could be a part of the zip-file or a GIT
repo.
BTW, has anyone tried to pull the content of zip-file off GIT? I'd rather
have that than a zip-file. Much easier to maintain. Just my 2 cents.
> One thing in regards to SSH key distribution - one of the other
> possibilities is include it directly in the image (for those of us who
> builds their own FDI), the other could be a part of the zip-file or a GIT
> repo.
The plan is to provide the ssh key via kernel command line. It should
fit, I think it is 128kB in red hats and most distros.
