A physical slot authentication-based diskless node startup admission and image view allocation method

Abstract

The application discloses a kind of based on physical slot authentication's diskless node starting admission and mirror view distribution method, it is related to diskless starting admission technical field, including, to the starting request slot landing piece is carried out source link reverse challenge, and around slot reverse proof element is carried out slot closed loop reverse proof solidification, the starting admission request that closed loop reverse proof passes is encapsulated as reverse slot proof, the starting admission request that closed loop reverse proof does not pass is written in slot abnormal position, generates reverse slot proof chain;Based on slot starting admission list, the production image discovery shielding of the starting chain position that is not connected production admission mark is carried out, only returns blank discovery response and isolation discovery response, and the starting chain position that is connected production admission mark is carried out namespace alias visualization, generates slot image alias chain.The application provides slot level proof for production admission and namespace alias visualization, reduces production starting image namespace misopening risk.

Description

Technical Field

[0001] This invention relates to the field of diskless boot admission technology, and in particular to a diskless node boot admission and mirror view allocation method based on physical slot authentication. Background Technology

[0002] Diskless node booting technology is widely used in centralized operation and maintenance, batch deployment and high-density computing scenarios. The relevant technology usually involves the diskless node initiating a boot access request through the network boot link after power-on. The server discovers the request based on the node identifier, boot time, boot path and image namespace to complete the boot access control, and allocates image views to different nodes through production boot images or rescue images, thereby reducing local storage dependence and improving the centralized management capability of node images.

[0003] Existing technologies typically focus on matching node identity, network address, or pre-configured startup policies. In scenarios involving concurrent startup of multiple nodes, port link reuse, or physical slot migration, there is often a lack of closed-loop verification between the source link of the startup admission request and the actual physical slot. This is because existing processes mostly use the node identity or image permissions registered in the forward direction as the basis for admission, and rarely conduct link-by-link verification between the actual arrival link of the startup request, the ingress port location, the physical slot status, and the image namespace alias. This results in a lack of reverse verification constraints oriented towards physical slots before the image namespace is opened for production startup. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a diskless node boot admission and mirror view allocation method based on physical slot authentication to solve the problem of difficulty in closed-loop authentication of physical slot identity and secure allocation of mirror view in diskless node boot admission.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] This invention provides a method for diskless node boot admission and mirror view allocation based on physical slot authentication, comprising:

[0008] The system collects boot admission requests from diskless nodes after power-on, verifies the ingress port location of the actual link reached by the boot admission request, locks the ingress port location, and writes the slot status of the physical slot associated with the ingress port location to generate a boot request slot location fragment. It then performs a reverse challenge on the source link of the boot request slot location fragment and solidifies the slot closed-loop reverse proof around the slot's counter-proof elements. Boot admission requests that pass the closed-loop reverse proof are encapsulated as reverse slot proofs, while boot admission requests that fail the closed-loop reverse proof are written to the slot anomaly location, generating a reverse slot proof chain. Finally, it performs a unique back-connection of the reverse slot proof chain to verify the consistency between the reverse slot proof and the actual location of the request. The system establishes a unique connection between the slot fragments in the startup request and sets up separate production and isolation admissions for startup admission requests based on the unique connection status, generating a slot startup admission list. Based on the slot startup admission list, production image discovery is masked for startup chains without a continuous production admission marker, returning only blank discovery and isolation discovery responses. Namespace aliases are made explicit for startup chains with a continuous production admission marker, generating a slot image alias chain. Based on the slot image alias chain, startup image access is allocated to diskless nodes, rescue image access is restricted for diskless nodes within the isolation startup range, and abnormal image identifiers are reclaimed, generating a slot admission allocation result.

[0009] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the ingress port location verification of the actual arrival link of the boot admission request is specifically as follows:

[0010] Collect the startup admission requests after the diskless node is powered on, and collect and aggregate the startup source identifier, startup time and pre-startup request content carried in the startup admission requests to generate startup admission request access segments;

[0011] Based on the access segment of the startup admission request, the ingress port backtracking evidence is performed on the actual link reached by the startup admission request, and the port placement is suspended for the same startup admission request with multiple entry points occupied, entry point breaks and missing pre-startup bearer paths, generating an ingress port evidence chain.

[0012] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the generation of the boot request slot placement fragment is specifically as follows:

[0013] Extract the port chain bits that have locked the port position from the ingress port evidence chain, reverse locate the physical slots corresponding to the port chain bits, and paste the slot presence status and slot power supply status of the corresponding physical slots back to the port chain bits to form a slot status pasting list.

[0014] The slot status feedback list is closed into a block of slot links, and the slot placement mark is fixed for port links that have been closed. Port links that have not been closed are kept outside the production start-up scope, and a start-up request slot placement fragment is generated.

[0015] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the step of performing source link reverse challenge on the boot request slot placement segment is as follows:

[0016] Extract the startup chain position marked by the slot position from the startup request slot position fragment, perform link reverse challenge landing point locking on the startup chain position, and write the startup chain position that cannot be locked to the feedback entry into the challenge waiting range to form the source link reverse challenge list.

[0017] Extract the reverse challenge landing point and the startup request source link from the reverse challenge list of the source link, encode and bind the reverse challenge landing point, generate the slot challenge value, and send it back to the diskless node along the corresponding startup request source link. Receive the returned slot challenge response and verify it with the slot challenge value. Retain the startup chain positions that fail to send back, have missing responses, or deviate from the link to form the slot challenge feedback chain.

[0018] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the generation of the reverse slot proof chain is specifically as follows:

[0019] The slot challenge feedback chain is aggregated into slot counter-proof elements. Content that can fall into the same starting chain position is continued to the same counter-proof carrying position, and content that cannot fall into the same starting chain position is written into the counter-proof pending verification position, forming a slot counter-proof element carrying spectrum.

[0020] Extract the counter-evidence carrier position from the counter-evidence element carrier spectrum of the slot, perform authentication position compression on the counter-evidence carrier position, compress the slot challenge value, the source link of the startup request and the physical slot status to the same physical slot authentication position, and perform counter-evidence placement on the physical slot authentication position to form a slot closed-loop counter-evidence list.

[0021] Based on the slot closed-loop counter-proof list, the starting chain position of the solidified closed-loop counter-proof mark is encapsulated with reverse slot proof, and the reverse slot proof and the slot abnormal position are sequentially connected to generate the reverse slot proof chain.

[0022] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the unique connection between the verified reverse slot proof and the boot request slot placement segment is as follows:

[0023] Extract the chain position order of the reverse slot proof chain, locate the slot counter-proof elements carried by the reverse slot proof, and reconnect the slot counter-proof elements to the slot placement mark in the slot placement segment of the startup request according to the startup chain position order. Write the reconnection pointer relationship into the corresponding startup chain position to form the slot proof reconnection index.

[0024] Based on the slot proof reconnection index, a one-to-one acceptance calibration is performed on the reverse slot proof and the start request slot placement fragment in each start chain position. Chain positions where the reverse slot proof corresponds to only a single start request slot placement fragment and the start request slot placement fragment accepts only a single reverse slot proof are retained in the unique reconnection range. The positions of duplicate reconnections, empty reconnections, and cross-chain position reconnections are written into the unique reconnection reception location to form a unique reconnection verification list.

