PSU Sensors - Associations

[Patrick Venture]

On Thu, Oct 24, 2019 at 6:07 AM Matt Spinler <mspinler at linux.ibm.com> wrote:
>
>
>
> On 10/23/2019 9:03 PM, Lei YU wrote:
> > On Thu, Oct 24, 2019 at 1:39 AM Patrick Venture <venture at google.com> wrote:
> >> So, I flipped the association interface addition and the property
> >> initialization to match other sensors, and then it started working.  I
> >> was curious if you had any suggestions on how to find the matching
> >> sensor given the paths, for instance:
> >>
> >> busctl get-property xyz.openbmc_project.PSUSensor
> >> /xyz/openbmc_project/sensors/temperature/alt2_Temperature
> >> xyz.openbmc_project.Association.Definitions Associations
> >> a(sss) 1 "chassis" "all_sensors"
> >> "/xyz/openbmc_project/inventory/system/board/Altie"
> >>
> >> busctl tree --no-pager xyz.openbmc_project.EntityManager|grep Altie
> >>            |-/xyz/openbmc_project/inventory/system/board/Altie
> >>            | |-/xyz/openbmc_project/inventory/system/board/Altie/al_temp_0
> >>            | |-/xyz/openbmc_project/inventory/system/board/Altie/al_temp_1
> >>            | |-/xyz/openbmc_project/inventory/system/board/Altie/al_temp_2
> >>            | `-/xyz/openbmc_project/inventory/system/board/Altie/alt1
> >>
> >> No alt2 -- so how do I know this?  I can walk every subordinate object
> >> to find the name match, but I was curious if you had a faster idea?
> > It looks like buggy, I think mapper shall make sure the association
> > object is created only when the associated object exists.
> > @Matt Spinler could you confirm that?
>
> I'm not entirely following  what the problem is here, but I will still
> take a moment
> to plug my association (and other mapper functionality) documentation at:
> https://github.com/openbmc/docs/blob/master/architecture/object-mapper.md#associations

Thanks, so given the documentation, we can create additional endpoints
because there is more than one relationship with the object.

>