How to display IPMI consoles in the Foreman?

Support
1

Hi,

Is there any way to display the console of IPMI (aka iDrac in Dell or iLo
in HP) in the foreman? I believe this would a good idea to have on the
hosts section which are deployed as a metal metal servers.

If it's not possible then is there any other alternative for this?

Please let me know.

Thanks,
No1.

2

We use conman, https://github.com/dun/conman, which is in the RHEL OS repos. Be great if this kind of functionality existed in Foreman.

3

I believe the original poster was interested in using the iKVM that is
part of most BMC chipsets now days.

I think that is a lot harder because the chipsets use a java based
VNC-like protocol that is proprietary.

··· On 10/20/2017 09:03 PM, treydock wrote: > We use conman, https://github.com/dun/conman, which is in the RHEL OS repos. Be great if this kind of functionality existed in Foreman. >

–
Alvin Starr || land: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
alvin@netvel.net ||

4

FWIW, idrac also exposes VNC

··· On Fri, Oct 20, 2017 at 9:21 PM Alvin Starr wrote:

I believe the original poster was interested in using the iKVM that is
part of most BMC chipsets now days.

I think that is a lot harder because the chipsets use a java based
VNC-like protocol that is proprietary.

On 10/20/2017 09:03 PM, treydock wrote:

We use conman, https://github.com/dun/conman, which is in the RHEL OS
repos. Be great if this kind of functionality existed in Foreman.

–
Alvin Starr || land: (905)513-7688 <(905)%20513-7688>
Netvel Inc. || Cell: (416)806-0133 <(416)%20806-0133>
alvin@netvel.net ||

–
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.

5

Hi Neil,

I know I can use any standalone VNC viewer to view the console, but it
won't allow me to send controls.

The question is, Can I replicate the same VNC consoles in Foreman as it
supports noVNC. I am looking for a solution when I cna consolidate all the
iDrac consoles in a single place rather than launching each iDrac console
separately. Is this possible?

Thanks.

··· On Sunday, October 22, 2017 at 3:54:06 PM UTC-5, Neil Hanlon wrote: > > FWIW, idrac also exposes VNC > > On Fri, Oct 20, 2017 at 9:21 PM Alvin Starr > wrote: > >> I believe the original poster was interested in using the iKVM that is >> part of most BMC chipsets now days. >> >> I think that is a lot harder because the chipsets use a java based >> VNC-like protocol that is proprietary. >> >> >> On 10/20/2017 09:03 PM, treydock wrote: >> > We use conman, https://github.com/dun/conman, which is in the RHEL OS >> repos. Be great if this kind of functionality existed in Foreman. >> > >> >> -- >> Alvin Starr || land: (905)513-7688 >> Netvel Inc. || Cell: (416)806-0133 >> al...@netvel.net || >> >> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> >
6

Hi No1!

> Hi Neil,
>
> I know I can use any standalone VNC viewer to view the console, but it
> won't allow me to send controls.
>
> The question is, Can I replicate the same VNC consoles in Foreman as it
> supports noVNC. I am looking for a solution when I cna consolidate all the
> iDrac consoles in a single place rather than launching each iDrac console
> separately. Is this possible?
>
> Thanks.
You might try to use websocket-based server[1] which actually connects to VNC
in iDRAC and wire this in Foreman. I guess it's what noVNC provides by
default[2]. We used websockify together with noVNC from ikvm branch from
kelleyk[3], works very well with idrac and supermicro BMCs.

  1. https://github.com/novnc/websockify
  2. https://github.com/novnc/websockify/blob/master/README.md
  3. https://github.com/kelleyk/noVNC
··· On 10/24/2017, at 10:25:00 AM you wrote:

–
WBR et al.

7

Hi Konstantin Lepikhov,

