All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.ibm.com>
To: Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>,
	tomjose@linux.vnet.ibm.com
Cc: openbmc@lists.ozlabs.org
Subject: Re: Attention users of network IPMI
Date: Tue, 10 Apr 2018 12:57:33 +1000	[thread overview]
Message-ID: <87in8zn4yq.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <4333c25f-d5bb-e4b8-f6c4-62deb53362a1@linux.vnet.ibm.com>

Deepak Kodihalli <dkodihal@linux.vnet.ibm.com> writes:
> On 29/03/18 2:53 pm, Tom Joseph wrote:
>> Hello,
>> 
>> Based on  feedback from the team writing management scripts for OpenBMC. 
>> There is a suggestion to
>> support the "-U" parameter when running the IPMI over network, to keep 
>> the script consistent across
>> multiple BMC implementations.
>> 
>> The support currently in  OpenBMC for the IPMI user accounts is the 
>> nameless account and the -U option
>> is not needed and only the -P option is needed. With the proposed 
>> change, "-U admin" is needed, for the
>
> This would break current users based on a nameless account. So I suppose 
> that you'd have to still support a nameless account.

For current OpenPOWER systems, it's only IBM FSP machines and OpenBMC
that have a nameless account. Both SuperMicro and AMI BMCs require
usernames, so any scripts targetting OpenPOWER systems need to deal with
both situations.

But maintaining backwards compatibility with existing openbmc ipmi
implementations is also a good thing.

-- 
Stewart Smith
OPAL Architect, IBM.

      parent reply	other threads:[~2018-04-10  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  9:23 Attention users of network IPMI Tom Joseph
2018-03-29 13:26 ` Deepak Kodihalli
2018-03-29 16:18   ` Alexander Amelkin
2018-03-29 16:37     ` Emily Shaffer
2018-03-29 17:27       ` Brad Bishop
2018-04-10  2:57   ` Stewart Smith [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87in8zn4yq.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.ibm.com \
    --cc=dkodihal@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tomjose@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.