SimpleStorage proposals

[Jun-Lin Chen (陳俊霖)]

-----Original Message-----
From: Ed Tanous <edtanous at google.com> 
Sent: Thursday, May 20, 2021 5:41 AM
To: Nan Zhou <nanzhou at google.com>
Cc: openbmc at lists.ozlabs.org; Jun-Lin Chen (陳俊霖) <Jun-Lin.Chen at quantatw.com>; bradleyb at fuzziesquirrel.com
Subject: Re: SimpleStorage proposals

On Wed, May 19, 2021 at 2:27 PM Nan Zhou <nanzhou at google.com> wrote:
>
> Thanks for your reply, Ed!
>
>>
>> You've also omitted what properties you're trying to target.  Could 
>> you walk through a little bit about what you're trying to accomplish 
>> with this?  (beyond just "implement the redfish schemas).  Are you 
>> trying to get smart data?  just inventory information?  Do you plan 
>> to represent connections?
>
>
> 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.

I'm assuming these will be the dbus properties names, as redfish doesn't really have a presence property or a powerstatus property.
With that said, that seems reasonable to me to want to do, but we need to make sure we're clear on how this differs from the existing Drive interfaces.

After question in redfish forum, https://redfishforum.com/thread/483/different-storage-simplestorage
We got SimpleStorage was the early model in Redfish for showing storage devices, and "Devices" in this resource do equate to drives.
We would use xyz.openbmc_project.Inventory.Drive instead xyz.openbmc_project.Inventory.SimpleStorage to represent our storage device.

>
> On Wed, May 19, 2021 at 1:43 PM Ed Tanous <ed at tanous.net> wrote:
>>
>> On Wed, May 19, 2021 at 12:57 AM Jun-Lin Chen (陳俊霖)
>> <Jun-Lin.Chen at quantatw.com> wrote:
>> >
>> > Hi all,
>> >
>> >
>> >
>> > In order to implement the feature to view simple storage device status, such SATA HDD presence status.
>> >
>> > We propose to implement it on the Redfish SimpleStorage URI.
>> >
>> >
>> >
>> > As our proposal for Redfish SimpleStorage, 
>> > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
>> > errit.openbmc-project.xyz%2Fc%2Fopenbmc%2Fdocs%2F%2B%2F43352&da
>> > ta=04%7C01%7CJun-Lin.Chen%40quantatw.com%7Cd419ece6a8d344d93bbb08d9
>> > 1b0ec5c4%7C179b032707fc4973ac738de7313561b2%7C1%7C0%7C6375705731225
>> > 16364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
>> > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=BvHa13JAozhhau6qxQqs
>> > 8XMe1BX1jMi057h%2BFZ67lJk%3D&reserved=0
>> >
>> > And an new daemon, 
>> > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
>> > errit.openbmc-project.xyz%2Fc%2Fopenbmc%2Fdocs%2F%2B%2F43351&da
>> > ta=04%7C01%7CJun-Lin.Chen%40quantatw.com%7Cd419ece6a8d344d93bbb08d9
>> > 1b0ec5c4%7C179b032707fc4973ac738de7313561b2%7C1%7C0%7C6375705731225
>> > 26352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
>> > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=c7TSGNJC5BlMxWwmFBQH
>> > X3gHH8xbPEu53hsNHun04Jo%3D&reserved=0
>> >
>> >
>> >
>> > There are two new dbus-interfaces to be proposed,
>> >
>> > xyz.openbmc_project.Inventory.Item.StorageDevice: here is an empty interface just mark the dbus path that SimpleStorage Manager should collect.
>> >
>> > xyz.openbmc_project.Inventory.Item.SimpleStorage: it should have the properties redfish needs, and can be parser by bmcweb.
>>
>>
>> How does this differ from xyz.openbmc_project.Inventory.Item.Drive?
>> They look fairly similar;  We generally don't name dbus interfaces 
>> after Redfish directly.  We should reuse what already exists where 
>> possible, and only invent new things where needed.
>>
>> You've also omitted what properties you're trying to target.  Could 
>> you walk through a little bit about what you're trying to accomplish 
>> with this?  (beyond just "implement the redfish schemas).  Are you 
>> trying to get smart data?  just inventory information?  Do you plan 
>> to represent connections?
>>
>> >
>> >
>> >
>> > The details are in the proposal.
>> >
>> >
>> >
>> > Welcome and thank you for comments and suggestions
>> >
>> >
>> >
>> > Best regards,
>> >
>> > Jun-Lin Chen
>> >
>> >