openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Entity Manager ReScan Functionality
@ 2020-10-28  2:30 Rahul Kapoor
  2020-10-28 16:03 ` Ed Tanous
  0 siblings, 1 reply; 2+ messages in thread
From: Rahul Kapoor @ 2020-10-28  2:30 UTC (permalink / raw)
  To: openbmc

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

Hi,

I have noticed that in its current state the entity manager ReScan function does not detect changes in the exposed configuration data unless the configuration name property in the JSON is changed. Is my understanding correct?
I am currently working around this by updating the Name property along with each object within the exposed data since Redfish bmcweb interface only reports objects associated with latest configuration. But I am sure there is a better way

-Rahul

[-- Attachment #2: Type: text/html, Size: 6079 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Entity Manager ReScan Functionality
  2020-10-28  2:30 Entity Manager ReScan Functionality Rahul Kapoor
@ 2020-10-28 16:03 ` Ed Tanous
  0 siblings, 0 replies; 2+ messages in thread
From: Ed Tanous @ 2020-10-28 16:03 UTC (permalink / raw)
  To: Rahul Kapoor; +Cc: openbmc

On Tue, Oct 27, 2020 at 7:31 PM Rahul Kapoor <rahulkapoor@microsoft.com> wrote:
>
> Hi,
>
>
>
> I have noticed that in its current state the entity manager ReScan function does not detect changes in the exposed configuration data unless the configuration name property in the JSON is changed. Is my understanding correct?
>
> I am currently working around this by updating the Name property along with each object within the exposed data since Redfish bmcweb interface only reports objects associated with latest configuration. But I am sure there is a better way

I've read the above a couple of times, and I'm still trying to make
sure I understand;  You're modifying the config files on disk, then
calling rescan and expecting them to be re-read?  If I have that
right, that's not how that works, and would be undefined behavior even
if it did work.  Entity-manager is expecting that the config files are
fixed for the lifetime of a service.  If you're doing this for testing
purposes, a simple systemctl restart entitymanager.service would
reload the files from disk and reinit all configurations, but as a
matter of practice, a system should not be modifying the config files
at runtime.  If you need that behavior, use the dbus interfaces to
modify parameters on dbus, and entity-manager will persist them for
you.

>
>
>
> -Rahul

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-10-28 16:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-28  2:30 Entity Manager ReScan Functionality Rahul Kapoor
2020-10-28 16:03 ` Ed Tanous

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).