[0025] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication according to the present invention, the method for generating the slot boot admission list is characterized in that:

[0026] For the start-up chain positions within the unique connection range in the unique connection verification list, production support is continued, the unique connection reception split position is transferred to the isolated start-up support position, the connection relationship between the unique connection reception split position and the production start-up support position is severed, and the production start-up support positions and isolated start-up support positions are collected according to the start-up chain position order to form a start-up access split spectrum;

[0027] Based on the production start-up carrier position and the isolation start-up carrier position in the start-up access distribution spectrum, an access mark continuation operation is performed. The start-up chain position corresponding to the production start-up carrier position is connected to the production access mark, and the start-up chain position corresponding to the isolation start-up carrier position is connected to the isolation access mark, thereby generating a slot start-up access list.

[0028] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the step of masking the production mirror discovery for boot chain bits without continuous production admission markers is as follows:

[0029] Extract the production start access scope and isolation start scope from the slot start access list, take over the image namespace discovery request initiated by the diskless node, attach the image namespace discovery request to the corresponding start chain position, and let the image namespace discovery request enter the slot access control path first to form a namespace discovery interception chain.

[0030] The system locates the image namespace discovery request initiated by the diskless node in the namespace discovery interception chain, severs the discovery connection between the production startup image namespace and the corresponding startup chain position for startup chain positions that have not been connected to the production admission flag, and connects the blank discovery response and isolation discovery response for the corresponding startup chain position to form a namespace shielding chain.

[0031] Locate the reverse slot in the namespace shielding chain to prove the unique connection of the start chain position, extend the explicit range of the corresponding start chain position, extend the production start access range to the namespace alias explicit range, and isolate and discover the start chain position in the isolated start range to retain it, forming a namespace explicit access list.

[0032] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the generation of the slot mirror alias chain is specifically as follows:

[0033] The namespace explicit access list is mapped to a mirror view alias, the production startup image and slot configuration content are mapped to a temporary image identifier, and the temporary image identifier is bound to a slot proof to form a namespace alias explicit table.

[0034] The alias chain is aggregated in the namespace alias explicitation table. Along the startup chain in the namespace alias explicitation table, the temporary image identifier, blank discovery response, isolation discovery response and rescue image namespace alias are connected to the corresponding chain position. The temporary image identifier is restricted to the corresponding production startup access range to generate the slot image alias chain.

[0035] As a preferred embodiment of the diskless node boot admission and mirror view allocation method based on physical slot authentication described in this invention, the generation of slot admission allocation results is specifically as follows:

[0036] The binding relationship between the starting chain of the location slot image alias chain and the namespace alias is defined. The starting chain of the temporary image identifier is continued to the production image view. The starting chain of the rescue image namespace alias is continued to the rescue image access restriction position to form an image view open list.

[0037] Based on the open locations in the open list of mirror views, temporary mirror identifiers are used to open the open locations of production mirror views, and access restrictions are imposed on the access-restricted locations of rescue mirrors, thus blocking and isolating the continuation of the startup scope to the production startup mirror namespace, forming a startup view open chain;

[0038] Based on the open chain of the startup view, the startup repost content of the diskless node is checked. The startup chain position that matches the open position of the production image view is fixed as the open state of the image view. The startup chain positions that deviate from the startup chain position and the startup chain positions that repeatedly post temporary image identifiers are written to the abnormal alias recycling position to form a startup repost verification list.

[0039] Based on the startup reply verification list, the temporary image identifiers in the abnormal image identifier recycling position are recycled, the startup chain bit written to the abnormal image identifier recycling position is transferred to the isolation startup range, and the production startup completion status and rescue startup status are written, generating the slot access allocation result.

[0040] The beneficial effects of this invention are as follows: by calculating the physical slot closed-loop counter-proof value, synchronously verifying the slot challenge value feedback, the start request source link reconnection, and the physical slot status synchronization, the start chain position with insufficient closure is written into the counter-proof anomaly position, so that the reverse slot proof is only carried by the start chain position that is closed by the link, source, and slot, providing slot-level proof for production access and namespace alias disclosure, and reducing the risk of mistakenly opening the production startup image namespace. Attached Figure Description

[0041] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a flowchart of the diskless node boot admission and mirror view allocation method based on physical slot authentication.

[0043] Figure 2 A flowchart for initiating the slot placement request.

[0044] Figure 3 The flowchart for the reverse slot proof is shown.

[0045] Figure 4 A flowchart for slot admission and mirror view allocation. Detailed Implementation

[0046] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0047] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0048] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0049] Reference Figures 1-4 This is one embodiment of the present invention, which provides a diskless node boot admission and mirror view allocation method based on physical slot authentication, including the following steps:

[0050] S1: Collect the startup admission request after the diskless node is powered on, verify the ingress port location of the actual link to which the startup admission request arrives, lock the ingress port location, and write the slot status of the physical slot associated with the ingress port location and connect the status in the same position to generate the startup request slot location fragment.

[0051] S1.1: Collect the startup admission request after the diskless node is powered on, and collect the startup source identifier, startup time and pre-startup request content carried in the startup admission request to generate a startup admission request access segment.

[0052] The startup source identifier is a unique identifier that identifies the source of the startup access request for a diskless node. It is used to distinguish the source of different startup requests in a multi-node concurrent startup scenario and is used for subsequent source tracing and correspondence verification of the startup chain.

[0053] The startup time is a timestamp-like information that records the startup admission request initiated by the diskless node. It is used to determine the time sequence of startup requests and is used for subsequent link backtracking, conflict detection, and determination of the order of multiple requests.

[0054] The pre-boot request content is a set of boot preparation request information submitted by the diskless node before the formal boot execution. It is used to express the boot intent and boot conditions, and is used for subsequent matching of boot admission conditions, verification of link legality, and verification of boot path integrity.

[0055] Furthermore, for each startup access request that enters the startup access channel after the diskless node is powered on, the startup source identifier is extracted and the corresponding source path information is parsed and written into the source path positioning chain. The startup time and timestamp information are extracted and written into the time sequence chain. The pre-startup request content is extracted and decomposed into a startup intent description field and written into the startup intent carrying chain. The corresponding relationship is then encapsulated into a startup access request access fragment.

[0056] S1.2: Based on the access segment of the start admission request, perform backtracking and evidence collection on the ingress port of the actual link reached by the start admission request, and suspend the port for the same start admission request with multiple entry points occupied, entry point breaks and missing pre-start bearer paths, and generate an ingress port evidence collection chain.

[0057] Furthermore, based on the access segment of the start admission request, the actual link to which the start admission request actually arrives is located according to the start source identifier and start time. The ingress port access record is searched from the start access channel entry to the previous link acceptance position. The entry identifier, arrival time and pre-start request content in the link acceptance position are checked against the access segment of the start admission request one by one. The link acceptance position that can correspond to the same start admission request is connected as the ingress port backtracking evidence collection path, and the ingress port position is locked in the ingress port backtracking evidence collection path.

