<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-im" style="color:rgb(80,0,80)">><br></span><span class="gmail-im" style="color:rgb(80,0,80)">> Thanks for your reply, Ed!<br></span><span class="gmail-im" style="color:rgb(80,0,80)">><br></span><span class="gmail-im" style="color:rgb(80,0,80)">>><br></span><span class="gmail-im" style="color:rgb(80,0,80)">>> You've also omitted what properties you're trying to target. Could<br></span><span class="gmail-im" style="color:rgb(80,0,80)">>> you walk through a little bit about what you're trying to accomplish<br></span><span class="gmail-im" style="color:rgb(80,0,80)">>> with this? (beyond just "implement the redfish schemas). Are you<br></span><span class="gmail-im" style="color:rgb(80,0,80)">>> trying to get smart data? just inventory information? Do you plan to<br></span><span class="gmail-im" style="color:rgb(80,0,80)">>> represent connections?<br></span><span class="gmail-im" style="color:rgb(80,0,80)">><br></span><span class="gmail-im" style="color:rgb(80,0,80)">><br></span><span class="gmail-im" style="color:rgb(80,0,80)">> As a first step, we are only going to implement three properties, Name, Presence, and PowerStatus. We don't plan to represent connections at the moment.</span><span class="gmail-im" style="color:rgb(80,0,80)"><br></span>I'm assuming these will be the dbus properties names, as redfish<br>doesn't really have a presence property or a powerstatus property.<br>With that said, that seems reasonable to me to want to do, but we need<br>to make sure we're clear on how this differs from the existing Drive<br>interfaces.</blockquote><div>Hi Ed, the presence I am talking about is kind of a logical concept. You can find the dbus and redfish properties in the proposal. I believe we plan to use the following mappings,</div><div><br></div><div>dbus redifish logical </div><div>State(enabled) Device#Status#State If state is "enabled", the device is considered present.<br></div><div>Health(OK) Device#Status#Heatlth(OK) If health is "OK", the device is considered present and its current status is OK (its power should be OK at least).</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 19, 2021 at 2:40 PM Ed Tanous <<a href="mailto:edtanous@google.com">edtanous@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, May 19, 2021 at 2:27 PM Nan Zhou <<a href="mailto:nanzhou@google.com" target="_blank">nanzhou@google.com</a>> wrote:<br>
><br>
> Thanks for your reply, Ed!<br>
><br>
>><br>
>> You've also omitted what properties you're trying to target. Could<br>
>> you walk through a little bit about what you're trying to accomplish<br>
>> with this? (beyond just "implement the redfish schemas). Are you<br>
>> trying to get smart data? just inventory information? Do you plan to<br>
>> represent connections?<br>
><br>
><br>
> As a first step, we are only going to implement three properties, Name, Presence, and PowerStatus. We don't plan to represent connections at the moment.<br>
<br>
I'm assuming these will be the dbus properties names, as redfish<br>
doesn't really have a presence property or a powerstatus property.<br>
With that said, that seems reasonable to me to want to do, but we need<br>
to make sure we're clear on how this differs from the existing Drive<br>
interfaces.<br>
<br>
><br>
> On Wed, May 19, 2021 at 1:43 PM Ed Tanous <<a href="mailto:ed@tanous.net" target="_blank">ed@tanous.net</a>> wrote:<br>
>><br>
>> On Wed, May 19, 2021 at 12:57 AM Jun-Lin Chen (陳俊霖)<br>
>> <<a href="mailto:Jun-Lin.Chen@quantatw.com" target="_blank">Jun-Lin.Chen@quantatw.com</a>> wrote:<br>
>> ><br>
>> > Hi all,<br>
>> ><br>
>> ><br>
>> ><br>
>> > In order to implement the feature to view simple storage device status, such SATA HDD presence status.<br>
>> ><br>
>> > We propose to implement it on the Redfish SimpleStorage URI.<br>
>> ><br>
>> ><br>
>> ><br>
>> > As our proposal for Redfish SimpleStorage, <a href="https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/43352" rel="noreferrer" target="_blank">https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/43352</a><br>
>> ><br>
>> > And an new daemon, <a href="https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/43351" rel="noreferrer" target="_blank">https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/43351</a><br>
>> ><br>
>> ><br>
>> ><br>
>> > There are two new dbus-interfaces to be proposed,<br>
>> ><br>
>> > xyz.openbmc_project.Inventory.Item.StorageDevice: here is an empty interface just mark the dbus path that SimpleStorage Manager should collect.<br>
>> ><br>
>> > xyz.openbmc_project.Inventory.Item.SimpleStorage: it should have the properties redfish needs, and can be parser by bmcweb.<br>
>><br>
>><br>
>> How does this differ from xyz.openbmc_project.Inventory.Item.Drive?<br>
>> They look fairly similar; We generally don't name dbus interfaces<br>
>> after Redfish directly. We should reuse what already exists where<br>
>> possible, and only invent new things where needed.<br>
>><br>
>> You've also omitted what properties you're trying to target. Could<br>
>> you walk through a little bit about what you're trying to accomplish<br>
>> with this? (beyond just "implement the redfish schemas). Are you<br>
>> trying to get smart data? just inventory information? Do you plan to<br>
>> represent connections?<br>
>><br>
>> ><br>
>> ><br>
>> ><br>
>> > The details are in the proposal.<br>
>> ><br>
>> ><br>
>> ><br>
>> > Welcome and thank you for comments and suggestions<br>
>> ><br>
>> ><br>
>> ><br>
>> > Best regards,<br>
>> ><br>
>> > Jun-Lin Chen<br>
>> ><br>
>> ><br>
</blockquote></div>