We use Conserver to provide an abstract interactive serial console to our heterogeneous environment.
I think having RedHat provide a version of Conserver is a good idea. For our deployment, we've only done on compile-time change; increasing the number of connections each conserver process handles. The default is 16. We've bumped it to 32 to reduce the number of conserver processes we have on a single server. Having that be something like that in the config file would be very nice.
If you do go that route of supporting it, be aware that we've seen after a number of months of uptime on the conserver process that will get a SEGV and basically become unusable at which time we have to bounce all the conserver processes. We have at our ADC facility, one conserver server with 575 conserver processes running (all from one parent conserver process) managing ~3700 servers. We'd probably open a ticket on this behavior once you support conserver.
Customer's Use Case.
- Provides a hardware abstract interactive serial interface to physical (dell, hp, ibm)/virtual heterogeneous hardware
- can rescue system when networking not working
- can rescue system when disk repair is required
- removes dependency on hardware specific remote mgmt tools (ilo,drac,imm, etc.)
- Provides a centralized audit access trail
- only one way in and it's logged
- Provides persistent logging of serial console for all hosts
- after the fact rca
Red Hat Enterprise Linux
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.