[0058] For link acceptance positions where multiple entry points occupy the same access request, write multi-entry point occupancy content; for link acceptance positions where adjacent link acceptance positions lack a continuous entry relationship, write entry point occupancy break content; for link acceptance positions where the pre-startup request content cannot be continued to the access channel entry point, write pre-startup bearer path missing content. The port chain positions corresponding to the multi-entry point occupancy content, entry point occupancy break content, and pre-startup bearer path missing content are retained in the port placement suspension range. The port chain positions that can lock the ingress port position and the port placement suspension range are continued in the order of the access request to generate the ingress port evidence chain.

[0059] S1.3: Extract the port chain bit with the locked port position from the ingress port evidence chain, reverse locate the physical slot corresponding to the port chain bit, and paste the slot presence status and slot power supply status of the corresponding physical slot back to the port chain bit to form a slot status pasting list.

[0060] Furthermore, the port chain bits with locked ingress port locations are extracted from the ingress port evidence chain. Based on the ingress port access identifier, link connection location, and startup time in the port chain bits, the physical slot corresponding to the same ingress port location is searched in the port-physical slot correspondence table. The found physical slot and port chain bits are connected to the same slot bearing location. Port chain bits that lack ingress port access identifiers or whose port-physical slot correspondence is broken are not connected to the slot bearing location.

[0061] Extract the slot presence status and slot power supply status along the physical slot corresponding to the port link, and paste the slot presence status and slot power supply status back to the corresponding port link. The slot presence status indicates that the physical slot has an in-situ connection with the diskless node, and the slot power supply status indicates that the physical slot has a power supply connection during the power-on phase. The port link, the corresponding physical slot, the slot presence status and the slot power supply status are connected to the same link position to form a slot status paste list.

[0062] It should be noted that the slot in-slot status refers to the existence of an access occupancy or connection relationship between the physical slot and the diskless node, which is used to prove that the startup admission request can be placed in the actual physical slot.

[0063] Slot power supply status refers to the physical slot having a power supply connection during the power-on phase of a diskless node, which is used to prove that the physical slot is in a startable power-on link.

[0064] The port-to-physical slot correspondence table is pre-fixed based on the inlet port wiring relationship, physical slot number, and diskless node insertion position. The substrate management controller replies the slot presence status and slot power supply status corresponding to the physical slot to the data processor, and writes the port link, corresponding physical slot, slot presence status, and slot power supply status to the same slot carrier position according to the inlet port position, forming a slot status replies list.

[0065] S1.4: Close the slot chain in the slot status reply list and mark the slot placement for the port chain that has been closed. Keep the port chain that has not been closed outside the production start-up range and generate a start-up request slot placement fragment.

[0066] Furthermore, the port chain, corresponding physical slot, slot presence status, and slot power supply status are extracted from the slot status repost list. The continuity between the ingress port position and the corresponding physical slot is checked along the port chain sequence corresponding to the start admission request. When the port chain can maintain a one-to-one correspondence between the ingress port position and the physical slot, the slot presence status and the slot power supply status can be reposted to the same port chain, and there is no link disconnection or cross-occupancy between adjacent port chains, the port chain continues as a closed segment of the slot chain.

[0067] The port links in the slot link closure segment are written with the slot placement mark, and the slot placement mark, the inlet port position, the corresponding physical slot, the slot in-slot status, and the slot power supply status are fixed to the same startup link. Port links that cannot form a slot link closure segment are not connected to the production startup range. The original port link order and slot status feedback content are retained. All port links are encapsulated according to the startup admission request order to generate a startup request slot placement segment.

[0068] It should be noted that the closure is valid based on the following conditions: the inlet port position corresponds one-to-one with the corresponding physical slot; the slot's in-position state and power supply state can be reattached in the same position; the port chain sequence is continuous and there are no multiple inlet occupants, broken inlet occupants, or missing pre-start bearing paths. If any of these conditions are missing, the closure is invalid.

[0069] S2: Perform reverse challenge on the source link of the slot fragment of the startup request, and solidify the slot closed-loop reverse proof around the slot reverse proof elements. Encapsulate the startup admission request that passes the closed-loop reverse proof into a reverse slot proof, and write the startup admission request that fails the closed-loop reverse proof into the slot exception position to generate a reverse slot proof chain.

[0070] S2.1: Extract the startup chain position marked by the slot position from the startup request slot position fragment, perform link reverse challenge landing point locking on the startup chain position, and write the startup chain position that cannot be locked back into the challenge waiting range to form the source link reverse challenge list.

[0071] Furthermore, the slot placement mark and ingress port access identifier are extracted from the slot placement fragment of the startup request chain position one by one. Starting from the link node corresponding to the startup access channel entry, the ingress port access record of the previous hop link node is extracted sequentially along the communication connection relationship. The ingress port access record of each link node is compared with the ingress port position item by item. The link nodes that can form a matching relationship are marked as candidate link nodes. The nodes among the candidate link nodes that can form a continuous connection with the slot placement mark are determined as link reverse challenge landing point locking nodes. The link entry identifier corresponding to the locking node is written into the link entry locking record.

[0072] Based on the link reverse challenge landing point locking, the connection relationship of the link entry identifier corresponding to each starting link position is checked segment by segment along the feedback path. The link entry identifier corresponding to the starting link position that cannot form a continuous connection relationship with the entry port position is written into the entry lock missing record, and the corresponding starting link position is written into the challenge pending verification range. The link entry lock record and entry lock missing record are collected in the order of the starting link positions to generate the source link reverse challenge list.

[0073] It should be noted that the slot placement marker's start chain bit refers to the start chain bit that is written into the slot placement marker and used to uniquely identify the link position of the corresponding start request after the slot status has been re-attached and the correspondence between the physical slot has been confirmed in the start request link.

[0074] S2.2: Extract the reverse challenge landing point and the start request source link from the reverse challenge list of the source link, encode and bind the reverse challenge landing point, generate the slot challenge value, and send it back to the diskless node along the corresponding start request source link. Receive the returned slot challenge response and verify it with the slot challenge value. Leave the start link positions that fail to send back, have missing responses, or deviate from the link, forming a slot challenge feedback chain.

[0075] Furthermore, the reverse challenge landing point and the startup request source link are extracted from the reverse challenge list of the source links according to the startup chain position order. The ingress port position, startup chain position and startup time corresponding to the reverse challenge landing point are encoded and bound and encapsulated into a slot challenge value. The slot challenge value is only valid within the corresponding startup chain position and startup request source link. The slot challenge value is connected to the feedback entry of the startup request source link and sent back to the diskless node segment by segment along the link receiving position. The diskless node receives the slot challenge value, writes the slot challenge value into the slot challenge response, and returns along the corresponding startup request source link.

[0076] Upon receiving the slot challenge response, verify the slot challenge value, return entry, and feedback chain position carried in the slot challenge response. Retain the starting chain positions with consistent slot challenge values, corresponding return entry positions, and continuous feedback chain positions within the slot challenge feedback range. Write the starting chain positions where the slot challenge value has not arrived, the slot challenge response is missing, the response content is inconsistent, the feedback chain position is deviated, or the return entry is inconsistent into the challenge feedback reservation position. Continuously connect the slot challenge value, slot challenge response, starting request source link, and challenge feedback reservation position in the order of the starting chain positions to form the slot challenge feedback chain. After the slot challenge value has completed response verification, been written into the challenge feedback reservation position, or written into the subsequent counter-evidence pending verification position, it will no longer be used as the basis for a reverse challenge of a non-corresponding starting chain position.

