DCF node configuration for device data
One example method includes receiving, at a node of a data confidence fabric (DCF), a DCF backbone, installing the DCF backbone at the node, receiving a config file at the node, and the config file includes configuration information concerning the node, and receiving and installing a trust insertion component specified in the configuration information, where operation of the trust insertion component is enabled by the DCF backbone, and the trust insertion component is operable to associate trust metadata with data received by the node.
1. A method, comprising:
receiving, at a node of a data confidence fabric (DCF), a DCF backbone;
installing the DCF backbone at the node, wherein the DCF backbone comprises multiple application program interfaces (APIs), and each of the APIs enables a different respective trust insertion component to be identified, and loaded into the DCF backbone;
receiving a config file at the node, wherein the config file describes which trust insertion technologies will be used, by which of the trust insertion components, to associate trust metadata with data received by the node, the trust insertion components update the trust metadata by adding additional trust metadata at the node, and the updated trust metadata is available to a consumer to enable the consumer to evaluate a trustworthiness of the data before consuming the data; and
receiving, from a trust insertion component catalog, and installing, into the DCF backbone, the trust insertion components described in the config file, where operation of the trust insertion components to evaluate the data and insert trust metadata concerning that data is enabled by the DCF backbone.
2. The method as recited in claim 1 , wherein the DCF backbone is blank at the time of installation at the node.
3. The method as recited in claim 1 , wherein the APIs enable the node to invoke the one or more trust insertion components.
4. The method as recited in claim 1 , wherein the node comprises hardware and/or software.
5. The method as recited in claim 1 , wherein the node is one of a gateway, edge device, or cloud.
6. The method as recited in claim 1 , wherein the config file identifies a function to be performed by the node with respect to the data received by the node.
7. The method as recited in claim 1 , wherein a device that provides the data to the node is a sensor.
8. The method as recited in claim 1 , wherein the trust insertion components, after installation in the DCF backbone, are invoked automatically as the data passes through the node.
9. The method as recited in claim 1 , wherein the DCF backbone is blank prior to loading of the trust insertion components, and the DCF backbone cannot support performance of trust insertion operations until after the trust insertion components are loaded.
10. The method as recited in claim 1 , wherein the DCF backbone is configured to be scanned by the node to enable the node to determine which of the trust insertion components are, or are not, installed at the node.
11. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
receiving, at a node of a data confidence fabric (DCF), a DCF backbone;
installing the DCF backbone at the node, wherein the DCF backbone comprises multiple application program interfaces (APIs), and each of the APIs enables a different respective trust insertion component to be identified, and loaded into the DCF backbone;
receiving a config file at the node, wherein the config file describes which trust insertion technologies will be used, by which of the trust insertion components, to associate trust metadata with data received by the node, the trust insertion components update the trust metadata by adding additional trust metadata at the node, and the updated trust metadata is available to a consumer to enable the consumer to evaluate a trustworthiness of the data before consuming the data; and
receiving, from a trust insertion component catalog, and installing, into the DCF backbone, the trust insertion components described in the config file, where operation of the trust insertion components to evaluate the data and insert trust metadata concerning that data is enabled by the DCF backbone.
12. The non-transitory storage medium as recited in claim 11 , wherein the DCF backbone is blank at the time of installation at the node.
13. The non-transitory storage medium as recited in claim 11 , wherein the APIs enable the node to invoke the one or more trust insertion components.
14. The non-transitory storage medium as recited in claim 11 , wherein the node comprises hardware and/or software.
15. The non-transitory storage medium as recited in claim 11 , wherein the node is one of a gateway, edge device, or cloud.
16. The non-transitory storage medium as recited in claim 11 , wherein the config file identifies a function to be performed by the node with respect to the data received by the node.
17. The non-transitory storage medium as recited in claim 11 , wherein a device that provides the data to the node is a sensor.
18. The non-transitory storage medium as recited in claim 11 , wherein the trust insertion components, after installation in the DCF backbone, are invoked automatically as the data passes through the node.
19. The non-transitory storage medium as recited in claim 11 , wherein the DCF backbone is blank prior to loading of the trust insertion components, and the DCF backbone cannot support performance of trust insertion operations until after the trust insertion components are loaded.
20. The non-transitory storage medium as recited in claim 11 , wherein the DCF backbone is configured to be scanned by the node to enable the node to determine which of the trust insertion components are, or are not, installed at the node.