Would you mind explaining a little more on how did you implemented noVNC
from ikvm branch from kelleyk [https://github.com/kelleyk/noVNC ]?. I am
confused on the part to wire the info into Foreman and how to I do that?

Any help is appreciated.

Thanks
No1.

··· On Wednesday, October 25, 2017 at 6:14:01 AM UTC-5, Konstantin Lepikhov wrote: > > Hi No1! > > On 10/24/2017, at 10:25:00 AM you wrote: > > > Hi Neil, > > > > I know I can use any standalone VNC viewer to view the console, but it > > won't allow me to send controls. > > > > The question is, Can I replicate the same VNC consoles in Foreman as it > > supports noVNC. I am looking for a solution when I cna consolidate all > the > > iDrac consoles in a single place rather than launching each iDrac > console > > separately. Is this possible? > > > > Thanks. > You might try to use websocket-based server[1] which actually connects to > VNC > in iDRAC and wire this in Foreman. I guess it's what noVNC provides by > default[2]. We used websockify together with noVNC from ikvm branch from > kelleyk[3], works very well with idrac and supermicro BMCs. > > 1. https://github.com/novnc/websockify > 2. https://github.com/novnc/websockify/blob/master/README.md > 3. https://github.com/kelleyk/noVNC > > -- > WBR et al. >
8

Hi No1!

··· On 10/25/2017, at 12:27:11 PM you wrote:

Hi Konstantin Lepikhov,

Would you mind explaining a little more on how did you implemented noVNC
from ikvm branch from kelleyk [https://github.com/kelleyk/noVNC ]?. I am
confused on the part to wire the info into Foreman and how to I do that?

Any help is appreciated.

Thanks
No1.

You need to replace novnc js code in foreman by js code from kelleyk
version + modify foreman host controller. Then you can connect
to servers’s bmc ikvm via foreman’s websockify.

Another thing - extend host inventory adding properties related
connection/bmc_type.

–
WBR et al.

9

I understood a little bit of what you said. I didn't quite get the point of
changing the foreman host controller. Are you saying hostcontroller.rb?

BTW, Are you available on IRC?

Thanks,
No1.

··· On Thursday, October 26, 2017 at 10:38:09 AM UTC-5, Konstantin Lepikhov wrote: > > Hi No1! > > On 10/25/2017, at 12:27:11 PM you wrote: > > > Hi Konstantin Lepikhov, > > > > Would you mind explaining a little more on how did you implemented noVNC > > from ikvm branch from kelleyk [https://github.com/kelleyk/noVNC ]?. I > am > > confused on the part to wire the info into Foreman and how to I do that? > > > > Any help is appreciated. > > > > Thanks > > No1. > > > > > You need to replace novnc js code in foreman by js code from kelleyk > version + modify foreman host controller. Then you can connect > to servers's bmc ikvm via foreman's websockify. > > Another thing - extend host inventory adding properties related > connection/bmc_type. > > -- > WBR et al. >
10

This sounds like an excellent thing to send a patch for, if you're
interested - or at least log a feature request with some tips on wiring
it up. Then it can be available for everyone :slight_smile:

Greg

··· On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote: > > You need to replace novnc js code in foreman by js code from kelleyk > version + modify foreman host controller. Then you can connect > to servers's bmc ikvm via foreman's websockify. > > Another thing - extend host inventory adding properties related > connection/bmc_type.
11

Hi Greg!

> >
> > You need to replace novnc js code in foreman by js code from kelleyk
> > version + modify foreman host controller. Then you can connect
> > to servers's bmc ikvm via foreman's websockify.
> >
> > Another thing - extend host inventory adding properties related
> > connection/bmc_type.
>
> This sounds like an excellent thing to send a patch for, if you're
> interested - or at least log a feature request with some tips on wiring
> it up. Then it can be available for everyone :slight_smile:
>
> Greg
>
I've checked the source, it doesn't looks hard to add it:

  1. we need to extend discovery to provide extra attributes for kvm
    functionality (it could be either 'idrac_vnc' DELL or 'sm_vnc' for Supermicro).

  2. add novnc ikvm js to vendor/assets/javascripts.

  3. add custom app/views/hosts/console/*.html.erb for ikvm vnc which
    includes ikvm nonvc.

  4. extend console in app/controllers/hosts_controller.rb to handle _vnc
    atrributes for physical boxes too

PROFIT.

So I just need a hardware to test and then I can make a patch :slight_smile:

··· On 10/27/2017, at 10:25:20 AM you wrote: > On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote:

–
WBR et al.

12

With the start of this discussion I started poking around at a couple of
ideas and the novnc referenced.

I have access to a number of Supermicro and HP systems and decided to
try the novnc solution.

My in house several year old Supermicro is built using a different
chipset than the one referenced in the novnc by kellyk It looks like
there is some sort of authentication incompatibility.

On the much newer Supermicro systems I have access to the VNC ports
appear to be blocked by some sort of internal firewall.

HP uses port 17990 and at first look does not appear to be VNC but it
may just be VNC with some wrapping around it.

I have no Dell equipment to test against.

Although I would love to be able to pull up a iKVM console via Foreman
my feeling is that the novnc fork needs some testing first.

··· On 10/27/2017 06:47 AM, Konstantin Lepikhov wrote: > Hi Greg! > > On 10/27/2017, at 10:25:20 AM you wrote: > >> On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote: >>> You need to replace novnc js code in foreman by js code from kelleyk >>> version + modify foreman host controller. Then you can connect >>> to servers's bmc ikvm via foreman's websockify. >>> >>> Another thing - extend host inventory adding properties related >>> connection/bmc_type. >> This sounds like an excellent thing to send a patch for, if you're >> interested - or at least log a feature request with some tips on wiring >> it up. Then it can be available for everyone :) >> >> Greg >> > I've checked the source, it doesn't looks hard to add it: > > 1) we need to extend discovery to provide extra attributes for kvm > functionality (it could be either 'idrac_vnc' DELL or 'sm_vnc' for Supermicro). > > 2) add novnc ikvm js to vendor/assets/javascripts. > > 3) add custom app/views/hosts/console/*.html.erb for ikvm vnc which > includes ikvm nonvc. > > 4) extend console in app/controllers/hosts_controller.rb to handle _vnc > atrributes for physical boxes too > > PROFIT. > > So I just need a hardware to test and then I can make a patch :) >

–
Alvin Starr || land: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
alvin@netvel.net ||

13

Hi,

I can help in testing with the Dell Servers as I have PowerEdge 620,630 and
730 in handy with me. Let me know if that helps!

··· On Friday, October 27, 2017 at 7:53:59 AM UTC-5, Alvin Starr wrote: > > With the start of this discussion I started poking around at a couple of > ideas and the novnc referenced. > > I have access to a number of Supermicro and HP systems and decided to > try the novnc solution. > > My in house several year old Supermicro is built using a different > chipset than the one referenced in the novnc by kellyk It looks like > there is some sort of authentication incompatibility. > > On the much newer Supermicro systems I have access to the VNC ports > appear to be blocked by some sort of internal firewall. > > HP uses port 17990 and at first look does not appear to be VNC but it > may just be VNC with some wrapping around it. > > I have no Dell equipment to test against. > > Although I would love to be able to pull up a iKVM console via Foreman > my feeling is that the novnc fork needs some testing first. > > > On 10/27/2017 06:47 AM, Konstantin Lepikhov wrote: > > Hi Greg! > > > > On 10/27/2017, at 10:25:20 AM you wrote: > > > >> On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote: > >>> You need to replace novnc js code in foreman by js code from kelleyk > >>> version + modify foreman host controller. Then you can connect > >>> to servers's bmc ikvm via foreman's websockify. > >>> > >>> Another thing - extend host inventory adding properties related > >>> connection/bmc_type. > >> This sounds like an excellent thing to send a patch for, if you're > >> interested - or at least log a feature request with some tips on wiring > >> it up. Then it can be available for everyone :) > >> > >> Greg > >> > > I've checked the source, it doesn't looks hard to add it: > > > > 1) we need to extend discovery to provide extra attributes for kvm > > functionality (it could be either 'idrac_vnc' DELL or 'sm_vnc' for > Supermicro). > > > > 2) add novnc ikvm js to vendor/assets/javascripts. > > > > 3) add custom app/views/hosts/console/*.html.erb for ikvm vnc which > > includes ikvm nonvc. > > > > 4) extend console in app/controllers/hosts_controller.rb to handle _vnc > > atrributes for physical boxes too > > > > PROFIT. > > > > So I just need a hardware to test and then I can make a patch :) > > > > -- > Alvin Starr || land: (905)513-7688 > Netvel Inc. || Cell: (416)806-0133 > al...@netvel.net || > >
14

I can do the discovery part, but frankly not fully understand what
exactly how do we grab the fact value. Is that some value that needs
to be fetched from iDRAC API?

LZ

··· On Fri, Oct 27, 2017 at 12:47 PM, Konstantin Lepikhov wrote: > Hi Greg! > > On 10/27/2017, at 10:25:20 AM you wrote: > >> On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote: >> > >> > You need to replace novnc js code in foreman by js code from kelleyk >> > version + modify foreman host controller. Then you can connect >> > to servers's bmc ikvm via foreman's websockify. >> > >> > Another thing - extend host inventory adding properties related >> > connection/bmc_type. >> >> This sounds like an excellent thing to send a patch for, if you're >> interested - or at least log a feature request with some tips on wiring >> it up. Then it can be available for everyone :) >> >> Greg >> > I've checked the source, it doesn't looks hard to add it: > > 1) we need to extend discovery to provide extra attributes for kvm > functionality (it could be either 'idrac_vnc' DELL or 'sm_vnc' for Supermicro). > > 2) add novnc ikvm js to vendor/assets/javascripts. > > 3) add custom app/views/hosts/console/*.html.erb for ikvm vnc which > includes ikvm nonvc. > > 4) extend console in app/controllers/hosts_controller.rb to handle _vnc > atrributes for physical boxes too > > PROFIT. > > So I just need a hardware to test and then I can make a patch :) > > -- > WBR et al. > > -- > 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.

–
Later,
Lukas @lzap Zapletal

15

I imagine the the API will require authentication. I think were need
something like

··· On Mon, 30 Oct 2017 at 13:31, Lukas Zapletal wrote:

I can do the discovery part, but frankly not fully understand what
exactly how do we grab the fact value. Is that some value that needs
to be fetched from iDRAC API?

LZ

On Fri, Oct 27, 2017 at 12:47 PM, Konstantin Lepikhov > lakostis@unsafe.ru wrote:

Hi Greg!

On 10/27/2017, at 10:25:20 AM you wrote:

On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote:

You need to replace novnc js code in foreman by js code from kelleyk
version + modify foreman host controller. Then you can connect
to servers’s bmc ikvm via foreman’s websockify.

Another thing - extend host inventory adding properties related
connection/bmc_type.

This sounds like an excellent thing to send a patch for, if you’re
interested - or at least log a feature request with some tips on wiring
it up. Then it can be available for everyone :slight_smile:

Greg

I’ve checked the source, it doesn’t looks hard to add it:

  1. we need to extend discovery to provide extra attributes for kvm
    functionality (it could be either ‘idrac_vnc’ DELL or ‘sm_vnc’ for
    Supermicro).

  2. add novnc ikvm js to vendor/assets/javascripts.

  3. add custom app/views/hosts/console/*.html.erb for ikvm vnc which
    includes ikvm nonvc.

  4. extend console in app/controllers/hosts_controller.rb to handle _vnc
    atrributes for physical boxes too

PROFIT.

So I just need a hardware to test and then I can make a patch :slight_smile:

–
WBR et al.

–
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.

–
Later,
Lukas @lzap Zapletal

–
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.

16

Hi,

I don't know if it can help for your use case, but foreman manage BMC ifaces and there is a snippet to configure it at provisioning time (https://github.com/theforeman/community-templates/blob/develop/provisioning_templates/snippet/bmc_nic_setup.erb)
We use it to configure IPMI ifaces on our Dell servers. If you configure a BMC iface in foreman, maybe you can use these infos (user/password) too establish the VNC connection.

Have a nice day.

Cheers.

··· ----- Le 30 Oct 17, à 19:16, Sean O'Keeffe a écrit :

I imagine the the API will require authentication. I think were need something
like [ https://github.com/newrelic/puppet-dell/blob/master/lib/facter/idrac.rb

https://github.com/newrelic/puppet-dell/blob/master/lib/facter/idrac.rb ]

On Mon, 30 Oct 2017 at 13:31, Lukas Zapletal < [ mailto:lzap@redhat.com | > lzap@redhat.com ] > wrote:

I can do the discovery part, but frankly not fully understand what
exactly how do we grab the fact value. Is that some value that needs
to be fetched from iDRAC API?

LZ

On Fri, Oct 27, 2017 at 12:47 PM, Konstantin Lepikhov >> < [ mailto:lakostis@unsafe.ru | lakostis@unsafe.ru ] > wrote:

Hi Greg!

On 10/27/2017, at 10:25:20 AM you wrote:

On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote:

You need to replace novnc js code in foreman by js code from kelleyk
version + modify foreman host controller. Then you can connect
to servers’s bmc ikvm via foreman’s websockify.

Another thing - extend host inventory adding properties related
connection/bmc_type.

This sounds like an excellent thing to send a patch for, if you’re
interested - or at least log a feature request with some tips on wiring
it up. Then it can be available for everyone :slight_smile:

Greg

I’ve checked the source, it doesn’t looks hard to add it:

  1. we need to extend discovery to provide extra attributes for kvm
    functionality (it could be either ‘idrac_vnc’ DELL or ‘sm_vnc’ for Supermicro).
  1. add novnc ikvm js to vendor/assets/javascripts.
  1. add custom app/views/hosts/console/*.html.erb for ikvm vnc which
    includes ikvm nonvc.
  1. extend console in app/controllers/hosts_controller.rb to handle _vnc
    atrributes for physical boxes too

PROFIT.

So I just need a hardware to test and then I can make a patch :slight_smile:

–
WBR et al.

–
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 [ mailto:foreman-users%2Bunsubscribe@googlegroups.com |
foreman-users+unsubscribe@googlegroups.com ] .
To post to this group, send email to [ mailto:foreman-users@googlegroups.com |
foreman-users@googlegroups.com ] .
Visit this group at [ https://groups.google.com/group/foreman-users |
https://groups.google.com/group/foreman-users ] .
For more options, visit [ https://groups.google.com/d/optout |
https://groups.google.com/d/optout ] .

–
Later,
Lukas @lzap Zapletal

–
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 [ mailto:foreman-users%2Bunsubscribe@googlegroups.com |
foreman-users+unsubscribe@googlegroups.com ] .
To post to this group, send email to [ mailto:foreman-users@googlegroups.com |
foreman-users@googlegroups.com ] .
Visit this group at [ https://groups.google.com/group/foreman-users |
https://groups.google.com/group/foreman-users ] .
For more options, visit [ https://groups.google.com/d/optout |
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 [ mailto:foreman-users+unsubscribe@googlegroups.com |
foreman-users+unsubscribe@googlegroups.com ] .
To post to this group, send email to [ mailto:foreman-users@googlegroups.com |
foreman-users@googlegroups.com ] .
Visit this group at [ https://groups.google.com/group/foreman-users |
https://groups.google.com/group/foreman-users ] .
For more options, visit [ https://groups.google.com/d/optout |
https://groups.google.com/d/optout ] .

–
Baptiste AGASSE
Lyra Network France, Senior GNU/Linux engineer
109 Rue de l’innovation, 31670 Labège - France
Phone: (+33)5.67.22.31.87
Fax: (+33)5.67.22.31.61
Website: http://www.lyra-network.com

17

Hi Sean!

> I imagine the the API will require authentication. I think were need
> something like
> https://github.com/newrelic/puppet-dell/blob/master/lib/facter/idrac.rb
>
Yes, you need to know is vnc is enabled and encryption activated or not.
This could easily checked by racadm:
http://www.dell.com/support/manuals/us/en/04/idrac8-with-lc-v2.05.05.05/idrac8_2.05.05.05_ug-v1/using-vnc-client-to-manage-remote-server?guid=guid-bf36a9fe-9ec5-4f2b-91cd-3a428bb8eb26&lang=en-us
http://www.dell.com/support/manuals/us/en/04/idrac8-with-lc-v2.05.05.05/racadm_idrac_pub-v1/idracvncserver?guid=guid-93ce8273-3517-4d79-a258-070f61dc0ee4&lang=en-us

$ racadm -r <ip> -u <adm user> -p <passwd> get idrac.vncserver
$ racadm … set idrac.vncserver.enable Enabled
$ racadm … set idrac.vncserver.Password <passwd>

NB: vnc on dell is available only with enterprise license, so why this
should be checked first.

··· On 10/30/2017, at 06:16:19 PM you wrote:

–
WBR et al.

18

Hi Konstantin,

Please let me know if you need help from my side in IPMI consoles testing :slight_smile:

Thanks,
No1.

··· On Tuesday, October 31, 2017 at 4:52:42 AM UTC-5, Konstantin Lepikhov wrote: > > Hi Sean! > > On 10/30/2017, at 06:16:19 PM you wrote: > > > I imagine the the API will require authentication. I think were need > > something like > > https://github.com/newrelic/puppet-dell/blob/master/lib/facter/idrac.rb > > > Yes, you need to know is vnc is enabled and encryption activated or not. > This could easily checked by racadm: > > http://www.dell.com/support/manuals/us/en/04/idrac8-with-lc-v2.05.05.05/idrac8_2.05.05.05_ug-v1/using-vnc-client-to-manage-remote-server?guid=guid-bf36a9fe-9ec5-4f2b-91cd-3a428bb8eb26&lang=en-us > > http://www.dell.com/support/manuals/us/en/04/idrac8-with-lc-v2.05.05.05/racadm_idrac_pub-v1/idracvncserver?guid=guid-93ce8273-3517-4d79-a258-070f61dc0ee4&lang=en-us > > $ racadm -r -u -p get idrac.vncserver > $ racadm ... set idrac.vncserver.enable Enabled > $ racadm ... set idrac.vncserver.Password > > NB: vnc on dell is available only with enterprise license, so why this > should be checked first. > > -- > WBR et al. >
19

Hi,

Is anyone working on this feature?
Thanks!
Ido

···

On Friday, October 20, 2017 at 11:46:44 PM UTC+3, No1 wrote:

Hi,

Is there any way to display the console of IPMI (aka iDrac in Dell or iLo
in HP) in the foreman? I believe this would a good idea to have on the
hosts section which are deployed as a metal metal servers.

If it's not possible then is there any other alternative for this?

Please let me know.

Thanks,
No1.

20

Hi,

Is there any way to display the console of IPMI (aka iDrac in Dell or iLo
in HP) in the foreman? I believe this would a good idea to have on the
hosts section which are deployed as a metal metal servers.

If it's not possible then is there any other alternative for this?

Please let me know.

Hi,

Is there any update?
Thanks!
Ido

···

On Friday, October 20, 2017 at 11:46:44 PM UTC+3, No1 wrote:

Thanks,
No1.