Patent Application
20190327234
A typical fabric switch includes a central switch having many ports surrounded by a variety of fabric devices and resources for high performance computing (HPC) such as CPU, GPU, memory, storage, peripherals (which may include user workstations). HPC fabrics often integrate a fabric controller into a central processing unit (CPU) package making it both high performing and easily integrated into an ad-hoc mesh of devices and peripherals. A threat facing ad-hoc mesh systems built around HPC fabrics is the potential for rogue devices being able to inject malicious packets or act as clandestine man-in-the-middle devices observing traffic that passes over the fabric. In addition, fabric computing business models are taking fabric computing out of the ‘glass houses’ of single owner environments and placing them in shared computing environments where cooperative organizations may add capacity overtime (e.g. memory, CPU, GPU, peripherals, storage etc. . . . ). This presents a challenge in terms of accounting to keep track of resource utilization by each fabric endpoint.
The following description is presented to enable any person skilled in the art to onboard a node onto a high performance computing system that includes a fabric switch network. Various modifications to the embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. In the following description, numerous details are set forth for the purpose of explanation. However, one of ordinary skill in the art will realize that the invention might be practiced without the use of these specific details. In other instances, well-known processes are shown in block diagram form in order not to obscure the description of the invention with unnecessary detail. Identical reference numerals may be used to represent different views of the same or similar item in different drawings.
Each node 102, 102-2 may be configured to act as a computing node, a service node or a management node through programming of its CPU 302, 302-2. Nodes programmed to act as compute nodes may be used for collaborate concurrent processing of tasks. Nodes programed to act as service nodes may implement storage, specialized processing such as cryptography, graphics rendering, machine learning, computer vision, for example. Nodes programed to act as management nodes may implement BMC functionality, hot-plug, failover-recovery, for example.
In operation, slave nodes N1, N2 . . . Nn within the fabric switch partition 500 communicate with each other via the fabric switch master 510. A slave node, e.g., N1, within the partition 500 sends, over its fabric controller 302 to the fabric switch master 510, a message addressed to another slave node, e.g., N2, within the partition 500. The fabric switch master 510 receives the message and sends it to the fabric controller 302 of the slave node, e.g., N2, to which the message is addressed. It will be appreciated that although only a single partition 500 and a single fabric switch master 510 are shown, an HPC 100, 200 may include a multiplicity of different partitions.
In addition to circuitry to provide connectivity required to communicate messages over the fabric switch network 104, 104-2, the fabric controllers 302, 302-2 of the slave node endpoints N1, N2 . . . Nn and the fabric switch master 510 also include slave OAB logic circuit blocks 310 and master logic blocks 504, respectively. The slave OAB logic blocks 310 and the master OAB logic block 504 ensure that these slave nodes may be safely onboarded and their accounting identity safely created. The slave and master OAB logic blocks 310, 504 are hardened against software attacks and most hardware attacks.
The fabric controllers 302, 302-2 in some embodiments are implemented as application specific integrated circuits (ASICs). The slave and master OAB logic blocks 310, 504 may be implemented directly in a fabric controller ASIC or may be implemented as a field programmable gate array (FPGA) that integrates with fabric controller ASIC. More particularly, for example, the slave and master OAB logic blocks 310, 504 may be implemented in an FPGA that integrates closely with the fabric controller ASIC so as to allow flexibility in how accounting information is collected and stored. In some embodiments, for example, there may be custom accounting algorithms that charge a customer based on a particular pattern of usage or based on a pattern of usage by a particular set of nodes. For example, if a first set of nodes require a certain subledger accounting (SLA) while a second set of nodes requires a different SLA, then the accounting logic in the OABs of the first and second sets of nodes will be configured differently. Moreover, for example, each node may be associated with a unique accounting identifier that may be used to track node utilization statistics across the various fabric connected nodes. Usage statistics subsequently may be tapped for billing or charge-back purposes. A nodes' unique accounting identity and its usage statistics may be incorporated into a fabric packet structure so as to be transparent to workload routing optimization strategies. In other words, accounting information such a node's accounting identifiers and a node's usage statistics is collected and transmitted in the course of routine package messages. Usage statistics may be digitally signed giving them non-repudiation properties—also useful for billing and charge-back accounting.
Table A lists certain information used during onboarding of a slave node, e.g., N1, N2, . . . Nn, to a fabric switch network 104, 104-2. Table A also lists some information that is used when communicating messages among nodes during normal operation for accounting purposes.
A master's OAB logic 504 and a slave node's OAB 310 contain complementary logic used to implement a node onboarding protocol. A node's OAB 310 includes a manufacture certificate that is used to attest the node to the Master's OAB. Attestation keys may include an EPID (Enhanced Privacy ID) or traditional asymmetric key or PIN-based “pairing” techniques. The onboarding UUID is used to associate the node instance with its manifest and to provide an indication of its possession history, e.g., a chain of physical and/or legal title. An accounting UUID is assigned by a fabric network master to each of its slave nodes. Nodes cooperate to track usage statistics which are accumulated by each node's OAB 310. The node OABs 310 may report statistics securely using a reporting key.
Table B lists certain information provided within a manifest document structure that provides a history of possession associated with a slave node and is used during onboarding of the slave node to a fabric switch network.
In some embodiments, the manifest structure maintains a history of signatures of legal owners who may be involved during the supply and retail handling of the device as it moves from vendor to customer. Moreover, the manifest structure provides a record of RFID tag tracking information collected as the node moves through a supply chain. In some embodiments, the node OAB implements an owner transfer interface that creates a new onboarding UUID for the next transfer. Thus, a new unique onboarding UUID is for a node created for each onboarding of the node to a fabric switch network 104, 104-2.
During onboarding of a slave node to a fabric switch network 104, 104-2, an onboarding node, e.g., N1, and a fabric switch master, e.g., 510 that is identified as the node's new master exchange information pursuant to protocols implemented in their respective slave and master OAB circuits 310, 504 to authenticate the onboarding node N1 to its new fabric switch master 510 and to assign an accounting identifier to the node N1. The protocols involve external communications (i.e. sending and receiving messages outside the fabric switch network) with a rendezvous server 802, discussed below, over a network, e.g., network 312, external to the fabric switch network 104, 104-2. In some embodiments, the rendezvous server 802 typically includes A rendezvous server allows a vendor of a node and the purchaser of the node to recognize that node and count it against a purchase order of nodes distributed by the vendor to the purchaser.
In some embodiments, individual slave nodes' OAB logic circuits 310 may be configured to implement a blockchain by allowing one or more of the slave nodes to also implement blockchain mining functionality. In some embodiments the blockchain mining capability may be implemented in an FPGA or ASIC that is with the node's OAB. ‘Miners’ are nodes that cooperate to establish that the contents of a message are intended/expected. When a majority of nodes agree similarly the agreement is considered ‘consensus truth’ that remaining miners accept as correct. Attention is then focused on the next message (aka transaction). Implementation of the agreement protocol between ‘miners’ is more efficient, secure and reliable in hardware (FPGA, ASIC) than in software. The switch 510 may also perform blockchain mining functions with peer fabric switches possibly performing the same workloads for redundancy and failover continuity. Nodes within a single fabric may perform ‘mining’ functionality where each node contributes its vote toward consensus truth of a transaction expected result. Nodes seeking to trust other nodes may perform attestation of the node to create a whitelist/blacklist that establishes whether it is appropriate to interact as miners seeking to share in a consensus truth protocol.
The foregoing description and drawings of embodiments are illustrative and it will be understood that various modifications may be made to the embodiments by those skilled in the art without departing from the spirit and scope of this disclosure.
Example 1 is an article of manufacture that includes a storage device that includes information to cause an onboarding slave node to perform a method comprising: receiving a message that includes an address of a fabric switch master over an external network, providing an identification message that provides an indication of a manufacturing source of an onboarding slave node, over the fabric switch network, to a fabric switch master; and receiving, the permission message, over the fabric switch network, from the fabric switch master.
In Example 2, the subject matter of Example 1 optionally receiving an accounting identifier over the fabric switch network, from the fabric switch master.
In Example 3, the subject matter of Example 2 optionally includes sending the accounting identifier over the fabric switch network within a message to another node after onboarding is completed.
In Example 4, the subject matter of Example 3 optionally includes storing in a blockchain, accounting information that is associated with the accounting identifier, by the onboarding slave node, after onboarding is completed.
Example 5 is an article of manufacture that includes a storage device that includes information to cause a master node to perform a method comprising: receiving the identification message that provides an indication of a manufacturing source of an onboarding slave node, over the fabric switch network, from the onboarding slave node; and providing a permission message over the fabric switch network, to the identified onboarding slave node.
In Example 6, the subject matter of Example 5 optionally includes verifying, at the fabric switch master, an identity of the onboarding slave node based upon the received identification message.
In Example 7, the subject matter of Example 6 optionally includes wherein providing the permission message further includes providing the permission message in response to a positive verification of an identity of the onboarding slave node.
In Example 8, the subject matter of any one or more of Examples 5-7 optionally include receiving an indication of the history of the onboarding slave node over the external network; and verifying an identity of the onboarding slave node based upon the indicated manufacturing source and the indicated history of possession.
In Example 9, the subject matter of any one or more of Examples 5-8 optionally include sending an accounting identifier over the fabric switch network, to the onboarding slave node.
In Example 10, the subject matter of Example 9 optionally includes verifying after onboarding is completed, that the message sent from the onboarding slave node contains the assigned accounting identifier before routing message to the another slave node of the group.
Example 11 is a method for onboarding and accounting of devices into an HPC fabric, the method comprising: receiving a message that includes an address of a fabric switch master over an external network, providing an identification message that provides an indication of a manufacturing source of an onboarding slave node, over the fabric switch network, to a fabric switch master; and receiving, the permission message, over the fabric switch network, from the fabric switch master.
In Example 12, the subject matter of Example 11 optionally includes receiving an accounting identifier over the fabric switch network, from the fabric switch master.
In Example 13, the subject matter of Example 12 optionally includes sending the accounting identifier over the fabric switch network within a message to another node after onboarding is completed.
In Example 14, the subject matter of Example 13 optionally includes storing in a blockchain, accounting information that is associated with the accounting identifier, by the onboarding slave node, after onboarding is completed.
Example 15 is a method for onboarding and accounting of devices into an HPC fabric, the method comprising: receiving the identification message that provides an indication of a manufacturing source of an onboarding slave node, over the fabric switch network, from the onboarding slave node; and providing a permission message over the fabric switch network, to the identified onboarding slave node.
In Example 16, the subject matter of Example 15 optionally includes verifying, at the fabric switch master, an identity of the onboarding slave node based upon the received identification message.
In Example 17, the subject matter of Example 16 optionally includes wherein providing the permission message further includes providing the permission message in response to a positive verification of an identity of the onboarding slave node.
In Example 18, the subject matter of any one or more of Examples 15-17 optionally include receiving an indication of the history of the onboarding slave node over the external network; and verifying an identity of the onboarding slave node based upon the indicated manufacturing source and the indicated history of possession.
In Example 19, the subject matter of any one or more of Examples 15-18 optionally include sending an accounting identifier over the fabric switch network, to the onboarding slave node.
In Example 20, the subject matter of Example 19 optionally includes verifying after onboarding is completed, that the message sent from the onboarding slave node contains the assigned accounting identifier before routing message to the another slave node of the group.
Example 21 is a system for onboarding and accounting of devices into an HPC fabric, the system comprising: means for receiving a message that includes an address of a fabric switch master over an external network, means for providing an identification message that provides an indication of a manufacturing source of an onboarding slave node, over the fabric switch network, to a fabric switch master; and means for receiving, the permission message, over the fabric switch network, from the fabric switch master.
In Example 22, the subject matter of Example 21 optionally includes means for receiving an accounting identifier over the fabric switch network, from the fabric switch master.
In Example 23, the subject matter of Example 22 optionally includes means for sending the accounting identifier over the fabric switch network within a message to another node after onboarding is completed.
In Example 24, the subject matter of Example 23 optionally includes means for storing in a blockchain, accounting information that is associated with the accounting identifier, by the onboarding slave node, after onboarding is completed.
Example 25 is a system for onboarding and accounting of devices into an HPC fabric, the system comprising: means for receiving the identification message that provides an indication of a manufacturing source of an onboarding slave node, over the fabric switch network, from the onboarding slave node; and means for providing a permission message over the fabric switch network, to the identified onboarding slave node.
In Example 26, the subject matter of Example 25 optionally includes means for verifying, at the fabric switch master, an identity of the onboarding slave node based upon the received identification message.
In Example 27, the subject matter of Example 26 optionally includes wherein the means for providing the permission message further includes means for providing the permission message in response to a positive verification of an identity of the onboarding slave node.
In Example 28, the subject matter of any one or more of Examples 25-27 optionally include means for receiving an indication of the history of the onboarding slave node over the external network; and means for verifying an identity of the onboarding slave node based upon the indicated manufacturing source and the indicated history of possession.
In Example 29, the subject matter of any one or more of Examples 25-28 optionally include means for sending an accounting identifier over the fabric switch network, to the onboarding slave node.
In Example 30, the subject matter of Example 29 optionally includes means for verifying after onboarding is completed, that the message sent from the onboarding slave node contains the assigned accounting identifier before routing message to the another slave node of the group.
Example 31 is a high performance computing system comprising: a fabric switch network that includes a master fabric switch; and a group of slave nodes each including a central processing unit (CPU), a fabric controller to route messages over the fabric switch network to other members of the group to the master fabric switch, an input/output (I/O) circuit coupled to communicate messages over an external network, and a slave onboarding and accounting (OAB) logic block; wherein the fabric switch master is to route messages between slave nodes of the group over the fabric switch network, and includes an I/O circuit coupled to communicate messages over an external network, and includes a master OAB logic block; wherein a slave OAB logic circuit of at least one slave node is operative during onboarding of its slave node to: receive a fabric switch master address message over the at least one slave node's I/O circuit, and provide an identification message, over the at least one slave node's fabric controller to the fabric switch master, and receive, over the at least one slave node's fabric controller, a permission message from the fabric switch master; and wherein the master OAB logic circuit is operative during onboarding of the at least one slave node to: receive the identification message, over its switch master's fabric controller, from the at least one slave node, and provide the permission message, over the fabric switch master's fabric controller, to the identified at least one slave node.
In Example 32, the subject matter of Example 31 optionally includes wherein the at least one slave node identification message provides an indication of a manufacturing source of the at least one slave node.
In Example 33, the subject matter of any one or more of Examples 31-32 optionally include wherein a slave OAB logic circuit of at least one slave node is further operative during onboarding of its slave node to encrypt the onboarding slave node identification message with an encryption key that provides an indication of a manufacturing source of an onboarding slave node.
In Example 34, the subject matter of any one or more of Examples 31-33 optionally include wherein the master OAB logic circuit is further operative during onboarding of the at least one slave node to verify an identity of the at least one slave node based upon the received identification message.
In Example 35, the subject matter of any one or more of Examples 31-34 optionally include wherein the master OAB logic circuit is further operative during onboarding of the at least one slave node to: verify an identity of the at least one slave node based upon the received identification message, and provide the onboarding slave node permission message, over the fabric switch master's fabric controller to the at least one slave node, in response to a positive verification of an identity of the at least one slave node.
In Example 36, the subject matter of any one or more of Examples 31-35 optionally include wherein a slave OAB logic circuit of at least one slave node is further operative during onboarding of its slave node to provide in a message, over the at least one slave node's fabric controller, an indication of a history of possession of the at least one slave node; and wherein the master OAB logic circuit is further operative during onboarding of the at least one slave node to receive, over the fabric switch master's I/O circuit, an indication within a message of the history of possession of the at least one slave node.
In Example 37, the subject matter of any one or more of Examples 31-36 optionally include wherein the at least one identification message provides an indication of a manufacturing source of the at least one slave node; wherein a slave OAB logic circuit of at least one slave node is further operative during onboarding of its slave node to provide in the identification message an indication of a history of possession of the at least one slave node; and wherein the master OAB logic circuit is further operative during onboarding of the at least one slave node to: verify an identity of the at least one slave node based upon the indicated manufacturing source and the indicated history of possession of the at least one slave node, and provide the onboarding slave node permission message, over the fabric switch master's fabric controller to the at least one slave node, in response to positive verifications of identity and history of possession of the at least one slave node.
In Example 38, the subject matter of any one or more of Examples 31-37 optionally include wherein a slave OAB logic circuit of at least one slave node is further operative during onboarding of its slave node to receive from the fabric switch master, over the at least one slave node's fabric controller, an accounting identifier; and wherein the master OAB logic circuit is further operative during onboarding of the at least one slave node to assign and send the accounting identifier, over the fabric switch master's fabric controller, to the at least one slave node.
In Example 39, the subject matter of Example 38 optionally includes wherein a slave OAB logic circuit of at least one slave node is further operative during onboarding of its slave node to receive the accounting identifier within an encrypted message; and wherein the master OAB logic circuit is further operative during onboarding of the at least one slave node to encrypt a message that includes the accounting identifier.
In Example 40, the subject matter of any one or more of Examples 38-39 optionally include wherein the slave OAB logic circuit of at least one slave node is operative during normal of its slave node to include the accounting identifier with messages sent to other nodes within the group of slave nodes, over the at least one slave node's fabric controller.
In Example 41, the subject matter of Example 40 optionally includes wherein the master OAB logic circuit is operative during normal operation to verify that a message received from the at least one slave node contains the assigned accounting identifier before routing message to another slave node of the group.
In Example 42, the subject matter of any one or more of Examples 40-41 optionally include wherein the slave OAB logic circuit of at least one slave node is operative during normal of its slave node to store accounting information associated with an accounting identifier in a blockchain.
Example 43 is a method to onboard a slave node to a high performance computing system comprising: receiving a message that includes an address of a fabric switch master, at an onboarding slave node, over an external network, providing an identification message, by the onboarding slave node, over the fabric switch network, to the fabric switch master; receiving the identification message, at the fabric switch master, over the fabric switch network, from the onboarding slave node; providing a permission message, by the fabric switch master, over the fabric switch network, to the identified onboarding slave node; and receiving, the permission message, at the onboarding slave node, over the fabric switch network, from the fabric switch master.
In Example 44, the subject matter of Example 43 optionally includes wherein the identification message provides an indication of a manufacturing source of the onboarding slave node.
In Example 45, the subject matter of any one or more of Examples 43-44 optionally include encrypting the identification message with an encryption key that provides an indication of a manufacturing source of an onboarding slave node.
In Example 46, the subject matter of Examples 43-45 optionally includes verifying, at the fabric switch master, an identity of the onboarding slave node based upon the received identification message.
In Example 47, the subject matter of Examples 43-46 optionally includes wherein providing the permission message further includes providing the permission message in response to a positive verification of an identity of the onboarding slave node.
In Example 48, the subject matter of Examples 43-47 optionally includes wherein providing the identification message, at the onboarding slave further includes providing an indication of a manufacturing source of the onboarding slave node and providing, with the identification message, an indication of a history of possession of the onboarding slave node; and further including: receiving an indication of the history of the onboarding slave node, at the fabric switch master, over the external network; and verifying, at the fabric switch master, an identity of the onboarding slave node based upon the indicated manufacturing source and the indicated history of possession.
In Example 49, the subject matter of Examples 43-48 optionally includes receiving an accounting identifier, at the onboarding slave node, over the fabric switch network, from the fabric switch master; and sending an accounting identifier, by the fabric switch master, over the fabric switch network, to the onboarding slave node.
In Example 50, the subject matter of Examples 43-49 optionally includes including the accounting identifier within a message sent, by the onboarding slave node, after onboarding is completed, over the fabric switch network, to another node within the group of slave nodes.
In Example 51, the subject matter of Examples 43-50 optionally includes verifying, by the fabric switch master, after onboarding is completed, that the message sent from the onboarding slave node contains the assigned accounting identifier before routing message to the another slave node of the group.
In Example 52, the subject matter of Examples 43-51 optionally includes storing in a blockchain, accounting information that is associated with the accounting identifier, by the onboarding slave node, after onboarding is completed.
Example 53 is at least one machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations of any of the methods of Examples 11-20.
Example 54 is at least one machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations of any of the methods of Examples 43-52.
Example 55 is an apparatus comprising means for performing any of the methods of Examples 11-20.
Example 56 is an apparatus comprising means for performing any of the methods of Examples 43-52.
The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as “examples.” Such examples may include elements in addition to those shown or described. However, the present inventors also contemplate examples in which only those elements shown or described are provided. Moreover, the present inventors also contemplate examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
All publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.
The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with each other. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. The scope of the embodiments should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
This application is a continuation of U.S. application Ser. No. 15/392,379, filed Dec. 28, 2016, which is incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15392379 | Dec 2016 | US |
| Child | 16459082 | US |
