Proposal for the connected redfish client info

Ivan Mikhaylov i.mikhaylov at yadro.com
Wed Mar 18 04:58:44 AEDT 2020


On Tue, 2020-03-17 at 18:31 +0530, Ratan Gupta wrote:
> Hi Team,
> 
> Looking for your inputs 
> 
> James, How about option1 for the below use case
> 
> Ratan
> 
> On 3/11/20 3:48 PM, Ratan Gupta wrote:
> > Hi Team,
> > 
> > In IBM we have a following requirement
> > 
> > Show the connected redfish client info.
> >   ClientIP
> >   Client Unique Identifier(unique serial number of the client etc)
> > 
> > Presently there is no way through which we can get this info.
> > 
> > I have following two proposal for the above requirement.
> > 
> > 1/ (Extend the session schema)
> > 
> > Add the IPaddress and the client Identifier as a OEM in the session schema,
> > Clinet IP would be read only and will be updated once the redfish client
> > creates the session.

We've already some sort of it in our local env for old builds. I don't mind
about client ip read only property inside session/connection inside bmcweb. 

> > ClientIdentifier(Management console unique serial number etc) will be
> > writable property and can be set by the redfish client 
> > during creation of the session or after creating the session.

What is 'ClientIdentifier' and why it should be there?



More information about the openbmc mailing list