System and method for dynamically configuring storage mapping

1. A method comprising:

receiving, by an embedded controller, a first event notification of an insertion of a first compute sled in a first slot in a chassis, wherein the first event notification of the insertion includes a power on request from the first compute sled;

in response to determining that the first compute sled is a replacement to a prior compute sled that was removed from the first slot in the chassis, and wherein there is a potential data loss if the first compute sled is powered on:

determining a first pending storage mapping associated with the prior compute sled that was removed from the first slot, wherein the first pending storage mapping is the first pending storage mapping of one or more pending storage mappings;

generating a graphical user interface to configure the one or more pending storage mappings, wherein the graphical user interface of includes the first pending storage mapping associated with the prior compute sled that was removed from the first slot;

determining whether to reinstate the first pending storage mapping to the first compute sled; and

in response to determining to reinstate the first pending storage mapping, reinstating the first pending storage mapping to the first compute sled in the first slot; and

in response to determining that there is none of the one or more pending storage mappings remaining to be resolved for the first compute sled, powering-on the first compute sled based on the power on request.

2. The method of claim 1 , further comprising displaying the graphical user interface indicating an option whether to apply the first pending storage mapping or not.

3. The method of claim 1 , further comprising displaying the graphical user interface indicating an option whether to clear the first pending storage mapping or not.

4. The method of claim 1 , wherein the potential data loss is based on whether the first compute sled in the chassis has a first service tag that is different than a second service tag of the prior compute sled.

5. The method of claim 1 , wherein the graphical user interface is displayed at a display panel in the chassis.

6. The method of claim 1 , wherein the graphical user interface includes information associated with the first compute sled or the first slot.

7. The method of claim 1 , wherein the first pending storage mapping is a slot assigned storage mapping.

8. The method of claim 1 , further comprising receiving a second event notification of another insertion of a second compute sled in a second slot in the chassis.

9. The method of claim 8 , further comprising adding a second pending storage mapping associated with the second event notification to a queue of the one or more pending storage mappings associated with the chassis.

10. The method of claim 9 , further comprising in response to a user action, removing the first pending storage mapping from the queue of pending storage mappings associated with the chassis.

11. A system, comprising:

a first embedded controller configured to the system via a management interface displayed at a mobile device;

a second embedded controller configured to manage a display panel at the system, wherein the second embedded controller is distinct from the first embedded controller;

receiving, by the first embedded controller, a first event notification of an insertion of a compute sled in the system, wherein the first event notification of the insertion includes a power on request from the compute sled;

in response to the receiving of the first event notification, determining a pending storage mapping associated with a prior compute sled in the system and determining whether to power on the compute sled based on the power on request;

in response to determining that the compute sled is a replacement to the prior compute sled that was removed from the system, and wherein there is potential data loss if the compute sled is powered on:

displaying, by the first embedded controller at the management interface at the mobile device, information associated with the pending storage mapping associated with the prior compute sled, wherein the pending storage mapping is one of one or more pending storage mappings;

generating, by the second embedded controller, a graphical user interface to configure the one or more pending storage mappings, wherein the graphical user interface includes the information associated with the pending storage mapping associated with the prior compute sled, wherein the graphical user interface is displayed at the display panel;

receiving a user input associated with the pending storage mapping at the management interface;

in response to determining that the user input is to apply the pending storage mapping of the prior compute sled to the compute sled inserted in the system; and

updating the graphical user interface in response to the user input; and

in response to determining that there is no pending storage mapping to be resolved for the compute sled, powering on the compute sled based on the power on request.

12. The system of claim 11 , further comprising in response to receiving the user input associated with the pending storage mapping, disallowing the compute sled to boot.

13. The system of claim 11 , further comprising in response to receiving the user input associated with the pending storage mapping, sending a second event notification to the second embedded controller.

14. The system of claim 11 , further comprising synchronizing the information associated with the pending storage mapping between the first embedded controller and the second embedded controller.

15. A memory device storing instructions that when executed cause a hardware processor to perform operations, the operations comprising:

receiving an event notification of an insertion of a compute sled in a slot of a chassis, wherein the event notification of the insertion includes a power on request from the compute sled;

in response to determining that the compute sled is a replacement to a prior compute sled that was removed from the slot in the chassis and that there is potential data loss when the compute sled is powered on:

determining that a pending storage mapping associated with the prior compute sled on the slot is not compatible with the compute sled currently inserted in the slot of the chassis, wherein the pending storage mapping is one of one or more pending storage mappings;

generating a graphical user interface for configuring the one or more pending storage mappings, wherein the graphical user interface includes information associated with the pending storage mapping;

displaying the graphical user interface at a display panel, the graphical user interface providing a first option to clear the pending storage mapping; and

clearing the pending storage mapping in response to a user action to clear the pending storage mapping; and

in response to determining that there is no pending storage mapping in the one or more pending storage mappings for resolution, powering on the compute sled based on the power on request.

16. The memory device of claim 15 , wherein the operations further include displaying the graphical user interface providing a second option to not clear the pending storage mapping.

17. The memory device of claim 15 , wherein the operations further include blocking power to the compute sled until the pending storage mapping is resolved.

18. The memory device of claim 15 , wherein the potential data loss is associated with the insertion of the compute sled with a first serial tag that is different than a second serial tag of the prior compute sled.

19. The memory device of claim 15 , wherein the operations further include in response to the user action, removing the pending storage mapping from a queue of pending storage mappings.

20. The memory device of claim 15 , wherein the operations further include in response to the user action, removing the graphical user interface from the display panel of the chassis.