Information handling system supporting distributed file system and compound namespace in pre-boot environment
A UEFI client initiates an SMB negotiation with a remote server for an augmented capability protocol that supports secure distributed namespace compounding via customized commands and trusted share-specific and transaction-specific data structures, referred to herein simply as secure blobs, communicated over a secure tunnel. The client platform may include a nonvolatile storage resource containing factory-installed AC modules for both the client and the server, as well as factory stored profile information for known remote shares. Upon successfully negotiating for the AC protocol, the UEFI client may retrieve and install the AC client and server modules to enable the AC protocol. The AC client may mount a local namespace, which includes a namespace folder for each remote share. The AC server module, in combination with remote share profile information provided by the AC client, enables the remote server to mount a virtual distributed namespace and function as a RVDN server.
1. A network boot method, comprising:
sending, by a unified extensible firmware image (UEFI) client executing on a client platform, a client request for a secure message block (SMB) connection with a remote server;
negotiating an augmented capability (AC) protocol with the remote server;
mounting a root directory for a virtual distributed namespace (VDN), wherein the VDN encompasses a plurality of remote shares; and
conveying profile metadata, indicative of a profile for each of the plurality of remote shares, to the remote server to establish the remote server as a remote VDN (RVND) server;
wherein the RVDN server is configured to:
establish an SMB session with each of the remote shares responsive to receiving the client request; and
responsive to receiving a data request from the UEFI client, generate a compound SMB request comprising a plurality of remote share data requests including a remote share data request corresponding to each of the plurality of remote shares.
2. The method of claim 1 , wherein communication from the UEFI client to the RVDN server includes secure blobs generated by an AC client module based, at least in part, on a profile of the RVDN conveyed within a native SMB secure tunnel.
3. The method of claim 2 , wherein the compound SMB request includes AC information, wherein the AC information includes a VDN header, indicative of the virtual domain namespace and RVDN server information.
4. The method of claim 2 , wherein the secure blobs are generated based, at least in part, on a globally unique identifier (GUID) specific to the client request.
5. The method of claim 1 , wherein mounting includes retrieving the profile metadata from a local nonvolatile data store.
6. The method of claim 5 , wherein retrieving the profile metadata comprises retrieving a secure blob indicative of the profile metadata, wherein the secure blob is generated based, at least in part, on a globally unique identifier of the data store.
7. The method of claim 1 , wherein negotiating the AC protocol includes:
retrieving an AC client module from a local data store and installing the AC client module on the UEFI client; and
retrieving an AC server module from the local data store and pushing the AC client module to the remote server.
8. An information handling system, comprising:
a central processing unit (CPU);
a system memory communicatively coupled to the CPU; and
a network interface resource configured to perform network boot operations including:
sending, by a unified extensible firmware image (UEFI) client executing on a client platform, a client request for a secure message block (SMB) connection with a remote server;
negotiating an augmented capability (AC) protocol with the remote server;
mounting a root directory for a virtual distributed namespace (VDN), wherein the VDN encompasses a plurality of remote shares; and
conveying profile metadata, indicative of a profile for each of the plurality of remote shares, to the remote server to establish the remote server as a remote VDN (RVND) server;
wherein the RVDN server is configured to:
establish an SMB session with each of the remote shares responsive to receiving the client request; and
responsive to receiving a data request from the UEFI client, generate a compound SMB request comprising a plurality of remote share data requests including a remote share data request corresponding to each of the plurality of remote shares.
9. The information handling system of claim 8 , wherein communication from the UEFI client to the RVDN server includes secure blobs generated by an AC client module based, at least in part, on a profile of the RVDN.
10. The information handling system of claim 9 , the compound SMB request includes AC information, wherein the AC information includes a VDN header, indicative of the virtual domain namespace and RVDN server information.
11. The information handling system of claim 9 , wherein the secure blobs are generated based, at least in part, on a globally unique identifier (GUID) specific to the data request.
12. The information handling system of claim 8 , wherein mounting includes retrieving the profile metadata from a local nonvolatile data store.
13. The information handling system of claim 12 , wherein retrieving the profile metadata comprises retrieving a secure blob indicative of the profile metadata, wherein the secure blob is generated based, at least in part, on a globally unique identifier of the data store.
14. The information handling system of claim 8 , wherein negotiating the AC protocol includes:
retrieving an AC client module from a local data store and installing the AC client module on the UEFI client; and
retrieving an AC server module from the local data store and pushing the AC client module to the remote server.