[0077] S2.3: Collect slot counter-proof elements for the slot challenge feedback chain, and continue the content that can fall in the same starting chain position to the same counter-proof carrying position. Write the content that cannot fall in the same starting chain position to the counter-proof waiting position to form a slot counter-proof element carrying spectrum.

[0078] The slot challenge feedback chain unfolds sequentially from the starting chain position. First, the feedback position of the slot challenge value is located under the same starting chain position. Then, the feedback position of the slot challenge value is checked against the feedback entry point, link acceptance position, and reverse challenge landing point in the starting request source link. If the slot challenge value can return to the same starting chain position along the starting request source link, the feedback entry point and the reverse challenge landing point can correspond, the link acceptance position does not deviate from the starting request source link, and the starting chain position has not written the challenge feedback retention position, the slot challenge value and the starting request source link are connected to the same counter-evidence bearing position.

[0079] If the slot challenge value does not return to the same starting chain position, the feedback entry does not correspond to the reverse challenge landing point, the link acceptance position deviates from the starting request source link, or the starting chain position has been written to the challenge feedback retention position, the corresponding starting chain position will be written to the counter-evidence pending verification position; the counter-evidence bearing position and the counter-evidence pending verification position will be connected in the order of the starting chain position to form the slot counter-evidence element bearing spectrum.

[0080] It should be noted that the slot counter-evidence element carrying spectrum refers to the chained proof carrying spectrum that carries the slot challenge value and the co-location relationship of the source link of the start request according to the start chain position, and classifies the content that cannot fall in the same start chain position into the counter-evidence pending verification position.

[0081] S2.4: Extract the counter-evidence carrier position from the slot counter-evidence element carrier spectrum, perform authentication position compression on the counter-evidence carrier position, compress the slot challenge value, the start request source link and the physical slot status to the same physical slot authentication position, and perform counter-evidence placement on the physical slot authentication position to form a slot closed-loop counter-evidence list.

[0082] Furthermore, the slot counter-evidence element carrying spectrum locates the counter-evidence carrying position according to the order of the start chain position. Around the same counter-evidence carrying position, the co-position relationship between the slot challenge value, the start request source link, and the physical slot status is checked. The return chain position where the slot challenge value is located is aligned with the link entry where the start request source link is located, and the link entry where the start request source link is located is aligned with the port chain position where the physical slot status is located. The chain position that is jointly undertaken is solidified as the physical slot authentication position. If the slot challenge value, the start request source link, and the physical slot status cannot all fall into the same chain position of the counter-evidence carrying position, it will not be connected to the physical slot authentication position.

[0083] The expression for the closed-loop counter-proof value of the physical slot is as follows:

[0084] ;

[0085] In the formula, This is the closed-loop counter-proof value for the physical slot. Send a corresponding marker to the slot challenge value. To initiate the peer-to-peer flag for the request source link, For physical slot status, use a corresponding marker. This refers to the number of slot challenge value feedback locations that match the link receiving locations in the startup request source link. This represents the total number of link-bearing locations in the source link of the startup request. The chain number is returned as the slot challenge value. For the reverse challenge landing point chain position number, The number of times the counter-proof position is written to the same start chain bit. The number of times the counter-evidence exception position is written to the same start chain bit. This refers to the number of valid chain bits within the same physical slot authentication location that can simultaneously carry the slot challenge value, the source link of the startup request, and the physical slot status. It is a natural constant.

[0086] The physical slot closed-loop counter-proof value is used to verify the degree of closure of the slot challenge value feedback, the start request source link reconnection, and the physical slot status alignment within the same physical slot authentication position. The more complete the link alignment, the smaller the deviation between the feedback link and the reverse challenge landing point, and the fewer the counter-proof pending verification positions and counter-proof abnormal positions, the closer the physical slot closed-loop counter-proof value is to the closed-loop state. When the physical slot closed-loop counter-proof value meets the closed-loop counter-proof writing requirements, the physical slot authentication position is written to the closed-loop counter-proof position. When the closed-loop counter-proof writing requirements are not met, the physical slot authentication position is written to the counter-proof abnormal position. The closed-loop counter-proof position and the counter-proof abnormal position are arranged in the order of the start link to form the slot closed-loop counter-proof list.

[0087] It should be noted that the formula uses "co-position closure enhancement, link fit enhancement, offset suppression, and anomaly suppression" in the same fraction to convert the slot challenge value, the source link of the startup request, and the physical slot status into a calculable physical slot closed-loop counter-proof value. The formula will only generate effective closure gain when the slot challenge value feedback, the startup request source link reconnection, and the physical slot status are all co-positioned. The more complete the link connection fit, the higher the physical slot closed-loop counter-proof value. When the feedback link position deviates from the reverse challenge landing point, the counter-proof waiting position increases, or the counter-proof anomaly position increases, the physical slot closed-loop counter-proof value will be suppressed. This ensures that the physical slot authentication position can only be written into the closed-loop counter-proof position when the link feedback, source reconnection, and slot status are co-positioned and closed, avoiding the direct formation of reverse slot proof by a single link fit or a single slot status reconnection.

[0088] S2.5: Based on the slot closed-loop counter-proof list, perform reverse slot proof encapsulation on the starting chain position of the solidified closed-loop counter-proof mark, and perform proof chain sequential continuation on the reverse slot proof and the slot abnormal position to generate the reverse slot proof chain.

[0089] Furthermore, the slot closed-loop counter-proof list is expanded chain by chain according to the order of the starting chain. For the starting chain with a fixed closed-loop counter-proof mark, the closed-loop counter-proof mark, physical slot authentication position, slot challenge value, and starting request source link are connected to the same starting chain. When encapsulating the reverse slot proof, the physical slot authentication position corresponding to the closed-loop counter-proof mark and the starting chain corresponding to the physical slot authentication position are written into the reverse slot proof, so that the reverse slot proof can carry the proof landing point relationship between the closed-loop counter-proof mark, physical slot authentication position, and starting chain. If the closed-loop counter-proof mark is not fixed, the physical slot authentication position is missing, or the closed-loop counter-proof content cannot be connected back to the same starting chain, it is written to the slot abnormal position.

[0090] The proof chain continuation revolves around the reverse slot proof and the slot anomaly position. According to the order of the starting chain positions in the slot closed-loop reverse proof list, the reverse slot proof is continuated to the corresponding starting chain position, and the slot anomaly position is continuated to the starting chain position where the slot anomaly position is written. The starting request source link is written into the slot anomaly position, and the link positions where inconsistencies occur between the feedback entry, feedback chain position and reverse challenge landing point in the starting request source link are written simultaneously to retain the starting chain position source written to the slot anomaly position. After the reverse slot proof and the slot anomaly position are continuated in the order of the starting chain positions, the reverse slot proof chain is generated.

[0091] S3: Perform unique back-connection of the reverse slot proof chain, verify the unique connection relationship between the reverse slot proof and the slot placement fragment of the startup request, and perform production access and isolation access separation on the startup access request according to the unique connection status, and generate a slot startup access list.

