<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div class="ApplePlainTextBody">Hello,<br><br>Wonder if the community has any thoughts ?<br><br>Thanks,<br>!! Vishwa !!<br><br><blockquote type="cite">On 14-Feb-2020, at 4:51 PM, Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com> wrote:<br><br>Hello,<br><br>Writing this to get your thoughts on representing LED logical groups in Redfish.<br><br>OpenBmc LED subsystem has 2 layers<br><br>1/. Logical LED group manager<br>2/. Physical LED controller that sets ONE particular LED to On/Off/Blink<br><br>Logical LED group manager:<br><br>This is where we define a group with set of physical LEDs and their respective actions for one use case.<br><br>For example: https://github.com/openbmc/phosphor-led-manager/blob/master/led.yaml<br><br>When the user wants to turn on the Identify indicators, they don’t target the physical LEDs individually. Instead, they just set the “Asserted” property : “xyz/openbmc_project/led/groups/enclosure_identify/attr/Asserted"<br><br>LED manager will then request physical led controllers of those LEDs to take the right action<br><br>Current bmcweb actually uses the groups than targeting the physical LEDs. So it’s good. https://github.com/openbmc/bmcweb/blob/1c8fba97b1feb4164e9b54cd66aad530bbfc1826/redfish-core/lib/led.hpp#L33<br><br>However, I am not sure if there are ways to express the LED logical groups in the redfish schema.<br><br>Any ideas ?<br><br>Thank you,<br>!! Vishwa !!<br></blockquote><br></div></body></html>