From: James Feist <james.feist@linux.intel.com>
To: Matt Spinler <mspinler@linux.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Message registries continuation
Date: Tue, 16 Jun 2020 13:39:18 -0700 [thread overview]
Message-ID: <85015a54-0de6-42e2-bd56-732c7f0a420d@linux.intel.com> (raw)
In-Reply-To: <74794819-3b3c-0c39-30e0-b2ca6c46d9fb@linux.ibm.com>
On 6/16/2020 12:47 PM, Matt Spinler wrote:
> Hi James,
>
> Picking up the discussion again from
> https://lists.ozlabs.org/pipermail/openbmc/2020-February/020620.html
> about reading in message registries...
>
> When this was left off, I believe we were leaning toward being able to
> copy message registry JSON files
> into some target directory on the BMC during the build where bmcweb
> would load them on startup
> and leave them in their JSON objects, and they would be pulled from
> there when LogService requests
> were made.
>
> This was to be able to support multiple languages, and in general just
> to support other registries besides
> the existing OpenBMC one that is hardcoded in a header file. (We're
> going to have an IBM registry we
> use together with our D-Bus logs based LogService.)
There's 3 registries, fwiw:
https://github.com/openbmc/bmcweb/tree/master/redfish-core/include/registries
>
> An open issue we still had was if these registries had to be validated,
> or if that was left to whoever
> made them. A stake in the ground could be that we leave the OpenBMC
> registry as it is in a header
> file, which negates validation, or put it in JSON too and validate just
> that one during the build.
> Or if there are any other ideas here...
Entity-manager uses valijson, in that way you could validate them
against a schema: https://github.com/tristanpenman/valijson. It plays
nicely with nlohmann-json. Although if these are compiled in json files,
I'm not sure it's a large issue. We could just create a compile-time
script to validate.
>
> As far as the directory used, I think that /usr/share/bmcweb/ would be
> appropriate, or maybe
> /usr/share/bmcweb/registries/ if either of those are OK with you.
I think the directory is a good idea so it can load any json file from
that directory. Maybe /usr/share/bmcweb/registries/<language> even to
make it easier to switch between languages?
>
> Also, it may be overkill to need to read in the same registry for every
> language, as there could
> be dozens and realistically they will never all be used on a single
> system, but if the desire is only
> to load them at startup before the current language is known I don't
> really see a way around it.
I think this would require a default language and a bmcweb reload if the
language changed? Its probably ok to change languages after startup, as
long as the default language is loaded immediately to lower the chances
of run-time issues. As changing languages is probably a very infrequent
operation.
>
> Thanks!
> Matt
next prev parent reply other threads:[~2020-06-16 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 19:47 Message registries continuation Matt Spinler
2020-06-16 20:39 ` James Feist [this message]
2020-06-16 20:50 ` Patrick Williams
2020-06-16 20:58 ` James Feist
2020-06-16 21:30 ` Matt Spinler
2020-06-16 21:57 ` James Feist
2020-06-18 15:23 ` Brad Bishop
2020-06-22 20:46 ` Matt Spinler
2020-06-22 21:16 ` James Feist
2020-06-23 18:02 ` Matt Spinler
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=85015a54-0de6-42e2-bd56-732c7f0a420d@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=mspinler@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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.