[0092] S3.1: Extract the chain position order of the reverse slot proof chain, locate the slot counter-proof elements carried by the reverse slot proof, and reconnect the slot counter-proof elements to the slot placement mark in the slot placement segment of the startup request according to the startup chain position order. Write the reconnection pointer relationship into the corresponding startup chain position to form the slot proof reconnection index.

[0093] Furthermore, the reverse slot proof chain unfolds in the order of the starting chain positions, locating the reverse slot proof and the chain position where the slot anomaly position is located one by one; for the starting chain position carrying the reverse slot proof, the closed-loop counter-proof mark, physical slot authentication position, slot challenge value and starting request source link written in the reverse slot proof are checked, and the content that can all point to the same starting chain position is included in the slot counter-proof element; for the starting chain position that writes the slot anomaly position, the inconsistency source between the slot anomaly position and the starting request source link is retained and not included in the slot counter-proof element callback scope.

[0094] The slot counter-proof elements are reconnected to the slot placement mark in the slot placement segment of the startup request according to the startup chain position sequence. During the reconnection, it is checked whether the startup chain position in the reverse slot proof is consistent with the startup chain position in the slot placement segment of the startup request. Then, it is checked whether the physical slot authentication position and the slot placement mark fall in the same startup chain position. Consistent slot counter-proof elements are written to the corresponding startup chain position, and the relationship between the reverse slot proof pointing to the slot placement mark and the physical slot authentication position pointing to the startup chain position is written into the reconnection pointing relationship. The reconnection pointing relationship continues along the startup chain position sequence to form the slot proof reconnection index.

[0095] S3.2: Based on the slot proof reconnection index, perform one-to-one acceptance calibration for the reverse slot proof and the start request slot placement fragment in each start chain position. Keep the chain positions where the reverse slot proof corresponds to only a single start request slot placement fragment and the start request slot placement fragment accepts only a single reverse slot proof in the unique reconnection range. Write the positions of duplicate reconnections, empty reconnections and cross-chain position reconnections into the unique reconnection reception location to form a unique reconnection verification list.

[0096] Furthermore, the slot proof callback index is expanded in the order of the startup chain position, and the slot placement mark pointed to by the reverse slot proof is checked against the slot placement mark in the startup request slot placement segment for each chain position. When the reverse slot proof points to only one startup request slot placement segment, and the startup request slot placement segment only accepts one reverse slot proof, the corresponding startup chain position is retained in the unique callback range.

[0097] The chain position where the same reverse slot proof points to multiple start request slot placement segments is written to the duplicate callback position. The chain position where the start request slot placement segment does not inherit the reverse slot proof is written to the empty callback position. The chain position where the reverse slot proof and the start request slot placement segment are not in the same start chain position is written to the cross-chain callback position. The duplicate callback position, empty callback position and cross-chain callback position are connected to the unique callback reception partition position to form the unique callback verification list.

[0098] It should be noted that repeated reconnection positions refer to the same reverse slot proof pointing to multiple startup request slot placement segments at the same time, resulting in a reverse slot proof not uniquely corresponding to the position of a startup request slot placement segment.

[0099] A missing callback position refers to a position where the startup request slot fragment does not receive the corresponding reverse slot proof, resulting in the startup chain position lacking a reverse slot proof callback source.

[0100] The cross-chain bit reconnection position refers to the fact that the starting chain bit pointed to by the reverse slot bit proof is inconsistent with the starting chain bit where the starting request slot bit fragment is located, causing the reconnection relationship to deviate from the original starting chain bit position.

[0101] S3.3: For the start-up chain positions within the unique connection range in the unique connection verification list, the production carrying capacity is continued, the unique connection reception split position is transferred to the isolated start-up carrying position, the connection relationship between the unique connection reception split position and the production start-up carrying position is severed, and the production start-up carrying positions and isolated start-up carrying positions are collected according to the start-up chain position order to form a start-up access split spectrum.

[0102] Furthermore, the unique reconnection verification list is expanded in the order of the start chain position, and the start chain position within the unique reconnection range is located one by one. The reverse slot proof, the start request slot placement segment and the slot placement mark are continued to be connected to the same production start-up bearing position. The one-to-one reconnection relationship between the reverse slot proof and the start request slot placement segment is maintained at the production start-up bearing position, so that the start chain position within the unique reconnection range can undertake the subsequent production start-up access.

[0103] The unique reception location is arranged according to the start chain position corresponding to the repeated reception location, the empty reception location, and the cross-chain position reception location. The start chain position corresponding to the repeated reception, the empty reception, and the cross-chain position reception is transferred to the isolated start bearer location, and the link connection between the unique reception location and the production start bearer location is disconnected. The production start bearer location and the isolated start bearer location are arranged according to the start chain position order to form the start access location spectrum.

[0104] It should be noted that a one-to-one callback relationship means that the reverse slot proof only callbacks to one startup request slot placement fragment, and the same startup request slot placement fragment also only undertakes a unique correspondence of one reverse slot proof.

[0105] S3.4: Based on the production start-up carrier position and the isolation start-up carrier position in the start-up access distribution spectrum, perform the access mark continuation operation, connect the start-up chain position corresponding to the production start-up carrier position to the production access mark, and connect the start-up chain position corresponding to the isolation start-up carrier position to the isolation access mark, and generate the slot start-up access list.

[0106] Furthermore, the start-up access distribution spectrum is expanded according to the start-up chain position sequence. The start-up chain position in the production start-up carrier position retains the one-to-one connection relationship between the reverse slot proof and the start-up request slot placement segment. The production start-up carrier position, start-up chain position, reverse slot proof, start-up request slot placement segment and production access mark are written into the same access list position, so that the production access mark can point to the corresponding start-up chain position and the source of the production start-up carrier position, forming a production access succession relationship.

[0107] The start-up chain position in the isolated start-up bearer position originates from the unique return reception split position. The isolated start-up bearer position, start-up chain position, unique return reception split position, and isolated access mark are written into the same access list position, and the source position of duplicate return, empty return, or cross-chain position return is retained. The isolated access mark no longer points to the production start-up bearer position. The production access succession relationship and the isolated access succession relationship are connected to the same list bearer range according to the start-up chain position order to generate the slot start-up access list.

[0108] S4: Based on the slot start-up admission list, perform production mirror discovery masking on start-up chain bits that do not have a continuous production admission mark, only return blank discovery response and isolation discovery response, and make namespace aliases explicit for start-up chain bits with a continuous production admission mark, generating slot mirror alias chain.

[0109] S4.1: Extract the production start access scope and isolation start scope from the slot start access list, take over the image namespace discovery request initiated by the diskless node, attach the image namespace discovery request to the corresponding start chain position, and let the image namespace discovery request enter the slot access control path first to form a namespace discovery interception chain.

[0110] Furthermore, the slot start-up access list is expanded in the order of the start-up chain position. The access list position with the production access mark is located and included in the production start-up access range, and the access list position with the isolation access mark is located and included in the isolation start-up range. The production start-up access range retains the same write position of the start-up chain position, the production access mark, and the production start-up carrier position, and the isolation start-up range retains the same write position of the start-up chain position, the isolation access mark, and the isolation start-up carrier position.

[0111] When an image namespace discovery request initiated by a diskless node arrives at the boot access channel, the boot source identifier carried by the image namespace discovery request is checked against the boot chain position in the slot boot admission list. Image namespace discovery requests that correspond to the same boot chain position are attached to the corresponding boot chain position. Image namespace discovery requests that have not been checked by the admission scope are not directly connected to the image namespace discovery path, but are first connected to the slot admission control path to form a namespace discovery interception chain.

[0112] It should be noted that the namespace discovery interception chain refers to the set of chain positions that accept the image namespace discovery request according to the startup chain position and retain the admission verification path before the image namespace discovery request is connected to the production startup image namespace. This chain is used to perform subsequent discovery path splitting based on the production admission mark and isolation admission mark in the slot startup admission list.

[0113] S4.2: Locate the namespace discovery interception chain for the image namespace discovery request initiated by the diskless node, cut off the discovery connection between the production startup image namespace and the corresponding startup chain position for the startup chain position that has not been connected to the production admission flag, and connect the blank discovery response and isolation discovery response for the corresponding startup chain position to form a namespace shielding chain.

[0114] Furthermore, the namespace discovery interception chain unfolds according to the startup chain position order, locates the image namespace discovery request initiated by the diskless node, and verifies the admission flag of the startup chain position where the image namespace discovery request is located; for startup chain positions that have not written the production admission flag and fall into the isolation startup range, the discovery entry of the production startup image namespace towards the corresponding startup chain position is closed, and the image namespace discovery request is removed from the production startup image namespace discovery path to prevent the isolation startup range from obtaining the production startup image namespace.

[0115] The corresponding startup chain positions are written with blank discovery responses and isolation discovery responses. The blank discovery response is used to return the status that no production startup image namespace is discoverable, and the isolation discovery response is used to limit the image namespace discovery request to the isolation startup scope. The startup chain positions for writing blank discovery responses and isolation discovery responses are arranged in the original startup chain position order, and the source of the image namespace discovery request is retained, forming a namespace shielding chain.

[0116] It should be noted that the namespace shielding chain refers to the set of chain bits that record the corresponding relationships between the production startup image namespace discovery entry closed status, blank discovery response, and isolation discovery response in the order of the startup chain bits. It is used to prevent startup chain bits that have not been followed by the production access flag from obtaining the production startup image namespace and to limit the image namespace discovery request to the isolation startup scope.

[0117] S4.3: Locate the reverse slot in the namespace shielding chain to prove the unique connection of the start chain position, extend the explicit range of the corresponding start chain position, extend the production start access range to the namespace alias explicit range, and isolate and discover the start chain position in the isolated start range to retain it, forming a namespace explicit access list.

[0118] Furthermore, the namespace shielding chain unfolds according to the startup chain position sequence, locates the startup chain position that has written the production access mark and the reverse slot proof uniquely established, verifies the production startup access range corresponding to the startup chain position in the slot startup access list, and writes the production startup access range, production access mark, corresponding startup chain position and mirror namespace discovery request into the same namespace alias disclosure range, so that the corresponding startup chain position has the qualification to subsequently disclose the temporary mirror identifier.

[0119] The startup chain position in the isolated startup scope retains blank discovery responses and isolated discovery responses. Mirror namespace discovery requests are not written to the namespace alias explicit scope. The isolated discovery bearer position retains the isolated admission flag, the corresponding startup chain position, and the isolated discovery response, which are used to limit the startup chain position in the isolated startup scope to only obtain isolated discovery content. The namespace alias explicit scope and the isolated discovery bearer position are merged into the same list bearer scope in the order of the startup chain positions to form the namespace explicit admission list.

[0120] It should be noted that the namespace alias explicit range refers to the range within which the startup chain bit in the production start access range is allowed to obtain a temporary mirror identifier. Only startup chain bits that have been written with the production access flag and whose reverse slots prove a unique callback can enter the namespace alias explicit range.

[0121] S4.4: Perform mirror view alias mapping on the namespace explicit admission list, map the production startup image and slot configuration content to temporary image identifiers, and bind the temporary image identifiers to slot proofs to form a namespace alias explicit table.

[0122] Furthermore, the namespace explicit access list is expanded in the order of the startup chain position, and the startup chain position that enters the namespace alias explicit range is located. The production startup image and slot configuration content are written to the same alias generation position. The production startup image is used to provide a view of subsequent production startup images, and the slot configuration content is used to limit the production startup image to be explicit only to the corresponding startup chain position. The alias generation position generates a temporary image identifier according to the startup chain position and writes the temporary image identifier to the corresponding startup chain position.

[0123] Slot proof binding revolves around temporary mirror identifiers and reverse slot proofs. The temporary mirror identifier, reverse slot proof, slot placement marker, and corresponding startup chain position are written to the same alias binding position, so that the temporary mirror identifier can only point to the startup chain position that has completed a unique callback. Startup chain positions that have not entered the namespace alias disclosure range are not written to the temporary mirror identifier. All alias binding positions are arranged in the order of startup chain positions to form a namespace alias disclosure table.

[0124] S4.5: Collect alias chain positions in the namespace alias explicitation table, and connect the temporary image identifier, blank discovery response, isolation discovery response and rescue image namespace alias to the corresponding chain position along the startup chain position in the namespace alias explicitation table, and limit the temporary image identifier to the corresponding production startup access range to generate the slot image alias chain.

[0125] Furthermore, the namespace alias disclosure table expands according to the startup chain position, locates the startup chain position where the temporary image identifier is written, writes the temporary image identifier to the alias chain position of the corresponding startup chain position, and simultaneously writes it to the production startup access range, so that the temporary image identifier can only be disclosed to the corresponding startup chain position within the production startup access range; the startup chain position in the namespace alias disclosure table that does not have a temporary image identifier but retains a blank discovery response, writes the blank discovery response to the corresponding alias chain position, in order to maintain the discoverable state of the namespace without production startup image.

[0126] The startup chain position in the isolation startup range is located according to the isolation admission mark to the corresponding alias chain position. The isolation discovery response and the rescue image namespace alias are written to the same alias chain position, and the source of the isolation startup bearer position is retained. The startup chain position in the isolation startup range can only obtain the rescue image namespace alias. The temporary image identifier, blank discovery response, isolation discovery response and rescue image namespace alias are arranged in the order of startup chain position to generate the slot image alias chain.

[0127] It should be noted that the rescue image namespace alias refers to the rescue image access name generated for the boot chain position in the isolated boot scope. It is used to restrict the corresponding diskless node to access the rescue image when the production boot image namespace is blocked, and to keep the rescue image access relationship bound to the corresponding boot chain position, so as to prevent diskless nodes in the isolated boot scope from accessing the production boot image.

[0128] The slot image alias chain refers to the rescue image access alias returned by the corresponding boot chain position when the boot chain position in the isolated boot range cannot obtain the production boot image namespace. It is used to limit diskless nodes to only enter the rescue image namespace and maintain the isolated boot state.

[0129] S5: Based on the slot image alias chain, allocate boot image access for diskless nodes, restrict rescue image access for diskless nodes in the isolated boot range, reclaim abnormal image identifiers, and generate slot admission allocation results.

[0130] S5.1: Locate the binding relationship between the start chain of the location slot image alias chain and the namespace alias, perform production image view continuation on the start chain of the bound temporary image identifier, and continuate the start chain of the bound rescue image namespace alias to the rescue image access restriction position to form an image view open list.

[0131] Furthermore, the slot image alias chain expands according to the startup chain position, locates the chain position where the temporary image identifier is located and the corresponding startup chain position, and verifies whether the startup chain position corresponding to the temporary image identifier is within the production startup access range; when the corresponding startup chain position is within the production startup access range, the production startup image view, temporary image identifier, production startup access range and corresponding startup chain position are written to the same image view open position, so that the production startup image view is only open to the startup chain position bound to the temporary image identifier.

[0132] The startup chain bit of the rescue image namespace alias is written into the location slot image alias chain. The source of the isolation discovery response and isolation startup bearer location is verified. The rescue image namespace alias, isolation discovery response, rescue image access restriction scope and corresponding startup chain bit are written into the same rescue image access restriction location, so that the corresponding startup chain bit can only access the rescue image through the rescue image namespace alias. The image view open location and rescue image access restriction location are arranged in the order of startup chain bit to form the image view open list.

[0133] S5.2: Based on the open locations in the open list of mirror views, temporarily mark the open locations of production mirror views as open, and restrict access to rescue mirrors at the access-restricted locations, thereby blocking the continuation of the startup scope to the production startup image namespace and forming a startup view open chain.

[0134] Furthermore, the open list of mirror views is expanded in the order of the startup chain position, locating the temporary mirror identifier, production startup access scope, and corresponding startup chain position carried by the open position of the production mirror view. The temporary mirror identifier is connected to the temporary access entry of the production startup mirror namespace, and an access relationship is established between the production startup mirror view and the corresponding startup chain position. The production startup mirror namespace only responds to access requests that carry the corresponding temporary mirror identifier and are within the production startup access scope. Startup chain positions that do not have a temporary mirror identifier or are not within the production startup access scope do not return the production startup mirror view content.

[0135] The rescue image namespace alias, isolation discovery response, and corresponding startup chain bit carried by the rescue image access restriction location are located. The rescue image namespace alias and isolation discovery response are returned to the corresponding startup chain bit in the isolation startup range, and the discovery entry of the production startup image namespace facing the isolation startup range is closed, so that the startup chain bit in the isolation startup range can only access the rescue image through the rescue image namespace alias. The production image view open position and the rescue image access restriction position are connected in the order of the startup chain bit to form the startup view open chain.

[0136] S5.3: Based on the open chain of the startup view, perform startup reply verification on the startup reply content of the diskless node, solidify the startup chain position that matches the open position of the production image view as the open state of the image view, and write the startup chain positions that deviate from the startup chain position and duplicate reply temporary image identifiers into the abnormal alias recycling position to form a startup reply verification list.

[0137] Furthermore, the startup view open chain is expanded in startup chain position order, using the production image view open position as the verification benchmark. It receives startup reply content from diskless nodes and verifies the binding relationship between the startup chain position and temporary image identifier in the diskless node startup reply content and the production image view open position. When the startup chain position in the startup reply content is consistent with the startup chain position corresponding to the production image view open position, and the temporary image identifier in the startup reply content is consistent with the temporary image identifier bound to the production image view open position, the corresponding startup chain position is written to the image view open status.

[0138] If the content of the startup reply for a diskless node deviates from the open position of the production image view, or if the temporary image identifier is repeatedly replied to by multiple startup chain positions, the corresponding startup chain position is written to the abnormal alias recycling position; the image view open status and the abnormal alias recycling position are merged into the same verification scope in the order of the startup chain positions to form a startup reply verification list.

[0139] S5.4: Based on the startup reply verification list, reclaim the temporary image identifier in the abnormal image identifier recycling position, transfer the startup chain bit written to the abnormal image identifier recycling position to the isolation startup range, and write the production startup completion status and rescue startup status to generate the slot access allocation result.

[0140] Furthermore, the abnormal image identifier recycling location is used as the temporary image identifier recycling entry point to locate the source of the startup reply content deviating from the corresponding startup chain position or the temporary image identifier being repeatedly replied to. The corresponding temporary image identifier is moved out of the access position of the production startup image namespace, and the alias recycling status is written in the original alias chain position. At the same time, the image view open status of the corresponding startup chain position is canceled, so that the production startup image namespace no longer returns the production startup image view content to the corresponding startup chain position.

[0141] Transfer the startup chain bit written to the abnormal image identifier recycling position to the isolation startup range, and write the corresponding startup chain bit, abnormal image identifier recycling position, isolation admission flag and rescue image namespace alias to the same isolation startup position; write the startup chain bit in the image view open state that is valid to the production startup completed state, write the startup chain bit in the rescue image access restricted position to the rescue startup state, and encapsulate the alias recycling state, production startup completed state and rescue startup state in the order of startup chain bit to generate slot admission allocation results.

[0142] It should be noted that the production startup completion status refers to the completion status where the startup chain obtains the production startup image view through the temporary image identifier, and the diskless node startup repost content has been aligned with the open position of the production image view.

[0143] The rescue startup state refers to an isolated startup state in which the startup chain has not obtained the production startup image namespace and can only enter the rescue image access scope through the rescue image namespace alias.

[0144] In summary, this invention calculates the physical slot closed-loop counter-proof value, simultaneously verifies the slot challenge value feedback, reconnects the startup request source link, and ensures the physical slot status is in sync. It writes the startup chain position with insufficient closure to the counter-proof anomaly position, so that the reverse slot proof is only carried by the startup chain position that is closed by the link, source, and slot. This provides slot-level proof for production access and namespace alias disclosure, reducing the risk of mistakenly opening the production startup image namespace.

[0145] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for diskless node boot admission and mirror view allocation based on physical slot authentication, characterized in that, include: Collect the startup admission request after the diskless node is powered on, verify the ingress port location of the actual link to which the startup admission request arrives, lock the ingress port location, and write the slot status of the physical slot associated with the ingress port location and connect it with the status to generate the startup request slot location fragment. The source link of the slot placement segment of the startup request is challenged, and the slot closed-loop counter-proof is solidified around the counter-proof elements of the slot. The startup admission request that passes the closed-loop counter-proof is encapsulated as a reverse slot proof, and the startup admission request that fails the closed-loop counter-proof is written to the slot abnormal position to generate a reverse slot proof chain. Perform unique back-connection of slot proof on the reverse slot proof chain, verify the unique connection relationship between the reverse slot proof and the slot placement segment of the startup request, and perform production access and isolation access separation on the startup access request according to the unique connection status, and generate a slot startup access list. Based on the slot start-up admission list, production mirror discovery is masked for start-up chain positions that do not have a continuous production admission mark, and only blank discovery response and isolation discovery response are returned. Namespace aliases are made explicit for start-up chain positions with a continuous production admission mark, and slot mirror alias chain is generated. Based on the slot image alias chain, boot image access is allocated to diskless nodes, rescue image access is restricted for diskless nodes in the isolated boot range, abnormal image identifiers are reclaimed, and slot admission allocation results are generated.

2. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 1, characterized in that, The ingress port location verification of the actual link to which the admission request arrives is performed is as follows: Collect the startup admission requests after the diskless node is powered on, and collect and aggregate the startup source identifier, startup time and pre-startup request content carried in the startup admission requests to generate startup admission request access segments; Based on the access segment of the startup admission request, the ingress port backtracking evidence is performed on the actual link reached by the startup admission request, and the port placement is suspended for the same startup admission request with multiple entry points occupied, entry point breaks and missing pre-startup bearer paths, generating an ingress port evidence chain.

3. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 2, characterized in that, The specific details of generating the startup request slot placement fragment are as follows: Extract the port chain bits that have locked the port position from the ingress port evidence chain, reverse locate the physical slots corresponding to the port chain bits, and paste the slot presence status and slot power supply status of the corresponding physical slots back to the port chain bits to form a slot status pasting list. The slot status feedback list is closed into a block of slot links, and the slot placement mark is fixed for port links that have been closed. Port links that have not been closed are kept outside the production start-up scope, and a start-up request slot placement fragment is generated.

4. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 3, characterized in that, The specific steps for performing reverse challenge on the source link of the startup request slot fragment are as follows: Extract the startup chain position marked by the slot position from the startup request slot position fragment, perform link reverse challenge landing point locking on the startup chain position, and write the startup chain position that cannot be locked to the feedback entry into the challenge waiting range to form the source link reverse challenge list. Extract the reverse challenge landing point and the startup request source link from the reverse challenge list of the source link, encode and bind the reverse challenge landing point, generate the slot challenge value, and send it back to the diskless node along the corresponding startup request source link. Receive the returned slot challenge response and verify it with the slot challenge value. Retain the startup chain positions that fail to send back, have missing responses, or deviate from the link to form the slot challenge feedback chain.

5. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 4, characterized in that, The generation of the reverse slot proof chain is as follows: The slot challenge feedback chain is aggregated into slot counter-proof elements. Content that can fall into the same starting chain position is continued to the same counter-proof carrying position, and content that cannot fall into the same starting chain position is written into the counter-proof pending verification position, forming a slot counter-proof element carrying spectrum. Extract the counter-evidence carrier position from the counter-evidence element carrier spectrum of the slot, perform authentication position compression on the counter-evidence carrier position, compress the slot challenge value, the source link of the startup request and the physical slot status to the same physical slot authentication position, and perform counter-evidence placement on the physical slot authentication position to form a slot closed-loop counter-evidence list. Based on the slot closed-loop counter-proof list, the starting chain position of the solidified closed-loop counter-proof mark is encapsulated with reverse slot proof, and the reverse slot proof and the slot abnormal position are sequentially connected to generate the reverse slot proof chain.

6. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 5, characterized in that, The unique connection between the verified reverse slot proof and the startup request slot placement segment is as follows: Extract the chain position order of the reverse slot proof chain, locate the slot counter-proof elements carried by the reverse slot proof, and reconnect the slot counter-proof elements to the slot placement mark in the slot placement segment of the startup request according to the startup chain position order. Write the reconnection pointer relationship into the corresponding startup chain position to form the slot proof reconnection index. Based on the slot proof reconnection index, a one-to-one acceptance calibration is performed on the reverse slot proof and the start request slot placement fragment in each start chain position. Chain positions where the reverse slot proof corresponds to only a single start request slot placement fragment and the start request slot placement fragment accepts only a single reverse slot proof are retained in the unique reconnection range. The positions of duplicate reconnections, empty reconnections, and cross-chain position reconnections are written into the unique reconnection reception location to form a unique reconnection verification list.

7. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 6, characterized in that, The generated slot startup admission list is as follows: For the start-up chain positions within the unique connection range in the unique connection verification list, production support is continued, the unique connection reception split position is transferred to the isolated start-up support position, the connection relationship between the unique connection reception split position and the production start-up support position is severed, and the production start-up support positions and isolated start-up support positions are collected according to the start-up chain position order to form a start-up access split spectrum; Based on the production start-up carrier position and the isolation start-up carrier position in the start-up access distribution spectrum, an access mark continuation operation is performed. The start-up chain position corresponding to the production start-up carrier position is connected to the production access mark, and the start-up chain position corresponding to the isolation start-up carrier position is connected to the isolation access mark, thereby generating a slot start-up access list.

8. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 7, characterized in that, The specific steps for masking the production mirror discovery of startup chains without continuous production access markers are as follows: Extract the production start access scope and isolation start scope from the slot start access list, take over the image namespace discovery request initiated by the diskless node, attach the image namespace discovery request to the corresponding start chain position, and let the image namespace discovery request enter the slot access control path first to form a namespace discovery interception chain. The system locates the image namespace discovery request initiated by the diskless node in the namespace discovery interception chain, severs the discovery connection between the production startup image namespace and the corresponding startup chain position for startup chain positions that have not been connected to the production admission flag, and connects the blank discovery response and isolation discovery response for the corresponding startup chain position to form a namespace shielding chain. Locate the reverse slot in the namespace shielding chain to prove the unique connection of the start chain position, extend the explicit range of the corresponding start chain position, extend the production start access range to the namespace alias explicit range, and isolate and discover the start chain position in the isolated start range to retain it, forming a namespace explicit access list.

9. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 1, characterized in that, The specific steps for generating the slot image alias chain are as follows: The namespace explicit access list is mapped to a mirror view alias, the production startup image and slot configuration content are mapped to a temporary image identifier, and the temporary image identifier is bound to a slot proof to form a namespace alias explicit table. The alias chain is aggregated in the namespace alias explicitation table. Along the startup chain in the namespace alias explicitation table, the temporary image identifier, blank discovery response, isolation discovery response and rescue image namespace alias are connected to the corresponding chain position. The temporary image identifier is restricted to the corresponding production startup access range to generate the slot image alias chain.

10. The diskless node boot admission and mirror view allocation method based on physical slot authentication as described in claim 1 or 9, characterized in that, The specific results of the generated slot admission allocation are as follows: The binding relationship between the starting chain of the location slot image alias chain and the namespace alias is defined. The starting chain of the temporary image identifier is continued to the production image view. The starting chain of the rescue image namespace alias is continued to the rescue image access restriction position to form an image view open list. Based on the open locations in the open list of mirror views, temporary mirror identifiers are used to open the open locations of production mirror views, and access restrictions are imposed on the access-restricted locations of rescue mirrors, thus blocking and isolating the continuation of the startup scope to the production startup mirror namespace, forming a startup view open chain; Based on the open chain of the startup view, the startup repost content of the diskless node is checked. The startup chain position that matches the open position of the production image view is fixed as the open state of the image view. The startup chain positions that deviate from the startup chain position and the startup chain positions that repeatedly post temporary image identifiers are written to the abnormal alias recycling position to form a startup repost verification list. Based on the startup reply verification list, the temporary image identifiers in the abnormal image identifier recycling position are recycled, the startup chain bit written to the abnormal image identifier recycling position is transferred to the isolation startup range, and the production startup completion status and rescue startup status are written, generating the slot access allocation result.

Images