Skip to content

Conversation

@lollipopman
Copy link
Contributor

The library libipmiconsole allows you to set defaults via the config
file libipmiconsole.conf. However, these defaults are not used unless
the engine_config flags are initialized with all bits toggled to 1.

This functionality is useful for setting flags such as:

libipmiconsole-context-engine-flags serialkeepalive

Which was necessary for Dell's ipmi SOL implementation, which upon
connection establishment does not send any output from the server until
an input character is sent on stdin. This renders conman's console
logging useless you manually connect to each console. However, using the
serialkeepalive setting, the '\0' char triggers the connection to start
sending output.

lollipopman and others added 2 commits December 8, 2017 13:03
The library libipmiconsole allows you to set defaults via the config
file libipmiconsole.conf. However, these defaults are not used unless
the engine_config flags are initialized with all bits toggled to 1.

This functionality is useful for setting flags such as:

  libipmiconsole-context-engine-flags serialkeepalive

Which was necessary for Dell's ipmi SOL implementation, which upon
connection establishment does not send any output from the server until
an input character is sent on stdin. This renders conman's console
logging useless you manually connect to each console. However, using the
serialkeepalive setting, the '\0' char triggers the connection to start
sending output.
The config file libipmiconsole.conf can also specify workaround-flags.
But conmand initializes the IPMI workaround-flags to 0 which indicates
no workarounds (thereby overriding the standard libipmiconsole default
or one configured via libipmiconsole.conf).

This commit fixes that behavior.  IPMI workaround-flags are initialized
to the standard libipmiconsole default which can be overridden in either
libipmiconsole.conf (via libipmiconsole-context-workaround-flags)
or conman.conf (via ipmiopts).

Signed-off-by: Chris Dunlap <cdunlap@llnl.gov>
@dun
Copy link
Owner

dun commented Dec 12, 2017

Looks good, but don't the workaround-flags have the same problem? I've pushed a commit that (hopefully) addresses that. Can you give it a test in your setup?

@lollipopman
Copy link
Contributor Author

thanks @dun I have confirmed in my environment that your additional patch allows you to set default workaround flags in libipmiconsole.conf, that are then picked up by conman.

dun pushed a commit that referenced this pull request Dec 12, 2017
The library libipmiconsole allows you to set defaults via the config
file libipmiconsole.conf. However, these defaults are not used unless
the engine_config flags are initialized with all bits toggled to 1.

This functionality is useful for setting flags such as:

  libipmiconsole-context-engine-flags serialkeepalive

Which was necessary for Dell's ipmi SOL implementation, which upon
connection establishment does not send any output from the server until
an input character is sent on stdin. This renders conman's console
logging useless you manually connect to each console. However, using the
serialkeepalive setting, the '\0' char triggers the connection to start
sending output.

Signed-off-by: lollipopman <jesse@mbuki-mvuki.org>
Signed-off-by: Chris Dunlap <cdunlap@llnl.gov>
PR #27
dun added a commit that referenced this pull request Dec 12, 2017
The config file libipmiconsole.conf can also specify workaround-flags.
But conmand initializes the IPMI workaround-flags to 0 which indicates
no workarounds (thereby overriding the standard libipmiconsole default
or one configured via libipmiconsole.conf).

This commit fixes that behavior.  IPMI workaround-flags are initialized
to the standard libipmiconsole default which can be overridden in either
libipmiconsole.conf (via libipmiconsole-context-workaround-flags)
or conman.conf (via ipmiopts).

Signed-off-by: Chris Dunlap <cdunlap@llnl.gov>
Signed-off-by: lollipopman <jesse@mbuki-mvuki.org>
PR #27
@dun dun closed this in 060adda Dec 12, 2017
@dun dun added this to the 0.2.9 milestone Dec 12, 2017
@dun
Copy link
Owner

dun commented Dec 12, 2017

I'll try to get 0.2.9 out this week. Thanks for the PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants