GUI : FRUs Concurrently Maintainable

derick-montague commented 4 years ago

SMEs

BMC: @santoshpuranik

Tasks

[ ] Set up time in Design exchange meeting
- [ ] Determine if presence of FRU can be detected
- [ ] Validate UI workflow
- [ ] Why is state (enabled, absent) hard coded and will that change

Summary

Shows the user that these HW inventory items can be concurrently maintained. There are two devices only related to this story, which are associated with #2012. Currently, we have not designed a way to show this in the HW inventory.

Background

Hardware components which are concurrently maintanble can be replaced without rebooting the system.
Remove/install: Most components need to be "removed" from the GUI before removing them in the field, and then subsequently "installed" from the GUI after physically instaling a new replacement.
Remove means that the firmware will not read any data/monitor from the device anymore. Install means that the firmware will start monitoring the device again.
State: Enabled/Absent - Some devices can show this if there is a hardware capability to detect physical presence. Otherwise it is hardcoded. It is unknown if this will be supported for TOD battery. Need to discuss with backend on which statuses are possible to show.

ASMI Screen Captures

Control / OP Panel

TOD Battery

User Story

As an admin or SSR, I need to remove and install a component from the GUI before and after replacing it in the system, so that there are no errors and the new hardware performs as expected.

References

eBMC Feature Item: 2.2.5
Link to Discovery doc: https://ibm.ent.box.com/notes/656691140903 (same as https://github.com/ibm-openbmc/dev/issues/2210)

Invision links

Removing a FRU Installing a FRU

Interaction requirements

Show Remove button for supported device. (Not sure if it is supported for Battery)
Click Remove and wait for status to update.
SSR replaces the component physically
Click Install and wait for status to update.

nicoleconser commented 4 years ago

TOD Battery = RTC Batter (time of day / real time clock)

mzipse commented 4 years ago

@derick-montague , just fyi. I'm working to get some clarification on the concurrently maintainable device vs the hot pluggable devices. We're also checking on differences between our platforms. I'll keep you posted.

derick-montague commented 4 years ago

Concurrent Maintenance and what is Concurrent Maintainable for R / E.

https://ibm-systems-power.slack.com/archives/GBVDZRCQK/p1595254273246600

nicoleconser commented 4 years ago

From Gunnar: This IBM wiki has some gold on Concurrent Maintenance and what is Concurrently Maintainable

nicoleconser commented 4 years ago

Note that this includes the closed story #2237.

derick-montague commented 4 years ago

Mini-workshops happening on 8/4/20 and 8/5/20, technical discussion let by Santosh.

The intent is to hold two workshops related to HW Concurrent Maintenance:

Part 1 (8/4/20 9am CST) - Address eBMC external interfaces to support Redfish, HMC and eBMC GUI
Part 2 (8/5/20 9am CST) - Address Host interfaces to eBMC

I will be attending these workshops and will create and add information to a discovery document. Documentation will be captured in box: https://ibm.ent.box.com/notes/699945208563

nicoleconser commented 4 years ago

8/7 sync-up notes:

Need to find out what this page looks like in ASMI (Russ says this is on P8s only)
Unclear that this belongs on the Hardware Inventory / VPD page (Justin says yes, Russ says totally unrelated)

priyanka-pillai97 commented 3 years ago

Concurrently Maintainable FRUs -

On Rainier, the following will be concurrently maintainable: PCIe Adapters, NVMe Drives (this is driven by the host, not BMC GUI).
On Everest, in addition to those two, the TOD Battery, Base Op Panel, and LCD Op panel are concurrently maintainable.

Slack conversation - https://ibm-systems-power.slack.com/archives/C0Q6TQP5Z/p1610963741022400

derick-montague commented 3 years ago

The current state of the backend requires that we schedule time in @bradbishop design exchange meeting. @derick-montague will we responsible for setting up time in the meeting.

derick-montague commented 3 years ago

Possibly moving out of GA1. Will know soon. As a side note, Rainier and Everest are different and TOD is not concurrently maintainable on Rainier systems, so the availability of this in the GUI will need to be based on Redfish indicating if the FRU supports CM for a specific FRU.

derick-montague commented 3 years ago

Slack conversation for TOD Battery

what's the best way for me to get up to speed on the requirements around RTC battery concurrent maint?

Slack Conversation about Op Panel Vishwa gave a brief sequencing list for the battery - could you take a crack at a similar one for the panel? Or is it too complex

Slack conversation regarding Ops Panel and TOD Redfish

Santosh and vishwa for panel/battery CM it sounds like we need a Redfish resource to call a method on to start the operation?

So we need the "ReadyForRemove" on assembly ?

do you know where op panel and battery CM redfish endpoints would fall priority-wise relative to the items listed by above?

mzipse commented 2 years ago

Work is complete. Closing.

ibm-openbmc / dev